<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>HPE Comware v7 on vlan51</title><link>https://vlan51.com/comware-v7/</link><description>Recent content in HPE Comware v7 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/comware-v7/index.xml" rel="self" type="application/rss+xml"/><item><title>BFD Static Route Tracking on HPE Comware v7</title><link>https://vlan51.com/comware-v7/bfd-static-route-tracking/</link><pubDate>Mon, 01 Jan 2024 00:00:00 +0000</pubDate><guid>https://vlan51.com/comware-v7/bfd-static-route-tracking/</guid><description>&lt;p&gt;How to use BFD echo mode with static route tracking on HPE Comware v7. When the primary path fails, BFD detects it rapidly and the tracked static route is withdrawn, activating the backup.&lt;/p&gt;&#10;&lt;p&gt;BFD echo mode does not require BFD support on the remote peer — packets loop back through the remote device, so this works with any upstream equipment.&lt;/p&gt;&#10;&lt;p&gt;Track is a detection module in Comware that reports positive or negative based on interface status, link status, reachability or performance. Here it&amp;rsquo;s paired with BFD to watch a remote IP, and static route preferences change the routing table when the far end becomes unreachable.&lt;/p&gt;</description></item><item><title>NTP Configuration on HPE Comware v7 Switches</title><link>https://vlan51.com/comware-v7/ntp/</link><pubDate>Mon, 01 Jan 2024 00:00:00 +0000</pubDate><guid>https://vlan51.com/comware-v7/ntp/</guid><description>&lt;p&gt;How to configure NTP on HPE Comware v7 with BST (British Summer Time) handling for UK deployments.&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;system-view&#10;clock summer-time BST 02:00:00 March last Sunday 02:00:00 October last Sunday 02:00:00&#10;ntp-service unicast-server 1.2.3.4 priority 1&#10;ntp-service unicast-server 4.5.6.7 priority 2&#10;save f&#10;quit&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&#10;&lt;blockquote&gt;&#10;&lt;p&gt;For Comware v5 syntax, see &lt;a href="https://vlan51.com/comware-v5/ntp"&gt;NTP on Comware v5&lt;/a&gt;.&lt;/p&gt;&#10;&lt;/blockquote&gt;</description></item><item><title>Policy Based Routing (PBR) on HPE Comware v7</title><link>https://vlan51.com/comware-v7/policy-based-routing/</link><pubDate>Mon, 01 Jan 2024 00:00:00 +0000</pubDate><guid>https://vlan51.com/comware-v7/policy-based-routing/</guid><description>&lt;p&gt;How to configure Policy Based Routing (PBR) on HPE Comware v7. Traffic is matched by ACLs and redirected to an alternative next-hop, overriding the routing table.&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;The setup is identical to the &lt;a href="https://vlan51.com/aruba-provision/policy-based-routing/"&gt;ArubaOS-Switch PBR guide&lt;/a&gt;. The switch (&lt;code&gt;.254&lt;/code&gt;) has a default gateway of &lt;code&gt;2.2.2.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 breakout via the default gateway, internet via the firewall at 1.1.1.1" loading="lazy" decoding="async"&gt;&lt;/a&gt;&lt;figcaption&gt;PBR topology: local breakout via the default gateway, internet via the firewall at 1.1.1.1&lt;/figcaption&gt;&#10;&lt;/figure&gt;&#10;&lt;p&gt;From &lt;code&gt;192.168.10.0/24&lt;/code&gt;: internal traffic (to &lt;code&gt;10.0.0.0/8&lt;/code&gt; or &lt;code&gt;192.168.0.0/16&lt;/code&gt;) uses the normal routing table, internet traffic is sent to &lt;code&gt;1.1.1.1&lt;/code&gt;.&lt;/p&gt;</description></item><item><title>Policy Based Routing Within a VRF/VPN-Instance on HPE Comware v7</title><link>https://vlan51.com/comware-v7/policy-based-routing-vrf/</link><pubDate>Mon, 01 Jan 2024 00:00:00 +0000</pubDate><guid>https://vlan51.com/comware-v7/policy-based-routing-vrf/</guid><description>&lt;p&gt;How to configure PBR within a VRF/VPN-Instance on HPE Comware v7. Useful in multi-tenant environments where traffic must be steered within an isolated routing domain.&lt;/p&gt;&#10;&lt;blockquote&gt;&#10;&lt;p&gt;PBR within a VRF is only supported on Comware v7 — not Comware v5.&lt;/p&gt;&#10;&lt;/blockquote&gt;&#10;&lt;p&gt;Only a few changes are needed compared with &lt;a href="https://vlan51.com/comware-v7/policy-based-routing/"&gt;PBR outside a VRF&lt;/a&gt;: the VPN-Instance has to be referenced in the next-hop and in the ACL rules. A VPN-Instance is Comware&amp;rsquo;s name for a VRF.&lt;/p&gt;</description></item><item><title>RADIUS Login Authentication on HPE Comware v7 Switches</title><link>https://vlan51.com/comware-v7/radius-login/</link><pubDate>Mon, 01 Jan 2024 00:00:00 +0000</pubDate><guid>https://vlan51.com/comware-v7/radius-login/</guid><description>&lt;p&gt;How to configure RADIUS management login on HPE Comware v7 using Microsoft NPS.&lt;/p&gt;&#10;&lt;blockquote&gt;&#10;&lt;p&gt;This covers the Comware configuration only. For the NPS server setup, see the &lt;a href="https://vlan51.com/aruba-provision/radius-login"&gt;ArubaOS-Switch RADIUS login guide&lt;/a&gt; which covers the NPS side in full.&lt;/p&gt;&#10;&lt;/blockquote&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;Create a RADIUS scheme:&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;radius scheme nps&#10; primary authentication x.x.x.x&#10; primary accounting x.x.x.x&#10; key authentication simple reallysecurekey&#10; key accounting simple reallysecurekey&#10; user-name-format without-domain&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&#10;&lt;p&gt;Apply to the default domain:&lt;/p&gt;</description></item><item><title>VRF / VPN-Instance Inter-VLAN Routing on HPE Comware v7</title><link>https://vlan51.com/comware-v7/vrf-inter-vlan-routing/</link><pubDate>Mon, 01 Jan 2024 00:00:00 +0000</pubDate><guid>https://vlan51.com/comware-v7/vrf-inter-vlan-routing/</guid><description>&lt;p&gt;How to route between VLANs that sit in different VPN-Instances (VRFs) on an HPE Comware switch.&lt;/p&gt;&#10;&lt;p&gt;A customer running VPN-Instances on HPE Comware 5500-HI switches needed the switch to act as the default gateway and route between two VPN-Instances. A VPN-Instance splits the routing table, the same as a VRF on Cisco, so this isn&amp;rsquo;t enabled by default. &lt;strong&gt;You can&amp;rsquo;t do it with static routing&lt;/strong&gt;: it needs MP-BGP to leak routes between the instances using route targets.&lt;/p&gt;</description></item></channel></rss>