Hitachi

JP1 Version 12 JP1/Network Node Manager i Setup Guide


26.2.1 Configuring SNMP access

To collect individual information related to the configuration and connectivity of managed nodes, NNMi discovery needs SNMP access to those nodes. SNMP is used also during status monitoring in order to access the operating states of nodes and the objects contained in them.

Note

NNM tries the community strings one by one in the order they are listed in the configuration of the matching area, and uses the first community string verified to be available. In contrast, NNMi tries all configured community strings in parallel, and uses the first community string verified to be available. If multiple values are available, configure the most suitable community string.

[Figure]

The NNM management station has the configuration information needed by SNMP to access the devices in the environment being used.

  1. To export the NNM SNMP configuration, perform either of the following operations:

    • Open the user interface, choose Options, Configure SNMP, and then click Export. For the target file name, specify snmpout.txt.

    • Run the following command:

      xnmsnmpconf -export > snmpout.txt

    Example of NNM SNMP information

    An output example follows:

    10.2.126.75:public:*::::::

    mytest57.mycorp.net:public:*::::::

    127.0.0.1:public:*::::::

    10.97.233.209:mycommstr:*::::::

    mpls2950.mycorp.net:mycommstr:*::::::

    mplsce04.mycorp.net:mycommstr:*::::::

    *.*.*.*:mycommstr:*:8:2:900:::

    The target file has the following fields separated by a colon (:):

    target:community:proxy#1:timeout#2:retries:poll interval#3:port:set-community:

    #1: An asterisk (*) indicates that the item is not a proxy.

    #2: Expressed in 1/10 seconds.

    #3: Expressed in seconds.

    To see the detailed information for a value, use the following command (do not use it for import, however):

    xnmsnmpconf -export -verbose

    For details about the ovsnmp.conf file format, see the ovsnmp.conf Reference Page.

  2. Check the configured community string in the following file:

    • Windows: %OV_CONF%\netmon.cmstr

    • Linux: $OV_CONF/netmon.cmstr

[Figure]

Select methods for entering community strings in NNMi. Use these methods starting with the unique communication string list in the snmpout.txt file created in step 1 under Collect from NNM.

Note

You cannot migrate the settings in the SNMP Proximity System and Configuration Community Name configuration areas.

Organization of this subsection

(1) Simple method

The simplest method is to enter all NNM community strings so that NNMi can resolve the SNMP community strings used by individual devices. Community string discovery is enabled by default. This function enables quick migration.

  1. Inform the network operating center (NOC) to expect authentication errors during the initial discovery by NNMi.

    NOC personnel can ignore these authentication errors during this period.

  2. Perform one of the following operations:

    • Modify snmpout.txt to match the format used by NNMi. Next, use NNMi to load these values.

    • Using the snmpout.txt file as a sample, manually build an NNMi input file. Next, use NNMi to load these values.

    • Enter the values into the NNMi console according to the following procedure:

      a. Examine the unique community string value list in the snmpout.txt file:

      - Windows: Open the snmpout.txt file using Excel. First select data rows and then sort them by column B.

      In this example, the following two unique community strings are considered:

      public

      mycommstr

      - Linux: Run the following command:

      cut -f 2 -d ':' < snmpout.txt | sort -u

      b. In the NNMi console, from the Configuration workspace, choose Communication Configuration. Enter all unique values in the Default SNMPv1/v2 Community Strings tab.

      c. Set up the timeout, retry count, and ports.

      [Figure]

(2) Modified simple method

Group the community strings for each IP area to be used. Enter the values in each area in the NNMi console so that NNMi determines the SNMP community string to be used for each device. There will be fewer authentication failures than the aforementioned simple method.

  1. Check the unique values list in the snmpout.txt file for each IP used by NNM.

  2. In the NNMi console, from the Configuration workspace, choose Communication Configuration.

    After creating IP areas, enter community strings in each area.

  3. Set up the timeout value, retry count, and ports.

(3) Automated method

After converting the snmpout.txt file into the format needed by the nnmcommload.ovpl command, load the individual community string being used by each device.

  1. To make the snmpout.txt file conform for use by NNMi tools, perform either of the following operations:

    • Use an editor to create a file that is appropriate to NNMi. The result follows:

      10.2.126.75,public

      mytest57.mycorp.net,public

      127.0.0.1,public

      10.97.233.209,mycommstr

      mpls2950.mycorp.net,mycommstr

      mplsce04.mycorp.net,mycommstr

    • Run the following command (applicable in Linux only):

      awk 'BEGIN {FS = ":" };{printf"%s,%s\n",$1,$2 }' \ <snmpout.txt> mysnmp.txt

      This command is valid only for configuring the individual nodes in the file. Manually delete the range and wildcard settings.

  2. Run the following command:

    nnmcommload.ovpl -u username -p password -file mysnmp.txt

  3. In the NNMi console, configure the default community string and a community string for the IP range.

  4. In the NNMi console, set up the timeout value, retry count, and ports.

(4) Method using NNMi

In the NNMi console, from the Configuration workspace, choose Communication Configuration.

Replicate the configured values of the snmpout.txt file.

[Figure]

Using the following information, enhance NNMi's communication access configuration:

  • Host name wildcard (if it is more suitable to the environment than an IP range)

  • Global default, IP range, and ICMP timeout and retry count for certain nodes

  • Enabling or disabling SNMP or ICMP access to a specific area in the network

  • Management addresses given higher priority for certain nodes

    Note

    NNM selects the smallest loopback address when selecting a management address. NNMi also selects the smallest loopback address.