02-15-2017 01:14 AM
Hello All,
I have the following scenario, I have an ASR9006 and ASR9910 acting as Hosts, and an NCS5002 acting as Satellite, all devices are running IOS-XR 6.1.2, below is the config I am using and some of the show commands for your kind reference, the problem is the standby Host not taking over when the Active Host fails, I am simulating the failure by physically unplugging the port between the Active Host and the Satellite "the NCS5002" from the Satellite side.
NCS5002
-----------------------------------------------------------------
set
-----------------------------------------------------------------
I am using interfaces Te0/0/0/78 and interface Te0/0/0/79, I have no configuration on these interfaces aside from the description.
ASR9006
-----------------------------------------------------------------
Wed Feb 15 01:52:56.433 UTC
interface Loopback10
ipv4 address 10.0.0.1 255.255.255.255
!
-----------------------------------------------------------------
Wed Feb 15 01:53:39.352 UTC
interface TenGigE0/4/0/35
description ICCP-TO-ASR9006-Lab
ipv4 address 4.0.0.1 255.255.255.0
!
-----------------------------------------------------------------
Wed Feb 15 01:53:04.361 UTC
router static
address-family ipv4 unicast
10.0.0.2/32 4.0.0.2
!
-----------------------------------------------------------------
Wed Feb 15 01:54:56.957 UTC
redundancy
group 1
member
neighbor 10.0.0.2
!
backbone
interface TenGigE0/4/0/35
!
!
-----------------------------------------------------------------
Wed Feb 15 01:54:52.142 UTC
satellite 100
type ncs5002
redundancy
host-priority 10
!
serial-number FOC1946R0D2
!
-----------------------------------------------------------------
Wed Feb 15 01:55:07.271 UTC
interface TenGigE0/4/0/0
description TO-NCS5002-Lab
satellite-fabric-link satellite 100
redundancy
!
remote-ports TenGigE 0/0/0-79
!
!
-----------------------------------------------------------------
ASR9910
-----------------------------------------------------------------
Thu Feb 16 08:51:45.669 UTC
interface Loopback10
ipv4 address 10.0.0.2 255.255.255.255
!
-----------------------------------------------------------------
Thu Feb 16 08:51:40.249 UTC
interface TenGigE0/1/0/29
description ICCP-TO-A99K
ipv4 address 4.0.0.2 255.255.255.0
!
-----------------------------------------------------------------
Thu Feb 16 08:52:07.422 UTC
router static
address-family ipv4 unicast
10.0.0.1/32 4.0.0.1
!
-----------------------------------------------------------------
Thu Feb 16 08:52:27.752 UTC
redundancy
group 1
member
neighbor 10.0.0.1
!
backbone
interface TenGigE0/1/0/29
!
!
-----------------------------------------------------------------
Thu Feb 16 08:52:40.690 UTC
satellite 100
type ncs5002
redundancy
host-priority 20
!
serial-number FOC1946R0D2
!
-----------------------------------------------------------------
Thu Feb 16 08:53:09.081 UTC
interface TenGigE0/1/0/0
description TO_NCS5002_Lab
satellite-fabric-link satellite 100
redundancy
!
remote-ports TenGigE 0/0/0-79
!
-----------------------------------------------------------------
As for the verification, please find it below,
This is on the A99K the Active Host
-----------------------------------------------------------------
Wed Feb 15 02:01:50.810 UTC
Satellite 100
-------------
Status: Connected (Stable)
Redundancy: Active (Group: 1)
Type: ncs5002
Displayed device name: Sat100
MAC address: c472.95a7.a325
IPv4 address: 10.0.100.1 (auto, VRF: **nVSatellite)
Serial Number: FOC1946R0D2
Remote version: Compatible (latest version)
IOFPGA: 0.16
MB_MIFPGA: 0.16
DB_MIFPGA: 0.16
BIOS: 1.08
XR: 6.1.2 (Latest)
Received candidate fabric ports:
nVFabric-TenGigE0/0/78-79 (permanent)
nVFabric-HundredGigE0/1/0-3 (permanent)
Configured satellite fabric links:
TenGigE0/4/0/0
--------------
Status: Satellite Ready
Remote ports: TenGigE0/0/0-77,79
Rejected remote ports: TenGigE0/0/78
-----------------------------------------------------------------
Wed Feb 15 02:03:05.049 UTC
Redundancy Group 1
member
monitor: route-watch (up)
backbone interface Te0/4/0/35: up
enabled applications: SatelliteORBIT
isolation recovery delay timer: 180 s, not running
-----------------------------------------------------------------
On the Standby Host the ASR9006,
-----------------------------------------------------------------
Thu Feb 16 08:58:19.861 UTC
Satellite 100
-------------
Status: Discovery Stalled; Conflict: no Identification received yet
Type: ncs5002
IPv4 address: 10.0.100.1 (auto, VRF: **nVSatellite)
Serial Number: FOC1946R0D2
Configured satellite fabric links:
TenGigE0/1/0/0
--------------
Status: Discovery Stalled; Conflict: no Identification received yet
Remote ports: TenGigE0/0/0-79
Thu Feb 16 08:58:32.091 UTC
Redundancy Group 1
member
monitor: route-watch (up)
backbone interface Te0/1/0/29: up
enabled applications: SatelliteORBIT
isolation recovery delay timer: 180 s, not running
-----------------------------------------------------------------
Thank you so much for your help in advance.
Solved! Go to Solution.
02-16-2017 09:57 AM
ICCP is up between the two hosts, but there's a connectivity issue between the ASR9006 and the satellite. If you swap ICL cables on the satellite side, does the problem follow the satellite port or the host port?
02-16-2017 09:57 AM
ICCP is up between the two hosts, but there's a connectivity issue between the ASR9006 and the satellite. If you swap ICL cables on the satellite side, does the problem follow the satellite port or the host port?
02-17-2017 05:40 AM
Hello Aleksander,
Thank you for your kind support, I swapped the ICL cables before and the problem follows the Host port. Fortunately, I was able to find out what my problem was, I had used the same devices earlier to test the MC-LAG technology, the backbone interfaces had the "proxy-arp" command leftover from the previous Lab, when I removed it the problem was resolved, and I got the below results, now I am facing other problems that I think it is better to open another discussion for.
RP/0/RSP0/CPU0:ASR9006-Lab#sho nv satellite status
Sat Feb 18 12:40:25.072 UTC
Satellite 100
-------------
Status: Connected (Stable)
Redundancy: Active (Group: 1)
Type: ncs5002
Displayed device name: Sat100
MAC address: c472.95a7.a325
IPv4 address: 10.0.100.1 (auto, VRF: **nVSatellite)
Serial Number: FOC1946R0D2
Remote version: Compatible (latest version)
IOFPGA: 0.16
MB_MIFPGA: 0.16
DB_MIFPGA: 0.16
BIOS: 1.08
XR: 6.1.2 (Latest)
Received candidate fabric ports:
nVFabric-TenGigE0/0/78-79 (permanent)
nVFabric-HundredGigE0/1/0-3 (permanent)
Configured satellite fabric links:
TenGigE0/1/0/0
--------------
Status: Satellite Ready
Remote ports: TenGigE0/0/0-77
Rejected remote ports: TenGigE0/0/78-79
RP/0/RSP0/CPU0:ASR9006-Lab#
And on the A99K:
RP/0/RSP0/CPU0:A99k-Lab#sho nv s s
Fri Feb 17 05:46:05.645 UTC
Satellite 100
-------------
Status: Connected (Stable)
Redundancy: Standby (Group: 1) (Recovery Delay remaining: 4m 50s)
Type: ncs5002
Displayed device name: Sat100
MAC address: c472.95a7.a325
IPv4 address: 10.0.100.1 (auto, VRF: **nVSatellite)
Serial Number: FOC1946R0D2
Remote version: Compatible (latest version)
IOFPGA: 0.16
MB_MIFPGA: 0.16
DB_MIFPGA: 0.16
BIOS: 1.08
XR: 6.1.2 (Latest)
Received candidate fabric ports:
nVFabric-TenGigE0/0/78-79 (permanent)
nVFabric-HundredGigE0/1/0-3 (permanent)
Configured satellite fabric links:
TenGigE0/4/0/0
--------------
Status: Satellite Ready
Remote ports: TenGigE0/0/0-77
Rejected remote ports: TenGigE0/0/78-79
RP/0/RSP0/CPU0:A99k-Lab#
And When I simulate a failure scenario, the standby host would take over immediately.
Thank you again for your kind support.
Kind regards,
Ahmed Muhi
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide