Wired Intelligent Edge

 View Only
last person joined: yesterday 

Bring performance and reliability to your network with the Aruba Core, Aggregation, and Access layer switches. Discuss the latest features and functionality of the ArubaOS-Switch and ArubaOS-CX devices, and find ways to improve security across your network to bring together a mobile first solution.
Expand all | Collapse all

Aruba 5400R zl2 VSF OoBM MAD (via direct inter-link)

This thread has been viewed 20 times
  • 1.  Aruba 5400R zl2 VSF OoBM MAD (via direct inter-link)

    MVP GURU
    Posted Aug 12, 2019 06:24 AM

    Hello all,

     

    I need a clarification about how VSF OoBM MAD on our Aruba 5400R zl2 were setup...actually there is a direct link between both OoBM ports and I recall I've set IP addressing on both OoBM using appropriate VSF OoBM commands.

     

    What I actually see is this:

     

    VSF# show oobm vsf member 1
    
     VSF Member 1 
      OOBM Port Type         : 100/1000T   
      OOBM Interface Status  : Up              
      OOBM Port              : Enabled     
      OOBM Port Speed        : Auto        
      MAC Address            : f40343-XXXXXX    
    
    VSF# show oobm vsf member 2
    
     VSF Member 2 
      OOBM Port Type         : 100/1000T   
      OOBM Interface Status  : Up              
      OOBM Port              : Enabled     
      OOBM Port Speed        : Auto        
      MAC Address            : f40343-YYYYYY
    
    
    VSF# show oobm ip                              
    
      IPv4 Status          : Enabled 
      IPv4 Default Gateway :                                               
    
                |                                     Address  Interface
     VSF-member | IP Config IP Address/Prefix Length  Status   Status   
     ---------- + --------- ------------------------- -------- ---------
     Global     | dhcp                                Active   Up       
     1          | dhcp      10.100.100.1/24           Active   Up       
     2          | manual    10.100.100.2/24           Active   Up       
    
    VSF# show oobm ip vsf member all
    
      IPv4 Status          : Enabled 
      IPv4 Default Gateway :                                               
    
                |                                     Address  Interface
     VSF-member | IP Config IP Address/Prefix Length  Status   Status   
     ---------- + --------- ------------------------- -------- ---------
     1          | dhcp      10.100.100.1/24           Active   Up       
     2          | manual    10.100.100.2/24           Active   Up       
    
    VSF# show oobm ip vsf member 1  
    
      IPv4 Status          : Enabled 
      IPv4 Default Gateway :                                               
    
                |                                     Address  Interface
     VSF-member | IP Config IP Address/Prefix Length  Status   Status   
     ---------- + --------- ------------------------- -------- ---------
     1          | dhcp      10.100.100.1/24           Active   Up       
    
    VSF# show oobm ip vsf member 2
    
      IPv4 Status          : Enabled 
      IPv4 Default Gateway :                                               
    
                |                                     Address  Interface
     VSF-member | IP Config IP Address/Prefix Length  Status   Status   
     ---------- + --------- ------------------------- -------- ---------
     2          | manual    10.100.100.2/24           Active   Up       
    
    

    And the running configuration reports:

     

    VSF# show running-config oobm  
    
    Running configuration:
    
    oobm
       ip address dhcp-bootp
       vsf member 1
          ip address 10.100.100.1 255.255.255.0
          ip default-gateway 10.100.100.2
          exit
       vsf member 2
          ip address 10.100.100.2 255.255.255.0
          ip default-gateway 10.100.100.1
          exit
       exit

    What make me feel uncomfortable is seeing (a) that VSF Member "1" seems to have a DHCP assigned IP Address for its OoBM Port...and (b) I don't understand what is the role of VSF Member "Global" with regard to OoBM...looking at the running configuration I thought I should have simply ended up instead with something like (granted that Global is something I still need to understand [*]):

     

    VSF# show oobm ip                              
    
      IPv4 Status          : Enabled 
      IPv4 Default Gateway :                                               
    
                |                                     Address  Interface
     VSF-member | IP Config IP Address/Prefix Length  Status   Status   
     ---------- + --------- ------------------------- -------- ---------
     Global     | dhcp                                Active   Up       
     1          | manual    10.100.100.1/24           Active   Up       
     2          | manual    10.100.100.2/24           Active   Up       
    
    VSF# show oobm ip vsf member all
    
      IPv4 Status          : Enabled 
      IPv4 Default Gateway :                                               
    
                |                                     Address  Interface
     VSF-member | IP Config IP Address/Prefix Length  Status   Status   
     ---------- + --------- ------------------------- -------- ---------
     1          | manual    10.100.100.1/24           Active   Up       
     2          | manual    10.100.100.2/24           Active   Up       
    
    VSF# show oobm ip vsf member 1  
    
      IPv4 Status          : Enabled 
      IPv4 Default Gateway :                                               
    
                |                                     Address  Interface
     VSF-member | IP Config IP Address/Prefix Length  Status   Status   
     ---------- + --------- ------------------------- -------- ---------
     1          | manual    10.100.100.1/24           Active   Up       
    
    VSF# show oobm ip vsf member 2
    
      IPv4 Status          : Enabled 
      IPv4 Default Gateway :                                               
    
                |                                     Address  Interface
     VSF-member | IP Config IP Address/Prefix Length  Status   Status   
     ---------- + --------- ------------------------- -------- ---------
     2          | manual    10.100.100.2/24           Active   Up
     

    where the VSF Member "1" uses a statically assigned IP Address - 10.100.100.1 - for its OoBM Port...

     

    Should I remove all and redo the VSF OoBM MAD configurations for Global, 1 and 2 VSF Members? Any idea?

     

    [*] Edit: this article clarifies things a bit even if looking at Management and Configuration Guide doesn't provide the very same explanation to deploy VSF OoBM MAD



  • 2.  RE: Aruba 5400R zl2 VSF OoBM MAD (via direct inter-link)

    EMPLOYEE
    Posted Aug 12, 2019 12:47 PM

    Greetings!

     

    OoBM in a VSF configuration on the 5400R allows you to both configure addresses for the individual VSF member chassis, but also a global OoBM IP address that can be used to access the stack regardless of which member is the current stack Commander.

     

    If you're using OoBM purely for MAD purposes, you do not need to configure a global IP address, and can simply use the individual member OoBM IP addresses as they are currently configured.



  • 3.  RE: Aruba 5400R zl2 VSF OoBM MAD (via direct inter-link)

    Posted May 16, 2022 10:40 PM
    Hi Parnassus,
    Did you end up fixing the issue with one of your oobm port stating it was via DHCP instead of manual?
    I have a similar situation on my 2 5406Rzl2 VSF switches, which are indirectly connected together via a 4-member 5700 IRF switch:

    VSFswitch# sh oobm ip

    IPv4 Status : Enabled
    IPv4 Default Gateway :

    | Address Interface
    VSF-member | IP Config IP Address/Prefix Length Status Status
    ------------------- + -------------- -------------------------------------- -------- ---------
    Global            | dhcp                                                         Active Up
    1                      | dhcp         10.10.3.7/24                          Active Up
    2                      | manual    10.10.3.8/24                          Active Up



    VSFswitch# sh oobm vsf member 1

    VSF Member 1
    OOBM Port Type : 100/1000T
    OOBM Interface Status : Up
    OOBM Port : Enabled
    OOBM Port Speed : Auto
    MAC Address : f860f0-fc6701

    VSFswitch# sh oobm vsf member 2

    VSF Member 2
    OOBM Port Type : 100/1000T
    OOBM Interface Status : Up
    OOBM Port : Enabled
    OOBM Port Speed : Auto
    MAC Address : f860f0-fc0801



    VSFswitch# sh oobm ip vsf member all

    IPv4 Status : Enabled
    IPv4 Default Gateway :

    | Address Interface
    VSF-member | IP Config IP Address/Prefix Length Status Status
    ------------------- + -------------- --------------------------------------- -------- ---------
    1                      | dhcp         10.10.3.7/24                          Active Up
    2                      | manual    10.10.3.8/24                         Active Up




    VSFswitch# sh running-config oobm

    Running configuration:

    oobm
    ip address dhcp-bootp
    vsf member 1
    ip address 10.10.3.7 255.255.255.0
    exit
    vsf member 2
    ip address 10.10.3.8 255.255.255.0
    exit
    exit


    The only thing i can see is that the global ip address is set to DHCP, which may account for member 1 reporting that its IP is DHCP.
    Parnassus,did you end up getting this resolved?
    I will try and set a global oobm management address to see if it resolves the issue.
    Regards,
    James




    ------------------------------
    James Shepherd
    ------------------------------



  • 4.  RE: Aruba 5400R zl2 VSF OoBM MAD (via direct inter-link)

    Posted May 17, 2022 01:20 AM
    Hi Parnassus,
    I found the reason behind why the oobm on member 1 (commander) was picking up DHCP. It is because it is using the global oobm setting (in this case was set to DHCP).
    When i had the global oobm ip set to DHCP, the config of the active member assumes the global setting. I needed to set a different global management ip. Thus my configuration now looks like:

    VSFswitch# sh running-config oobm

    Running configuration:

    oobm
        ip address 10.10.3.6 255.255.255.0
        vsf member 1
            ip address 10.10.3.7 255.255.255.0
        exit
        vsf member 2
            ip address 10.10.3.8 255.255.255.0
            exit
        exit

    where as the oobm ip command shows

    VSFswitch# sh oobm ip

    IPv4 Status : Enabled
    IPv4 Default Gateway :

                                                                                                    Address  Interface
    VSF-member | IP Config IP Address/Prefix Length   Status    Status
    ------------------- + --------------- --------------------------------------- ------------ -----------
    Global            | manual      10.10.3.6/24                           Active    Up
    1                      | manual      10.10.3.6/24                           Active    Up
    2                      | manual      10.10.3.8/24                           Active    Up

    Thus, when the VSF is up, i can SSH into the global ip of 10.10.3.6 (which will SSH into the current commander) and i can SSH into the Standby member of 10.10.3.8. (i cannot SSH into 10.10.3.7 or ping it)
    I am assuming when the VSF fails, i would be able to then SSH into the individual members, member 1 using 10.10.3.7 and to member 2 using 10.255.3.8, but i am not sure as i have not tested this yet (maybe the active member will assume the global IP and the standby will assume its normal manually configured oobm ip
    Hope that helps.
    Regards,
    James

    ------------------------------
    James Shepherd
    ------------------------------