Wired Intelligent Edge (Campus Switching and Routing)

Reply
Highlighted
MVP Expert

ArubaOS-CX: show running config vsx doesn't show keepalive interface context

Just a note.

 

On ArubaOS-CX - VSX - running show running config vsx shows all related VSX configured contexts except the one used to define VSX ISL Keepalive interface (physical or logical, doesn't matter).

 

Davide.

Re: ArubaOS-CX: show running config vsx doesn't show keepalive interface context

As ISL keepalive is a UDP probe, the source and destination IP addresses are not related to VSX, so it the interfaces used for keepalive do not appear in show run vsx.

 

However, do you have any particular need that the current CLI does not cover in this respect ?

 

 

MVP Expert

Re: ArubaOS-CX: show running config vsx doesn't show keepalive interface context

Hi Vincent!

 

My thought was that anything related to basic VSX implementation (and ISL along with its Keepalive IMHO are essential part of a VSX implementation) should appear when show running config vsx command is invoked...thus providing running configuration of VSX should mean to follow an all-or-nothing approach...indeed...why showing that configured VSX is using a dedicated VRF for ISL Keepalive providing peer IP addresses information (the below line appears on vsx context):

 

keepalive peer X.X.X.X source Y.Y.Y.Y vrf ISL-KEEPALIVE-VRF-NAME

... and concurrently not showing also that a particular physical interface (or a LAG) ROP configured:

 

interface 1/1/N (N on VSX Node 1, M on VSX Node 2, eventually N=M)
  description ISL-Keepalive
  no shutdown
  vrf attach ISL-KEEPALIVE-VRF-NAME
  ip address X.X.X.X/30 (X.X.X.X on VSX Node 1, Y.Y.Y.Y on VSX Node 2, /30 for convenience)

...is exactly used for that?

 

It looks like show running configuration vsx command reports only contexts (or configuration lines) of vsx, vsx interface involved with that VSX ISL (inter-switch-link), VSX LAGs and interfaces involved with those VSX LAGs..it thus shows just the presence of a dedicated VRF (since it is included into the vsx context) for its ISL Keepalive but it.excludes all the information shown above on where - physically more than logically - the ISL Keepalive feature is running on.

 

Hope these thoughts make sense...

Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: