Wired Intelligent Edge

 View Only
  • 1.  Central Template - CX Variables.

    Posted Mar 01, 2024 03:08 PM

    For a CX VSF Stack, I am trying to pass a variable that includes interface #'s . This is to apply a switchport configuration to Misc. ports across the entire stack.  I cannot get this to work. For a simplified example... 

    Template:

      interface %data%
        no shutdown 
        no routing
        vlan access 10

    In my Variable Files, I have two separate lines. 1 line for each switch in the stack. I have omitted all the variables that work and just include relevant var's for this example:

    _sys_serial _sys_lan_mac modified _sys_hostname data
    SG00000000 64:e8:81:99:99:99 y Switch1 1/1/3
    SG90000001 88:3A:30:00:00:00 y Switch2 2/1/3

    Switch 1 will apply the config to port 1/1/3 but Switch 2 will not apply port config. Acts like it does not exists. I assume because it is part of a stack and relies on the Conductor (switch1)  to configure it. So,.... maybe I put that interface into the Switch 1 variable field??...

    If I try this...

    _sys_serial _sys_lan_mac modified _sys_hostname data
    SG00000000 64:e8:81:99:99:99 y Switch1 2/1/3
    SG90000001 88:3A:30:00:00:00 y Switch2 2/1/3

    Switch 1 fails it sync Pre-Check and does not pull down the config at all. Central Audit Log tells me it is an invalidd config. 

    How do I get a port on Switch two to take a port config? - Without manually specifying the interface in the template. 



    ------------------------------
    Philip Wightman, ACEX #69
    Aruba Partner Ambassador
    ------------------------------


  • 2.  RE: Central Template - CX Variables.

    Posted Mar 02, 2024 02:20 PM

    In case of a stack, all the variables needs to be applied on the conductor. Best to apply ALL the variables on both the conductor and standby conductor in case of failover. Just try something like this

    _sys_serial _sys_lan_mac modified _sys_hostname data data2
    SG00000000 64:e8:81:99:99:99 y Switch1 1/1/3 2/1/3

    I prefer to use a different kind of style in the template. Something like this

    interface 1/1/3
       %if interface.1.1.3.admin=1%
        vlan access 20
       %else
        vlan access 10
       %endif%

    interface 2/1/3
       %if interface.2.1.3.admin=1%
        vlan access 20
       %else
        vlan access 10
       %endif%

    Variable file (json style)

    {
    "SG00000000": {
    "interface.1.1.3.admin": "1",
    "interface.2.1.3.admin": "0"
    }
    }


    ------------------------------
    Willem Bargeman
    Systems Engineer Aruba
    ACEX #125
    ------------------------------



  • 3.  RE: Central Template - CX Variables.

    Posted Mar 02, 2024 03:56 PM
    That would work as you are defining the interface in the template whereas I need to define the interface in the variables file. Know of any tricks to get that to work? 

    Philip Wightman 

    Sr. Systems Engineer

    Wireless & Identity | ACMX | ACCX | ACDX | ACEX #69

    LAKETEC  Voice | Network | Cloud 
    Tel:  440-575-6029
    Fax:  440-925-1828
    email 
    pwightman@laketec.com

    web: www.Laketec.com

    After-Hours Emergency Support - Call 1-800-859-4604

    Click Here to access online ticketing portal

     







  • 4.  RE: Central Template - CX Variables.

    Posted Mar 03, 2024 03:02 AM
    I don’t think that is going to work. The template output needs to be the same as the running configuration at the switch.
    That means that each interface needs to be defined in the template. Best is to use the variables within the interface context.

    ---------------------------------
    Willem Bargeman
    Systems Engineer Aruba
    ACEX #125
    ---------------------------------





  • 5.  RE: Central Template - CX Variables.

    Posted Mar 04, 2024 08:29 AM

    I figured that was going to be the answer. Bummer.  I am working on migrating a customer from approx 70 Cisco switches with 30 VLANs spread across various ports. It is east to copy/paste all the Interfaces for a specific VLAN but not so easy to do the other way around.  So for example port 1/1/1 on each switch may be on a different VLAN. Repeat for the rest of the 48 ports.. for each switch. 



    ------------------------------
    Philip Wightman, ACEX #69
    Aruba Partner Ambassador
    ------------------------------



  • 6.  RE: Central Template - CX Variables.

    Posted Mar 04, 2024 08:57 AM

    That is not how the templates works. ClearPass can be ideal for that question (colourless ports).

    Other option is the interface profiles that with have with MultiEdit. This is a kind off template that easily can be applied on a range off interfaces.



    ------------------------------
    Willem Bargeman
    Systems Engineer Aruba
    ACEX #125
    ------------------------------



  • 7.  RE: Central Template - CX Variables.

    Posted Mar 04, 2024 09:03 AM

    Agreed, all great options however we need to do ZTP and keep it Template based for this customer. No CPPM until next year where DUR will be in play. Appreciate all the feedback though!



    ------------------------------
    Philip Wightman, ACEX #69
    Aruba Partner Ambassador
    ------------------------------