To configure your StoreFabric B-Series switches to be monitored by Insight RS, complete the following sections:

The HPE FlexNetwork 5130 HI Switch Series comprises Gigabit Ethernet switches that support static and RIP Layer 3 routing, diversified services, and IPv6 forwarding, as well as provide four 10 Gigabit Ethernet (10GbE) interfaces. Hewlett Packard Enterprise Support Center HPE Support Center. To install the HP Network Discovery Tool follow these steps: From a PC (running Windows Vista SP2, Windows 7 SP1, 8, 2008 SP2 or R1 SP1, or later), type in the URL. for the HP Network Discovery Tool into a browser’s address field and press Enter. When asked, open the file. In the resulting folder, double-click on the file setup. The HP 2610-24 Switch is a fanless switch with quiet operation, making it ideal for deployments in open spaces. TheHP 2610-24-PPoE, 2610-24-PoE, and 2610-48-PoE Switches are IEEE 802.3af compliant for Power over Ethernet (PoE) andprovide up to 15.4 W for 12, 24, and 48 ports. The 2610-24-PPoE switch has 24 10/100 ports and provides 12 ports of PoE. HPE Network Discovery Tool 1.0.0.77 is free to download from our software library. The software is included in Internet & Network Tools. The actual developer of the free software is Hewlett Packard Enterprise. You've discovered and mapped your network with SolarWinds network discovery tool.

Note: Test trap support for B-series SAN switches requires the installation of Fabric Operating System v6.3.0b firmware or higher. For more details, refer to the HPE Fabric OS 6.3.0b Customer Advisory at: http://h20565.www2.hpe.com/hpsc/doc/public/display?docId=emr_na-c01924282.

Note: Telnet or SSH is required for configuration collection support. Telnet and SSH are enabled by default on StoreFabric B-Series switches.

To configure your monitored devices, complete the following sections:

You can use SNMPv1 or SNMPv3 to monitor your B-Series switches. Follow the steps in one of the options below to configure SNMP on your switch.

Use the following procedure to configure SNMP on a B-Series switch so that it can be monitored with Insight Remote Support.

1. Display the current or default SNMPv1 settings:

   > snmpconfig --show snmpv1

   SNMPv1 community and trap recipient configuration:

   Community 1: public (rw) No trap recipient configured yet

   Community 2: public (rw) No trap recipient configured yet

   Community 3: public (rw) No trap recipient configured yet

   Community 4: public (ro) No trap recipient configured yet

   Community 5: common (ro) No trap recipient configured yet

   Community 6: FibreChannel (ro) No trap recipient configured yet

2. Set SNMPv1 community string and Trap recipient:

   > snmpconfig --set snmpv1

   SNMP community and trap recipient configuration:

   Community (rw): [public] gcc-public ! Create new community

   Trap Recipient's IP address : [0.0.0.0] 1.2.3.4

   Trap recipient Severity level : (0..5) [0] 2

   Trap recipient Port : (0..65535) [162] Community (rw): [public]

   Trap Recipient's IP address : [0.0.0.0] Community (rw): [public]

   Trap Recipient's IP address : [0.0.0.0] Community (ro): [public]

   Trap Recipient's IP address : [0.0.0.0] Community (ro): [common]

   Trap Recipient's IP address : [0.0.0.0] Community (ro): [FibreChannel]

   Trap Recipient's IP address : [0.0.0.0] Committing configuration...done.

   Note: The trap severity level is associated with each trap recipient IP address. The event trap level is in conjunction with the event's severity level. When an event occurs and if its severity level is at or below the set value, the SNMP event traps (swEventTrap, swFabricWatchTrap, and connUnitEventTrap) are sent to the trap recipients.

   By default, this value is set to 0, implying that no such traps are sent. The possible values are the following:

   • 0 none
   • 1 critical
   • 2 error
   • 3 warning
   • 4 informational
   • 5 debug

