How to Add a New Node to an IGX/BPX Network [Cisco IGX 8400 Series Switches]

Document ID: 46040

PDF Downloads

How to Add a New Node to an IGX/BPX Network

Introduction

This document describes how to add a new node to an existing IGX/BPX network.

Prerequisites

Requirements

Ensure that you meet these requirements before you attempt this configuration:

Basic IGX switch and BPX switch configuration skills

Components Used

The information in this document is based on these software and hardware versions:

Cisco IGX and BPX switches
All software releases available for the IGX/BPX switches

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

Conventions

Refer to the Cisco Technical Tips Conventions for more information on document conventions.

Add Your New Node

Step-by-Step Instructions

Complete these steps in order to add a new node in your network:

On the new the new node you want to add, use the clrallcnf command to clear any configuration that may be present due to previous usage of an older processor card and to ensure integrity on new processor cards.
Use the rnmnd command to pre-number the node you want to add.

If the selected node numbers are within the range and are unique, no renumbering of nodes occurs when networks are joined. This allows you to avoid massive message transmission in the network due to node renumbering when you add your new node.

You must select a number that is not already in use in the existing network. Use the command dspnds +non any existing node in the network to see the node numbers currently in use. It should not be the highest or lowest numbered node because these numbers have specific messaging implications on your network. The highest node number is the clocking source for all other nodes if all previously user configured clock sources become unusable. The lowest node number maintains the User ID and Time of Day information.

Note: If you do not renumber the nodes, automatic node numbering is used when you add your node to the network. The node number is changed at the node where the addtrk command is typed. Renumbering is based on a first fit algorithm.

These examples are based on automatic node numbering.

Example 1:

Network A has node numbers 1, 2, 3, 4, 5, 6, 7, and 8, and Network B has node numbers 1, 2, 5, and 6.

The addtrk command is issued from Network A. Network A renumbers its nodes to the next available unused number, as 3, 4, 7, 8, 9, 10, 11, and 12. This results in a new network—Network C—with node numbers 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, and 12.

Note: The User IDs in Network A are overwritten by the User IDs in Network B, because it maintains the lowest node number.

Note: The highest node numbers in Network A (node 8) and Network B (node 6) do not maintain default clocking control of the network. New node number 12 maintains clocking.

Example 2:

Network A has node numbers 1, 2, 3, 4, 9, 10, 11, and 12, and Network B had node numbers 5, 6, 7, and 8 before the network is joined together.

The addtrk command is issued from Network A. Network A does not renumber its nodes because there are no duplicate node numbers on both networks. This action results in a new network called Network C with node numbers of 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12.

Note: The User IDs and Time of Day information in Network A is maintained because this network contains the lowest node number. The User IDs and Time of Day in Network A overrides the information in Network B.

The highest node number in Network A (node 12) maintains the default clocking control of the network.
Complete these network parameter settings:
1. Use the cnfsysparm command to ensure that these parameters on the new node match the current parameters on the existing network nodes.
2. Use the cnfcmb command to ensure that the parameters on the new node match the network side (this parameter is available for IGX switches, but not BPX switches).
3. Use the cnfswfunc command to ensure that the features enabled on the new node are the same as those enabled on the network.
  
  Note: Refer to Understanding and Enabling Software Functions (cnfswfunc) on BPX 8600 Switches when you use the cnfswfunc command to determine which features you can purchase and which are free.
  
  Caution: You can potentially lose network features if you do not correctly configure a new node which is then added to your network.
  
  You must ensure that the parameters match before you join the networks. This is best done according to these steps because each parameter is negotiated separately.
Complete these steps in order to configure the trunks to other routing nodes:
1. Use the dspcds command to verify that the correct cards are in both the local and remote nodes.
2. Use the uptrk command to bring up the trunk at each node.
3. Use the cnftrk command to configure any parameters required for the trunk at each node.
4. Use the cnfnodeparm command to change node parameters 2 and 3 from 30000 to 60000. This increases the time between network messages.
5. Use the addtrk command, from the new node, to add the new node.
6. Use the cnfnodeparm command to change the node parameters 2 and 3 from 60000 to 30000 when the node is added and can reach all nodes in the network.