[quagga-dev 16696] Re: quagga route shows inactive

Siva Prasad sivaprasadmsr at gmail.com
Thu Dec 28 11:24:53 GMT 2017


Hi Joakim

What do you mean by "outside Q" . I dint get you. Can you please explain ?

Regards
Siva

On Thu, Dec 28, 2017 at 10:54 AM, Joakim Tjernlund <
Joakim.Tjernlund at infinera.com> wrote:

> On Thu, 2017-12-28 at 10:37 +0530, Siva Prasad wrote:
> > CAUTION: This email originated from outside of the organization. Do not
> click links or open attachments unless you recognize the sender and know
> the content is safe.
> >
> > Hi Team
> >
> > When quagga received routes , it marked as inactive.
> >
> > Following is the route table in vtysh
> >
> >
> > root at router0D1E0F:~# vtysh
> >
> > Hello, this is Quagga (version 0.99.22.4).
> > Copyright 1996-2005 Kunihiro Ishiguro, et al.
> >
> > router0D1E0F# show ip route
> > Codes: K - kernel route, C - connected, S - static, R - RIP,
> >        O - OSPF, I - IS-IS, B - BGP, H - HSLS, o - OLSR,
> >        b - BATMAN, A - Babel,
> >        > - selected route, * - FIB route
> >
> > K * 0.0.0.0/0 via 192.168.11.1, eth0 inactive
>
> Looks like you set def. gateway outside Q. Do a static def. route from
> zebra cli instead.
>
> > R>* 10.207.241.0/24 [120/2] via 192.168.1.5, eth2.1, 13:24:19
> > C>* 127.0.0.0/8 is directly connected, lo
> > R>* 169.254.0.0/16 [120/2] via 192.168.1.5, eth2.1, 13:24:19
> > C>* 192.168.1.0/24 is directly connected, eth2.1
> > K * 192.168.11.0/24 is directly connected, eth0
> > C>* 192.168.11.0/24 is directly connected, eth0
> > K>* 192.168.11.1/32 is directly connected, eth0
> > R   192.168.111.0/24 [120/2] via 192.168.11.1 inactive, 00:00:49
> >
> >
> >
> > What can be the issue ?
> >
> > Any help is highly appreciated.
> >
> > Regards,
> > Siva
> > _______________________________________________
> > Quagga-dev mailing list
> > Quagga-dev at lists.quagga.net
> > https://lists.quagga.net/mailman/listinfo/quagga-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.quagga.net/pipermail/quagga-dev/attachments/20171228/3f3b660d/attachment.html>


More information about the Quagga-dev mailing list