Network Management

Hello, I've two Aruba 8320 switches deployed using VSX (Virtual Switching eXtension) running both ArubaOS-CX 10.01.0001.

I was able to successfully add both VSX's Switches (here Aruba-8320-1 and Aruba-8320-2) on HPE IMC using SNMPv3 but I see that lag128 - which, on both switches,  is the dedicated ISL LAG link - and the interface 1/1/48 - which, for both, is the ISL dedicated Keepalive link...are both shown in status "Unknown".

Question: is the HPE IMC actually able to represent VSX deployments based on ArubaOS-CX 10.01? 

VSX ISL (lag128 -- lag128):

VSX ISL (lag128 -- lag128) details:

VSX ISL Keepalive (1/1/48 -- 1/1/48) details:

 VSX is clearly operational:

Aruba-8320-1# show vsx status
VSX Operational State
---------------------
  ISL channel             : In-Sync
  ISL mgmt channel        : operational
  Config Sync Status      : in-sync
  NAE                     : peer_reachable
  HTTPS Server            : peer_reachable

Attribute           Local               Peer
------------        --------            --------
ISL link            lag128              lag128
ISL version         2                   2
System MAC          d0:67:26:xx:xx:xx   d0:67:26:yy:yy:yy
Platform            8320                8320
Software Version    TL.10.01.0001       TL.10.01.0001
Device Role         primary             secondary

Kind regards, Davide.

Hello ,

Can you please confirm which version of IMC you are using ? 

As i checked , some of the features for Aruba 8320 switch is not fully enabled on iMC . If you need more information realted to this, Kindly log a cases with HPE support. 

Hello! as written on the thread title...HPE IMC 7.3 E0605P04 (latest available and version used when I saw the issue although I know that HPE released a more hot fix E0605H05 these days)...we're going to open a support case as soon as we got the IMC Enterprise license registered and our IMC host will be up and running again (What we found related to Aruba 8320 deployed as a VSX cluster was tested on a 60 day free trial HPE IMC deployment we used as testbed, this 60 day free period ended -sigh - August, 28th 2018).

AFAIK VSX is too new (but MC-LAG, from what it was derived, is not) so I'm not too surprised that IMC is not actually able to recognize ISL related ports correctly...

Just a follow up: this issue is still valid using HPE IMC 7.3 E0605P06 (licensed Enterprise Ediiton)...on the other hand we haven't rised a support request in order to see if VSX status monitoring can be done by using HPE IMC 7.3 (I know that there are still some management - and monitoring too - restrictions about Aruba 8320/8400).