Hello my friends,
Lately I have been thinking a lot about the future of networking and the career paths in this domain. As you probably know I like to guide and mentor people and with everything going on in the industry it can be confusing to find your way and to know what skills to work on to stay ahead of the curve.
I decided to reach out to some of my friends to ask them of their vision of the role of the future networking engineer and how to prepare for the changes that we are now seeing. First out is my friend Russ White who is also the co-author of the book Unintended Features that we wrote together.
Daniel: What are the major skills that people in networking need to learn to stay ahead of the curve?
Russ: Some of these have never changed — for instance, communication and abstraction. Some skills have been more important forever, such as people skills and project manage, but they never seem to really rise to the top in terms of actual demand. I don’t think this is going to change much; companies say they want people skills, and then recruit based Continue reading
The post Worth Reading: The Microsoft Ireland Case appeared first on 'net work.
The post Worth Reading: Solving network documentation with code appeared first on 'net work.
The post On the ‘net: The Foggy Future of Network Engineering appeared first on 'net work.
Last time we looked at the snaproute BGP code, we discovered the peer bringup process is a finite state machine. With this in mind, let’s try to unravel the state machine into a set of calls, beginning from our original starting point, a debug message that prints on the screen when a new peering relationship is established. The key word in the debug message was ConnEstablished,
which led to:
func (fsm *FSM) ConnEstablished() {
fsm.logger.Info(fmt.Sprintln("Neighbor:", fsm.pConf.NeighborAddress, "FSM", fsm.id, "ConnEstablished - start"))
fsm.Manager.fsmEstablished(fsm.id, fsm.peerConn.conn)
fsm.logger.Info(fmt.Sprintln("Neighbor:", fsm.pConf.NeighborAddress, "FSM", fsm.id, "ConnEstablished - end"))
}
From here, we searched for calls to ConnEstablished,
and found—
func (fsm *FSM) ChangeState(newState BaseStateIface) {
...
if oldState == BGPFSMEstablished && fsm.State.state() != BGPFSMEstablished {
fsm.ConnBroken()
} else if oldState != BGPFSMEstablished && fsm.State.state() == BGPFSMEstablished {
fsm.ConnEstablished()
}
}
Looking for ChangeState
leads us to a lot of different calls, but only one that seems to relate to establishing a new peer, as evidenced by a state that relates to established in some way. This, in turn, leads to—
func (st *OpenConfirmState) processEvent(event BGPFSMEvent, data Continue reading
The post Worth Reading: How Facebook makes you miss out on life appeared first on 'net work.
The post On the ‘Net: Big thinkers leave Cisco appeared first on 'net work.
The post On the ‘Net: You keep using that SDN word… appeared first on 'net work.
The post Worth Reading: Protecting your assets appeared first on 'net work.
The post Worth Reading: Microsoft’s Bid for LinkedIn appeared first on 'net work.
The post Worth Reading: Open Internet access on the line appeared first on 'net work.
This is a recent round table discussion I participated in over at LightReading. My friends over at ECI put this together.
The post Worth Watching: Has SDN lived up to the hype? appeared first on 'net work.
The post On the ‘net: What does a control plane do? appeared first on 'net work.
The post Worth Reading: Navigating EU safe harbor appeared first on 'net work.
The post Worth Reading: All the Apache streaming projects appeared first on 'net work.