Configure Reth With Family Ethernet Switching on Srx
Understanding Layer 2 Ethernet Switching Capability in Chassis Cluster on SRX-Branch
Ethernet ports support various Layer 2 features such equally Spanning Tree Protocols (xSTP), DOT1X, Link Assemblage (LAG), Internet Group Membership Protocol (IGMP), GARP, VLAN Registration Protocol (GVRP), Link Layer Discovery Protocol (LLDP), and snooping. The enhanced characteristic extends Layer 2 switching adequacy to devices in a chassis cluster.
This feature allows users to utilize Ethernet switching features on both nodes of a chassis cluster. The Ethernet ports on either of the nodes can be configured for family unit Ethernet switching. Users tin can configure a Layer ii VLAN domain with member ports from both of the nodes and the Layer 2 switching protocols on both of the devices. To ensure that Layer 2 switching works seamlessly across chassis cluster nodes, a dedicated concrete link connecting the nodes is required. This type of link is chosen a switching textile interface (swfab). Its function is to transmit Layer two traffic between the nodes.
Note:
-
Configuring a LAG with family ethernet switching is not supported.
-
Configuring a Reth with family unit ethernet switching is non supported. This is only supported in Transparent mode.
-
Behavior of the nodes may be unpredictable, if the Ethernet switching-related features are configured before configuring the swfab interface on both the nodes.
When chassis cluster failover occurs, a new main node is elected and the Ethernet Switching Daemon (ESWD) runs in a different node. During failover, chassis control subsystem is restarted, and the traffic outage occurs until the PICs are up and the VLAN entries are re-programmed. Afterward fail over, all Layer ii protocols re-converge, because Layer 2 protocols states are not maintained in the secondary node.
Note: The Ethernet-switching subsystem runs only in the primary node.
The concrete link used every bit the switch fabric members must be direct connected. Switching supported ports must be used for swfab interfaces. For SRX650, the swfab member ports must belong to the aforementioned GPIM. Members spanning across multiple GPIMs are non supported. New pseudo interfaces - swfab0 and swfab1 are created for Layer ii fabric functionality. Users need to configure dedicated Ethernet ports on each side of the node to exist associated with the swfab interface.
To configure swfab interfaces:
-
Configure swfab0 and swfab1 to associate switch fabric interfaces to enable switching across the nodes.
Annotation: swfab0 corresponds to node 0 and swfab1 corresponds to node 1.
Sample configuration on SRX650
ge-0/0/0, ge-9/0/0 are fxp0 (out-of-band management) ge-0/0/1,ge-9/0/one are fxp1 (command link) ge-0/0/2, ge-ix/0/2 are fab links and ge-2/0/5 and ge-xi/0/5 are swfab members. ge-two/0/0,ge-xi/0/0 are role of VLAN A and ge-2/0/1,ge-11/0/1 are office of VLAN B
CLI Configuration
interfaces { ge-2/0/0 { unit of measurement 0 { family ethernet-switching { vlan { members A; } } } } ge-two/0/one { unit 0 { family ethernet-switching { vlan { members B; } } } } ge-11/0/0 { unit of measurement 0 { family ethernet-switching { vlan { members A; } } } } ge-11/0/1 { unit of measurement 0 { family unit ethernet-switching { vlan { members B; } } } } fab0 { fabric-options { fellow member-interfaces { ge-0/0/2; } } } fab1 { cloth-options { fellow member-interfaces { ge-9/0/ii; } } } swfab0 { fabric-options { fellow member-interfaces { ge-two/0/5; } } } swfab1 { fabric-options { member-interfaces { ge-eleven/0/five; } } } } vlans { A { vlan-id 100; } B { vlan-id 200; } } Verification
-
Use
show chassis cluster ethernet-switching interfacescommand to view the advisable member interfaces.
{primary:node1}[edit] root@SRX-650# run show chassis cluster ethernet-switching interfaces swfab0: Name Status ge-2/0/five up swfab1: Name Status ge-xi/0/v up -
Employ
show chassis cluster ethernet-switching statusto brandish chassis cluster Ethernet switching status (probe status and switching domain).
{master:node1}[edit] root@SRX-650# run show chassis cluster ethernet-switching status Cluster ID: i Node Priority Status Preempt Manual failover Redundancy grouping: 0 , Failover count: 0 node0 100 chief no no node1 one secondary no no Redundancy group: 1 , Failover count: 0 node0 100 principal no no node1 ane secondary no no Ethernet switching status:
Probe country is Up. Both nodes are in single Ethernet switching domain(southward). If proper interface for swfab purpose (such equally on-board interfaces on SRX650), and Ethernet-switching is not used, the status is displayed as Probe state is Downward. Both nodes are in carve up Ethernet switching domain(s).
-
Use
show chassis cluster ethernet-switching statisticsto display chassis cluster switch fabric probe statistics.
{primary:node1}[edit] root@SRX-650# run show chassis cluster ethernet-switching statistics Switch fabric link statistics: Probe land : UP Probes sent: 1866 Probes received: 1871 Probe recv errors: 0 Probe send errors: 0 Technical Documentation
For additional information and examples, refer to the Technical Documentation, Ethernet Switching on Chassis Cluster
Annotation: Layer3 routing from L2 ethernet-switching network via L3-interface Vlan.X in chassis cluster deployment is supported as of Junos OS 12.1X44-D20, 12.1X45-D10 and higher versions.
sterngoomencirt1968.blogspot.com
Source: https://kb.juniper.net/InfoCenter/index?page=content&id=KB21422
Post a Comment for "Configure Reth With Family Ethernet Switching on Srx"