Andrew Gideon | 29 Jun 05:26 2015

[quagga-users 14031] "SLOW THREAD" errors and "Hold Timer Expired" events on all neighbors

I've an older "router" running CentOS5 that I'm trying to replace with
one running CentOS7.  Both machines have 1G of RAM.

I'm having no problems with the older router.  My reason for upgrading
is to get away from the old 2.6.18 kernel and into a newer (3.10) kernel
with support for RFC6164, ipset, etc.

The older machine is running Quagga v0.99.22.4.  I've tried both
quagga-0.99.22.4-4.el7 and 0.99.24.1 on the newer machine.

In both cases, there are up to six IPv4 neighbors.  Two are eBGP peers
providing full feeds.  The other four are iBGP peers providing whatever
routes are "best" on those devices.

Just because of how our topology is, this usually means 500000+ routes
from three of the six peers.  The others are just sending a small number
of routes for the subnets to which they provide gateway service.

The newer router also has two IPv6 iBGP peerings, each providing about
10000 to 20000 routes.

Very rarely, I'll see something like:

        SLOW THREAD: task bgp_read (987250) ran for 9292ms (cpu time 9266ms)

on the older router.

On the newer router, the slightest route change (ie. adding or removing
a gateway IP for some subnet, which means adding or removing a single
route that will be distributed by BGP) often causes errors like:
(Continue reading)

durga | 25 Jun 08:40 2015
Picon

[quagga-users 14022] query w.r.t generic behaviour of quagga engine when PBR is in place

Hi All,

I am just looking for a clarification on quagga engine behaviour in the below scenario.
                           _1_____________1_      
                           |                            |_   
10.10.10.100--(R1)                           _(R2) -- 3(40.40.40.100)
                           |_2____________2_|
    
the router R2 has learnt the route to destination network 10.10.10.100 via interface 2, through OSPF

Currently , the behaviour that I notice is that R2 drops all packets destined to 40.40.40.100 from 10.10.10.100 received on interface 1, but permits packets  from interface 2.  I was wondering if quagga engine is intrinsically filtering packets from 10.10.10.100 on interface 1.



Cheers!
Durga

_______________________________________________
Quagga-users mailing list
Quagga-users@...
https://lists.quagga.net/mailman/listinfo/quagga-users
Arnaud Launay | 20 Jun 10:18 2015

[quagga-users 14020] Quagga BGPD crash

Hello,

We had last week a crash on the bgpd daemon, under
Quagga 0.99.23.1, on a Gentoo server with few traffic.

The only thing we found are those messages:

BGP: Received signal 11 at 1434421685 (si_addr 0x0); aborting...
Backtrace for 10 stack frames:
/usr/lib64/libzebra.so.0(zlog_backtrace_sigsafe+0x2a)[0x7fdb9b05650a]
/usr/lib64/libzebra.so.0(zlog_signal+0x319)[0x7fdb9b056c09]
/usr/lib64/libzebra.so.0(+0x3dea5)[0x7fdb9b060ea5]
/lib64/libc.so.6(+0x35090)[0x7fdb9a6e1090]
/usr/sbin/bgpd[0x4329be]
/usr/lib64/libzebra.so.0(work_queue_run+0xc9)[0x7fdb9b061a79]
/usr/lib64/libzebra.so.0(thread_call+0x3e)[0x7fdb9b04952e]
/usr/sbin/bgpd(main+0x318)[0x41a7c8]
/lib64/libc.so.6(__libc_start_main+0xf5)[0x7fdb9a6cda95]
/usr/sbin/bgpd[0x41a84c]
2015/06/16 04:28:06 ZEBRA: client 16 disconnected. 564367 bgp routes removed from the rib

We just restarted the daemon, it works fine since.

There's nothing elsewhere in the logs. Any idea ?

	Arnaud.
Torbjorn Tornkvist | 17 Jun 08:54 2015
Picon

[quagga-users 14011] BGP Update messages

Hi,

I'm trying to understand when Update messages are issued.

Specifically, when I change the Metric (MED) value in a route-map,
no Update message seem to be generated unless I run: clear bgp <neighbor>

So my question is: should an Update message be issued when the Metric 
value change ?

Cheers, Tobbe
Jafar Al-Gharaibeh | 11 Jun 18:30 2015

[quagga-users 14007] Running Multiple Instances of Quagga

