06-24-2019 08:58 AM
The problem occurs after rebooting the switch. The switch comes back up, but I am not able to ping the switch or telnet to the switch.
When connecting directly into the console of the switch, the switch is not able to ping out. Shutting down the vlan with the management IP and turning it back on brings the switch back online and I am able to ping and telnet. It is happening every time after the switch gets rebooted. I have to physically connect to the switch to bring it back online.
The switch is 3850 and I just upgraded it to 16.6.5. It seems like the problem started on the new version.
Solved! Go to Solution.
06-25-2019 12:49 AM
@yuli7641 wrote:
The switch is 3850 and I just upgraded it to 16.6.5. It seems like the problem started on the new version.
CSCvo59504
06-24-2019 10:19 AM
- Are you sure there is a functional startup configuration or does it perhaps contain errors ?
M.
06-24-2019 11:20 AM
It is a fully functional configuration on a production switch. I didn't have any issues on 3.6.8E, now after I upgraded it to 16.6.5 I am having this issue.
06-24-2019 12:10 PM
how is your network management interface connected. do you have any topology and share the configuration ?
what is the errors before you shut and shutdown the interface ?
after reboot can you post below output
show ip interface brief
06-24-2019 12:33 PM
No errors. Nothing that indicates any problem. The management IP is configured on the data vlan. The switch is connected with a trunk port to the core.
show ip int br was showing UP UP for that vlan
Interface IP-Address OK? Method Status Protocol
Vlan207 10.x.x.x YES NVRAM up up
06-25-2019 12:49 AM
@yuli7641 wrote:
The switch is 3850 and I just upgraded it to 16.6.5. It seems like the problem started on the new version.
CSCvo59504
06-25-2019 05:43 AM
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide