Optional For failover-time seconds , enter how long the switch waits for the primary gateway route after the route to the backup gateway is established. Optional For keepalive seconds , enter how often the switch sends keepalive messages. For retry-count , enter the number of unanswered keepalive messages that the switch sends before the connection is terminated.
The default for each is 0. Optional For reconnect time , enter the maximum time interval that the switch waits before trying to reconnect to the event gateway. Optional For source ip-address , enter the source IP address of this device. Step 4 show cns event connections Verify information about the event agent.
Step 5 show running-config Verify your entries. Step 6 copy running-config startup-config Optional Save your entries in the configuration file. Switch config cns event You can enable the Cisco IOS agent with these commands: The cns config initial global configuration command enables the Cisco IOS agent and initiates an initial configuration on the switch.
The cns config partial global configuration command enables the Cisco IOS agent and initiates a partial configuration on the switch. You can then use the Configuration Engine to remotely send incremental configurations to the switch. Enabling an Initial Configuration Beginning in privileged EXEC mode, follow these steps to enable the CNS configuration agent and initiate an initial configuration on the switch: Command Purpose Step 1 configure terminal Enter global configuration mode.
Step 3 cli config-text Enter a command line for the CNS connect template. Step 5 exit Return to global configuration mode. Step 6 cns connect name [ retries number ] [ retry-interval seconds ] [ sleep seconds ] [ timeout seconds ] Enter CNS connect configuration mode, specify the name of the CNS connect profile, and define the profile parameters.
Enter the name of the CNS connect profile. Optional For retries number , enter the number of connection retries. The range is 1 to The default is 3. Optional For retry-interva l seconds , enter the interval between successive connection attempts to the Configuration Engine.
The range is 1 to 40 seconds. The default is 10 seconds. Optional For sleep seconds , enter the amount of time before which the first connection attempt occurs. The range is 0 to seconds. The default is 0. Optional For timeout seconds , enter the amount of time after which the connection attempts end. The range is 10 to seconds. The default is For controller controller-type , enter the controller type. For dlci , enter the active data-link connection identifiers DLCIs.
For interface [ interface-type ], enter the type of interface. For line line-type , enter the line type. Step 8 template name [ Step 10 exit Return to global configuration mode. Step 11 hostname name Enter the hostname for the switch. Step 12 ip route network-number Optional Establish a static route to the Configuration Engine whose IP address is network-number.
For interface num , enter the type of interface—for example, ethernet, group-async, loopback, or virtual-template. Optional Enter event to set the ID to be the event-id value used to identify the switch. Optional Enter image to set the ID to be the image-id value used to identify the switch.
Optional For port-number , enter the port number of the configuration server. Optional Enable event for configuration success, failure, or warning messages when the configuration is finished. Optional Enable no-persist to suppress the automatic writing to NVRAM of the configuration pulled as a result of entering the cns config initial global configuration command. If the no-persist keyword is not entered, using the cns config initial command causes the resultant configuration to be automatically written to NVRAM.
Optional For page page , enter the web page of the initial configuration. Optional Enter source ip-address to use for source IP address. Optional Enable syntax-check to check the syntax when this parameter is entered.
Step 16 show cns config connections Verify information about the configuration agent. Step 17 show running-config Verify your entries. Switch config cns template connect template-dhcp Switch config-tmpl-conn cli ip address dhcp Switch config-tmpl-conn exit Switch config cns template connect ip-route Switch config-tmpl-conn cli ip route 0. Optional Enter source ip-address to use for the source IP address.
Step 4 show cns config stats or show cns config outstanding Verify information about the configuration agent. Was this Document Helpful? Yes No Feedback. A bootstrap configuration file that includes the CNS configuration commands that enable the switch to communicate with the Configuration Engine The switch configured to use either the switch MAC address or the serial number instead of the default hostname to generate the ConfigID and EventID The CNS event agent configured to push the configuration file to the switch.
Verify information about the configuration agent. Each period means the network server timed out while waiting for a reply. Simultaneously press and release the Ctrl , Shift , and 6 keys and then press the X key. The Layer 2 traceroute feature allows the switch to identify the physical path that a packet takes from a source device to a destination device. Layer 2 traceroute supports only unicast source and destination MAC addresses. It finds the path by using the MAC address tables of the switches in the path.
When the switch detects a device in the path that does not support Layer 2 traceroute, the switch continues to send Layer 2 trace queries and lets them time out. The switch can only identify the path from the source device to the destination device. It cannot identify the path that a packet takes from source host to the source device or from the destination device to the destination host. These are the Layer 2 traceroute usage guidelines:.
If any devices in the physical path are transparent to CDP, the switch cannot identify the path through these devices. If the IP address is not resolved, the path is not identified, and an error message appears.
You can display physical path that a packet takes from a source device to a destination device by using one of these privileged EXEC commands:. For more information, see the command reference for this release. You can use IP traceroute to identify the path that packets take through the network on a hop-by-hop basis. The command output displays all network layer Layer 3 devices, such as routers, that the traffic passes through on the way to the destination. Your switches can participate as the source or destination of the traceroute privileged EXEC command and might or might not appear as a hop in the traceroute command output.
If the switch is the destination of the traceroute, it is displayed as the final destination in the traceroute output. Intermediate switches do not show up in the traceroute output if they are only bridging the packet from one port to another within the same VLAN. However, if the intermediate switch is a multilayer switch that is routing a particular packet, this switch shows up as a hop in the traceroute output.
Traceroute finds the address of the first hop by examining the source address field of the ICMP time-to-live-exceeded message. The first router decrements the TTL field by 1 and sends the datagram to the next router.
The second router sees a TTL value of 1, discards the datagram, and returns the time-to-live-exceeded message to the source.
This process continues until the TTL is incremented to a value large enough for the datagram to reach the destination host or until the maximum TTL is reached. To learn when a datagram reaches its destination, traceroute sets the UDP destination port number in the datagram to a very large value that the destination host is unlikely to be using. When a host receives a datagram destined to itself containing a destination port number that is unused locally, it sends an ICMP port-unreachable error to the source.
Because all errors except port-unreachable errors come from intermediate hops, the receipt of a port-unreachable error means that this message was sent by the destination port. Beginning in privileged EXEC mode, follow this step to trace that the path packets take through the network:.
Trace the path that packets take through the network. Note Though other protocol keywords are available with the traceroute privileged EXEC command, they are not supported in this release. This example shows how to perform a traceroute to an IP host:. The display shows the hop count, the IP address of the router, and the round-trip time in milliseconds for each of the three probes that are sent. Table Traceroute Output Display Characters.
Administratively unreachable. Usually, this output means that an access list is blocking traffic. When running TDR, a local device sends a signal through a cable and compares the reflected signal to the initial signal. It is not supported on SFP module ports. If one of the twisted-pair wires is open, TDR can find the length at which the wire is open.
Use TDR to diagnose and resolve cabling problems in these situations:. To display the results, enter the show cable-diagnostics tdr interface interface-id privileged EXEC command. For a description of the fields in the display, see the command reference for this release. These sections explains how you use debug commands to diagnose and resolve internetworking problems:. Note For complete syntax and usage information for specific debug commands, see the command reference for this release.
All debug commands are entered in privileged EXEC mode, and most debug commands take no arguments. The switch continues to generate output until you enter the no form of the command.
If you enable a debug command and no output appears, consider these possibilities:. Alternately, in privileged EXEC mode, you can enter the undebug form of the command:. To display the state of each debugging option, enter this command in privileged EXEC mode:. Beginning in privileged EXEC mode, enter this command to enable all-system diagnostics:.
The no debug all privileged EXEC command disables all diagnostic output. Using the no debug all command is a convenient way to ensure that you have not accidentally left any debug commands enabled. By default, the network server sends the output from debug commands and system error messages to the console. If you use this default, you can use a virtual terminal connection to monitor debug output instead of connecting to the console port. Possible destinations include the console, virtual terminals, internal buffer, and UNIX hosts running a syslog server.
The syslog format is compatible with 4. Note Be aware that the debugging destination you use affects system overhead. Logging messages to the console produces very high overhead, whereas logging messages to a virtual terminal produces less overhead. Logging messages to a syslog server produces even less, and logging to an internal buffer produces the least overhead of any method.
The output from the show platform forward privileged EXEC command provides some useful information about the forwarding results if a packet entering an interface is sent through the system. Depending upon the parameters entered about the packet, the output provides lookup table results and port maps used to calculate forwarding destinations, bitmaps, and egress information.
Note For more syntax and usage information for the show platform forward command, see the switch command reference for this release. Most of the information in the output from the command is useful mainly for technical support personnel, who have access to detailed information about the switch application-specific integrated circuits ASICs. However, packet forwarding information can also be helpful in troubleshooting.
This is an example of the output from the show platform forward command on port 1 in VLAN 5 when the packet entering that port is addressed to unknown MAC addresses. The packet should be flooded to all other ports in VLAN 5. It should be forwarded from the port on which the address was learned.
Because there is no default route set, the packet should be dropped. It should be forwarded as specified in the routing table. The crashinfo files save information that helps Cisco technical support representatives to debug problems that caused the Cisco IOS image to fail crash. The switch writes the crash information to the console at the time of the failure. The switch creates two types of crashinfo files:. The information in the basic file includes the Cisco IOS image name and version that failed, a list of the processor registers, and other switch-specific information.
You can provide this information to the Cisco technical support representative by using the show tech-support privileged EXEC command. Basic crashinfo files are kept in this directory on the flash file system :. Each new crashinfo file that is created uses a sequence number that is larger than any previously existing sequence number, so the file with the largest sequence number describes the most recent failure.
Version numbers are used instead of a timestamp because the switches do not include a real-time clock. You cannot change the name of the file that the system will use when it creates the file. However, after the file is created, you can use the rename privileged EXEC command to rename it, but the contents of the renamed file will not be displayed by the show tech-support privileged EXEC command. You can delete crashinfo files by using the delete privileged EXEC command.
You can display the most recent basic crashinfo file that is, the file with the highest sequence number at the end of its filename by entering the show tech-support privileged EXEC command. You also can access the file by using any command that can copy or display files, such as the more or the copy privileged EXEC command.
The switch creates the extended crashinfo file when the system is failing. The information in the extended file includes additional information that can help determine the cause of the switch failure.
You provide this information to the Cisco technical support representative by manually accessing the file and using the more or the copy privileged EXEC command.
Extended crashinfo files are kept in this directory on the flash file system :. You can configure the switch to not create the extended creashinfo file by using the no exception crashinfo global configuration command. These tables are a condensed version of troubleshooting documents on Cisco. This section lists some possible symptoms that could be caused by the CPU being too busy and shows how to verify a CPU utilization problem. Table lists the primary types of CPU utilization problems that you can identify.
Note that excessive CPU utilization might result in these symptoms, but the symptoms could also result from other causes. Note the underlined information in the first line of the output example. This example shows normal CPU utilization. Interrupt percentage value is almost as high as total CPU utilization value.
The CPU is receiving too many packets from the network. Determine the source of the network packet. Stop the flow, or change the switch configuration. This is usually triggered by an event that activated the process. Identify the unusual event, and troubleshoot the root cause.
Table lists some PoE troubleshooting scenarios. Ensure that the PoE power supply to the expansion module is connected at the time of IOS boot as it is a prerequisite for power-on-self-test POST to pass before enabling the power inline function.
Verify that PoE power supply is connected and working on the expansion module. Check show post to verify that power-on-self-test POST is passed for power controllers. Trouble is on only one switch port. PoE and non-PoE devices do not work on this port, but do on other ports. Verify that the powered device works on another PoE port. Use the show run, show interface status, or show power inline detail user EXEC commands to verify that the port is not shut down or error disabled.
Note Most switches turn off port power when the port is shut down, even though the IEEE specifications make this optional. Verify that the Ethernet cable from the powered device to the switch port is good: Connect a known good non-PoE Ethernet device to the Ethernet cable, and make sure that the powered device establishes a link and exchanges traffic with another host. Verify that the total cable length from the switch front panel to the powered device is not more than meters. Disconnect the Ethernet cable from the switch port.
Use a short Ethernet cable to connect a known good Ethernet device directly to this port on the switch front panel not on a patch panel. Next, connect a powered device to this port, and verify that it powers on.
If a powered device does not power on when connected with a patch cord to the switch port, compare the total number of connected powered devices to the switch power budget available PoE. Use the show inline power and show inline power detail commands to verify the amount of available power. Trouble is on all switch ports. Nonpowered Ethernet devices cannot establish an Ethernet link on any port, and PoE devices do not power on.
If there is a continuous, intermittent, or reoccurring alarm related to power, replace the power supply if possible it is a field-replacable unit. Otherwise, replace the switch. If the problem is on a consecutive group of ports but not all ports, the power supply is probably not defective, and the problem could be related to PoE regulators in the switch. Use the show log privileged EXEC command to review alarms or system messages that previously reported PoE conditions or status changes.
If there are no alarms, use the show interface status command to verify that the ports are not shut down or error-disabled. If ports are error-disabled, use the shut and no shut interface configuration commands to re-enable the ports. Review the running configuration to verify that power inline never is not configured on the ports.
Connect a nonpowered Ethernet device directly to a switch port. Use only a short patch cord. Do not use the existing distribution cables. Connect the other end of the cable to the console port on the switch. Start a terminal-emulation program on the PC. Configure the PC terminal emulation software for bits per second, 8 data bits, no parity, 1 stop bit, and no flow control.
Use the CLI to enter commands to configure the switch. See the software configuration guide and the command reference for more information. See the "Accessing Online Help" section for a list of supporting documents. These sections explain how to install the switch on a DIN rail or in a rack. Refer to the switch hardware guide for instructions on mounting the switch on a wall:. Obtain these necessary tools and equipment:. When you determine where to install the switch, verify that these guidelines are met:.
To prevent the switch from overheating, these must be the minimum clearances:. Note When the switch is installed in an industrial enclosure, the temperature within the enclosure is greater than normal room temperature outside the enclosure. Use a zinc-plated, yellow-chromate steel DIN rail to assure proper grounding.
The use of other materials such as aluminum, plastic, and so on that can corrode, oxidize, or are poor conductors can result in improper or intermittent grounding. Follow these steps to mount the switch on a DIN rail or in a rack. If you are mounting the switch in a rack, first secure the Cisco IE rack adapter to the rack. Insert a flat-head screwdriver in the space next to the tab, and turn the screw driver to release the latch and push it out.
If you are using a 15 mm DIN rail, rotate all feet to the extended positions. Otherwise, rotate the feet to the recessed positions. Position the rear panel of the switch directly in front of the DIN rail, making sure that the DIN rail fits in the space between the two latches.
You hear a click when the latches are completely locked. Follow these steps to connect the switch to a protective ground. Use a standard Phillips screwdriver or a ratcheting torque screwdriver with a Phillips head to remove the ground screw from the front panel of the switch. Store the ground screw for later use.
Use a wire stripping tool to strip the to gauge ground wire to 0. Insert the ground wire into the ring terminal lug, and using a crimping tool, crimp the ring terminal to the wire. Use a ratcheting torque screwdriver to tighten the ground screw and ring terminal lug to the switch front panel to 8.
Attach the other end of the ground wire to a grounded bare metal surface, such as a ground bus, a grounded DIN rail, or a grounded bare rack. Follow these steps to prepare the DC power cable.
Identify the positive and return DC power connections on the connector. Measure a strand of twisted-pair copper wire to AWG long enough to connect to the DC power source. Using an gauge wire-stripping tool, strip each of the two wires to 0. Do not strip more than 0. Stripping more than the recommended amount of wire can leave exposed wire from the connector after installation.
Insert the exposed part of the positive wire into the connection labeled V and the exposed part of the return wire into the connection labeled RT. Make sure that you cannot see any wire lead. Only wire with insulation should extend from the connector. Use a ratcheting torque flathead screwdriver to torque the power and relay connector captive screws above the installed wire leads to 2 in-lb, the maximum recommended torque.
Connect the other end of the positive wire the one connected to V to the positive terminal on the DC power source, and connect the other end of the return wire the one connected to RT to the return terminal on the DC power source.
When you are testing the switch, one power connection is sufficient. If you are installing the switch and are using a second power source, repeat Step 3 through Step 7 using a second power and relay connector.
Follow these steps to connect the DC power and relay connector to the switch:. Insert the power and relay connector into the Pwr A receptacle on the switch front panel. Use a flathead screwdriver to tighten the captive screws on the sides of the power and relay connector. Optionally, insert a second power and relay connector into the Pwr B receptacle on the switch front panel. Use a flathead screwdriver to tighten the captive screws on the sides of the second power and relay connector.
These sections describe how to connect to the switch ports, the SFP module ports, and the dual-purpose ports. Use a twisted four-pair, Category 5 cable when you connect to other switches, hubs, or repeaters. For simplified cabling, the automatic medium-dependent interface crossover auto-MDIX feature is enabled by default on the switch. With auto-MDIX enabled, the switch detects the required cable type for copper Ethernet connections and configures the interfaces accordingly.
Grasp the module on the sides, and insert it into the switch slot until you feel the connector snap into place. For a list of supported modules, see the release notes on Cisco. For detailed instructions on installing, removing, and connecting to SFP modules, see the documentation that came with the SFP module. Only one port on a dual-purpose port can be active at a time. If both ports are connected, the SFP module port has priority.
After you connect to the switch port and another device, the port LED turns amber while the switch establishes a link. This process takes about 30 seconds, and then the LED turns green when the switch and the target device have an established link. If the LED is off, the target device might not be turned on, there might be a cable problem, or there might be a problem with the adapter installed in the target device. See these sections if you have difficulty setting up your switch:.
Help with the initial switch configuration is provided here. For additional assistance, see the online documentation at Cisco.
If no, or you are not sure, restart the switch. If yes, or you are not sure, restart the switch, and repeat the Express Setup procedure. Did you start a browser session on your PC and the set-up page did not appear? If the window does not appear, enter a URL in your browser, such as Cisco. Did you have a pop-up blocker running on your PC when you connected to the switch port?
If yes, disconnect the cable from the switch port, disable the pop-up blocker, press the Express Setup button, and reconnect the cable to the blinking Ethernet port. Did you have proxy settings enabled in your browser software when you connected to the switch port? If yes, disconnect the cable from the switch port, disable the proxy settings, press the Express Setup button, and reconnect the cable to the blinking Ethernet port. Did you have a wireless client running on your PC when you connected to the switch port?
If yes, disconnect the cable from the switch port, disable the wireless client, press the Express Setup button, and reconnect the cable to the blinking Ethernet port.
Do you need to change the switch IP address after you have already completed the initial setup? For more information about changing the switch IP address, see the switch configuration guide online at Cisco. Follow these steps to return your switch to the factory default settings. These are reasons why you might want to reset the switch:. Power off the switch. Power on the switch, and at the same time, press and hold down the Express Setup button until all the system LEDs turn red.
Release the Express Setup button, and the switch continues to boot. After the switch restarts, continue to run Express Setup. First look for a solution to your problem in the troubleshooting section of the switch hardware installation guide or the switch software configuration guide on Cisco.
You can also access the Cisco Technical Support and Documentation website for a list of known hardware problems and extensive troubleshooting documentation. For more information about the switch, see these documents on Cisco.
0コメント