Chapter 7, SONET Topologies

This chapter explains Cisco ONS 15327 SONET topologies. To provision topologies, refer to the Cisco ONS 15327 Procedure Guide.

7.1 Bidirectional Line Switched Rings

One ONS 15327 can support two concurrent BLSRs each BLSR can have up to 32 ONS 15327s. Because the working and protect bandwidths must be equal, you can create only OC-12, or OC-48 BLSRs. For information about BLSR protection channels, see the "BLSR Protection Channel Circuits" section.

Note For best performance, BLSRs should have one LAN connection for every ten nodes in the BLSR.

7.1.1 BLSR Functionality

The Cisco ONS 15327 supports two-fiber BLSRs (the ONS 15454 also supports four-fiber BLSRs); each fiber in a two-fiber BLSR is divided into working and protect bandwidths. For example, in an OC-48 BLSR ( Figure 7-1), STSs 1 to 24 carry the working traffic, and STSs 25 to 48 are reserved for protection. Working traffic (STSs 1 to 24) travels in one direction on one fiber and in the opposite direction on the second fiber. The Cisco Transport Controller (CTC) circuit routing routines calculate the "shortest path" for circuits based on many factors, including user requirements, traffic patterns, and distance. For example, in Figure 7-1, circuits going from Node 0 to Node 1 will typically travel on Fiber 1, unless that fiber is full, in which case circuits will be routed on Fiber 2 through Node 3 and Node 2. Traffic from Node 0 to Node 2 (or Node 1 to Node 3) can be routed on either fiber, depending on circuit provisioning requirements and traffic loads.

The SONET K1, K2, and K3 bytes carry the information that governs BLSR protection switches. Each BLSR node monitors the K bytes to determine when to switch the SONET signal to an alternate physical path. The K bytes communicate failure conditions and actions taken between nodes in the ring.

If a break occurs on one fiber, working traffic targeted for a node beyond the break switches to the protect bandwidth on the second fiber. The traffic travels in a reverse direction on the protect bandwidth until it reaches its destination node. At that point, traffic is switched back to the working bandwidth.

Figure 7-3 shows how traffic is rerouted following a line break between Node 0 and Node 3.

•

All circuits originating on Node 0 carried traffic to Node 2 on Fiber 2 are switched to the protect bandwidth of Fiber 1. For example, a circuit carrying traffic on STS-1 on Fiber 2 is switched to STS-25 on Fiber 1. A circuit carried on STS-2 on Fiber 2 is switched to STS-26 on Fiber 1. Fiber 1 carries the circuit to Node 3 (the original routing destination). Node 3 switches the circuit back to STS-1 on Fiber 2 where it is routed to Node 2 on STS-1.

•

Circuits originating on Node 2 that normally carried traffic to Node 0 on Fiber 1 are switched to the protect bandwidth of Fiber 2 at Node 3. For example, a circuit carrying traffic on STS-2 on Fiber 1 is switched to STS-26 on Fiber 2. Fiber 2 carries the circuit to Node 0 where the circuit is switched back to STS-2 on Fiber 1 and then dropped to its destination.

7.1.2 BLSR Bandwidth

BLSR nodes can terminate traffic coming from either side of the ring. Therefore, BLSRs are suited for distributed node-to-node traffic applications such as interoffice networks and access networks.

BLSRs allow bandwidth to be reused around the ring and can carry more traffic than a network with traffic flowing through one central hub. BLSRs can also carry more traffic than a UPSR operating at the same OC-N rate. Table 7-1 shows the bidirectional bandwidth capacities of BLSRs. The capacity is the OC-N rate divided by two, multiplied by the number of nodes in the ring minus the number of pass-through STS-1 circuits.

Table 7-1 BLSR Capacity
OC Rate	Working Bandwidth	Protection Bandwidth	Ring Capacity
OC-12	STS1-6	STS 7-12	6 x N¹ - PT²
OC-48	STS 1-24	STS 25-48	24 x N - PT

¹N equals the number of ONS 15327 nodes configured as BLSR nodes.

²PT equals the number of STS-1 circuits passed through ONS 15327 nodes in the ring (capacity can vary depending on the traffic pattern).

Figure 7-4 shows an example of BLSR bandwidth reuse. The same STS carries three different traffic sets simultaneously on different spans around the ring: one set from Node 3 to Node 1, another set from Node 1 to Node 2, and another set from Node 2 to Node 3.

