Node in Out-of-Band Cluster

The following procedure is to replace the control card on a GigaVUE‑HC3 node in an out-of-band cluster.

Use the show chassis command to record the GigaVUE‑HC3 chassis box ID and the show cluster config command to record the cluster ID, cluster name, cluster leader address vip, cluster leader preference, and cluster interface.

To replace a control card in a GigaVUE‑HC3 that is in an out-of-band cluster:

  1. On the cluster leader, backup the entire configuration on the cluster to a text file.

(config) # configuration text generate active running upload <ftp | tftp | scp | sftp>://<upload URL>/<profilename.txt>

  1. On the cluster leader, remove the configuration of the GigaVUE‑HC3 node from the cluster database. The commands may vary depending on your configuration.

(config) # no map all(config) # no gsop all(config) # no vport all(config) # no tunnel all(config) # no gsgroup all(config) # no stack alias <alias>

  1. On the GigaVUE‑HC3 node, issue the following commands:

(config) # no cluster enable(config) # write memory

  1. On the cluster leader node, remove the GigaVUE‑HC3 node information from the cluster database. Answer YES when prompted. This removes the GigaVUE‑HC3 from the cluster.

(config) # no chassis box-id <box ID>

WARNING !! All the cards, ports, and traffic configuration will be lost.

Enter 'YES' to confirm this operation: YES

  1. Replace the control card by following the procedure for Standalone Node up to and including Step 11. (Since the GigaVUE‑HC3 has been removed from the cluster, it is a standalone node.)
  2. When the GigaVUE‑HC3 is back up, reinstate the cluster configuration including the cluster ID, cluster name, cluster leader address vip, cluster leader preference, and cluster interface, as well as the chassis box ID.

(config) # cluster id <cluster ID>(config) # cluster name <cluster name>(config) # cluster leader address vip <cluster leader vip>(config) # cluster interface eth<x>(config) # cluster leader preference <preference number for leader, standby, or normal>

  1. On the cluster leader, configure chassis information on the GigaVUE‑HC3, including the chassis box ID, serial number, and new node type.

(config) # chassis box-id <box ID> serial-num <serial number> type hc3

  1. On the GigaVUE‑HC3 node, issue the following command for the node to rejoin the cluster:

(config) # cluster enable

  1. When the GigaVUE‑HC3 node is in the cluster, from the cluster leader apply the previously saved configuration:

(config) # configuration text fetch <http | https | ftp | tftp | scp | sftp>://<download URL>/<profilename.txt> apply fail-continue verbose

  1. Verify that the information on the cluster matches the previously saved configuration for chassis, cards, and traffic using the following CLI commands or others, depending on your configuration:

(config) # show version(config) # show cluster global(config) # show chassis(config) # show cards(config) # show map(config) # show map stats all