Zhone Technologies IMACS Network Device - Manual (Page 83)

Zhone Technologies, Inc. IMACS Product Book, Version 4
March 2001 Page 79
DPNSS Trunk Routing
Digital Private Network Signaling System #1 (DPNSS) is the predominant Common Channel Signaling scheme
used in the United Kingdom for private inter PABX communications. DPNSS Trunk Routing provides low delay
for multi DPNSS channel provisioning off a single E1 DPNSS aggregate. This is achieved by mapping the B
channels to dedicated time slots rather than to hunt groups, which in turn provides efficient D channel grooming and
subsequent billing.
3. Management Channel Concentrator (MCC) Server
The Management Communications Concentrator (MCC) provides management connectivity to remote IMACS
systems. It can concentrate the TCP/IP management traffic from up to 131 remote IMACS networks onto either a
single, local 10 BASE-T Ethernet port, or encapsulate the information as per RFC1490 on to a Frame Relay link.
There can be up to 3 MCC server cards in an IMACS chassis in non-redundant operation. The following hardware
and firmware must be included in an IMACS to add MCC Server operation:
•
880360- CPU Control Card with 8 T1/E1 Cross Connect (redundant-capable)
•
892260/892360/892460 - 8 T1/E1 Interface card w/ 128K NVRAM.
•
881360 - Advanced Communication Server (ACS) with 131 logical ports
•
60511 - Host Firmware version 5.0.x
•
63110 - MCC Server firmware
The following protocols are supported by the MCC:
•
Ethernet Media Access Control Protocol (MAC)
•
Address Resolution Protocol (ARP) (RFC 1122)
•
Internet Protocol, version 4. (IP) (RFC 791, RFC950, RFC 1122)
•
Internet Control Message Protocol (ICMP) RFC 792
•
User Datagram Protocol (UDP) RFC 768
•
Routing Information Protocol (RIP) (RFC1812)
•
Frame Relay (RFC1490)
The MCC provides routing between the bxr formatted ports and Ethernet, allowing IP management data of remote
IMACS’ to be terminated onto a local area network. The MCC can route between any of its interfaces depending on
its configuration. In addition to the B7R protocol used for T1, and B4R used for E1, a full DS0 is also provided on
all ports. B7R and full DS0 cannot be combined unless configured in groups of 64.
The MCC offers far more interfaces and functionality than the BnR, thus replacing it and the terminal server
required to bring the IP traffic to a LAN. The MCC can be configured to use unnumbered or numbered interfaces.
If unnumbered interfaces are used, MCC is accessed through the global Ethernet address regardless of what interface
is used. If numbered interfaces are used, each interface has a local IP address. When unnumbered interfaces are
selected, the IP address entered on the port is the IP address of the remote device. Similarly, when numbered
interfaces are used, the IP address entered for any given numbered port is the IP address of the local port itself.
Unnumbered interfaces help conserving IP addresses as only one address is used per interface. This addressing
method may not be compatible with HP Openview.
The MCC routes IP datagrams between all of its interfaces, based on each datagram’s IP destination address.
Datagrams are directed (or routed) to the interface carrying the sub-net to which the datagram belongs or is being
transported to, according to the content of the routing table. The routing table may be supplied with dynamic routes
from the Routing Information Protocol (RIP) when enabled. If no match is found in the routing table, a default route
can be designated to direct all unresolved datagrams to a specific interface.
Initial configuration of the MCC can made through the local VT100 port. When a working interface is established
to the CPU hosting the MCC, subsequent configurations can be done remotely via SNMP/TELNET. All