On 06/07/16 17:44, Adrian Minta wrote:
On 07/04/2016 04:29 PM, Chris Welti wrote:
Hi all,
I can confirm that the bug has been fixed in 03.18.01.S / 15.6(2)S1
which is now out on CCO.
Caution, after the first reload when you upgrade from a previous
version, there will be a FPGA upgrade and thus a second (automatic)
reboot.
Consider a longer maintenance window since a reload takes its times on
these devices :)
Best regards,
Chris
The bug is 99% fixed.
The log message when you remove the sfp+ transceiver is "changed state
to administratively down" but this is mostly a cosmetic issue.
You are right, I didn't even catch that.
In my logs:
Jul 7 13:29:21.220: %LINK-5-CHANGED: Interface TenGigabitEthernet0/0/26,
changed state to administratively down
Jul 7 13:29:24.238: %LINK-3-UPDOWN: Interface TenGigabitEthernet0/0/26,
changed state to down
Jul 7 13:37:58.873: %LINK-5-CHANGED: Interface TenGigabitEthernet0/0/26,
changed state to administratively down
Jul 7 13:38:01.859: %LINK-3-UPDOWN: Interface TenGigabitEthernet0/0/26,
changed state to down
Maybe they still put it to admin down but have an EEM script that re-enables it
again as a workaround :-)
I currently don't have one in the lab anymore, could you check when you just
remove a transceiver you get a second message with
"changed state to down" after 3 seconds as well?
Chris
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
