Re: [j-nsp] Basic Implementation of VLAN/LogicalPort across MPLS

[Eric Van Tol]

 interfaces {
 ae0 {
 aggregated-ether-options {
 lacp {
 active;
 }
 vlan-tagging;
 encapsulation flexible-ethernet-services;
 unit 10 {
 encapsulation vlan-ccc;
 vlan-id 10;
 }
 unit 20 {
 encapsulation vlan-ccc;
 vlan-id 20;
 }
 }

Additionally, if you need to transport a single VLAN on one side to a full port 
on the other, you need to pop the VLAN on ingress (and push on egress) into 
(and out of) the tunnel:

unit 10004 {
description To Port-Based EoMPLS;
encapsulation vlan-ccc;
vlan-id 2123;
input-vlan-map pop;
output-vlan-map push;
family ccc;
}
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

[j-nsp] RE switch master to backup

[james list]

Gents,

has anybody seen a dual RE MX gear switch the routing engine master to
backup due to a “possibly bad console cable” ?





Jul  1 11:21:29.786 2015  MX480LON_0 /kernel: sio0: 1 more excessive
framing errors (total 1)

Jul  1 11:21:29.941 2015  MX480LON_0 init: getty repeating too quickly on
port /dev/ttyd0, sleeping 30 secs

Jul  1 11:21:31.136 2015  MX480LON_0 /kernel: sio0: 1 more excessive
framing errors (total 2)

Jul  1 11:21:32.473 2015  MX480LON_0 chassisd[1694]:
CHASSISD_RE_CONSOLE_FE_STORM: Console device encountering framing error
storm on Routing Engine 0 (possibly a bad console cable)

Jul  1 11:21:32.485 2015  MX480LON_0 alarmd[2729]: Alarm set: RE
color=YELLOW, class=CHASSIS, reason=Excessive framing errors on console port





Code is 13.3R6



I’m not able to find any PR or KB.



Thanks for any input.



Cheers

James
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] Basic Implementation of VLAN/LogicalPort across MPLS

[Levi Pederson]

All,

Thank you all for your help!  It's putting me on the right track!

One thing to note since I'm using EX4550's I do not have Flexible Ethernet
Services  Only vlan-ccc and ethernet-ccc

Thank you all for your help!

*Levi Pederson*
Mankato Networks LLC
cell | 612.481.0769
work | 612.787.7392
levipeder...@mankatonetworks.net


On Wed, Jul 8, 2015 at 4:34 AM, Eric Van Tol e...@atlantech.net wrote:

  interfaces {
  ae0 {
  aggregated-ether-options {
  lacp {
  active;
  }
  vlan-tagging;
  encapsulation flexible-ethernet-services;
  unit 10 {
  encapsulation vlan-ccc;
  vlan-id 10;
  }
  unit 20 {
  encapsulation vlan-ccc;
  vlan-id 20;
  }
  }

 Additionally, if you need to transport a single VLAN on one side to a full
 port on the other, you need to pop the VLAN on ingress (and push on egress)
 into (and out of) the tunnel:

 unit 10004 {
 description To Port-Based EoMPLS;
 encapsulation vlan-ccc;
 vlan-id 2123;
 input-vlan-map pop;
 output-vlan-map push;
 family ccc;
 }
 ___
 juniper-nsp mailing list juniper-nsp@puck.nether.net
 https://puck.nether.net/mailman/listinfo/juniper-nsp

___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

[j-nsp] UDLD on Juniper ?

[james list]

Gents,

A customer of mine asked for migrating a port-channel from a C6500 towards
another C6500 with UDLD to an MX towards a C6500, customer would like to
keep UDLD to prevent faults.


I know UDLD is something proprietary by Cisco… I’d like to know your option
or experience to have somethng similar among C6500 and Juniper MX…



Thanks in advance


Cheers

James
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] UDLD on Juniper ?

[Saku Ytti]

On (2015-07-08 18:23 +0200), james list wrote:

Hey,

 A customer of mine asked for migrating a port-channel from a C6500 towards
 another C6500 with UDLD to an MX towards a C6500, customer would like to
 keep UDLD to prevent faults.

Prevent what type of faults? UDLD is done in all platforms that I know off
from the control-plane, this introduces some new failure modes.

Typically what is attempted to fix is having unidirectional link, which can
cause very serious problem in L2 networks running STP.
However, point-to-point ethernet link should guarantee bidirectionally unless
specifically broken by turning off autonego or such. If ethernet links detects
loss of link, it'll assert RFI, and far end can use this to go down as well.

Same RFI is used optionally in Juniper to force CPEs WAN port down when
l2circuit in PE goes down (without putting local interface down).

-- 
  ++ytti
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp