cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2749
Views
25
Helpful
5
Replies

ASR1001 "Major" LED since IOSXE upgrade

ropeadope
Level 1
Level 1

Hello,

I have recently upgraded two ASR1001s to a new IOS-XE version, and the "Major" LED light is on for both of them now.

ASR-1#show facility-alarm status

System Totals  Critical: 1  Major: 1  Minor: 0

Source              Severity      Description [Index]

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

Power Supply Module 0      CRITICAL      Power Supply Failure [0]

module 0                   MAJOR         Boot state [1]

xcvr container 0/0/1       INFO          Transceiver Missing [0]

xcvr container 0/0/2       INFO          Transceiver Missing [0]

GigabitEthernet0           INFO          Physical Port Administrative State Down

It's indicating something with the boot state. The "Critical" alarm is not a concern because it goes away when the second Power supply is plugged in.

When the boot marker uses the previous IOS image to boot from, the Major alert goes away. Here is the boot config:

boot-start-marker

boot system flash bootflash:asr1001-universalk9.03.10.02.S.153-3.S2-ext.bin

boot-end-marker

ASR-1#show bootvar

BOOT variable = bootflash:asr1001-universalk9.03.10.02.S.153-3.S2-ext.bin,1;

CONFIG_FILE variable does not exist

BOOTLDR variable does not exist

Configuration register is 0x2102

Standby not ready to show bootvar

The device performs as expected, with no issues I can see. Any suggestions? On bootup, there is a message about initiatilization taking longer than expected:

Boot image size = 376844620 (0x1676314c) bytes

Package header rev 0 structure detected

Calculating SHA-1 hash...done

validate_package: SHA-1 hash:

        calculated 498d334d:12861c50:69d2791e:29e2fc98:6597e1bf

        expected   498d334d:12861c50:69d2791e:29e2fc98:6597e1bf

Image validated

%IOSXEBOOT-4-BOOT_ACTIVITY_LONG_TIME: (rp/0): Chasfs initialisation took: 20 seconds, expected max time 10 seconds

5 Replies 5

Iulian Vaideanu
Level 4
Level 4

I've only had some experience with ASRs 1002 and 1004, but what was the previous IOS XE version on the device and what does the output of "show platform" look like?

Here is the previous IOS version as opposed to the new one:

asr1001-universal.03.07.00.S.152-4.S.bin

The only difference is that one of them is the K9 image and the other one isn't.

Below is the output of "show platform". Again, the CRITICAL alarm goes away when I plug the second power supply in, but the MAJOR one stays on.

ASR-1#show platform

Chassis type: ASR1001

Slot      Type                State                 Insert time (ago)

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

0         ASR1001             ok                    18:15:58

0/0      ASR1001             ok                    18:14:56

R0        ASR1001             ok, active            18:15:58

F0        ASR1001             ok, active            18:15:58

P0        ASR1001-PWR-AC      ps, fail              18:15:23

P1        ASR1001-PWR-AC      ok                    18:15:23

P2        ASR1001-FANTRAY     ok                    18:15:25

Slot      CPLD Version        Firmware Version

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

0         10042219            15.0(1r)S

R0        10042219            15.0(1r)S

F0        10042219            15.0(1r)S

You said there's no performance degradation, so there's a chance it might just be a "cosmetic" issue...  It probably wouldn't hurt to have the ROMMONs updated to at least 15.2(1r)S, which I see is the recommended version for ASR1001, no matter the IOS XE release.

Thanks, Lulian. I updated the ROMMON code to 15.3 but the boot LED still persists. I'm thinking you're right and this either a bug or a cosmetic issue. Going to close this out. Thanks.

Hi all,

 

Quite an old post now but thought I would share below.

 

I encountered the same and did this:

 

  • Installed asr1001-universalk9.03.16.05.S.155-3.S5-ext.bin
  • Deleted asr1001-universalk9.03.10.02.S.153-3.S2-ext.bin
  • Performed Shut command GigabitEthernet0/0/0 to GigabitEthernet0/0/3

 

Before:

 

Router#show facility-alarm status
System Totals Critical: 1 Major: 1 Minor: 0

Source Severity Description [Index]
------ -------- -------------------
module 0 MAJOR Boot state [1]
xcvr container 0/0/0 INFO Transceiver Missing [0]
xcvr container 0/0/1 INFO Transceiver Missing [0]
xcvr container 0/0/2 INFO Transceiver Missing [0]
GigabitEthernet0/0/3 INFO Physical Port Administrative State Down

 

 

After:

 

Router#show facility-alarm status
System Totals Critical: 0 Major: 0 Minor: 0

Source Time Severity Description [Index]
------ ------ -------- -------------------
xcvr container 0/0/0 Jun 12 2019 10:04:26 INFO Transceiver Missing [0]
xcvr container 0/0/1 Jun 12 2019 10:05:21 INFO Transceiver Missing [0]
xcvr container 0/0/2 Jun 12 2019 10:04:32 INFO Transceiver Missing [0]
xcvr container 0/0/3 Jun 12 2019 10:04:37 INFO Transceiver Missing [0]
GigabitEthernet0 Jun 12 2019 10:04:59 INFO Physical Port Administrative State Down [2]

 

Summary:

 

In my case the software upgrade to asr1001-universalk9.03.16.05.S.155-3.S5-ext.bin did the trick removing Major Alarm

 

Shutting down interfaces GigabitEthernet0/0/0 to GigabitEthernet0/0/3 removing Critical Alarm

Review Cisco Networking products for a $25 gift card