Cisco 3850 upgrade issue

[nicohuangyi]

Hi all,

We encountered the following scenario while upgrading the 3850 Cisco switches in another office:

Putty to SSH to the master switch and perform the upgrade to ver 16.12.11, waited almost 30 mins after the switch reloaded and it still wouldn't ping through. We had to ask the local staff to help us use the console cable to check, and it turned out that the version had been upgraded successfully, except that the sfp network module didn't light up. We ran the commands 'no errdisable detect cause gbic-invalid' and 'service unsupported-transceiver' and sfp network module came back on...

May I ask if this is a common issue? Why the SFP module may go down after performing a version upgrade? Is there anything we can do to prevent it? (Or we have to rely on onsite support when problems occur...)

Thank you.

[marce1000]

  - In  general when done remotely , it's best to have a 'watching console' attached to the device for review afterwards, then errors could be seen related to it during the upgrade and or after the device has booted again (ability to watch the first-boot process too)

 M,

[nicohuangyi]

appreciate the response!