u2000 side durring cusotmer make nms inspect found there are lot of temparary routes . there is high risk once LINUX system rebooted these temp routes will be lost .
Configuring Routes
This topic describes how to configure routes. After the U2000 is installed, if the network configurations of the server change, you can configure the routes of the server through the MSuite.
Prerequisites
•U2000 processes must have been stopped.
◾For the Single-Server System (Windows), see How to End the Processes of the U2000 Single-Server System on Windows.
◾For the Single-Server System (Solaris), see How to End the Processes of the U2000 Single-Server System on (Solaris).
◾For the Single-Server System (SUSE Linux), see How to End the Processes of the U2000 Single-Server System on (SUSE Linux).
◾For the High Availability System (Solaris/SUSE Linux), see How to End the U2000 Processes of the High Availability System (Solaris, PC Linux).
•The MSuite server and client are installed on the same computer or communicate with each other properly.
Context
•In the high availability system (Veritas hot standby), if you need to modify the routes of the primary and secondary sites, you need to log in to the MSuite servers of the primary and secondary sites to perform the operation.
•On Solaris, if the MSuite client is not installed and you need to modify the default route, see How to Add the Default Route. If the MSuite client is not installed and you need to modify a static route, see How to Add a Static Route.
•On SUSE Linux, if the MSuite client is not installed and you need to modify the default route, see How to manually Add the Default Route (SUSE Linux). If the MSuite client is not installed and you need to modify a static route, see How to manually Add a Static Route (SUSE Linux).
NOTICE:
Modifying routing information may result in network interruption. Perform this operation only if you fully understand network conditions.
NOTE:
Configuring routes on Solaris OS is used as an example.
Procedure
1.Ensure that the MSuite server has been started.
Run the following command as the root user to check whether the MSuite servers are started:
NOTE:
If security hardening is enabled, log in to the OS as the ossuser user. Then run the su - root command and enter the root user password to switch to the root user.
# ps -ef | grep javaA message similar to the following will be displayed in the Solaris system:
...
root 16023 12635 0 16:53:09 pts/4 0:00 grep java
ossuser 21288 1 0 May 17 ? 45:21 /opt/oss/OSSJRE/jre_sol/bin/java -server -Dlanguage=zh -DoperationIp=10.61.33.2mA message similar to the following will be displayed in the SUSE Linux system:
...
root 7593 7130 0 06:31 pts/7 00:00:00 grep java
ossuser 8937 12803 0 04:13 pts/8 00:00:42 /opt/oss/OSSJRE/jre_linux/bin/java -Dprocname=AgentIntegrate -Dfile.encoding=UTF8 -Xmx1024m -XX:MetaspaceSize=16m -XX:MaxMetaspaceSize=256m -XX:+UseCompressedClassPointers -XX:+UseCompressedOops -XX:CompressedClassSpaceSize=128m -XX:+HeapDumpOnOutOfMemoryError -DabsCfgPath=/opt/oss/server/etc/oss_cfg/frame -cp nbi/agentintegrate/thirdparty/*:3rdlib/*:common/uflightdispatcher/lib/jdom.jar:cbb/qasn/lib/*:common/uflight/frame_app/plugins/com.huawei.uflight.platformadapter/*:common/uflight/web_app/plugins/pax-web-runtime-2.1.2.jar:common/uflight/web_app/plugins/web_app/plugins/pax-web-spi-2.1.2.jar:nbi/agentintegrate/lib/*:nbi/agentintegrate/bin/* com.huawei.u2000.inventory.webserver.JettyStarter
... NOTE:
If the displayed information contains /opt/oss/OSSJRE/jre_sol/bin/java -server in the Solaris system and /opt/oss/OSSJRE/jre_linux/bin/java -server in SUSE Linux system, the MSuite servers have been started.
If the MSuite servers have not been started, switch to the ossuser and run the following commands as the root user to start the MSuite servers:
# su - ossuser$ cd /opt/oss/engr/engineering$ ./startserver.sh
2.Log in to the MSuite client. For details, see Logging In to the MSuite Client.
3.On the MSuite client, click the Server tab.
4.Right-click the target server and choose Configure Route from the shortcut menu. The Configure Route dialog box is displayed.
5.In the dialog box that is displayed, click Add or Delete according to actual route conditions to configure the route.
NOTICE:
Before adding a route, ensure that the server and the router are directly connected. Otherwise, the route cannot be added.
For example, the procedure for adding a route from a client (IP address: 10.70.73.77) to a server (IP address: 10.71.224.12) is as follows, with the IP address of the intermediate router being 10.71.224.1:
a.Ensure that the server and the router are directly connected.
b.Click Add. Set Destination to 10.70.73.0, Subnet Mask to 255.255.255.0, and Gateway to 10.71.224.1.
6.Click OK.
7.After the configurations are complete, run the netstat -nr command to view route configurations.
se temp rout
