No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Server Gateway Switchover Through Practical Extraction Reporting Language (Perl)

Publication Date:  2012-07-27 Views:  60 Downloads:  0
Issue Description
When the T8000 is used as the SIG server and the SIG is simultaneously connected to blades 7 and 8 of the T8000 through two GE interfaces for redundancy, the Back End is likely to be directly connected to the Front End, as shown in the following figure.
The Front End of the SIG does not support Ethernet Trunk port mode. The IP addresses of the two interfaces of the Front End are 1.1.1.100/24 (GE3/0/0) and 1.1.2.100/24 (GE3/0/1). The IP addresses of the OMC, SPS, and SAS are on the 192.168.1.0/24 subnet.
The IP address of the blade server ranges from 1.1.1.0/24 to 1.1.1.99/24, and those of the subinterfaces range from 1.1.2.0/24 to 1.1.2.99/24.
 
Alarm Information
None.
Handling Process
Step 1     Ping 1.1.1.100. If this IP address is unreachable, change the next hop of 192.168.1.0 to 1.1.2.100. If 1.1.2.100 is unreachable, change the next hop of 192.168.1.0 to 1.1.1.100.

Step 2     Add subinterfaces. Access /etc/sysconfi/network and locate the network interface card (NIC) to which the subinterfaces will be added. In this example, the NIC (fabric) is added to bond0.

Modify the file using vi and add three lines as shown in the contents circled with red lines in the following figure. After restarting the NIC services, you can bind multiple IP addresses with the NIC.  

IPADDR_xxx=’1.1.2.1’            #IP address. The part represented by xxx must be identical to the content in the label.

IPADDR_xxx=’1.1.2.1’            #Net mask. The part represented by xxx must be identical to the content in the label.

LABEL_xxx=’xxx’ #              #Label of the NIC.

Set the gateway IP address to 1.1.1.100 using YaST.
The following describes the scripts needed.
With one Front End (in this example)

With two Front Ends (the Ukraine project)


Execute the script in the following directory. The script is applicable to SUSE Linux, and may not be applicable to Red Hat.
The files in /etc/init.d:
boot.local: This bootup file is initialized before the rc5.d script is executed.
halt.local: This shutdown file is initialized at last.
before.local: This file is a commonplace and therefore omitted.
after.local: This file is initialized after the rc5.d script is executed. Routes are set in this file and the bootup file is copied or written in this file.

Root Cause
By default, Linux does not support dynamic routing.
Suggestions
This solution streamlines high-availability networking and reduces the needed network devices at the cost of higher system resource consumption and more applications of the operating system.
The script can be executed by using the Linux scheduling function crontab to achieve switchover within minutes; or by automatic writing calculator to achieve switchover within seconds. In addition, calling the shell function by using Perl is inefficient. Installing a ping-Net package can improve the efficiency, but ensure that the package is compatible with other SIG files.
The openness and diverse interfaces of Linux system offer greater flexibility to accommodate more complicated applications.

END