Dear All,
We have upgraded our network via Cuda12000. In Cuda 12000, we have two Controller cards so we would like to configure one as primary and other as secondary. At this moment, both are plugged and showing primary on front led.
Kindly advice.
Regards,
Tahir
is not a good thing.
The configuration of this is not done through the CMTS CLI from by running a setup script from linux on each BCM module.
First you have to make sure they have the same revision of code in the same partitions.
Hook up a keyboard and monitor to each bcm and from linux run the following commands:
show_partitions.sh
and
rpm -qa | grep -i cuda
The output could look something like the following depending on the code version:
root@adc-cuda /root]# show_partitions.sh
Partition Set 1: 5.5.0 (327) *** Active ***
Partition Set 2: empty
[root@adc-cuda /root]# rpm -qa | grep -i cuda
Cuda12000-common-3.1-58
Cuda12000-base-3.1-58
Send me the output and we'll see if this can be setup.
Dear,
Following is the output of commands;
[root@adc-cuda /root]# show_partitions.sh
Partition Set 1: 7.0.0 (191) *** Active ***
Partition Set 2: 6.0.1 (21)
[root@adc-cuda /root]# rpm -qa | grep -i cuda
bash: rpm: command not found
Kindly advice.
I only see the partition info from one module. Does the other BCM have the exact same versions in the respective partitions?
From the cli on the production BCM do a show version and send the output.
Dear,
Other BCM Hard drive is the mirror of primary BCM. so, the partition, Cuda version and configuration is same in both BCM hard-drives.
Regards,
Tahir
I can't speak about the 7.x code train but there was NO automatic mirrioring capabilities of the partitions or images in the 6.x train. You had to manually build the image contents of the second module being installed to match the existing BCM. If you DONT have matching partions and matching images, setting up BCM redundancy will fail.
If you added a second bcm to the chassis recently and both say primary I would plug in a keyboard to the recently added BCM and hit Ctrl-Alt-Del, when you see the lights go off back it out of the chassis.
Log in and copy of the current running config before attempting to setup BCM redundancy.
From linux (on each BCM) you'll find a script named config_chassis. Below is a snapshot of a functional redundant BCM setup. The configuration below does not used the 10/100 craft port on either bcm for out of band ip management. You notice in the setup configuration that each bcm points to the name of the OTHER PARTNER module, i.e. setup run on slot 13 bcm point to slot 14 and 14 points to 13.
Use the setup script to name each bcm based on the slot they resides in. On my system it's named cuda-west.
If the bcm in slot 13 is the operational one do the following:
[root@cuda-west-13 /root]# config_chassis.sh
Do you wish to configure a redundant Chassis Controller? [Y]:
Hostname of this Chassis Controller [cuda-west-13]:
Do you wish to configure management craft port (eth0) [Y]: n
Hostname of partner Chassis Controller [cuda-west-14]: cuda-west-14
The default shared hostname is undefined.
Would you like to configure the virtual hostname with the default value? [Y]:
The default configuration for eth1 and eth2 is:
eth1 /28 subnet: 192.0.2.0/28
eth2 addresses: 192.0.2.17/30 and 192.0.2.18/30
Would you like to configure eth1 and eth2 with the default values? [Y]:
error reading information on service basctlr: No such file or directory
The default IP Monitor configuration is:
Enabled = No
Would you like to configure the IP Monitor with the default values? [Y]:
The default configuration of Console on Serial port is:
ENABLED (9600)
Would you like to configure the Console with the default value? [Y]:
Chassis Controller configuration complete. Please REBOOT for
the changes to take effect.
Reboot now? [Y]: y
At the point the BCM will go down, will reboot and it will attempt to find a peer bcm in the chassis. The LED will display this activity. After about 5 miutes it will eventually say primary.
INSTALL the second BCM into the chassis and run the setup script on it. Notice below that this one is named 14 since it resides in slot 14.
[root@cuda-west-14 /root]# config_chassis.sh
Do you wish to configure a redundant Chassis Controller? [Y]:
Hostname of this Chassis Controller [cuda-west-14]:
Do you wish to configure management craft port (eth0) [Y]: n
Hostname of partner Chassis Controller [cuda-west-13]:
The default shared hostname is undefined.
Would you like to configure the virtual hostname with the default value? [Y]:
The default configuration for eth1 and eth2 is:
eth1 /28 subnet: 192.0.2.0/28
eth2 addresses: 192.0.2.17/30 and 192.0.2.18/30
Would you like to configure eth1 and eth2 with the default values? [Y]:
error reading information on service basctlr: No such file or directory
The default IP Monitor configuration is:
Enabled = No
Would you like to configure the IP Monitor with the default values? [Y]:
The default configuration of Console on Serial port is:
ENABLED (9600)
Would you like to configure the Console with the default value? [Y]:
Chassis Controller configuration complete. Please REBOOT for
the changes to take effect.
Reboot now? [Y]: y
The module will reboot, hopefully find it's peer, and begin the sync process for the chassis configuration from the primary module. After about 10-15 minutes is should say seconday on the led display. If both say primary there is something wrong like non matching partitions, images or incorrect hostnames.
Thanks dear its working fine with primary and secondary combination.