
Reacting to peering policy mismatch on monday morning

Reacting to peering policy mismatch on monday morning

Incumbent’s reaction to your most recent network expansion

After a coworker enables STP on customer facing interfaces for redundancy purposes

When that old (tel)coworker discovers the routers still can do Frame Relay

When Development and Provisioning have to share the same pool of line cards

Applying the vendor’s latest workaround

Connecting few trial customers to that novel 20-slot router

Few people realise that MIT’s Remy development was heavily inspired by Remy the cat. CATNIP was replaced by DEC-POMDP.

When your first remote deployment just works

When the vendor’s TAC tells you they listen to customer feedback

“wr mem” and “do wr mem”

When customer tries to announce your own aggregated IP space

Coworker cleaning up the mail queue after accidentally the entire IS-IS process

Spotting to that person who rejected your peering proposal at the conference

When coworker leaks IPv6 NLRIs over IPv4 BGP peering sessions.

Showing the manager how the honeypot system works

The network engineer

The new PCAP archive system

IS-IS versus OSPF

Debugging problems at the internet exchange with your peers

Replicating that bug in the lab

When you try to follow the upgrade manual

When the newcomer criticises the routing policy

New Observium release

When competitor leaks full routing table to all peers

Purposefully not fixing outdated prefix-filters

Port mirroring 100GE to a 10GE

The Network Architect

IETF draft-previdi-filsfils-isis-segment-routing