![brocade san switch basics brocade san switch basics](https://docplayer.net/docs-images/49/17970254/images/page_20.jpg)
MarginalPorts contributing to MARGINAL status: (0.100) 1įaultyPorts contributing to DOWN status: (0.100) įaultyPorts contributing to MARGINAL status: (0.100) 1 MarginalPorts contributing to DOWN status: (0.100) Out of range Flash contributing to MARGINAL status: (0.1) Out of range Flash contributing to DOWN status: (0.1) To change the overall switch status policy parameters the current overall switch status policy parameters:īad PowerSupplies contributing to DOWN status: (0.2) īad PowerSupplies contributing to MARGINAL status: (0.2) īad Temperatures contributing to DOWN status: (0.1) īad Temperatures contributing to MARGINAL status: (0.1) īad Fans contributing to DOWN status: (0.2) īad Fans contributing to MARGINAL status: (0.2) SANSW001:FID128:admin> switchstatuspolicyset We don’t want to transition the switch into a “ Down” status because too many ports are faulty or down, we do want to change the status to “ Marginal” as this will trigger both the “ swEventTrap” (bad port is listed in the event log) and “ swStateChangeTrap” as the switch transitioned into a “ Marginal” status. In the SSH session, execute the following commands and configure the values according to the switch type and number of utilized ports. You need to change this carefully, as we don’t want an incident to be created upon a server reboot. Reconfigure the switch status policy to correctly send events upon port changes (faulty- and/or marginal ports). SANSW001:FID128:admin> snmpconfig –enable mibcapability -mib_name SW-MIB -trap_name swStateChangeTrap SANSW001:FID128:admin> snmpconfig –enable mibcapability -mib_name SW-MIB -trap_name swEventTrap SANSW001:FID128:admin> snmpconfig –set mibcapability -mib_name SW-MIB -bitmask 1 These traps are not active by default, execute the following commands to activate them: We decided to catch only the traps: “ swEventTrap” and “ swStateChangeTrap“, where “ swEventTrap” contains events added to the system error log and “ swstatechangetrap” is triggered when the switch goes from “Online” to “Offline” or “Marginal”. The easiest way is to consult the “ Fabric OS MIB Reference Guide” and list the traps you want to catch. When an event occurs and it’s severity level is equal or below the configured value, an SNMP trap is sent to the configured SNMP trap recipients. Trap recipient severity can be one of the following values: none, critical, error, warning, informational or debug. Trap recipient Severity level : (0.5) 3 (see below for more details)
![brocade san switch basics brocade san switch basics](https://i.ebayimg.com/images/g/b7AAAOSwRTFg9q~5/s-l1600.jpg)
UserIndex: (1.6) ( refers to the customeruseraccount listed above) SNMP Informs Enabled (true, t, false, f): Īuth Protocol : (1.3) SANSW001:FID128:admin> snmpconfig –set snmpv3 Open an SSH connection to the SAN switch with an administrative account and execute the following command. The use of Microsoft System Center is not mandatory, a Nagios could do the trick as well.Ĭonfigure the SNMP trap recipients on the SAN switch.īefore we can configure the traps, we need to perform some basic SNMP configuration. We will be using Microsoft System Center Orchestrator to collect the information in the SNMP traps and push it into a incident management tool.
![brocade san switch basics brocade san switch basics](https://i.ytimg.com/vi/K5-Z6BltJw8/maxresdefault.jpg)
This blogpost will guide you through the configuration process of SNMP on Brocade SAN switches. Brocade Network Advisor can be integrated with Microsoft System Center Operations Manager with a Management Pack ( plugin).Ī different approach is by monitoring the devices with plain SNMP traps.
Brocade san switch basics software#
BNA is a tool used to manage, monitor and report (performance -, throughput visualization and many more) on fiber channel SAN switches and comes with a cost (platform hosting the software + software licenses/support). The first approach is by implementing Brocade Network Advisor (BNA). Therefore it’s important to monitor the devices correctly to ensure the operational continuity of your storage infrastructure. SAN switches are the core components in your Storage Area Network.