Table of Contents
Advertisement
RUGGEDCOM ROX II
CLI User Guide
Troubleshooting
This chapter describes troubleshooting steps for common issues that may be encountered when using
RUGGEDCOM ROX II or designing a network. It describes the following tasks:
IMPORTANT!
For further assistance, contact Siemens Customer Support.
NOTE
For a description of pre-configured alarms, refer to
•
Section 6.1, "Feature Keys"
•
Section 6.2, "Ethernet Ports"
•
Section 6.3, "Multicast Filtering"
•
Section 6.4, "Spanning Tree"
•
Section 6.5, "VLANs"
Section 6.1
Feature Keys
The following describes common problems related to feature keys.
Problem
A file-based feature key does not match the
hardware
Section 6.2
Ethernet Ports
The following describes common problems related to Ethernet ports.
Problem
A link seems fine when traffic levels are low,
but fails as traffic rates increase OR a link
can be pinged but has problems with FTP/
SQL/HTTP/etc.
Feature Keys
Section 4.6.1, "Pre-Configured
Solution
Each file-based feature key is licensed to a particular device. When transferring a feature
key from one device to another, such as when configuring a backup unit to replace a
malfunctioning device, the device will detect a hardware mismatch with the key and trigger
an alarm.
Do not transfer file-based feature keys between devices. Contact a Siemens Canada Ltd.
sales representative to order a feature key matching the serial numbers of the hardware in
the destination device.
Solution
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-
Chapter 6
Troubleshooting
Alarms".
623
Advertisement
Table of Contents
Troubleshooting
