[minipost]Quick LAB/config example for IPv6 BGP between HP Networking Comware v5 andCisco

A small lab showing basic configuration of BGP between Cisco and HP (Comware v5). This is just something small we deploying recently, there is nothing grand here, only a minor configuration example to follow later when needed.

NOTE on HP Comware v5  vs newer Comware v7, I understand I am using older version of the operating system on HP devices, the point is that this article is using one of my real work projects where Comware v5 was used without possibility to upgrade. However ALL Ipv6 functions that we needed were provided already on this older Comware, and when I checked, Comware v7 variant of this LAB is only changing commands syntax (actually quite easy to convert from v5 to v7 only following the “?”), therefore this article will remain in Comware v5 and I believe many readers will take the principles and will have no problem to upgrade to Comware v7 on their own.

Lab Topology:

This is a simple topology that is trying to simulate a typical L3 Edge / Distribution / Access with several HP 5800 layer3 switches and Cisco 3750 is simulating a typical WAN provider with dual-homing access. Of course all with limits of my LAB equipment. The target is to have full routing between the IPv6 Loopback on HP L3 Access and two Loopbacks on Cisco side simulating WAN destinations.

LAB Topoplogy used to present IPv6 and BGP between HP Networking Comware v5 and Cisco IOS boxes

LAB Topoplogy used to present IPv6 and BGP between HP Networking Comware v5 and Cisco IOS boxes

Part 1: Preparing cisco for IPv6

In my lab, I used my 3750 layer 3 switches. On these boxes, I had IPv6 support, but I needed to activate the IPv6 configurations via Switch Database Management (SDM) templates. This is something that controls resource allocation and by default doesn’t give any system resources to IPv6 functionality. To actually activate IPv6, you need to activate dual IPv4/IPv6 template and reload the switch. So we are going to do just that here:

and after reboot:

real config

after the same done on the oposite T5_CiscoL3-1, on T6 you can see the routes coming from the loopback:

You can also ping the BGP route for a test.

Step 2 – creating Cisco to HP BGP sessions

Cisco part T6 example:

H3C part TS4 example:



Now on H3C we need to initiate the BGP parts

Ok, great, now we have a BGP peering between Cisco and H3C established, and the HP routers see the Cisco Loopback interfaces.

SKIP – more VLANs, more basic BGP sessions and we jump to TS1/TS2 and MSR VRRPv6 groups

Step 3 – Configuring VRRP for IPv6 on H3C

This is a small extra on enabling servers access to our topology with VRRP, which functions only a little bit different on IPv6 as it uses link-local addresses for negotiation and global unicast IPv6 addresses are negotiated on top of this negotiation.

First, lets just configure the basic IPv6 VRRP in global and have a look on the interface with which we are starting here.

Next, what we need to realize is that in the broadcast domain where we want VRRP to function, we need to enable link-local IPv6 addresses first (these are the FE80::/10). We do this by simply enabling the auto configuration and then checking the interface. In the picture below we autoconfigured the FE80::BAAF:67FF:FE22:C47E as our link-local IP :

You can see that we now have a link-local IP of FE80::BAAF:67FF:FE22:C47E, we can move to VRRP configuration itself. First, we need to create a link-local VRRP IP with the typical virtual router ID (1-255). So lets choose vrid of 5 and the link-local address lets choose for simplicity “FE80::1”.

Only after this, we can create the globally unique VRRP IP with a second command:

In summary, this is the interface configuration on the interface.

Verification is with the typical “display vrrp” commands, but with IPv6 extension, please note that in the quick view with “display vrrp ipv6” you only see the link-local IPv6, the global unicast one is hidden under the verbose version of this command.

By default, we would now go to the router on the very left side of the LAB, give it a IPv6 IP on the Eth0/0 interface, configure default route towards the VRRP IP manually and that is the end like this:

 Step 4 – Redistributing static to BGP

On the TS1 and TS2 routers, we are going to create a static route towards the loopback on the TS7 router.

Now static routes are not moved to BGP tables by default and we need to use a redistribution for this, which is not hard. In fact in our very simple scenario this is just these commands to achieve:

Verification is via the display bgp vpnv6 commands like this

But more importantly, lets check this on the far end cisco box that this static route has arrived to it.

And the very FINAL TEST, pinging the two loopbacks from the oposite sides of this lab.

  1. Cisco to H3C ping
  2. H3C to Cisco ping


H3C/HP VRRP for IPv6

H3C/HP IPv6 configuration



If you enjoyed this blog, please share.

About Peter Havrila

Author's Profile