Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

NV edge Clustering ASR-9001-S

Hello everyone

 

I have a couple of identical ASR-9001-S,  can't get them to form a cluster, keep getting:

shelfmgr[406]: %PLATFORM-SHELFMGR_HAL-7-BOOT_REQ_FAILED : Invalid Boot Request from 0/RSP0/CPU0 rejected.  Incompatible chassis types

 

IOS XR 5.1.1

 

RP/0/RSP0/CPU0:ironman0#admin show license
Tue Apr  8 19:14:21.283 UTC

FeatureID: ASR9000_DEMO (Slot based, Evaluation[Valid])
  Total licenses 1
  Available for use         1
  Allocated to location     0
  Active                    0
  Store name             Permanent
  Store index               1
    Pool: Owner
      Total licenses in pool: 1
      Status: Available     1    Operational:    0


RP/0/RSP0/CPU0:ironman0#admin show license features
Tue Apr  8 19:14:26.390 UTC

Platform Feature ID:
  A9K-iVRF-LIC
  A9K-9001-AIP-LIC
  A9K-9001-OPT-LIC
  A9K-9001-VID-LIC
  A9K-NVSAT1-LIC
  A9K-NVSAT5-LIC
  A9K-NVSAT20-LIC
  A9K-NV-CLUSTR-LIC
  A9K-BNG-LIC-8K
  A9K-9001-MOB-LIC

 

 

RP/0/RSP0/CPU0:ironman0#show hw-module fpd location all
Tue Apr  8 19:26:33.099 UTC

===================================== ==========================================
                                      Existing Field Programmable Devices
                                      ==========================================
                                        HW                       Current SW Upg/
Location     Card Type                Version Type Subtype Inst   Version   Dng?
============ ======================== ======= ==== ======= ==== =========== ====
0/RSP0/CPU0  ASR9001-RP                 1.0   lc   fpga2   0       1.14     No
                                              lc   cbc     0      22.114    No
                                              lc   rommon  0       2.03     No
--------------------------------------------------------------------------------
0/FT0/SP     ASR-9001-FAN               1.0   ft   cbc     7      24.115    No
--------------------------------------------------------------------------------
0/0/CPU0     ASR9001-LC-S               1.0   lc   cbc     0      23.114    No
                                              lc   fpga2   0       1.18     No
                                              lc   fpga4   0       2.10     No
                                              lc   rommon  0       2.03     No
--------------------------------------------------------------------------------
0/0/0        A9K-MPA-4X10GE             1.0   spa  fpga6   0       1.06     No
--------------------------------------------------------------------------------

 

 

Any suggestions would be appreciated.

 

Thank you,

 

Regards,

Elnur

 

 

  • XR OS and Platforms
Everyone's tags (2)
1 ACCEPTED SOLUTION

Accepted Solutions
Cisco Employee

Hi Elnur,

Hi Elnur,

 

We are actually working on putting out a troubleshooting note on this.

Here are the details.

 

 

Problem Description:

When booting up an ASR9K in a, Nv Edge (cluster) environment the following error message may be displayed and the boot process aborted.

 

 

mbi_val_process_packet: received repsonse (rack 1)
Received do not boot message: [min ver: 00.00] reason 6
Don't boot reason: Incompatible chassis types
MBI Validation aborted

 

 

 

There are three scenarios where we may see this 'Incompatible chassis types' error message.

Scenario 1 and 2 ONLY apply to the ASR-9001-S while scenario 3 applies to any ASR9K chassis.

 

 

1.

In this scenario there are two 9001-S chassis which are being clustered.

 

If one 9001-S has been upgraded to 120G but the second 9001-S is only running 60G then the incompatible chassis types error message will be displayed when booting the second router.

 

In order to fix the incompatibility make sure that both routers are upgraded (120G) or not upgraded (60G).

The command show license log operational can be used to check if the license is active.

 

In this example the 120G license is not operational.

RP/0/RSP0/CPU0:ASR9001#show license log operational
#ID     :SDR     :FeatureID       :NodeID    :Time:   Log
15      :Owner   :A9K-9001-120G-LIC:0/RSP0/CPU0:Wed Oct 16 05:44:35 2013: 
license_acquire: opaque_string (null), result('License Manager' detected the 
'warning' condition 'Licensed feature does not exist')



In this example the 120G license is operational

RP/0/RSP0/CPU0:ASR9001#show license log operational
#ID     :SDR     :FeatureID       :NodeID    :Time:   Log
1       :Owner   :A9K-9001-120G-LIC:0/RSP0/CPU0:Sat Mar 15 00:22:09 2014: license_acquire: opaque_string (null), result(No error) 

 

 

2.

In this scenario there are two 9001-S chassis in a cluster and neither chassis has been upgraded to 120G (see scenario 1 for verification).

 

