Switching between SFP and onboard interfaces on SRX 210
AS IT'S KNOWN SRX 210 DOESN'T SUPPORT ETHERNET SWITCHING BETWEEN OPTICAL [ 1-PORT SMALL FORM-FACTOR PLUGGABLE (SFP) MINI-PHYSICAL INTERFACE MODULE ] AND ONBOARD INTERFACES.
SURELY YOU CAN APPLY ROUTING METHODS, BUT I HAVE FOUND ONE PRACTICAL SOLUTION TO ARRANGE THIS. LET'S SEE HOW TO PERFORM THIS:
1) Activate packet mode on device:
forwarding-options {
family {
mpls {
mode packet-based;
}
2) Activate routing instances VPN, instance-type vpls to all interfaces including optical:
routing-instances {
VPN {
instance-type vpls;
interface ge-0/0/0.0;
interface ge-0/0/1.0;
interface fe-0/0/2.0;
interface fe-0/0/3.0;
interface fe-0/0/4.0;
interface fe-0/0/5.0;
interface fe-0/0/6.0;
interface fe-0/0/7.0;
interface ge-1/0/0.0;
}
}
3) On interface hierarchy add encapsulation ethernet-vpls:
ge-0/0/0 {
encapsulation ethernet-vpls;
unit 0 {
family vpls;
}
}
ge-0/0/1 {
encapsulation ethernet-vpls;
unit 0 {
family vpls;
}
}
fe-0/0/2 {
encapsulation ethernet-vpls;
unit 0 {
family vpls;
}
}
fe-0/0/3 {
encapsulation ethernet-vpls;
unit 0 {
family vpls;
}
}
fe-0/0/4 {
encapsulation ethernet-vpls;
unit 0 {
family vpls;
}
}
fe-0/0/5 {
encapsulation ethernet-vpls;
unit 0 {
family vpls;
}
}
fe-0/0/6 {
encapsulation ethernet-vpls;
unit 0 {
family vpls;
}
}
fe-0/0/7 {
encapsulation ethernet-vpls;
unit 0 {
family vpls;
}
}
ge-1/0/0 {
encapsulation ethernet-vpls;
unit 0 {
family vpls;
}
}
}
4) Actually that's all. But one thing remains. What about management interface. For that purpose I think we should use logical tunnel interface lt. So we must repeat steps 2 and 3 for lt interface and assign IP address to it:
routing-instances {
VPN {
instance-type vpls;
interface lt-0/0/0.1;
lt-0/0/0 {
unit 0 {
encapsulation ethernet;
peer-unit 1;
family inet {
address 172.16.254.21/16;
}
}
unit 1 {
encapsulation ethernet-vpls;
peer-unit 0;
}
}
That is the final point !!!
For more information please refer to "Branch SRX Series and J Series Selective Packet Services" - Configuring Selective Packet Services on Branch SRX Series Services Gateways and J Series Services Routers.
SURELY YOU CAN APPLY ROUTING METHODS, BUT I HAVE FOUND ONE PRACTICAL SOLUTION TO ARRANGE THIS. LET'S SEE HOW TO PERFORM THIS:
1) Activate packet mode on device:
forwarding-options {
family {
mpls {
mode packet-based;
}
2) Activate routing instances VPN, instance-type vpls to all interfaces including optical:
routing-instances {
VPN {
instance-type vpls;
interface ge-0/0/0.0;
interface ge-0/0/1.0;
interface fe-0/0/2.0;
interface fe-0/0/3.0;
interface fe-0/0/4.0;
interface fe-0/0/5.0;
interface fe-0/0/6.0;
interface fe-0/0/7.0;
interface ge-1/0/0.0;
}
}
3) On interface hierarchy add encapsulation ethernet-vpls:
ge-0/0/0 {
encapsulation ethernet-vpls;
unit 0 {
family vpls;
}
}
ge-0/0/1 {
encapsulation ethernet-vpls;
unit 0 {
family vpls;
}
}
fe-0/0/2 {
encapsulation ethernet-vpls;
unit 0 {
family vpls;
}
}
fe-0/0/3 {
encapsulation ethernet-vpls;
unit 0 {
family vpls;
}
}
fe-0/0/4 {
encapsulation ethernet-vpls;
unit 0 {
family vpls;
}
}
fe-0/0/5 {
encapsulation ethernet-vpls;
unit 0 {
family vpls;
}
}
fe-0/0/6 {
encapsulation ethernet-vpls;
unit 0 {
family vpls;
}
}
fe-0/0/7 {
encapsulation ethernet-vpls;
unit 0 {
family vpls;
}
}
ge-1/0/0 {
encapsulation ethernet-vpls;
unit 0 {
family vpls;
}
}
}
4) Actually that's all. But one thing remains. What about management interface. For that purpose I think we should use logical tunnel interface lt. So we must repeat steps 2 and 3 for lt interface and assign IP address to it:
routing-instances {
VPN {
instance-type vpls;
interface lt-0/0/0.1;
lt-0/0/0 {
unit 0 {
encapsulation ethernet;
peer-unit 1;
family inet {
address 172.16.254.21/16;
}
}
unit 1 {
encapsulation ethernet-vpls;
peer-unit 0;
}
}
That is the final point !!!
For more information please refer to "Branch SRX Series and J Series Selective Packet Services" - Configuring Selective Packet Services on Branch SRX Series Services Gateways and J Series Services Routers.
Comments