In this section:
The two MCH cards in slots 1 and 14 provide redundant Ethernet switching operating in ACTIVE/ACTIVE mode, with each MCH managing disjoint subnets.
The MCH cards provide the following functionality:
MCH platform management function
MCH IP functions in ACTIVE/ACTIVE mode. Switches on both MCH cards function at full speed independently from one another. If a switch fails, all IP paths through that switch are unavailable. Application-level provisioning must take this into account in order to avoid single-failure situations.
For example, an Adjacent Diameter Node (ADN) configured using TCP has only one IP path. Should the switch hosting that path fail, the ADN remains out of service until the switch is restored. Configuring the same ADN using SCTP with two endpoints -- one endpoint for each of the two locally provisioned Data IP addresses -- remains active in a single-switch failure situation.
MCH platform management functions in ACTIVE/BACKUP mode. The MCH platform management function communicates between the two cards using the external 10/100Base-T ports on the RMC670 μRTM (refer to RMC670 µRTM Interface Connectors). In the event the platform management active MCH fails, the alternate MCH acquires active status with no other effect on system processes.
The
DSC 8000 VLAN Networks
Network | Function | Description |
---|---|---|
VLAN1 | Internal backplane connectivity | VLAN1 is configured so the system cards can communicate internally without the traffic leaving the system. |
VLAN2 | Routing IP traffic | VLAN2 carries Routing IP Network traffic. |
VLAN3 | Management traffic | VLAN3 carries Management messages. |
VLAN4 | Routing IP traffic | VLAN4 carries Routing IP Network traffic. |
VLAN5 | Management traffic | VLAN5 carries management messages. |
VLAN6 | IMF | VLAN6 carries IMF messages between the DSC 8000 and an external monitoring application. |
VLAN7 | IMF | VLAN7 carries IMF messages between the DSC 8000 and an external monitoring application. |
Custom | Custom | User-defined VLAN. |
Custom VLANs are permitted on the DSC 8000 platform. Refer to the Platform Manager Guide for details on how to configure custom VLANs.
The
The internal IP interfaces are restricted to VLAN1 and support the following two (2) hard-coded System Area Network (SAN) subnets:
The internal network is private, and the IP interfaces are inaccessible to systems outside of the
The external IP interfaces (p19p1.3, p19p2.5, p19p1.2, p19p2.4, and may include p19p1.6, p19p2.7 if the system is configured for IMF) are allocated to the two (2) required Management and the two (2) required default Routing CPUs. If the system is equipped with additional Routing CPUs, then additional external IP interfaces are supported for each of these CPUs (p19p1.2, p19p2.4, and may include p19p1.6, p19p2.7 if the system is configured for IMF).
The shared IP interfaces on the two (2) Management CPUs are as follows.
The Management CPU card that boots first takes control of the shared IP interface. The unique IP interface periodically pings the gateways that were entered when you configured the management IP interface to confirm connectivity. If this Management CPU is removed from the chassis for any reason, the remaining Management CPU takes over. Users connected to the Web UI may be asked to log onto the system again to resume their activities.
If one of the MCH cards (AMC671) is extracted, the switchover of management traffic to the other MCH card is seamless and there is no time delay.
It is recommended that between 100 Mbps to 1 Gbps bandwidth is reserved for
Each Ethernet interface on any AMC124 CPU card and the corresponding remote node must be configured on a separate subnetwork (that is, subnet) through different gateways; hence, ensuring that IP traffic on these subnets remains segregated.
The following figure shows the logical representation of the
DSC 8000 Ethernet Port Mapping
The following table provides a listing of the internal and external IP interface configuration.
Do not change the Ethernet configuration shown in the following table, Ethernet Port Mapping (Control Shelf). Otherwise, the system may not perform as expected. If this configuration conflicts with the existing network configuration on your system, contact Customer Support.
The Ethernet configuration is the same for the Expansion shelves with the exception that these shelves are not equipped with the Routing and Management CPUs that are required for the Control shelf.
DSC 8000 Ethernet Port Mapping (Control Shelf)
Ethernet redundancy is already built into the
For failover scenarios, the
Only one of the two ports is active at all times, provided that at least one of the associated Ethernet interfaces (p19p1.2 or p19p2.4) has connectivity to the remote end.
Sections AMC671 MCH Interface Connectors and RMC670 µRTM Interface Connectors show the physical connections to the AMC671 and RMC670 (µRTM).
The cabling connections for communication between the DSC 8000 shelves on the MCH cards is made using the 10Gbps FP1 and FP2 ports. For specifications on these cables, refer to Installing Communication Cables.
DSC 8000 Inter-shelf Connections