Routing

Hi,

Am having challenge pinging the IP i have configured on one of the interfaces on my MX. what could i be missing??

this is the config: 

re0# show so-2/0/1
speed oc3;
clocking internal;
sonet-options {
    fcs 32;
    rfc-2615;
}
unit 0 {
    family inet {
        rpf-check {
            fail-filter RPF-FAIL;
            mode loose;
        }
  
        address 124.36.46.65/31;
    }
    family inet6 {
        address 2c0f:f748:101:1::2/126;
    }
}

This is what happens when i try ping the above IP from the router itself:

re0# run ping 2c0f:f748:101:1::2

PING6(56=40+8+8 bytes) 2c0f:f748:101:1::2 --> 2c0f:f748:101:1::2
^C
--- 2c0f:f748:101:1::2 ping6 statistics ---
19 packets transmitted, 0 packets received, 100% packet loss

 Thanks All.

A couple of years ago, I started playing with JunOS and IPv6.

For routers, I found this little gem of info that was required before IPv6 would work:

I have a J2320, and after I did this, my IPv6 worked 🙂

security {
    forwarding-options {
        family {
            inet6 {
                mode flow-based;
            }
        }
    }

I also have an EX4200, and this was not needed.

I cannot say if you need this or not, but I'm thinking you do.

a few links of info:

http://www.juniper.net/documentation/en_US/junos12.2/topics/task/configuration/interface-security-logical-property-ipv6-traffic-flow-based-processing-enabling-cli.html

IPv6 related books from Juniper (and free!!)

http://www.juniper.net/us/en/training/jnbooks/day-one/networking-technologies-series/exploring-ipv6/index.page

http://www.juniper.net/us/en/training/jnbooks/day-one/networking-technologies-series/advanced-ipv6-config/index.page

hth...Jeff

Do i need do this for M series and MX series routers??

Regards,
sheeel.

Nope you only needthe flow stuff on the srx's , as you can see below i can ping the v6 address fine on a mx , is the interfcae up ? can you ping the v4 address ? 

[edit]
iank@test-mx-re0# show interfaces ge-1/0/2 
unit 0 {
    family inet6 {
        address 2c0f:f748:101:1::2/126;
    }
}

[edit]
iank@test-mx-re0# run ping 2c0f:f748:101:1::2    
PING6(56=40+8+8 bytes) 2c0f:f748:101:1::2 --> 2c0f:f748:101:1::2
16 bytes from 2c0f:f748:101:1::2, icmp_seq=0 hlim=64 time=0.197 ms
16 bytes from 2c0f:f748:101:1::2, icmp_seq=1 hlim=64 time=0.035 ms
^C
--- 2c0f:f748:101:1::2 ping6 statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max/std-dev = 0.035/0.116/0.197/0.081 ms

hi,

Yes, the interface is up and i can ping the V4 address.see below

re0# show interfaces so-2/0/1
speed oc3;
clocking internal;
sonet-options {
    fcs 32;
    rfc-2615;
}
unit 0 {
    family inet {
        rpf-check {
            fail-filter RPF-FAIL;
            mode loose;
        }
      
        address xxx.xxx.xxx.1/31;
    }
    family inet6 {
        address 2c0f:f748:101:1::2/126;

and here is the ping to the v4 address:

-re0# run ping xxx.xxx.xxx.1
PING xxx.xxx.xxx.1 (xxx.xxx.xxx.1): 56 data bytes
64 bytes from xxx.xxx.xxx.1: icmp_seq=0 ttl=64 time=0.583 ms
64 bytes from xxx.xxx.xxx.1: icmp_seq=1 ttl=64 time=0.108 ms
64 bytes from xxx.xxx.xxx.1: icmp_seq=2 ttl=64 time=0.101 ms
64 bytes from xxx.xxx.xxx1: icmp_seq=3 ttl=64 time=0.100 ms
64 bytes from xxx.xxx.xxx.1: icmp_seq=4 ttl=64 time=0.108 ms
64 bytes from xxx.xxx.xxx.1: icmp_seq=5 ttl=64 time=0.106 ms
64 bytes from xxx.xxx.xxx.1: icmp_seq=6 ttl=64 time=0.115 ms
64 bytes from xxx.xxx.xxx.1: icmp_seq=7 ttl=64 time=0.107 ms
^C
--- xxx.xxx.xxx.1 ping statistics ---
8 packets transmitted, 8 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.100/0.166/0.583/0.158 ms

What could be wrong ?? this interface was supporting V6 address before.as we had aprevious v6 BGP session peering on P2P V6 address configured on the same interface.

the only thing i can say changed since then is the junos upgrade on this router. this is the current version running.

-re0> show version
Hostname: xxxxxxx
Model: m120
JUNOS Base OS boot [12.3R2.5]
JUNOS Base OS Software Suite [12.3R2.5]
JUNOS Kernel Software Suite [12.3R2.5]
JUNOS Crypto Software Suite [12.3R2.5]
JUNOS Packet Forwarding Engine Support (M/T/EX Common) [12.3R2.5]
JUNOS Packet Forwarding Engine Support (M120) [12.3R2.5]
JUNOS Online Documentation [12.3R2.5]
JUNOS Services AACL Container package [12.3R2.5]
JUNOS Services Application Level Gateways [12.3R2.5]
JUNOS AppId Services [12.3R2.5]
JUNOS Border Gateway Function package [12.3R2.5]
JUNOS Services Captive Portal and Content Delivery Container package [12.3R2.5]
JUNOS Services HTTP Content Management package [12.3R2.5]
JUNOS IDP Services [12.3R2.5]
JUNOS Services LL-PDF Container package [12.3R2.5]
JUNOS Services NAT [12.3R2.5]
JUNOS Services PTSP Container package [12.3R2.5]
JUNOS Services RPM [12.3R2.5]
JUNOS Services Stateful Firewall [12.3R2.5]
JUNOS Voice Services Container package [12.3R2.5]
JUNOS Services Example Container package [12.3R2.5]
JUNOS Services Crypto [12.3R2.5]
JUNOS Services SSL [12.3R2.5]
JUNOS Services IPSec [12.3R2.5]
JUNOS Runtime Software Suite [12.3R2.5]
JUNOS platform Software Suite [12.3R2.5]
JUNOS Routing Software Suite [12.3R2.5]
JUNOS Web Management [12.3R2.5]

Check you filter on lo0 interface and allow ipv6. 

Akushner,

thank you so much. the issue was the filter on the lo0 interface. i had to add next-header ICMP6 and ping responded.

Sheeel.

If the v6 peering was working before the upgrade and nothing else was changed apart from a software upgrade , then i suggest a call is logged with JTAC to investiagte a possible PR.

is v6 working anywhere else on the box ? 

it was filter issue applied on the lo0 interface that wasnt allowing v6.

Sheeel.