In this section:
The Ribbon DSC 8000 is equipped with two required Management (slot 2 and 13) and two required Routing CPUs (slot 3 and 12). Additional Routing and/or Application CPUs may be installed in the system.
DSC 8000 VLAN Networks
The DSC 8000 is designed with two Ethernet fabrics (Ethernet Fabric 1 and 2). The Ethernet fabric used for networking depends on the configuration of the VLAN interface used. For information on configuring the Ethernet Networking Base Interface attribute, see section Configuring Custom VLANs on DSC 8000.
The custom networking configurations (referred to as Custom VLANs in this document) allow you to create IEEE 802.1Q VLAN Tagged Ethernet interfaces on the Control and Expansion shelves (if any), but only on the Routing CPUs. A maximum of 12 custom VLANs are supported per Ethernet fabric. Refer to the section, Configuring Custom VLANs on DSC 8000 for more information on Custom VLANs.
Note
The VLAN count is per Ethernet fabric, which means that if you create a custom VLAN interface on multiple Routing CPUs but with the same VLAN ID, it only counts as one VLAN from the perspective of the Ethernet Fabric.
The DSC 8000 has been designed with the VLAN networks listed and described in the following table.
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 | Custom VLAN carries Routing IP Network traffic. |
Note
Custom VLANs are available on DSC 8000 Routing Cards.
DSC 8000 Ethernet Interfaces
The DSC 8000 supports internal, external, and shared IP interfaces.
The internal IP interfaces are restricted to VLAN 1 and support the following two hardcoded System Area Network (SAN) subnets:
- 192.168.240.<slot number>
- 192.168.241.<slot number>
The internal network is private and the IP interfaces are inaccessible to systems outside of the DSC 8000. All internal subnet IP interfaces are statically preconfigured on each system card, where the specific address within the subnet is determined using the slot number of the card. The external IP interfaces (p19p1.3; p19p2.5; p19p1.2; p19p2.4; Custom VLANs p19p1.n and p19p2.n; as well as p19p1.6, p19p2.7 if the system is configured for IMF) are allocated to the two required Management and the two required 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).
Note
Custom VLANs are only supported on Routing CPUs.
The shared IP interfaces on the two Management CPUs are as follows.
- Management CPU in slot 2 is p19p1.3:0
- Management CPU in slot 13 is p19p2.5:0
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.
DSC 8000 Subnetworks Configuration
Each Ethernet interface on the CPU cards and the corresponding remote node must be configured on separate subnetworks (subnets) through different gateways; hence, ensuring that IP traffic on these subnets remain segregated.
Caution
Do not change the Ethernet configuration shown in the following table. Otherwise, the system may not perform as expected. If this configuration conflicts with the existing network configuration on your system, contact Customer Support.
The following Figure shows the logical representation of the DSC 8000 Control shelf Ethernet configuration and the Table that follows provides a summary this configuration.
DSC 8000 Control Shelf Ethernet Connectivity
DSC 8000 Ethernet Configuration (Control Shelf Example)
| Slot Number | System Cards1 | Subnet | Interface | Virtual Port Number2 | Ethernet Fabric | VLAN ID |
|---|---|---|---|---|---|---|
| 2 | Management CPU (Required for Control shelf only) | MGMT | p19p1.3 | P4 | FP1 MCH in slot 1 | 3 |
| p19p1.3:0 | ||||||
| 13 | Management CPU (Required for Control shelf only) | MGMT | p19p2.5 | P4 | FP2 MCH in slot 14 | 5 |
| p19p2.5:0 | ||||||
| 33 | Routing CPU (Required for Control shelf only)
| Routing IP Network | p19p1.2 | 10 Gbps Ethernet FP3 and FP4
| 0 | 2 |
| p19p2.4 | 1 | 4 | ||||
| Custom | p19p1.n | FP3 and FP4 | 0 | 10-4094 | ||
| p19p2.n | 1 | 10-4094 | ||||
| IMF | p19p1.6 | 10 Gbps Ethernet BP2 | 0 | 6 | ||
| p19p2.7 | 1 | 7 | ||||
| 124 | Routing CPU (Required for Control shelf only) | Routing IP Network | p19p1.2 | 10 Gbps Ethernet FP3 and FP4
| 0 | 2 |
| p19p2.4 | 1 | 4 | ||||
| Custom | p19p1.n | FP3 and FP4 | 0 | 10-4094 | ||
| p19p2.n | 1 | 10-4094 | ||||
| IMF | p19p1.6 | 10 Gbps Ethernet BP2 | 0 | 6 | ||
| p19p2.7 | 1 | 7 | ||||
| 4 | Routing CPU5 (Optional) | Routing IP Network | p19p1.2 | 10 Gbps Ethernet FP3 and FP4
| 0 | 2 |
| p19p2.4 | 1 | 4 | ||||
| Custom | p19p1.n | FP3 and FP4
| 0 | 10-4094 | ||
| p19p2.n | 1 | 10-4094 | ||||
| IMF | p19p1.6 | 10 Gbps Ethernet BP2 | 0 | 6 | ||
| p19p2.7 | 1 | 7 | ||||
| 5 | Routing CPU (Optional) | Routing IP Network | p19p1.2 | 10 Gbps Ethernet FP3 and FP4
| 0 | 2 |
| p19p2.4 | 1 | 4 | ||||
| Custom | p19p1.n | FP3 and FP4 | 0 | 10-4094 | ||
| p19p2.n | 1 | 10-4094 | ||||
| IMF | p19p1.6 | 10 Gbps Ethernet BP2 | 0 | 6 | ||
| p19p2.7 | 1 | 7 | ||||
| 6 | Routing CPU (Optional) | Routing IP Network | p19p1.2 | 10 Gbps Ethernet FP3 and FP4
| 0 | 2 |
| p19p2.4 | 1 | 4 | ||||
| Custom | p19p1.n | FP3 and FP4 | 0 | 10-4094 | ||
| p19p2.n | 1 | 10-4094 | ||||
| IMF | p19p1.6 | 10 Gbps Ethernet BP2 | 0 | 6 | ||
| p19p2.7 | 1 | 7 | ||||
| 7 | Routing CPU (Optional) | Routing IP Network | p19p1.2 | 10 Gbps Ethernet FP3 and FP4
| 0 | 2 |
| p19p2.4 | 1 | 4 | ||||
| Custom | p19p1.n | FP3 and FP4 | 0 | 10-4094 | ||
| p19p2.n | 1 | 10-4094 | ||||
| IMF | p19p1.6 | 10 Gbps Ethernet BP2 | 0 | 6 | ||
| p19p2.7 | 1 | 7 | ||||
| 8 | Routing CPU (Optional) | Routing IP Network | p19p1.2 | 10 Gbps Ethernet FP3 and FP4
| 0 | 2 |
| p19p2.4 | 1 | 4 | ||||
| Custom | p19p1.n | FP3 and FP4 | 0 | 10-4094 | ||
| p19p2.n | 1 | 10-4094 | ||||
| IMF | p19p1.6 | 10 Gbps Ethernet BP2 | 0 | 6 | ||
| p19p2.7 | 1 | 7 | ||||
| 9 | Routing CPU (Optional) | Routing IP Network | p19p1.2 | 10 Gbps Ethernet FP3 and FP4
| 0 | 2 |
| p19p2.4 | 1 | 4 | ||||
| Custom | p19p1.n | FP3 and FP4 | 0 | 10-4094 | ||
| p19p2.n | 1 | 10-4094 | ||||
| IMF | p19p1.6 | 10 Gbps Ethernet BP2 | 0 | 6 | ||
| p19p2.7 | 1 | 7 | ||||
| 10 | Routing CPU (Optional) | Routing IP Network | p19p1.2 | 10 Gbps Ethernet FP3 and FP4
| 0 | 2 |
| p19p2.4 | 1 | 4 | ||||
| Custom | p19p1.n | FP3 and FP4 | 0 | 10-4094 | ||
| p19p2.n | 1 | 10-4094 | ||||
| IMF | p19p1.6 | 10 Gbps Ethernet BP2 | 0 | 6 | ||
| p19p2.7 | 1 | 7 | ||||
| 11 | Routing CPU (Optional) | Routing IP Network | p19p1.2 | 10 Gbps Ethernet FP3 and FP4
| 0 | 2 |
| p19p2.4 | 1 | 4 | ||||
| Custom | p19p1.n | FP3 and FP4 | 0 | 10-4094 | ||
| p19p2.n | 1 | 10-4094 | ||||
| IMF | p19p1.6 | 10 Gbps Ethernet BP2 | 0 | 6 | ||
| p19p2.7 | 1 | 7 |
1The Ethernet configuration is the same for the Expansion shelves with the exception that these shelves are not equipped with the Management and Routing CPUs that are required for the Control shelf.
2Ports FP1 and FP2 are used for inter-chassis connections. The port capacity is 10Gbps. For cabling specifications, see the appropriate chapter in the DSC 8000 Hardware Installation Guide.
3FP3 and FP4 operate in an active-standby mode. Traffic is only transmitted on one port at a time. The standby port becomes active should the active port, for some reason, stops transmitting traffic.
4See footnote 3.
5Control shelf slots 4 to 11 and Expansion shelves slots 16 to 27, 30 to 41, and 45 to 55 may be equipped with Routing, Application CPUs or I/O cards, or a combination of these cards depending on your system configuration.
DSC 8000 Dual Ports
Ethernet redundancy is already built into the DSC 8000 through the two MCH AMC671 cards in slots 1 and 14.
For fail over scenarios, the DSC 8000 also supports dual ports, FP3 and FP4, to ensure that there is no interruption to Ethernet traffic if one of these ports become out-of-service for some reason. If the Ethernet links on FP3 fail, the traffic is automatically rerouted to FP4. If the connectivity is re-established on FP3, the traffic is not immediately rerouted through this port. Traffic is only rerouted back to FP3, if FP4 subsequently fails.
Note
The failover port scenario also applies to Custom VLANs.
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.
DSC 8000 Ports Physical Connections in a Shelf
The following figures show the physical connections to the AMC671 MCH and RMC671μRTM.
AMC671 MCH Faceplate with Port Connections
RMC670 μRTM Faceplate with Port Connections
DSC 8000 Physical Connection between Shelves
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 for these cables, see the appropriate section in the DSC 8000 Hardware Installation Guide.
DSC 8000 Inter-shelf Connections
Overview
Content Tools