To commission a device for NFM-P management

Commissioning tasks not covered in this procedure
Table 8-1: Location of device commissioning information

Device

Information location

Devices for model-driven management

NSP System Administrator Guide

CAUTION 

CAUTION

Service Disruption

Do not apply an SNMP log filter to the NFM-P SNMP log. The NFM-P cannot manage an NE that has an SNMP log filter applied to the log used by the NFM-P, which is typically log ID 98. In rare cases, Nokia may apply filters.

Steps
 
1 

Open a console window on the device.

2 

Enter the following command to configure the system address:

configure router interface system address nnn.nnn.nnn.nnn/mask ↵

where nnn.nnn.nnn.nnn is the system IP address

mask is the subnet mask

3 

Enter the following command to enable Telnet:

configure system security telnet-server ↵

4 

Enter the following command to enable FTP:

configure system security ftp-server ↵

5 

If required, enter the following command to enable SSH2:

configure system security ssh version 2 ↵

6 

Enter the following command to enable console, FTP, and SNMP access for the appropriate user account on the device:

configure system security user user_account access console ftp snmp ↵

where user_account is the appropriate user account for Telnet, FTP, and SNMP access, for example, admin

7 

If required, enter one of the following commands to enable hash encryption for passwords and authentication keys during device configuration save or list operations:

  1. For 7x50 devices, Release 16.0 R3 and earlier, enter the following:

    configure system security hash-control read-version read-version write-version write-version ↵

    where

    read-version is the version of encryption accepted during read operations, for example, 1, 2, or all to indicate that both are accepted

    write-version is the version of encryption used during write operations, for example, 1 or 2

    Version 1 encryption uses a simple key algorithm that generates the same character string each time it hashes a specific password or authentication key.

    Version 2 encryption uses a more complex key algorithm that generates a different character string each time it hashes a specific password or authentication key.

  2. For 7x50 devices, Release 16.0 R4 and later, enter one of the following:

    configure system security management-interface classic-cli read-algorithm read-algorithm ↵

    configure system security management-interface classic-cli write-algorithm write-algorithm ↵

    configure system security management-interface md-cli hash-algorithm hash-algorithm ↵

    configure system security management-interface netconf hash-algorithm hash-algorithm ↵

    configure system security management-interface grpc hash-algorithm hash-algorithm ↵

    where

    read-algorithm is the version of encryption accepted during read operations. Nokia recommends using hash2.

    write-algorithm/hash-algorithm is the version of encryption accepted during write operations. Nokia recommends using hash2.

8 

Enter the following commands in sequence to set the time zone and time:

configure system time zone time_zone -offset_from_UCT ↵

admin set-time YYYY/MM/DD hh:mm:ss ↵

where

time_zone is the appropriate time zone, for example, EST

offset_from_UCT is the offset, in hours, from Universal Co-ordinated Time, also known as Greenwich Mean Time, for example, if you specify EST, offset_from_UCT is -5, as EST lags UCT by five hours

YYYY/MM/DD hh:mm:ss is the current local time

9 

If required, perform one of the following to enable a time protocol.

  1. Enter the following command to enable NTP:

    configure system time ntp server-address server_IP_address ↵

    where

    server_IP_address is the IP address of the NTP server

  2. Enter the following command to enable SNTP:

    configure system time sntp server-address server_IP_address ↵

    where

    server_IP_address is the IP address of the SNTP server

10 

Enter the following in sequence to enable the SNMPv2 engine and to configure an SNMP community:

configure system snmp no shutdown ↵

configure system snmp packet-size 9216 ↵

configure system security snmp community community_name rwa version both ↵

where community_name is the SNMPv2 community name

Caution: When configuring a mediation policy, you need use a community string that uses rwa in order for the trap destination is set on the NE. This ensures fault conditions and alarms are reported.

Note: The command is used for the NFM-P write mediation policy. If you are using SNMPv2, you must use this mediation policy for read as well, or create another mediation policy that is also configured for rwa.

The SNMPv2 community string name rwa attributes must be enabled for the NFM-P to properly manage a device, even if the NFM-P is only used to monitor a network.

11 

Enter the following commands in sequence to ensure that the device uses persistent SNMP indexes:

bof persist on ↵

bof save ↵

12 

Enter the following command to save the configuration changes:

admin save ↵

13 

If the device has redundant CPMs, enter the following command to synchronize the CPMs:

admin redundancy synchronize boot-env ↵

14 

Enter the following command to reboot the device:

admin reboot now ↵

The device initializes with SNMP communication enabled.

15 

Enter the following to clear the log ID and trap group ID:

configure log ↵

log-id 98 ↵

shutdown ↵

exit ↵

no log-id 98 ↵

no snmp-trap-group 98 ↵

exit all ↵

16 

Use an NFM-P client to discover the device and to verify that the device configuration allows management of the device. See Chapter 9, Device discovery for information about device discovery.

End of steps