3. Display the new settings:

   > snmpconfig --show snmpv1

   SNMPv1 community and trap recipient configuration:

   Community 1: gcc-public (rw) Trap recipient: 1.2.3.4 Trap port: 162 Trap recipient Severity level: 2

   Community 2: public (rw) No trap recipient configured yet

   Community 3: public (rw) No trap recipient configured yet

   Community 4: public (ro) No trap recipient configured yet

   Community 5: common (ro) No trap recipient configured yet

   Community 6: FibreChannel (ro) No trap recipient configured yet

4. Set SNMP access control:

   > snmpconfig --set accesscontrol

   SNMP access list configuration:

   Access host subnet area : [11.0.0.2] 1.2.3.4 ! set to the IP add of SIM Read/Write? (true, t, false, f): [true]

   Access host subnet area : [1.2.3.4] Read/Write? (true, t, false, f): [true] f

   Access host subnet area : [1.2.3.4] Read/Write? (true, t, false, f): [true] f

   Access host subnet area : [1.2.3.4] 0.0.0.0 ! remove this one Read/Write? (true, t, false, f): [true] f

   Access host subnet area : [1.2.3.4] Read/Write? (true, t, false, f): [true]

   Access host subnet area : [1.2.3.4] Read/Write? (true, t, false, f): [true]

   Committing configuration...done.

5. Remove the remaining IP address from the SNMP Access Control List if required:

   > snmpconfig --set accesscontrol

   SNMP access list configuration:

   Access host subnet area : [1.2.3.4] Read/Write? (true, t, false, f): [true]

   Access host subnet area : [1.2.3.4] 0.0.0.0 Read/Write? (true, t, false, f): [false] f

   Access host subnet area : [1.2.3.4] 0.0.0.0 Read/Write? (true, t, false, f): [false] f

   Access host subnet area : [0.0.0.0] Read/Write? (true, t, false, f): [false]

   Access host subnet area : [1.2.3.4] 0.0.0.0 Read/Write? (true, t, false, f): [true] f

   Access host subnet area : [1.2.3.4] 0.0.0.0 Read/Write? (true, t, false, f): [true] f

   Committing configuration...done.

6. Check the access to SNMP control list:

   > snmpconfig --show accesscontrol

   SNMP access list configuration:

   Entry 0: Access host subnet area 1.2.3.4 (rw)

   Entry 1: No access host configured yet

   Entry 2: No access host configured yet

   Entry 3: No access host configured yet

   Entry 4: No access host configured yet

   Entry 5: No access host configured yet

7. Set MIB Capability:

   > snmpconfig --set mibcapability

   The SNMP Mib/Trap Capability has been set to support FE-MIB SW-MIB FA-MIB HA-MIB SW-TRAP FA-TRAP HA-TRAP

   FA-MIB (yes, y, no, n): [yes]

   FICON-MIB (yes, y, no, n): [no]

   HA-MIB (yes, y, no, n): [yes] yes

   FCIP-MIB (yes, y, no, n): [no]

   ISCSI-MIB (yes, y, no, n): [no]

   SW-TRAP (yes, y, no, n): [yes]

   swFCPortScn (yes, y, no, n): [no] yes

   swEventTrap (yes, y, no, n): [no] yes

   swFabricWatchTrap (yes, y, no, n): [no] yes

   swTrackChangesTrap (yes, y, no, n): [no] yes

   FA-TRAP (yes, y, no, n): [yes]

   connUnitStatusChange (yes, y, no, n): [no] yes

   connUnitEventTrap (yes, y, no, n): [no] yes

   connUnitSensorStatusChange (yes, y, no, n): [no] yes

   connUnitPortStatusChange (yes, y, no, n): [no] yes

   SW-EXTTRAP (yes, y, no, n): [no] yes

8. Display the IP address of the switch, so it can be added to the Insight RS Console:

   > ipaddrshow

   SWITCH Ethernet IP Address: 1.2.3.4

   Ethernet Subnetmask: 1.2.3.4

   Fibre Channel IP Address: none

   Fibre Channel Subnetmask: none

   Gateway IP Address: 1.2.3.4

   DHCP: Off

