SRX

Hopefully a quick question for the guru's. 

I have a test network where I have dual-stack IPv4 and IPv6 with a neighbor that was directly connected. 

This was accomplished through the use of two neighbor statements, one with v4 and one with v6 address. 

To experiement with multi-hop, I put a "dumb" router in between the two (the other BGP end is a cisco 1941) and configured the loopback address and got multi-hop up and running, however I got a conflict when I tried to commit and had to remove the neighbor v6 address. 

'bgp'
Error in neighbor <IPv6 address here> of group external:
local and peer addresses must be from the same family
error: configuration check-out failed

When I tried to add a "local address" with a v6 address, it overwrote the v4 address? 

I am not sure if I am doing it incorrectly, or if I have to create a separate "group" to multihop over v6 from the v4 group, which is strange because when they are directly connected I can dual-stack the same group. 

Any thoughts? 

Could you post your confiiguration?

I am able to setup a single group with dual stack multihop peers in the lab.

Seems like you are using local-address command in group or bgp hierarchy.

If you are using both IPv6 and Ipv4 neighbor, you can't configure only ipv4 or Ipv6 as local address in group or bgp hierarchy.

Each family neighbor needs local-address from the same family.

If you are using local-address as v6 address in group or bgp hierarchy, you will have to configure explict ipv4 local-address with ipv4 bgp neighbor

set protocol bgp group test local-address xxxx::x

set protocol bgp group test neighbor yyyy::1 peer-as xxx

set protocol bgp group test neighbor x.x.x.x local-address z.z.z.z peer-as yy

or vice-versa

root@mx480# commit check
[edit protocols]
  'bgp'
    Error in neighbor 10.0.0.1 of group test:
local and peer addresses must be from the same family
error: configuration check-out failed

[edit]
root@mx480#

[edit]
root@mx480# deactivate protocols bgp group test neighbor 10.0.0.1

[edit]
root@mx480# commit check

root@mx480# show protocols bgp
group test {
    local-address 2222::2;
    export as-path-prepend-global;
    inactive: neighbor 10.0.0.1 {
        peer-as 400;
    }
    neighbor 2300::1 {
        peer-as 600;
    }
    neighbor 23.23.23.23 {
        local-address 2.2.2.2;
        peer-as 500;
    }
}

[edit]
root@mx480#

HTH

That is EXACTLY what I was doing. 

I had set the local-address property in the group hierarchy rather than the neighbor, which I didn't know I could do. I am just learning JunOS and I am really loving the CLI but still getting lost on a regular basis. Sometimes it isn't very clear (to me anyways) how many things can be placed at varying levels downstream in the config. 

I was just getting ready to post my config snippets for evaluation, but that reply has it solved for me. Thanks! 

Cheers.