Testing L2 Connectivity In A Data Centre/ Naming COnvention Of Line Cards

hitmen

Dear guys,

I am currently working in a data centre and I am experiencing some trouble.

The switch connectivity for my test bed is haywire. Since they are switches, they are L2 and I cannot ping to test connectivity. What should I do in this case? Visual fault locator are too expensive for me.

Secondly, I understand that the naming convention for my equipment are chasis/slot/module/port. As far as I know, the chasis and module are always zero. Are there any situations where the chasis or module are not zero. If so, pls give example. Thanks.

Priston

What model switches are you working with? Are you asking where 0/1/0/1 is physically on the chassis?

asrivastava0202

you cab assign IP address to VLAN 1 on each switch and test the connectivity ...

hitmen

Priston wrote: »

What model switches are you working with? Are you asking where 0/1/0/1 is physically on the chassis?

ASR9000 series. However, the chasis number and the module number is always zero which I never unbderstand why.

oli356

You can cluster the chassis and there is your 1/0/0/0, so two chassis.

Depending on the line card the module will change. For example if you have a MOD80 with 2 MPA's in then the module number will be different.

1/3/1/5
Chassis 1, slot 3 (MOD80), module 1 (MPA), port 5.

hitmen

Hi!
The correct answer I got from my senior is to use the show mac-address dynamic command to see if mac addresses have been learnt. SVI not necessary at L2.

Roguetadhg

Wait.
You're working on an ASR 9000 series switch, on a test bed, and a visual fault locator is too expensive?