Configuring Node Groups for the QFabric System

There are three types of Node groups in a QFabric system:

• Automatically generated server Node groups—By default, every Node device that joins the QFabric system is placed within an automatically generated server Node group that contains one Node device (the device itself). Server Node groups connect to servers and storage devices.

• Network Node groups—You can assign up to eight Node devices to a network Node group. When grouped together, the Node devices within a network Node group connect to other routers running routing protocols such as OSPF and BGP.

• Redundant server Node groups—You can assign two Node devices to a redundant server Node group. When grouped together, you can create link aggregation groups (LAGs) that span the interfaces on both Node devices to provide resiliency and redundancy.

Before you create Node groups in a QFabric system:

• Make sure your QFabric system is operational.

• Issue the show fabric administration inventory node-devices command to display the Node devices that are available to add to a Node group.

• Issue the show fabric administration inventory node-groups command to display the existing Node groups.

  Note

  The following rules apply to QFabric Node group naming:

  • Node group names must use alphabetic (A through Z and a through z), numeric (0 through 9), or dash (-) characters.

  • The maximum length of a Node group name is 30 characters.

  • Node group names are case sensitive. For example, MY-NG-1 and my-ng-1 refer to different components.

  • You cannot use the reserved names all, fabric, or director-group as a Node group name.

  Note

  If you attempt to commit all configuration settings for a new Node group (such as the Node group itself, aliasing, and other features) at the same time, the commit operation might appear to succeed when it actually has failed. For this reason, we recommend configuring and verifying Node groups and aliases first, followed by configuring and verifying other features. Establishing the Node groups and aliases first enables the QFabric system to reject any potentially unsupported configuration. The resulting commit errors indicate where the configuration problem lies. To verify the establishment of Node groups and aliases before configuring other features, issue the show fabric administration inventory command.

• Issue the show fabric administration inventory node-groups command and look for Node groups containing a single Node device that has the same name or serial number as the server Node group.

  root@qfabric> show fabric administration inventory node-groups

1. Specify the Node devices you wish to add to the network Node group by including the node-device statement at the [edit fabric resources node-group NW-NG-0] hierarchy level.Note

   • The network Node group must use the predefined name NW-NG-0. You must use this name when adding Node devices to the network Node group. You cannot specify a different name. Also, you can configure only one network Node group per partition.

   • When you configure routing protocols on the QFabric system, you must use interfaces from the Node devices assigned to the network Node group. If you try to configure routing protocols on interfaces from the Node devices assigned to server Node groups, the configuration commit operation fails.

   root@qfabric# set fabric resources node-group NW-NG-0 node-device Node0

   root@qfabric# set fabric resources node-group NW-NG-0 node-device Node1
2. To designate the Node group as a network Node group, include the network-domain statement at the [edit fabric resources node-group NW-NG-0] hierarchy level.
   root@qfabric# set fabric resources node-group NW-NG-0 network-domain
3. Review your configuration and issue the commit command.
   root@qfabric# show fabric

   root@qfabric# commit
   Note

   When you add or delete Node devices from a Node group configuration, the corresponding Node devices reboot when you commit the configuration change.

4. To determine if your network Node group is operational, issue the show fabric administration inventory node-groups command in operational mode.
   root@qfabric>show fabric administration inventory node-groups NW-NG-0

1. Specify the two Node devices you wish to add to the redundant server Node group by including the node-device statement at the [edit fabric resources node-group node-group-name] hierarchy level.Note

   Ensure that the two Node devices are of the same type, either two QFX3500 Node devices, two QFX3600 Node devices, or two QFX5100 Node devices. You cannot add different Node device types to the same redundant server Node group.

   root@qfabric# set fabric resources node-group S1 node-device Node2

   root@qfabric# set fabric resources node-group S1 node-device Node3
2. Review your configuration and issue the commit command.
   root@qfabric# show fabric

   root@qfabric# commit
   Note

   When you add or delete Node devices from a Node group configuration, the corresponding Node devices reboot when you commit the configuration change.

3. To determine if your redundant server Node groups are operational, issue the show fabric administration inventory node-groups redundant-server-node-group-name command in operational mode.
   root@qfabric> show fabric administration inventory node-groups S1