#Sg300 cli show interface errors Patch
#Sg300 cli show interface errors software

The two options are singlemode fiber (SMF) or multimode fiber (MMF). Always ground the cables (especially in new cable runs) to a suitable and safe earth ground before you connect them to the module.ДЇor fiber, make sure you have the correct cable for the distances involved and the type of fiber ports that are used. Warning:В Category 5e and Category 6 cables can store high levels of static electricity because of the dielectric properties of the materials used in their construction. Always use either Category 5, Category 5e, or Category 6 UTP for 10/100 or 10/100/1000Mbps connections. Category 3 copper cable can be used for 10 Mbps unshielded twisted pair (UTP) connections, but must never be used for 10/100 or 10/100/1000Mbps UTP connections.

Make sure you have the correct cable for the type of connection you are making. See the Common Port and Interface Problems section of this document for more information. The show module command can indicate faulty, which can indicate a hardware problem. Use the show port command for CatOS or the show interface command for Cisco IOS to look for errdisable, disable or shutdown status. Move the cable to a known good port to troubleshoot a suspect port or module. See the Gigabit Ethernet Troubleshooting section of this document.Д«ad Port or Module Port or Interface or Module not enabled Verify Hw and Sw support for this type of GBIC. Bypass the media convertor if possible to rule it out.Д«ad or wrong Gigabit Interface Convertor (GBIC)

#Sg300 cli show interface errors Patch

Bypass the patch panel if possible to rule it out.Д®liminate faulty media convertors: fiber-to-copper, etc. Unplug the cable and reinsert it.Д®liminate faulty patch panel connections. Sometimes a cable appears to be seated in the jack, but is not. Look for broken or missing pins on connectors.Д¬heck for loose connections. Swap suspect cable with known good cable. Refer to the Catalyst Switch Cable Guide. Make sure that both ends of the cable are plugged into the correct ports. If the link light for the port does not come on, you can consider these possibilities: Possible CauseД¬onnect cable from switch to a known good device. Check the Cable and Both Sides of the Connection

Normally you can identify this situation if the port has many packet errors, or the port constantly flaps (loses and regains link). The cable can have encountered physical stress that causes it to be functional at a marginal level. A single broken wire or one shutdown port can cause the problem where one side has a link light, but the other side does not.ДЄ link light does not guarantee that the cable is fully functional. The table describes the LED status indicators for Ethernet modules or fixed-configuration switches: PlatformД®nsure that both sides have a link. If you have physical access to the switch, it can save time to look at the port LEDs which give you the link status or can indicate an error condition (if red or orange). Physical Layer Troubleshooting Using the LEDs to Troubleshoot Refer to Cisco Technical Tips Conventions for more information on document conventions.

#Sg300 cli show interface errors software

This document is not restricted to specific software and hardware versions. There are no specific requirements for this document. This document applies to Catalyst switches that run CatOS Software on the Supervisor or Cisco IOS В® System Software on the Supervisor. This document is intended to help determine why a port or interface experiences problems.