9. Modify the switch systemgroup variables if required:

   > snmpconfig --set systemGroup

   Customizing MIB-II system variables ... At each prompt, do one of the following:

   o to accept current value,

   o enter the appropriate new value,

   o to skip the rest of configuration, or

   o to cancel any change.

   To correct any input mistake: erases the previous character, erases the whole line,

   sysDescr: [Fibre Channel Switch.] Brocade 4/16 FC Switch

   sysLocation: [End User Premise.] HPE Building 11th floor

   sysContact: [Field Support.] John Doe

   authTrapsEnabled (true, t, false, f): [true]

   Committing configuration...done.

Before configuring SNMPv3, you will need the SNMP username and appropriate credentials to be used (Auth, Priv, and passwords for each).

Important: HPE Insight RS supports the secure SNMPv3 protocol on B-Series switches that support SNMPv3. Insight RS only supports SNMPv3 traps, and does not support SNMPv3 Informs. Insight RS listens on port 1162 for SNMPv3 traps, and your SNMPv3 passwords must be at least 8 characters long. Refer to your device's documentation to determine the versions of SNMP your device supports.

To configure SNMPv3, complete the following steps. Example responses are shown in red.

1. Using PuTTY or suitable SSH access tool, SSH to the switch and login as an Administrator user.

2. Disable SNMPv1 using the following command:

   #snmpconfig –disable snmpv1

3. Configure MIB capability on the switch to enabled the HA MIB and HA TRAPS:

   #snmpconfig –set mibcapability

   FE-MIB (yes, y, no, n): [yes] <return>

   SW-MIB (yes, y, no, n): [yes] <return>

   FA-MIB (yes, y, no, n): [yes] <return>

   FICON-MIB (yes, y, no, n): [no] <return>

   HA-MIB (yes, y, no, n): [no] Yes; if already Yes then <return>

   FCIP-MIB (yes, y, no, n): [no] <return>

   IF-MIB (yes, y, no, n): [yes] <return>

   BD-MIB (yes, y, no, n): [yes] <return>

   BROCADE-MAPS-MIB (yes, y, no, n): [yes] <return>

   T11-FC-ZONE-SERVER-MIB (yes, y, no, n): [no] <return>

   SW-TRAP (yes, y, no, n): [yes] <return>

   swFCPortScn (yes, y, no, n): [yes] <return>

   swEventTrap (yes, y, no, n): [yes] <return>

   DesiredSeverity: (0..4) [0] <return>

   swIPv6ChangeTrap (yes, y, no, n): [yes] <return>

   swPmgrEventTrap (yes, y, no, n): [yes] <return>

   swFabricReconfigTrap (yes, y, no, n): [no] <return>

   swFabricSegmentTrap (yes, y, no, n): [no] <return>

   swExtTrap (yes, y, no, n): [yes] <return>

   swStateChangeTrap (yes, y, no, n): [no] <return>

   swPortMoveTrap (yes, y, no, n): [no] <return>

   swBrcdGenericTrap (yes, y, no, n): [no] <return>

   swDeviceStatusTrap (yes, y, no, n): [no] <return>

   swZoneConfigChangeTrap (yes, y, no, n): [no] <return>

   FA-TRAP (yes, y, no, n): [yes] <return>

   connUnitStatusChange (yes, y, no, n): [yes] <return>

   connUnitEventTrap (yes, y, no, n): [yes] <return>

   connUnitPortStatusChange (yes, y, no, n): [yes] <return>

   HA-TRAP (yes, y, no, n): [no] yes

   fruStatusChanged (yes, y, no, n): [no] yes

   cpStatusChanged (yes, y, no, n): [no] yes

   fruHistoryTrap (yes, y, no, n): [no] yes

   IF-TRAP (yes, y, no, n): [yes] <return>

   linkDown (yes, y, no, n): [yes] <return>

   linkUp (yes, y, no, n): [yes] <return>

   BD-TRAP (yes, y, no, n): [yes] <return>

   bdTrap (yes, y, no, n): [yes] <return>

   bdClearTrap (yes, y, no, n): [yes] <return>

   MAPS-TRAP (yes, y, no, n): [yes] <return>

