Abstract:After the server configuration is modified and restarted, the resource status is not online or offline, and the status of faulted and state unknown occurs, causing the maintenance tool to fail to start
Case Body:
Background
The network management system installed this time is the local high availability system (Veritas) U2000, based on SUSE (Linux). Local dual-machine configuration, three directions: connect the core device in the south direction, connect the yi yang to the north through the DCN network, connect the heartbeat between the two machines, and configure BOND. The IP address needs to be configured with southbound, northbound, heartbeat, and floating IP. After the configuration, you need to restart to make the configuration take effect.
Problem, event description
After the restart, the status of APP BOND is FAULTED and the status of FloatIP is UNKNOW. In this case, even if the hares –online command is used, online APP BOND cannot be enabled, and the network maintenance tool cannot be opened.

Analysis and countermeasures
Enter the following command to view the information:
hares –display APPBOND | grep Device

cat /etc/sysconfig/network/ifcfg-bond0

cat /etc/hosts

cat /etc/hosts.YaST2save

cat /etc/ICMR/netCfg/VCS/vcs_net_config.cfg

cat /etc/OSSENGR/engrIPInfo.xml
ifconfig –a

Copy the contents of bond1 to the configuration of bond2:
ifcfg-bond0
cd /etc/sysconfig/network/
cp ifcfg-bond1 ifcfg-bond0
vi ifcfg-bond0

There is still no bond2 in the same directory, but there is eth38:

cp ifcfg-eth38 ifcfg-eth2
Then execute rcnetwork restart
At this point, both interfaces appear, and after restarting the device, the response is normal.
process result
The southbound bond has two interfaces, eth2 and eth38. The real network cable only connects to eth2, but the configuration is configured with 38 by default. After the 38 configuration is transferred to eth2, it returns to normal.
experiences and lessons
To learn to view interface information, especially if you have a bond but directly connected to a network cable, be sure to see if your configuration is equipped with a valid port