The cause of this issue is the IML variable being incorrectly set to 1 in ROMMON. This variable should ONLY be set to 1 once the chassis is upgraded to 120G.

To resolve this issue set the IML variable to 0.

 

rommon B1 > IML=0
rommon B2 > sync
rommon B3 > boot 

 

 

3.

In this scenario two dissimilar chassis types are in a cluster.

 

ASR9K nV Edge does not allow dissimmilar chassis to form a cluster. During bootup the system will check the chassis type for the purpose of clustering capabilities. Any dissimilar combination can hit this issue, such as 9010 to 9922 or 9001 to 9006.

 

In order to verify the chassis type use the command admin show diag chassis eeprom-info in XR or the bpcookie command in ROMMON.

The below example shows the output for a ASR-9001 from both XR and ROMMON.

 

RP/0/RSP0/CPU0:ASR9001#admin show diag chassis eeprom-info
Rack 0 - ASR-9001 Chassis
        Controller Family       : ef
        Controller Type         : 400
        PID                     : ASR-9001


rommon B1 > bpcookie
bpcookie:
        Controller Family        : ef
        Controller Type          : 400
        Product Number           : ASR-9001 

 

 

HTH,

Sam

 

2 REPLIES
Cisco Employee

Hi Elnur,

Hi Elnur,

 

We are actually working on putting out a troubleshooting note on this.

Here are the details.

 

 

Problem Description:

When booting up an ASR9K in a, Nv Edge (cluster) environment the following error message may be displayed and the boot process aborted.

 

 

mbi_val_process_packet: received repsonse (rack 1)
Received do not boot message: [min ver: 00.00] reason 6
Don't boot reason: Incompatible chassis types
MBI Validation aborted

 

 

 

There are three scenarios where we may see this 'Incompatible chassis types' error message.

Scenario 1 and 2 ONLY apply to the ASR-9001-S while scenario 3 applies to any ASR9K chassis.

 

 

1.

In this scenario there are two 9001-S chassis which are being clustered.

 

If one 9001-S has been upgraded to 120G but the second 9001-S is only running 60G then the incompatible chassis types error message will be displayed when booting the second router.

 

In order to fix the incompatibility make sure that both routers are upgraded (120G) or not upgraded (60G).

The command show license log operational can be used to check if the license is active.

 

In this example the 120G license is not operational.

RP/0/RSP0/CPU0:ASR9001#show license log operational
#ID     :SDR     :FeatureID       :NodeID    :Time:   Log
15      :Owner   :A9K-9001-120G-LIC:0/RSP0/CPU0:Wed Oct 16 05:44:35 2013: 
license_acquire: opaque_string (null), result('License Manager' detected the 
'warning' condition 'Licensed feature does not exist')



In this example the 120G license is operational

RP/0/RSP0/CPU0:ASR9001#show license log operational
#ID     :SDR     :FeatureID       :NodeID    :Time:   Log
1       :Owner   :A9K-9001-120G-LIC:0/RSP0/CPU0:Sat Mar 15 00:22:09 2014: license_acquire: opaque_string (null), result(No error) 

 

 

2.

In this scenario there are two 9001-S chassis in a cluster and neither chassis has been upgraded to 120G (see scenario 1 for verification).

 

The cause of this issue is the IML variable being incorrectly set to 1 in ROMMON. This variable should ONLY be set to 1 once the chassis is upgraded to 120G.

To resolve this issue set the IML variable to 0.

 

rommon B1 > IML=0
rommon B2 > sync
rommon B3 > boot 

 

 

3.

In this scenario two dissimilar chassis types are in a cluster.

 

ASR9K nV Edge does not allow dissimmilar chassis to form a cluster. During bootup the system will check the chassis type for the purpose of clustering capabilities. Any dissimilar combination can hit this issue, such as 9010 to 9922 or 9001 to 9006.

 

In order to verify the chassis type use the command admin show diag chassis eeprom-info in XR or the bpcookie command in ROMMON.

The below example shows the output for a ASR-9001 from both XR and ROMMON.

 

RP/0/RSP0/CPU0:ASR9001#admin show diag chassis eeprom-info
Rack 0 - ASR-9001 Chassis
        Controller Family       : ef
        Controller Type         : 400
        PID                     : ASR-9001


rommon B1 > bpcookie
bpcookie:
        Controller Family        : ef
        Controller Type          : 400
        Product Number           : ASR-9001 

 

 

HTH,

Sam

 

New Member

Hi SamIt turns out it was IML

Hi Sam

It turns out it was IML in my case, appreciate your response!!!

 

Thank you 

 

Cheers

Elnur

781
Views
0
Helpful
2
Replies
This widget could not be displayed.