Junos OS

Hi,

 

I have a working, configured, eBGP IPv4 interface to the upstream ISP. However, as we wish to run dual stack I now have to configure IPv6 peering on the same interface.

 

So, I have configured the IPv6 address supplied by the upstream ISP, on the interface. So I now have an IPv4 and an IPv6 address on the interface. I can ping the upstream ISP's IPv6 address. However when I try and configure the following:

 

set protocols bgp group external-peers neighbor xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx

 

I get the following error:

[edit protocols]
'bgp'
Error in neighbor xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx of group external-peers:
local and peer addresses must be from the same family
error: configuration check-out failed

 

So, I am assuming that the MX thinks that the group is of IPv4 type only. However, I have configured the following:

set protocols bgp group external-peers family inet6 unicast

 

And I thought just apllying the IPv6 neighbor statement would do, but obviously not.....

 

Any help please?

 

 

Either configure a ipv6 local-address alongwith ipv6 ebgp peer configuration as below

set protocols bgp group Internal neighbor 2000::1 local-address 2000::2

or use a different group with ipv6 as a local address

---

@adgwytc wrote:

Hi,

 

So I now have an IPv4 and an IPv6 address on the interface. I can ping the upstream ISP's IPv6 address. However when I try and configure the following:

 

set protocols bgp group external-peers neighbor xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx

 

I get the following error:

[edit protocols]
'bgp'
Error in neighbor xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx of group external-peers:
local and peer addresses must be from the same family
error: configuration check-out failed

 

 

 

---

Looks like You have a "local-address $IPv4_address" in this group.

Move that to under the IPv4 neighbor and configure "local-address $IPv6_address" for under IPv6 neighbor.

 

---

@adgwytc wrote:

Hi,

 

 

 

So, I am assuming that the MX thinks that the group is of IPv4 type only. However, I have configured the following:

set protocols bgp group external-peers family inet6 unicast

 

 

 

 

---

Move this statement also under IPV6 neighbor. 

Or, better still, create a whole new group for IPv6 neighbor(s).

This will help down the road when You'll discover that You cannot mix IPv4 and IPv6 prefixes in the same prefix-list.

HTH

Thx
Alex

It's all good. I managed to configure it with a new IPv6 group and am now getting the full IPv6 Internet Routing Table.

 

Thanks

 

 

Hi aarseniev,

 

I'm having a real problem trying to advertise my IPv6 prefix's.... I have configured what I believe to be the aggregation corerctly, but I'm really not sure.

 

I know the upstream ISP will not accept anything above a ::/48, so that is what I am advertsing, but when I complete the command:

 

show route advertsing-protocol bgp <peer address>

 

I see nothing advertised.....

 

Any help on configuring IPv6 aggregation would be great....

 

Thanks

Hello,

I hope You configured a static or aggregate /48 IPv6 route? Like below:

set routing-options rib inet6.0 static route 2002::/48 discard

or

set routing-options rib inet6.0 aggregate 2002::/48 discard
set routing-options rib inet6.0 aggregate 2002::/48 as-path origin igp

 

And then matched it in the IPv6 neighbor' export policy? Like below:

 

set policy-options policy-statement ipv6-export term t1 from protocol [ static aggregate ]
set policy-options policy-statement ipv6-export term t1 then accept
set protocols bgp group ipv6-ebgp neighbor 2001::1 export ipv6-export

- then it should work.

Please post Your config and "show bgp neighbor" printout if it does not.

HTH

Thx

Alex