Back
If you run he ifconfig command and see no output, that means all network devices are currently inactive. If you run the ifconfig -a command and don't see an UDP in the output to any configured network device, that confirms the inactivity.
The first thing to check in that case is the contents of the /etc/sysconfig/network configuration file. It's a pretty simple file. In general, you should see something similar to the following in that file.
NETWORKING = yes
HOSTNAME = server1.example.com
If NETWORKING = no, then the /etc/sysconfig/network script does not activate any devices. The one other issue that may prevent networking from starting is the status of the script. Run the chkconfig --list network command. The output should look like :
0:off 1:off 2:on 3:on 4:on 5:on 6:off
If the settings next to the run-levels 3 and 5 are off, that's problem. To make sure a command service is active in appropriate run-levels, run the chkconfig network on command .
If you run he ifconfig command and see no output, that means all network devices are currently inactive. If you run the ifconfig -a command and don't see an UDP in the output to any configured network device, that confirms the inactivity.
The first thing to check in that case is the contents of the /etc/sysconfig/network configuration file. It's a pretty simple file. In general, you should see something similar to the following in that file.
NETWORKING = yes
HOSTNAME = server1.example.com
If NETWORKING = no, then the /etc/sysconfig/network script does not activate any devices. The one other issue that may prevent networking from starting is the status of the script. Run the chkconfig --list network command. The output should look like :
0:off 1:off 2:on 3:on 4:on 5:on 6:off
If the settings next to the run-levels 3 and 5 are off, that's problem. To make sure a command service is active in appropriate run-levels, run the chkconfig network on command .