4. Verify that the configuration changes have been accepted:

   #snmpconfig –show mibcapability

   FE-MIB: YES

   SW-MIB: YES

   FA-MIB: YES

   FICON-MIB: NO

   HA-MIB: YES

   FCIP-MIB: NO

   IF-MIB: YES

   BD-MIB: YES

   BROCADE-MAPS-MIB: YES

   T11-FC-ZONE-SERVER-MIB: NO

   SW-TRAP: YES

   swFCPortScn: YES

   swEventTrap: YES

   DesiredSeverity:None

   swIPv6ChangeTrap: YES

   swPmgrEventTrap: YES

   swFabricReconfigTrap: NO

   swFabricSegmentTrap: NO

   swExtTrap: YES

   swStateChangeTrap: NO

   swPortMoveTrap: NO

   swBrcdGenericTrap: NO

   swDeviceStatusTrap: NO

   swZoneConfigChangeTrap: NO

   FA-TRAP: YES

   connUnitStatusChange: YES

   connUnitEventTrap: YES

   connUnitPortStatusChange: YES

   FICON-TRAP: NO

   linkRNIDDeviceRegistration: NO

   linkRNIDDeviceDeRegistration: NO

   linkLIRRListenerAdded: NO

   linkLIRRListenerRemoved: NO

   linkRLIRFailureIncident: NO

   HA-TRAP: YES

   fruStatusChanged: YES

   cpStatusChanged: YES

   fruHistoryTrap: YES

   IF-TRAP: YES

   BD-TRAP: YES

   bdTrap: YES

   bdClearTrap: YES

   MAPS-TRAP: YES

   T11-FC-ZONE-SERVER-TRAP: NO

   t11ZsRequestRejectNotify: NO

   t11ZsMergeFailureNotify: NO

   t11ZsMergeSuccessNotify: NO

   t11ZsDefZoneChangeNotify: NO

   t11ZsActivateNotify: NO

5. Begin to configure SNMPv3. Identify a configured SNMP user to use:

   #snmpconfig -- show snmpv3

   SNMPv3 USM configuration:

   User 1 (rw): snmpadmin1

   User 2 (rw): snmpadmin2

   Auth Protocol: noAuth

   Priv Protocol: noPriv

   User 3 (rw): snmpadmin3

   User 4 (ro): snmpuser1

   Auth Protocol: noAuth

   Priv Protocol: noPriv

   User 5 (ro): snmpuser2

   User 6 (ro): snmpuser3

   Auth Protocol: noAuth

   Priv Protocol: noPriv

   SNMPv3 Trap/Informs configuration:

   Trap Entry 1: No trap recipient configured yet

   Notify Type: TRAP(1)

   Trap Entry 2: No trap recipient configured yet

   Notify Type: TRAP(1)

   Trap Entry 3: No trap recipient configured yet

   Notify Type: TRAP(1)

   Trap Entry 4: No trap recipient configured yet

   Notify Type: TRAP(1)

   Trap Entry 5: No trap recipient configured yet

   Notify Type: TRAP(1)

   Trap Entry 6: No trap recipient configured yet

   Notify Type: TRAP(1)

   Choose a user not already defined in the SNMPv3 Trap/Inform configuration. In the example above, no SNMPv3 Trap/Inform configuration has been defined so all the listed users are available for use. In this example, we will use snmpadmin1.

6. Once you have selected the SNMP user and have the appropriate credentials you want to use for the Auth/Priv configuration you can begin to configure SNMPv3.

   SNMP Informs Enabled (true, t, false, f): [false] <return>; needs to be “false”

   SNMPv3 user configuration (snmp user not configured in FOS user database will have physical AD and admin role as the default):

   User (rw): [snmpadmin1] <return>

   Auth Protocol [MD5(1)/SHA(2)/noAuth(3)]: (1..3) 1; example selects MD5

   New Auth Passwd: <enter password, must be at least 8 chracters>

   Priv Protocol [DES(1)/noPriv(2)/AES128(3)/AES256(4)]): (1..4) 1; example selects DES

   New Priv Passwd: <enter password, must be at least 8 chracters>

   User (rw): [snmpadmin2] <return>

   Auth Protocol [MD5(1)/SHA(2)/noAuth(3)]: (1..3) [3] <return>

   Priv Protocol [DES(1)/noPriv(2)/AES128(3)/AES256(4)]): (2..2) [2] <return>

   User (rw): [snmpadmin3] <return>

   Auth Protocol [MD5(1)/SHA(2)/noAuth(3)]: (1..3) [3] <return>

   Priv Protocol [DES(1)/noPriv(2)/AES128(3)/AES256(4)]): (2..2) [2] <return>

   User (ro): [snmpuser1] <return>

   Auth Protocol [MD5(1)/SHA(2)/noAuth(3)]: (1..3) [3] <return>

   Priv Protocol [DES(1)/noPriv(2)/AES128(3)/AES256(4)]): (2..2) [2] <return>

   User (ro): [snmpuser2] <return>

   Auth Protocol [MD5(1)/SHA(2)/noAuth(3)]: (1..3) [3] <return>

   Priv Protocol [DES(1)/noPriv(2)/AES128(3)/AES256(4)]): (2..2) [2] <return>

   User (ro): [snmpuser3] <return>

   Auth Protocol [MD5(1)/SHA(2)/noAuth(3)]: (1..3) [3] <return>

   Priv Protocol [DES(1)/noPriv(2)/AES128(3)/AES256(4)]): (2..2) [2] <return>

   SNMPv3 trap/inform recipient configuration:

   Trap Recipient's IP address : [0.0.0.0] <Add RS Host IP Here>

   Notify Type [TRAP(1)/INFORM(2)]: (1..1) [1] <return>; leave 1 for Traps

   UserIndex: (1..6) [1]; snmpadmin1 is the first in the list above, so 1 represents that user

   Trap recipient Severity level : (0..5) [2] 4

   Trap recipient Port : (0..65535) [162] 1162; must be 1162 for Insight RS listener

   Trap Recipient's IP address : [0.0.0.0] <return>

   Trap Recipient's IP address : [0.0.0.0] <return>

   Trap Recipient's IP address : [0.0.0.0] <return>

   Trap Recipient's IP address : [0.0.0.0] <return>

   Trap Recipient's IP address : [0.0.0.0] <return>

The configuration of the Brocade is now complete.

* Dependent on the version of SNMP used on the monitored device.

To discover your monitored devices, complete the following sections:

Create an SNMPv1 or SNMPv3 protocol credential to correspond to the protocol you configured on your switch in Option 1: Configure SNMPv1orOption 2: Configure SNMPv3.

If your device's SNMP community string is set to public and your community access mode is read only, Insight RS automatically associates an SNMPv1 protocol with your device. If you use a different community string or use a nonstandard port, you must create an SNMPv1 protocol credential in the Insight RS Console.

To configure SNMPv1 in the Insight RS Console, complete the following steps:

1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Credentials tab.
3. From the Select and Configure Protocol drop-down list, select Simple Network Management Protocol Version 1, V2C (SNMPv1, SNMPv2C).

4. Click New. The New Credential dialog box appears.

5. Type the Community String you have configured on your device.
6. Click Add.

Insight RS creates the protocol credential and it appears in the credentials table.

To configure SNMPv3 in the Insight RS Console, complete the following steps:

1. Create a Named Credential for every set of Management Group credentials:

   1. In the Insight RS Console, navigate to Company Information → Named Credentials.
   2. Click Add New Credential.
   3. Type a Credential Name, for example: Brocade SNMPv3.
   4. In the Protocol drop-down list, select Simple Network Management Protocol Version 3 (SNMPv3).
   5. Use the default port of 161.

   6. In the SNMP Account Credential fields, add:

      1. Type the Username for the user identified in Option 2: Configure SNMPv3.

      2. Account Authentication Protocol: MD5 or SHA

         The example used MD5 in Option 2: Configure SNMPv3.

      3. Account Authentication Password.

      4. Account Privacy Protocol: DES, DES3, AES128, AES192, AES256

         The example used DES in Option 2: Configure SNMPv3.

      5. Account Privacy Passphrase.

      6. Leave the Context Name blank.

   7. Click Save.

