How do you know you're an SP-geek

  1. You're creating a multi-AS BGP test lab on Sunday evening;
  2. The core AS is running 12.2SRC code;
  3. You insert a P-router in the core network ... because every large network has P-routers;
  4. You create BGP session templates instead of configuring two parameters of a few IBGP neighbors;
  5. You configure MPLS in the core network instead of using BGP on all routers ... because it saves you a few BGP sessions ... and that's the way things should be done anyway;
  6. When configuring OSPF, you define inter-AS links as passive interfaces ... not because you're running OSPF in the other AS but for security reasons :)
  7. ... add your comment here ...


  1. 7. And then you realize you forgot it was Mother's Day
  2. You compose and deploy iACLs, then CoPP policies and GTSM, all in order to remove any possibility that your XBox 360 and your MythTV DVR might gang up try and take down an eBGP session.
  3. 8. You use penultimate hop pop in every day conversation, and then wonder why your wife looks at your weird....

    9. You use VPLS more often then Spanning Tree.

    10. You consistently bug Cisco's business units about having all devices having capable of imposing and popping tags.
  4. 7. You run MPLS TE in each core between P-routers and tunnel LDP inside TE-tunnels ... because running full mesh TE between PEs doesn't scale.
    8. You implement RTBH just in case
    9. You set up a complex communities-driven policy, even if the goal of the lab is just to test some obscure SRC feature.
  5. Your default configs have an NTP server setup, because you want all your debugs to sync up properly. :)
  6. And just when you think you have got the best SP network implemented your largest customers then forces you to add a bunch of GRE and L2TPv3 tunnels to cure *their* problems.

    Finally, your customer asked that they wanted your network to support X.25 switching :-)
Add comment