Table of Contents

Automatic Shutdown

Verifying Hardware Installation

Monitoring Hardware Using Alarms

Configuring the Common Criteria Tcl Scripts

Monitoring the Control Plane

Performing File System Cleanups

Upgrading System Software

Performing Factory Reset

Preface

Automatic Shutdown

Under certain conditions, the Cisco ASR 1000 Series Aggregation Services Router or one of its power supplies can perform an automatic shutdown.

This chapter includes the following sections:

- Automatic Router Shutdown

- Automatic Power Supply Shutdown

- For More Information

Automatic Router Shutdown

When the router detects a condition that could result in physical damage to system components, the router can shut down without operator intervention. When the router shuts down automatically, the system controller disables DC power to all internal components. All DC power remains disabled until you toggle the power switch.

The default for automatic router shutdown is off. To allow automatic router shutdown, the facility-alarm critical exceed-action shutdown command must be enabled. If the facility-alarm critical exceed-action shutdown command is enabled, the router performs an automatic shutdown under the following conditions:

- Internal Temperature of Router or Power Supply Exceeds Temperature Threshold

- Voltage of AC or DC Power Supplies Is Out of Tolerance

- Automatic Power Supply Shutdown

Internal Temperature of Router or Power Supply Exceeds Temperature Threshold

A temperature threshold is exceeded if any of the following conditions occur:

- The internal temperature of the router (the ambient air temperature on the active Cisco ASR 1000 Series Route Processor) is over 100° C.

- The internal temperature of the AC power supply is over 100° C.

- The internal temperature of the DC power supply is over 100° C.

Note Temperature threshold values cannot be configured or changed.

Voltage of AC or DC Power Supplies Is Out of Tolerance

The voltage of a power supply must be within certain ranges (within tolerance). A power supply is out of tolerance if voltage is outside of the following ranges:

- AC input range: 85 VAC to 264 VAC

- DC input range: –40.5 VDC to –72 VDC

Note Voltage tolerance ranges cannot be configured or changed.

Automatic Power Supply Shutdown

Automatic power supply shutdown occurs independently of a router shutdown. If the internal temperature of a power supply exceeds 100° C, the power supply shuts down immediately. The facility-alarm critical exceed-action shutdown command does not need to be enabled.

Each power supply fail safe is independent of the other and independent of the router. The fans in the power supplies continue to operate as long as the second power entry module (PEM) is powering the system.

For More Information

Topic

Document

Command descriptions

Cisco IOS Master Command List, All Releases

Command Lookup Tool (Requires Cisco.com user ID and password)

Environmental monitoring and reporting

Verifying Hardware Installation

After installing the Cisco ASR 1000 Series Aggregation Services Router or replacing any of its hardware components that are field-replaceable units (FRUs), verify the installation.

This chapter includes the following sections:

- Checking the LEDs

- Checking Status Using show Commands

- When Installation Is Not Successful

- For More Information

Checking the LEDs

Check the LEDs on the faceplates of the following FRUs:

- Cisco ASR 1000 Series Route Processors

- Cisco ASR 1000 Series Embedded Services Processors

- Cisco ASR 1004 Router, Cisco ASR 1006 Router

- Shared Port Adapters

- Cisco ASR 1001 Built-in Gigabit Ethernet SPA LEDs

Cisco ASR 1000 Series Route Processors

Route processor LEDs vary according to the chassis model, as described in the following sections.

Cisco ASR 1013 Router

Table 1-1 shows the color or state of the LEDs in the Cisco ASR 1000 Series Route Processor-2 (RP-2) that indicate a successful installation. Figure 1-1 shows a view of the LEDs on the faceplate.

Note Only Route Processor-2 (RP-2) and ESP-40 (Embedded Service Processor) are supported for installation on the Cisco ASR 1013 Router.

Table 1-1 RP-2 Faceplate LEDs Indicating a Successful Installation (Cisco ASR 1013 Router)

LED Label

Color—State

Description

PWR

Solid green

All power requirements are within specification

Off

Off indicates that the router is in standby mode.

STAT

Solid green

Cisco IOS has successfully booted.

Yellow

BOOT ROM has successfully loaded.

Red

System failure.

ACTV

Green

Lit when this is the active ASR 1000 Series route processor (Cisco ASR1000-RP1 or Cisco ASR1000-RP2).

STBY

Yellow

Lit when this is the standby ASR 1000 Series route processor.

CRIT

Solid red

Critical alarm indicator. This is on at power up, turned off by software.

MAJ

Solid red

Major alarm indicator.

MIN

Amber

Minor alarm indicator.

DISK HD

Flashing green

Active indicator.

Off

No activity.

DISK USB

Flashing green

Active indicator.

Off

No activity.

DISK BF

Flashing green

Active indicator.

Off

No activity.

Figure 1-1 RP-2 Faceplate LEDs for an Active RP (Cisco ASR 1013 Router)

Cisco ASR 1001 Router

The Cisco ASR 1001 Router faceplate has common components for each type of ASR 1001 Router configuration. Figure 1-2 shows the Cisco ASR1000 front panel LEDs of the Cisco ASR 1001 Router. Table 1-2 shows the color or state of the LEDs in the Cisco ASR 1001 Series Router.

Figure 1-2 Common LEDs for Cisco ASR 1001 Router

Table 1-2 Cisco ASR 1001 LED Color or State Details

LED Label

Color—State

Description

PWR

Solid green

Power requirements are within specification.

STAT

Solid green

Cisco IOS booted successfully.

MIN

Off

No minor alarms.

MAJ

Off

No major alarms.

CRIT

Off

No critical alarms.

BF

Green

Indicates activity of the EUSB device

Link

Green

Solid Green indicates Link, Flashing green indicates MGMT Ethernet port activity.

USB

Green

USB is green and flashes when accessed.

Cisco ASR 1004 Router, Cisco ASR 1006 Router

Table 1-3 shows the color or state of the LEDs in the Cisco ASR 1000 Series Route Processor (RP) that indicate a successful installation. Figure 1-3 shows a view of the LEDs on the faceplate.

Table 1-3 RP LEDs Indicating a Successful Installation (Cisco ASR 1004 Router, Cisco ASR 1006 Router)

LED Label

Color—State

Description

PWR

Solid green

Power requirements are within specification.

STAT

Solid green

Cisco IOS booted successfully.

ACTV

Green

Active RP.

STBY

Yellow

Standby RP.

CRIT

Off

No critical alarms.

MAJ

Off

No major alarms.

MIN

Off

No minor alarms.

Figure 1-3 RP Faceplate LEDs for an Active RP (Cisco ASR 1004 Router, Cisco ASR 1006 Router)

Cisco ASR 1002 Router

Table 1-4 shows the color or state of the LEDs in the Cisco ASR 1000 Series Route Processor (RP) that indicate a successful installation. Figure 1-4 shows a view of the LEDs on the faceplate.

Table 1-4 RP LEDs Indicating a Successful Installation (Cisco ASR 1002 Router)

LED Label

Color—State

Description

pwr

Solid green

Power requirements are within specification.

stat

Solid green

Cisco IOS booted successfully.

min

Off

No minor alarms.

maj

Off

No major alarms.

crit

Off

No critical alarms.

Figure 1-4 RP Faceplate LEDs for an Active RP (Cisco ASR 1002 Router)

Cisco ASR 1000 Series Embedded Services Processors

Table 1-5 shows the color or state of the LEDs in the Cisco ASR 1000 Series Embedded Services Processor (ESP) that indicate a successful installation. Figure 1-5 shows a view of the LEDs on the faceplate.

Table 1-5 ESP LEDs Indicating a Successful Installation

LED Label

Color—State

Description

PWR

Solid green

Power requirements are within specification.

STAT

Solid green

Cisco IOS booted successfully.

ACTV

Green

Active ESP.

STBY

Yellow

Standby ESP.

Figure 1-5 ESP Faceplate LEDs for an Active ESP

Cisco ASR 1013 Router

Table 1-6 shows the color or state of the LEDs in the Cisco ASR 1000 Series SPA Interface Processors (SIP) that indicate a successful installation. Figure 1-6 shows a view of the LEDs on the faceplate.

Table 1-6 SIP LEDs Indicating a Successful Installation (Cisco ASR 1013 Router)

LED Label

Color—State

Description

PWR

Solid green

SIP is powered on.

STATUS

Solid green

SIP is online.

In the Cisco ASR 1013 Router, each Cisco ASR1000- SIP40 supports:

- Up to 6 ASR1000-SIP40G SIPs.

- Each SIP-40G supports:

– Four half-height (¼ Rate or full rate or combination) SPAs with up to 24 ports per SPA

– Two full-height (¼ Rate or full rate or combination) SPAs with up to 48 ports per SPA

– Two half-height and 1 full-height combination that does not exceed 96 ports

Note If ASR-SIP10 is inserted in slot 0 to 5 of a Cisco ASR 1013 Router then you need to upgrade CPLD and ROMMON. If ASR-SIP40 is inserted in slot 4 or 5, it behaves like the ASR-SIP10.

Figure 1-6 SIP Faceplate LEDs (Cisco ASR 1013 Router)

Cisco ASR 1004 Router, Cisco ASR 1006 Router

Table 1-7 shows the color or state of the LEDs in the Cisco ASR 1000 Series SPA Interface Processors (SIP) that indicate a successful installation. Figure 1-7 shows a view of the LEDs on the faceplate.

Table 1-7 SIP LEDs Indicating a Successful Installation (Cisco ASR 1004 Router, Cisco ASR 1006 Router)

LED Label

Color—State

Description

PWR

Solid green

SIP is powered on.

STATUS

Solid green

SIP is online.

Figure 1-7 SIP Faceplate LEDs (Cisco ASR 1004 Router, Cisco ASR 1006 Router)

Cisco ASR 1002 Router

Table 1-8 shows the color or state of the LEDs in the Cisco ASR 1000 Series SPA Interface Processors (SIP) that indicate a successful installation. Figure 1-8 shows a view of the LEDs on the faceplate.

Table 1-8 SIP LEDs Indicating a Successful Installation (Cisco ASR 1002 Router)

LED Label

Color—State

Description

PWR

Solid green

SIP is powered on.

STAT

Solid green

SIP is online.

Figure 1-8 SIP Faceplate LEDs (Cisco ASR 1002 Router)

Shared Port Adapters

