RuggedCom RS400 manual Resetting Ports, Ethernet Ports Name, Duplex

Ethernet Ports

Name

Synopsis: Any 15 characters

A descriptive name that may be used to identify the device connected on that port.

Link

Synopsis: { ----, ----, Down, Up }

The port's link status.

Speed

Synopsis: { ---, 10, 100, 1000 }

The port's current speed.

Duplex

Synopsis: { ----, Half, Full }

The port's current duplex status.

3.2.8 Resetting Ports

This command performs a reset of the specified Ethernet ports. This action is useful for forcing re-negotiation of speed and duplex or in situations where the link partner has latched into an inappropriate state.

3.3 Troubleshooting

Problem One

One of my links seems to be fine at low traffic levels, but starts to fail as traffic rates increase.

One of my links pings OK but has problems with FTP/SQL/HTTP/…

A possible cause of intermittent operation is that of a ‘duplex mismatch’. If one end of the link is fixed to full duplex and the peer auto-negotiates, the auto-negotiating end falls back to half- duplex operation. At lower traffic volumes the link may display few if any errors. As the traffic volume rises the fixed negotiation side will begin to experience dropped packets while the auto- negotiating side will experience collisions. Ultimately, as traffic loads approach 100% the link will become entirely unusable.

Note: The ping command with flood options is a useful tool for testing commissioned links. The command “ping 192.168.0.1 500 2” can be used to issue 500 pings each separated by 2 milliseconds to the next switch. If the link used is of high quality then no pings should be lost and the average round trip time should be small.

Problem Two

I am trying to use the LFI protection feature but my links won’t even come up.

Is it possible that the peer also has LFI enabled? If both sides of the link have LFI enabled then both sides will withhold link signal generation from each other.

RS400 109 ROS™ v3.5