02-10-2015 08:28 AM
I have 2 switches, DCX managed via BNA, separate fabric, NO isl between them, up until 3 days ago it was working fine but now something changed that I am no longer able to manage/discover my switches in BNA nor I can access switch via http or web interface.
switches still ping and they are moving data since I have not lost any connections just yet.
I also have other switches being managed through the same application and the other switches work fine.
ahh yea, I can also access via CLI no problem, but need to be able to do the BNA since it is a one stop for all the fabric. I also restarted the application and same issue, switches saying "not available" I also try to re-discover via snmp and it fails?
What changed? BNA application hung? service on both switches died? windows host problems?
02-15-2015 11:52 PM
Most likely ran into one or more bugs on the switches where the weblinker or httpd process died.
You'll need to restart these or bounce the entire switch.
06-24-2015 07:32 PM
we have these problems every few months - with both the web interface and the CLI are not responding to logon. The way we recover it is via the HAfailover command. But this have to be done via the service port in front of the switch. Not very convenient becasue you need an onsite engineer.
Is there any other suggestion ?
04-29-2016 11:16 PM
->..with both the web interface and the CLI are not responding to logon.
can you ping the switch ?
switch type ? FOS Release ?
05-02-2016 04:29 AM
From the CLI, I would start to checking HA status with hashow and if state is synchronized, I would do a hafailover.
This will transfer the management to the standby cp and perform a reboot on the actual active cp.