[TriLUG] Labelling conventions...

[Chris Bullock]

Although, this has been mentioned before and noses were turned up, this is
what we did while I was an intern.  I swapped out about 50 Cisco switches
and replaced them with Catalyst 4006, I was on a 20,000 node network, and
what we did was we had the name of the switch followed by port number and
on the second line the UTP #, so it would be:
switchname a24
UTP D-317

This would be at both ends of the cable, so whichever way you started you
knew where the other end was.
As far as moving switchports why would you do that, and how often do
switchports go bad?  If you move a person, you make a new label and the
same for switchports.
Regards,
Chris
--- Chris Knowles <chrisk at trilug.org> wrote:

> Should also make it clear that the # assigned to the wire is NOT the
> port number, for exactly the reasons outlined elsewhere.
> 
> It's just a number.
> 
> CJK
> 
> On Tue, 2007-12-11 at 15:05 -0500, Chris Knowles wrote:
> > Excellent suggestions... 
> > 
> > Here's what I was thinking of... 
> > 
> > We've got 23 switches, with fiber connecting them to the backbone and
> > copper out to the desks.
> > 
> > Since the label maker we have uses a 5 char label for wire, was going
> > with something like this...
> > 
> > The Switches get a label, $BUILDING + "S" + $CODE.
> > Where $BUILDING is A B or C and $CODE is A-Z identifying the switch.
> > Each building has it's own A-Z for $CODE.
> > 
> > Wires get labeled based on the switch they connect to.  This, going to
> > the first switch in building C, CSA#  Where # is 1-24... that being
> the
> > number of ports...
> > 
> > sounds to me like that's similar to the some of the other ideas...
> > 
> > However, the problem comes in with the fiber... Since it connects
> > switches, which switch gets the naming rights?  I could slap two
> labels
> > on each fiber, but that's annoying.
> > 
> > Anyway, thanks for all of your ideas and input...
> > 
> > CJK
> > 
> > 
> > 
> > On Tue, 2007-12-11 at 10:18 -0500, Chris Knowles wrote:
> > > So, we're finally upgrading/refreshing/ripping-out-and-replacing our
> > > network here at $COMPANY. 
> > > 
> > > I have inherited a rat's nest network, wires completely unlabeled,
> no
> > > wire management... it's crazy.
> > > 
> > > So I'm working to make things better... 
> > > 
> > > However, the thing that's giving me fits... labeling the wires.  I
> don't
> > > want to just label them 1, 2, 3, 4, and I also don't really want to
> > > label them "Jim's PC" "Mary's PC" etc... (This is how several labels
> > > here are currently, which is really handy as there hasn't been a
> Mary in
> > > that building for 5 years now... )
> > > 
> > > So I was wondering what you network admins out there might do... Or
> any
> > > good websites on the subject... My Google-fu is weak at the moment.
> > > 
> > > Thanks again...
> > > CJK
> > > -- 
> > > TriLUG mailing list        :
> http://www.trilug.org/mailman/listinfo/trilug
> > > TriLUG Organizational FAQ  : http://trilug.org/faq/
> > > TriLUG Member Services FAQ : http://members.trilug.org/services_faq/
> > -- 
> > TriLUG mailing list        :
> http://www.trilug.org/mailman/listinfo/trilug
> > TriLUG Organizational FAQ  : http://trilug.org/faq/
> > TriLUG Member Services FAQ : http://members.trilug.org/services_faq/
> > -- 
> TriLUG mailing list        :
> http://www.trilug.org/mailman/listinfo/trilug
> TriLUG Organizational FAQ  : http://trilug.org/faq/
> TriLUG Member Services FAQ : http://members.trilug.org/services_faq/



      ____________________________________________________________________________________
Never miss a thing.  Make Yahoo your home page. 
http://www.yahoo.com/r/hs