Product specifications

CRS-170A L-Band 1:1 Redundancy Switch Revision 3

Modem and Switch Configuration MN/CRS170A.IOM

3.3.1 IP Redundancy Configuration

The following steps outline setting up a CDM-570L 1:1 IP Redundant system using the CLI:

1. The two CDM-570Ls will need an Ethernet connection to each other through a Layer 2 switch

or hub (preferably an L2 switch).

2. Before connecting the modems to the CRS-170A, you will need to first configure the following

CDM-570L IP module settings:

• Redundancy Configuration Æ 1:1 Redundancy set to DISABLED.

• Administration Æ Working Mode: Both modems need to be set to the same

Working Mode.

• Administration Æ Features: Both modems need to have the same IP Option

Feature set.

3. On both modems, enter a unique IP Address that is on the same subnet (Interface

Configuration Æ Ethernet Interface Æ IP Address). Verify that you can ping from one

570 to the other (Operations and Maintenance Æ Diagnostics Æ Ping).

4. On both modems, set Redundancy Configuration Æ 1:1 Redundancy to ENABLED.

Save Parameters to permanent storage and power down both modems.

5. Connect the modems to the CRS-170A. Refer to the CDM-570/570L Installation and

Operation Manual, Sections H.4 Cabling with the CDM-570L and H.5 Cabling with the

CDM-570 IF.

6. While monitoring the Serial console CLI on both modems, observe the following after

powering on both modems at the same time (also observe the CRS-170A Online LEDs to see

which modem is the Online modem).

• Online modem CLI will display:

1:1 Redundancy (Auto Detected)

Redundancy: PARAM File Connection Established.

Redundancy: Sending PARAM File...

• Offline modem CLI will display:

1:1 Redundancy (Auto Detected)

Redundancy: Received PARAM File...

Writing 5447 bytes to PARAM file on Flash

7. On the Online modem, select the Redundancy Configuration menu (Figure 3-2). Observe

that the correct IP Address/Mask is displayed for the Local and Redundant Unit. You will

then need to set the Traffic IP Address/Mask (this also needs to be in the same subnet as the

Management IP addresses).

3–4