Trap recipient Severity level : (0.5) 5ĭisplay traps and MIBs supported in Fabric OS: switch:admin> snmpTraps -show Trap Recipient's IP address : 10.26.4.102 SNMP Informs Enabled (true, t, false, f): The following is an example of configuring an SNMPv3 user recipient with a DNS name and an IPv6 address: switch:admin> snmpconfig -set snmpv3 Trap Entry 6: No trap recipient configured yet
Trap Entry 5: No trap recipient configured yet Trap Entry 4: No trap recipient configured yet Trap Entry 3: No trap recipient configured yet
Trap Recipient's IP address : 10.35.52.27 Trap Recipient's IP address : 10.35.52.33 Have physical AD and admin role as the default):Īuth Protocol : (1.3) SNMPv3 user configuration(snmp user not configured in FOS user database will SNMP Informs Enabled (true, t, false, f): t switch:admin> userconfig -add sa_user -r switchadmin -l 1-128 -h1 -c adminĪccount sa_user has been successfully added. Run the userconfig command to create a user and assign a role to it on the switch module in a virtual fabric context. switch:admin> userconfig -add fa_adm -r fabricadmin -h0 -a 0-255Īccount fa_adm has been successfully added.
Switch01:FID128:admin> snmptraps -send -trap_name cp-status-change-trap -ip_address 192.168.1.The following example shows how to configure SNMP users and traps using CLI. I have enabled frustatuschange and cpuchange traps. Switch01:FID128:admin> snmpconfig -enable mibcapability -mib_name HA-MIB -trap_name cpStatusChanged Switch01:FID128:admin> snmpconfig -enable mibcapability -mib_name HA-MIB -trap_name fruStatusChanged I have enabled HA-MIB, now I need to enable specific traps. Switch01:FID128:admin> snmpconfig -set mibcapability -mib_name HA-MIB -bitmask 1 There is a non interactive approach available and its quite easy to set it up.Īll you need the MIB name and the trap name and this can be enabled in a single line command. To enable this traps, we don't have go through all the way on setting the mibcapability. Oops, the test is failed and the reason is the status change notification MIB is disabled(hope you have noticed it on the previous step!) Unable to send trap: cp-status-change-trap : MIB is disabled Switch01:FID128:admin> snmptraps -send -trap_name cp-status-change-trap -ip_address 192.168.1.110
You have to mention the trap name and ip address of the SNMP server while using snmptraps command. With the latest versions, we have "snmptraps" which can be used to simulate the error condition. On older firmware versions, to test SNMP forwarding, we normally enable/disable the ports. SwFabricSegmentTrap (yes, y, no, n): ĬonnUnitStatusChange (yes, y, no, n): ĬonnUnitDeletedTrap (yes, y, no, n): ĬonnUnitSensorStatusChange (yes, y, no, n): ĬonnUnitPortStatusChange (yes, y, no, n): Switch01:FID128:admin> snmpconfig -set mibcapability To modify the MIB capabilty for a brocade switch, we have issue snmpconfig command along with the -set option as described below. Observe that, HA-MIB and BD-MIB are turned off here.ideally, this should be enabled to receive status change notifications. Switch01:FID128:admin> snmpconfig -show mibcapability TO view the traps which are currently enabled for a switch, issue the command as below. Brocade-specific MIB trap - Associated with the Brocade-specific Brocade MIB (SW-MIB),manages Brocade switches only.FibreAlliance MIB trap - Associated with the Fibre Alliance MIB (FA-MIB), this MIB manages SANswitches and devices from any company that complies with Fibre Alliance specifications.The management information base (MIB) is a database of monitored and managed information on a device.For Brocade, there are two main MIB trap choices: to perform that task we have to modify the MIB capability of the Brocade swith. Once the configuration is in place, the next step is to identify the traps which has to be forwarded to generate tickets. Switch01:FID128:admin> snmpconfig -show snmpv3 SNMPv1 community and trap recipient configuration: Switch01:FID128:admin> snmpconfig -show snmpv1 To check the SNMP settings, issue the command as below, Once the SNMP server IPs are configured and settings are applied, the next step is to verify the settings and do modifications in case required.