The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
The RDU (Regional Distribution Unit) redundancy feature involves setting up the RDU in High Availability (HA) mode where a two node failover pair is configured for the RDU.
This chapter describes how to configure the RDU redundancy feature in Prime Cable Provisioning.
The following prerequisites must be met before you proceed with RDU redundancy setup:
Utility Requirements
Redundancy Requirements
Redundant network configuration should be available to avoid network downtime.
Redundant electrical supply must be available on both servers. Ensure that the electrical supply source for both servers is reachable.
PCP Geo Redundancy Requirements
Route injection for VIP (virtual IP) needs to be done on the ingress routers to which primary and secondary servers are connected.
The VIP will be advertised as RIP2 advertisement from the active server ,so route redistribution needs to be done for RIP2 to the dynamic routing protocol running in the user environment.
Example: Here OSPF is the dynamic protocol
router ospf 1
redistribute rip metric-type 1 subnets.
Logical Volume Manager (LVM) Setup
Both RDU nodes must be configured over Logical Volume Manager (LVM). The LVM allows you to create a volume group which can be further divided into logical volumes based on the requirement. The LVM also provides the flexibility to resize the volume group and logical volumes based on the dynamic memory usage.
On both primary and secondary RDU nodes, a logical volume group must be created with three logical volumes on it. The logical volumes are created based on the following specifications:
<logical volume for Prime Cable Provisioning install directory> - Mounted on /bprHome directory. For example, LVBPRHOME.
<logical volume for Prime Cable Provisioning data directory> - Mounted on /bprData directory. For example, LVBPRDATA
<logical volume for Prime Cable Provisioning log directory > - Mounted on /bprLog directory. For example, LVBPRDBLOG
Ensure that the /etc/fstab entries are updated for these logical volumes.
Ensure that the /bprData, /bprHome, and /bprLog directories are empty.
The logical volumes should be of same capacity on both the nodes with a pre-created ext4 filesystem.
Requirements for Proper Synchronization between Nodes
Identify the virtual IP address that can be used to locate both servers. Ensure that this virtual IP address is not configured for any physical interfaces in the network infrastructure. Also, this virtual IP address must belong to the network cluster in which you configure the primary and secondary RDU nodes.
The Network Time Protocol (NTP) must be synchronized between primary and secondary RDU nodes.
Both RDU nodes must exist in the same network cluster. This ensures that the same virtual IP address can be used to reach both the RDU nodes.
Both RDU nodes must be configured with the following two network interfaces:
Public access - Used for external communication. The DPE, PWS, CPNR_EP, and API clients use this interface to communicate with the RDU. A public IP address is configured to access this network interface.
Failover link between RDU nodes - Used for disk synchronization. If the RDU nodes are co-located, the failover link can be a crossover link, else the failover link must be configured in the private LAN. The failover IP addresses for primary and secondary nodes must be unique in the network cluster. This is to achieve the high speed access between primary and secondary RDU nodes, and also make them isolated from the network traffic.
Miscellaneous Requirements
The following figure provides a high level RDU HA setup.
If both primary and secondary RDU nodes are available in the network infrastructure, you can use primary-secondary installation mode to configure HA cluster.
Before installing the RDU redundancy function, you must perform the required server configurations and establish a communication channel between primary and secondary RDU servers.
To prepare primary and secondary RDU nodes for HA setup:
Sequence | Installation Scripts | Description |
---|---|---|
1 | pre_install_bac_HA.sh |
|
2 | install_bac.sh | Used to install the RDU component on the logical volumes. |
3 | post_install_bac_HA.sh | Used to automate the supported configuration tasks for RDU redundancy function setup. |
To set up the RDU two node failover pair:
Step 1 | Log into the primary RDU as root. |
Step 2 | Extract the installation package using the following commands: |
Step 3 | Run the
preinstallation script using the following command:
# sh pre_install_bac_HA.sh
|
Step 4 | Enter the RDU redundancy information. The RDU redundancy information includes: |
Step 5 | Enter the name of the logical volume group. For example, VGBPR. |
Step 6 | Enter the name of the logical volumes created for home, data, and database log directories. For example, you can enter LVBPRHOME for home directory, LVBPRDATA for data directory, and LVBPRDBLOG for database log directory. |
Step 7 | Enter the network IP address of the subnet under which both the RDU cluster nodes exist. |
Step 8 | Enter the
virtual IP address. The virtual IP address is the floating IP address that is
used to reach both primary and secondary RDU nodes, but allocated to only
active RDU node. Ensure that this virtual IP address is not configured for any
physical interfaces in the network.
|
Step 9 | Enter
y to enable
automatic failback, else enter
n. If the
automatic failback is enabled, the primary RDU node becomes active once it
comes up after the failover event.
|
Step 10 | Install RDU on the synchronized logical volumes; LVBPRHOME, LVBPRDATA, and LVBPRDBLOG. For details, see Installing the RDU in Interactive Mode. |
Step 11 | Run the post-installation script available under
directory:
# sh post_install_bac_HA.sh
The post-installation script performs the automated configuration tasks required for RDU redundancy function setup. |
To uninstall the RDU HA setup in the primary and secondary RDU nodes, you must run the uninstall scripts sequentially. The following table describes the uninstall scripts and the sequence in which you run them.
Sequence | Uninstall Scripts | Description |
---|---|---|
1 | uninstall_bac.sh | Used to unistall the RDU component from the logical volume blocks; /bacHAHome, /bacHAData, and /bacHADBLog . For details, see Uninstalling Prime Cable Provisioning. |
2 | uninstall_bac_HA.sh | Used to remove the utilities installed for RDU redundancy
function.
|
RDU Geo Redundancy is an enhanced feature of RDU HA supported on RHEL 6.5 or CentOs 6.5 (both 64bit), wherein the RDU primary and secondary node can be in different geographical location or both the nodes can be in different subnet.
In Geo redundancy mode the VIP can be in any subnet it is not necessary to have in the subnet range common to both nodes.
In Geo redundancy mode the CIDR value of VIP should be 32.
The VIP will be advertised as a RIP advertisement from the active server, so on the ingress router of both the nodes route injection need to be done.
For setting up RDU in Geo redundancy mode follow steps mentioned in Setting Up RDU Redundancy