Prerequisite tasks

Plan your NFM-P deployment for managing devices by determining the following:

• the number of NEs the NFM-P is to manage, the redundancy requirements and the hardware required for the system

• the management network latency and management network bandwidth requirements

• the naming conventions for objects that you create

See the NSP Planning Guide for the full list of deployment considerations.

Integrate the NFM-P with other EMS, as required.

Review the NSP NFM-P Network Element Compatibility Guide for release-specific information about the compatibility of managed device features in NFM-P releases. Install the physical device as per the appropriate device-specific hardware user documentation.

Review GUI basics for managing devices

Familiarize yourself with GUI operations for configuring and managing devices such as the following:

• navigating the GUI, performing searches, and customizing the GUI user preferences; see Chapter 1, NFM-P GUI .

• creating custom workspaces to simplify navigation and operation; see Chapter 2, NFM-P custom workspaces .

• managing devices using the equipment navigation tree; see Chapter 3, NFM-P navigation tree .

• managing equipment using topology maps; see Chapter 4, Topology map management .

• creating schedules to allow for the automatic execution of tasks at designated times; see Chapter 5, NFM-P-based schedules .

Launch the on-product user documentation to access the NFM-P customer documentation and search tools.

Perform account and security tasks

Set up all required NFM-P user accounts and user groups with the required scope of command roles, span of control permissions, and the ongoing monitoring and management of those accounts. See the section on NFM-P user security in the NSP System Administrator Guide for more information.

Perform the required NFM-P and UNIX security management tasks for accessing and securing the managed device. See the sections on NE user and device security and TCP enhanced authentication in the NSP System Administrator Guide for more information.

Prepare network devices for NFM-P management

Commission Nokia devices for NFM-P management and ensure all non-Nokia devices have a GNE profile. Configure how and when the NFM-P polls the devices for MIB changes; see Chapter 8, Device commissioning and management .

Create a mediation security policy and discovery rule to define the criteria required to add devices to the managed network, and optionally configure SSH2 security for CLI sessions; see Chapter 9, Device discovery .

Use a Telnet or SSH CLI from the NFM-P for device access; see Chapter 10, Device CLI sessions .

Customize the global system settings, as required. See the section on NFM-P component configuration in the NSP System Administrator Guide.

Configure and manage the discovered device

Configure and manage equipment navigation tree objects including:

• general network objects; see Chapter 11, Working with network objects

• device objects; see Chapter 12, Device object configuration

• logical group objects; see Chapter 13, Logical group object configuration

• ESA objects; see Chapter 14, ESA object configuration

• shelf, card, and daughter card objects; see Chapter 15, Shelf and card object configuration

• port and channel objects; see Chapter 16, Port and channel object configuration

Perform additional device management functions, as required such as the following:

• equipment inventories of managed devices; see Chapter 17, Inventory management

• card migrations; see Chapter 18, Card migration

• configure threshold-crossing alarms; see Chapter 19, TCA

• bulk configuration changes; see Chapter 20, Bulk operations

Manage the network functions

Configure NE routing and forwarding on NEs; see Chapter 27, NE routing and forwarding . As required, configure specific routing and forwarding functions and services such as:

• NE protocols; see Chapter 28, Routing protocol configuration

• OpenFlow; see Chapter 29, OpenFlow

• IS-NAT groups; see Chapter 30, NAT

• MPLS and LSPs; see Chapter 31, MPLS

• MPLS-TP; see Chapter 32, MPLS-TP

• service tunnels to carry service traffic; see Chapter 33, Service tunnels

• IPsec sessions; see Chapter 34, IPsec

• ISA-Video groups and members, see Chapter 35, ISA-Video

Configure network redundancy, protection, and offloading as required to ensure network availability in case of a network device or path failure using functions such as:

• VRRP; see Chapter 37, VRRP

• APS; see Chapter 38, APS

• Wi-Fi offloading; see Chapter 39, lightRadio Wi-Fi

• MC peer groups; see Chapter 40, MC peer groups

