Chasis Number and Show Controller
Q1 Assume that the interface is 0/1/2
0 = chasis number
1 = slot number
2 = port number.
Does anyone know when the chasis number can ever be changed. It is always zero.
Q2 Does anyone know why troubleshooting is done on the physical card layer such as show controller??
If a card is faulty, I change the entire card. I dont need to troubleshoot what is wrong with the processor.
0 = chasis number
1 = slot number
2 = port number.
Does anyone know when the chasis number can ever be changed. It is always zero.
Q2 Does anyone know why troubleshooting is done on the physical card layer such as show controller??
If a card is faulty, I change the entire card. I dont need to troubleshoot what is wrong with the processor.
Comments
-
vinbuck
Member Posts: 785 ■■■■□□□□□□
Q1 Assume that the interface is 0/1/2
0 = chasis number
1 = slot number
2 = port number.
Does anyone know when the chasis number can ever be changed. It is always zero.
Q2 Does anyone know why troubleshooting is done on the physical card layer such as show controller??
If a card is faulty, I change the entire card. I dont need to troubleshoot what is wrong with the processor.
You need to understand things like timing, line buildout, clocking, etc to be able to effectively troubleshoot at layer 1. When I worked in the provider world, I spent the vast majority of my time troubleshooting at Layer 1 due to storms, floods and heat - all of which are not kind to networks
You don't want to keep changing cards when there is a problem on the carrier side - that gets expensive
Cisco was my first networking love, but my "other" router is a Mikrotik... -
xXErebuS
Member Posts: 230
Pardon me but do you mean by carrier side? Provider edge routers?
I think what vinbuck means is... for example... you don't want to keep changing blades out when there is an issue with the chassis.
However, it wouldn't be the first time nor last time I was wrong about something.