<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Aruba on vlan51</title><link>https://vlan51.com/tags/aruba/</link><description>Recent content in Aruba on vlan51</description><generator>Hugo</generator><language>en-gb</language><lastBuildDate>Mon, 01 Jan 2024 00:00:00 +0000</lastBuildDate><atom:link href="https://vlan51.com/tags/aruba/index.xml" rel="self" type="application/rss+xml"/><item><title>802.1x Port Authentication on HPE Aruba ArubaOS-Switch</title><link>https://vlan51.com/aruba-provision/802-1x-port-authentication/</link><pubDate>Mon, 01 Jan 2024 00:00:00 +0000</pubDate><guid>https://vlan51.com/aruba-provision/802-1x-port-authentication/</guid><description>&lt;p&gt;How to configure 802.1x port authentication on HPE Aruba ArubaOS-Switch, with MAC authentication for devices that do not support 802.1x (such as printers), and LLDP-MED bypass for VoIP phones.&lt;/p&gt;&#10;&lt;p&gt;This guide covers the switch configuration and the Microsoft NPS (Network Policy Server) setup for automatic EAP-RADIUS authentication of PCs, MAC authentication for printers, and voice VLAN bypass for Avaya handsets.&lt;/p&gt;&#10;&lt;p&gt;&lt;strong&gt;Prerequisites:&lt;/strong&gt; Microsoft NPS installed and registered in Active Directory, a PKI in place with client certificates deployed to machines you want to authenticate via 802.1x.&lt;/p&gt;</description></item><item><title>ACL / Access Lists on HPE Aruba ArubaOS-Switch</title><link>https://vlan51.com/aruba-provision/acl-guest-network/</link><pubDate>Mon, 01 Jan 2024 00:00:00 +0000</pubDate><guid>https://vlan51.com/aruba-provision/acl-guest-network/</guid><description>&lt;p&gt;How to create extended ACLs on HPE Aruba ArubaOS-Switch and apply them to a VLAN interface. This example restricts a guest wireless network from accessing any internal address space while allowing internet access.&lt;/p&gt;&#10;&lt;h2 id="scenario"&gt;Scenario &lt;a class="anchor" href="#scenario" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;Guest network subnet: &lt;code&gt;192.168.0.0/23&lt;/code&gt;. Guests must reach the internet but must not reach any RFC1918 internal ranges.&lt;/p&gt;&#10;&lt;h2 id="create-the-acl"&gt;Create the ACL &lt;a class="anchor" href="#create-the-acl" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;div class="code"&gt;&#10; &lt;div class="code-bar"&gt;&lt;span&gt;cli&lt;/span&gt;&lt;button class="copy" type="button" aria-label="Copy to clipboard"&gt;Copy&lt;/button&gt;&lt;/div&gt;&lt;pre&gt;&lt;code&gt;ip access-list extended &amp;#34;GUEST-ACL&amp;#34;&#10; 10 permit ip 192.168.0.0 0.0.1.255 192.168.0.0 0.0.1.255&#10; 20 deny ip 192.168.0.0 0.0.1.255 10.0.0.0 0.255.255.255 log&#10; 30 deny ip 192.168.0.0 0.0.1.255 172.16.0.0 0.15.255.255 log&#10; 40 deny ip 192.168.0.0 0.0.1.255 192.168.0.0 0.0.255.255 log&#10; 50 permit ip 192.168.0.0 0.0.1.255 0.0.0.0 255.255.255.255 log&#10; exit&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;Line 10 — permits intra-subnet traffic (required for hosts on the /23 to communicate with each other)&lt;/li&gt;&#10;&lt;li&gt;Lines 20, 30, 40 — deny RFC1918 ranges&lt;/li&gt;&#10;&lt;li&gt;Line 50 — permit all other destinations (internet)&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h2 id="apply-to-the-vlan-interface"&gt;Apply to the VLAN interface &lt;a class="anchor" href="#apply-to-the-vlan-interface" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;div class="code"&gt;&#10; &lt;div class="code-bar"&gt;&lt;span&gt;cli&lt;/span&gt;&lt;button class="copy" type="button" aria-label="Copy to clipboard"&gt;Copy&lt;/button&gt;&lt;/div&gt;&lt;pre&gt;&lt;code&gt;vlan 10&#10; name &amp;#34;Guest Network&amp;#34;&#10; ip access-group &amp;#34;GUEST-ACL&amp;#34; in&#10; ip address 192.168.0.1 255.255.254.0&#10;exit&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&#10;&lt;p&gt;The ACL is applied &lt;strong&gt;inbound&lt;/strong&gt; (&lt;code&gt;in&lt;/code&gt;) — it inspects traffic as it arrives from guest clients.&lt;/p&gt;</description></item><item><title>DHCP Server on HPE Aruba ArubaOS-Switch</title><link>https://vlan51.com/aruba-provision/dhcp-server/</link><pubDate>Mon, 01 Jan 2024 00:00:00 +0000</pubDate><guid>https://vlan51.com/aruba-provision/dhcp-server/</guid><description>&lt;p&gt;HPE Aruba ArubaOS-Switch has a built-in DHCP server. This guide covers creating a DHCP pool, enabling it on a VLAN, and adding static reservations for individual devices.&lt;/p&gt;&#10;&lt;blockquote&gt;&#10;&lt;p&gt;&lt;strong&gt;Important:&lt;/strong&gt; You must disable the DHCP server globally before making any changes to pool configuration.&lt;/p&gt;&#10;&lt;/blockquote&gt;&#10;&lt;h2 id="create-a-dhcp-pool"&gt;Create a DHCP pool &lt;a class="anchor" href="#create-a-dhcp-pool" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;div class="code"&gt;&#10; &lt;div class="code-bar"&gt;&lt;span&gt;cli&lt;/span&gt;&lt;button class="copy" type="button" aria-label="Copy to clipboard"&gt;Copy&lt;/button&gt;&lt;/div&gt;&lt;pre&gt;&lt;code&gt;conf t&#10;dhcp-server disable&#10;&#10;dhcp-server pool &amp;#34;GUEST-DHCP&amp;#34;&#10; authoritative&#10; default-router &amp;#34;192.168.0.1&amp;#34;&#10; dns-server &amp;#34;8.8.8.8,8.8.4.4&amp;#34;&#10; domain-name &amp;#34;test.local&amp;#34;&#10; lease 00:01:00&#10; network 192.168.0.0 255.255.254.0&#10; range 192.168.0.21 192.168.1.149&#10;exit&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&#10;&lt;h2 id="enable-dhcp-on-the-vlan-interface"&gt;Enable DHCP on the VLAN interface &lt;a class="anchor" href="#enable-dhcp-on-the-vlan-interface" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;div class="code"&gt;&#10; &lt;div class="code-bar"&gt;&lt;span&gt;cli&lt;/span&gt;&lt;button class="copy" type="button" aria-label="Copy to clipboard"&gt;Copy&lt;/button&gt;&lt;/div&gt;&lt;pre&gt;&lt;code&gt;vlan 10&#10; name &amp;#34;Guest Wireless&amp;#34;&#10; ip address 192.168.0.1 255.255.254.0&#10; dhcp-server&#10; exit&#10;&#10;conf t&#10;dhcp-server enable&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&#10;&lt;h2 id="static-dhcp-reservations"&gt;Static DHCP reservations &lt;a class="anchor" href="#static-dhcp-reservations" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;Each reservation requires its own named pool. Disable the server first:&lt;/p&gt;</description></item><item><title>NTP / SNTP on HPE Aruba ArubaOS-Switch</title><link>https://vlan51.com/aruba-provision/ntp-sntp/</link><pubDate>Mon, 01 Jan 2024 00:00:00 +0000</pubDate><guid>https://vlan51.com/aruba-provision/ntp-sntp/</guid><description>&lt;p&gt;How to configure SNTP time synchronisation on HPE Aruba ArubaOS-Switch.&lt;/p&gt;&#10;&lt;h2 id="configuration"&gt;Configuration &lt;a class="anchor" href="#configuration" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;Syntax varies slightly between firmware versions — use whichever your switch accepts:&lt;/p&gt;&#10;&lt;p&gt;&lt;strong&gt;Current syntax:&lt;/strong&gt;&lt;/p&gt;&#10;&lt;div class="code"&gt;&#10; &lt;div class="code-bar"&gt;&lt;span&gt;cli&lt;/span&gt;&lt;button class="copy" type="button" aria-label="Copy to clipboard"&gt;Copy&lt;/button&gt;&lt;/div&gt;&lt;pre&gt;&lt;code&gt;sntp unicast&#10;timesync sntp&#10;sntp server priority 1 1.2.3.4&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&#10;&lt;p&gt;&lt;strong&gt;Older syntax:&lt;/strong&gt;&lt;/p&gt;&#10;&lt;div class="code"&gt;&#10; &lt;div class="code-bar"&gt;&lt;span&gt;cli&lt;/span&gt;&lt;button class="copy" type="button" aria-label="Copy to clipboard"&gt;Copy&lt;/button&gt;&lt;/div&gt;&lt;pre&gt;&lt;code&gt;sntp unicast&#10;timesync sntp&#10;sntp server 1.2.3.4&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&#10;&lt;p&gt;Replace &lt;code&gt;1.2.3.4&lt;/code&gt; with your NTP server IP. Domain controllers are a practical choice as they run Windows Time Service automatically.&lt;/p&gt;</description></item><item><title>Policy Based Routing (PBR) on HPE Aruba ArubaOS-Switch</title><link>https://vlan51.com/aruba-provision/policy-based-routing/</link><pubDate>Mon, 01 Jan 2024 00:00:00 +0000</pubDate><guid>https://vlan51.com/aruba-provision/policy-based-routing/</guid><description>&lt;p&gt;How to configure Policy Based Routing (PBR) on HPE Aruba ArubaOS-Switch. Applies to the 3800, 5400zl v2, and 8200 series. PBR can only be applied &lt;strong&gt;inbound&lt;/strong&gt;.&lt;/p&gt;&#10;&lt;p&gt;Three components: a &lt;strong&gt;class&lt;/strong&gt; to match traffic, a &lt;strong&gt;policy&lt;/strong&gt; to define the action, and a &lt;strong&gt;VLAN/port&lt;/strong&gt; to apply it.&lt;/p&gt;&#10;&lt;h2 id="scenario"&gt;Scenario &lt;a class="anchor" href="#scenario" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;Traffic from &lt;code&gt;192.168.10.0/24&lt;/code&gt; to &lt;code&gt;10.0.0.0/24&lt;/code&gt; uses gateway &lt;code&gt;2.2.2.1&lt;/code&gt;. All other traffic uses &lt;code&gt;1.1.1.1&lt;/code&gt;.&lt;/p&gt;&#10;&lt;figure&gt;&#10; &lt;a href="https://vlan51.com/images/provision-pbr-topology.png" target="_blank" rel="noopener"&gt;&lt;img src="https://vlan51.com/images/provision-pbr-topology.png" alt="PBR topology — local and internet breakout" loading="lazy" decoding="async"&gt;&lt;/a&gt;&lt;figcaption&gt;PBR topology — local and internet breakout&lt;/figcaption&gt;&#10;&lt;/figure&gt;&#10;&lt;h2 id="class-configuration"&gt;Class configuration &lt;a class="anchor" href="#class-configuration" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;div class="code"&gt;&#10; &lt;div class="code-bar"&gt;&lt;span&gt;cli&lt;/span&gt;&lt;button class="copy" type="button" aria-label="Copy to clipboard"&gt;Copy&lt;/button&gt;&lt;/div&gt;&lt;pre&gt;&lt;code&gt;class ipv4 &amp;#34;CLASS-192.168-LOCAL-BREAKOUT&amp;#34;&#10; 5 match ip 192.168.10.0 0.0.0.255 10.0.0.0 0.0.0.255&#10; exit&#10;&#10;class ipv4 &amp;#34;CLASS-192.168-INTERNET-BREAKOUT&amp;#34;&#10; 5 match ip 192.168.10.0 0.0.0.255 0.0.0.0 255.255.255.255&#10; exit&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&#10;&lt;h2 id="policy-configuration"&gt;Policy configuration &lt;a class="anchor" href="#policy-configuration" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;div class="code"&gt;&#10; &lt;div class="code-bar"&gt;&lt;span&gt;cli&lt;/span&gt;&lt;button class="copy" type="button" aria-label="Copy to clipboard"&gt;Copy&lt;/button&gt;&lt;/div&gt;&lt;pre&gt;&lt;code&gt;policy pbr &amp;#34;POLICY-INTERNET-BREAKOUT&amp;#34;&#10; 5 class ipv4 &amp;#34;CLASS-192.168-LOCAL-BREAKOUT&amp;#34;&#10; action ip next-hop 2.2.2.1&#10; exit&#10; 6 class ipv4 &amp;#34;CLASS-192.168-INTERNET-BREAKOUT&amp;#34;&#10; action ip next-hop 1.1.1.1&#10; exit&#10; exit&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&#10;&lt;h2 id="apply-to-vlan-interface"&gt;Apply to VLAN interface &lt;a class="anchor" href="#apply-to-vlan-interface" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;div class="code"&gt;&#10; &lt;div class="code-bar"&gt;&lt;span&gt;cli&lt;/span&gt;&lt;button class="copy" type="button" aria-label="Copy to clipboard"&gt;Copy&lt;/button&gt;&lt;/div&gt;&lt;pre&gt;&lt;code&gt;vlan 10&#10; name &amp;#34;192.168.10.0-VLAN&amp;#34;&#10; ip address 192.168.10.254 255.255.255.0&#10; service-policy &amp;#34;POLICY-INTERNET-BREAKOUT&amp;#34; in&#10; exit&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&#10;&lt;h2 id="important-locally-connected-networks"&gt;Important: locally connected networks &lt;a class="anchor" href="#important-locally-connected-networks" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;If other VLANs are on the same switch, PBR will break inter-VLAN routing because it overrides the routing table for matched traffic. Fix this by pointing the local class next-hop at &lt;strong&gt;the switch&amp;rsquo;s own IP&lt;/strong&gt;:&lt;/p&gt;</description></item><item><title>Port Security on HPE Aruba ArubaOS-Switch</title><link>https://vlan51.com/aruba-provision/port-security/</link><pubDate>Mon, 01 Jan 2024 00:00:00 +0000</pubDate><guid>https://vlan51.com/aruba-provision/port-security/</guid><description>&lt;p&gt;Port security is a form of MAC lockdown (layer 2 control). It lets you limit, restrict or fix the MAC addresses allowed on an individual switch port, and decide what the switch does when that rule is broken. This applies to the HPE Aruba 2920, 2930, 3800, 5400 and 8200 series running ArubaOS-Switch.&lt;/p&gt;&#10;&lt;p&gt;I wrote this after a reader asked how to set it up. These are the scenarios I use most.&lt;/p&gt;</description></item><item><title>RADIUS Login Authentication on HPE Aruba ArubaOS-Switch</title><link>https://vlan51.com/aruba-provision/radius-login/</link><pubDate>Mon, 01 Jan 2024 00:00:00 +0000</pubDate><guid>https://vlan51.com/aruba-provision/radius-login/</guid><description>&lt;p&gt;How to configure RADIUS authentication for switch management logins on HPE Aruba ArubaOS-Switch using Microsoft NPS, allowing administrators to log in with Active Directory credentials.&lt;/p&gt;&#10;&lt;h2 id="switch-configuration"&gt;Switch configuration &lt;a class="anchor" href="#switch-configuration" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;div class="code"&gt;&#10; &lt;div class="code-bar"&gt;&lt;span&gt;cli&lt;/span&gt;&lt;button class="copy" type="button" aria-label="Copy to clipboard"&gt;Copy&lt;/button&gt;&lt;/div&gt;&lt;pre&gt;&lt;code&gt;radius-server host 192.168.50.80 key reallysecretkey&#10;&#10;aaa authentication login privilege-mode&#10;aaa authentication console login radius local&#10;aaa authentication console enable radius local&#10;aaa authentication telnet login radius local&#10;aaa authentication telnet enable radius local&#10;aaa authentication web login radius local&#10;aaa authentication web enable radius local&#10;aaa authentication ssh login radius local&#10;aaa authentication ssh enable radius local&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&#10;&lt;p&gt;The &lt;code&gt;local&lt;/code&gt; fallback ensures you can still log in if the RADIUS server is unreachable. Do not remove it.&lt;/p&gt;</description></item><item><title>SNMPv3 Configuration on HPE Aruba ArubaOS-Switch with HPE IMC</title><link>https://vlan51.com/aruba-provision/snmpv3-imc/</link><pubDate>Mon, 01 Jan 2024 00:00:00 +0000</pubDate><guid>https://vlan51.com/aruba-provision/snmpv3-imc/</guid><description>&lt;p&gt;How to configure SNMPv3 on HPE Aruba ArubaOS-Switch for HPE IMC. The built-in wizard initialises SNMPv3, then you replace the wizard user with a stronger SHA/AES-128 account.&lt;/p&gt;&#10;&lt;h2 id="step-1--run-the-snmpv3-wizard"&gt;Step 1 — Run the SNMPv3 wizard &lt;a class="anchor" href="#step-1--run-the-snmpv3-wizard" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;Use throwaway passwords — you will delete this user:&lt;/p&gt;&#10;&lt;div class="code"&gt;&#10; &lt;div class="code-bar"&gt;&lt;span&gt;cli&lt;/span&gt;&lt;button class="copy" type="button" aria-label="Copy to clipboard"&gt;Copy&lt;/button&gt;&lt;/div&gt;&lt;pre&gt;&lt;code&gt;Switch(config)# snmpv3 enable&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&#10;&lt;p&gt;At the prompts: accept defaults, answer &lt;code&gt;n&lt;/code&gt; to creating a SHA user, answer &lt;code&gt;y&lt;/code&gt; to restricting SNMPv1/v2c to read-only.&lt;/p&gt;</description></item><item><title>Static ARP for Microsoft NLB Multicast on HPE Aruba ArubaOS-Switch</title><link>https://vlan51.com/aruba-provision/static-arp-nlb-multicast/</link><pubDate>Mon, 01 Jan 2024 00:00:00 +0000</pubDate><guid>https://vlan51.com/aruba-provision/static-arp-nlb-multicast/</guid><description>&lt;p&gt;Microsoft NLB in multicast mode causes switches to flood traffic to all ports because the multicast MAC address is never seen as a source — the switch cannot learn which port the cluster is on and treats it as an unknown destination.&lt;/p&gt;&#10;&lt;p&gt;HPE Aruba ArubaOS-Switch does not have a direct static MAC/ARP entry feature like Cisco, but &lt;code&gt;ip arp-mcast-replies&lt;/code&gt; combined with IGMP resolves the flooding.&lt;/p&gt;&#10;&lt;h2 id="hpe-aruba-solution"&gt;HPE Aruba solution &lt;a class="anchor" href="#hpe-aruba-solution" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;div class="code"&gt;&#10; &lt;div class="code-bar"&gt;&lt;span&gt;cli&lt;/span&gt;&lt;button class="copy" type="button" aria-label="Copy to clipboard"&gt;Copy&lt;/button&gt;&lt;/div&gt;&lt;pre&gt;&lt;code&gt;ip arp-mcast-replies&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&#10;&lt;p&gt;Enable IGMP on the NLB client VLAN, and ensure NLB is set to &lt;strong&gt;multicast&lt;/strong&gt; cluster operation mode:&lt;/p&gt;</description></item></channel></rss>