How to cycle a external interface

Response:

This notification might be issued during network maintenance. If the notification was issued during network maintenance and you experience no other symptoms, you can safely clear the notification.

To clear the notification:

1. Open an SSH connection on any node in the cluster and log on using the "root" account.

    2.Run the following command where is the alert ID of the alert you want to cancel:

isi alert cancel

NOTE
You can get the event ID for the notification you want to clear by running the following command:

isi alert list

If this notification was not issued during network maintenance, follow the steps below to troubleshoot the issue:

1. Ensure that the node's network cable is connected securely and that neither the cable nor the connector is damaged.
2. If the carrier issue is intermittent, try the following:
   1. Determine whether the issue is related to the cable or the node.
      • Plug the cable into another node that has a functioning network port and an identical network configuration. Be sure to plug the cable into the same switch port on the different node.

             2.If the issue persists, replace the cable.

             3.If the issue persists, move the cable to a different port on the switch.

             4.If the issue persists, review the switch logs.

3.If this alert is not ongoing and this is not a recurring problem, ensure that all cables in the rack and in adjacent racks are connected securely.

4.If none of the suggested solutions resolves the issue, contact Isilon Technical Support.

chjatwork,

You can use the ifconfig command to mark an interface down and then back up again.

ifconfig em0 down

ifconfig em0 up

Note that this will mark the interface as down, which should trigger an alert message and stop traffic to that interface, which could be disruptive to active operations.  For more information on the command you can use 'man ifconfig'.

However, I must add that I do not believe this is a solution to the status message you posted above.  In the alert above, the message indicates the external link is down.  Suman has correctly responded with some steps you can take to troubleshoot a flaky connection if this is happening regularly.  It has not been my experience that cycling the interface would offer a resolution, rather that either maintenance was in progress that temporarily interrupted traffic to that interface, or a failing cable or link may be responsible.  If the problem persists, do contact Isilon Technical support for further assistance.

Hi Cadiletta

have you had these problems with the interfaces?

My interface no work (ext-1)

I rebooted the node

I got ping but I disconnected the cable ethernet and I lost the ping, I connected my cable and I couldn't recover the ping

I checked about cable and port of switch, they are ok

I tried to down and up the interface but I got the same result

do you have any ideas about the problem?

Thanks

Hi Francisco,

What kind of switch are you connecting to?  I recall seeing similar behavior with a cheap Ethernet switch.  When they auto-negotiate a race condition occurs, causing one or both ends to never reconnect.

Try setting the switch end to a fixed setting (i.e. NOT auto-negotiate, set full-duplex, etc...) and see if that helps.

This should not occur in most modern hardware, but you never know.

I would also try another Ethernet cable as well; nothing worse than having a $5 defective cable waste your time...

Cheers,
Matt