Skip to main content

Configuring a Brocade SAN Integration for BNA SMI-S Discovery


Before configuring an instance of a Brocade SAN Integration where BNA (SMI-S) discovery will be used, it is recommended that the heap size be adjusted from the default 1GB to one of the settings indicated in the table below. Open the file $INSTALLDIR/conf/cimomsvc.conf, locate the line that contains set.MAX_HEAP_SIZE and change it to set.MAX_HEAP_SIZE=N, where N equals the heap setting shown below, which is based on the number of Brocade SAN Integration ports to be configured.

# of Brocade SAN Ports to be Configured

BNA Heap Setting

1 - 1,000




> 2,560


Before configuring an instance of a Brocade SAN Integration where BNA (SMI-S) discovery will be used, make sure that BNA has completed its discovery.

If you are using Brocade Network Advisor (BNA) network management tool for discovery, you need to configure SMI-S.

  1. From the Settings screen, click Integrations in the Probes and Integrations section.

    The Integrations screen is displayed.

  2. Click View for the integration.

    The Brocade SAN screen is displayed.

  3. Click New.

    The New Brocade SAN screen is displayed.

  4. Enter a name for the integration discovery instance.

    A name is required. The Name field can be edited after the configuration is saved.

  5. Select the Brocade Network Advisor (BNA) Discovery Mode.

  6. Complete the rest of the information on the New Brocade SAN screen as follows:



    Hostname / IP Address

    Hostname or IP address of the SMI-S provider.

    Use SSL

    Enables or disables use of SSL for login.


    Port of the SMI-S provider. If the SSL check box is selected, the port is 5989. If the SSL check box is not selected, it is port 5988.


    Username of the SMI-S provider, for example, the username for the Brocade BNA.


    Password of the SMI-S provider, for example, the password for the Brocade BNA.

  7. Click Test Connection to verify the connection.

    IPM tests the connection (hostname and credentials) and tries to find all the switches. This process can take up to five minutes.

  8. Click Next.

    Discovery begins for all the switches accessible. This process can take several minutes, depending on the number of switches to be discovered.

    The New Integration page opens to display the Configuration tab.

    The Namespace field is auto-detected.The Vendor,Hostname/IP, Port, Username,Password, and Use SSL fields are carried over from the previous screen. The Name field is user-configurable.

  9. Enable or disable scheduled discovery.

    By default, regularly scheduled discovery is enabled for Brocade SAN Integration configurations. If you would like to disable regularly scheduled discovery, uncheck the Enable scheduled discovery check box. If you would like to have discovery scheduled regularly, keep the box checked and choose a discovery frequency and time of day. By default, the frequency and time of day for Brocade SAN Integration is every other day and 2am appliance time.

  10. Click Save.

  11. Click on the SNMP Sources tab on the New Integration page.

    A list of available auto-detected SNMP switch sources displays.

  12. Select the switches you want to use with the integration and click Add.

    You can configure multiple switches at one time. The columns headings in the Switches table are defined as follows:

    Table 33. Switches Table Fields



    Switch Name

    Auto-detected name of the switch.

    Port Count

    Active port count.


    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 an Integration fails to collect metrics for two hours. The notification takes the form of a IPM Health Notification as well as an email notification.

    Metrics Polling Interval

    Metrics polling interval set for the switch.


    Configuration or subscription errors. Mousing over an error displays a tooltip containing the error text.

  13. With the switches still selected, click Configure.

    If you selected one switch, the Switch Configuration dialog box displays. Proceed to Step 14.

    If you selected more than one switch, the Bulk Switch Configuration dialog box displays. Proceed to Step15.

  14. If you select one switch, enter the values in the Switch Configuration dialog.

    The Name, Vendor, IP, 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.

    Proceed to Step16.

  15. If you select two or more switches, select the properties to configure in the Bulk Switch Configuration dialog.

  16. Click OK.

  17. With the switches still selected, click Subscribe.

    When you click Subscribe, IPM validates that there are sufficient licenses.

  18. 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.

  19. Click Yes to start immediate discovery.

    After clicking yes, you are returned to the main grid of all configurations, and the integration that you just created has "Discovering…" in its last discovery time column.

    If you drill down into the 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.


    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.