you can configure duplex mode to half, full, or autonegotiate on gigabit ethernet interfaces if the speed is set to 10 or 100 mbps. you cannot configure half-duplex mode on gigabit ethernet interfaces if the interface speed is 1000 mbps.
voltages that present a shock hazard may exist on power over ethernet (poe) circuits if interconnections are made using uninsulated exposed metal contacts, conductors, or terminals. avoid using such interconnection methods, unless the exposed metal parts are located within a restricted access location and users and service people who are authorized within the restricted access location are made aware of the hazard. a restricted access area can be accessed only through the use of a special tool, lock and key or other means of security. statement 1072
to maximize performance, choose one of these methods for configuring the ethernet ports:
1 let the ports autonegotiate both speed and duplex.
2 set the port speed and duplex parameters on both ends of the connection.
you can configure the 10/100 or 10/100/1000 ports on the catalyst 3560 poe switches either to automatically provide poe when a cisco ip phone, cisco aironet access point, or end device compliant with ieee 802.3af is connected or to never to provide poe, even if an ip phone or an access point is connected. the default setting is auto. to prevent electrostatic-discharge (esd) damage, follow your normal board and component handling procedures.
follow these steps to connect to 10base-t or 100base-tx devices:
step 1 when connecting to workstations, servers, routers, and cisco ip phones, connect a straight-through cable to an rj-45 connector on the front panel. (see figure 2-18.) when connecting to switches or repeaters, use a crossover cable. (see the “cable and adapter specifications” section for cable-pinout descriptions.)
poe faults are caused when noncompliant cabling or powered devices are connected to a poe port. only standard-compliant cabling can be used to connect cisco pre-standard ip phones or wireless access points or ieee 802.3af-compliant devices to poe ports. a cable or device that causes a poe fault must be removed from the network.
you can use the mdix auto interface configuration command in the cli to enable the automatic medium-dependent interface crossover (auto-mdix) feature. when the auto-mdix feature is enabled, the switch detects the required cable type for copper ethernet connections and configures the interfaces accordingly. therefore, you can use either a crossover or a straight-through cable for connections to a copper 10/100, 10/100/1000, or 1000base-t sfp module port on the switch, regardless of the type of device on the other end of the connection.the auto-mdix feature is enabled by default on switches running cisco ios release 12.2(18)se or later. for releases between cisco ios release 12.1(14)ea1 and 12.2(18)se, the auto-mdix feature is disabled by default. for configuration information for this feature, see the switch software configuration guide or the switch command reference.
the catalyst 3560 switch can connect to a cisco ip phone through a straight-through, twisted four-pair category 5 cable. the rear panel of the cisco ip phone might have more than one rj-45 connector. use the lan-to-phone connector to connect the ip phone to the switch. see the cisco ip phone documentation for more information about connecting devices to it.
many legacy powered devices, including older cisco ip phones and access points that do not fully support ieee 802.3af, might not support poe when connected to the switches by a crossover cable.
step 2 connect the other end of the cable to an rj-45 connector on the other device. the port led turns on when both the switch and the connected device have established link.
the port led is amber while spanning tree protocol (stp) discovers the topology and searches for loops. this takes about 30 seconds, and then the port led turns green. if the port led does not turn on,the device at the other end might not be turned on, or there might be a cable problem or a problem with the adapter installed in the attached device. see chapter 3, “troubleshooting,” for solutions to cabling problems.
step 3 reconfigure and reboot the connected device, if necessary.
step 4 repeat steps 1 through 3 to connect each device.