Hi,

   While we are waiting for the dust to settle on VRF support, and also 
adding VRF-aware daemons, I'm trying to run multiple instances of Quagga 
on the same machine isolated in network namespaces. There are several 
command line options that help doing that, like pointing to different 
config files, pid files, etc. Things seem to be a little more tricky 
when it comes to vtysh.

Going through the email-list history didn't reveal enough information on 
how to do it properly, but I know that several people on the list 
indicated that they have done this kind of setup before. Did anybody 
create a guide/help on  how to do that?  Maybe have scripts that you are 
willing to share?

Thanks in Advance,
Jafar
David Ganor | 11 Jun 15:50 2015

[quagga-users 14006] ISISd consumes 100% CPU

Hi,
I'm running quagga 0.9.24 on Ubuntu12.04. The Adjacent router is a 
JUNIPER EX-series running both ISIS and OSPF.
Recently I've noticed that some hosts connected to the Juniper are not 
reachable due to the fact that the route towards them does not exist.
During such periods (before I restart the quagga service), I've also 
noticed that the ISISd consumed 100% CPU (as indicated by 'top')
Is there a known issue related to this?
Anything I can do to limit CPU consumption?
I'm attaching a fragment of the ISISd syslog, if it will help...

Thanks!

-- 
Best regards,
David Ganor

|||||||||||||||||||||||||||||||||||
Cell: +972-54-3090299
Tel: +972-74-7028642
Fax: +972-153-74-7028642

SW developer
www.oliver-solutions.com
|||||||||||||||||||||||||||||||||||