• MC IPsec; see Chapter 41, MC IPsec

• MC endpoint groups; see Chapter 42, MC endpoint groups

• MC LAG groups; see Chapter 43, MC LAG groups

• MC synchronization groups; see Chapter 44, MC synchronization groups

• MC ring groups; see Chapter 45, MC ring groups

Create policies to manage devices

Depending on your service delivery model, create, distribute, and assign the appropriate service or routing policies that define the conditions for managing network devices using the NFM-P; see Chapter 49, Policies overview for general information about policy management. See Chapter 50, QoS policies to Chapter 68, 7705 SAR Security policies for specific policy information and the associated workflows to configure the policy.

Create services over devices

Familiarize yourself with service management and QoS concepts prior to configuring services over the devices; see Chapter 70, Service management and QoS . Configure the following adjunct service delivery methods to support the creation of network services as required:

• shared queue groups to allow SAP or IP interface forwarding classes to be redirected; see Chapter 71, Queue groups .

• virtual ports to support clustering and enforce the aggregate rate of each destination BSAN; see Chapter 72, Virtual ports .

• create and manage customers and the services they subscribe to; see Chapter 73, Customer configuration and service management .

• tunnel administrative groups to enable services to use a PW template; see Chapter 88, Tunnel administrative groups .

Configure the following network services as required:

• services for residential subscribers; see Chapter 74, Residential subscriber management .

• VLAN services; see Chapter 75, VLAN service management .

• VLL services; see Chapter 76, VLL service management .

• VPLS; see Chapter 77, VPLS management .

• IES; see Chapter 78, IES management .

• VPRN services; see Chapter 79, VPRN service management .

• SPB services; see Chapter 80, SPB service management .

• PW routing and dynamic MS-PW services; see Chapter 81, PW routing and dynamic MS-PW service management and Chapter 83, Service PW template policies .

• Composite services; see Chapter 85, Composite service management .

• Dynamic services; see Chapter 86, Dynamic service management .

Monitor, maintain, and troubleshoot devices

Configure alarm policies, and monitor incoming alarms to check the type and characteristics of the alarms, and to resolve the network problems or physical equipment failures identified by the alarms; see Chapter 36, Alarm management .

Perform the following service assurance functions as required, to ensure that services offered over network devices meet the pre-defined service quality level expected by customers:

• use the NFM-P Service Test Manager to group OAM diagnostic tests into suites of manual and automatically-generated tests; see Chapter 89, Service Test Manager .

• use OAM diagnostic tools to troubleshoot network problems and for SLA verification; see Chapter 90, OAM diagnostic tests .

• configure Ethernet CFM to detect, isolate, and report connectivity faults in Ethernet networks; see Chapter 91, Ethernet CFM .

• create mirror services to troubleshoot customer traffic issues or for use with Lawful Intercept; see Chapter 93, Mirror services and Chapter 94, Lawful Intercept .

• test and report network delay and loss using CFM messaging in Layer 2 networks; see Chapter 92, Performance Monitoring tests .

• perform on-demand verifications of the configuration of services and physical links using an RCA audit; see Chapter 95, RCA audit .

• create a copy of the SAP configuration of an end-user service to emulate the bandwidth, throughput, and QoS requirements of a service; see Chapter 96, Service throughput configuration .

• configure Application Assurance to provide deep-packet inspection and NSP subscriber traffic management; see Chapter 87, Application assurance .

Collect NFM-P and NE statistics to monitor network and service performance, compile equipment usage and billing data, and ensure SLA compliance; see the NSP NFM-P Statistics Management Guide.

Perform device maintenance functions, as required, for example:

• configuration backups and restores; see Chapter 23, NE backup and restore

• checkpoint file creation and configuration rollbacks; see Chapter 24, NE configuration rollback

• deployment management; see Chapter 25, NE deployment

• software upgrades; see Chapter 26, NE software upgrades

Identify and resolve performance issues in an NFM-P-managed network or on an NFM-P system as required.