Re: [j-nsp] meaning/cause of syslog messages

default syslog looks like: Month Day time hostname daemon/device[id]: SYSLOG_CATEGORY: Syslog message but in this case it is /kernel reporting - not sure if it's documented elsewhere (or not publicly at all). Ok so look like jtac time thanks Dave > > On Wed, Aug 19, 2009 at 8:32 AM, Dave Kru

[j-nsp] meaning/cause of syslog messages

Hi List I just want to find out what you use to determine the cause of obscure syslog messages. Is there a juniper equivalent to cisco's error message decoder somewhere on juniper.net that I cant find? For instance - we have a M120 that barfs about: /kernel: if_pfe_peek_peer_info: PFE_MSG_PEER

Re: [j-nsp] per-packet load balancing over multiple l2tp tunnels

ols which has a similar answer: - OSPF cannot be run on dynamic IP interfaces. (because of KA26012 Juniper removed this feature) I think these two problem is unacceptable and I cannot find any meaningful reason for this kind of lack. On Tue, Aug 26, 2008 at 11:59 AM, Dave Kruger &l

[j-nsp] per-packet load balancing over multiple l2tp tunnels

Hi All Has anyone ever tried to do change the load balancing technique over l2tp tunnels on an ERX? the default is obviously per-flow: sh ip interface tun l2tp:139254/1105340/1016347 | i Multipath Multipath mode = hashed It seems enabling per-packet on the physical interface over which the l2