[j-nsp] JunOS 6.3 not logging BGP state transitions

[Jared Gillis]

Erdem Sener wrote:
> Hi Jared,
> 
> A couple more questions than, risking that I might be re-stating the
> obvious:

No problem, I appreciate the input.

> 
> - do you have that information on what's "sent" to your syslog server?

How do you mean? I have confirmed that our syslog server is receiving syslog
messages from our Juniper routers with the configuration I provided. The core of
the issue is that BGP states change on the Junipers, SNMP traps are sent, but no
syslog is generated, locally or to the server.

> - is your bgp configured on the main instance, or on a logical router?

Main instance, none of the Junipers involved make use of logical routers.

> - what does your 'show system storage' look like?

Filesystem        512-blocks       Used      Avail Capacity Mounted on
/dev/ad0s1a           158174      68472      77050     47%  /
devfs                     32         32          0    100%  /dev/
/dev/vn0               22816      22816          0    100%  /packages/mnt/jbase
/dev/vn1               77956      77956          0    100%
/packages/mnt/jkernel-6.3R1.3
/dev/vn2               22852      22852          0    100%
/packages/mnt/jpfe-M40-6.3R1.3
/dev/vn3                4492       4492          0    100%
/packages/mnt/jdocs-6.3R1.3
/dev/vn4               27556      27556          0    100%
/packages/mnt/jroute-6.3R1.3
/dev/vn5                9620       9620          0    100%
/packages/mnt/jcrypto-6.3R1.3
mfs:152              3048670        210    2804568      0%  /tmp
/dev/ad0s1e            23742        146      21698      1%  /config
procfs                     8          8          0    100%  /proc
/dev/ad1s1f        110372936     471320  101071782      0%  /var

Plenty of space in /var =)

> - does that happen on all your routers with same release, or just one?

This happens on all our Junipers, all with the same BGP base config, running a
mix of 6.3R1.3, 6.3R2.2, and 7.5R3.1. Regardless of the platform or code rev, I
see the lack of syslog for BGP neighbor state transitions.

> 
> Cheers,
> Erdem
> 
> 
> On 6/13/07, Jared Gillis <jared at sonic.net> wrote:
>> I agree, the config looks proper, but I don't get the expected log
>> messages
>> anywhere. I've caused BGP hits on the router with this config and
>> never see any
>> log messages in any of the message files or on our syslog server.
>>
>> % zcat /var/log/messages*.gz | grep -i bgp
>> %
>> % grep -i bgp /var/log/daemon
>> Sep  9 10:34:36  host.name mgd[4421]: UI_COMMIT_EMPTY_CONTAINER:
>> Skipped empty
>> object 'bgp'
>> %
>>
>> Erdem Sener wrote:
>> > Hi Jared,
>> >
>> > You should see you neighbor going down in your 'messages' file at
>> > least based on the configuration you've sent.
>> >
>> > Are you trying to have this information somewhere else?
>> >
>> > Thanks,
>> > Erdem
>> >
>> > On 6/13/07, Jared Gillis <jared at sonic.net> wrote:
>> >> Hi,
>> >>
>> >> I manage a number of M40 routers running JunOS 6.3. I have the
>> log-updown
>> >> directive enabled in the protocol bgp hierarchy (via an apply-group),
>> >> but I get
>> >> no syslog messages anywhere when a BGP session goes down or comes
>> up. I'm
>> >> logging all daemon messages level info or higher to a syslog host and
>> >> locally.
>> >> I've tried manually configuring log-updown at each level of the bgp
>> >> configuration (globally, under a group, or under individual
>> >> neighbors), I can't
>> >> get any BGP syslog messages at all.
>> >> Is there a known issue with this on this code rev? Is there other
>> >> configuration
>> >> necessary?
>> >>
>> >> Here's sanitized config snips:
>> >>
>> >> syslog {
>> >>     archive size 1m files 20;
>> >>     user * {
>> >>         any emergency;
>> >>     }
>> >>     host 1.2.3.4 {
>> >>         any notice;
>> >>         kernel any;
>> >>         authorization info;
>> >>         daemon info;
>> >>         cron any;
>> >>         facility-override local4;
>> >>     }
>> >>     file messages {
>> >>         any notice;
>> >>         authorization info;
>> >>     }
>> >>     file command-history {
>> >>         change-log any;
>> >>         interactive-commands any;
>> >>     }
>> >>     file syslog {
>> >>         any warning;
>> >>     }
>> >>     file firewall {
>> >>         firewall any;
>> >>     }
>> >>     file daemon {
>> >>         daemon info;
>> >>     }
>> >>     file kernel {
>> >>         kernel any;
>> >>     }
>> >>     file pfe {
>> >>         pfe any;
>> >>     }
>> >>     file user {
>> >>         user any;
>> >>     }
>> >>     file conflicts {
>> >>         conflict-log any;
>> >>     }
>> >> }
>> >>
>> >> bgp {
>> >>     path-selection always-compare-med;
>> >>     advertise-inactive;
>> >>     log-updown;
>> >>     group ibgp {
>> >> <snip>
>> >>     }
>> >> }
>> >>
>> >> --
>> >> Jared Gillis - jared at corp.sonic.net       Sonic.net, Inc.
>> >> Network Operations                        2260 Apollo Way
>> >> 707.522.1000 (Voice)                      Santa Rosa, CA 95407
>> >> 707.547.3400 (Support)                    http://www.sonic.net/
>> >> _______________________________________________
>> >> juniper-nsp mailing list juniper-nsp at puck.nether.net
>> >> https://puck.nether.net/mailman/listinfo/juniper-nsp
>> >>
>> >
>> >
>>
>>
>> -- 
>> Jared Gillis - jared at corp.sonic.net       Sonic.net, Inc.
>> Network Operations                        2260 Apollo Way
>> 707.522.1000 (Voice)                      Santa Rosa, CA 95407
>> 707.547.3400 (Support)                    http://www.sonic.net/
>> _______________________________________________
>> juniper-nsp mailing list juniper-nsp at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/juniper-nsp
>>
> 
> 


-- 
Jared Gillis - jared at corp.sonic.net       Sonic.net, Inc.
Network Operations                        2260 Apollo Way
707.522.1000 (Voice)                      Santa Rosa, CA 95407
707.547.3400 (Support)                    http://www.sonic.net/