Table 1-9 shows the color or state of the LED the shared port adapter (SPA) that indicates a successful installation. Figure 1-9 shows a view of the LED on the faceplate.

Table 1-9 SPA LED Indicating a Successful Installation

LED Label

Color—State

Description

STATUS

Solid green

SPA is powered on and is operational.

Figure 1-9 SPA Faceplate LED

Cisco ASR 1001 Built-in Gigabit Ethernet SPA LEDs

The Cisco ASR 1001 Router has a Built-in Gigabit Ethernet SPA, which is installed. Table 1-10 shows the Built-in SPA LEDs details.

Table 1-10 Cisco ASR 1001 Router Built-in Gigabit Ethernet SPA Successful Installation

LED Label

Color—State

Description

GE SFP STATUS

Amber or Green

Off indicates port is not enabled by software.

Amber indicates the port is enabled by software, but Ethernet Link is not yet established.

Green indicates the port is enabled by software and that an Ethernet Link has been established.

AC and DC Power Supplies

Table 1-11 shows the color or state of the LEDs that indicate a successful installation. Figure 1-10 shows a view of the LEDs on the faceplate.

Table 1-11 AC and DC Power Supply LEDs Indicating a Successful Installation

LED Label

Color—State

Description

INPUT OK

Green

Input voltage is within normal operating range.

FAN OK

Green

All fans are operational.

OUTPUT FAIL

Off

Output voltage is within normal operating range.

Figure 1-10 AC and DC Power Supply Faceplate LEDs

Checking Status Using show Commands

Use the show platform and show environment all commands to check the online and environmental status of each FRU after installation.

The show platform command displays the online status information for router FRUs. The State column in show platform command output should display “ok” for SIPs, SPAs, power supplies, and fans. For RPs (shown as R0, R1) and ESPs (shown as F0, F1), the State column should display “ok, active” or “ok, standby.”

Note There is only one LED for each Power Supply on Cisco ASR 1001 Router and it is green when powered-up.

Router# show platform

Chassis type: ASR1001

Slot Type State Insert time (ago)

--------- ------------------- --------------------- -----------------

0 ASR1001 ok 23:28:16

0/0 4XGE-BUILT-IN ok 23:27:23

0/1 SPA-2XOC12-POS ok 23:27:21

0/2 ASR1001-IDC-4XGE ok 23:27:23

R0 ASR1001 ok 23:28:16

R0/0 ok, active 23:28:16

F0 ASR1001 ok, active 23:28:16

P0 Unknown ps, fail never

P1 ASR1001-PWR-AC ok 23:27:50

P2 ASR1001-FANTRAY ok 23:27:51

Slot CPLD Version Firmware Version

--------- ------------------- ---------------------------------------

