Installation

SAN monitoring: troubleshooting

  • SNMP mibCapability is turned off during some FOS upgrade. Most specially FCIP-MIB, enable it after the upgrade:
    SAN1:admin> snmpconfig --enable mibCapability -mib_name FCIP-MIB
    
  • General troubleshooting for Brocade based switches when connection test does not work:

    1. make sure there open port 161 UDP to the switch, on the STOR2RRD server run:
      $ perl /home/stor2rrd/stor2rrd/bin/conntest_udp.pl 192.168.1.1 161
        UDP connection to "192.168.1.1" on port "161" is ok
      
    2. Brocade note: SNMPv2 is not supported in FOS v9.0.1a but is not blocked. SNMPv2 will be blocked beginning with FOS v9.1.0.

    3. make sure that stor2rrd host/IP is on the switch access list
      SAN1:admin> snmpconfig --show accessControl
      
    4. make sure that there are allowed these mibs at least on the switch
      SAN1:admin> snmpconfig --show mibCapability
        FE-MIB: YES
        SW-MIB: YES
        FA-MIB: YES
        FICON-MIB: YES
        HA-MIB: YES
        FCIP-MIB: YES
        ISCSI-MIB: YES
        IF-MIB: YES
        BD-MIB: YES
        BROCADE-MAPS-MIB: YES
        ...
      
      Activate missing MIBs like below:
      SAN1:admin> snmpconfig --enable mibCapability -mib_name FICON-MIB
      SAN1:admin> snmpconfig --enable mibCapability -mib_name HA-MIB
      SAN1:admin> snmpconfig --enable mibCapability -mib_name FCIP-MIB
      SAN1:admin> snmpconfig --enable mibCapability -mib_name ISCSI-MIB
      SAN1:admin> snmpconfig --enable mibCapability -mib_name BD-MIB
      ...
      
      make sure it works from stor2rrd server:
      $ /opt/freeware/bin/snmpwalk -v 1 -c public <Switch IP/hostname> 1.3.6.1.2.1.75.1.1.1
        SNMPv2-SMI::mib-2.75.1.1.1.0 = Hex-STRING: 10 00 00 27 F8 6E 88 CD 
      
    5. make sure community string is proper for v1 and v2c
      SAN1:admin> snmpconfig --show snmpv1
      
    6. set SNMP GET security level to 0
      SAN1:admin> snmpconfig --show seclevel
      
      SAN1:admin> snmpconfig --set seclevel
        Select SNMP GET Security Level
        (0 = No security, 1 = Authentication only, 2 = Authentication and Privacy, 3 = No Access): (0..3) [3] 0
      
  • Note a potential CPU issue on switches when you use vFabric support.

  • In case you find below error during initial configuration then follow this page
    $ cd /home/stor2rrd/stor2rrd/logs
    $ tail -1 err.log-<Switch IP>
      Can't load '/opt/freeware/lib/perl5/vendor_perl/5.8.8/ppc-thread-multi/auto/NetSNMP/default_store/default_store.so' for module NetSNMP::default_store:
      Could not load module /opt/freeware/lib/libnetsnmp.a(libnetsnmp.so.25).
      Dependent module /usr/lib/libcrypto.a(libcrypto.so.1.0.1) could not be loaded.
      Member libcrypto.so.1.0.1 is not found in archive
    
  • STOR2RRD presents bad health status even if the switch is fine
    # snmpwalk -v 2c -c public <Switch IP/hostname> 1.3.6.1.3.94.1.6.1.6
    SNMPv2-SMI::experimental.94.1.6.1.6.16.0.136.148.113.64.127.199.0.0.0.0.0.0.0.0 = INTEGER: 5
    
    It should return "3".
    HPE support adviced to do hareboot and it helped, now it returns "3" what means that it is ok. More information

  • Check our forum or contact us via support@stor2rrd.com

Debug data

To be able to debug SAN switch connectivity we would need this data:
  1. from the switch:
    SAN1:admin> snmpconfig --show seclevel
    SAN1:admin> snmpconfig --show mibCapability
    SAN1:admin> snmpconfig --show accessControl
    
  2. IP address of STOR2RRD server
    ifconfig -a
    
  3. this output:
    # snmpwalk -v 2c -c public <Switch IP/hostname> 1.3.6.1.3.94.1.6.1.6