8/12/2019 Sharing+of+Terminals+at+NOC+for+Console+Port+Network+Elements

1/2

8/12/2019 Sharing+of+Terminals+at+NOC+for+Console+Port+Network+Elements

2/2

Sharing of Terminals at NOC for Console Port Network Elements

White Paper

looptelecom.com 2 March 8, 2002

Shared Terminal Scheme for Console Port Network Elements

The primary reason for needing a dedicated terminal for each "RS232 type" network element is to collectalarms. Otherwise, by changing the IP address inside the terminal server, a single terminal can be shared,albeit in time-shared mode talking to one NE at a time. The proposal here is to have

1. One port of the Terminal Server will be dedicated to Alarm Collection. The PC connected to this port willbe programmed (a) to receive from multiple RS232 type network elements, (b) displaying the addressand type of NE, and (c) logging the message with a time stamp.

2. Several other ports will be time-shared for interactive session with any NE. The PCs connected to theseports is used in a time-shared mode by changing its destination IP address. In this way, a few terminalswill suffice to manage a multitude of "RS232 type" network elements.

Alarm Collection

Terminal

TS

Loop-V4200-9

TS

Loop-V4200-9

TS: Terminal Server

Network

Element

Network

Element

Network

Element

Shared Management Terminals

TS

TS

IP

NETWORK

Since each type of NE may need specific management software, each of the management PCs will have theappropriate management software as needed.

The number of network elements to be managed in this way is not unlimited. It is determined by the expectedtraffic. With a very large number of elements, then N terminal ports will be needed for alarm collection, and Mterminal ports for interactive management. For example, if 20,000 such network elements are to be managed,

then perhaps 2 terminals would be needed for alarm collection, and 10 terminals for interactive management.