I85PREP
⌘ K
Aruba Switching Associate study materials
Aruba Switching Associate study resources

New Switch Gets No Management Address

Aruba Switching Associate · Put your knowledge to work in context.

All case studies

New Switch Gets No Management Address

A new Aruba 2930F is racked and cabled. The team wants to manage it via SSH on VLAN 1. The switch boots, and the console shows it is up. A DHCP server exists on VLAN 1 (10.0.1.0/24) and other devices get leases. The new switch does not appear to obtain an address. The engineer runs show ip and sees no IP address on VLAN 1. The uplink port is connected to a working access port on another switch that is untagged in VLAN 1. The engineer has not yet logged in to change anything.

1. List the most likely reasons the switch has no management IP and how to check each.

Read the worked answer

Possible causes, in likely order:

  1. DHCP is not enabled for the management VLAN. On ArubaOS-Switch, IP config can be static or DHCP per VLAN; check show run for ip address dhcp-bootp under vlan 1. If it is static with no address, no lease is requested.
  2. The uplink port is not actually in VLAN 1 untagged, or the cable/port is down. Check show interfaces for link state and show vlan for port membership.
  3. DHCP snooping or a helper issue on the upstream - but other devices work, so less likely.
  4. The switch may have a static address already in a different subnet (check show ip). Verification commands: show ip, show run interface vlan 1, show interfaces brief, show vlan 1, and show dhcp/logs for lease attempts.

2. If DHCP is confirmed enabled and the link is up but still no lease, what would you check next on the upstream side?

Read the worked answer

Check the upstream access port and its VLAN: confirm it is untagged in VLAN 1 and not shut down, and that the DHCP server/relay serves that subnet. Also verify the switch is actually sending DHCPDISCOVER - check show logging or enable debug on DHCP. If the upstream port is a trunk expecting tagged frames, untagged DHCP broadcasts from the new switch would land in the wrong VLAN. Finally, confirm there is no MAC-based or 802.1X port security on the upstream port that would block the new switch's MAC until authenticated. If port security is the cause, the port would show as unauthorized/blocked rather than simply no lease.