2015/06/11 4:00:53 ISIS: Quagga-ISISd 0.99.24 starting: vty <at> 2608
2015/06/11 4:00:53 ISIS: %ADJCHANGE: Adjacency to 0192.0169.0001 (eth1) changed from Unknown to
Initializing, unspecified
2015/06/11 4:00:53 ISIS: %ADJCHANGE: Adjacency to 0192.0169.0001 (eth1) changed from Initializing to
Up, own SNPA found in LAN Neighbours TLV
2015/06/11 4:00:54 ISIS: ISIS-Spf: No LSP 0192.0169.0001.00-00 found for IS adjacency L1 on eth1 (ID 1)
2015/06/11 4:00:54 ISIS: ISIS-Spf: No LSP found for 0192.0169.0001.00-00
2015/06/11 4:00:54 ISIS: ISIS-Spf: No LSP 0192.0169.0001.00-00 found for IS adjacency L1 on eth1 (ID 1)
2015/06/11 4:00:54 ISIS: ISIS-Spf: No LSP found for 0192.0169.0001.00-00
2015/06/11 4:01:24 ISIS: ISIS-Spf: No LSP 0192.0169.0001.00-00 found for IS adjacency L1 on eth1 (ID 1)
2015/06/11 4:01:24 ISIS: ISIS-Spf: No LSP found for 0192.0169.0001.00-00
2015/06/11 4:01:24 ISIS: ISIS-Spf: No LSP 0192.0169.0001.00-00 found for IS adjacency L1 on eth1 (ID 1)
2015/06/11 4:01:24 ISIS: ISIS-Spf: No LSP found for 0192.0169.0001.00-00
...
...
2015/06/11 11:31:38 ISIS: No support for ES-IS packet IDRP=82
2015/06/11 11:31:39 ISIS: ISIS-TLV (ISIS): unsupported TLV type 14, length 2
2015/06/11 11:32:23 ISIS: No support for ES-IS packet IDRP=82
2015/06/11 11:33:11 ISIS: No support for ES-IS packet IDRP=82
2015/06/11 11:33:39 ISIS: Nonexitant ip address 2001:10:254:104::a3f/64 removal attempt from 		     
circuit 140
2015/06/11 11:33:39 ISIS: Nonexitant ip address 2001:10:254:104::ad8/64 removal attempt from 		     
circuit 140
2015/06/11 11:33:39 ISIS: Nonexitant ip address 2001:10:254:104::987/64 removal attempt from 		     
circuit 140
2015/06/11 11:33:39 ISIS: Nonexitant ip address 2001:10:254:104::a38/64 removal attempt from 		     
circuit 140
2015/06/11 11:33:39 ISIS: Nonexitant ip address 2001:10:254:104::922/64 removal attempt from 		     
circuit 140
2015/06/11 11:33:39 ISIS: Nonexitant ip address 2001:10:254:104::c3e/64 removal attempt from 		     
circuit 140
2015/06/11 11:33:39 ISIS: Nonexitant ip address 2001:10:254:104::dec/64 removal attempt from 		     
circuit 140
2015/06/11 11:33:39 ISIS: Nonexitant ip address 2001:10:254:104::b6e/64 removal attempt from 		     
circuit 140
2015/06/11 11:33:39 ISIS: Nonexitant ip address 2001:10:254:104::bcb/64 removal attempt from 		     
circuit 140
2015/06/11 11:33:39 ISIS: Nonexitant ip address 2001:10:254:104::b05/64 removal attempt from 		     
circuit 140
2015/06/11 11:33:39 ISIS: Nonexitant ip address 2001:10:254:104::87a/64 removal attempt from 		     
circuit 140
2015/06/11 11:33:59 ISIS: No support for ES-IS packet IDRP=82
2015/06/11 11:34:31 ISIS: ISIS-TLV (ISIS): unsupported TLV type 14, length 2
2015/06/11 11:34:45 ISIS: No support for ES-IS packet IDRP=82
2015/06/11 11:35:32 ISIS: No support for ES-IS packet IDRP=82
2015/06/11 11:36:32 ISIS: No support for ES-IS packet IDRP=82
2015/06/11 11:37:18 ISIS: No support for ES-IS packet IDRP=82
2015/06/11 11:38:18 ISIS: No support for ES-IS packet IDRP=82
2015/06/11 11:38:52 ISIS: ISIS-TLV (ISIS): unsupported TLV type 14, length 2
2015/06/11 11:39:13 ISIS: No support for ES-IS packet IDRP=82
2015/06/11 11:40:08 ISIS: No support for ES-IS packet IDRP=82
2015/06/11 11:40:58 ISIS: No support for ES-IS packet IDRP=82
2015/06/11 11:41:43 ISIS: No support for ES-IS packet IDRP=82
2015/06/11 11:42:42 ISIS: No support for ES-IS packet IDRP=82
2015/06/11 11:43:31 ISIS: No support for ES-IS packet IDRP=82
2015/06/11 11:44:27 ISIS: No support for ES-IS packet IDRP=82
2015/06/11 11:45:13 ISIS: No support for ES-IS packet IDRP=82
2015/06/11 11:46:08 ISIS: No support for ES-IS packet IDRP=82
2015/06/11 11:47:02 ISIS: No support for ES-IS packet IDRP=82
2015/06/11 11:47:42 ISIS: ISIS-TLV (ISIS): unsupported TLV type 14, length 2
2015/06/11 11:47:57 ISIS: No support for ES-IS packet IDRP=82
2015/06/11 11:48:56 ISIS: No support for ES-IS packet IDRP=82
2015/06/11 11:49:41 ISIS: No support for ES-IS packet IDRP=82
2015/06/11 11:50:38 ISIS: No support for ES-IS packet IDRP=82
2015/06/11 11:51:28 ISIS: No support for ES-IS packet IDRP=82
2015/06/11 11:52:13 ISIS: ISIS-TLV (ISIS): unsupported TLV type 14, length 2
2015/06/11 11:52:21 ISIS: No support for ES-IS packet IDRP=82
2015/06/11 11:53:01 ISIS: Nonexitant ip address 2001:10:254:104::1000/64 removal attempt from 		     
circuit 140
2015/06/11 11:53:07 ISIS: No support for ES-IS packet IDRP=82
2015/06/11 11:54:03 ISIS: No support for ES-IS packet IDRP=82
2015/06/11 11:54:49 ISIS: No support for ES-IS packet IDRP=82
2015/06/11 11:55:45 ISIS: No support for ES-IS packet IDRP=82
2015/06/11 11:56:37 ISIS: No support for ES-IS packet IDRP=82
2015/06/11 11:57:25 ISIS: No support for ES-IS packet IDRP=82
...
_______________________________________________
Quagga-users mailing list
Quagga-users@...
https://lists.quagga.net/mailman/listinfo/quagga-users
Quentin Giorgi | 10 Jun 09:34 2015
Picon

[quagga-users 14005] setting route tag to redistributed connected into ospf.

Hi all,

I am trying to tag some routes that i redistribute from RIB (connected)
to OSPF in order to filter them all over areas depending of the tag.
I have heard set tag and match tag have been added,in fact thsi is not
working for me, but i must do something bad.

