Security

 View Only

  • 1.  Cisco to Aruba Migration

    Posted Nov 21, 2024 03:21 AM
    hello all 

    I  am migrating  Cisco SG200 to Aruba switch infrastructure 
    an example of the configuration on the SG200 is shown below 
    the U denotes untagged and the P PVID
    for example GE7 will this map to 
    int 1/1/7
    vlan trunk native 1
    vlan trunk allowed 1,60,70



  • 2.  RE: Cisco to Aruba Migration

    Posted Nov 21, 2024 05:45 AM

    Hello Sean,

    Take a look at this guide where you have a comparison of Cisco commands to adapt them to Aruba, whether you are going to do it with an Aruba-CX or Aruba AOS-S switch. If you have any questions, post them in the forum.

    https://www.hpe.com/psnow/doc/c04793912

    Best Regards



    ------------------------------
    Daniel Ruiz
    -----------------------
    Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.
    If you have urgent issues, always contact your Aruba partner, distributor, or Aruba TAC Support.
    Check https://www.arubanetworks.com/support-services/contact-support/ for how to contact Aruba TAC.
    ------------------------------



  • 3.  RE: Cisco to Aruba Migration

    Posted Nov 21, 2024 08:57 AM

    Hello! the jargons (CLI grammars) of ArubaOS-Switch and ArubaOS-CX command line interfaces are different and this reflects also to configuration of VLAN membership of an interface.

    ArubaOS-Switch ("untagged" generally equals to PVID Port VLAN Id or "tagged" or "untagged" + "tagged" or, again, only "tagged", in any case a port can't be PVID orphaned), example (to cope with 1/1/7 VLAN membership configuration you posted):

    vlan 1

    untagged 7

    vlan 60

    tagged 7

    vlan 70

    tagged 7  

    interface 7
       tagged vlan 60,70
       untagged vlan 1

    show vlan ports ethernet 7 detail

     Status and Counters - VLAN Information - for ports 7

      VLAN ID Name                 | Status     Voice Jumbo Mode    
      ------- -------------------- + ---------- ----- ----- --------
      1       DEFAULT_VLAN         | Port-based No    No    Untagged
      60      VLAN-60              | Port-based No    No      Tagged
      70      VLAN-70              | Port-based No    No      Tagged

    alternatively on ArubaOS-CX the same configuration should be obtained with:

    switch#interface 1/1/7

    switch(config-if)# vlan trunk native 1

    switch(config-if)# vlan trunk allowed 60,70

    interface 1/1/7
        no shutdown 
        no routing
        vlan trunk native 1
        vlan trunk allowed 1,60,70

    switch# show vlan port 1/1/7          

    -------------------------------------------------------------------------------
    VLAN  Name                            Mode            Mapping                  
    -------------------------------------------------------------------------------
    1     VLAN-1                          native-untagged port

    60    VLAN-60                         trunk           port

    70    VLAN-70                         trunk           port

    On ArubaOS-CX the "native" Mode of an interface (operating in Trunk or Access mode) could be set to be "tagged" (which is a little bit counter-intuitive to me since I've always associated the idea of PVID with an untagged VLAN coming from the ArubaOS-Switch experience), in this case the vlan trunk native 1 command reported above will transform into vlan trunk native 1 tag (the same applies when an interface is configured to operate in Access mode of operation: in this case no other VLAN Ids are allowed so the port could be - needs to be - member of just one VLAN, untagged or tagged).




  • 4.  RE: Cisco to Aruba Migration

    Posted Nov 21, 2024 09:09 AM

    Thank you

     




    Original Message


Related Content