Setup guide

5-3

Cisco 6400 Software Setup Guide

OL-1183-04

Chapter5 Redundancy and SONET APS Configuration

NSP Redundancy

Both NSP slots are numbered slot 0 for consistent interface identification between primary and

secondary devices. Nevertheless, the left NSP slot is labeled slot A and the right slot is labeled slot B to

distinguish between the two slots, when required.

You can use EHSA redundancy for simple hardware backup or for software error protection. Hardware

backup protects against NSP card failure because you configure both NSP cards with the same software

image and configuration information. Additionally, you configure the system to automatically

synchronize configuration information on both cards when changes occur.

Software error protection protects against critical Cisco IOS software errors in a particular release

because you configure the NSP cards with different software images, but use the same configuration. If

you are using new or experimental Cisco IOS software, consider using the software error protection

method.

This section includes:

• Configuring Redundant NSPs, page 5-3

• Synchronizing Redundant NSPs, page 5-4

• Erasing Startup Configurations on Redundant NSPs, page 5-5

• PCMCIA Disk Mirroring, page 5-5

• Using NSP Redundancy for Hardware Backup, page 5-12

• Using NSP Redundancy for Software Error Protection, page 5-13

• Booting Redundant NSPs from a Network Server, page 5-14

Configuring Redundant NSPs

If two NSPs are installed in the Cisco 6400, they automatically act as a redundant pair. No configuration

is necessary.

Verifying NSP Redundancy

To verify NSP redundancy, use the show redundancy EXEC command:

Switch# show redundancy

NSP A:Primary

NSP B:Secondary

Secondary NSP information:

Secondary is up

Secondary has 131072K bytes of memory.

User EHSA configuration (by CLI config):

secondary-console = off

keepalive = on

config-sync modes:

standard = on

start-up = on

boot-var = on

config-reg = on

calendar = on

Debug EHSA Information: