Thanks Justin, that did the trick.
Now we need to figure out how to raise the level so we can turn off
debug and make it something more reasonable like warn for the OSPF
info...
Thanks again.
-------
Try lowering your syslog level to debug; the messages from OSPF are
likely filtered.
Best,
Justin Fletcher
On Dec 21, 2007 6:56 AM, Adair, Nick <[EMAIL PROTECTED]> wrote:
> Hi All,
> This is my configuration for syslog logging, right now we have
> everything turned on and going to our syslog host. The problem is we
> are not seeing OSPF notifications, I'm not sure what we are missing.
We
> looked in the manuals (what a concept) and found the section "Sending
> OSPF messages to Syslog" and did what it indicated but it does not
seem
> to send OSPF info, we do see syslog messages when logrotated runs, ssh
> logins, etc. We want to know when a neighbor changes. Any help would
> be greatly appreciated.
>
> 1 protocols {
> 2 ospf4 {
> 3 router-id: 192.168.4.2
> 4 rfc1583-compatibility: false
> 5 ip-router-alert: false
> 6 traceoptions {
> 7 flag {
> 8 all {
> 9 disable: false
> 10 }
> 11 }
> 12 }
> 13 area 0.0.0.0 {
> 14 area-type: "normal"
> 15 interface eth0 {
> 16 link-type: "broadcast"
> 17 address 192.168.3.4 {
> 18 priority: 128
> 19 hello-interval: 10
> 20 router-dead-interval: 40
> 21 interface-cost: 1
> 22 retransmit-interval: 5
> 23 transit-delay: 1
> 24 passive: false
> 25 disable: false
> 26 }
> 27 }
> 28 interface eth1 {
> 29 link-type: "broadcast"
> 30 address 192.168.4.253 {
> 31 priority: 128
> 32 hello-interval: 10
> 33 router-dead-interval: 40
> 34 interface-cost: 1
> 35 retransmit-interval: 5
> 36 transit-delay: 1
> 37 passive: false
> 38 disable: false
> 39 }
> 40 }
> 41 }
> 42 }
> 43 snmp {
> 44 community pilot {
> 45 client 192.168.100.104
> 46 client 192.168.100.105
> 47 authorization: "rw"
> 48 }
> 49 contact: ""
> 50 description: ""
> 51 location: ""
> 52 }
> 53 }
> 54 policy {
> 55 }
> 56 interfaces {
> 57 restore: false
> 58 loopback lo {
> 59 description: ""
> 60 address 192.168.4.2 {
> 61 prefix-length: 32
> 62 disable: false
> 63 }
> 64 }
> 65 ethernet eth0 {
> 66 disable: false
> 67 discard: false
> 68 description: "Uplink to RTR Cloud"
> 69 hw-id: 00:50:56:85:72:6f
> 70 duplex: "auto"
> 71 speed: "auto"
> 72 address 192.168.3.4 {
> 73 prefix-length: 24
> 74 disable: false
> 75 }
> 76 }
> 77 ethernet eth1 {
> 78 disable: false
> 79 discard: false
> 80 description: "Connectivity to Access Switch"
> 81 hw-id: 00:50:56:85:1e:3c
> 82 duplex: "auto"
> 83 speed: "auto"
> 84 address 192.168.4.253 {
> 85 prefix-length: 24
> 86 disable: false
> 87 }
> 88 }
> 89 }
> ... <snip>
> 122 system {
> 123 host-name: "vy-rtr-access"
> 124 domain-name: "pilot-bmc.com"
> 125 domain-search {
> 126 domain "calbro.ase"
> 127 }
> 128 name-server 192.168.100.100
> 129 time-zone: "GMT"
> 130 ntp-server "69.59.150.135"
> 131 static-host-mapping {
> 132 host-name "vy-rtr-access" {
> 133 inet: 192.168.4.2
> 134 }
> 135 }
> ... <snip>
> 150 syslog {
> 151 host "192.168.3.110" {
> 152 facility "*" {
> 153 level: "info"
> 154 }
> 155 }
> 156 }
> ...
> 164 }
>
>
> Nick
>
> _______________________________________________
> Vyatta-users mailing list
> Vyatta-users@mailman.vyatta.com
> http://mailman.vyatta.com/mailman/listinfo/vyatta-users
>
_______________________________________________
Vyatta-users mailing list
Vyatta-users@mailman.vyatta.com
http://mailman.vyatta.com/mailman/listinfo/vyatta-users
