snaproute Go BGP Code Dive (12): Moving to Established
In last week’s post, the new BGP peer we’re tracing through the snaproute BGP code moved from open to openconfirmed by receiving, and processing, the open message. In processing the open message, the list of AFIs this peer will support was built, the hold timer set, and the hold timer started. The next step is to move to established. RFC 4271, around page 70, describes the process as—
If the local system receives a KEEPALIVE message (KeepAliveMsg (Event 26)), the local system:
- restarts the HoldTimer and
- changes its state to Established.
In response to any other event (Events 9, 12-13, 20, 27-28), the local system:
- sends a NOTIFICATION with a code of Finite State Machine Error,
- sets the ConnectRetryTimer to zero,
- releases all BGP resources,
- drops the TCP connection,
- increments the ConnectRetryCounter by 1,
- (optionally) performs peer oscillation damping if the DampPeerOscillations attribute is set to TRUE, and
- changes its state to Idle.
For a bit of review (because this is running so long, you might forget how the state machine works), the way the snaproute code is written is as a state machine. The way the state machine works is Continue reading
Dugan will replace Jack Waters who left the company in July to be CTO of the Zayo Group
The multi-IoT platform will be housed at the company’s cloud data center, which is known as the “House of Clouds.”
SDxCentral sat down with Nachman Shelef, VP & GM of HPE OpenSDN, to dig deep into HPE’s new SDN strategy & details of its OpenSDN controller.
Metaswitch also completed all certifications in HPE’s OpenNFV.
SDN provides the perfect fit for network monitoring.