We kind of grouped ours: Small range dedicated to uplinks Maybe 1 through 5 Small range dedicated to cross links (VSS or VPC) Maybe 6 through 9 Large range dedicated to downlinks - Majority are here, 10 up to the max.
Works good for a normal 3 layer campus design. Since they're only locally significant, we reuse them. So on any given access layer switch, we know its uplink is a certain number assuming just one. I suppose you could break up the downlinks to correspond to a floor number in a building maybe. 10 - 19 first floor, etc. Whatever you design, plan for growth. Chuck -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Mark Tinka Sent: Thursday, March 08, 2012 6:33 AM To: [email protected] Subject: Re: [c-nsp] port channel numbering schemes On Wednesday, March 07, 2012 10:49:50 PM -Hammer- wrote: > +1 > > We don't have a formal port channel naming schema. We just go serially. Cisco's start at "1", Juniper's start at "0", so documentation is useful, although interface descriptions on both sides of the link help a lot too. We try not to match interface numbers to VLAN ID's. That works out alright when you're starting out, but as the network grows, many face-palm and hair-pulling moments :-). Mark. _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
