In principle, which ever router has 12.1.1.1 as inet address, also needs to have ::ffff:12.1.1.1 as a (secondary) inet6 address, and advertise this in IGP.
Hello per， Thanks for ur response.R1 dont accept the route in 10.4. how do we do make it accept the route. Thanks ------------------ Original ------------------ From: "Per Granath"<per.gran...@gcc.com.cy<mailto:per.gran...@gcc.com.cy>>; Date: Fri, Mar 16, 2012 11:46 PM To: "juniper-nsp"<juniper-nsp@puck.nether.net<mailto:juniper-nsp@puck.nether.net>>; Cc: "bruno"<bruno.juni...@gmail.com<mailto:bruno.juni...@gmail.com>>; Subject: RE: [j-nsp] bgp ipv6 route problem In 10.4 the automatically created "IPv4-compatible IPv6-address" changed, that is the (::ffff:12.1.1.1). Before 10.4 it used to be just (::12.1.1.1). If you have mixture in the network it will be confusing... BTW, the JNCIE exam is now using 10.4. > i met some odd problem on junos 10.4 . two router(R1----R2) establish ipv4 > bgp session with ipv4 and ipv6 family. session is up. only the ipv4 route is > accept. not ipv6 route. so i trace on r1 . i find the ipv6 route is ignore. > but > not problem on junos 9.4. > lab@junos104.#<mailto:lab@junos104.#> run show bgp summary logical-system r1 > 12.1.1.1 400 26 28 0 1 9 > Establ > inet.0: 1/1/1/0 > inet6.0: 0/0/0/0 > > > > Mar 15 03:12:42.988838 bgp_nexthop_sanity: peer 12.1.1.1 (External AS 600) > next hop ::ffff:12.1.1.1 unexpectedly remote, ignoring routes in this update > Mar 15 03:12:42.988853 bgp_rcv_nlri: Peer 12.1.1.1 (External AS 600) Mar 15 > 03:12:42.988865 bgp_rcv_nlri: 2222:2222:2222::/48 Mar 15 03:12:42.988880 _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