7.1.3 BLSR Application Example

Figure 7-5 shows a BLSR implementation example. A regional long-distance network connects to other carriers at Node 0. Traffic is delivered to the service provider's major hubs.

•

Carrier 1 delivers two DS-3s over one OC-3 spans to Node 0. Carrier 2 provides two DS-3s directly. Node 0 receives the signals and delivers them around the ring to the appropriate node.

•

The ring also brings 14 DS-1s back from each remote site to Node 0. Intermediate nodes serve these shorter regional connections.

•

The ONS 15327 OC-3 card supports a total of four OC-3 ports so that two additional OC-3 spans can be added at little cost.

Figure 7-7 shows the shelf assembly layout for the remaining sites in the ring. In this BLSR configuration, an additional three DS-3s at Nodes 1, 2, 3, and 4 can be activated. Each site has free slots for future traffic needs.

7.1.4 BLSR Fiber Connections

Plan your fiber connections and use the same plan for all BLSR nodes. For example, make the east port the farthest slot to the right and the west port the farthest slot to the left. Plug fiber connected to an east port at one node into the west port on an adjacent node. Figure 7-8 shows fiber connections for a BLSR with trunk (span) cards in Slot 1 (west) and Slot 2 (east). See the Cisco ONS 15327 Procedure Guide for fiber connection procedures.

Note Always plug the transmit (Tx) connector of an OC-N card at one node into the receive (Rx) connector of an OC-N card at the adjacent node. Cards will display an SF LED when Tx and Rx connections are mismatched.

7.2 Unidirectional Path Switched Rings

UPSRs provide duplicate fiber paths around the ring. Working traffic flows in one direction and protection traffic flows in the opposite direction. If a problem occurs with the working traffic path, the receiving node switches to the path coming from the opposite direction.

CTC automates ring configuration. UPSR traffic is defined within the ONS 15327 on a circuit-by-circuit basis. If a path-protected circuit is not defined within a 1+1 or BLSR line protection scheme and path protection is available and specified, CTC uses UPSR as the default.

A UPSR circuit requires two DCC-provisioned optical spans per node. UPSR circuits can be created across these spans until their bandwidth is consumed.

Because each traffic path is transported around the entire ring, UPSRs are best suited for networks where traffic concentrates at one or two locations and is not widely distributed. UPSR capacity is equal to its bit rate. Services can originate and terminate on the same UPSR, or they can be passed to an adjacent access or interoffice ring for transport to the service-terminating location.

Note If a UPSR circuit is created manually by TL1, data communications channels (DCCs) are not needed; therefore, UPSR circuits are limited by the cross-connection bandwidth, or the span bandwidth, but not by the number of DCCs.

7.2.1 UPSR Bandwidth

The span bandwidth consumed by a UPSR circuit is two times the circuit bandwidth, because the circuit is duplicated. The cross-connection bandwidth consumed by a UPSR circuit is three times the circuit bandwidth at the source and destination nodes only. The cross-connection bandwidth consumed by an intermediate node has a factor of one.

The UPSR circuit limit is the sum of the optical bandwidth containing 10 section data communications channels (SDCCs) divided by two if you are using redundant XTC cards. The spans can be of any bandwidth from OC-3 to OC-48. The circuits can be of any size from VT1.5 to 48c.

7.2.2 UPSR Application Example

Figure 7-9 shows a basic UPSR configuration. If Node ID 0 sends a signal to Node ID 2, the working signal travels on the working traffic path through Node ID 1. The same signal is also sent on the protect traffic path through Node ID 3.

If a fiber break occurs ( Figure 7-10), Node ID 2 switches its active receiver to the protect signal coming through Node ID 3.

Figure 7-11 shows a common UPSR application. OC-3 optics provide remote switch connectivity to a host TR-303 switch. In the example, each remote switch requires eight DS-1s to return to the host switch. Figure 7-12 and Figure 7-13 show the shelf layout for each site.

Node ID 0 has two XTC-28-3 cards to provide 28 active DS-1 ports. The other sites only require XTC-14 cards to handle the 14 DS-1s to and from the remote switch. You can use the other half of each ONS 15327 shelf assembly to provide support for a second or third ring to other existing or planned remote sites.

In the OC-3 UPSR sample, Node ID 0 contains two XTC 28-3 cards and two OC3 IR 4 1310 cards. Two free slots can be provisioned with cards or left empty. Figure 7-12 shows the shelf setup for these cards.

In the Figure 7-11 example, Nodes IDs 1, 2, and 3 each contain two XTC cards and two OC3 IR 4 1310 cards. Two free slots exist. They can be provisioned with other cards or left empty. Figure 7-13 shows the shelf assembly setup for this configuration sample.

7.3 Subtending Rings

The ONS 15327 supports up to ten SONET SDCCs. Table 7-2 shows the SONET rings that can be created on each ONS 15327 node using redundant XTC cards.

Table 7-2 ONS 15327 Rings with Redundant XTC Cards
Ring Type	Maximum rings per node
BLSRs	2
UPSR	5^¹

¹See the "Unidirectional Path Switched Rings" section

Subtending rings reduce the number of nodes and cards required and reduce external shelf-to-shelf cabling. Figure 7-14 shows an ONS 15327 with two subtending rings.

7.3.1 Subtending Ring Examples

Figure 7-15 shows a UPSR subtending from a BLSR. In this example, Node 3 is the only node serving both the BLSR and UPSR. OC-N cards in Slots 1 and 2 serve the BLSR, and OC-N cards in Slots 3 and 4 serve the UPSR.

The ONS 15327 can support two BLSRs on the same node. This capability allows you to deploy an ONS 15327 in applications requiring SONET digital cross connect systems (DCSs) or multiple SONET add/drop multiplexers (ADMs).

Figure 7-16 shows two BLSRs shared by one ONS 15327. Ring 1 runs on Nodes 1, 2, 3, and 4. Ring 2 runs on Nodes 4, 5, 6, and 7. Two BLSR rings, Ring 1 and Ring 2, are provisioned on Node 4. Ring 1 uses cards in Slots 1 and 2, and Ring 2 uses cards in Slots 3 and 4.

After subtending two BLSRs, you can route circuits from nodes in one ring to nodes in the second ring. For example, in Figure 7-16 you can route a circuit from Node 1 to Node 7. The circuit would normally travel from Node 1 to Node 4 to Node 7. If fiber breaks occur, for example between Nodes 1 and 4 and Nodes 4 and 7, traffic is rerouted around each ring: in this example, Nodes 2 and 3 in Ring 1 and Nodes 5 and 6 in Ring 2.

7.3.2 Connecting ONS 15327 Nodes and ONS 15454 Nodes

You can install ONS 15327 nodes into a network comprised entirely of ONS 15327 nodes or into a network that has a mix of ONS 15327 and ONS 15454 nodes. The ONS 15327 interoperates with the ONS 15454 in linear, UPSR, and 2-fiber BLSR configurations. Because connection procedures for both types of nodes are the same (for example, adding or dropping nodes from a UPSR or linear configuration, or creating DCCs), follow the instructions in the Cisco ONS 15327 Procedure Guide whenever you make connections between ONS 15454 and ONS 15327 nodes. Figure 7-17 shows a basic linear or UPSR connection between ONS 15327 and ONS 15454 nodes.

7.4 Terminal Point-to-Point and Linear ADM Configurations

You can configure ONS 15327s in a terminal point-to-point network (2 nodes) or as a line of add/drop multiplexers (ADMs) (3 or more nodes) by configuring one set of OC-N cards as the working path and a second set as the protect path. Unlike rings, terminal and linear ADMs require that the OC-N cards at each node be in 1+1 protection to ensure that a break to the working line is automatically routed to the protect line.

Figure 7-19 shows three ONS 15327s in a linear ADM configuration. Working traffic flows from Slot 3/Node 1 to Slot 3/Node 2, and from Slot 2/Node 2 to Slot 2/Node 3. You create the protect path by placing Slot 3 in 1+1 protection with Slot 1 at Nodes 1 and 2, and Slot 2 in 1+1 protection with Slot 4 at Nodes 2 and 3.

7.5 Path-Protected Mesh Networks

In addition to single BLSRs, UPSRs and terminal point-to-point or linear ADMs, you can extend ONS 15327 traffic protection by creating path-protected mesh networks (PPMNs). PPMNs include multiple ONS 15327 SONET topologies and extend the protection provided by a single UPSR to the meshed architecture of several interconnecting rings. In a PPMN, circuits travel diverse paths through a network of single or multiple meshed rings. When you create circuits, you can have CTC automatically route circuits across the PPMN, or you can manually route them. You can also choose levels of circuit protection. For example, if you choose full protection, CTC creates an alternate route for the circuit in addition to the main route. The second route follows a unique path through the network between the source and destination and sets up a second set of cross-connections.

