Wired Intelligent Edge

 View Only
last person joined: 5 hours ago 

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

7205 Mobility Controller can ping after boot then I can't

This thread has been viewed 26 times

  • 1.  7205 Mobility Controller can ping after boot then I can't

    Posted Feb 02, 2023 04:34 PM

    I'm not sure if I'm posting this under the correct community or not, but I have a 7205 Mobility controller and I have set an IP on VLAN 2 and set the controller-ip to use VLAN 2 and I have also setup the default gateway.  I just configured the Management interface and gave it an IP in our management subnet.  The MC is connected to an Aruba 6300 switch and that is connected to an 8325 switch that is our core switch.   I'm connected to interface 0/0/0 and have verified it is attached to VLAN 2 and I have assigned it's IP as xxx.xxx.2.34, the port on the 6300 and the 7205 are both Access VLAN 2.  The Management port is assigned IP xxx.xxx.119.115 and the port on the 6300 is Access VLAN 1.  I'm running a continuous ping on both IPS and when I reload the 7205 and it comes back up I can ping both IPs for about 25 times each and then it won't respond to a PING and I can't access the web interface but the link on both ports never go down.  I'm hoping someone can shine some light on this and tell me what I have missed or overlooked.

    Thanks,

    Leigh



  • 2.  RE: 7205 Mobility Controller can ping after boot then I can't

    Posted Feb 03, 2023 02:07 AM
    Did you get chance to look into the status of "show spanning-tree" ? Are the ports in forwarding state ?

    ------------------------------
    Shobana
    Aruba
    ------------------------------

    Original Message


  • 3.  RE: 7205 Mobility Controller can ping after boot then I can't

    Posted Feb 03, 2023 08:58 AM
    Yes, both ports on the 6300 are in a forwarding state.

    Here is the mgmt port config:
    interface 5/1/23
    no shutdown
    no routing
    vlan access 1
    spanning-tree rpvst-guard
    exit

    Here is the uplink port config:
    interface 1/1/24
    no shutdown
    description Aruba-7205 WLC Gi0/0
    no routing
    vlan access 2
    spanning-tree rpvst-guard
    exit


    Original Message


  • 4.  RE: 7205 Mobility Controller can ping after boot then I can't

    Posted Feb 03, 2023 09:30 AM
    Here is the spanning-tree information on the 7205:

    Interface GE 0/0/0 (port 1) in Spanning tree is FORWARDING
    Port path cost 20000, Port priority 128 Role DESIGNATED
    PortFast DISABLED P-to-P ENABLED
    BpduGuard DISABLED
    Designated root has priority 32768 address 20:4c:03:02:ff:88
    Designated bridge has priority 32768 address 20:4c:03:02:ff:88
    Designated port is 1, path cost 0
    Timers: message age 0, forward delay 0, hold 0
    Counts: BPDUs received 0, sent 87


    Original Message


  • 5.  RE: 7205 Mobility Controller can ping after boot then I can't

    Posted Feb 03, 2023 03:34 PM
    I'll also note that after I reload the 7205 the mgmt port responds to a PING about twice as long as GI 0/0/0 does before it times out.
    Original Message


  • 6.  RE: 7205 Mobility Controller can ping after boot then I can't

    Posted Feb 03, 2023 04:28 PM
      |   view attached
    Attached are the system logs.

    Attachment(s)

    txt
    MC 7205 sys log.txt   30 KB 1 version
    Original Message


  • 7.  RE: 7205 Mobility Controller can ping after boot then I can't

    Posted Feb 06, 2023 05:35 AM
    I would suggest raise a TAC case with support-files of gateway and switch for further debugging

    ------------------------------
    Shobana
    Aruba
    ------------------------------

    Original Message


  • 8.  RE: 7205 Mobility Controller can ping after boot then I can't

    Posted Feb 06, 2023 04:13 PM
    Thanks, I found out that the flash and config were backed up well before I started messing with the controller and I was able to restore the flash from that backup and I could access the GUI and assigned an IP to the MGMT interface.   Thank you for your help on this.
    Original Message