If you’re running a network that uses Aruba switches, you’ve probably heard of link-local addresses before—they’re those auto-assigned IPv6 addresses that let devices on the same local network talk to each other without needing a router or DHCP server. As someone who’s supplied Aruba switches for years, I know a lot of folks new to Aruba gear get tripped up setting these addresses up correctly, especially when they’re testing a new network segment, connecting a legacy device, or troubleshooting a connection. Today I’m breaking down exactly how to set up a link-local address on Aruba switches, plus a few pro tips I’ve picked up from working with small business owners and IT teams across North America. Switches for Aruba
First, let’s cut through the jargon so we’re all on the same page. Link-local addresses (fe80::/10 range, if you care) are super useful because they’re automatically generated by every IPv6-enabled device—no need to buy extra licensing, set up a DHCPv6 server, or juggle static IPv6 assignments. On Aruba switches specifically, these addresses are perfect for point-to-point links, isolated test networks, or even managing a switch directly via its serial console without connecting to a full network. I’ve used them countless times for quick switch configs when a main router is down; it beats scrambling to reconfigure DHCP just to access the switch’s web UI.
Now, before we dive into steps, a quick heads up: this guide works for most common Aruba switch models—think the 2530, 2930F, 2930M, and 3810 series, which are the ones I supply most often. If you’ve got a super old model like the 5400zl, the process is almost identical, so don’t stress. I’m using ArubaOS 16.x here, which is the standard firmware for modern Aruba switches, so if you’re on an older OS, you might need to tweak a tiny detail, but it’ll still work.
First, you’ll need to get into the switch’s command line interface (CLI). There’s a few ways to do this: serial console cable (the old reliable, great if you can’t reach the network), SSH, or even the web UI’s terminal tab. For this tutorial, I’m assuming you’re already logged into the CLI—if not, just open your terminal app, connect via SSH to the switch’s management IP, or plug in your serial cable and hit enter.
When you first log in, you’ll probably be at the “Switch” prompt, which is user EXEC mode. To make config changes, you need to get to global config mode by typing configure terminal (or just conf t, we all use the abbreviation) and hitting enter. That prompt will change to Switch(config)#, which is what we want.
Next, you’ll pick the interface you want to set the link-local address on. Most of the time, this is a switch port you’re using for a direct connection—like a port you’re plugging a laptop or another device into, or the management port (usually called “mgmt” on Aruba switches). Let’s go with a regular access port first, say interface 1/1/1. To pull up that interface’s config, type interface 1/1/1. Your prompt will switch to Switch(config-if)#, which is exactly where you need to be.
Now, here’s the part everyone messes up at first: enabling IPv6 on the interface. By default, Aruba switches have IPv6 turned off on all physical interfaces, even if the switch itself supports IPv6. So if you skip this step, the link-local address won’t stick. Type ipv6 enable and hit enter. That’s it—no IP address needed here, wait, hold on, is that right? Wait, no, if you want to manually set a link-local address instead of letting the switch auto-generate it, you do add that. Let’s clarify that: auto-generated link-local is great, but sometimes you want a specific one for consistency, like if you’re setting up a test script that relies on a fixed IP.
So after ipv6 enable, type ipv6 address fe80::1234:5678:9abc:def1/10 link-local. Wait, let’s break that down: fe80:: is the start of the link-local range, /10 is the subnet mask for link-local addresses, and link-local at the end tells the switch this is a link-local address, not a global one. You can pick any address in the fe80::/10 range, just make sure it’s unique on that segment—no one else on the same port/link can have the same address, otherwise you’ll get IP conflicts. If you just type ipv6 link-local without specifying an address, the switch will auto-generate one based on its MAC address, which is fine for most use cases. I usually default to auto-generated for quick setups, but manual is better for repeatable configs.
Wait, a quick test: after you set the address, type show ipv6 interface 1/1/1 and hit enter. You should see a line that says “Link-local address” with either your manual address or the auto-generated one, plus “State: Up”. If it says state is down, double-check that the interface isn’t shutdown—type no shutdown in the interface config if it is, because Aruba ports default to shutdown sometimes when they’re new.
Once that’s set, you’re not quite done yet—you need to make sure the switch is accepting neighbor discovery requests, which is how devices on the link find each other. Link-local addresses use NDP (Neighbor Discovery Protocol) instead of ARP for IPv4, and Aruba switches have NDP enabled by default, but it never hurts to confirm. Type show ipv6 nd interface 1/1/1 and make sure “ND Suppress” is set to No. If it’s Yes, type no ipv6 nd suppress in the interface config to turn it off—otherwise, the switch will block NDP packets, so your laptop or other device won’t see the link-local address.
Now, let’s test if it works. Grab a laptop, plug it into port 1/1/1, and make sure the laptop has IPv6 enabled (most modern OSes like Windows 10/11, macOS, and Linux have it on by default). Open a command prompt or terminal on the laptop, and type ping6 fe80::1234:5678:9abc:def1%eth0 (the %eth0 is the interface name—on Windows it’s usually a number like %4, macOS/Linux it’s the interface, or you can use the link-local scope ID). If the ping works, you’re golden—your link-local address is set up correctly. If not, check a few things: first, make sure both the switch port and the laptop’s port are up, not in a disabled state. Second, confirm the switch’s link-local address is unique—if another device on that segment has the same one, it’ll fail. Third, make sure NDP isn’t suppressed, like we checked earlier.
Now, I want to share a few mistakes I see customers make all the time when setting up link-local addresses on Aruba switches. First, don’t forget to enable IPv6 on the interface. I can’t tell you how many times a customer calls me saying their link-local isn’t working, and it turns out they skipped the ipv6 enable step. It’s such a tiny line, but it’s non-negotiable. Second, don’t mix up link-local with global IPv6 addresses. Global addresses are for routing across the internet, link-local is only for the same local segment—you can’t ping a link-local address from another network, so don’t try. Third, if you’re using the management port, it’s almost the same process, but the interface is mgmt, not 1/1/1. Type interface mgmt, then ipv6 enable, then your ipv6 address command, and you’re good. The only big difference with the management port is that it uses a different VLAN by default, but link-local works regardless of VLAN here, since it’s a local segment protocol.
Another pro tip: if you’re setting up multiple link-local addresses on different ports, don’t reuse the same fe80::… address across ports on the same switch. Wait, actually, can you? Let me confirm—yes, technically you can, because each port is a separate link, but it’s way easier to keep them unique to avoid confusion. I usually assign simple numbers like fe80::1 on port 1/1/1, fe80::2 on 1/1/2, so if I have a problem, I can tell which port a link-local is on just by the number. Saves so much time troubleshooting later.
Also, if you’re using Aruba’s instant on switches, the process is almost identical, but the CLI is a tiny bit different. For Instant On, you’ll go to the web UI, go to Switch Settings > Interfaces, pick the port, enable IPv6, then add the link-local address there. It’s the same logic, just point and click instead of CLI, which is great for people who prefer web configs.
Wait, let’s circle back to why link-local is such a big deal for small businesses and IT teams. A lot of the Aruba switches I supply go to businesses that don’t have a full-time IT staff, so they need fast, reliable ways to connect devices without complicated DHCP setups. Link-local lets you plug a laptop into a switch port, get an IP in 2 seconds, and start transferring files or managing the switch, no router needed. It’s also perfect for testing new switch configs before rolling them out to the main network—you can set up a test segment with link-local, play with VLANs and QoS, and make sure it works before connecting to production.
Now, if you’ve tried the steps and it still isn’t working, or you’re setting up link-local addresses for a larger network and need help optimizing the config, feel free to reach out. As a supplier of Aruba switches, I work with IT teams of all sizes, from solo business owners to enterprise networks, and I can help you troubleshoot, pick the right switch model for your needs, or walk through advanced configs like multiple link-local segments or NDP filtering. Whether you’re just setting up your first Aruba switch or upgrading your entire network, I’m here to help make the process as smooth as possible.
Before I wrap up, a quick note on security: link-local addresses are great for convenience, but they’re not for public facing use. Since they’re only local to your network, they’re not exposed to the internet, which is good, but always make sure your switch’s management access is limited to trusted IPs, even for link-local. You can use Aruba’s ACLs (Access Control Lists) to block unauthorized access to the switch’s CLI or web UI from link-local addresses, which adds an extra layer of protection.
Let me just recap the steps to make sure you don’t miss anything, in case you need to reference it later: 1. Log into the Aruba switch CLI (SSH, serial, or web terminal). 2. Enter global config mode with configure terminal. 3. Select your target interface (interface [port number] or interface mgmt). 4. Enable IPv6 on the interface with ipv6 enable. 5. (Optional but recommended) Set a unique link-local address with ipv6 address fe80::[your unique number]/10 link-local, or let the switch auto-generate it. 6. Confirm NDP is enabled with no ipv6 nd suppress (if needed). 7. Verify with show ipv6 interface [port] to make sure the link-local address is present and the state is Up.
That’s it—super straightforward once you skip the common pitfalls of forgetting to enable IPv6 or mixing up interface names. I’ve used this process hundreds of times over the years, and it works every time for all the Aruba switch models I supply. If you’re in the market for Aruba switches, need help with a custom config, or have questions about link-local addresses or any other Aruba network features, don’t hesitate to get in touch to discuss your needs.
Switches References: Aruba Switch Configuration Guide, ArubaOS 16.x CLI Reference Manual, Link-Local Addressing Best Practices for Enterprise Networks.
AITI Tech Limited
AITI Tech Limited is one of the most professional switches for aruba manufacturers and suppliers in China for over 20 years, featured by quality products and low price. Welcome to buy bulk discount switches for aruba in stock here from our factory. If you have any enquiry about pricelist, please feel free to email us.
Address: 6F, Haogong Building, Yannan Road, Futian District, Shenzhen, China
E-mail: kelly@hkaiti.com
WebSite: https://www.hkaiti.com/