for this i do the following: (Here is the configuration)

router ospf
 redistribute connected route-map partners

ip prefix-list others seq 5 permit 193.x.x.0/24
ip prefix-list partners seq 5 permit 19y.y.y.0/24
!
route-map partners permit 10
 match ip address prefix-list partners
 set tag 77
!
route-map partners permit 20
 match ip address prefix-list others

I have restarted deamons and
sh ip pref det tell me this:

OSPF: ip prefix-list others:
   count: 1, range entries: 0, sequences: 5 - 5
   seq 5 permit 193.x.x.0/24 (hit count: 7, refcount: 7)
OSPF: ip prefix-list partners:
   count: 1, range entries: 0, sequences: 5 - 5
   seq 5 permit 19y.y.y.0/24 (hit count: 7, refcount: 14)

sh ip ospf data extern self

  LS Seq Number: 80000008
  Checksum: 0x5c70
  Length: 36
  Network Mask: /24
        Metric Type: 2 (Larger than any link state path)
        TOS: 0
        Metric: 20
        Forward Address: 0.0.0.0
        External Route Tag: 0

Any advice welcome !!!

Best regards,

--

-- 
XU, YANG (YANG | 8 Jun 23:54 2015
Picon

[quagga-users 14004] Label in NLRI support


Hi all,

I am new to BGP and Quagga. When I did packet trace for BGP protocol between two OpenBSD based BGP routers, I
see MP_REACH_NLRI as following: 

            MP_REACH_NLRI (34 bytes)
                Flags: 0x80 (Optional, Non-transitive, Complete)
                Type code: MP_REACH_NLRI (14)
                Length: 31 bytes
                Address family: IPv4 (1)
                Subsequent address family identifier: Labeled VPN Unicast (128)
                Next hop network address (12 bytes)
                    Next hop: Empty Label Stack RD=0:0 IPv4=10.42.42.1 (12)
                Subnetwork points of attachment: 0
                Network layer reachability information (14 bytes)
                    Label Stack=666 (bottom) RD=310:1, IPv4=172.16.0.0/16
                        MP Reach NLRI Prefix length: 104
                        MP Reach NLRI Label Stack: 666 (bottom)
                        MP Reach NLRI Route Distinguisher: 310:1
                        MP Reach NLRI IPv4 prefix: 172.16.0.0 (172.16.0.0)

My question is if I use Quagga as BGP routers, can I configure Quagga to insert Label Stack (e.g. "MP Reach
NLRI Label Stack: 666" as above) to the routes it receives? 

Thanks in advance,

-Yang
AJ NOURI | 3 Jun 07:49 2015
Picon

[quagga-users 14002] Annoying logs: "BABEL: Expiring old routes."

Hi,

How to get rid of these logging inf.

2015/06/03 15:40:50 BABEL: Expiring old routes.
2015/06/03 15:41:20 BABEL: Expiring old routes.
2015/06/03 15:41:50 BABEL: Expiring old routes.
2015/06/03 15:41:57 BABEL: Checking neighbours.
2015/06/03 15:42:15 BABEL: Expiring old routes.

they are appearing everywhere, in the shell as well in the vtysh console.
_______________________________________________
Quagga-users mailing list
Quagga-users@...
https://lists.quagga.net/mailman/listinfo/quagga-users
Ram Krishna | 29 May 13:01 2015
Picon

[quagga-users 14000] Generating CLI commands from Configuration

Hi,
 
Is there any support for generating CLI commands from the stored configuration on a device running quagga?
 
thanks,
Ram
_______________________________________________
Quagga-users mailing list
Quagga-users@...
https://lists.quagga.net/mailman/listinfo/quagga-users
Pedro Ribeiro | 21 May 19:12 2015
Picon

[quagga-users 13999] OSPFv3 daemon inconsistencies between Quagga versions (and problems!)

Hello,

Sorry for the long email, I'm trying to send all the information that seems important for the problem analysts.

I'm using a few PCs working as routers with Quagga in a mixed vendor scenario.
After upgrading Quagga in one of the routers, a Cisco router became inaccessible over IPv6.
After analysis I've found the route to the Cisco's loopback interface was missing in the upgraded Quagga.
With some testing I've concluded that changing the address prefix from /128 to /127 changed the behaviour
of the newer Quagga and made the route appear in the table (with an undesired prefix but that's a minor problem).

Following I'm presenting a few command outputs from 3 of the equipments.
The Cisco that become inaccessible, an old Quagga (0.99.22.4) and the newer (0.99.24.1).

The loopback interface of the Cisco router is configured this way:

interface Loopback6
 no ip address
 ipv6 address 2001:690:2008::1003/128
 ipv6 ospf network point-to-point
 ipv6 ospf 1 area 0
end
The state of the Cisco database regarding the prefix LSAs
C1841#sh ipv6 ospf database prefix self-originate

            OSPFv3 Router with ID (193.137.220.250) (Process ID 1)

        Intra Area Prefix Link States (Area 0)

  Routing Bit Set on this LSA
  LS age: 7
  LS Type: Intra-Area-Prefix-LSA
  Link State ID: 0
  Advertising Router: 193.137.220.250
  LS Seq Number: 80003C5D
  Checksum: 0x58C1
  Length: 64
  Referenced LSA Type: 2001
  Referenced Link State ID: 0
  Referenced Advertising Router: 193.137.220.250
  Number of Prefixes: 2
  Prefix Address: 2001:690:2008::1003
  Prefix Length: 128, Options: LA , Metric: 0
  Prefix Address: 2001:690:2009:EFE0::
  Prefix Length: 64, Options: None, Metric: 400
In the new Quagga (named scratchy):
scratchy# sh version
Quagga 0.99.24.1 ().
Copyright 1996-2005 Kunihiro Ishiguro, et al.
configured with:
    --prefix=/usr --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --disable-dependency-tracking --disable-silent-rules --libdir=/usr/lib64 --docdir=/usr/share/doc/quagga-0.99.24.1 --enable-user=quagga --enable-group=quagga --enable-vty-group=quagga --with-cflags=-O2 -pipe -march=native -mtune=native -fno-strict-aliasing --sysconfdir=/etc/quagga --enable-exampledir=/usr/share/doc/quagga-0.99.24.1/samples --localstatedir=/run/quagga --disable-static --disable-pie --disable-capabilities --disable-pcreposix --disable-tcp-zebra --disable-doc --disable-ripngd --enable-multipath=0 --enable-vtysh --without-libpam --enable-ipv6 --enable-babeld --enable-ospf6d --enable-rtadv

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

scratchy# sh ipv6 ospf6 database adv-router 193.137.220.250

        Area Scoped Link State Database (Area 0.0.0.0)

Type LSId           AdvRouter       Age   SeqNum                        Payload
Rtr  0.0.0.0        193.137.220.250  32 80003d02       193.137.220.222/0.0.0.30
INP  0.0.0.0        193.137.220.250  39 80003c5d        2001:690:2008::1003/128
INP  0.0.0.0        193.137.220.250  39 80003c5d        2001:690:2009:efe0::/64
INP  0.0.0.0        193.137.220.250  39 80003c5d        2001:690:2009:efe0::/64

        I/F Scoped Link State Database (I/F bond0 in Area 0.0.0.0)

Type LSId           AdvRouter       Age   SeqNum                        Payload

        I/F Scoped Link State Database (I/F outs1dmz in Area 0.0.0.0)

Type LSId           AdvRouter       Age   SeqNum                        Payload
Lnk  0.0.0.12       193.137.220.2501039 80003c43       fe80::211:21ff:fe85:d2e2

        I/F Scoped Link State Database (I/F dummy0 in Area 0.0.0.0)

Type LSId           AdvRouter       Age   SeqNum                        Payload

        I/F Scoped Link State Database (I/F dummy1 in Area 0.0.0.0)

Type LSId           AdvRouter       Age   SeqNum                        Payload

        AS Scoped Link State Database

Type LSId           AdvRouter       Age   SeqNum                        Payload

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

scratchy# sh ipv6 ospf6 database intra-prefix adv-router 193.137.220.250

        Area Scoped Link State Database (Area 0.0.0.0)

Type LSId           AdvRouter       Age   SeqNum                        Payload
INP  0.0.0.0        193.137.220.250  63 80003c5d        2001:690:2008::1003/128
INP  0.0.0.0        193.137.220.250  63 80003c5d        2001:690:2009:efe0::/64
INP  0.0.0.0        193.137.220.250  63 80003c5d        2001:690:2009:efe0::/64

Are this 3 LSAs Ok? the 2nd and the 3rd seem duplicates, the older Quagga only has 1 (see below)
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

scratchy# sh ipv6 ospf6 database intra-prefix adv-router 193.137.220.250 detail

        Area Scoped Link State Database (Area 0.0.0.0)

Age:   78 Type: Intra-Prefix
Link State ID: 0.0.0.0
Advertising Router: 193.137.220.250
LS Sequence Number: 0x80003c5d
CheckSum: 0x58c1 Length: 64
Duration: 00:01:16
     Number of Prefix: 2
     Reference: Router Id: 0.0.0.0 Adv: 193.137.220.250
     Prefix Options: --|--|LA|--
     Prefix: 2001:690:2008::1003/128
     Prefix Options: --|--|--|--
     Prefix: 2001:690:2009:efe0::/64

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
The route isn't in the table, only the static blackhole route to our entire IPv6 block
scratchy# sh ipv6 route 2001:690:2008::1003
Routing entry for 2001:690:2008::/47
  Known via "static", distance 250, metric 0, reject
    directly connected, null0 inactive


In the older Quagga (named itchy)
itchy# sh version  
Quagga 0.99.22.4 ().
Copyright 1996-2005 Kunihiro Ishiguro, et al.

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

itchy# sh ipv6 ospf6 database adv-router 193.137.220.250

        Area Scoped Link State Database (Area 0.0.0.0)

Type         LSId            AdvRouter        Age   SeqNum Cksm  Len Duration
Router       0.0.0.0         193.137.220.250  101 80003d02 36a5   40 00:01:40
Intra-Prefix 0.0.0.0         193.137.220.250  109 80003c5d 58c1   64 00:01:47

        I/F Scoped Link State Database (I/F bond0 in Area 0.0.0.0)

Type         LSId            AdvRouter        Age   SeqNum Cksm  Len Duration

        I/F Scoped Link State Database (I/F outs1 in Area 0.0.0.0)

Type         LSId            AdvRouter        Age   SeqNum Cksm  Len Duration
Link         0.0.0.12        193.137.220.250 1109 80003c43 6515   44 00:18:27

        I/F Scoped Link State Database (I/F dummy0 in Area 0.0.0.0)

Type         LSId            AdvRouter        Age   SeqNum Cksm  Len Duration

        I/F Scoped Link State Database (I/F dummy1 in Area 0.0.0.0)

Type         LSId            AdvRouter        Age   SeqNum Cksm  Len Duration

        AS Scoped Link State Database

Type         LSId            AdvRouter        Age   SeqNum Cksm  Len Duration

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

itchy# sh ipv6 ospf6 database intra-prefix adv-router 193.137.220.250

        Area Scoped Link State Database (Area 0.0.0.0)

Type         LSId            AdvRouter        Age   SeqNum Cksm  Len Duration
Intra-Prefix 0.0.0.0         193.137.220.250  132 80003c5d 58c1   64 00:02:10

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

itchy# sh ipv6 ospf6 database intra-prefix adv-router 193.137.220.250 detail  

        Area Scoped Link State Database (Area 0.0.0.0)

Age:  150 Type: Intra-Prefix
Link State ID: 0.0.0.0
Advertising Router: 193.137.220.250
LS Sequence Number: 0x80003c5d
CheckSum: 0x58c1 Length: 64
     Number of Prefix: 2
     Reference: Router Id: 0.0.0.0 Adv: 193.137.220.250
     Prefix Options: --|--|LA|--
     Prefix: 2001:690:2008::1003/128
     Prefix Options: --|--|--|--
     Prefix: 2001:690:2009:efe0::/64

The route is in the route table of this equipment !!!

itchy# sh ipv6 route 2001:690:2008::1003
Routing entry for 2001:690:2008::1003/128
  Known via "ospf6", distance 110, metric 230, best
  Last update 00:03:40 ago
  * fe80::461e:a1ff:fe53:1250, via bond0

Ok, now I've changed the prefix in the address and repeated some commands.

interface Loopback6
 no ip address
 ipv6 address 2001:690:2008::1003/127
 ipv6 ospf network point-to-point
 ipv6 ospf 1 area 0
end

C1841#sh ipv6 ospf database prefix self-originate

            OSPFv3 Router with ID (193.137.220.250) (Process ID 1)

        Intra Area Prefix Link States (Area 0)

  Routing Bit Set on this LSA
  LS age: 500
  LS Type: Intra-Area-Prefix-LSA
  Link State ID: 0
  Advertising Router: 193.137.220.250
  LS Seq Number: 80003C5C
  Checksum: 0x1B03
  Length: 64
  Referenced LSA Type: 2001
  Referenced Link State ID: 0
  Referenced Advertising Router: 193.137.220.250
  Number of Prefixes: 2
  Prefix Address: 2001:690:2008::1002
  Prefix Length: 127, Options: None, Metric: 1
  Prefix Address: 2001:690:2009:EFE0::
  Prefix Length: 64, Options: None, Metric: 400

In the newer Quagga the LSAs seem similar, with the prefix changed
scratchy# sh ipv6 ospf6 database adv-router 193.137.220.250

        Area Scoped Link State Database (Area 0.0.0.0)

Type LSId           AdvRouter       Age   SeqNum                        Payload
Rtr  0.0.0.0        193.137.220.250 421 80003d00       193.137.220.222/0.0.0.30
INP  0.0.0.0        193.137.220.250 421 80003c5c        2001:690:2008::1002/127
INP  0.0.0.0        193.137.220.250 421 80003c5c        2001:690:2009:efe0::/64
INP  0.0.0.0        193.137.220.250 421 80003c5c        2001:690:2009:efe0::/64

        I/F Scoped Link State Database (I/F bond0 in Area 0.0.0.0)

Type LSId           AdvRouter       Age   SeqNum                        Payload

        I/F Scoped Link State Database (I/F outs1dmz in Area 0.0.0.0)

Type LSId           AdvRouter       Age   SeqNum                        Payload
Lnk  0.0.0.12       193.137.220.250 788 80003c43       fe80::211:21ff:fe85:d2e2

        I/F Scoped Link State Database (I/F dummy0 in Area 0.0.0.0)

Type LSId           AdvRouter       Age   SeqNum                        Payload

        I/F Scoped Link State Database (I/F dummy1 in Area 0.0.0.0)

Type LSId           AdvRouter       Age   SeqNum                        Payload

        AS Scoped Link State Database

Type LSId           AdvRouter       Age   SeqNum                        Payload

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

scratchy# sh ipv6 ospf6 database intra-prefix adv-router 193.137.220.250        

        Area Scoped Link State Database (Area 0.0.0.0)

Type LSId           AdvRouter       Age   SeqNum                        Payload
INP  0.0.0.0        193.137.220.250 446 80003c5c        2001:690:2008::1002/127
INP  0.0.0.0        193.137.220.250 446 80003c5c        2001:690:2009:efe0::/64
INP  0.0.0.0        193.137.220.250 446 80003c5c        2001:690:2009:efe0::/64

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

scratchy# sh ipv6 ospf6 database intra-prefix adv-router 193.137.220.250 detail

        Area Scoped Link State Database (Area 0.0.0.0)

Age:  463 Type: Intra-Prefix
Link State ID: 0.0.0.0
Advertising Router: 193.137.220.250
LS Sequence Number: 0x80003c5c
CheckSum: 0x1b03 Length: 64
Duration: 00:07:41
     Number of Prefix: 2
     Reference: Router Id: 0.0.0.0 Adv: 193.137.220.250
     Prefix Options: --|--|--|--
     Prefix: 2001:690:2008::1002/127
     Prefix Options: --|--|--|--
     Prefix: 2001:690:2009:efe0::/64
Now, the route is in the table
scratchy# sh ipv6 route 2001:690:2008::1003
Routing entry for 2001:690:2008::1002/127
  Known via "ospf6", distance 110, metric 201, best
  Last update 00:02:55 ago
  * fe80::211:21ff:fe85:d2e2, via outs1dmz

I'm I doing some mistake? It's the expected behaviour or a bug?
I hope this could help the developers.

regards. thanks for the excellent work in this project!
-- Best regards, =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Pedro Ribeiro IPLNet, Redes de dados e comunicações Departamento de Sistemas de Informação e Comunicações Instituto Politécnico de Lisboa Telefone: +351 210 464 701 VoIP: sip:80101-eNdSyHewRMXQUPosyRRdSA@public.gmane.org =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
_______________________________________________
Quagga-users mailing list
Quagga-users@...
https://lists.quagga.net/mailman/listinfo/quagga-users

Gmane