Hi, Last year we purchased 7x6509s running code bootflash:cat6000-sup2k8.8-4-3.bin in order to enable 802.1x. However, due to instability issues with that code related to 802.1x - our SE/account rep had asked us to force-authorize the ports - essentially disabling 802.1x till a 'stable' code was available.
However - with the ports on FA - we have experienced random yet frequent issues on multiple switches, multiple blades at different times. In each of these cases - I opened cases with TAC who txshot the issue and recommended swapping the blade.
Today, I have a similar issue on another switch in the same campus. I can furnish sh ver/tech as required.
In all cases, the symptoms are as follows : User laptop which worked fine on a known good working port - suddenly loses network connectivity and ends up in a generic 169 network. On the switch itself -
- active link lights on the affected switch port
- show port status indicates connected, but the laptop is unable to retrieve an IP address
- - if the laptop is configured with a static ip address - it still cannot ping its gateway.
- Move the laptop to another port - sometimes on the same module and it works fine getting an IP address
- a colleague of mine txshot this at one point and confirmed with Cisco that this was essentially a failure at the switch port functionality level L2.
- The problem does not affect the entire module - only some ports.
- Cisco's recommendation has been to reseat the module or replace.
Since in most cases this is an after hour change, I generally opt to replace the module instead of taking 2 maintenance windows to 'fix' a problem if reseating works only 'temporarily'.
- So far, I have not had to replace a module 'twice'. I will confirm that - just in case
In all the cases that I opened with TAC after research on CCO - I had them check hw/sw/versions etc and they have not related this to any bug - just an unofficial possible bad batch of blades. I doubt that though ... just a hunch ..
Has anyone experienced this issue
thanks much
arathy
