Configuring Ethernet Interfaces
Troubleshooting an Ethernet Interface
Depending on the error messages displayed, you should check the cabling or
the configuration settings for the Ethernet interface. If the "eth 0/1 is DOWN"
message is displayed, substitute a different 10Base-T or 100Base-T cable and
make sure the connectors are securely seated in the Ethernet port on both the
router and the far-end device.
If the "line protocol is DOWN" message is displayed, check your configuration.
Ensure that the Ethernet interface can successfully negotiate the speed and
duplex settings for the line.
show event-history Command
Another useful tool for troubleshooting problems on the Ethernet interface is
the show event-history command. By default, the ProCurve Secure Router
logs events such as changes in the status of interfaces and ports. To display
this information, enter the following command from the enable mode context:
ProCurve# show event-history
To isolate problems, you can clear the event history, reproduce the problem,
and then display the event history again. To clear the event history, enter the
following command from the enable mode context:
ProCurve# clear event-history
The event history is automatically cleared when the router is rebooted.
debug interface ethernet Command
If you check the configurations and basic hardware used for the Ethernet
connection and still cannot resolve the issue, you can use the debug interface
command to display information about the interface in real-time.
Syntax: debug interface <interface>
Replace <interface> with Ethernet.
For example, if you cannot establish an Ethernet connection, you may want
to enter this command to determine if the Ethernet interface is successfully
negotiating the speed and the duplex setting. Figure 3-9 shows the debug
messages for an Ethernet interface that was successfully established.
3-25