Navigate to Administration>Device Profile to open the Device Profile window where you can:
Set up or modify the device list. Initially, the device list contains all the devices discovered from the TED. The device IP address (if not already discovered) and the PCEP IP address for each device are required. The PCEP IP address is the local address of the PCC located in the PCE statement stanza block.
Supply a hostname for each router for OSPF networks. This is necessary because the TED does not contain hostnames for OSPF networks.
Specify an MD5 key to secure PCEP communication between the NorthStar Controller and the PCC.
Specify device SNMP parameters for SNMP connectivity.
Test connectivity of devices using ping, SSH, and SNMP.
Figure 1 shows the Device Profile window.
The Device Profile window consists of the following panes:
Device List (upper pane)—Lists all the devices that are part of the profile selected in the profile names list.
Device Detail (lower pane)—Displays detailed information about the device selected in the device list.
Device List Pane
The Device List pane shows all the devices in the profile along with many of their properties. You can change the order of the devices in the list by clicking and dragging rows. Sorting, column selection, and filtering options are available when you hover over a column heading and click the down arrow that appears. Figure 2 shows these options.
You can filter the devices that are included in the display by activating a filter on any column. See Sorting and Filtering Options in the Network Information Table for a description of the column filtering functionality, along with an example.
The buttons across the top of the Device List pane perform the functions described in Table 1. Button labels are displayed when you hover over the buttons.
Table 1: Device List Button Functions
Saves the profile devices changes. The icon turns red when modifications or edits have been made to entries or fields in the device list. When the icon is red, you must click the Save icon to complete your changes.
Tests connectivity on the selected devices.
Adds a device.
Modifies the selected devices.
Deletes the selected devices.
Copies the selected devices.
Pastes the copied devices
Synchronizes profile devices with the live network.
Imports devices from a CSV file.
You can perform many of these functions on multiple devices simultaneously. To select multiple devices, Ctrl-click or Shift-click the device rows and then click the button for the function you wish to perform.
The Test Connectivity button opens the Profile Connectivity window shown in Figure 3.
In this example, multiple devices were selected for testing. Select the Use Management IP check box if the devices to be tested have management IP addresses specified for out-of-band use. Click Options to open the Test Connectivity Options window shown in Figure 4.
In the General tab, you can:
Specify which test methods you want to use (Ping, SSH, SNMP). Multiple methods are allowed (by default, all methods are tested). To select or deselect methods, click the corresponding check boxes.
Netconf connectivity is not tested.
Allow for concurrent access of a number of devices by specifying a simultaneous access limit from 1 to 16. The default is 7.
In the Login/Password tab, you can enter alternate login credentials to be used in case of login/password failure.
Click OK to submit your selections and close the Test Connectivity Options window.
In the Profile Connectivity window, click Start to begin the connectivity test. You can click Stop if the test fails to complete quickly. The test is complete when the green (pass) or red (fail) status icons are displayed as shown in Figure 5.
In SNMP connectivity testing, the host name and device type (vendor) are polled and are auto-populated in the test results if the information was previously missing or incorrect in the device profile. A red triangle in the upper left corner of a field in the test results indicates that a change was automatically made. You can see an example in the Type column in Figure 5. To propagate those changes to the device profile, click Profile Fix at the bottom of the Connectivity Test Results window.
To display the detailed test results for an individual device in the lower part of the window, click the device row in the upper portion of the window, even if you only tested connectivity for a single device.
The Start button remains unavailable after test completion until you close the window and reopen it to begin a new connectivity test.
The Add button opens the Add New Device window shown in Figure 6.
Table 2 describes the data entry fields under the Access Parameters tab.
Table 2: Add New Device Access Field Descriptions
Autofill device from the selected profile entry
Select a device on which to model the new device using the drop-down menu. The properties of the selected device populate the new device window. You can modify the imported fields.
Name of the network device, which should be identical to the hostname. During configuration collection, the software uses this name as part of the name of the collected configuration file. The configuration filename uses the format ip.name.cfg. If the device name is left blank, the configuration filename uses the format ip.cfg.
Required field: IP address of the network device.
Management IP address for the device. NorthStar Controller first attempts connection using the management IP address if it is specified, and then the IP address.
Note: The management IP address is required for out-of-band management access.
Select the device vendor from the drop-down menu. The default is GENERIC. The vendor is displayed in the Device List under the column heading Type.
Model number of the device.
Type of operating system installed on the device.
Version number of the operating system build installed on the network device. The default value is > 14.2x.
Note: For routers configured with PCEP using Junos OS Release 14.2x and earlier, select <= 14.2x for this parameter.
Number of milliseconds after which a connection attempt times out. The default is 300. To enter a different value, type the number of milliseconds in the field or use the up and down arrows to increment or decrement the displayed value.
Number of times a connection to the device is attempted. The default is 3. To enter a different value, type the number of retries in the field.
Command to use for SSH connection. The default is ssh. To enter a different value, type the command in the field. Include the full path of the command and options used for ssh, such as /usr/bin/ssh -1 -p 8888.
Select this checkbox to enable Netconf communication to the device.
Enter the number of times a Netconf connection is to be attempted. The default is three.
Note: A value of 0 means an unlimited number of retries - connection attempts never stop.
The local address of the PCC located in the PCE statement stanza block.
Note: We highly recommend that this field be populated.
PCEP MD5 String
Message Digest 5 Algorithm (MD5) key string, also configured on the router. Configuring MD5 provides information on configuring MD5 authentication.
Note: All the routers in the network must have their PCEP IP addresses in the profile. This is especially important if any router in the network is configured with an MD5 authentication key.
Login ID for the network device.
Password for the network device.
Login ID for situations that require a higher-security login.
Password for situations that require a higher-security login.
The fields on the SNMP Parameters tab are required to set up for SNMP collection. The SNMP parameters are described in Table 3.
Table 3: SNMP Parameters
Use the drop-down menu to select SNMPv1, SNMPv2c, or SNMPv3. The default is SNMPv2c.
SNMP port. The default is 161. Must match the port configured on the router.
SNMP get community string as configured on the router.
SNMP set community string. This parameter is reserved for future use.
Number of seconds after which connection attempts will stop. The default is 3.
Number of times connection will be attempted. The default is 3.
Click Submit to complete the device addition. The new device appears in the device list.
The Modify button opens the Modify Device window, which has the same fields as the Add New Device window. Edit the fields you want to change and click Submit. Click the Save button (disk icon) to complete the modification. You can wait until you have completed all your device modifications to click the Save button, which will have turned red to indicate there are unsaved changes.
To modify one or more fields in the same way for multiple devices, Ctrl-click or Shift-click to select the devices in the device list and click the Modify (pencil) button. On the resulting Modify Device(s) window, you can make changes that affect all the selected devices.
As an alternative to opening the Modify Device window, you can change some of the device properties directly in the Device List pane by double-clicking the fields.
To delete a device, select the device row in the Device List and click the Delete button. A confirmation window is displayed as shown in Figure 7.
Click Yes to complete the deletion.
If you delete a device from the liveNetwork profile, you are not deleting it from the live network itself. You can restore the device to the profile using the Sync with Live Network button.
Copy and Paste Device
Use the Copy and Paste buttons to copy devices and paste them into the device list. You can then use the Modify Device function to edit the properties of the copy as appropriate.
To copy a device, select the device row and click the Copy button. Click the Paste button to add the copy to the device list. Select the added row and click the Modify button to modify the copy. You can copy and paste multiple rows at once.
Sync with Live Network
To synchronize profile devices with the live network, click the Sync with Live Network button. This function does not delete devices from the selected profile that do not exist in the live network, but it does add devices that are missing from the live network, and it synchronizes all devices with a corresponding live network device.
The Import button opens the Import Devices from CSV window shown in Figure 8. This function is particularly useful when there are a large number of devices to add.
Click Browse to specify the CSV file that contains the devices to be added, and indicate the appropriate delimiter by selecting the corresponding radio button. A preview of the data appears in the Data Preview box.
Click Import to complete the import. The imported devices appear in the device list.
Device Detail Pane
The Device Detail pane displays the properties of the device that is highlighted in the Device List pane. There are two ways to minimize this pane:
Click the down arrow at the top center of the pane. Click the up arrow to maximize the pane.
Click the down arrow in the top right corner of the pane. Click the up arrow to maximize the pane.
Click and drag the top margin of the pane to resize the pane.
MD5 can be used to secure PCEP sessions as described in RFC 5440, Path Computation Element (PCE) Communication Protocol (PCEP). MD5 authentication must be configured on both the NorthStar Controller (in the Device Profile window) and on the router (using the Junos OS CLI). The authentication key must be the same in both configurations. The device profile acts as a “white list” when MD5 is configured. The NorthStar Controller does not report LSPs or provision LSPs for the routers not included in the device profile.
The first time MD5 is enabled on the router, all PCEP sessions to routers are reset to apply MD5 at the system level. Whenever the MD5 enabled status on a router or the MD5 key changes, that router resets the PCEP connection to the NorthStar Controller.
In the NorthStar Controller Device Profile window, perform the following steps to configure MD5 for the PCEP session to a router.
- Select a router in the Device List pane.
- Click to open the Modify Device(s) window.
- In the MD5 String field, enter the MD5 key string. Click Modify.
- Click to save your changes.
The PCEP MD5 Configured field for the router changes from no to yes.
All the routers in the network must have their PCEP IP addresses in the profile. When you save your changes, you might receive a warning, reminding you of this.
In the Junos OS CLI on the router, perform the following step to configure MD5 for the PCEP session to the NorthStar Controller.
- Use the set authentication-key command at the [edit protocols pcep pce] hierarchy level to configure the MD5 authentication key.user@pcc# set protocols pcep pce pce-id authentication-key md5-key