Ruijie S8600E Series Operating instructions

S8600E Series Switch
Routine Maintenance and Troubleshooting

Contents
■Preface
■Routine Maintenance Suggestions
■Handling of Common Faults
■Troubleshooting
■Obtaining Help

Preface
Revision History
Audience
Ruijie business partners and customers who are responsible for configuring
and maintaining Ruijie wireless devices.
Note :
For more detail configuration , see configuration guide for each product . you can download
configuration guide at http://www.ruijienetworks.com
For more technical enquiry , you can visit Ruijie Service portal at http://case.ruijienetworks.com
. You need to sign up before submit a case.

Contents
■Preface
■Routine Maintenance Suggestions
■Handling of Common Faults
■Troubleshooting
■Obtaining Help

Routine Maintenance Suggestions
Importance of routine maintenance:
□Routine maintenance is preventative, during which defects or potential issues
of the device can be timely detected and solved in the process of normal
operating and the device health level can be maintained, so that the device
can securely, stably, and reliably operate in a long term.
Major contents of routine maintenance:
■Hardware running status maintenance
■Smart and automatic health check and periodical maintenance using the Ruijie
Networks health check tool (recommended)
■Manual check of software running status
■Periodical maintenance using the network management system (NMS)
■Checking whether the version upgrade is needed every half year or every year

Routine Maintenance Suggestions–Hardware Running Status
Maintenance
■Check the environment.
□Cleanness:
▪The equipment chassis and floor should be clean and free of any dust. Clean or replace the cabinet
air filters in time; otherwise, ventilation and heat dissipation of the cabinet door and fan tray will be
affected.
□Heat dissipation:
▪When the device runs normally, fans should run properly. If any fan is faulty, the device temperature
will increase and may damage the device. Do not place sundries at the air inlet or outlet of the
device. In addition, periodically clean the dust away from the fans to prevent too much dust from
accumulating on the fans.
▪Run the Ruijie#show tempr command to check whether the operating temperature of the device is
normal.
▪It is recommended a routine inspection be performed on a monthly basis.

Routine Maintenance Suggestions–Hardware Running Status
Maintenance
■Device hardware status:
□Status indicators:
When the device is running, you can check the indicators on boards to monitor the running status
of each board.
If the Alarm indicator on the supervisor module is on in red, a fault occurs in the system. In
this case, log in to the system and check the logs or hardware status information to locate
and rectify the fault.
If the Alarm indicator on the supervisor module is on in yellow, the system temperature
exceeds the alarm threshold and affects the running performance of the system, but the
system can still run. In this case, log in to the system and check the related fault information
to locate and rectify the fault.
If the Status indicator of the fan tray is off, the fan tray is not powered or is faulty. In this
case, log in to the system and check the fan status.
If the Status indicator on a board is off, flashes, or is on in red, the board is faulty. In this
case, identify the fault cause and, if necessary, perform a power-off check.
It is recommended a routine inspection be performed on a monthly basis.

Routine Maintenance Suggestions–Hardware Running Status
Maintenance
■Device hardware status:
□Fans:
▪Fans do not generate abnormal sound. Little dust is attached on the fans. You can run
the show fan command to display the operating status of fans.
□Power supply:
▪The power supply is normal, and the indicator is on in green. You can run the show
power command to display the operating status of the power supply.
It is recommended a routine inspection be performed on a monthly basis.

Routine Maintenance Suggestions–Manual Check of Software
Running Status
Recommended check items:
Health status items:
■CPU usage: Check whether the CPU usages of the line card and engine are
normal.
■CPU protection (CPP) count: Check the number of received or dropped CPU
packets to judge whether the network environment is normal.
■Memory usage: Check whether the memory usage is normal.
■Interface status: Check whether any interface encounters a CRC error.
■Logs: Check whether any abnormal log information exists.
Device configurations (optional)
Run the show ip route command to check whether the route size is the same or
close to the normal size.
Run the show arp counter command to check whether the number of users is the
same or close to the usual size.
Run the show run command to check whether any configuration changes.
It is recommended a routine inspection be performed on a monthly basis.

Routine Maintenance Suggestions–Manual Check of Software
Running Status
■CPU usage:
□Use the show cpu command to check the CPU running status.
▪Ruijie#show cpu New feature: The CPU usage of each line card can be
displayed in RGOS 11.X.
=======================================
CPU utilization in five seconds: 12.41%
CPU utilization in one minute: 13.11%
CPU utilization in five minutes: 13.08%
The CPU usage may increase sharply in a short time if a batch configuration is
performed or a show command is executed. This is a normal symptom.
▪show processes cpu history New feature: Statistics can be taken on the
history CPU usages.
▪In the healthy state, "CPU utilization in five minutes" should be lower than
30%. The CPU usage increases with the load of bearer services, which is a
normal symptom. However, if the CPU usage exceeds 60%, call 4008-111-
000 for consultation or check the technical support documents on the official
website of Ruijie Networks.
It is recommended a routine inspection be performed on a monthly basis.

