Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Discovering Network Elements

    Use this procedure to discover network elements in the network you want to manage.

    1. Select the Network Element Discovery button on the toolbar or choose Tools >Network Element Discovery from the menu.

      The Network Element Discovery window is displayed, as shown below.

    2. Enter the criteria with which to discover the network elements in the Discovery Criteria field.

      Table 1: Discovery Criteria




      Group Name



      The use of the group name as part of the network element discovery criteria allows you to specify a group of network elements for discovery. The group of network elements must have been previously created. See Creating a new group.

      Note: Using the group name is not applicable when discovering network elements for the first time.

      Host Name (DNS)



      IP address

      List separated by comma or single entry,

      Address range

      All devices in a subnet

    3. Optionally, specify the Ethernet Management Domain.

      Domains are used when creating Ethernet services. For more information on domains, see Ethernet Network Domains.

      If you do not plan on creating Ethernet services, you do not need to specify a domain.

    4. Optionally, select Automatically Configure JUNOS if you want PSM to automatically configure a Juniper Networks router or switch for NETCONF and SNMP access from PSM.

      When selected, PSM configures the router or switch to accept NETCONF requests from the specified Port and sets the SNMP write community string to private.

    5. Optionally, specify the NETCONF parameters if the network element you are discovering supports NETCONF.

      You can specify the NETCONF Username, Password, and Port, or you can leave them blank to use the defaults. The defaults are set to match the defaults on the devices being managed.

    6. Optionally, specify the SNMP parameters.

      You can specify an SNMP Write Community string and a Port, or you can leave them blank to use the defaults. The default write community string is private. The default port is 161.

      Note: Because PSM uses SNMP for the initial communications with the network element, the SNMP parameters must be correct even if PSM is using NETCONF to manage the network element. Additionally, some devices require SNMP for trap server registration.

    7. Optionally, select Auto-Discovery of Connected Devices if you want PSM to automatically discover all network elements connected to the network element you are discovering.

      If you select this option, PSM will automatically discover all connected network elements in a BTI7000 Series DOL network, and all connected network elements in a BTI7800 Series ROADM network or a BTI7800 Series transport network .

    8. Optionally, select Configure Topology Discovery if you want to enable LLDP on the NE.

      If you select this option, PSM will enable LLDP on the NE after the NE is discovered. If you do not select this option, PSM will not enable LLDP on the NE after the NE is discovered. In this latter case, the LLDP setting on the NE is left unchanged.

      This setting applies to BTI7000, BTI800, and BTI700 network elements only.

    9. Click OK to start device discovery.

      The following figure shows PSM when network elements are discovered successfully.

      The Elements branch in the Network tree can be expanded to show all the components on the network element.

      If PSM is unsuccessful in discovering a network element, the font below the network element icon is red. Common reasons for failure include invalid credentials or port numbers, or if the network element cannot be reached.

      Note: The first discovery of a new network element type or version might take longer than subsequent discoveries. The reason for this is that PSM builds a database schema for each new network element type or version it encounters.

    Modified: 2017-08-09