Specifications

Reference Guide
2-33
Applications Management Channel Concentrator (MCC) Server
interfaces are used, each interface has a local IP address. 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 configurable port parameters are permanently stored in
NV-RAM and downloaded to the card during startup. An interface card remains in standby
position until correctly configured and activated. Statistics are also available on both interface
cards.
IP-based management information from clients is typically provided to the MCC by a Digital
Access and Cross-connect System (DACS) as Bit Seven Redundant (B7R) or Bit Four
Redundant (B4R) DS0 channels on a T1 or E1 link. The MCC routes IP packets among the
131 available WAN interfaces, the local host CPU and Ethernet. Each interface represents a
separate network or subnet as specified by the IP address and Netmask combination. Three of
the 131 are high-speed interfaces that can either be configured as Nx64 kbps (N=1 to 24 for
T1 or 1 to 31 for E1). Those interfaces can independently be configured for the Frame Relay
protocol or for transparent HDLC. The 128 lower-speed WAN interfaces can be configured in
groups of 64, to either be in BnR mode or plain 64 kbps. HDLC mode.
Figure 2-21shows FDL channels from the remote IAD a, b, c, and d fed into a DACS II for
translation into multiple B7R encoded DS0 channels. IAD I, connected to the DACS II, routes
IP datagrams to IAD II through the alternative high-speed interfaces. IAD II in turn routes
datagrams to the Local Ethernet to the NMS.