Does anyone know how to retrieve the last time each port on a mds 9500 series director was issued a shutdown command?
I have the problem listed in the release notes for san-os 1.3(3c) under CSCee89946 where once the uptime for a port reaches 248 days a port link reinitialization fails following a link down state change.
I have run a show port internal info command which displays 3 dates but I cannot determine which of these if any are a recording of the last time the port was shut.
This is an extract:
Lock Info: resource [fc1/1]
FREE @ 411108 usecs after Sat Aug 7 22:29:32 2004
FREE @ 963835 usecs after Mon Jun 20 00:51:40 2005
FREE @ 519076 usecs after Sat Aug 7 22:29:33 2004
I can't upgrade the SAN-OS soon due to internal change management processes, so I need to know which ports will fail soon so I can issue the workaround.
Hi Charlie, there is no need to shut/no shut every time you reboot the server. With the 248 day bug, you only need to shut/no shut the port once. As soon as you do that the port will be OK for another 248 days. Hopefully you can upgrade before the next set of 248 days lapses.
Its more a management issue that we have 130 servers connected to the SAN and 4 depts that reboot servers and so it is easier to have a process that everyone follows each time they reboot a server rather than ask them to determine whether it is neccessary or not.
VMware Trunk Port Group is supported from ACI version 2.1
VMM integration must be configured properly
ASA device package must be uploaded to APIC
ASAv version must be compatible with ACI and device package version
In the Previous articles of ACI Automation, we are using Postman/Newman as the Rest API tool to automate the ACI Configuration.
In this article I’m going to discuss on usin...
One of the first steps in building your ACI Fabric is to go through Fabric Discovery. While Fabric Discovery is usually a straightforward process, there are various issues that may prevent you from discovering an ACI switch. This article wil...