For example, in Figure 7-20, a circuit is created from Node 3 to Node 9. CTC determines that the shortest route between the two nodes passes through Node 8 and Node 7, shown by the dotted line, and automatically creates cross-connections at Nodes 3, 8, 7, and 9 to provide the primary circuit path.

If full protection is selected, CTC creates a second unique route between Nodes 3 and 9 which, in this example, passes through Nodes 2, 1, and 11. Cross-connections are automatically created at Nodes 3, 2, 1, 11, and 9, shown by the dashed line. If a failure occurs on the primary path, traffic switches to the second circuit path. In this example, Node 9 switches from the traffic coming in from Node 7 to the traffic coming in from Node 11 and service resumes. The switch occurs within 50 ms.

PPMN also allows spans with different SONET speeds to be mixed together in "virtual rings." Figure 7-21 shows Nodes 1, 2, 3, and 4 in a standard OC-48 ring. Nodes 5, 6, 7, and 8 link to the backbone ring through OC-12 fiber. The "virtual ring" formed by Nodes 5, 6, 7, and 8 uses both OC-48 and OC-12 cards.

7.6 Four Node Configurations

You can link multiple ONS 15327s using their OC-N cards (also known as creating a fiber-optic bus) to accommodate more access traffic than a single ONS 15327 can support. For example, to drop more than 28 DS-1s or 3 DS-3s (the maximum that can be aggregated in a single node), you can link the nodes but not merge multiple nodes into a single ONS 15327. You can link nodes with OC-12 or OC-48 fiber spans as you would link any other two network nodes. The nodes can be grouped in one facility to aggregate more local traffic.

7.7 Optical Speed Upgrades

A span is the optical fiber connection between two ONS 15327 nodes. In a span (optical speed) upgrade, the transmission rate of a span is upgraded from a lower to a higher OC-N signal but all other span configuration attributes remain unchanged. With multiple nodes, a span upgrade is a coordinated series of upgrades on all nodes in the ring or protection group.

To perform a span upgrade, the higher-rate optical card must replace the lower-rate card in the same slot. All spans in the network must be upgraded. The protection configuration of the original lower-rate optical card (BLSR, UPSR, and 1+1) is retained for the higher-rate optical card.

When performing span upgrades on a large number of nodes, Cisco recommends that you upgrade all spans in a network consecutively and in the same maintenance window. Until all spans are upgraded, mismatched card types will be present.

Cisco recommends using the Span Upgrade Wizard to perform span upgrades. Although you can also use the manual span upgrade procedures, the manual procedures are mainly provided as error recovery for the wizard. The Span Upgrade Wizard and the manual span upgrade procedures require at least two technicians (one at each end of the span) who can communicate with each other during the upgrade. Upgrading a span is non-service affecting and will cause no more than three switches, each of which is less than 50 ms in duration.

Note Span upgrades do not upgrade SONET topologies, for example, a 1+1 group to a BLSR. See the Cisco ONS 15327 Procedure Guide for topology upgrade procedures.

7.7.1 Span Upgrade Wizard

The Span Upgrade Wizard automates all steps in the manual span upgrade procedure (BLSR, UPSR, and 1+1). The wizard can upgrade both lines of a 1+1 group; the wizard upgrades UPSRs and BLSRs one line at a time. The Span Upgrade Wizard requires that spans have DCCs enabled.

The Span Upgrade Wizard provides no way to back out of an upgrade. In the case of an error, you must exit the wizard and initiate the manual procedure to either continue with the upgrade or back out of it. To continue with the manual procedure, examine the standing conditions and alarms to identify the stage in which the wizard failure occurred.

7.7.2 Manual Span Upgrades

Manual span upgrades are mainly provided as error recovery for the Span Upgrade Wizard, but they can be used to perform span upgrades. You can perform a manual span upgrade on a BLSR, UPSR, and on a 1+1 protection group.

Downgrading can be performed to back out of a span upgrade. The procedure for downgrading is the same as upgrading except that you choose a lower-rate card type and install a lower-rate card. You cannot downgrade if circuits exist on the STSs that will be removed (the higher STSs).

Table Of Contents

SONET Topologies