Re: [j-nsp] Could you pls clarify a bit about OAM for link fault management?

2014-07-10 Thread Ben Dale
Hi Victor, Something like this should do the trick once you've configured it on both ends: set protocols oam ethernet link-fault-management action-profile UDLD event link-adjacency-loss set protocols oam ethernet link-fault-management action-profile UDLD action syslog set protocols oam ethernet

Re: [j-nsp] chassisd[1299]: %DAEMON-3: rtslib: ERROR Failed to allocate new block of size 16384

2014-07-10 Thread Morgan McLean
Other KB articles with similar failed to allocate block errors point to memory related issues and recommend restarting the routing engine. Any log messages that came up right before the failed to allocate message? Thanks, Morgan On Thu, Jul 10, 2014 at 1:53 PM, Alex D. wrote: > Hi, > since yes

[j-nsp] Could you pls clarify a bit about OAM for link fault management?

2014-07-10 Thread Victor Sudakov
Colleagues, I have pairs of EX4200 switches connected via third party MUXes. When the actual physical medium goes down, the MUXes do not shutdown their Ethernet interfaces. So I need some sort of point-to-point L2 link fault management between the EX4200s. I thought OAM could be used for this pur

[j-nsp] Configure SRX as bridge for DSL connection

2014-07-10 Thread Try Chhay
Hi All, Let say there are two SRX110 devices such as SRX110-A and SRX110-B as the below setup. SRX110-A will act as bridge and SRX110-B will configure PPPoE. Is there any way or idea to implement DSL bridge mode on SRX? SRX110-B (fe-0/0/0)………Ethernet ……..(fe-0/0/0) SRX110-A (at-1/0/0) ………..DSL li

[j-nsp] chassisd[1299]: %DAEMON-3: rtslib: ERROR Failed to allocate new block of size 16384

2014-07-10 Thread Alex D.
Hi, since yesterday, i see the following syslog messages from several M10i running JUNOS 10.4R8.5: chassisd[1299]: %DAEMON-3: rtslib: ERROR Failed to allocate new block of size 16384 This message occurs in irregular intervals and doesn't result in routing issues. Does anybody know what it mean

Re: [j-nsp] MX80 stops forwarding after enabling inline flow sampling

2014-07-10 Thread Justin M. Streiner
On Wed, 9 Jul 2014, Scott Granados wrote: I have an interesting problem. I have an MX80 where I wish to enable inline flow sampling. I used the kb entry as a template and configured. When setting the table size the PFE rebooted which is expected but when it came back online forwarding stop

[j-nsp] QinQ interface configuration question

2014-07-10 Thread R S
Hi I'm wondering if under a QinQ interface configuration it's accepted by the MX the same SVLAN (outer vlan) or the commit will fail. The PE QinQ interface prospect configuration scenarios are: 1) different SVLAN and CVLAN 2) different SVLAN and same CVLAN 3) same SVLAN and different CVLAN 4) sa

[j-nsp] MX80 stops forwarding after enabling inline flow sampling

2014-07-10 Thread Scott Granados
Hi, I have an interesting problem. I have an MX80 where I wish to enable inline flow sampling. I used the kb entry as a template and configured. When setting the table size the PFE rebooted which is expected but when it came back online forwarding stopped. I rebooted again and had th

[j-nsp] 2014-07 Security Bulletin: Junos: Denial of Service in TCP packet processing (CVE-2004-0230)

2014-07-10 Thread Richard A Steenbergen
Hey Juniper, If you're going to send out a security update on what is literally now a 10 year old issue (god I feel old), you should at least wait until Throwback Thursday. :) 2014-07 Security Bulletin: Junos: Denial of Service in TCP packet processing (CVE-2004-0230) Junos now implements the