Classic management communication

Introduction

Communication among NFM-P components and external systems uses IPv4 or IPv6 exclusively, with the following exceptions:

Figure 7-4: NFM-P component communication
NFM-P component communication
Servers and managed NEs

NFM-P main and auxiliary servers communicate directly with the managed network.

The CLI of a managed NE is accessible from the client GUI using Telnet or SSH.

The NFM-P uses protocols such as FTP, SFTP, and SCP to back up NE configuration data, collect NE accounting statistics, and download software to NEs.

Main server and clients

Client interfaces provide access to an NFM-P system and the managed network through a main server.

A main server and clients communicate in the following ways:

Main server and main database

A main server communicates with a main database instance using JDBC, a Java API for interworking with SQL relational databases.

Main server and auxiliary servers

A main server sends requests to auxiliary servers. An auxiliary server notifies the main server after it finishes processing a request. If the main server fails to send a request, or all auxiliary servers are unresponsive to a request, the main server raises an alarm.

NFM-P integration with external systems

The NFM-P can be integrated with external network management systems for purposes such as alarm forwarding. Depending on the external system type, you can use a client GUI contextual menu option to open a session on the external system. See the NSP NFM-P User Guide for information.