I. Console setting errors (baud rate, flow control, and COM port) on the host.
II. Console cable damage.
III. PC system faults.
IV. Switch software faults, causing process crash.
V. Switch hardware faults (for example, faults of stacking modules or cables causing switch crash, and faults of console-based circuit).
Step 1: Check whether flow control is disabled on the terminal management software (SecureCRT or Hyper Terminal).
If the setting is incorrect, correct and saved it, exit and the restart the software. Flow control is enabled by default on the SecureCRT. Disable flow control when setting parameters.
Step 2: Check whether the COM port is correct.
Right-click My Computer and then choose Device Manager > Ports (COM & LPT).
The COM port needs to be the same as the serial port specified on the Hyper Terminal or SecureCRT.
Step 3: Change the baud rate to 57600 or 115200 to check whether the fault is rectified. The default baud rate is 9600 on the console port.
If the fault persists, go to Step 4.
Step 4: Press Ctrl+Shift+6 and then enter x to check whether the console port is recovered.
Step 5: Check whether the device can be accessed through Telnet and check with the customer about whether services are operational.
If services are operational and the device supports Telnet, run the following commands under Telnet (no risk) to identify the cause for no output on the console terminal:
=========================================================
Ruijie#debug su
Ruijie(support)#tech-support package
=========================================================
After information collection, run the clear line console 0 command to recover services. If the services are not recovered, collect information and contact Ruijie technical support.
If services are operational but the device cannot be accessed through Telnet, run the following commands to identify the cause for no output on the console terminal:
全部评论