cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
904
Views
0
Helpful
8
Replies

ASR 9000v sat fails to come up CRS 5.1.3

Aaziz AMHAOUCH
Level 1
Level 1

Hi all,

We have a problem in ASR 9000v Satellitte with CRS 5.1.3, it doesn't come UP :

RP/0/RP0/CPU0:CRS#sh nv satellite status 
Tue Mar  3 11:54:14.305 UTC
Satellite 200
-------------
  Status: Discovery Stalled; Conflict: no Identification received yet
  Type: asr9000v
  IPv4 address: 10.0.0.2 (VRF: NV-MGMT-VRF)
  Configured satellite fabric links:
    TenGigE0/0/0/10
    ---------------
      Status: Discovery Stalled; Conflict: no Identification received yet
      Remote ports: GigabitEthernet0/0/0-43
RP/0/RP0/CPU0:CRS#

 

The configuration is as follow:

vrf NV-MGMT-VRF
 address-family ipv4 unicast

 

interface Loopback1000
 vrf NV-MGMT-VRF
 ipv4 address 10.0.0.1 255.255.255.0
!
!
interface TenGi0/0/0/10
 vrf NV-MGMT-VRF
 ipv4 point-to-point
 ipv4 unnumbered Loopback1000
 nv
 satellite-fabric-link satellite 200
 remote-ports GigabitEthernet 0/0/0-43
 
nv satellite 200

 ipv4 address 10.0.0.2 / 24

 type asr900v

 

Thanks for your help !

BR

1 Accepted Solution

Accepted Solutions

If you need this implemented immediately then you will need the CRS-3 LC.

If you can wait a few months for 5.3.1 then you can use the CRS-X LCs and upgrade the router.

 

Thanks,

Sam

View solution in original post

8 Replies 8

smilstea
Cisco Employee
Cisco Employee

The type under nv satellite 200 is incorrect.

 

'debug nv sat internal dpm all sat 200 detail' will tell us if the software is trying to generate the discovery probes, and the interface counters will tell us if the discovery packets are going out towards the satellite or if the satellite is responding. Discovery messages are sent every second.

 

HTH,

Sam

 

Hi Sam,

the config under nv is:

nv
 satellite 200
  type asr9000v
  ipv4 address 10.0.0.2
 !

show interfaces:

TenGigE0/0/0/10 is up, line protocol is down 
  Interface state transitions: 147
  Hardware is TenGigE, address is 7426.ac47.0533 (bia 7426.ac47.0533)
  Description: Link_toward_nV_Satellite
  Internet address is 10.0.0.1/24
  MTU 1514 bytes, BW 10000000 Kbit (Max: 10000000 Kbit)
     reliability 255/255, txload 0/255, rxload 0/255
  Encapsulation ARPA,
  Full-duplex, 10000Mb/s, LR, link type is force-up
  output flow control is off, input flow control is off
  loopback not set,
  ARP type ARPA, ARP timeout 04:00:00
  Last input never, output 18:14:06
  Last clearing of "show interface" counters never
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
     0 packets input, 0 bytes, 0 total input drops
     0 drops for unrecognized upper-level protocol
     Received 0 broadcast packets, 0 multicast packets
              0 runts, 0 giants, 0 throttles, 0 parity
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
     2 packets output, 120 bytes, 0 total output drops
     Output 2 broadcast packets, 0 multicast packets
     0 output errors, 0 underruns, 0 applique, 0 resets
     0 output buffer failures, 0 output buffers swapped out
     147 carrier transitions


RP/0/RP0/CPU0:CRS#

The result of debugging is :

RP/0/RP0/CPU0:CRS#LC/0/0/CPU0:Mar  4 05:49:28.252 : icpe_satfabmgr[193]: [I:dpm-io:0308] Attaching max of 1 interfaces
LC/0/0/CPU0:Mar  4 05:49:28.252 : icpe_satfabmgr[193]: [B:dpm-io:0348] Failed to SPIO attach/detach 1 interfaces: 'Subsystem(3795)' detected the 'warning' condition 'Code(4)'

BR,

Please open a TAC case for troubleshooting, the discovery probes are not being generated / sent out.

 

Thanks,

Sam

Hi Sam,

Many thanks for your help Sam, It's a CRS-X and you told us tha nvSat is not supported on CRS-X hardware. Is it a compatibility problem with PLIM 40x10G so we can use PLIM 14x10 G or it's not supported on CRS-X chassis ?

BR,

Aaziz

Hi Aaziz,

 

Just responded to your email.

The issue is the MSC/PLIM. CRS-X LCs will support satellite starting in 5.3.1.

A 14x10GE CRS-3 card will support satellite.

 

Thanks,

Sam

Hi Sam,

 

I tested the nv Satellite in CRS-X ver 5.1.3 using a 14x10GE  and it works :

RP/0/RP0/CPU0:CRS#admin sh platform 
Wed Mar 11 08:55:35.705 UTC
Node          Type              PLIM               State           Config State
------------- ----------------- ------------------ --------------- ---------------
0/0/CPU0      FP-X              40-10GbE           IOS XR RUN      PWR,NSHUT,MON
0/1/CPU0      FP-140G           14-10GbE           IOS XR RUN      PWR,NSHUT,MON
0/RP0/CPU0    RP(Active)        N/A                IOS XR RUN      PWR,NSHUT,MON
0/RP1/CPU0    RP(Standby)       N/A                IOS XR RUN      PWR,NSHUT,MON
0/SM0/SP      FC-400G/S(H)(SP)  N/A                IOS XR RUN      PWR,NSHUT,MON
0/SM1/SP      FC-400G/S(H)(SP)  N/A                IOS XR RUN      PWR,NSHUT,MON
0/SM2/SP      FC-400G/S(H)(SP)  N/A                IOS XR RUN      PWR,NSHUT,MON
0/SM3/SP      FC-400G/S(H)(SP)  N/A                IOS XR RUN      PWR,NSHUT,MON

 

RP/0/RP0/CPU0:CRS#sh nv satellite status satellite 200
Wed Mar 11 08:56:44.244 UTC
Satellite 200
-------------
  Status: Connected (Stable)
  Type: asr9000v
  MAC address: <....>
  IPv4 address: 10.0.0.2 (VRF: NV-MGMT-VRF)
  Serial Number: <...>
  Remote version: Compatible (not latest version)
    ROMMON: 127.0 (Latest)
    FPGA: 1.13 (Latest)
    IOS: 323.1 (Available: 338.1)
  Configured satellite fabric links:
    TenGigE0/1/0/0
    --------------
      Status: Satellite Ready
      Remote ports: GigabitEthernet0/0/0-43
RP/0/RP0/CPU0:CRS#

 

What is your recommendation about this ?

Many Thanks,

BR,

Aaziz

If you need this implemented immediately then you will need the CRS-3 LC.

If you can wait a few months for 5.3.1 then you can use the CRS-X LCs and upgrade the router.

 

Thanks,

Sam

ok Sam,

Thank you very much for your help :)

BR,

Aaziz