Cisco 2948G - Catalyst Switch Resolução de problemas de hardware - Página 6
Procurar online ou descarregar pdf Resolução de problemas de hardware para Interruptor Cisco 2948G - Catalyst Switch. Cisco 2948G - Catalyst Switch 30 páginas. End-of-sale and end-of-life announcement
Também para Cisco 2948G - Catalyst Switch: Manual de Perguntas Frequentes (7 páginas), Boletim de apoio ao produto (3 páginas)
Imprimir página
Missing Software, or an Upgrade Failure, or from ROMMON Mode for more information on
recovery.
Receiving the "Failed to allocate session block" error message
If you receive the Failed to allocate session block error message while you access the switch
on the Telnet, the problem occurs because the switch cannot allocate the required memory for the Telnet
application. The available free memory is low because of some process that uses more memory or because of
a memory leakage in the switch.
In order to avoid the error, issue the show proc mem command and verify the process that uses more memory
in the switch. In order to resolve the problem, either add more memory to the system or disable some features
in order to free some of the existing memory.
If there is memory leak in the switch, reset the switch in order to release all the process in the memory. If the
error message still appears even after you reboot, upgrade the software version of the switch.
Can not connect to a remote host, router, or another switch
Complete these steps:
1.
Verify that the port LED status is green. If the link LED is solid orange, it has been disabled by the
software. If it is blinking orange after supervisor bootup and module initialization, this is a hardware
failure. If there is no link LED, check and swap the cables. Verify operation of the end device and
NIC.
Refer to Troubleshooting Cisco Catalyst Switches to NIC Compatibility Issues for more information
on NIC troubleshooting.
2.
What type of media is involved? Fiber? Gigabit Interface Converter (GBIC)? Gigabit Ethernet?
10/100 BaseTX? If this a physical layer issue, refer to the Physical Layer Troubleshooting section of
Troubleshooting Switch Port Problems for more information.
3.
Issue the show port <mod/port> command in order to verify that the status is connected, which
means that the port is operational. If any other status is displayed, see the Port status shows not
connected, faulty, disabled, inactive, or errdisable section for troubleshooting steps.
If the end device is a Cisco router or switch, and Cisco Discovery Protocol (CDP) is enabled, issue the
show cdp neighbor detail command in order to identify the device, remote interface type, and remote
IP address.
Note: A status of connected does not mean that the ports are free of errors. If there are errors on the
ports, proceed to the Seeing errors on the ports section of this document.
4.
Swap the cables. Move the cable to a different port. Eliminate patch panels. Patch panels are a
common source of connectivity failures, so attempt to connect directly to the end device. Verify the
operation of the end device.
5.
Capture the output of the show config , show module , and show test 0 commands.
a.
Issue the show module command in order to verify that the status is ok for that module and
not disabled or faulty.
◊
If the status is disabled, issue the set module enable <mod> command.
◊
If the status is faulty, establish a console connection to capture bootup Power On Self
Test (POST) diagnostics and any system error messages. Issue the reset <mod>
command in order to reset the module. Issue the show test 0 command in order to
determine if this module passed all of it's diagnostic tests on bootup.