Troubleshooting
Ethernet port
Appendix C
Tr
oubleshooting
VIPER Product Family User’s Guide
175
Ethernet port
Symptom:
The VIPER fails to access a network through
the Ethernet connection.
1. If you have a console window active, the Ethernet cable can
be removed or inserted any time. When inserted, the speed
and duplex conditions of the connection are displayed.
2. Make sure the Ethernet cable is securely connected at both
ends.
3. At the # prompt, type
ifconfig -a
, press Enter, and
look for bge0 to verify the Ethernet connection. Your display
should show a list of active flags, one of which must be
“
up
”. You should also see your Internet address.
If bge0 does not appear, try typing the following com-
mands at the
#
prompt:
ifconfig bge0 plumb
ifconfig bge0 IPADDR up
4. Type
ping -s <hostname>
and press
Enter
to ver-
ify your connection to the host. The display should show the
following information continuously:
• 64 bytes returned
• Your Internet address
• One ICMP sequence number
• The round-trip time it takes data to travel from
the notebook to the host and back
If <hostname> is not in your host file, use an IP address.
To stop this information from scrolling, hold down the
Ctrl key and press C.
5. Run
watch-net
at OBP as a low level hardware port
check.
Summary of Contents for VIPER
Page 1: ...VIPER Product Family User s Guide...
Page 20: ...xx VIPER Product Family User s Guide Table of Contents...
Page 21: ...Preface...
Page 27: ...Chapter 1 Overview...
Page 35: ...Chapter 2 Getting Started...
Page 45: ...Chapter 3 Using VIPER...
Page 102: ...76 VIPER Product Family User s Guide...
Page 103: ...Chapter 4 Maintaining VIPER...
Page 116: ...90 VIPER Product Family User s Guide...
Page 117: ...Chapter 5 Power Management...
Page 127: ...Chapter 6 Changing Locations...
Page 145: ...Chapter 7 Installing Solaris...
Page 171: ...Chapter 8 VIPER Specifications...
Page 177: ...Appendix A Connector Pin Assignments...
Page 187: ...Appendix B External Monitor Matrix...
Page 192: ...166 VIPER Product Family User s Guide...
Page 193: ...Appendix C Troubleshooting...
Page 207: ...Index...