Cisco NCS 5504: Route redistribution configuration.

[mamunabdullah]

Hi,

I want to redistribute the static routes to EIGRP with customized matric based on ipsla tacking. As the NCS configuration pattern is little different from normal ISR/ASR. Can anyone share a sample? Or validate my draft. 

ipsla
operation 230 type icmp echo source address 10.10.10.1
operation 230 type icmp echo destination address 20.20.20.2
operation 230 type icmp echo timeout 5000
operation 230 type icmp echo frequency 5
!
schedule operation 230 start-time now
schedule operation 230 life forever
!
exit
!
------------------------------------------------------------------------------------
track 30 type rtr 230 reachability
!
------------------------------------------------------------------------------------
prefix-set AAA
192.168.230.0/24
end-set
!
prefix-set BBB
192.168.232.0/24
end-set
!

prefix-set Others
30.30.30.0/24,

40.40.40.0/24

end-set
!
---------------------------------------------------------------------------------------
router static address-family ipv4 unicast 192.168.230.0/24 10.10.10.2 1 description AAA
router static address-family ipv4 unicast 192.168.232.0/24 10.10.10.2 1 description BBB
router static address-family ipv4 unicast 20.20.20.2/32 10.10.10.2 1 description track!

router static address-family ipv4 unicast 30.30.30.0/32 172.16.31.2 1 description CCC

router static address-family ipv4 unicast 40.40.40.0/32 172.16.31.2 1 description CCC

!

exit
!
------------------------------------------------------------------------------------
route-policy static_into_eigrp
if (destination in AAA and track 30 is up) then
set eigrp-metric 1000000 1000 255 255 1500
endif
if (destination in AAA and track 30 is down) then
set eigrp-metric 10000 1000 255 255 1500
endif
if (destination in BBB and track 32 is up) then
set eigrp-metric 10000 1000 255 255 1500
endif
if (destination in BBB and track 32 is down) then
set eigrp-metric 1000 1000 255 255 1500
endif
if (destination in Others) then
set eigrp-metric 1000000 100 255 255 1500
endif
!
exit
!
------------------------------------------------------------------------------------
router eigrp 100
address-family ipv4
redistribute static route-policy static_into_eigrp
!

-----------------------------------------------End------------------------------------

Thanks,

Mamun.

[khorram1998]

The configuration you have provided looks like a good starting point for redistributing static routes into EIGRP with customized metrics based on IPSLA tracking. It appears you have created IPSLA operations and a schedule, defined a track object to track the reachability of an IP address based on the IPSLA operation, created prefix-sets for different IP ranges, and configured static routes for those ranges. Then, you have created a route-policy that checks the destination IP address against the prefix-sets and sets the EIGRP metric accordingly based on the reachability status of the tracked IP address. Lastly, you have configured EIGRP to redistribute the static routes with the specified route-policy.

However, there are a few things that need to be corrected in the configuration provided:

1. The track object's number is 30, but it references operation 230. It should be track 230 instead.
2. The track object is checking "reachability" but the operation is "icmp echo" operation. It should be track 230 type rtr 230 icmp-echo instead.
3. The prefix-set "Others" is not closed properly. It should be end-set after the last IP prefix.
4. The static route for IP address 20.20.20.2/32 doesn't match any of the prefix-sets, so it will not be redistributed by EIGRP.
5. The static route for IP address 30.30.30.0/24 and 40.40.40.0/24 should have next-hop IP address instead of the description "CCC"
6. Also, you will have to configure EIGRP on the interface facing the other network to redistribute the EIGRP routes.

I hope this helps, let me know if you have any more questions.

Please rate this and mark as solution/answer, if this resolved your issue
All the best,
AK

[mamunabdullah]

Hi,

Thanks for your time, and recommendations.

But as per your 2nd correction, i do not find any rtr type as "icmp-echo". Please have a look,

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

RP/0/RP0/CPU0:RT-NCS-5504(config)#track 230 type rtr 230 ?
reachability Tracks whether the route is reachable
RP/0/RP0/CPU0:RT-NCS-5504(config)#track 230 type rtr 230

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

[khorram1998]

I apologize for the confusion, it seems that the "icmp-echo" option is not available on the NCS 5504 platform.

Instead of using "icmp-echo" you can use the "reachability" option for the route tracking to track the reachability of the route.

You can configure the route tracking using the following command:

track <track-id> type rtr <rtr-id> reachability

Example: track 230 type rtr 230 reachability

This will track the reachability of the route with RTR ID 230. If the route becomes unreachable, the corresponding routing protocol will withdraw the route.

Please let me know if you have any further questions.

Please rate this and mark as solution/answer, if this resolved your issue
All the best,
AK