2. Add Discovery credentials for the B-Series switches:

   1. In the Insight RS Console, navigate to Discovery → Credentials.

   2. Create discovery protocol credentials for the Named Credential created earlier.

      1. In the Select and Configure Protocol drop-down list, select Simple Network Management Protocol Version 3 (SNMPv3).
      2. Click New.
      3. In the Named Credential drop-down list, select the Named Credential created earlier.
      4. Click Add.

To discover the device from the Insight RS Console, complete the following steps:

1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Discovery and click the Sources tab.

3. Expand the IP Addresses section and add the IP address for your device:

   1. Click New.
   2. Select the Single Address, Address Range, or Address List option.
   3. Type the IP address(es) of the devices to be discovered.
   4. Click Add.
4. Click Start Discovery.

Hpe Network Discovery Tool

To verify the device was discovered correctly, complete the following steps:

1. In a web browser, log on to the Insight RS Console.
2. In the main menu, select Devices and click the Device Summary tab.

3. Make sure the Status column contains a success icon ().

   If there is no success icon, see Resolve monitored device status issues for troubleshooting information.

Verify that the warranty and contract information was discovered correctly in the Insight RS Console:

1. In the Insight RS Console, navigate to Devices and click the switch Device Name.

2. Expand the Hardware section, and make sure the Acquired Serial Number and Acquired Product Number are correct. If they are not correct, type the correct values in the Override Serial Number and Override Product Number fields and click Save Changes.

   Note: If your SAN switch is covered by a critical service level contract then add CS4SAN to the Custom Delivery ID field in order to elevate the response to service events.

To verify communication between your monitored device and Insight RS, complete the following sections:

Since B-Series Fabric-OS v6.3.x was released, B-Series switches can emit test traps to ensure that the complete end-to-end event flow can be verified. The user must log on to the switch CLI admin interface and issue the following command:

Send SNMP traps to test the configuration:

1. Telnet or SSH to the B-Series switch.

2. Show the available traps you can send as tests:

   snmptraps --show

3. Send a blanket test trap for all tests:

   snmptraps --send

4. Or send a specific test trap:

   snmptraps --send --trap_name <trapname>

   For example:

   snmptraps --send -trap_name cp-status-change-trap -ip_address <hosting_device_ip>

   where <hosting_device_ip> is the IP address of the Hosting Device. If the switch reports that the test trap cannot be sent, make sure snmpmibcaps is configured to send HA traps. If it is configured correctly, this command should create a test event visible in the Insight RS Console and also submit an incident to HPE.

Note: Not all traps result in an incident being delivered to the Insight RS Console. Not all traps are sent and not all are received. Some get received as ‘unregistered event’ if you have that option selected as a receive option in Events. The events that show up as ‘unregistered’ are not compiled in the SIM Mibs. FA-MIB’s generate a valid hardware event.

See the B-Series Switch documentation for more details.

Hpe Network Switches

Collections are not automatically run after discovery. HPE recommends that you manually run a collection after discovery completes in order to verify connectivity. Run the collection schedule manually on the Collection Services → Collection Schedules tab. For more information about scheduling collections, see Manage Collection Schedules.

Verify that this collection ran successfully on the Collection Services → SAN Storage Collection Results tab in the Insight RS Console.

1. Log on to the Insight RS Console.
2. In the main menu, select Collection Services and then click the SAN Storage Collection Results tab.
3. Expand the Storage Configuration Collection section.
4. Locate the entry for your device and check the Result column. If the collection was successful, a success icon appears (). If it failed, an error icon appears ().

Hpe Switch Selector

Hpe Switch Discovery Tool Kit