I have heard that trunk links can flap if you set the physical interface to auto duplex/speed...
set port speed 5/1 100
set port duplex 5/1 full
Without these commands, it will be auto speed and duplex...then the trunk, in this case, DTP...
set trunk 5/1 auto negotiate 1-1005,1025-4094
Spantree portfast is disabled on the entire module (C6509, SUP1A). Here is why I am wondering...
5/1 errdisable 1 full 100 10/100BaseTX
5/2 errdisable 1 auto auto 10/100BaseTX
5/3 errdisable 10 auto auto 10/100BaseTX
5/4 errdisable 1 auto auto 10/100BaseTX
5/5 errdisable 10 auto auto 10/100BaseTX
5/6 errdisable 1 auto auto 10/100BaseTX
5/7 errdisable 1 full 100 10/100BaseTX
5/8 errdisable 5 auto auto 10/100BaseTX
5/9 errdisable 1 auto auto 10/100BaseTX
5/10 errdisable 1 auto auto 10/100BaseTX
5/11 errdisable 1 auto auto 10/100BaseTX
5/12 errdisable 1 auto auto 10/100BaseTX
5/13 errdisable 10 auto auto 10/100BaseTX
5/14 errdisable 1 full 100 10/100BaseTX
5/15 errdisable 1 auto auto 10/100BaseTX
5/16 errdisable 1 auto auto 10/100BaseTX
5/17 errdisable 1 auto auto 10/100BaseTX
5/18 errdisable 1 auto auto 10/100BaseTX
5/19 errdisable 1 auto auto 10/100BaseTX
5/20 errdisable 5 auto auto 10/100BaseTX
5/21 errdisable 5 auto auto 10/100BaseTX
5/22 errdisable 1 auto auto 10/100BaseTX
5/23 errdisable 5 auto auto 10/100BaseTX
5/24 errdisable 1 auto auto 10/100BaseTX
5/25 errdisable 1 full 100 10/100BaseTX
5/26 errdisable 1 auto auto 10/100BaseTX
5/27 errdisable 1 auto auto 10/100BaseTX
5/28 errdisable 1 half 100 10/100BaseTX
5/29 errdisable 1 auto auto 10/100BaseTX
5/30 errdisable 1 auto auto 10/100BaseTX
5/31 errdisable 1 auto auto 10/100BaseTX
5/32 errdisable 1 auto auto 10/100BaseTX
5/33 errdisable 1 auto auto 10/100BaseTX
5/34 errdisable 5 auto auto 10/100BaseTX
5/35 errdisable 1 auto auto 10/100BaseTX
5/36 errdisable 1 auto auto 10/100BaseTX
5/37 errdisable 1 auto auto 10/100BaseTX
5/38 errdisable 1 auto auto 10/100BaseTX
5/39 errdisable 1 auto auto 10/100BaseTX
5/40 errdisable 1 auto auto 10/100BaseTX
5/41 errdisable 1 auto auto 10/100BaseTX
5/42 errdisable 5 auto auto 10/100BaseTX
5/43 errdisable 10 auto auto 10/100BaseTX
5/44 errdisable 5 auto auto 10/100BaseTX
5/45 errdisable 1 auto auto 10/100BaseTX
5/46 errdisable 1 auto auto 10/100BaseTX
5/47 errdisable 1 full 100 10/100BaseTX
5/48 errdisable 50 auto auto 10/100BaseTX
I have not looked far into this issue...there is no "set option errport enable" global command, so they are shut down. I do see that some of the ports are set to full/100, and they are errdisable as well. The customer must not be too worried about this...lol
set port speed 5/1,5/7,5/14,5/25,5/28,5/47 100
set port duplex 5/1,5/7,5/14,5/25,5/47 full
Most ports in mod 5 are set to trunk on, not DTP. I imagine resetting module 5 may clear this up. My other questions are
1)What exactly is the command to reset the module, and
2)Would I still need to set port enable (or set option errport enable, set errdisable-timeout globally) to get the ports to come back up after a module reset?
I realize that doing this will not fix the root cause of the problem. I have not tried doing a sh errdisable-timeout yet, but I will before I do anything. Thanks in advance.
Burt
set port speed 5/1 100
set port duplex 5/1 full
Without these commands, it will be auto speed and duplex...then the trunk, in this case, DTP...
set trunk 5/1 auto negotiate 1-1005,1025-4094
Spantree portfast is disabled on the entire module (C6509, SUP1A). Here is why I am wondering...
5/1 errdisable 1 full 100 10/100BaseTX
5/2 errdisable 1 auto auto 10/100BaseTX
5/3 errdisable 10 auto auto 10/100BaseTX
5/4 errdisable 1 auto auto 10/100BaseTX
5/5 errdisable 10 auto auto 10/100BaseTX
5/6 errdisable 1 auto auto 10/100BaseTX
5/7 errdisable 1 full 100 10/100BaseTX
5/8 errdisable 5 auto auto 10/100BaseTX
5/9 errdisable 1 auto auto 10/100BaseTX
5/10 errdisable 1 auto auto 10/100BaseTX
5/11 errdisable 1 auto auto 10/100BaseTX
5/12 errdisable 1 auto auto 10/100BaseTX
5/13 errdisable 10 auto auto 10/100BaseTX
5/14 errdisable 1 full 100 10/100BaseTX
5/15 errdisable 1 auto auto 10/100BaseTX
5/16 errdisable 1 auto auto 10/100BaseTX
5/17 errdisable 1 auto auto 10/100BaseTX
5/18 errdisable 1 auto auto 10/100BaseTX
5/19 errdisable 1 auto auto 10/100BaseTX
5/20 errdisable 5 auto auto 10/100BaseTX
5/21 errdisable 5 auto auto 10/100BaseTX
5/22 errdisable 1 auto auto 10/100BaseTX
5/23 errdisable 5 auto auto 10/100BaseTX
5/24 errdisable 1 auto auto 10/100BaseTX
5/25 errdisable 1 full 100 10/100BaseTX
5/26 errdisable 1 auto auto 10/100BaseTX
5/27 errdisable 1 auto auto 10/100BaseTX
5/28 errdisable 1 half 100 10/100BaseTX
5/29 errdisable 1 auto auto 10/100BaseTX
5/30 errdisable 1 auto auto 10/100BaseTX
5/31 errdisable 1 auto auto 10/100BaseTX
5/32 errdisable 1 auto auto 10/100BaseTX
5/33 errdisable 1 auto auto 10/100BaseTX
5/34 errdisable 5 auto auto 10/100BaseTX
5/35 errdisable 1 auto auto 10/100BaseTX
5/36 errdisable 1 auto auto 10/100BaseTX
5/37 errdisable 1 auto auto 10/100BaseTX
5/38 errdisable 1 auto auto 10/100BaseTX
5/39 errdisable 1 auto auto 10/100BaseTX
5/40 errdisable 1 auto auto 10/100BaseTX
5/41 errdisable 1 auto auto 10/100BaseTX
5/42 errdisable 5 auto auto 10/100BaseTX
5/43 errdisable 10 auto auto 10/100BaseTX
5/44 errdisable 5 auto auto 10/100BaseTX
5/45 errdisable 1 auto auto 10/100BaseTX
5/46 errdisable 1 auto auto 10/100BaseTX
5/47 errdisable 1 full 100 10/100BaseTX
5/48 errdisable 50 auto auto 10/100BaseTX
I have not looked far into this issue...there is no "set option errport enable" global command, so they are shut down. I do see that some of the ports are set to full/100, and they are errdisable as well. The customer must not be too worried about this...lol
set port speed 5/1,5/7,5/14,5/25,5/28,5/47 100
set port duplex 5/1,5/7,5/14,5/25,5/47 full
Most ports in mod 5 are set to trunk on, not DTP. I imagine resetting module 5 may clear this up. My other questions are
1)What exactly is the command to reset the module, and
2)Would I still need to set port enable (or set option errport enable, set errdisable-timeout globally) to get the ports to come back up after a module reset?
I realize that doing this will not fix the root cause of the problem. I have not tried doing a sh errdisable-timeout yet, but I will before I do anything. Thanks in advance.
Burt