×

Warning message

  • Cisco Support Forums is in Read Only mode while the site is being migrated.
  • Cisco Support Forums is in Read Only mode while the site is being migrated.

EEM to track a route on Nexus 7K

Unanswered Question
Aug 18th, 2013
User Badges:
  • Super Silver, 17500 points or more
  • Hall of Fame,

    Founding Member

  • Cisco Designated VIP,

    2017 LAN, WAN

I have a customer who is converting from a 6509 to Nexus 7K as their core switch. On the 6509 they have a floating static route and use the track function to detect loss of connectivity over the primary static default route and to fail over to the floating static route. Unfortunately Nexus 7K seems that track does not provide the functionality of controlling a static route or really of detecting loss of connectivity over the route. So I am wondering if it is possible to write something in EEM that would provide this function. What I think that I need to do is to ping some host over the primary route on a periodic basis. If I get x consecutive failures the script should change the config to remove the primary default route and allow the floating static to take over. When ping is successful y number of times the script should insert the primary static default route.


Has anyone done something like this? Any pointers on how to do this?


Thanks for your help.


Rick

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Joe Clarke Sun, 08/18/2013 - 13:48
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

This requires more capability in NX-OS EEM than exists today.  IOS supports IPSLA with object tracking whereas NX-OS does not.  While you could write a Tcl script to do the pinging, there is no timer event detector in NX-OS to trigger it.  This could be executed from the scheduler feature of NX-OS (similar to kron on IOS), but calling scripts from scheduler is not officially supported yet.  If you have new enough code, it will work, though.


If you do want to go this route, the trick will be storing the ping results to obtain your x/y numbers.  It might be easiest to do this in a file on flash.  I do have a sample NX-OS Tcl script at https://supportforums.cisco.com/docs/DOC-24068 you can use as a guide, at least for the CLI execution piece.

Richard Burts Sun, 08/18/2013 - 14:48
User Badges:
  • Super Silver, 17500 points or more
  • Hall of Fame,

    Founding Member

  • Cisco Designated VIP,

    2017 LAN, WAN

Joe


Thank you for the response. It confirms what I thought about the lack of support in NX-OS for what we want to do for tracking the route. I had hoped for a more supported option through EEM. The switch is running 6.1(2) so I will have a try at scheduler/tcl.


Thanks


Rick

Actions

This Discussion