Cloud Managed Networks

 View Only
last person joined: 10 hours ago 

Forum to discuss all things related to HPE Aruba Networking Central and UXI Network Management, including deployment of managed networks, configuration, best practices, APIs, Cloud Guest, AIOps, Presence Analytics, and other included Applications
Expand all | Collapse all

Aruba Central - Device internal error

This thread has been viewed 12 times
  • 1.  Aruba Central - Device internal error

    Posted 10 hours ago

    Hello,

    Last week I have rolled out five new 6200F switches for one of our customers. There are two VSF stacks of two switches each and one stand-alone switch. All the configuration is done via a template and a variable configuration file; everything went fine up to a point when, suddenly, one of the stacks went out of sync.

    After each change I make to the template or after uploading a new variable configuration file, I get the error shown below.

    list
    Clicking the three dots doesn't reveal much:
    I ahve also checked the events - nothing relevant there.
    And here is the log from the switch console:
    ESW-CAB2-0002# show logging -r -s err
    ---------------------------------------------------
    Event logs from current boot 
    ---------------------------------------------------
    2024-07-17T21:05:46.078598+00:00 ESW-CAB2-0002 log-proxyd[791]: Event|13002|LOG_ERR|CDTR|1|User admin login from 0.0.0.0 for CONSOLE session has failed.
    2024-07-17T21:05:28.067518+00:00 ESW-CAB2-0002 log-proxyd[791]: Event|13002|LOG_ERR|CDTR|1|User admin login from 0.0.0.0 for CONSOLE session has failed.
    2024-07-17T20:36:39.413348+00:00 ESW-CAB2-0002 hpe-restd[921]: Event|4640|LOG_ERR|AMM|-|Failed to connect to Aruba Central on location device-eucentral3-d2.central.arubanetworks.com on VRF default with Source IP automatic
    2024-07-17T20:32:22.242067+00:00 ESW-CAB2-0002 hpe-restd[921]: Event|4640|LOG_ERR|AMM|-|Failed to connect to Aruba Central on location device-eucentral3-d2.central.arubanetworks.com on VRF default with Source IP automatic
    2024-07-17T20:30:15.477300+00:00 ESW-CAB2-0002 hpe-restd[921]: Event|4640|LOG_ERR|AMM|-|Failed to connect to Aruba Central on location device-eucentral3-d2.central.arubanetworks.com on VRF default with Source IP automatic
    2024-07-17T20:29:12.113347+00:00 ESW-CAB2-0002 hpe-restd[921]: Event|4640|LOG_ERR|AMM|-|Failed to connect to Aruba Central on location device-eucentral3-d2.central.arubanetworks.com on VRF default with Source IP automatic
    2024-07-17T20:28:05.649416+00:00 ESW-CAB2-0002 hpe-restd[921]: Event|4640|LOG_ERR|AMM|-|Failed to connect to Aruba Central on location device-eucentral3-d2.central.arubanetworks.com on VRF default with Source IP automatic
    2024-07-17T19:48:01.041071+00:00 6200 ztpd[3370]: Event|8730|LOG_ERR|UKWN|1|ZTP service status changed to failed because configuration file download encountered unexpected error. Reason: User created configuration found
    
    The error first showed on the 17/07.
    I should highlight that the configuration template applies to both stacks and to the stand-alone switch. The other stack and the stand alone switch are "In sync" with no issues.
    I Have opened a support case with Aruba TAC and they suggested to create a new, test group and move the "faulty" stack there, to see if the issue persists.
    Has anyone else encountered this error?


  • 2.  RE: Aruba Central - Device internal error

    EMPLOYEE
    Posted 7 hours ago

    The logging suggests that the switch cannot reach Central anymore (through the default VRF). Could it be that your change blocked access to Central? Or another network change (firewall?) blocked access from your switch to central?

    It seems that you use template based configuration. Does the Configuration Audit (go in your config group; select switches, configuration, Configuration Audit tab) explain more about what is out of sync or what commands provide errors?



    ------------------------------
    Herman Robers
    ------------------------
    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. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

    In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
    ------------------------------



  • 3.  RE: Aruba Central - Device internal error

    Posted 6 hours ago

    Hi Herman,

    Thank you for your feedback.

    Indeed, the logging shows that the stack lost its connectivity to Central (on the mgmt VRF it happened when I disconnected all the MGMT interfaces from the old network; this way I did the initial configuration and I kept a "back door" in case something was going wrong on VLAN 1).

    In any case, the switches are still connected to Central using the default VRF (they show "online" in the list and I can use the Aruba Central console connection to this switch to make changes (after enabling aruba-central support mode).

    ESW-CAB2-0002(config)# show aruba-central 
    Central admin state                     : enabled
    
    Central location                        : device-eucentral3-d2.central.arubanetworks.com
    VRF for connection                      : default
    Shared Token                            : N/A
    Central connection status               : connected
    
    Central source                          : activate
    Central source connection status        : connected
    Central source last connected on        : Wed Jul 17 21:10:13 UTC 2024
    
    Main location                           : device-eucentral3-d2.central.arubanetworks.com
    Main VRF                                : default
    Alternative location                    : N/A
    Alternative VRF                         : N/A
    
    Activate Server URL                     : devices-v2.arubanetworks.com
    System time synchronized from Activate  : True
    
    Source IP                               : 172.21.253.2
    Source IP Overridden                    : False
    
    Central support mode                    : disabled
    
    Here is the output of the "Configuration Status" for the "Not in Sync Device":
    !
    !Version ArubaOS-CX ML.10.13.1010
    !export-password: default
    hostname ESW-CAB2-0002
    user admin group administrators password ciphertext [...]
    ntp server fr.pool.ntp.org minpoll 4 maxpoll 4 iburst prefer
    ntp enable
    !
    !
    !
    !
    !
    !
    ssh server vrf default
    ssh server vrf mgmt
    vsf member 1
    	type jl728a
    	vsf secondary-member 2
    	vsf member 1
    		type jl728a
    		link 1  1/1/49
    		link 2  1/1/50
    	vsf member 2
    		type jl728a
    		link 1  2/1/49
    		link 2  2/1/50
    vlan 1
    vlan 11
        name USERS
    vlan 12
        name VOIP
    vlan 13
        name OF_PRINTERS
    vlan 21
        name PRODUCTION
    vlan 31
        name T_AND_A
    vlan 32
        name CCTV
    vlan 33
        name ACCESS_CTRL
    vlan 99
        name GUEST
    vlan 253
        name MGMT
    vlan 315
    	name LEGACY_PABX
    vlan 316
    	name LEGACY
    vlan 404
    	name BLACK_HOLE
    spanning-tree mode rpvst
    spanning-tree
    interface mgmt
        no shutdown
        ip dhcp
    	interface lag 1
    		description LAG_TO_CAB1-0001
    		no shutdown
    		no routing
    		vlan trunk native 253
    		vlan trunk allowed all
    		lacp mode active
    		interface  1/1/49
    			no shutdown
    		interface  1/1/50
    			no shutdown
    		interface  2/1/49
    			no shutdown
    		interface  2/1/50
    			no shutdown
    	interface  1/1/51
    		description TO_CSW_CAB1_0001
    		no shutdown
    		lag 1
    	interface  2/1/51
    		description TO_CSW_CAB1_0001
    		no shutdown
    		lag 1
    	interface vlan 253
    		description MGMT
    		ip address 172.21.253.2/24
    		ip helper-address a.b.c.d
    		ip helper-address e.f.g.h
    	ip route 0.0.0.0/0 172.21.253.254
    interface 1/1/1-1/1/3,2/1/1-2/1/3
    	description WAP
    	no shutdown
    	vlan trunk native 253
    	vlan trunk allowed 11,99,253
    	spanning-tree bpdu-guard
    	spanning-tree loop-guard
    	loop-protect
    interface 1/1/4,2/1/4
    	description USER_DEVICE
    	no shutdown
    	vlan access 11
    	spanning-tree bpdu-guard
    	spanning-tree loop-guard
    	loop-protect
    interface 1/1/5,2/1/5
    	description OFFICE_PRINTER
    	no shutdown
    	vlan access 13
    	spanning-tree bpdu-guard
    	spanning-tree loop-guard
    	loop-protect
    interface 1/1/6-1/1/48,2/1/6-2/1/48
    	description LEGACY_PABX
    	no shutdown
    	vlan access 315
    interface 1/1/52,2/1/52
    	description NOT_IN_USE
    	shutdown
    	vlan access 404
    snmp-server vrf default
    snmp-server system-description AOS-CX
    snmp-server system-location LOCATION
    snmp-server system-contact CONTACT
    snmp-server community COMMUNITY
    snmpv3 user USER auth sha auth-pass ciphertext [...]
    ip dns domain-name example.com
    ip dns server-address a.b.c.d
    ip dns server-address e.f.g.h
    https-server vrf default
    https-server vrf mgmt
    configuration-lockout central managed
    And this is the current running configuration taken from the switch:
    Current configuration:
    !
    !Version ArubaOS-CX ML.10.13.1010
    !export-password: default
    hostname ESW-CAB2-0002
    user admin group administrators password ciphertext [...]
    ntp server fr.pool.ntp.org minpoll 4 maxpoll 4 iburst prefer
    ntp enable
    !
    !
    !
    !
    !
    !
    ssh server vrf default
    ssh server vrf mgmt
    			
    			
    vsf secondary-member 2
    vsf member 1 
        type jl728a
        link 1 1/1/49
        link 2 1/1/50
    vsf member 2 
        type jl728a
        link 1 2/1/49
        link 2 2/1/50
    vlan 1
    vlan 11
        name USERS
    vlan 12
        name VOIP
    vlan 13
        name OF_PRINTERS
    vlan 21
        name PRODUCTION
    vlan 31
        name T_AND_A
    vlan 32
        name CCTV
    vlan 33
        name ACCESS_CTRL
    vlan 99
        name GUEST
    vlan 192
    vlan 253
        name MGMT
    vlan 315
        name LEGACY_PABX
    vlan 316
        name LEGACY
    vlan 404
        name BLACK_HOLE
    spanning-tree mode rpvst
    spanning-tree
    interface mgmt
        no shutdown
        ip dhcp
    interface lag 1
        description LAG_TO_CAB1-0001
        no shutdown
        no routing
        vlan trunk native 253
        vlan trunk allowed all
        lacp mode active
    interface 1/1/1
        description WAP
        no shutdown
        no routing
        vlan trunk native 253
        vlan trunk allowed 11,99,253
        spanning-tree bpdu-guard
        spanning-tree loop-guard
        loop-protect
    interface 1/1/[...]
    			  
    interface 1/1/49
        no shutdown
    interface 1/1/50
        no shutdown
    interface 1/1/51
        description TO_CSW_CAB1_0001
        no shutdown
        lag 1
    interface 1/1/52
        description NOT_IN_USE
        shutdown
        no routing
        vlan access 404
    				  
    							
    						   
    						   
    								  
    interface 2/1/1
        description WAP
        no shutdown
        no routing
        vlan trunk native 253
        vlan trunk allowed 11,99,253
        spanning-tree bpdu-guard
        spanning-tree loop-guard
        loop-protect
    interface 2/1/[...]
    interface 2/1/49
        no shutdown
    			   
    						 
    						 
    			 
    interface 2/1/50
    						   
        no shutdown
    			   
    						 
    						 
    			 
    interface 2/1/51
        description TO_CSW_CAB1_0001
        no shutdown
        lag 1
    interface 2/1/52
        description NOT_IN_USE
        shutdown
        no routing
        vlan access 404
    interface vlan 1
    interface vlan 253
        description MGMT
        ip address 172.21.253.2/24
        ip helper-address a.b.c.d
        ip helper-address e.f.g.h
    snmp-server vrf default
    snmp-server system-description AOS-CX
    snmp-server system-location LOCATION
    snmp-server system-contact CONTACT
    snmp-server community COMMUNITY
    snmpv3 user USER auth sha auth-pass ciphertext [...]
    ip route 0.0.0.0/0 172.21.253.254
    ip dns domain-name example.com
    ip dns server-address a.b.c.d
    ip dns server-address e.f.g.h
    !
    !
    !
    !
    !
    https-server vrf default
    https-server vrf mgmt
    configuration-lockout central managed

    All the switches are on the latest recommended firmware (ML 10.13.1010)




  • 4.  RE: Aruba Central - Device internal error

    EMPLOYEE
    Posted 3 hours ago

    I don't have an out of sync device, but remember that there is a side-by-side comparison where you can see (only) the differences, or with a markup on the different lines. Don't you have that??



    ------------------------------
    Herman Robers
    ------------------------
    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. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

    In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
    ------------------------------



  • 5.  RE: Aruba Central - Device internal error

    Posted an hour ago
      |   view attached

    I think you mean the "Config comparison tool", in the "per-Device" Configuration Audit:

    I checked the side-by-side the "Device Running Configuration" and the "Attempted Configuration". Aparte from the long list of highlighted interfaces (the running config shows every single interface whereas as the template has range(s) of interfaces), the only two things which may lead to the error are:

    • one line in the VSF configuration:

    • one line in the default route configuration
    It's quite unlikely to get the error from these two as I always use this order for VSF stacking configuration. As for the default route, it is inserted there because I use the same template (attached) for the core stack and for the access stack & stand-alone switch, which don't get the error.


    Attachment(s)

    txt
    template.txt   7 KB 1 version