Example: Configuring the Chassis Cluster Fabric (CLI)

The fabric is the back-to-back data connection between the nodes in a cluster. Traffic on one node that needs to be processed on the other node or to exit through an interface on the other node passes over the fabric. Session state information also passes over the fabric.

Before You Begin
Read: Understanding Chassis Cluster Formation Example: Setting the Chassis Cluster Node ID and Cluster ID (CLI) Understanding the Chassis Cluster Control Plane

Before You Begin

Read:

In most SRX Series devices in a chassis cluster, you can configure any pair of Gigabit Ethernet interfaces or any pair of 10-Gigabit interfaces to serve as the fabric between nodes. Interfaces on SRX210 devices are Fast Ethernet or Gigabit Ethernet (the paired interfaces must be of a similar type) and all interfaces on SRX100 devices are Fast Ethernet interfaces.

In a J Series chassis cluster, you can configure any pair of Gigabit Ethernet interfaces to serve as the fabric between nodes.

You cannot configure filters, policies, or services on the fabric interface. Fragmentation is not supported on the fabric link. The maximum transmission unit (MTU) size is 8,980 bytes. We recommend that no interface in the cluster exceed this MTU. Jumbo frame support on the member links is enabled by default.

Enter the following commands to join ge-0/0/1 on one node in the cluster and ge-7/0/1 on the other to form the fabric:

{primary:node0}user@host# set interfaces fab0 fabric-options member-interfaces ge-0/0/1{secondary:node1}user@host# set interfaces fab1 fabric-options member-interfaces ge-7/0/1

For dual fabric links, enter the following commands to join ge-3/0/0 on one node in the cluster and ge-10/0/0 on the other to form one fabric and to join ge-0/0/0 and ge-7/0/0 to form the second fabric in the cluster:

{primary:node0}user@host# set interfaces fab0 fabric-options member-interfaces ge-3/0/0user@host# set interfaces fab0 fabric-options member-interfaces ge-0/0/0{secondary:node1}user@host# set interfaces fab1 fabric-options member-interfaces ge-10/0/0user@host# set interfaces fab1 fabric-options member-interfaces ge-7/0/0

This example is a typical configuration where the dual fabric links are formed with matching slots/ports on each node. That is, ge-3/0/0 on node0 and ge-10/0/0 on node1 match, as do ge-0/0/0 on node0 and ge-7/0/0 on node1 (the FPC slot offset is 7).

If you choose to configure a different slot/port for the other node, as shown in the following example, make sure you physically connect the RTO-and-probes link to the RTO-and-probes link on the other node. Likewise, make sure you physically connect the data link to the data link on the other node.

{primary:node0}user@host# set interfaces fab0 fabric-options member-interfaces ge-2/1/9user@host# set interfaces fab0 fabric-options member-interfaces ge-2/2/5{secondary:node1}user@host# set interfaces fab1 fabric-options member-interfaces ge-11/0/0user@host# set interfaces fab1 fabric-options member-interfaces ge-11/3/0

That is, physically connect the following two pairs:

The node0 RTO-and-probes link ge-2/1/9 to the node1 RTO-and-probes link ge-11/0/0
The node0 data link ge-2/2/5 to the node1 data link ge-11/3/0

Only the same type of interfaces can be configured as fabric children, and you must configure an equal number of child links for fab0 and fab1.

Note: If you are connecting each of the fabric links through a switch, you must enable the jumbo frame feature on the corresponding switch ports. If both of the fabric links are connected through the same switch, the RTO-and-probes pair must be in one virtual LAN (VLAN) and the data pair must be in another VLAN. Here too, the jumbo frame feature must be enabled on the corresponding switch ports.

Example: Configuring the Chassis Cluster Fabric (CLI)

Related Topics