|
Table Of Contents
Starting Up the Cisco ONS 15540
Using the Console Ports, NME Ports, and Auxiliary Ports
Configuring IP Access on the NME Interface
Displaying the NME Interface Configuration
Displaying the Operating Configurations
Displaying the NTP Configuration
About Processor Card Redundancy
Configuring Processor Card Redundancy
Forcing a Switchover from Privileged EXEC Mode
Forcing a Switchover from ROM Monitor Mode
Synchronizing the Configurations
Displaying the Processor Card Redundancy Configuration and Status
Configuring Fan Failure Shutdown
Displaying the Fan Tray Failure Shutdown Configuration
Initial Configuration
This chapter describes how to configure the Cisco ONS 15540 so it can be accessed by other devices. This chapter includes the following sections:
• Starting Up the Cisco ONS 15540
• Using the Console Ports, NME Ports, and Auxiliary Ports
• Configuring IP Access on the NME Interface
• About Processor Card Redundancy
• Configuring Processor Card Redundancy
• Configuring Fan Failure Shutdown
About the Processor Card
The processor card provides intelligence to the Cisco ONS 15540. The processor card supports SNMP (Simple Network Management Protocol) and many MIBs (Management Information Bases).
The Cisco ONS 15540 uses 64-bit MIPS RM7000 processors running at 250 MHz. The processor has primary cache comprised of 16 KB for instructions and 16 KB for data. The secondary cache is 256 KB for both instructions and data. A third-level cache controller supports 512 KB, 1 MB, 2 MB, 4 MB, and 8 MB block write-through cache. Both the primary cache and the secondary cache are integrated onto the processor. The optional third-level cache is controlled through an on-chip cache controller.
The processor card supports a dual-height Flash memory Type II slot that can accommodate two Flash PC Cards.
The Cisco ONS 15540 supports redundant operation with dual processor cards. The processor cards reside in slots 6 and 7, the seventh and eighth slots from the left as you face the chassis. For more information, see the "About Processor Card Redundancy" section.
For more information on the processor card, refer to the
Cisco ONS 15540 ESP Hardware Installation Guide.Starting Up the Cisco ONS 15540
Before starting up the Cisco ONS 15540, you should verify the following:
•The system is set for the correct AC (or DC) power voltages.
Refer to the Cisco ONS 15540 ESP Hardware Installation Guide for correct power voltages.
•The cables are connected to the system.
•A console terminal is connected to the system.
Refer to the Cisco ONS 15540 ESP Hardware Installation Guide for instructions.
When you start up the Cisco ONS 15540, the CLI (command-line interface) prompts you to enter the initial configuration dialog. Answer no to this prompt:
Would you like to enter the initial dialog? [yes]: no
You see the following user EXEC prompt:
Switch>
You can now begin configuring the processor card.
Using the Console Ports, NME Ports, and Auxiliary Ports
You can configure the Cisco ONS 15540 from a direct console connection to the console port or remotely through its NME (network management Ethernet) port.
•If you are using a direct console connection, configure your terminal emulation program for 9600 baud, 8 data bits, no parity, and 1 stop bit.
•If you are using the NME port interface, you must assign an IP address to the interface (fastethernet 0).
For interface configuration instructions, see the "Configuring IP Access on the NME Interface" section.
For further details on configuring ports and lines for management access, refer to the
Cisco IOS Configuration Fundamentals Configuration Guide.Modem Support
The auxiliary port of Cisco ONS 15540 provides for modem connection support. However, the hardware flow control signals are not available on the auxiliary port. The following settings on the modem are required:
•Enable auto answer mode
•Suppress result codes
•Disable hardware flow control
•Ensure auxiliary port terminal characteristics (speed/stop bits/parity) matches that of modem
You can configure your modem by setting the DIP switches on the modem itself or by setting them via terminal equipment connected to the modem. Refer to the user manual provided with your modem for the correct configuration information.
Note Because there are no hardware flow control signals available on the auxiliary port, the auxiliary port terminal characteristics should match the modem settings.
For further details on configuring ports and modems for management access, refer to the
Cisco IOS Configuration Fundamentals Configuration Guide and the
Cisco IOS Dial Services Configuration Guide: Terminal Services.About Passwords
You can configure both an enable password and an enable secret password. For maximum security, the enable password should be different from the enable secret password.
Enable Password
The enable password is a nonencrypted password. It can contain any number of uppercase and lowercase alphanumeric characters. Give the enable password only to users permitted to make configuration changes to the Cisco ONS 15540.
Enable Secret Password
The enable secret password is a secure, encrypted password. By setting an encrypted password, you can prevent unauthorized configuration changes. On systems running Cisco IOS, you must type in the enable secret password before you can access global configuration mode.You must type in the enable secret password to access boot ROM software.
An enable secret password contains from 1 to 25 uppercase and lowercase alphanumeric characters. The first character cannot be a number. Spaces are valid password characters. Leading spaces are ignored; trailing spaces are recognized.
You will configure passwords in the next section, Configuring IP Access on the NME Interface.
Configuring IP Access on the NME Interface
The Fast Ethernet interface, or NME, on the active processor card, named fastethernet 0, is the management interface that allows multiple, simultaneous Telnet or SNMP network management sessions.
You can remotely configure the Cisco ONS 15540 through the Fast Ethernet interface, but first you must configure an IP address so that the active processor card is reachable. There are two ways to configure the NME interface: manually from the CLI or by copying the configuration from the BOOTP server into NVRAM.
For information on configuring the NME interface on the standby processor card, fastethernet-sby 0, refer to the Cisco ONS 15540 ESP Software Upgrade Guide .
Note Before you begin to manually configure an NME interface, obtain its IP address and IP subnet mask. Also make sure the console cable is connected to the console port.
To configure IP access on the NME port fastethernet 0 from the CLI, perform these steps from the console interface:
Command PurposeStep 1
Switch> enable
Switch#
Enters privileged EXEC mode.
Step 2
Switch#
show hardware
Verifies the installed hardware part numbers and serial numbers.
Step 3
Switch#
configure terminal
Switch(config)#
Enters global configuration mode.
Step 4
Switch(config)# enable password password
Sets the enable password. See the "About Passwords" section.
Step 5
Switch(config)# enable secret password
Specifies an enable secret password. Once set, the enable secret password must be entered to gain access to global configuration mode.
Step 6
Switch(config)#
interface fastethernet 0
Switch(config-if)#
Enters interface configuration mode on interface fastethernet 0, the NME port on the active processor card.
Step 7
Switch(config-if)#
ip address ip-address subnet-mask
Specifies the IP address and IP subnet mask for the management port interface.
Step 8
Switch(config-if)#
speed {10 | 100 | auto}
Specifies the transmission speed. The default is auto (autonegotiation).
Step 9
Switch(config-if)#
duplex {auto | full | half}
Specifies the duplex mode. The default is auto (autonegotiation).
Step 10
Switch(config-if)#
exit
Switch(config)#
Returns to global configuration mode.
Step 11
Switch(config)#
line vty line-number
Switch(config-line)#
Enters line configuration mode for virtual terminal connections. Commands entered in this mode control the operation of Telnet sessions.
Step 12
Switch(config-line)# password password
Specifies a password for Telnet sessions.
Step 13
Switch(config-line)# end
Switch#
Returns to privileged EXEC mode.
Step 14
Switch#
copy system:running-config nvram:startup-config
Saves the configuration changes to NVRAM.
The Cisco ONS 15540 NME interface should now be operating correctly.
Note If a processor card switchover occurs, you can use the same IP address to access the other processor card after it becomes active.
Note In a dual shelf node configuration, perform these steps on the NME interfaces on both shelves in the node.
Displaying the NME Interface Configuration
To display the configuration of the NME interface, use the following EXEC command:
Example
Switch# show interfaces fastethernet 0
FastEthernet0 is up, line protocol is up
Hardware is AmdFE, address is 0000.1644.28ea (bia 0000.1644.28ea)
Internet address is 172.20.54.152/24
MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Half-duplex, 10Mb/s, 100BaseTX/FX
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:00, output 00:00:00, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue :0/40 (size/max)
5 minute input rate 3000 bits/sec, 6 packets/sec
5 minute output rate 1000 bits/sec, 3 packets/sec
36263 packets input, 3428728 bytes
Received 17979 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog
0 input packets with dribble condition detected
20363 packets output, 4279598 bytes, 0 underruns
0 output errors, 8 collisions, 0 interface resets
0 babbles, 0 late collision, 72 deferred
0 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out
Displaying the Operating Configurations
You can display the configuration file when you are in privileged EXEC (enable) mode.
•To see the current operating configuration, enter the following command at the enable prompt:
Switch#
more system:running-config
•To see the configuration saved in NVRAM, enter the following command:
Switch#
more nvram:startup-config
If you made changes to the configuration, but did not yet write the changes to NVRAM, the contents of the running-config file will differ from the contents of the startup-config file.
Configuring the Host Name
In addition to passwords and an IP address, your initial configuration should include the host name to make it easier to configure and troubleshoot the Cisco ONS 15540. To configure the host name, perform the following steps:
Note The host name is also synchronized with the standby processor card. The host name prompt on the standby processor card appears with "sby-" as a prefix.
Example
The following example shows how to configure a new host name, beginning in privileged EXEC mode:
Switch#
configure terminal
Switch(config)#
hostname ONS15540
ONS15540(config)#
end
ONS15540#
copy system:running-config nvram:startup-config
About NTP
The NTP (Network Time Protocol) is a utility for synchronizing system clocks over the network, providing a precise time base for networked workstations and servers. In the NTP model, a hierarchy of primary and secondary servers pass timekeeping information by way of the Internet to cross-check clocks and correct errors arising from equipment or propagation failures.
An NTP server must be accessible by the client switch. NTP runs over UDP (User Datagram Protocol), which in turn runs over IP. NTP is documented in RFC 1305. All NTP communication uses UTC (Coordinated Universal Time), which is the same as Greenwich Mean Time. An NTP network usually gets its time from an authoritative time source, such as a radio clock or an atomic clock attached to a time server. NTP distributes this time across the network. NTP is extremely efficient; no more than one packet per minute is necessary to synchronize two machines to within a millisecond of one another.
NTP uses a stratum to describe how many NTP hops away a machine is from an authoritative time source. A stratum 1 time server has a radio or atomic clock directly attached, a stratum 2 time server receives its time from a stratum 1 time server, and so on. A machine running NTP automatically chooses as its time source the machine with the lowest stratum number that it is configured to communicate with through NTP. This strategy effectively builds a self-organizing tree of NTP speakers.
NTP has two ways to avoid synchronizing to a machine whose time might be ambiguous:
•NTP never synchronizes to a machine that is not synchronized itself.
•NTP compares the time reported by several machines and does not synchronize to a machine whose time is significantly different from the others, even if its stratum is lower.
The communications between machines running NTP, known as associations, are usually statically configured; each machine is given the IP address of all machines with which it should form associations. Accurate timekeeping is possible by exchanging NTP messages between each pair of machines with an association.
The Cisco implementation of NTP does not support stratum 1 service; it is not possible to connect to a radio or atomic clock. We recommend that you obtain the time service for your network from the public NTP servers available in the IP Internet. If the network is isolated from the Internet, the Cisco NTP implementation allows a machine to be configured so that it acts as though it is synchronized using NTP, when in fact it has determined the time using other means. Other machines then synchronize to that machine using NTP.
A number of manufacturers include NTP software for their host systems, and a version for systems running UNIX and its various derivatives is also publicly available. This software allows host systems to be time-synchronized as well.
Configuring NTP
NTP services are enabled on all interfaces by default. You can configure your Cisco ONS 15540 in either of the following NTP associations:
•Peer association—This system either synchronizes to the other system or allows the other system to synchronize to it.
•Server association—This system synchronizes to the other system, and not the other way around.
From global configuration mode, use the following procedure to configure NTP in a server association that transmits broadcast packets and periodically updates the calendar:
For information on other optional NTP configurations, see the
Cisco IOS Configuration Fundamentals Configuration Guide.Displaying the NTP Configuration
To view the current NTP configuration and status, use the following EXEC command:
Example
The following example shows the NTP configuration and status:
Switch# show ntp status
Clock is synchronized, stratum 4, reference is 198.92.30.32
nominal freq is 250.0000 Hz, actual freq is 249.9999 Hz, precision is 2**24
reference time is B6C04F19.41018C62 (18:21:13.253 UTC Thu Feb 27 1997)
clock offset is 7.7674 msec, root delay is 113.39 msec
root dispersion is 386.72 msec, peer dispersion is 1.57 msec
About Processor Card Redundancy
The Cisco ONS 15540 supports fault tolerance by allowing the standby processor card to take over if the active processor card fails. This standby, or redundant, processor card runs in hot-standby state. In hot-standby state, the standby processor card is partially booted with Cisco IOS software, but no configuration is loaded.
At the time of a switchover from the active processor card, the standby processor card becomes active and loads the configuration as follows:
•If the running configuration file on the active and standby processor cards match, the new active processor card uses the running configuration file.
•If the running configuration file on the new active processor card is missing or invalid, the new active processor card uses the startup configuration file in its NVRAM (not the NVRAM of the former active processor card).
The former active processor card then reloads and becomes the standby processor card.
Note If the standby processor card is unavailable, the system reports a minor alarm. Use the show facility-alarm status command to display the redundancy alarm status.
When the Cisco ONS 15540 is powered on, the two processor cards arbitrate to determine which is the active processor card and which is the standby processor card. The following rules apply during arbitration:
•A newly inserted processor card always comes up as the standby processor card, except in cases where the newly inserted card is the only one present.
•If one of the processor cards cannot boot its software image, the other processor card boots as the active processor card, allowing you to correct the situation manually.
•If none of the above conditions is true, the processor card in slot 6 becomes the active processor card.
During normal operation, the active processor card boots completely. The standby processor card partially boots, stopping short of parsing the configuration. From this point, the active and standby processor cards communicate periodically to synchronize any system configuration changes.
Table 3-1 describes the five processor card hardware states.
Figure 3-1 shows the valid hardware transition states for a system with redundant processor cards.
Figure 3-1 Processor card State Transition Diagram
In response to redundancy events, such as switchovers and reboots of the active processor card, the software transitions through a series of software redundancy states. Table 3-2 lists some of the significant software states.
Redundant Operation Requirements
For fully redundant operation, the following requirements must be met:
•Two processor cards are required.
•The processor cards must have identical hardware configurations. This includes variables such as DRAM size, and so on.
•Both processor cards must have the same functional image.
•Both processor cards must be running compatible system images. System images are compatible across one major release.
•Both the running and startup configurations are automatically synchronized between the processor cards.
•Both processor cards must be set to autoboot (a default setting).
If these requirements are met, the Cisco ONS 15540 runs in redundant mode by default. If they are not met, the system is conditionally redundant.
Note For detailed information on updating system images, refer to the Cisco ONS 15540 ESP Software Upgrade Guide .
Conditions Causing a Switchover from the Active Processor Card
The following conditions can cause a switchover from the active processor card to the standby processor card:
•The active processor card is removed or swapped. When the processor card functioning as the active processor card is removed, the standby processor card takes over. The Cisco ONS 15540 is nonredundant until a second processor card is inserted.
•The active processor card is rebooted. When a processor card functioning as the active processor card is rebooted, it relinquishes its active role if the standby processor card has reached the hot-standby state.
•The active processor card fails. The standby processor card takes over as the active processor card, using the last synchronized running configuration file (or the last saved startup configuration file if the running configuration file synchronization was disabled or failed).
•A switchover is manually forced with the redundancy switch-activity command.
Configuring Processor Card Redundancy
This section describes how to configure processor card redundancy for your Cisco ONS 15540.
Note The initial default configuration will support processor card redundancy and database synchronization with no manual configuration required.
Forcing a Switchover from Privileged EXEC Mode
You can manually force the standby processor card to take over as the active processor card from privileged EXEC mode. To force a switchover from privileged EXEC mode, enter the following command on the active processor card CLI:
Command Purposeredundancy switch-activity [force]
Causes a processor card switchover. If the standby processor card has not reached the hot-standby software state, use the force option.
As long as you have not changed the default configuration register setting from autoboot, the standby processor card (formerly the active processor card) automatically boots until it reaches the hot-standby state.
Note Data transmission through the system is not affected by a processor card switchover.
Example
The following example shows how to manually cause a processor card switchover from privileged EXEC mode:
Switch# redundancy switch-activity
This will reload the active unit and force a switch of activity [confirm] y
Preparing to switch activity
00:12:05: %SYS-5-RELOAD: Reload requested
<Information deleted>
Forcing a Switchover from ROM Monitor Mode
You can manually force the standby processor card to take over as the active processor card ROM monitor mode. To force a switchover from ROM monitor mode, enter the following commands on the active processor card CLI:
Command Purposeswitchover
Causes a processor card reset and switchover. The processor card stays in ROM monitor mode.
m
Note Using the reset command in ROM monitor mode on the active processor CLI under normal conditions does not cause a switchover.
Example
The following example shows how to manually cause a processor card switchover from ROM monitor mode:
<Information deleted>
This CPU is ACTIVE (sev=0), peer CPU is NON-PARTICIPANT (sev=2)
MANHATTAN_OPTICAL platform with 131072 Kbytes of main memory
rommon 1 > switchover
System Bootstrap, Version 12.1(20010726:234219) [ffrazer-lh4 102], DEVELOPMENT S
OFTWARE
Copyright (c) 1994-1999 by cisco Systems, Inc.
Flash size is 16777216
Reset Reason Register = RESET_REASON_SW_NMI (0x4)
Reset type 0x2
Reading monitor variables from NVRAM
Running reset I/O devices
Enabling interrupts
Initializing TLB
Initializing cache
Initializing required TLB entries
Initializing main memory
SDRAM DIMM size 67108864
Sizing NVRAM
Initializing PCMCIA controller
Initializing SRC FPGA
CPU arbitration
This CPU is NON-PARTICIPANT (sev=2), peer CPU is ACTIVE (sev=0)
MANHATTAN_OPTICAL platform with 131072 Kbytes of main memory
rommon 1 >
Configuring Autoboot
If you have changed the default configuration register value from autoboot, you can change it back by performing the following steps, beginning in global configuration mode:
Command PurposeStep 1
Switch(config)# config-register 0x2102
Sets the configuration register for autoboot.1
Step 2
Switch(config)# boot system bootflash:filename
Sets the BOOT environment variable. This variable specifies the location and name of the system image file to use when automatically booting the system.
Step 3
Switch(config)# end
Switch#
Returns to privileged EXEC mode.
Step 4
Switch# copy system:running-config nvram:startup-config
Saves the configuration to NVRAM. The new configuration register value takes effect after the next system reload.
1 This is the default configuration register setting. For details on using the configuration register to set boot parameters, refer to the Cisco IOS Configuration Fundamentals Configuration Guide.
Note If the standby processor card remains in ROM monitor mode, you can manually boot the processor card using a system image either on the bootflash or on a Flash PC Card.
Example
The following example shows how to configure the Cisco ONS 15540 to autoboot using the first valid file on the Flash PC Card in slot 0:
Switch(config)# config-register 0x2102
Switch(config)# boot system flash slot0:
Switch(config)# end
Switch# copy system:running-config nvram:startup-config
Displaying the Autoboot Configuration
To display the configuration register value, use the following EXEC command:
Command Purposeshow version
Displays the configuration register value.
show bootvar
Displays the configuration register value.
Example
The following example shows the contents of the configuration register:
Switch# show version
Cisco Internetwork Operating System Software
IOS (tm) ONS-15540 Software (manopt-M0-M), Experimental Version 12.1(20010221:0]
Copyright (c) 1986-2001 by cisco Systems, Inc.
Compiled Tue 20-Feb-01 18:40 by lthanvan
Image text-base: 0x60010968, data-base: 0x604D8000
ROM: System Bootstrap, Version 12.1(20010204:232442) [vsankar-alarm_fix 106], DE
BOOTFLASH: M1540-ODS Software (manopt-M0-M), Experimental Version 12.1(20001229]
M1 uptime is 1 minute
System returned to ROM by power-on
System image file is "tftp://171.69.1.129//tftpboot/lthanvan/manopt-m0-mz"
cisco (QUEENS-CPU) processor with 98304K/32768K bytes of memory.
R7000 CPU at 234Mhz, Implementation 39, Rev 2.1, 256KB L2, 2048KB L3 Cache
Last reset from unexpected value
2 Ethernet/IEEE 802.3 interface(s)
509K bytes of non-volatile configuration memory.
16384K bytes of Flash internal SIMM (Sector size 64K).
Configuration register is 0x2102
The following example shows the contents of the boot variable:
Switch# show bootvar
BOOT variable = bootflash:ons15540-i-mz.1;
CONFIG_FILE variable =
BOOTLDR variable =
Configuration register is 0x2
Standby auto-sync startup config mode is on
Standby auto-sync running config mode is on
Synchronizing the Configurations
During normal operation, the startup and running configurations are synchronized by default between the two processor cards. In the event of a switchover, the new active processor card uses the current running configuration. Configurations are synchronized either manually from the CLI using the redundancy manual-sync command or automatically following configuration changes input from the CLI or from SNMP if automatic synchronization is enabled.
Synchronizing Configurations Manually
To immediately synchronize the configurations used by the two processor cards, use the following privileged EXEC command on the active processor card:
Command Purposeredundancy manual-sync {startup-config | running-config | both}
Immediately synchronizes the configuration.
Example
The following example shows how to manually synchronize the running configuration:
Switch# redundancy manual-sync running-config
Enabling and Disabling Automatic Synchronization
You can enable and disable automatic synchronization of the running configuration and the startup configuration between the two processor cards. Automatic synchronization ensures that, when a switchover occurs, the standby processor card has the most recent configuration information.
Note By default, the Cisco ONS 15540 automatically synchronizes the running configuration and the startup configuration between the two processor cards.
Table 3-3 lists the events that cause the automatic synchronization of the configuration files.
To enable or disable the system to automatically synchronize the configurations on both processor cards, perform the following steps on the active processor card, beginning in global configuration mode:
Example
The following example shows how to disable automatic synchronization of the running configuration:
Switch(config)# redundancy
Switch(config-red)# no auto-sync running-config
Switch(config-red)# end
Switch# copy system:running-config nvram:startup-config
Configuring Maintenance Mode
You can configure the Cisco ONS 15540 to enter the redundancy maintenance mode. Configuration synchronizations and standby processor card fault reporting are suppressed in maintenance mode. Upon exiting maintenance mode and reverting to redundant mode, the standby processor card is rebooted to bring it back to the hot-standby state.
Note When the system is in maintenance mode, switchovers only occur by entering the redundancy switch-activity force command, or physically removing the active processor card.
To configure maintenance mode, perform the following commands, beginning in global configuration mode:
Command PurposeSwitch(config)# redundancy
Switch(config-red)#
Enters redundancy configuration mode.
Switch(config-red)# maintenance-mode
Configures the system in maintenance mode.
Example
The following example shows how to configure redundancy maintenance mode:
Switch(config)# redundancy
Switch(config-red)# maintenance-mode
This command will place the system in SIMPLEX mode [comfirm] y
Displaying the Processor Card Redundancy Configuration and Status
To display the processor card redundancy configuration and status, use the following privileged EXEC commands:
Examples
The following example shows the processor card redundancy configuration and status:
Switch# show redundancy
Redundant system information
----------------------------
Available Uptime: 3 days, 4 hours, 35 minutes
Time since last switchover: 10 hours, 30 minutes
Switchover Count: 1
Inter-CPU Communication State:UP
Last Restart Reason: Switch over
Software state at switchover: ACTIVE
Last Running Config sync: 2 hours, 18 minutes
Running Config sync status: In Sync
Last Startup Config sync: 6 hours, 4 minutes
Startup Config sync status: In Sync
This CPU is the Active CPU.
-------------------------------
Slot: 7
Time since CPU Initialized: 22 hours, 33 minutes
Image Version: ONS-15540 Software(ONS15540-I-M),...
Image File: bootflash:ons15540-i-mz.010727
Software Redundancy State: ACTIVE
Hardware State: ACTIVE
Hardware Severity: 0
Peer CPU is the Standby CPU.
-------------------------------
Slot: 6
Time since CPU Initialized: 10 hours, 29 minutes
Image Version: ONS-15540 Software(ONS15540-I-M),...
Image File (on sby-CPU): bootflash:ons15540-i-mz.010727
Software Redundancy State: STANDBY HOT
Hardware State: STANDBY
Hardware Severity: 0
The following example shows the processor card capabilities:
Switch# show redundancy capability
CPU capability support
Active CPU Sby CPU Sby Compat CPU capability description
---------- ---------- ----------- ----------------------------------------
96 MB 96 MB OK CPU DRAM size
32 MB 32 MB OK CPU PMEM size
512 KB 512 KB OK CPU NVRAM size
16 MB 16 MB OK CPU Bootflash size
2.1 2.1 OK CPU hardware major.minor version
1.11 1.11 OK CPU functional major.minor version
Linecard driver major.minor versions, (counts:Active=18, Standby=18)
Active CPU Sby CPU Sby Compat Drv ID Driver description
---------- ---------- ----------- ------ -----------------------------------
1.1 1.1 OK 0x1000 CPU w/o Switch Fabric
1.1 1.1 OK 0x1001 Fixed Transponder, w/monitor
1.1 1.1 OK 0x1002 Fixed Transponder, no monitor
1.1 1.1 OK 0x1003 Pluggable Transponder, w/monitor
1.1 1.1 OK 0x1004 Pluggable Transponder, no monitor
1.1 1.1 OK 0x1005 Line Card Motherboard
1.1 1.1 OK 0x1006 Backplane
Active CPU Sby CPU Sby Compat Drv ID Driver description
---------- ---------- ----------- ------ -----------------------------------
1.1 1.1 OK 0x1007 32-ch Mux/Demux
1.1 1.1 OK 0x1008 Fixed 4-ch Mux/Demux, no OSC
1.1 1.1 OK 0x1009 Fixed 8-ch Mux/Demux, no OSC
1.1 1.1 OK 0x100A Modular 4-ch Mux/Demux, no OSC
1.1 1.1 OK 0x100B Modular 8-ch Mux/Demux, no OSC
1.1 1.1 OK 0x100C 32-ch Array Wave Guide
1.1 1.1 OK 0x100D Mux/Demux Motherboard
1.1 1.1 OK 0x100E Modular 4-ch Mux/Demux plus OSC
1.1 1.1 OK 0x100F Modular 8-ch Mux/Demux plus OSC
1.1 1.1 OK 0x1010 Mux-Demux Motherboard, no OSC
1.1 1.1 OK 0x1011 Line Card Motherboard, no splitter
Software sync client versions, listed as version range X-Y.
X indicates the oldest peer version it can communicate with.
Y indicates the current sync client version.
Sync client counts:Active=2, Standby=2
Active CPU Sby CPU Sby Compat Cl ID Redundancy Client description
---------- ---------- ----------- ----- ------------------------------------
ver 1-1 ver 1-1 OK 17 CPU Redundancy
ver 1-1 ver 1-1 OK 6 OIR Client
The following example shows how to display the running configuration file on the standby processor card:
sby-Switch# show redundancy running-config-file
!
version 12.1
no service pad
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
no service dhcp
!
hostname Switch
<Information deleted>
Reloading the Processor Cards
To reload one or both of the processor cards, use the following privileged EXEC commands on the active processor card CLI:
Command Purposeredundancy reload peer
Reloads the standby processor card.
redundancy reload shelf
Reloads both processor cards in the shelf.
Example
The following example shows how to reload the standby processor card:
Switch# redundancy reload peer
Reload peer [confirm] y
Preparing to reload peer
About Fan Failure Shutdown
The Cisco ONS 15540 fan assembly is located at the bottom of the chassis and contains eight individual fans and a fan controller board. The controller board monitors the status of each fan and reports the status to the processor cards.
If a single fan fails, a minor alarm is reported to the processor card. However, the chassis will never reach a critical high temperature when only one fan fails.
If two or more fans fail, a major alarm is reported to the processor card.
If all eight fans in the fan tray fail, the chassis will reach critical temperature after 14 minutes.
To prevent damage to the cards and modules in the shelf when two or more fans fail, you can configure the system to automatically reset or power off the transponder modules. The transponder modules power off if the hardware version of the line card motherboard is 5.1 or later; otherwise, the transponder modules reset. Use the show hardware command to determine the hardware version of the 2.5-Gbps line card motherboards.
To recover from fan failure shutdown, you must power-cycle the shelf.
Caution Do not save the startup configuration file after the line modules shutdown. This action would result in losing the previous startup configuration.
Caution The fan failure shutdown feature disrupts traffic on the shelf when two or more fans fail.
Configuring Fan Failure Shutdown
To configure the system to automatically shut down when two or more fans fail, use the following global configuration command:
Note The system will start powering off or resetting the transponder modules about 2 minutes after detecting that two or more fans have failed.
Example
The following example shows how to enable fan tray failure shutdown:
Switch(config)# environment-monitor shutdown fan
Displaying the Fan Tray Failure Shutdown Configuration
To display the fan tray failure shutdown configuration, use the following EXEC command:
Example
The following example shows how to display the fan tray failure shutdown feature configuration:
Switch# show environment
Fan
---
Status: Total Failure
Line card shutdown on fan failure:enabled
Sensor Temperature Thresholds
(degree C) Minor Major Critcal Low
-------------------- ----------- ------------------------------------
Inlet Sensor 28 65 75 80 -15
Outlet Sensor 28 75 85 90 -15
Sensor Alarms
Min
Critical
-------------------- ------------------------
Inlet Sensor 0 0 0
Outlet Sensor 0 0 0
Power Entry Module 0 type DC status: OK
Posted: Thu Jul 15 11:15:20 PDT 2004
All contents are Copyright © 1992--2004 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.