Re: [j-nsp] Interface to be used for Trunking MPLS
Thanks for the suggestions. Was a great help!
Regards.
On Fri, May 18, 2012 at 11:14 AM, Caillin Bathern caill...@commtelns.comwrote:
Try using encapsulation flexible-ethernet-services on the CE facing
interface.
-Original Message-
From: juniper-nsp-boun...@puck.nether.net
[mailto:juniper-nsp-boun...@puck.nether.net] On Behalf Of Saba Sumsam
Sent: Friday, 18 May 2012 9:29 AM
To: juniper-nsp@puck.nether.net
Subject: [j-nsp] Interface to be used for Trunking MPLS
Hi,
I have an MX-80 acting as a PE router, where ge-1/1/1 is the CE-facing
interface which is connected to the trunk port of a switch. The
configuration looks like this:
[edit interfaces ge-1/1/1]
flexible-vlan-tagging;
encapsulation vlan-ccc;
unit 0 {
encapsulation vlan-ccc;
vlan-id-range 700-800;
family ccc;
}
[edit protocols]
connections remote-interface-switch VLAN700-800 interface ge-1/1/1.0
connections remote-interface-switch VLAN700-800 transmit-lsp LSP_MX
connections remote-interface-switch VLAN700-800 receive-lsp LSP_EX
VLAN range 700-800 is being transported across MPLS to the remote PE
device. The same interface, ge-1/1/1 is also receiving VLAN400 (through
the
trunk) but should not be sent via MPLS but to another switch connected
to the MX-80. I tried the following configuration on the same interface:
[edit interfaces ge-1/1/1]
unit 400 {
family bridge {
interface-mode trunk;
vlan-id-list 400;
'unit 400'
Link encapsulation type is not valid for device type
error: configuration check-out failed
Any suggestions how to make this work? The same physical interface
should be able to send specific VLANs out over MPLS and others out any
other interfaces.
Regards.
*Saba Sumsam*
*Network Engineer - Level 2*
eintellego Pty Ltd
s...@eintellego.net a...@eintellego.net ; www.eintellego.net
Phone: 1300 753 383 ; Fax: (+612) 8572 9954
Cell +61 (0)424753773
facebook.com/eintellego
PO Box 7726, Baulkham Hills, NSW 1755 Australia
The Experts Who The Experts Call
Juniper - Cisco - Brocade - IBM
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
--
Message protected by MailGuard: e-mail anti-virus, anti-spam and
content filtering.http://www.mailguard.com.au/mg
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
[j-nsp] Interface to be used for Trunking MPLS
Hi,
I have an MX-80 acting as a PE router, where ge-1/1/1 is the CE-facing
interface which is connected to the trunk port of a switch. The
configuration looks like this:
[edit interfaces ge-1/1/1]
flexible-vlan-tagging;
encapsulation vlan-ccc;
unit 0 {
encapsulation vlan-ccc;
vlan-id-range 700-800;
family ccc;
}
[edit protocols]
connections remote-interface-switch VLAN700-800 interface ge-1/1/1.0
connections remote-interface-switch VLAN700-800 transmit-lsp LSP_MX
connections remote-interface-switch VLAN700-800 receive-lsp LSP_EX
VLAN range 700-800 is being transported across MPLS to the remote PE
device. The same interface, ge-1/1/1 is also receiving VLAN400 (through the
trunk) but should not be sent via MPLS but to another switch connected to
the MX-80. I tried the following configuration on the same interface:
[edit interfaces ge-1/1/1]
unit 400 {
family bridge {
interface-mode trunk;
vlan-id-list 400;
'unit 400'
Link encapsulation type is not valid for device type
error: configuration check-out failed
Any suggestions how to make this work? The same physical interface should
be able to send specific VLANs out over MPLS and others out any other
interfaces.
Regards.
*Saba Sumsam*
*Network Engineer - Level 2*
eintellego Pty Ltd
s...@eintellego.net a...@eintellego.net ; www.eintellego.net
Phone: 1300 753 383 ; Fax: (+612) 8572 9954
Cell +61 (0)424753773
facebook.com/eintellego
PO Box 7726, Baulkham Hills, NSW 1755 Australia
The Experts Who The Experts Call
Juniper - Cisco – Brocade - IBM
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Interface to be used for Trunking MPLS
On 2012-05-18, at 9:29 AM, Saba Sumsam wrote:
flexible-vlan-tagging;
encapsulation vlan-ccc;
unit 0 {
encapsulation vlan-ccc;
vlan-id-range 700-800;
family ccc;
}
unit 400 {
family bridge {
interface-mode trunk;
vlan-id-list 400;
}
Cant do that. Youve told the MX that this port is for VLAN-CCC's only.
You want:
#
ge-1/1/1 {
flexible-vlan-tagging;
encapsulation flexible-ethernet-services; allows different per-unit
encapsulations
unit 0 {
encapsulation vlan-ccc;
vlan-id-range 700-800;
family ccc;
}
unit 400 {
family bridge {
interface-mode trunk;
vlan-id-list 400;
}
}
#
or: (if youre on Trio with an Older JunOS release):
ge-1/1/1 {
flexible-vlan-tagging;
encapsulation flexible-ethernet-services;
unit 0 {
encapsulation vlan-ccc;
vlan-id-range 700-800;
family ccc;
}
unit 400 {
encapsulation vlan-bridge
vlan-id 400;
}
}
bridge-domains v400 {
interface ge-1/1/1.400
}
#
- CK.
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Interface to be used for Trunking MPLS
Try using encapsulation flexible-ethernet-services on the CE facing
interface.
-Original Message-
From: juniper-nsp-boun...@puck.nether.net
[mailto:juniper-nsp-boun...@puck.nether.net] On Behalf Of Saba Sumsam
Sent: Friday, 18 May 2012 9:29 AM
To: juniper-nsp@puck.nether.net
Subject: [j-nsp] Interface to be used for Trunking MPLS
Hi,
I have an MX-80 acting as a PE router, where ge-1/1/1 is the CE-facing
interface which is connected to the trunk port of a switch. The
configuration looks like this:
[edit interfaces ge-1/1/1]
flexible-vlan-tagging;
encapsulation vlan-ccc;
unit 0 {
encapsulation vlan-ccc;
vlan-id-range 700-800;
family ccc;
}
[edit protocols]
connections remote-interface-switch VLAN700-800 interface ge-1/1/1.0
connections remote-interface-switch VLAN700-800 transmit-lsp LSP_MX
connections remote-interface-switch VLAN700-800 receive-lsp LSP_EX
VLAN range 700-800 is being transported across MPLS to the remote PE
device. The same interface, ge-1/1/1 is also receiving VLAN400 (through
the
trunk) but should not be sent via MPLS but to another switch connected
to the MX-80. I tried the following configuration on the same interface:
[edit interfaces ge-1/1/1]
unit 400 {
family bridge {
interface-mode trunk;
vlan-id-list 400;
'unit 400'
Link encapsulation type is not valid for device type
error: configuration check-out failed
Any suggestions how to make this work? The same physical interface
should be able to send specific VLANs out over MPLS and others out any
other interfaces.
Regards.
*Saba Sumsam*
*Network Engineer - Level 2*
eintellego Pty Ltd
s...@eintellego.net a...@eintellego.net ; www.eintellego.net
Phone: 1300 753 383 ; Fax: (+612) 8572 9954
Cell +61 (0)424753773
facebook.com/eintellego
PO Box 7726, Baulkham Hills, NSW 1755 Australia
The Experts Who The Experts Call
Juniper - Cisco - Brocade - IBM
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
--
Message protected by MailGuard: e-mail anti-virus, anti-spam and
content filtering.http://www.mailguard.com.au/mg
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
