CANOGA PERKINS 9145E NID Software Version 4.10 - Manual (Page 23)

System Configuration 9145E NID Software User’s Manual
System Configuration Menu
11
Figure 3-3 Typical Application of the Control Plane Entities
Figure 3-3 shows how these different entities are typically used by a Service Provider. The grey
cloud represents the Service Provider's network, with the NIDs placed as the demarcation points
of the service (in this example, it is a Carrier Ethernet network delivering an EVPL service to a
customer, but it could have been an IP, VPLS, or any other type of service, for that matter).
The NIDs are typically managed via IP over a management VLAN. Each Manager will be
assigned an available IP Address by the OSS administrator, and the management VLAN will be
configured in each NID. A host on the OSS can then manage each NID by TELNET, or by using
an SNMP manager application. This traffic is shown in orange in the diagram.
Let us say the Service Provider wants to monitor the latency and jitter between the UNIs (i.e.,
between the Client Port of NID A and that of the NID B in Figure 3-3). A Test IP can be setup on
each NID in this point-to-point service. The Test IP Addresses chosen must be unique on each
NID and on the same subnet. NID A can then generate test traffic (shown in green) out the
Network Port to NID B. NID B will receive this test traffic, insert timestamps where appropriate,
and send it back to NID A for final processing. In this manner, NID A can test the path and gather
precise latency and jitter measurements between the two endpoints.
In addition to monitoring the performance of the service, the Service Provider might also like to
monitor the connectivity between the NIDs and the CEs. The Service Provider and the customer
can agree on exchanging ICMP Echo Request/Reply messages across the UNI (i.e., the Service
Provider and customer agree to allow PINGs to be generated from the NID to the CE). The IP
interface on the CE may very well be on a subnet that is different from the Manager (or the Test
IP, for that matter). Therefore, the Aux IP can be configured independently with an IP Address
and VLAN that provides connectivity to the CE for ICMP messages. The Service Provider can
then generate ICMP Echo Requests to the CE, and the CE can reply back with ICMP Echo Reply
Aux IP The Aux IP entity can be user assigned to any port on the NID. The user can
configure an Aux IP Address for this entity that is not on the Manager's subnet.
In this manner, the Aux IP can be used for diagnostic purposes, by allowing the
user to PING subnets not accessible by the Manager IP. The Aux IP entity will
process any packet received with this IP Address in the packet's destination
address field. Likewise, the entity will generate IP packets with this address as
its source address field.