SNMP Timeout when trying to access switch via Fabric Manager
we have recently installed four new small 8 port switches and I was successfully able to discover them in Fabric Manger out of 4 I was able to do zoning changes on 3 switches and the last one when I try to access or when I trying to do zoning changes or even try to change device aliasing I'm getting SNMP timeout. they are cisco MDS9000 Series on HP blade chasis. I can acess the switches via DM and FM but when I open from FM I also see in status column as below I'm pretty much new to cisco switches.
This means port 161 is not reliably open in the path from the server that has Fabric Manager installed to the MDS switch. Since DM is working, the difference in DM and FM is that FM by default tries TCP port 161 first. DM uses UDP port 161. There may be a firwall or ACL blocking TCP 161 in the path. There may be an intermittent ethernet/ip issue.
This means Fabric Manager could not register for snmp traps using this command. snmp-server host a.b.c.d traps version 2c public udp-port 2162
It may be related to the timeouts or there are already 10 "snmp-server host" already registered. The MDS switch will support up to 10 ip addresses to send snmp traps to. If there are 10 configured, try removing one of the unneeded snmp-server hosts no snmp-server host a.b.c.d traps version 2c public udp-port 2162.
The unmanaged mode is also known as Network only switching, which is introduced in Brazos release. It adds the flexibility for customer to use only network automation for service appliance.
If a device is configured a...
Usually, we can access ESXi Shell by pressing Alt+F1 from ESXi DCUI (Direct Console User Interface).
But on HyperFlex system, it just shows black window.
This is expected behavior because HyperFlex redirects ESXi Shell output to SoL...
Configuring an Export Policy Using the GUI
This procedure explains how to configure an Export policy using the APIC GUI. Follow these steps to trigger a backup of your data:
On the menu bar, choose Admi...