[j-nsp] EX4600 : Ping problem

[Eric Van Tol]

> 'no route to host' normally means 'did not get an
> arp reply, could not deliver packet'.

"no route to host" normally indicates that the route does not exist in the routing table, not that an ARP response isn't coming back.

Are all your interfaces operationally up, including the IRB? 

-evt

> -----Original Message-----
> From: juniper-nsp [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of
> Chris Morrow
> Sent: Monday, November 28, 2016 3:06 PM
> To: deloin.robert at laposte.net
> Cc: juniper-nsp at puck.nether.net
> Subject: Re: [j-nsp] EX4600 : Ping problem
> 
> SAt Mon, 28 Nov 2016 20:55:04 +0100 (CET),
> Deloin via juniper-nsp <juniper-nsp at puck.nether.net> wrote:
> >
> >
> > Hello,
> >
> > I have 2 EX4600 switchs.
> > They have the same symetric configurations:
> >
> >
> > SWITCH EX4600-1                        SWITCH EX4600-2
> >
> > interfaces {                           interfaces {
> >   xe-0/0/1 {                             xe-0/0/1 {
> >     unit 0 {                               unit 0 {
> >       family ethernet-switching {            family ethernet-switching {
> >         interface-mode access;                 interface-mode access;
> >         vlan {                                 vlan {
> >           members vlan-RESEAUX;                  members vlan-RESEAUX;
> >         }                                      }
> >         storm-control default;                 storm-control default;
> >       }                                      }
> >     }                                      }
> >   }                                      }
> >
> >   irb {                                  irb {
> >     unit 0 {                               unit 0 {
> >       family inet {                          family inet {
> >         address 10.101.0.4/16;                 address 10.101.0.5/16;
> >       }                                      }
> >     }                                      }
> >   }                                      }
> > }                                      }
> >
> >
> > routing-options {                      routing-options {
> >   static {                               static {
> >     route 0.0.0.0/0 next-hop 10.101.0.1;   route 0.0.0.0/0 next-hop
> 10.101.0.1;
> >   }                                      }
> > }                                      }
> >
> >
> > vlans {                                vlans {
> >   default {                              default {
> >     vlan-id 1;                             vlan-id 1;
> >   }                                      }
> >
> >   vlan-RESEAUX {                         vlan-RESEAUX {
> >     vlan-id 98;                            vlan-id 98;
> >     l3.interface irb.0;                    l3.interface irb.0;
> >   }                                      }
> > }                                      }
> >
> > I put an optic fiber between xe-0/0/1 from a switch and xe-0/0/1 from the
> other switch.
> > And I can't ping the @ 10.101.0.3 and 10.101.0.4 from each switchs.
> 
> you appear to have 2 interfaces connected, with a single fiber and a
> /16 netblock assigned.  Then you ping .3 which is on neither
> interface, so ... 'no route to host' normally means 'did not get an
> arp reply, could not deliver packet'.
> 
> this sounds like it's working exactly as expected?
> 
> > I obtain :
> > root at EX4600-01# run ping 10.101.0.3
> > PING 10.101.0.3 (10.101.0.3): 56 data bytes
> > ping: sendto: No route to host
> > ping: sendto: No route to host
> > ping: sendto: No route to host
> > ping: sendto: No route to host
> > the same for the other.
> >
> > Can you help me. Can you tell me where is the mistake, or what I forget ?
> >
> > Thank you !
> > _______________________________________________
> > juniper-nsp mailing list juniper-nsp at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/juniper-nsp
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp