Installing and Administering LAN/9000 Software

66 Chapter4

Troubleshooting LAN/9000

Troubleshooting Q & A

New system disrupts LAN: I tried to attach a new system to our site

LAN. To make the installation process faster, I copied over an

/etc/rc.config.d/netconf ﬁle from another system on the site LAN

and used it on the new system. When I booted up the system, the site

LAN went down.

Answer: You probably didn't assign a new IP address and host name

prior to rebooting the system. If any two systems on the LAN have the

same IP address and host name, the LAN will go down. Check the IP

address in the /etc/rc.config.d/netconf ﬁle against the IP address of

your system and other systems on your network map to be sure that no

duplicate IP addresses exist on the LAN.

Related Documentation: Refer to the ifconfig(1M) man page.

Determining interface name: How do I determine the name of the

interface to be conﬁgured?

Answer: Use the lanscan command to determine the hardware path of

the interface card that you want to conﬁgure. Then use the value

displayed for the “Net-Interface Name PPA” ﬁeld as the interface name.

Multiple LAN interfaces, intermittent failures: I have been having

problems getting the two LAN interfaces on my system to operate at the

same time. Occasionally the ethernet cards stop communicating with

remote systems. When this happens, the remote system also cannot

communicate with the local system.

Answer: Check that the two interfaces on your system do not have the

same network number or, if you are subnetting, the same subnet

address. If both LAN interfaces have the same value in the network

(subnet) address portions of the IP address, the cards may not be enabled

simultaneously (although they may both run separately.)

Related Documentation: Refer to chapter 6, “Network Addressing”.

New system, can’t reach some subnets: I recently tried to add a new

system onto a subnet on our site LAN, and I am not able to communicate

successfully with all LANs on the network.

Answer: Check the routing table to make sure the route for the LAN you

are trying to communicate with has been properly conﬁgured. Execute

netstat -rvn on both ends. Verify the subnet address, netmask and