Routine Maintenance Suggestions–Manual Check of Software
Running Status
■CPP status:
The system performs queuing and rate limitation on packets sent to the CPU based
on priorities of packets, thus protecting its own CPU.
□Run the show cpu-protect command to check the information about different
protocol packets received by the CPU.
▪In the healthy state, the rate of any protocol packet does not exceed the
preset threshold. If the rate of a certain protocol packet continuously
exceeds the threshold, this type of packet is dropped, and the number of
dropped packets keeps increasing, you need to identify the source of this
type of packets on the network and handle the fault accordingly. (You
can run the show cpu-protect command for two or three times to verify
that the fault occurs.)
It is recommended a routine inspection be performed on a monthly basis.

Routine Maintenance Suggestions–Manual Check of Software
Running Status
■Memory usage:
Run the show memory command to check the memory running status. (New features: You
can run the show memory sorted total command to list processes based on the memory
consumed by each process, or the show memory history command to check the history
peak memory usage and related process information.)
In the healthy state, the memory usage should be lower than 60%. The CPU usage
increases with the load of bearer services. If the memory usage exceeds 80%, contact us
for consultation or check the technical support documents on the official website of Ruijie
Networks.
It is recommended a routine inspection be performed on a monthly basis.

Routine Maintenance Suggestions–Manual Check of Software
Running Status
■Interface status:
□Run the show interface command to display the interface status and check:
▪Whether the traffic on an interface is normal. If the traffic approaches or reaches the
bandwidth, check whether the bandwidth meets the current application
requirements. Or, if the network attacks exist and exhaust the bandwidth, pay close
attention to the bandwidth occupied by the multicast or broadcast packets and the
increase rate of packets in a short term.
▪Whether the number of CRC errors and the number of dropped packets are large
and continuously increase. If yes, it is possible that the cable is not in good contact
or ages, or the duplex mode and rate does not match.
□Run the show interface tras dia command to display the Tx/Rx optical power of the
optical module and check whether any alarm is generated.
▪The purpose is to avoid packet loss caused by the faults of links or optical modules,
and eliminate the potential risks.

Routine Maintenance Suggestions–Manual Check of Software
Running Status
■Logs:
□Run the show log command to check whether any abnormal logs exist.
▪Run the show log command to check whether abnormal information
exists in the logs, for example, frequent up/down of interfaces or OSPF
neighbors. If the alarm level is level 2 or above, find the related logs
based on the actual symptoms of faults.
▪If you are not clear about the meaning of logs, contact us for technical
support.
It is recommended a routine inspection be performed on a monthly basis.

Routine Maintenance Suggestions–Automatic Maintenance Using
the NMS
■The NMS supplied by Ruijie Networks, such as SNC and RIIL, can be used to
monitor the CPU usage, memory usage, port traffic, MAC table, ARP table, and
routing table of a device in real time. In addition, the NMS can receive logs and
traps from the device periodically, based on which automatic routine maintenance
can be implemented.

Contents
■Preface
■Routine Maintenance Suggestions
■Handling of Common Faults
■Troubleshooting
■Obtaining Help

Handling of Common Faults
Symptom:
After the device is powered on, the Console port does not have any output, or outputs garbled
characters.
Possible Causes:
①The device is not properly powered on.
②The baud rate of the Console port on the device, baud rate configured on the PC, and
other related communication parameters are inconsistent. Or, the COM port selected on
the HyperTerminal is incorrect.
③The Console cable is damaged, or the line order of the Console cable is not standard.
④The Console cable is not inserted to the main engine.
Solution:
①Check whether the power cable of the device is correctly connected, whether the power
is supplied to the power socket properly, and whether the Status indicator on the front
panel of the device is steady green.
②Change the baud rate of the PC to 9600, and confirm that other COM port parameters
(select Restore Defaults on the HyperTerminal) and the COM port ID are correct.
③Replace the Console cable with the one that delivered with the switch, and configure data
again.
④Use the primary indicator to confirm the location of the main engine.

Handling of Common Faults
Symptom:
After the Ethernet port is connected to the network cable or optical cable, the Link indicator of
the port is off, and the port cannot be enabled.
Possible Causes:
①The Ethernet cable or optical fiber is damaged.
②The optical module type does not match.
③The duplex modes and rates of the Ethernet ports at two ends of the line do not match
with each other. (Currently, S86E ED line cards do not support the half-duplex mode.)
④The Rx and Tx ends are connected reversely.
Solution:
①Run the show interface tran dia command to diagnose the optical signals, and
replace the Ethernet cable or optical fiber with a new one for the test.
②Use the optical modules of the same type (single-mode, multi-node, and distance) for
the test.
③Configure forcibly the duplex mode and rate of Ethernet ports at both ends of the line.
④Switch the Rx and Tx ends of the optical jumper.

Handling of Common Faults
Symptom:
The Status indicator is on in red.
Possible Causes:
①Fan alarm
②Temperature alarm
③Power alarm
Solution:
①Check whether the fans do not run or are blocked or damaged. You
can run the show fan command to further locate the fault.
②Run the show temper command to verify the temperature. If the switch
has stopped normal service switching, check the operating
environment of the switch in time, clean the dust on the device, and
improve the cooling effect.
③Check whether the dual power supply systems run properly. You can
run the show power command to further locate the fault.

Handling of Common Faults
For details about handling of other common faults, see the Switch
Troubleshooting Guide.