0 0902010A 12.2(20090526:143323) [gschnorr-mcp_...

R0 09020110 12.2(20090526:143323) [gschnorr-mcp_...

F0 0902010A 12.2(20090526:143323) [gschnorr-mcp_...

Router# show platform

Chassis type: ASR1013

Slot Type State Insert time (ago)

--------- ------------------- --------------------- -----------------

0 ASR1000-SIP10 ok 1w0d

1 ASR1000-SIP40 ok 1w0d

1/1 SPA-5X1GE-V2 ok 1w0d

2 ASR1000-SIP40 ok 1w0d

2/1 SPA-1X10GE-L-V2 ok 1w0d

2/3 SPA-1X10GE-L-V2 ok 1w0d

3 ASR1000-SIP40 ok 1w0d

3/3 SPA-4XT3/E3 ok 1w0d

4 ASR1000-SIP40 ok 1w0d

4/2 SPA-5X1GE-V2 ok 1w0d

4/3 SPA-4XCT3/DS0 ok 1w0d

5 ASR1000-SIP40 ok 1w0d

R0 ASR1000-RP2 ok, active 1w0d

R1 ASR1000-RP2 ok, standby 1w0d

F0 ASR1000-ESP40 ok, active 1w0d

F1 ASR1000-ESP40 ok, standby 1w0d

P0 ASR1013-PWR-AC ok 1w0d

P1 ASR1013-PWR-AC ps, fail 1w0d

P2 ASR1013-PWR-AC ok 1w0d

P3 ASR1013-PWR-AC ps, fail 1w0d

Slot CPLD Version Firmware Version

--------- ------------------- ---------------------------------------

0 00200800 15.0(1r)S

1 00200800 15.0(1r)S

2 00200800 15.0(1r)S

3 00200800 15.0(1r)S

4 00200800 15.0(1r)S

5 00200800 15.0(1r)S

R0 10021901 15.0(1r)S

R1 10021901 15.0(1r)S

F0 1001270D 15.0(1r)S

F1 1001271D 15.0(1r)S

Router# show platform

Chassis type: ASR1006

Slot Type State Insert time (ago)

--------- ------------------- --------------------- -----------------

0 ASR1000-SIP10 ok 18:23:58

0/0 SPA-5X1GE-V2 ok 18:22:38

0/1 SPA-8X1FE-TX-V2 ok 18:22:33

0/2 SPA-2XCT3/DS0 ok 18:22:38

1 ASR1000-SIP10 ok 18:23:58

1/0 SPA-2XOC3-POS ok 18:22:38

1/1 SPA-8XCHT1/E1 ok 18:22:38

1/2 SPA-2XT3/E3 ok 18:22:38

R0 ASR1000-RP1 ok, active 18:23:58

F0 ASR1000-ESP10 ok, active 18:23:58

P0 ASR1006-PWR-AC ok 18:23:09

P1 ASR1006-FAN ok 18:23:09

Slot CPLD Version Firmware Version

--------- ------------------- ---------------------------------------

0 06120701 12.2(33r)XN2

1 06120701 12.2(33r)XN2

R0 07082312 12.2(33r)XN2

F0 07051680 12.2(33r)XN2

The show environment all command displays system temperature, voltage, fan, and power supply conditions. (It does not display environmental information for SPAs.) The State column in show environment all output should show “Normal,” except for fans where it indicates fan speed. A fan speed of 65% is normal.

Router# show environment all

Sensor List: Environmental Monitoring

Sensor Location State Reading

V1: VMA F0 Normal 1801 mV

V1: VMB F0 Normal 1206 mV

V1: VMC F0 Normal 1206 mV

V1: VMD F0 Normal 1103 mV

V1: VME F0 Normal 1005 mV

V1: 12v F0 Normal 11967 mV

V1: VDD F0 Normal 3295 mV

V1: GP1 F0 Normal 905 mV

V2: VMA F0 Normal 3295 mV

V2: VMB F0 Normal 2495 mV

V2: VMC F0 Normal 1499 mV

V2: VMD F0 Normal 1098 mV

V2: VME F0 Normal 1000 mV

V2: VMF F0 Normal 1000 mV

V2: 12v F0 Normal 11923 mV

V2: VDD F0 Normal 3295 mV

V2: GP1 F0 Normal 751 mV

Temp: Inlet F0 Normal 27 Celsius

Temp: Asic1 F0 Normal 44 Celsius

Temp: Exhaust1 F0 Normal 36 Celsius

Temp: Exhaust2 F0 Normal 34 Celsius

Temp: Asic2 F0 Normal 40 Celsius

V1: VMA 0 Normal 1103 mV

V1: VMB 0 Normal 1201 mV

V1: VMC 0 Normal 1503 mV

V1: VMD 0 Normal 1801 mV

V1: VME 0 Normal 2495 mV

V1: VMF 0 Normal 3295 mV

V1: 12v 0 Normal 11967 mV

V1: VDD 0 Normal 3295 mV

V1: GP1 0 Normal 751 mV

V1: GP2 0 Normal 903 mV

V2: VMB 0 Normal 1201 mV

V2: 12v 0 Normal 11967 mV

V2: VDD 0 Normal 3291 mV

V2: GP2 0 Normal 903 mV

Temp: Left 0 Normal 28 Celsius

Temp: Center 0 Normal 29 Celsius

Temp: Asic1 0 Normal 42 Celsius

Temp: Right 0 Normal 27 Celsius

V1: VMA 1 Normal 1103 mV

V1: VMB 1 Normal 1201 mV

V1: VMC 1 Normal 1503 mV

V1: VMD 1 Normal 1801 mV

V1: VME 1 Normal 2495 mV

V1: VMF 1 Normal 3295 mV

V1: 12v 1 Normal 11953 mV

V1: VDD 1 Normal 3291 mV

V1: GP1 1 Normal 754 mV

V1: GP2 1 Normal 903 mV

V2: VMB 1 Normal 1206 mV

V2: 12v 1 Normal 11967 mV

V2: VDD 1 Normal 3291 mV

V2: GP2 1 Normal 905 mV

Temp: Left 1 Normal 28 Celsius

Temp: Center 1 Normal 30 Celsius

Temp: Asic1 1 Normal 44 Celsius

Temp: Right 1 Normal 28 Celsius

PEM Iout P0 Normal 37 A

PEM Vout P0 Normal 12 V AC

PEM Vin P0 Normal 116 V AC

Temp: PEM P0 Normal 28 Celsius

Temp: FC P0 Fan Speed 65% 25 Celsius

Temp: FM P1 Normal 1 Celsius

Temp: FC P1 Fan Speed 65% 25 Celsius

V1: VMA R0 Normal 1118 mV

V1: VMB R0 Normal 3315 mV

V1: VMC R0 Normal 2519 mV

V1: VMD R0 Normal 1811 mV

V1: VME R0 Normal 1513 mV

V1: VMF R0 Normal 1220 mV

V1: 12v R0 Normal 12011 mV

V1: VDD R0 Normal 3300 mV

V1: GP1 R0 Normal 913 mV

V1: GP2 R0 Normal 1247 mV

Temp: CPU R0 Normal 29 Celsius

Temp: Outlet R0 Normal 30 Celsius

Temp: Inlet R0 Normal 25 Celsius

Temp: Asic1 R0 Normal 30 Celsius

The show environment all command output shows an example of one power supply in the Cisco ASR 1001 Router:

Router# show environment all

Sensor List: Environmental Monitoring

Sensor Location State Reading

PEM Iout P1 Normal 13 A

PEM Vout P1 Normal 12 V AC

PEM Vin P1 Normal 231 V AC

Temp: Inlet P1 Normal 27 Celsius

Temp: Internal P1 Normal 35 Celsius

V1: VMA R0 Normal 3295 mV

V1: VMB R0 Normal 1000 mV

V1: VMC R0 Normal 2495 mV

V1: VMD R0 Normal 2460 mV

V1: VME R0 Normal 1201 mV

V1: VMF R0 Normal 1796 mV

V1: 12v R0 Normal 11967 mV

V1: VDD R0 Normal 4970 mV

V1: GP1 R0 Normal 1201 mV

V1: GP2 R0 Normal 903 mV

V2: VMA R0 Normal 1098 mV

V2: VMB R0 Normal 1000 mV

V2: VMC R0 Normal 1499 mV

V2: VMD R0 5% high 1206 mV

V2: VME R0 Normal 1098 mV

V2: VMF R0 Normal 1054 mV

V2: 12v R0 Normal 11953 mV

V2: VDD R0 Normal 4985 mV

V2: GP1 R0 5% high 812 mV

V2: GP2 R0 20% low 2497 mV

Temp: Middle R0 Normal 54 Celsius

Temp: CPU Die R0 Normal 46 Celsius

Temp: Top Left R0 Normal 44 Celsius

Temp: Asic1 R0 Normal 67 Celsius

Temp: Inlet R0 Normal 35 Celsius

Temp: Asic3 R0 Normal 65 Celsius

Temp: Rear R0 Minor 60 Celsius

Temp: Asic2 R0 Normal 60 Celsius

Temp: Mid Frnt R0 Normal 50 Celsius

Temp: MCH Die R0 Normal 70 Celsius

Temp: FC R0 Fan Speed 65% 35 Celsius

To display the Field Programmable Devices (FPD) on Cisco ASR 1001 Router, use the show hw-module all fpd command:

Router# show hw-module all fpd

==== ====================== ====== =============================================

H/W Field Programmable Current Min. Required

Slot Card Type Ver. Device: "ID-Name" Version Version

==== ====================== ====== ================== =========== ==============

0/0 4XGE-BUILT-IN 1.0 1-GE I/O FPGA 1.10 1.10

---- ---------------------- ------ ------------------ ----------- --------------

0/1 SPA-2XOC12-POS 1.0 1-I/O FPGA 1.1 1.1

---- ---------------------- ------ ------------------ ----------- --------------

0/2 ASR1001-IDC-4XGE 1.1 1-GE I/O FPGA 1.10 1.10

==== ====================== ====== =============================================

To display the Field Programmable Devices (FPD) on Cisco ASR 1013 Router, use the show hw-module all fpd command:

Router# show hw-module all fpd

==== ====================== ====== =============================================

H/W Field Programmable Current Min. Required

Slot Card Type Ver. Device: "ID-Name" Version Version

==== ====================== ====== ================== =========== ==============

4/2 SPA-2CHT3-CE-ATM 1.0 3-SPAMON 1.4 1.4

6-IOFPGA 2.25 2.25

9-UFE 1.10 1.10

---- ---------------------- ------ ------------------ ----------- --------------

5/0 SPA-5X1GE-V2 1.2 1-GE I/O FPGA 1.10 1.10

---- ---------------------- ------ ------------------ ----------- --------------

5/1 SPA-8X1GE-V2 1.1 1-GE I/O FPGA 1.10 1.10

---- ---------------------- ------ ------------------ ----------- --------------

5/2 SPA-4XT3/E3 1.1 1-ROMMON 2.12 2.12

2-I/O FPGA 1.1 1.1

3-E3 FPGA 1.4 1.4

4-T3 FPGA 1.4 1.4

==== ====================== ====== =============================================

When Installation Is Not Successful

This section discusses the following items to check or troubleshoot when installation is not successful:

- Physical Connections

- Mechanical Damage

- Alarm LED Is Illuminated

- Status LED Remains Amber

- LEDS Are Not Illuminated on a Power Supply

Physical Connections

Rule out an easily-fixed physical connection problem by verifying that:

- Power supplies are plugged in and switched on.

- Cables are connected.

- All FRUs are seated correctly.

Mechanical Damage

Examples of mechanical damage are a bent flange on a power supply or bent pins on a connector. If you detect mechanical damage:

- Do not attempt to straighten pins or repair mechanical damage.

- If you can see damaged pins, do not attempt to insert an assembly (SPA, SIP, ESP, or RP) into any slot. Doing so can damage the assembly or the chassis.

- Return the damaged equipment.

Alarm LED Is Illuminated

If the CRIT, MAJ, or MIN alarm LED is illuminated, determine the cause of the alarm by doing one of the following:

- Review the alarm message. The logging alarm command must be enabled for the system to send alarm messages to the console. The following is an example of an alarm message that was generated when a SPA was removed without a graceful deactivation of the SPA:

*Aug 22 13:27:33.774: %ASR1000_OIR-6-REMSPA: SPA removed from subslot 1/1, interfaces disabled

*Aug 22 13:27:33.775: %SPA_OIR-6-OFFLINECARD: SPA (SPA-4XT-SERIAL) offline in subslot 1/1

- Enter the show facility-alarm status command. The following example shows a critical alarm that is generated when a SPA is removed fr om the system:

Router# show facility-alarm status

System Totals Critical: 1 Major: 0 Minor: 0

Source Severity Description [Index]

------ -------- -------------------

subslot 1/1 CRITICAL Active Card Removed OIR Alarm [0]

Note A critical alarm "Active Card Removed OIR Alarm" is generated even if a SPA is removed after performing graceful deactivation.

Status LED Remains Amber

As Cisco IOS boots on a FRU, the status LED is amber or yellow. When Cisco IOS has successfully booted, the status LED becomes solid green.

If the status LED remains amber or yellow, check the console for alarm messages. The logging alarm command must be enabled for the system to send alarm messages to the console.

If there is no information on the console, some setting or error is not allowing Cisco IOS to boot. Contact Cisco Support; it is possible you might need to replace the FRU.

LEDS Are Not Illuminated on a Power Supply

DC Power Supply

If LEDs are not illuminated on the DC power supply, many times the problem is reversed polarity. Check the DC input power supply to see if the positive and negative lead wires are swapped.

AC Power Supply

If LEDs are not illuminated on the AC power supply, there is no input power or the power cord is not fully seated. If the power cord is fully seated, check the input power.

For More Information

For more information about the topics discussed in this chapter, see the following documents:

Topic

Document

Command descriptions

Cisco IOS Master Command List, All Releases

Command Lookup Tool (Requires Cisco.com user ID and password)OL-17665-04

Graceful Deactivation of a SIP or SPA: Online insertion and removal (OIR)

“Installing and Removing a SIP” chapter in the

Cisco ASR 1000 Series Aggregation Services Routers SIP and SPA Hardware Installation Guide

LEDs for the RP, ESP, SIP, and AC and DC power supplies

“Cisco ASR 1000 Series Routers Components Overview” chapter in the Cisco ASR 1000 Series Router Hardware Installation Guide

LEDs for the SIP and SPA

Cisco ASR 1000 Series Aggregation Services Routers SIP and SPA Hardware Installation Guide

Cisco ASR 1001 Router Quick-Start

Cisco ASR 1001 Router Quick Start Guide

Overview, Installation, and Detailed information of Cisco ASR 1001 Router

Cisco ASR 1000 Series Router Hardware Installation Guide

Cisco ASR 1013 Router Quick-Start

Cisco ASR 1013 Router Quick Start Guide

Monitoring Hardware Using Alarms

Once hardware is installed and operational, use alarms to monitor hardware status on a daily basis.

This chapter includes the following sections:

- Router Design and Monitoring Hardware

- Approaches for Monitoring Hardware Alarms

- For More Information

Router Design and Monitoring Hardware

The Cisco ASR 1000 Series Aggregation Services Routers are designed to send alarm notifications when problems are detected. Network administrators do not need to use show commands to poll devices on a routine basis and can monitor the network remotely. However, network administrators can perform onsite monitoring if they so choose.

Approaches for Monitoring Hardware Alarms

The following sections discuss ways in which you can monitor hardware using alarms:

- Onsite Network Administrator Responds to Audible or Visual Alarms

- Network Administrator Checks Console or Syslog for Alarm Messages

- Network Management System Alerts Network Administrator When an Alarm Is Reported Through SNMP

Onsite Network Administrator Responds to Audible or Visual Alarms

An external element can be connected to a power supply using the DB-25 alarm connector on the power supply. The external element is a DC lightbulb for a visual alarm and a bell for an audible alarm.

If an alarm illuminates the CRIT, MIN, or MAJ LED on the Cisco ASR 1000 Series Route Processor (RP) faceplate, and a visual or audible alarm is wired, the alarm also activates an alarm relay in the power supply DB-25 connector (on the Cisco ASR 1006 Router and Cisco ASR 1004 Router). The bell rings or the lightbulb flashes.

Clearing Audible and Visual Alarms

To clear an audible alarm, do one of the following:

- Press the Audible Cut Off button on the RP faceplate.

- Enter the clear facility-alarm command.

To clear a visual alarm, you must resolve the alarm condition. The clear facility-alarm command does not clear an alarm LED on the RP faceplate or turn off the DC lightbulb. For example, if a critical alarm LED is illuminated because an active SPA was removed without a graceful deactivation of the SPA, the only way to resolve that alarm is to replace the SPA.

Network Administrator Checks Console or Syslog for Alarm Messages

The network administrator can monitor alarm messages by reviewing alarm messages sent to the system console or to a syslog. This section discusses the following topics:

- Enabling the logging alarm Command

- Examples of Alarm Messages

- Reviewing and Analyzing Alarm Messages

Enabling the logging alarm Command

The logging alarm command must be enabled for the system to send alarm messages to a logging device, such as the console or a syslog. This command is not enabled by default.

Examples of Alarm Messages

The following alarm messages are examples of alarm messages that are sent to the console when a SPA is removed without first doing a graceful deactivation of the SPA. The alarm is cleared when the SPA is re-inserted.

SPA REMOVED

*Aug 22 13:27:33.774: %ASR1000_OIR-6-REMSPA: SPA removed from subslot 1/1, interfaces disabled

*Aug 22 13:27:33.775: %SPA_OIR-6-OFFLINECARD: SPA (SPA-4XT-SERIAL) offline in subslot 1/1

SPA RE-INSERTED

*Aug 22 13:32:29.447: %ASR1000_OIR-6-INSSPA: SPA inserted in subslot 1/1

*Aug 22 13:32:34.916: %SPA_OIR-6-ONLINECARD: SPA (SPA-4XT-SERIAL) online in subslot 1/1

*Aug 22 13:32:35.523: %LINK-3-UPDOWN: SIP1/1: Interface EOBC1/1, changed state to up

ALARMS For Cisco ASR 1001 Router

Router# show platform diag

Chassis type: ASR1001

Slot: 0, ASR1001

Running state : ok

Internal state : online

Internal operational state : ok

Physical insert detect time : 00:00:51 (1d01h ago)

Software declared up time : 00:01:37 (1d01h ago)

CPLD version : 0902010A

Firmware version : 12.2(20090526:143323) [gschnorr-mcp_dev_1ru2 rel

ease 1.5 ]

Sub-slot: 0/0, 4XGE-BUILT-IN

Operational status : ok

Internal state : inserted

Physical insert detect time : 00:01:39 (1d01h ago)

Logical insert detect time : 00:01:45 (1d01h ago)

Sub-slot: 0/1, SPA-2XOC12-POS

Operational status : ok

Internal state : inserted

Physical insert detect time : 00:01:40 (1d01h ago)

Logical insert detect time : 00:01:47 (1d01h ago)

Sub-slot: 0/2, ASR1001-IDC-4XGE

Operational status : ok

Internal state : inserted

Physical insert detect time : 00:01:41 (1d01h ago)

Logical insert detect time : 00:01:45 (1d01h ago)

Slot: R0, ASR1001

Running state : ok

Internal state : online

Internal operational state : ok

Physical insert detect time : 00:00:51 (1d01h ago)

Software declared up time : 00:00:51 (1d01h ago)

CPLD version : 09020110

Firmware version : 12.2(20090526:143323) [gschnorr-mcp_dev_1ru2 rel

ease 1.5 ]

Sub-slot: R0/0,

Running state : ok, active

Logical insert detect time : 00:00:51 (1d01h ago)

Became HA Active time : 00:03:20 (1d01h ago)

Sub-slot: R0/1,

Running state : ok, standby

Logical insert detect time : 00:02:04 (1d01h ago)

Slot: F0, ASR1001

Running state : ok, active

Internal state : online

Internal operational state : ok

Physical insert detect time : 00:00:51 (1d01h ago)

Software declared up time : 00:01:32 (1d01h ago)

Hardware ready signal time : 00:01:26 (1d01h ago)

Packet ready signal time : 00:01:37 (1d01h ago)

CPLD version : 0902010A

Firmware version : 12.2(20090526:143323) [gschnorr-mcp_dev_1ru2 rel

ease 1.5 ]

Slot: P0, Unknown

State : ps, fail

Physical insert detect time : 00:00:00 (never ago)

Slot: P1, ASR1001-PWR-AC

State : ok

Physical insert detect time : 00:01:18 (1d01h ago)

Slot: P2, ASR1001-FANTRAY

State : ok

Physical insert detect time : 00:01:17 (1d01h ago)

To view the operational state of the major hardware components on Cisco ASR 1013 Router, use the show platform diag command. This example shows the Power supply P0 has failed:

Router# show platform diag

Chassis type: ASR1013

Slot: 4, ASR1000-SIP10

Running state : ok

Internal state : online

Internal operational state : ok

Physical insert detect time : 00:00:48 (02:20:23 ago)

Software declared up time : 00:01:42 (02:19:29 ago)

CPLD version : 09111601

Firmware version : 15.0(1r)S

Sub-slot: 4/2, SPA-2CHT3-CE-ATM

Operational status : ok

Internal state : inserted

Physical insert detect time : 00:00:44 (02:20:27 ago)

Logical insert detect time : 00:02:23 (02:18:48 ago)

Slot: 5, ASR1000-SIP40

Running state : ok

Internal state : online

Internal operational state : ok

Physical insert detect time : 00:00:48 (02:20:23 ago)

Software declared up time : 00:01:39 (02:19:32 ago)

CPLD version : 00200800

Firmware version : 15.0(1r)S

Sub-slot: 5/0, SPA-5X1GE-V2

Operational status : ok

Internal state : inserted

Physical insert detect time : 00:00:43 (02:20:28 ago)

Logical insert detect time : 00:02:30 (02:18:41 ago)

Sub-slot: 5/1, SPA-8X1GE-V2

Operational status : ok

Internal state : inserted

Physical insert detect time : 00:00:43 (02:20:28 ago)

Logical insert detect time : 00:02:24 (02:18:47 ago)

Sub-slot: 5/2, SPA-4XT3/E3

Operational status : ok

Internal state : inserted

Physical insert detect time : 00:00:43 (02:20:28 ago)

Logical insert detect time : 00:02:30 (02:18:40 ago)

Slot: R0, ASR1000-RP2

Running state : ok, active

Internal state : online

Internal operational state : ok

Physical insert detect time : 00:00:48 (02:20:23 ago)

Software declared up time : 00:00:48 (02:20:23 ago)

Became HA Active time : 00:05:05 (02:16:06 ago)

CPLD version : 10021901

Firmware version : 12.2(33r)XND

Slot: R1, ASR1000-RP2

Running state : ok, standby

Internal state : online

Internal operational state : ok

Physical insert detect time : 00:00:48 (02:20:23 ago)

Software declared up time : 00:02:42 (02:18:29 ago)

CPLD version : 10021901

Firmware version : 12.2(33r)XND

Slot: F0, ASR1000-ESP40

Running state : ok, active

Internal state : online

Internal operational state : ok

Physical insert detect time : 00:00:48 (02:20:23 ago)

Software declared up time : 00:05:30 (02:15:41 ago)

Hardware ready signal time : 00:04:22 (02:16:49 ago)

Packet ready signal time : 00:05:33 (02:15:37 ago)

CPLD version : 1003190E

Firmware version : 15.0(1r)S

Slot: F1, ASR1000-ESP40

Running state : init, standby

Internal state : online

Internal operational state : ok

Physical insert detect time : 00:00:48 (02:20:23 ago)

Software declared up time : 01:35:45 (00:45:26 ago)

Hardware ready signal time : 01:34:35 (00:46:36 ago)

Packet ready signal time : 00:00:00 (never ago)

CPLD version : 1003190E

Firmware version : 15.0(1r)S

Slot: P0, Unknown

State : ps,fail

Physical insert detect time : 00:00:00 (never ago)

Slot: P1, ASR1013-PWR-AC

State : ok

Physical insert detect time : 00:01:35 (02:19:36 ago)

Slot: P2, ASR1013-PWR-AC

State : ok

Physical insert detect time : 00:01:35 (02:19:35 ago)

Slot: P3, ASR1013-PWR-AC

State : ok

Physical insert detect time : 00:01:36 (02:19:35 ago)

Reviewing and Analyzing Alarm Messages

To facilitate the review of alarm messages, you can write scripts to analyze alarm messages sent to the console or syslog. Scripts can provide reports on events such as alarms, security alerts, and interface status.

Syslog messages can also be accessed through Simple Network Management Protocol (SNMP) using the history table defined in the CISCO-SYSLOG-MIB.

Network Management System Alerts Network Administrator When an Alarm Is Reported Through SNMP

The Simple Network Management Protocol (SNMP) is an application-layer protocol that provides a standardized framework and a common language used for monitoring and managing devices in a network. Of all the approaches to monitor alarms, SNMP is the best approach for enterprise and service provider customers that have many routers to monitor.

SNMP provides notification of faults, alarms, and conditions that might affect services. SNMP allows a network administrator to access router information through a network management system (NMS) instead of by polling devices, reviewing logs, or reviewing log reports.

Note “Transceiver Missing - Link Down” alarm will be reported with a severity of “CRITICAL” in the output of show facility-alarm status command.

To use SNMP to get alarm notification, you must use the following MIBs:

- ENTITY-MIB, RFC 4133 (required for the CISCO-ENTITY-ALARM-MIB and CISCO-ENTITY-SENSOR-MIB to work)

- CISCO-ENTITY-ALARM-MIB

- CISCO-ENTITY-SENSOR-MIB (for SPA and transceiver environmental alarm information, which is not provided through the CISCO-ENTITY-ALARM-MIB)

For More Information

For more information about the topics discussed in this chapter, see the following documents:

Cisco IOS Master Command List, All Releases

Command Lookup Tool (Requires Cisco.com user ID and password)

Configuring MIB support

Cisco ASR 1000 Series Aggregation Services Routers MIB Specifications Guide

Configuring SNMP

“SNMP Support” chapter in the Cisco IOS XE Network Management Configuration Guide, Release 2

Graceful Deactivation of a SIP or SPA: Online insertion and removal (OIR)

“Installing and Removing a SIP” chapter in the

Cisco ASR 1000 Series Aggregation Services Routers SIP and SPA Hardware Installation Guide

MIBs supported on the Cisco ASR 1000 Series Aggregation Services Routers

Cisco ASR 1000 Series Aggregation Services Routers MIB Specifications Guide

Power supplies and the DB-25 alarm connector

“Cisco ASR 1000 Series Routers Components Overview” chapter in the Cisco ASR 1000 Series Aggregations Services Routers Hardware Installation Guide

Configuring the Common Criteria Tcl Scripts

To monitor the packet drop event on the ASR 1000 Series Router, use the Common Criteria Tcl scripts.

This chapter includes the following sections:

- Common Criteria Tcl Scripts Overview

- Installing the Common Criteria Tcl Scripts

- How to Configure the Common Criteria Tcl Scripts

- Generating the Event Alarm Reports

- Configuration Examples of the Common Criteria Tcl Scripts

- For More Information

Common Criteria Tcl Scripts Overview

Common Criteria (CC) is an international standard for evaluating IT product security and reliability. It is recognized by over 15 countries around the world including Australia, Canada, France, Germany, Greece, Italy, Japan, New Zealand, Spain, UK, South Korea and the United States. Many government customers around the world consider Common Criteria a mandatory requirement for purchasing network security products.

Common Criteria is a methodology for product evaluation. There are seven levels of evaluation and only levels 1 through 4 are mutually recognized by the participating countries. Products typically target EAL2 or EAL4, an evaluation conducted in any one of the participating countries is valid for the rest for the members. Cisco continues to be a global leader in completing and pursuing Common Criteria evaluations.

ASR1000 Series Routers support packet drop event monitoring as required by the Common Criteria standards. The Common Criteria features can be enabled using Tcl scripting. To find out more about Cisco IOS XE scripting using Tcl, see the “Cisco IOS XE Scripting with Tcl” chapter of the Cisco IOS XE Network Management Software Configuration Guide.

Common Criteria leverages the IOS XE Embedded Syslog Manager (ESM) and Embedded Event Manager (EEM) mechanisms for enabling periodic actions. The ESM feature provides a programmable framework that allows you to filter, escalate, correlate, route, and customize system logging messages prior to delivery by the Cisco IOS system message logger. For more information, see the Embedded Syslog Manager (ESM) Configuration Guide.

Table 1-1 lists the Common Criteria Tcl scripts.

Table 1-1 Common Criteria Tcl Scripts

Script Name

Description

timer.tcl

Supports the Timer events for other scripts.

alarms_db.tcl

Manages the alarms database.

em_ike_phase1_failure.tcl

Monitors the Internet Key Exchange (IKE) protocol Phase 1 negotiation failures.

em_ike_phase2_failure.tcl

IKEv1 Phase 2 negotiation failures watcher script.

em_login_failure.tcl

Monitors the user login failures.

em_monitor_violation.tcl

Monitors the information flow violations. ACL-based event monitors must be configured to trigger the violation monitor watcher.

em_monitor_vpn_event.tcl

Monitors the VPN encryption, decryption faults, and packet replay events.

monitor_ipsec.tcl

Configures the VPN event monitors.

syslog_exclude.tcl

Excludes the syslog messages containing the keywords from the syslog database.

syslog_include.tcl

Includes the syslog messages containing the keywords in the syslog database.

esm_conf_vty.tcl

Configures the syslog message output to the connected vty devices.

Installing the Common Criteria Tcl Scripts

Super administrator can copy the scripts from a portable device such as a USB flash drive on the hard disk, which is defined as a protected directory.

Example:

Copy bootflash:<folder name> <Tcl file name> harddisk:/cc_scripts

How to Configure the Common Criteria Tcl Scripts

To configure the Common Criteria Tcl scripts, complete the following steps:

SUMMARY STEPS

1. enable

2. configure terminal

3. logging filter [script-url] [args filter-arguments]

4. end

5. show logging

DETAILED STEPS

Command or Action

Purpose

Step 1

enable

Router> enable

Enables the privileged EXEC mode.

Enter your password if prompted.

Step 2

configure terminal

Router# configure terminal

Enters the global configuration mode.

Step 3

logging filter [script-url][args filter-arguments]

Router(config)# logging filter bootflash:/escalate.tcl 1 args CONFIG_I 1

Specifies one or more syslog filter modules to be applied to the generated system logging messages. To remove a module from the list of modules to be executed, use the no form of this command.

Note Repeat this command for each syslog filter module that should be used.

- (Optional) The script-url argument specifies the script URL.

Note Provide a valid directory location, an incorrect location can trigger a router reload.

- (Optional) The args filter-arguments syntax can be added to pass arguments to the specified filter. Multiple arguments can be specified. The number and type of arguments should be defined in the syslog filter module. For example, if the syslog filter module is designed to accept a specific e-mail address as an argument, you could pass the e-mail address using the args user@host.com syntax. Multiple arguments are typically delimited by spaces.

Step 4

end

Router(config)# end

Ends your current configuration session and returns the CLI to privileged EXEC mode.

Step 5

show logging

Router# show logging

(Optional) Displays the status of system logging, including the status of ESM-filtered logging:

- If filtered logging to the buffer is enabled, this command also displays the data stored in the buffer.

- The order in which the syslog filter modules are listed in the output of this command is the order in which the filter modules are executed.

Examples

This section provides the following configuration examples:

- Alarm Confirmation Timer

- Alarm Database Manager

- IKEv1 Phase 1 and Phase 2 Failures Catcher

- Syslog Filter

- Information Flow Violations Watcher

- IPsec Policy Violation Category Watcher

- VPN Policy Violations Catcher

- Replication Output of Syslog Messages

Alarm Confirmation Timer

logging filter bootflash:timer.tcl args 120

Alarm Database Manager

When the alarm-property is set to alarm_audible, it enables audio signals for every CC alarm confirmation prompt. By default, audible-property is set to alarm_not_audible:

logging filter bootflash:alarms_db.tcl args alarm_audible

IKEv1 Phase 1 and Phase 2 Failures Catcher

The IKEv1 failure catcher alert enables the monitoring of IKEv1 phase 1 and phase 2 negotiation failures. The commands for configuring the IKEv1 negotiation failure monitor are:

logging filter <script-url>em_ike_phase1_failure.tcl [args threshold [interval]]

logging filter <script-url>em_ike_phase2_failure.tcl [args threshold [interval]]

The argument values are as follows:

- Threshold —number of failures after which the CC alarm is raised. The default threshold value is 1.

- Interval —time interval during which the number of failures must reach a set threshold. On reaching the threshold, the alarms are triggered. The default value is indefinite.

If the interval value is not set, the CC alarm is raised after the threshold pertaining to the number of failures is crossed.

If the interval value is set, and the value is less than the threshold value, the failure counter is reset and the CC alarm is not raised.

Example:

logging filter bootflash:em_ike_phase1_failure.tcl args 3 300

This configuration raises a CC alarm after three IKEv1 Phase 1 failures occur during the 300-second interval.

If the number of failures are less than three within the 300-second interval, the CC alarm is not raised, and the failure counter is reset.

Syslog Filter

Syslog filter commands support both inclusive and exclusive filtering of syslog messages. The configured filters determine the order of syslog command execution. The number of syslog filters that can be configured depends on the device memory size.

The commands for configuring the syslog filters are:

- Inclusive filtering:

logging filter <script-url>syslog_include.tcl [args <string>]

The value of the string argument is an arbitrary character string.

Note Strings containing special characters should be enclosed within a pair of the escape characters such as single quotes (' '), double quotes (" "), or backslash (\ \).

Information Flow Violations Watcher

When an information flow violation occurs, the information flow violations watcher triggers a CC alarm. The command to configure the information flow violations watcher is:

logging filter <script-url>em_monitor_violation.tcl

IPsec Policy Violation Category Watcher

When an IPsec policy violation occurs, the IPsec policy violations watcher triggers a CC alarm. The command to configure IPsec policy violations watcher is

logging filter <script-url>monitor_ipsec.tcl args <esp> <category> <threshold>

The argument values are as follows:

- esp —Active or standby ASR1000 ESP on which IPsec policy violations are monitored.

- category — decrypt-failed, or encrypt-failed, or replay.

Watches for decryption or encryption failures or IPsec packets replay events

- threshold —Number of events watched after which a cumulative event is reported. The threshold value must be greater than 0.

Note All command arguments are mandatory.

Multiple command lines can be configured for watching multiple categories of the IPsec policy violations.

Example:

logging filter bootflash:monitor_ipsec.tcl args active replay 100000

This command line configures a watcher for the IPsec packet replay violations. The watcher triggers an alarm after 100000 replayed IPsec packets are detected.

VPN Policy Violations Catcher

logging filter <script-url>esm_conf_vty.tcl

Generating the Event Alarm Reports

CC Protection Profiles identify a number of events that generate alarms. The alarms must be acknowledged by the administrator.

For example, the following commands display the acknowledgement of alarms on the router:

000077: *Apr 21 03:02:19.566: %CC-6-INFO: Please confirm alarm 000077

000077: *Apr 21 02:54:23.001: %CC-6-ALARM: Login Authentication Failed for user eve 2 times in 11 seconds interval

Alarm confirmation on the router:

Router (config)#event manager environment confirm_alarm 000077

Based on the administrator-specified values, the syslog messages indicate alarm-inducing events.The reports that are generated for the event alarms include:

- Specified number of authentication failures—IOS supports logging of authentication events. To report authentication failures, administrators use the following commands:

– conf t

– login on-failure log

– end

- Specified number of information flow policy violations by:

– Individual source network identifiers, such as IP address, within a specified time.

– Individual destination network identifiers, within user-specified time.

– Individual destination subject service identifiers, such as TCP port, within user-specified time.

– Individual or group rules within user-specified time.

Note The monitor drop command is used to configure event monitoring of the information flow policy violations.

- The VPN policy violation catcher includes:

– Any detected replay of TSF data or security attributes

– Security administrator-specified number of encryption failures

– Security administrator-specified number of decryption failures

Note The set platform hardware qfp feature ipsec event-monitor command is used to configure VPN-specific event monitoring.

The clear platform hardware qfp <mastership> feature ipsec event-monitor command is used for removing the event monitors.

Configuration Examples of the Common Criteria Tcl Scripts

Related Documents

Related Topic

Document Title

Embedded Syslog Manager

Embedded Syslog Manager module

Network Management Configurations

Cisco IOS Network Management Configuration Guide

Network Management commands (including Tcl and logging commands): complete command syntax, defaults, command mode, command history, usage guidelines, and examples

Cisco IOS Network Management Command Reference

Monitoring the Control Plane

To verify the overall health of your system, monitor control plane resources on a regular basis.

This chapter includes the following sections:

- Avoiding Problems Through Regular Monitoring

- Control Plane Overview

- Monitoring Control Plane Resources

- For More Information

Avoiding Problems Through Regular Monitoring

Monitoring system resources allows you to detect potential problems before they happen, thus avoiding outages. The following are show the advantages of regular monitoring:

- In a real-life example, customers installed new line cards. After the line cards were in operation for a few years, lack of memory on those line cards caused major outages in some cases. Monitoring memory usage would have identified a memory issue and avoided an outage.

- Regular monitoring establishes a baseline for a normal system load. You can use this information as a basis for comparison when you upgrade hardware or software—to see if the upgrade has affected resource usage.

Control Plane Overview

The following sections contain a high-level overview of the control plane:

- Cisco ASR 1000 Series Routers Control Plane Architecture

- Cisco IOS XE Software Architecture

Cisco ASR 1000 Series Routers Control Plane Architecture

The major components in the control plane are:

- Cisco ASR 1000 Series Route Processor (RP)—A general purpose CPU responsible for routing protocols, CLI, network management interfaces, code storage, logging, and chassis management. The Cisco ASR 1000 Series RPs process network control packets as well as protocols not supported by the Cisco ASR 1000 Series ESP.

- Cisco ASR 1000 Series Embedded Services Processor (ESP)—A forwarding processor that handles forwarding control plane traffic, and performs packet processing functions such as firewall inspection, ACLs, encryption, and QoS.

- Cisco ASR 1000 Series SPA Interface Processor (SIP)—An interface processor that provides the connection between the Route Processor and the shared port adapters (SPAs).

Distributed Control Plane Architecture

Cisco ASR 1000 Series Routers have a distributed control plane architecture. A separate control processor is embedded on each major component in the control plane, as shown in Figure 2-1:

- Route Processor (RP)

- Forwarding Engine Control Processor (FECP)

- I/O Control Processor (IOCP)

The RP manages and maintains the control plane using a dedicated Gigabit Ethernet out-of-band channel (EOBC). The internal EOBC is used to continuously exchange system state information among the different major components. For example, in the event of a failure condition, a switchover event occurs and the standby RP and ESP are immediately ready to assume the data forwarding functions or the control plane functions for the failed component.

The inter-integrated circuit (I2C) monitors the health of hardware components. The Enhanced SerDes Interconnect (ESI) is a set of serial links that are the data path links on the midplane connecting the RP, SIPs, and standby ESPs to the active ESP.

Figure 2-1 Cisco ASR 1000 Series Routers Control Plane Architecture

The control plane processors perform the following functions:

RP

- Runs the router control plane (Cisco IOS), including processing network control packets, computing routes, and setting up connections.

- Monitors interface and environmental status, including management ports, LEDs, alarms, and SNMP network management.

- Downloads code to other components in the system.

- Selects the active RP and ESP and synchronizes the standby RP and ESP.

- Manages logging facilities, on-board failure logging (OBFL), and statistics aggregation.

FECP

- Provides direct CPU access to the forwarding engine subsystem—the Cisco QuantumFlowProcessor (QFP) subsystem—that is the forwarding processor chipset and also resides on the ESP.

- Manages the forwarding engine subsystem and its connection to I/O.

- Manages the forwarding processor chipset.

IOCP

- Provides direct CPU access to SPAs installed in a SIP.

- Manages the SPAs.

- Handles SPA online insertion and removal (OIR) events.

- Runs SPA drivers that initialize and configure SPAs.

Cisco IOS XE Software Architecture

The control plane processors run Cisco IOS XE software, which is an operating system that consists of a Linux-based kernel and a common set of operating system-level utility programs. It is a distributed software architecture that moves many operating system responsibilities out of the IOS process.

In this architecture, IOS runs as one of many Linux processes while allowing other Linux processes to share responsibility for running the router. IOS runs as a user process on the RP. Hardware-specific components have been removed from the IOS process and are handled by separate middleware processes in Cisco IOS XE software. If a hardware-specific issue is discovered, the middleware process can be modified without touching the IOS process.

Figure 2-2 shows the main components of the Cisco IOS XE software architecture. This modular architecture increases network resiliency by distributing operating responsibility among separate processes. The architecture also allows for better allocation of memory so the router can run more efficiently.

All of the Cisco IOS XE software modules run in their own protective memory spaces, which facilitates fault containment. Any software outages of an individual software module are localized to that particular module. All other software processes continue to operate. For example, for each SPA, a separate driver process is executed on the SIP, even if multiple SPAs of the same type are present. Because each SPA driver runs in its own protective memory, failure or upgrade of an individual driver is localized to the affected SPA.

Figure 2-2 Cisco IOS XE Software Architecture

Using the Linux architecture, Cisco IOS XE provides the following benefits:

- The ability to integrate multi-core (multiple CPUs on a single piece of silicon) processors.

- The IOS process has no direct access to hardware components, thus providing a greater level of resiliency.

- The ability to run active and standby IOS processes on the non-hardware-redundant Cisco ASR 1004 Router and Cisco ASR 1006 Router.

- The IOS process operates as a virtual machine under the RP Linux kernel. Upon bootup, the RP Linux kernel allocates 50 percent of available memory to IOS processes as a one-time event. For systems that have a single IOS process, IOS is allocated approximately 45 percent of total RP memory. For redundant IOS process systems, each IOS process is allocated approximately 20 percent of total RP memory.

- Hardware components are managed through memory-protected middleware processes.

- SPA drivers run as unique processes allowing the ability to upgrade and restart individual SPAs.

Monitoring Control Plane Resources

The following sections discuss monitoring memory and CPU from the perspective of the IOS process and from the perspective of the overall control plane:

- IOS Process Resources

- Overall Control Plane Resources

IOS Process Resources

For information about memory and CPU utilization from within the IOS process, use the show memory command and the show process cpu command. Note that these commands provide a representation of memory and CPU utilization from the perspective of the IOS process only; they do not include information for resources on the entire route processor. For example, show memory on an RP2 with 8 GB of RAM running a single IOS process shows the following memory usage:

Router# show memory

Head Total(b) Used(b) Free(b) Lowest(b) Largest(b)

Processor 2ABEA4316010 4489061884 314474916 4174586968 3580216380 3512323496

lsmpi_io 2ABFAFF471A8 6295128 6294212 916 916 916

Critical 2ABEB7C72EB0 1024004 92 1023912 1023912 1023912

For the dual-core RP2, the show process cpu command reports a single IOS CPU utilization average using both processors:

Router# show process cpu

CPU utilization for five seconds: 0%/0%; one minute: 0%; five minutes: 0%

PID Runtime(ms) Invoked uSecs 5Sec 1Min 5Min TTY Process

1 583 48054 12 0.00% 0.00% 0.00% 0 Chunk Manager

2 991 176805 5 0.00% 0.00% 0.00% 0 Load Meter

3 0 2 0 0.00% 0.00% 0.00% 0 IFCOM Msg Hdlr

4 0 11 0 0.00% 0.00% 0.00% 0 Retransmission o

5 0 3 0 0.00% 0.00% 0.00% 0 IPC ISSU Dispatc

6 230385 119697 1924 0.00% 0.01% 0.00% 0 Check heaps

7 49 28 1750 0.00% 0.00% 0.00% 0 Pool Manager

8 0 2 0 0.00% 0.00% 0.00% 0 Timers

9 17268 644656 26 0.00% 0.00% 0.00% 0 ARP Input

10 197 922201 0 0.00% 0.00% 0.00% 0 ARP Background

11 0 2 0 0.00% 0.00% 0.00% 0 ATM Idle Timer

12 0 1 0 0.00% 0.00% 0.00% 0 ATM ASYNC PROC

13 0 1 0 0.00% 0.00% 0.00% 0 AAA_SERVER_DEADT

14 0 1 0 0.00% 0.00% 0.00% 0 Policy Manager

15 0 2 0 0.00% 0.00% 0.00% 0 DDR Timers

16 1 15 66 0.00% 0.00% 0.00% 0 Entity MIB API

17 13 1195 10 0.00% 0.00% 0.00% 0 EEM ED Syslog

18 93 46 2021 0.00% 0.00% 0.00% 0 PrstVbl

19 0 1 0 0.00% 0.00% 0.00% 0 RO Notify Timers

Overall Control Plane Resources

For information about control plane memory and CPU utilization on each control processor, use the show platform software status control-processor brief command (summary view) or the show platform software status control-processor command (detailed view).

All control processors should show a status of Healthy. Other possible status values are Warning and Critical. Warning indicates that the router is operational but that the operating level should be reviewed. Critical implies that the router is near failure.

If you see a status of Warning or Critical, take the following actions:

- Reduce static and dynamic loads on the system by reducing the number of elements in the configuration or by limiting the capacity for dynamic services.

- Reduce the number of routes and adjacencies, limit the number of ACLs and other rules, reduce the number of VLANs, and so on.

The following sections describe the fields in show platform software status control-processor command output.

Load Average

Load average represents the process queue or process contention for CPU resources. For example, on a single-core processor, an instantaneous load of 7 would mean that seven processes are ready to run, one of which is currently running. On a dual-core processor, a load of 7 would represent seven processes are ready to run, two of which are currently running.

Memory Utilization

Memory utilization is represented by the following fields:

- Total—Total line card memory

- Used—Consumed memory

- Free—Available memory

- Committed—Virtual memory committed to processes

CPU Utilization

CPU utilization is an indication of the percentage of time the CPU is busy and is represented by the following fields:

- CPU—The allocated processor

- User—Non-Linux kernel processes

- System —Linux kernel process

- Nice—Low priority processes

- Idle—Percentage of time the CPU was inactive

- IRQ—Interrupts

- SIRQ—System Interrupts

- IOwait—Percentage of time CPU was waiting for I/O

The following are examples of the show platform software status control-processor command.

Router# show platform software status control-processor brief

Load Average

Slot Status 1-Min 5-Min 15-Min

RP0 Healthy 0.25 0.30 0.44

RP1 Healthy 0.31 0.19 0.12

ESP0 Healthy 0.01 0.05 0.02

ESP1 Healthy 0.03 0.05 0.01

SIP1 Healthy 0.15 0.07 0.01

SIP2 Healthy 0.03 0.03 0.00

Memory (kB)

Slot Status Total Used (Pct) Free (Pct) Committed (Pct)

RP0 Healthy 3722408 2514836 (60%) 1207572 (29%) 1891176 (45%)

RP1 Healthy 3722408 2547488 (61%) 1174920 (28%) 1889976 (45%)

ESP0 Healthy 2025468 1432088 (68%) 593380 (28%) 3136912 (149%)

ESP1 Healthy 2025468 1377980 (65%) 647488 (30%) 3084412 (147%)

SIP1 Healthy 480388 293084 (55%) 187304 (35%) 148532 (28%)

SIP2 Healthy 480388 273992 (52%) 206396 (39%) 93188 (17%)

CPU Utilization

Slot CPU User System Nice Idle IRQ SIRQ IOwait

RP0 0 30.12 1.69 0.00 67.63 0.13 0.41 0.00

RP1 0 21.98 1.13 0.00 76.54 0.04 0.12 0.16

ESP0 0 13.37 4.77 0.00 81.58 0.07 0.19 0.00

ESP1 0 5.76 3.56 0.00 90.58 0.03 0.05 0.00

SIP1 0 3.79 0.13 0.00 96.04 0.00 0.02 0.00

SIP2 0 3.50 0.12 0.00 96.34 0.00 0.02 0.00

Router# show platform software status control-processor

RP0: online, statistics updated 10 seconds ago

Load Average: healthy

1-Min: 0.30, status: healthy, under 5.00

5-Min: 0.31, status: healthy, under 5.00

15-Min: 0.47, status: healthy, under 5.00

Memory (kb): healthy

Total: 3722408

Used: 2514776 (60%), status: healthy, under 90%

Free: 1207632 (29%), status: healthy, over 10%

Committed: 1891176 (45%), status: healthy, under 90%

Per-core Statistics

CPU0: CPU Utilization (percentage of time spent)

User: 30.12, System: 1.69, Nice: 0.00, Idle: 67.63

IRQ: 0.13, SIRQ: 0.41, IOwait: 0.00

RP1: online, statistics updated 5 seconds ago

Load Average: healthy

1-Min: 0.14, status: healthy, under 5.00

5-Min: 0.11, status: healthy, under 5.00

15-Min: 0.09, status: healthy, under 5.00

Memory (kb): healthy

Total: 3722408

Used: 2547488 (61%), status: healthy, under 90%

Free: 1174920 (28%), status: healthy, over 10%

Committed: 1889976 (45%), status: healthy, under 90%

Per-core Statistics

CPU0: CPU Utilization (percentage of time spent)

User: 21.98, System: 1.13, Nice: 0.00, Idle: 76.54

IRQ: 0.04, SIRQ: 0.12, IOwait: 0.16

ESP0: online, statistics updated 5 seconds ago

Load Average: healthy

1-Min: 0.06, status: healthy, under 5.00

5-Min: 0.09, status: healthy, under 5.00

15-Min: 0.03, status: healthy, under 5.00

Memory (kb): healthy

Total: 2025468

Used: 1432088 (68%), status: healthy, under 90%

Free: 593380 (28%), status: healthy, over 10%

Committed: 3136912 (149%), status: healthy, under 300%

Per-core Statistics

CPU0: CPU Utilization (percentage of time spent)

User: 13.37, System: 4.77, Nice: 0.00, Idle: 81.58

IRQ: 0.07, SIRQ: 0.19, IOwait: 0.00

ESP1: online, statistics updated 5 seconds ago

Load Average: healthy

1-Min: 0.22, status: healthy, under 5.00

5-Min: 0.08, status: healthy, under 5.00

15-Min: 0.02, status: healthy, under 5.00

Memory (kb): healthy

Total: 2025468

Used: 1377980 (65%), status: healthy, under 90%

Free: 647488 (30%), status: healthy, over 10%

Committed: 3084412 (147%), status: healthy, under 300%

Per-core Statistics

CPU0: CPU Utilization (percentage of time spent)

User: 5.76, System: 3.56, Nice: 0.00, Idle: 90.58

IRQ: 0.03, SIRQ: 0.05, IOwait: 0.00

SIP1: online, statistics updated 6 seconds ago

Load Average: healthy

1-Min: 0.05, status: healthy, under 5.00

5-Min: 0.06, status: healthy, under 5.00

15-Min: 0.00, status: healthy, under 5.00

Memory (kb): healthy

Total: 480388

Used: 293084 (55%), status: healthy, under 90%

Free: 187304 (35%), status: healthy, over 10%

Committed: 148532 (28%), status: healthy, under 90%

Per-core Statistics

CPU0: CPU Utilization (percentage of time spent)

User: 3.79, System: 0.13, Nice: 0.00, Idle: 96.04

IRQ: 0.00, SIRQ: 0.02, IOwait: 0.00

SIP2: online, statistics updated 8 seconds ago

Load Average: healthy

1-Min: 0.03, status: healthy, under 5.00

5-Min: 0.03, status: healthy, under 5.00

15-Min: 0.00, status: healthy, under 5.00

Memory (kb): healthy

Total: 480388

Used: 273992 (52%), status: healthy, under 90%

Free: 206396 (39%), status: healthy, over 10%

Committed: 93188 (17%), status: healthy, under 90%

Per-core Statistics

CPU0: CPU Utilization (percentage of time spent)

User: 3.50, System: 0.12, Nice: 0.00, Idle: 96.34

IRQ: 0.00, SIRQ: 0.02, IOwait: 0.00

For More Information

For more information about the topics discussed in this chapter, see the following documents:

Topic

Document

Command descriptions

Cisco IOS Master Command List, All Releases

Command Lookup Tool (Requires Cisco.com user ID and password)

Performing File System Cleanups

This chapter describes the various file system cleanups performed on the Cisco ASR 1000 Series Aggregation Services Router.

This chapter includes the following sections:

- Performing Core File and Trace File Cleanups

- Performing Crashinfo File Cleanups

- Performing Sub-Package File Cleanups

- For More Information

Performing Core File and Trace File Cleanups

Core and trace files are automatically created and saved to the core and tracelogs directories on the

harddisk: file system on all Cisco ASR 1000 Series Routers except the Cisco ASR 1001 Router, Cisco ASR 1002 Router and Cisco ASR 1002-F Router, which store core and trace files in the bootflash: file system.

Trace files are automatically created during normal operation of the router and are stored in the tracelogs directory. Normally, the router automatically purges the old tracelogs to provide space for new files.

In case of a process failure, core files may be generated in the core directory. If any core files are detected, contact Cisco TAC for assistance. Normally, the router will automatically purge the old core files to make space for new files.

The user has the option to delete unneeded core and tracelog files to make space for other content. However, such a removal may impact the debuggability of the system.

Note On an Cisco ASR 1001 Router equipped with the HDD IDC option, the ROMMON cannot see the hard disk and therefore the ROMMON has no access to the data stored on the HDD IDC. Though you can copy the Image to a harddisk on Cisco ASR 1001-HDD Router, you cannot boot from the hardisk. The ASR1001 HDD can be used for general storage but cannot be considered a complete filesystem (like bootflash or USB0:) and is only accessible when the box is running IOS. The true intent of the HDD is to support applications that require a harddisk. Therefore the HDD IDC on Cisco ASR 1001 Router should be used for application services such as call manager, etc.

To clean up the contents of the core and tracelogs directories, perform the following steps:

Step 1 Log in to the Cisco ASR 1000 Series Router using a Telnet or Secure Shell (SSH) connection.

Note The core and tracelogs directories can contain large volumes of output. Be sure to use a Telnet or SSH connection instead of the console port to avoid monopolizing the console port.

Step 2 Change to the core or tracelogs directory using the cd command.

Router# cd harddisk:/tracelogs

Step 3 Display the contents of the core or tracelogs directory using the dir command.

Router# dir

Directory of harddisk:/tracelogs/

753666 -rwx 164 Sep 14 2008 22:06:55 +01:00 inst_cleanup_R0-0.log.145

753667 -rwx 165 Sep 14 2008 21:01:41 +01:00 inst_cleanup_R0-0.log.221

753668 -rwx 165 Sep 14 2008 20:01:29 +01:00 inst_cleanup_R0-0.log.119

753669 -rwx 165 Sep 14 2008 20:06:30 +01:00 inst_cleanup_R0-0.log.110

753670 -rwx 165 Sep 14 2008 20:11:31 +01:00 inst_cleanup_R0-0.log.121

753671 -rwx 165 Sep 14 2008 20:16:32 +01:00 inst_cleanup_R0-0.log.132

753672 -rwx 165 Sep 14 2008 20:21:33 +01:00 inst_cleanup_R0-0.log.143

753673 -rwx 165 Sep 14 2008 20:26:34 +01:00 inst_cleanup_R0-0.log.154

753676 -rwx 165 Sep 14 2008 20:31:35 +01:00 inst_cleanup_R0-0.log.165

753677 -rwx 165 Sep 14 2008 20:36:36 +01:00 inst_cleanup_R0-0.log.176

753678 -rwx 165 Sep 14 2008 20:41:37 +01:00 inst_cleanup_R0-0.log.187

753679 -rwx 165 Sep 14 2008 20:46:38 +01:00 inst_cleanup_R0-0.log.198

753680 -rwx 165 Sep 14 2008 20:51:39 +01:00 inst_cleanup_R0-0.log.199

753681 -rwx 165 Sep 14 2008 20:56:40 +01:00 inst_cleanup_R0-0.log.200

753674 -rwx 165 Sep 14 2008 21:06:42 +01:00 inst_cleanup_R0-0.log.232

753675 -rwx 165 Sep 14 2008 21:11:43 +01:00 inst_cleanup_R0-0.log.233

753682 -rwx 165 Sep 14 2008 21:16:44 +01:00 inst_cleanup_R0-0.log.244

753683 -rwx 165 Sep 14 2008 21:21:45 +01:00 inst_cleanup_R0-0.log.255

753684 -rwx 165 Sep 14 2008 21:26:46 +01:00 inst_cleanup_R0-0.log.266

. . .

39313059840 bytes total (38428729344 bytes free)

Step 4 Remove files from the core or tracelogs directory using the delete command. Delete files based on their creation date; that is, delete older files first.

Router# delete inst_cleanup_R0-0*

Caution Core and trace files can be deleted; do not delete the core and tracelogs directories.

Step 5 Repeat Step 2 through Step 4 for all the core and tracelogs directories on the router as follows:

- For Cisco ASR 1006 Routers, perform the file cleanup on the harddisk: file system on both RPs.

- For Cisco ASR 1004 Routers, perform the file cleanup on the harddisk: file system on the single RP.

- For Cisco ASR 1002 Routers and Cisco ASR 1002-F Routers, perform the file cleanup on the bootflash: file system. (The harddisk: file system is not available.)

Performing Crashinfo File Cleanups

Crashinfo files are automatically created and saved to the bootflash: or harddisk: file systems on all Cisco ASR 1000 Series Routers. Delete unneeded crashinfo files at least once a week to maintain optimal router operation.

To delete crashinfo files, perform the following steps:

Step 1 Log in to the Cisco ASR 1000 Series Router using a Telnet or Secure Shell (SSH) connection.

Note Crashinfo files may generate large volumes of output. Be sure to use a Telnet or SSH connection instead of the console port to avoid monopolizing the console port.

Step 2 Change to the bootflash: or harddisk: directory using the cd command.

Router# cd harddisk:

Step 3 Display the contents of the directory using the dir command.

Router# dir

Directory of harddisk:/

11 drwx 16384 Dec 4 2007 12:23:10 +00:00 lost+found

557057 drwx 4096 Aug 4 2008 23:10:46 +01:00 core

12 -rw- 0 Dec 4 2007 12:24:35 +00:00 tracelogs.780

753665 drwx 167936 Sep 14 2008 22:27:00 +01:00 tracelogs

13 -rw- 234250 Feb 1 2008 05:56:59 +00:00 crashinfo_SIP_01_00_20080C

14 -rw- 46853 Apr 10 2008 00:50:12 +01:00 tech_support_ouput.tgz.tgz

15 -rw- 225308932 Aug 13 2008 22:50:29 +01:00 2008-08-10_14.32.rp_supern

16 -rw- 208904396 Aug 20 2008 21:20:33 +01:00 asr1000rp1-adventerprisekn

39313059840 bytes total (38428712960 bytes free)

Step 4 Delete crashinfo files using the delete command.

Router# delete crashinfo_SIP_01_00_20080C

Step 5 Repeat Step 2 through Step 4 for the other file system.

For Cisco ASR 1006 Routers, purge the crashinfo files on both RPs.

Performing Sub-Package File Cleanups

A consolidated package file can be stored in the bootflash: file system, on a USB Flash disk, or on any TFTP or other network server. Individual sub-package files and provisioning files must be stored in the bootflash: file system.

A sub-package file is no longer in use when it is no longer referenced by the booted or specified provisioning manager. Remove sub-package files and provisioning files that are no longer in use to maintain optimal router operation.

To delete sub-package files and provisioning files that are no longer in use, use the request platform software package clean command. This command checks to see which sub-package files and provisioning files are in use and deletes only those files that are not in use.

Example: Deleting All Unused Sub-Package Files and Provisioning Files From a Boot Directory

Router# request platform software package clean

Cleaning up unnecessary package files

No path specified, will use booted path harddisk:packages.conf

Cleaning harddisk:

Scanning boot directory for packages ... done.

Preparing packages list to delete ...

asr1000rp1-espbase.02.03.00.122-33.XNC.pkg

File is in use, will not delete.

asr1000rp1-rpaccess.02.03.00.122-33.XNC.pkg

File is in use, will not delete.

asr1000rp1-rpbase.02.03.00.122-33.XNC.pkg

File is in use, will not delete.

asr1000rp1-rpcontrol.02.03.00.122-33.XNC.pkg

File is in use, will not delete.

asr1000rp1-rpios-adventerprisek9.02.03.00.122-33.XNC.pkg

File is in use, will not delete.

asr1000rp1-sipbase.02.03.00.122-33.XNC.pkg

File is in use, will not delete.

asr1000rp1-sipspa.02.03.00.122-33.XNC.pkg

File is in use, will not delete.

packages.conf

File is in use, will not delete.

done.

SUCCESS: No extra package or provisioning files found on media. Nothing to clean.

Example: Deleting a Specific Sub-Package File from a Boot Directory

Router# request platform software package clean file harddisk:packages.conf

Cleaning up unnecessary package files

Scanning boot directory for packages ... done.

Preparing packages list to delete ...

packages.conf

File is in use, will not delete.

done.

SUCCESS: No extra package or provisioning files found on media. Nothing to clean.

Example: Deleting a Duplicate Sub-Package File on Different Media

Cisco IOS Master Command List, All Releases

Command Lookup Tool (Requires Cisco.com user ID and password)

Upgrading System Software

The Cisco ASR 1000 Series Routers introduce a new software packaging model and architecture. The new software packaging model and upgrade processes are described in the the Cisco ASR 1000 Series Aggregation Services Routers Software Configuration Guide.

For information, see the following chapters in that guide:

Topic

Chapter

Software packaging model and architecture

“Software Packaging and Architecture”

Upgrading system software offline

“Consolidated Packages and Sub-Package Management”

Interoperability of Cisco IOS XE software releases

“Cisco IOS XE Software Package Compatibility for ISSU”

ISSU Upgrade Procedure

“Software Upgrade Process”

Using Sub-packages for Software Upgrade on a Cisco ASR 1001 Router

“Software Upgrade Process”

Performing Factory Reset

- Understanding How Factory Reset Works

- Software and Hardware Support

- Prerequisites

- Restrictions

- When to Use Factory Reset

- What Happens after Factory Reset

Understanding How Factory Reset Works

The Factory Reset feature is used to remove all sensitive information from a router or restore the router to a fully functional state.

The factory reset process uses the factory reset–all command to take backup of existing configuration and then reset the router to an earlier fully functional state. In a high availability setup, the factory reset process is executed on the active Route Processor (RP) and is then synchronized to the standby RP. The duration of the factory reset process is dependent on the storage size of the router. It can extend between 30 minutes on an ASR1000 consolidated platform and up to 3 hours on a high availability setup.

Table 1 covers details of data erased or retained during the factory reset process:

Data Erased

Data Retained

Non-volatile random-access memory (NVRAM) data

OBFL (Onboard Failure Logging) logs

Value of configuration register

Licenses

Contents of USB

User data, startup, and running configuration

Credentials (Secure Unique Device Identifier [SUDI] certificates, public key infrastructure (PKI) keys, and FIPS-related keys)

Note: The factory reset process takes a backup of the boot image if the system is booted from an image stored locally (bootflash or harddisk). If the current boot image is a remote image or stored on an USB, NIM-SSD or such, ensure that you take a backup of the image before starting the factory reset process

Software and Hardware Support

- This feature is introduced starting from IOS XE Fuji 16.7.1 release.

- This feature is supported on all Cisco ASR 1000 platforms and Cisco ASR 1000 Series Route Processor 2 (RP2), and Cisco ASR 1000 Series Route Processor 3 (RP3)

- Factory reset process is supported on standalone routers and also on routers configured for high availability.

Prerequisites

- Ensure that all the software images, configurations and personal data is backed up before performing the factory reset operation.

- Ensure that there is uninterrupted power supply when the feature reset process is in progress.

- The factory reset process takes a backup of the boot image if the system is booted from an image stored locally (bootflash or harddisk). If the current boot image is a remote image or stored on an USB, NIM-SSD or such, ensure that you take a backup of the image before starting the factory reset process.

- Ensure that ISSU/ISSD (In- Service Software Upgrade or Downgrade) is not in progress before starting the factory reset process.

Restrictions

- Any software patches that are installed on the router will not be restored after the factory reset operation.

- If factory reset command is issued through a Virtual Teletype (VTY) session, the session is not restored after completion of factory reset process.

When to Use Factory Reset

- Return Material Authorization (RMA): If a router is returned back to Cisco for RMA, it is important that all sensitive information is removed.

- Router is Compromised: If the router data is compromised due to a malicious attack, the router must be reset to factory configuration and then reconfigured once again for further use.

- Repurposing: The router needs to be moved to a new topology or market from the existing site to a different site.

What Happens after Factory Reset

After factory reset is successfully completed, the router boots up. Before factory reset process is started, if the configuration register on the router is set to manually boot from ROMMON, then after factory reset the router will stop at ROMMON.

The factory reset process takes a backup of the boot image if the system is booted from an image stored locally (bootflash or harddisk). If the current boot image is a remote image or stored on an USB, NIM-SSD or such, ensure that you take a backup of the image before starting the factory reset process.

Preface

Revised: November 24, 2010, OL-17665-04

- Objectives

- Document Revision History

- Audience

- Organization

- Document Conventions

- Obtaining Documentation and Submitting a Service Request

Objectives

Document Revision History

This Document Revision History table records technical changes to this document.

October, 2008

Initial publication, including the following chapters:

- Verifying Hardware Installation

- Automatic Shutdown

- Monitoring Hardware Using Alarms

Cisco IOS XE 2.2

December, 2008

Modified the number of minutes from two to five for the router to shut down when a fan fails, per CSCsr59868. “Automatic Shutdown” chapter.

Cisco IOS XE 2.4

June, 2009

Added the following chapters:

- Monitoring the Control Plane

- Performing File System Cleanups

- Upgrading System Software

Cisco IOS XE 3.2S

November, 2010

Added the following chapter:

Configuring the Common Criteria Tcl Scripts

Audience

This document is intended for network operators who monitor and maintain networks for Cisco enterprise and service provider customers. Users of this document need a broad understanding of networks in general, networking principles, network configuration, and routing protocols.

Organization

This document contains the following sections:

Verifying Hardware Installation

Using LEDs and show commands to verify successful installation, and what to check if installation is unsuccessful.

2

Automatic Shutdown

Conditions under which the router and power supplies automatically shut down.

3

Monitoring Hardware Using Alarms

Using visual alarms, audible alarms, alarm messages sent to the console or syslog, and SNMP alarm notification to monitor hardware.

4

Configuring the Common Criteria Tcl Scripts

Configuring the Common Criteria Tcl scripts to monitor the packet drop event on the ASR 1000 Series Router.

5

Monitoring the Control Plane

Verifying the overall health of the system by monitoring control plane resources.

6

Monitoring File Systems

Maintaining proper router operation by performing cleanups of core, trace, crashinfo, and sub-package files .

7

Upgrading System Software

Upgrading software packages, including offline and in-service software upgrades. (Referred to the appropriate chapters in the Cisco ASR 1000 Series Aggregation Services Routers Software Configuration Guide.)

Document Conventions

Convention

Description

^ or Ctrl

The ^ and Ctrl symbols represent the Control key. For example, the key combination ^D or Ctrl-D means hold down the Control key while you press the D key. Keys are indicated in capital letters but are not case sensitive.

string

A string is a nonquoted set of characters shown in italics. For example, when setting an SNMP community string to public, do not use quotation marks around the string or the string will include the quotation marks.

Convention

Description

bold

Bold text indicates commands and keywords that you enter exactly as shown.

italics

Italic text indicates arguments for which you supply values.

[x]

Square brackets enclose an optional element (keyword or argument).

|

A vertical line indicates a choice within an optional or required set of keywords or arguments.

[x | y]

Square brackets enclosing keywords or arguments separated by a vertical line indicate an optional choice.

{x | y}

Braces enclosing keywords or arguments separated by a vertical line indicate a required choice.

Convention

Description

[x {y | z}]

Braces and a vertical line within square brackets indicate a required choice within an optional element.

Convention

Description

screen

Examples of information displayed on the screen are set in Courier font.

bold screen

Examples of text that you must enter are set in Courier bold font.

< >

Angle brackets enclose text that is not printed to the screen, such as passwords.

!

An exclamation point at the beginning of a line indicates a comment line. (Exclamation points are also displayed by the Cisco IOS software for certain processes.)

[ ]

Square brackets enclose default responses to system prompts.

The following conventions are used to attract the attention of the reader:

Caution Means reader be careful. In this situation, you might do something that could result in equipment damage or loss of data.

Note Means reader take note. Notes contain helpful suggestions or references to materials that may not be contained in this manual.

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What’s New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html