Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Management Communications Examples for TCX1000 Ring Networks

 

This sections describes management communications examples for TCX1000 ring networks. It focuses on network examples and describes how each device in the example handles management communications.

Ring ROADM Network – Single Homed Deployment Example 1

The example ring network Figure 1 includes four sites: A, B, C, D.

  • At site A, TCX1000-RDM20-a is on IP subnet Z.1 and TCX1000-RDM20-b is on IP subnet Z.2

  • At site B, TCX1000-RDM20-c is on IP subnet and Z.3 and TCX1000-RDM20-d is on IP subnet and Z.4

  • At site C, TCX1000-RDM20-e is on IP subnet Z.5 and TCX1000-RDM20-f is on IP subnet Z.6

  • At site D, TCX1000-RDM20-g is on IP subnet Z.7 and TCX1000-RDM20-h is on IP subnet Z.8

Looking at our rules for L2/L3 subnets, we can see that all sites are on the Z subnet, so we do not need to worry about the L2/L3 segregation rule in this example.

Figure 1: Ring Network – Single Homed Deployment Example 1
Ring Network – Single Homed
Deployment Example 1

Between the two TCX1000-RDM20s at sites B, C, D there are two connections:

  • The optical line shows the pass-through channels connected between the two TCX1000-RDM20s.

  • The black line shows the DCN ports daisy-chained between the two TCX1000-RDM20s for management communications.

Let us look at how each TCX1000 device in Figure 1 communicates to the DCN HA.

One thing stands out looking at this network; the only site in the network that has direct access to the DCN is site A. This tells us several things:

  • Site A is the hub for management communications and all management communications to sites B, C and D go through the TCX1000-RDM20s at site A.

  • All TCX1000-RDM20s at sites B, C and D must have OSC forwarding enabled in order for them to exchange management messages with site A devices.

  • We have no conflicts using OSC Forwarding because we know that all TCX1000 devices in the network are on the same L2/L3 subnet.

In this example, at site A both TCX1000-RDM20-a and TCX1000-RDM20-b are using their dual-DCN connections for management communications. However, they are also each responsible for communicating management messages over their Line ports to the TCX1000 devices at sites B and D and must therefore have OSC forwarding enabled. TCX1000-RDM20-a communicates management messages over its Line port to TCX1000-RDM20-d at site B and TCX1000-RDM20-b communicates management messages over its line port to TCX1000-RDM20-h at site D.

Table 1 summarizes the management communications and methods for the example network shown in Figure 1.

Table 1: Summary of Management Communications

Site

Device

OSC Forwarding Enabled

Management Communications for proNX Optical Director

A

TCX1000-RDM20-a

Yes

Best Practice: Uses its dual-DCN connections for management communications and its Line port to exchange management communications with TCX1000-RDM20-d at site B over its line port.

TCX1000-RDM20-b

Yes

Best Practice: Uses its dual-DCN connections for management communications and its Line port to exchange management communications with TCX1000-RDM20-h at site D over its line port.

B

TCX1000-RDM20-c

Yes

Uses its Line port to exchange management messages with TCX1000-RDM20-e at site C and has its DCN port daisy-chained to TCX1000-RDM20-d within the same node so that it can receive management messages over its DCN port received from the TCX1000-RDM20-d Line port.

TCX1000-RDM20-d

Yes

Uses its Line port to exchange management messages with TCX1000-RDM20-a at site A and has its DCN port daisy-chained to TCX1000-RDM20-c within the same node so that it can receive management messages over its DCN port received from the TCX1000-RDM20-c Line port.

C

TCX1000-RDM20-e

Yes

Uses its Line port to exchange management messages with TCX1000-RDM20-c at site B and has its DCN port daisy-chained to TCX1000-RDM20-f within the same node so that it can receive management messages over its DCN port received from the TCX1000-RDM20-f Line port connected to site B.

TCX1000-RDM20-f

Yes

Uses its Line port to exchange management messages with TCX1000-RDM20-g at site D and has its DCN port daisy-chained to TCX1000-RDM20-e within the same node so that it can receive management messages over its DCN port received from the TCX1000-RDM20-e Line port connected to site D.

D

TCX1000-RDM20-g

Yes

Uses its Line port to exchange management messages with TCX1000-RDM20-f at site C and has its DCN port daisy-chained to TCX1000-RDM20-h within the same node so that it can receive management messages over its DCN port received from the TCX1000-RDM20-h Line port connected to site A.

TCX1000-RDM20-h

Yes

Uses its Line port to exchange management messages with TCX1000-RDM20-b at site A and has its DCN port daisy-chained to TCX1000-RDM20-g within the same node so that it can receive management messages over its DCN port received from the TCX1000-RDM20-g Line port connected to site C.

In summary, all TCX1000 devices in Figure 1 have redundant paths for management communications either through their Ethernet management ports or their Line ports and we have met all of our other deployment rule requirements.

However, only the TCX1000-RDM20s at site A are using the best practice management communication methods. All other TCX1000-RDM20s use a single DCN port and their Line ports but none of them have dual-DCN connections to the DCN HA, which is the best method to use.

Ring ROADM Network – Single Homed Deployment Example 2

The example network in Figure 2 is exactly the same as the example shown in the previous example Figure 1. All the TCX1000 devices are on subnet Z, so we do not need to worry about IP segregating L2/L3 subnets.

Figure 2: Ring ROADM Network – Single Homed Example 2
Ring ROADM Network –
Single Homed Example 2

Between the two TCX1000-RDM20s at sites A, B, C, D there are two connections:

  • The optical line shows the pass-through channels connected between the two TCX1000-RDM20s.

  • The black line shows the DCN ports daisy-chained between the two TCX1000-RDM20s for management communications.

Let us look at how each TCX1000 device in Figure 2 communicates to the DCN HA.

The other thing that is similar is that the only site in the network that has direct access to the DCN is site A. Sites B, C and D have no direct DCN access and must be remotely managed over their Line ports. However, unlike the previous example, the TCX1000-RDM20s at site A have only a single connection to the DCN. This tells us several things:

  • All management communications in the network go through site A

  • All TCX1000-RDM20 devices at sites A, B, C and D must have OSC forwarding enabled, which we know is alright because the network is on one L2/L3 subnet.

At site A, each TCX1000-RDM20 at site A has only a single connection to the DCN for management communications and we need two paths to each device, so we must daisy-chained the other DCN port on each TCX1000-RDM20 at site A so that they can exchange management messages with each other as a second path.

Table 2 summarizes the management communications and methods for the example network shown in Figure 2.

Table 2: Summary of Management Communications

Site

Device

OSC Forwarding Enabled

Management Communications for proNX Optical Director

A

TCX1000-RDM20-a

Yes

Uses one DCN port to the switch and second DCN port is daisy-chained to TCX1000-RDM20-b so that the device can also communicate management messages over its second DCN port. Its also uses its Line port.

TCX1000-RDM20-b

Yes

Uses one DCN port to the switch and second DCN port is daisy-chained to TCX1000-RDM20-a so that the device can also communicate management messages over its second DCN port. Its also uses its Line port.

B

TCX1000-RDM20-c

Yes

Uses its Line port to exchange management messages with TCX1000-RDM20-e at site C and has its DCN port daisy-chained to TCX1000-RDM20-d within the same node so that it can receive management messages over its DCN port received from the TCX1000-RDM20-d Line port.

TCX1000-RDM20-d

Yes

Uses its Line port to exchange management messages with TCX1000-RDM20-a at site A and has its DCN port daisy-chained to TCX1000-RDM20-c within the same node so that it can receive management messages over its DCN port received from the TCX1000-RDM20-c Line port.

C

TCX1000-RDM20-c

Yes

Uses its Line port to exchange management messages with TCX1000-RDM20-c at site B and has its DCN port daisy-chained to TCX1000-RDM20-f within the same node so that it can receive management messages over its DCN port received from the TCX1000-RDM20-f Line port connected to site B.

TCX1000-RDM20-d

Yes

Uses its Line port to exchange management messages with TCX1000-RDM20-g at site D and has its DCN port daisy-chained to TCX1000-RDM20-e within the same node so that it can receive management messages over its DCN port received from the TCX1000-RDM20-e Line port connected to site D.

D

TCX1000-RDM20-g

Yes

Uses its Line port to exchange management messages with TCX1000-RDM20-f at site C and has its DCN port daisy-chained to TCX1000-RDM20-h within the same node so that it can receive management messages over its DCN port received from the TCX1000-RDM20-h Line port connected to site A.

TCX1000-RDM20-g

Yes

Uses its Line port to exchange management messages with TCX1000-RDM20-b at site A and has its DCN port daisy-chained to TCX1000-RDM20-g within the same node so that it can receive management messages over its DCN port received from the TCX1000-RDM20-g Line port connected to site C.

In summary, all TCX1000 devices in Figure 2 have redundant paths for management communications either through their Ethernet management ports or their Line ports and we have met all of our other deployment rule requirements.

However, none of the TCX1000-RDM20s in this example are using the best practice management communication methods, which is connecting each TCX1000-RDM20 to its own external Layer 2 switch through the dual-DCN ports on the device.

Ring ROADM Network – Dual Homed Example

The example in Figure 3shows a managed ring ROADM network that is dual-homed at sites A and D, providing complete redundancy for management communications.

This network has four sites: A, B, C and D:

  • At site A, TCX1000-RDM20-a is on IP subnet A.6 and TCX1000-RDM20-g is on IP subnet D.1

  • At site B, TCX1000-RDM20-b is on IP subnet and A.2 and TCX1000-RDM20-c is on IP subnet and A.3

  • At site C, TCX1000-RDM20-d is on IP subnet A.4 and TCX1000-RDM20-e is on IP subnet A.5

  • At site D, TCX1000-RDM20-f is on IP subnet A.6 and TCX1000-RDM20-h is on IP subnet D.1

