Configuring an integration for SNMP Discovery
Note
If your switches use ACLs, you must add the IO Platform IP address to those configurations.
Note
Switches that have an IPv6 address on the mgmt0 interface should not be configured for use with this integration.
From the Settings screen, click Integrations in the Probes and Integrations section.
The Integrations screen displays.
Click View under Cisco SAN.
The Cisco SAN screen displays.
The column headings in the main part of the screen are defined as follows:
Column Heading
Definition
Name
User-defined name for the integration, often the integration IP address or the type of integration. For example, Brocade_BNA_27, or seed_switch_1.
Subscription
Unsubscribed or Subscribed.
For Cisco SAN Integration and Brocade SAN Integration only, if subscribed, shows a ratio of the number of configured switches that are subscribed/the total number of configured switches. For example, 1/5 means that one configured switch is subscribed, out of 5 possible configured switches.
Last Discovery
Date and time that the integration was last discovered, discovering for currently discovering, no discovery, Discovery failed, or Warned. For Discovery fail or discovery Warned, you can mouse over the cell shows the error or warning as a tool tip.
Last Metrics Collection
Date and time of last metrics collection, Collecting metrics for metrics collection in progress, Metrics collection failed for failed metrics collection, followed by a ratio of the number of failed subscribed switches to total subscribed switches, no collection for no metrics collection, or Warned followed by a timestamp and with no ratio, for a warning. For both failures and warnings, there is no mouse-over tool tip and the user has to drill down and see the failures /warnings in the switch grid.
You are notified if an integration fails to collect metrics for two hours. The notification takes the form of a IO Health Notification as well as an email notification.
At the end of each row is a down arrow, which, if you click it, provides a short cut to Configure, Test Connection, Start Discovery, or Delete the integration in the associated row.
Click New.
The New Cisco SAN screen displays.
Enter the details for a Cisco seed switch connection:
Note
An NPV-enabled switch cannot be used as a seed switch.
Name for the integration discovery instance
The Name field can be edited after the configuration is saved.
Hostname/IP as an IP address
Optional IP (secondary) as an IP address
SNMP Timeout (sec)
SNMP Max Timeouts
SNMP Version (v1, v2c, v3 Auth Privacy, v3 Auth No Privacy, v3 No Auth No Privacy)
Community: Default is public
Enable or disable the Disable GetBulk Operation check box
Depending on the SNMP version detected, there might be more or fewer values to enter.
Click Next.
IO tests the connection to the seed switch and tries to find all of the switches accessible from that seed switch. This process can take up to five minutes. When the process completes, the Create New Integration screen displays.
The Vendor, Hostname / IP, Secondary IP, and SNMP version details are carried over from the previous screen. The Name field is user configurable.
Enter the integration Name.
Regularly scheduled discovery is enabled for Cisco SAN Integration and Brocade SAN Integration configurations by default. You can specify the Frequency and Time of Day of discovery. Uncheck the Enable scheduled discovery check box if you would like to disable regularly scheduled discovery.
You can also enable Mini Discovery (disabled by default) and specify the frequency in minutes. If you disable (uncheck) scheduled discovery, Mini is also disabled.
If mini discovery is disabled, full discovery discovers and detects changes in FCIDs for both FC Ports and Proxy FC Ports.
If mini is enabled:
Full discovery does not discover FCIDs for FC Ports or Proxy FC Ports.
Mini discovery discovers FCIDs for FC Ports or Proxy FC Ports immediately after the first full discovery finishes, and then associates FCID with FC Port.
Mini discovery detects changes in FCIDs and updates existing FCIDs.
Optionally, click Test Connection to test the connection.
The switches in the Switches table on the Create New window are those switches that were auto-detected.
You use the information in the Switches table to configure/unconfigure and subscribe/unsubscribe specific switches.The columns headings in the Switches table are defined as follows:
Table 29. Switches Table FieldsFields
Definition
Switch Name
Auto-detected name of the switch.
Port Count
Active port count.
Status
Discovered, Configured, Subscribed.
Last Metrics Collection
Date and time of last metrics collection, Collecting metrics for metrics collection in progress, metrics collection failed, or no collection for no collection.
You are notified if a software integration fails to collect metrics for two hours. The notification takes the form of a IO Health Notification alert as well as an email notification.
Metrics Polling Interval
Metrics polling interval set for the switch.
Error
Configuration or subscription errors. Mousing over an error displays a tool tip containing the error text.
At the end of each row is a down arrow, which, if you click it, provides a short cut to Configure, or Unconfigure the integration in the associated row.
Note
The seed switch cannot be unconfigured.
Select the switch or switches that you want to configure by selecting the check box associated with the switch or switches.
Click Configure, or, if you only chose one switch, you can also choose the Configure option from the drop-down menu at the end of the selected row.
If you selected one switch, the Switch Configuration dialog box displays. Proceed to Step 11.
If you selected more than one switch, the Bulk Switch Configuration dialog box displays. Proceed to Step 12..
If you select one switch, the Switch Configuration dialog box displays.
The Name, Vendor, Hostname/IP, and SNMPVersion are auto-detected. You can override the IP and SNMP Version. If auto-detect for the IP address failed, you must enter the IP address. Depending on the SNMP version detected, there might be more or less values to fill in.
The values in the other fields are filled out with default values. You can edit these fields, but it is recommended that you keep the default values provided. In some cases, such as when SNMP version 3 usernames and passwords are required, we cannot provide defaults, and you have to enter the information manually.
Note
SNMP Timeout multiplied by SNMP Max Timeouts cannot exceed half of the Polling Interval.
Note
For Core switches discovery times out, workaround is to increase the timeout value to 45 seconds and the metrics polling interval need to be set to 5 minutes, click OK and re-run the discovery.
Click OK to apply the configuration. Proceed to Step 13.
If you select two or more switches, the Bulk Switch Configuration dialog displays.
Select the properties that you want to configure and click OK.
A Switch Configuration dialog displays, with the selected properties ready to be configured. Enter the values for the selected properties and click OK to apply the configuration.
Subscribe to the switches by selecting the switch or switches to which you would like to subscribe and click Subscribe. When you click Subscribe, IO also validates that there are sufficient licenses.
Click Save to save all of your changes.
The Discovery dialog box displays, asking if you want the discovery process to start upon saving. Immediate discovery is recommended, as no metrics are collected until discovery is complete.
Click Yes to start immediate discovery.
After clicking yes, you get returned to the main grid of all software integration configurations, and the integration that you just created has "Discovering…" in its last discovery time column.
If you drill down into the integration configuration again, a banner displays on your screen saying that discovery is taking place. While the discovery is taking place you are in read-only mode. You cannot make any changes to the integration or switch configuration.
Note
If discovery completes with the error, “Illegal action: attempt to associate archived parent,” re-run discovery on the integration configuration that failed for it to unarchive the port.