Based on our rules for L2/L3 subnets, we have segregated the L2/L3 subnets at sites A and D using dedicated L2 switches and L3 (IP) management communications are segregated through separate Ethernet DCNs for the D.1 and A.6 IP subnets.

So again, we have segregated L2/L3 subnets and kept them together. This example also has two RSTP domains, one for subnet D.1 and one for subnet A.6.

Figure 3: Ring ROADM Network – Dual Homed Example
Ring ROADM Network – Dual
Homed Example

Between the two TCX1000-RDM20s at sites B and C there are two connections:

  • The optical line shows the pass-through channels connected between the two TCX1000-RDM20s.

    Note

    If their is a failure with management communications at site A hub, you can dynamically activate the site D management communication hub and all management communications will reroute over the pass-through connections between the TCX1000-RDM20s at sites A and D.

  • The black line shows the DCN ports daisy-chained between the two TCX1000-RDM20s for management communications.

As we look at how each TCX1000 device in Figure 3 communicates to its respective DCN, a couple of things are important to notice:

  • The TCX1000 devices on subnet D.1 at sites A and D (TCX1000-RDM20-g and TCX1000-RDM20-h), each have a single connection to their DCN for management communications. The second path for management communications for TCX1000-RDM20-g and TCX1000-RDM20-h on subnet D.1 is their Line ports and therefore we must enable OSC forwarding on both of these devices.

  • The TCX1000 devices on subnet A.6 at sites A and D (TCX1000-RDM20-a and TCX1000-RDM20-f), each have a single connection to their DCN for management communications. The second path for management communications for TCX1000-RDM20-a and TCX1000-RDM20-f on subnet A.6 is their Line ports and therefore we must enable OSC forwarding on both of these devices.

  • At sites B and C, each TCX1000-RDM20 uses its Line port for management communications and we therefore must enable OSC forwarding on them. We must also daisy chain the DCN port on the TCX1000-RDM20 at these sites so they can also receive management messages from each others Line ports.

Note

What we must never do in this network is daisy chain the DCN ports between the TCX1000-RDM20s at sites A and D. Both of these sites include TCX1000-RDM20s that are different L2/L3 subnets.

Table 3 summarizes the management communications and methods for the example network shown in Figure 3.

Table 3: Summary of Management Communications

Site

Device

OSC Forwarding Enabled

Management Communications for proNX Optical Director

A

TCX1000-RDM20-a

Yes

Uses a single connection to the DCN through the L2 switch for management communications and also exchanges management messages with TCX1000-RDM20-c at site B over its Line port.

TCX1000-RDM20-g

Yes

Uses a single connection to the DCN through the L2 switch for management communications and also exchanges management messages with TCX1000-RDM20-h at site D over its Line port.

B

TCX1000-RDM20-b

Yes

Uses its Line port to exchange management messages with TCX1000-RDM20-d at site C and has its DCN port daisy-chained to TCX1000-RDM20-c within the same node so that it can receive management messages over its DCN port from the TCX1000-RDM20-c Line port.

TCX1000-RDM20-c

Yes

Uses its Line port to exchange management messages with TCX1000-RDM20-a at site A and has its DCN port daisy-chained to TCX1000-RDM20-b within the same node so that it can receive management messages over its DCN port received from the TCX1000-RDM20-b Line port.

C

TCX1000-RDM20-d

Yes

Uses its Line port to exchange management messages with TCX1000-RDM20-b at site B and has its DCN port daisy-chained to TCX1000-RDM20-e within the same node so that it can receive management messages over its DCN port received from the TCX1000-RDM20-e Line port.

TCX1000-RDM20-e

Yes

Uses its Line port to exchange management messages with TCX1000-RDM20-f at site D and has its DCN port daisy-chained to TCX1000-RDM20-d within the same node so that it can receive management message over its DCN port received from the TCX1000-RDM20-d Line port connected to site D.

D

TCX1000-RDM20-f

Yes

Uses a single connection to the DCN through the switch and also exchange management messages over its Line port with TCX1000-RDM20-e at site C.

TCX1000-RDM20-h

Yes

Uses a single connection to the DCN through the switch and also exchange management messages with TCX1000-RDM20-g at site A.

In summary, all TCX1000 devices in Figure 3 have redundant paths for management communications either through their Ethernet management ports or their Line ports and we have met all of our other deployment rule requirements.

Best Practice

Although none of the TCX1000-RDM20s in this example are using the best practice management communication methods, which is connecting each TCX1000-RDM20 to its own external Layer 2 switch through the dual-DCN ports on the device, this example does meet best practices for management communications at site A, because it has completely duplicated the management communication hub at site D. If there is a failure with management communications at the site A hub, you can dynamically activate the site D hub in the proNX Optical Director.