Trunks are required to carry VLAN traffic from one switch to another. In this lesson I will demonstrate how to configure a trunk between Cisco Catalyst switches. Let me show you the topology that we’ll use:  Above you see a topology with a computer connected to each switch. We’ll put the computers in the same VLAN and create a trunk between the two switches.
In the show vlan mtu command output, the MTU_Mismatch column shows whether all the ports in the VLAN have the same MTU. When yes appears in the column, it means that the VLAN has ports with different MTUs, and packets that are switched from a port with a larger MTU to a port with a smaller MTU might be dropped. If the VLAN does not have an SVI, the hyphen (-) symbol appears in the SVI_MTU column. If the MTU-Mismatch column displays yes, the names of the ports with the MinMTU and the MaxMTU appear. If you try to associate a private VLAN secondary VLAN with a primary VLAN before you define the secondary VLAN, the secondary VLAN is not included in the show vlan private-vlan command output. In the show vlan private-vlan type command output, a type displayed as normal means a VLAN that has a private VLAN association but is not part of the private VLAN. For example, if you define and associate two VLANs as primary and secondary VLANs and then delete the secondary VLAN configuration without removing the association from the primary VLAN, the VLAN that was the secondary VLAN is shown as normal in the display. In the show vlan private-vlan output, the primary and secondary VLAN pair is shown as nonoperational. This is an example of output from the show vlan command. See the table that follows for descriptions of the fields in the display. Field Description VLAN VLAN number. Name Name, if configured, of the VLAN. Status Status of the VLAN (active or suspend). Ports Ports that belong to the VLAN. Type Media type of the VLAN. SAID Security association ID value for the VLAN. MTU Maximum transmission unit size for the VLAN. Parent Parent VLAN, if one exists. RingNo Ring number for the VLAN, if applicable. BrdgNo Bridge number for the VLAN, if applicable. Stp Spanning Tree Protocol type used on the VLAN. BrdgMode Bridging mode for this VLAN—possible values are source-route bridging (SRB) and source-route transparent (SRT); the default is SRB. Trans1 Translation bridge 1. Trans2 Translation bridge 2. Remote SPAN VLANs Identifies any RSPAN VLANs that have been configured. Primary/Secondary/Type/Ports Includes any private VLANs that have been configured, including the primary VLAN ID, the secondary VLAN ID, the type of secondary VLAN (community or isolated), and the ports that belong to it. This is an example of output from the show vlan dot1q tag native command: This is an example of output from the show vlan private-vlan command: This is an example of output from the show vlan private-vlan type command: This is an example of output from the show vlan summary command: This is an example of output from the show vlan id command: Page 2To display the software information of Layer 2 VPN (L2VPN), use the show platform software l2vpn switch command. show platform software fed switch {switch number | active | standby} {F0 | F1 | R0 | R1 | RP | {active | standby}} {atom | disposition | imposition | internal} The following is a sample output of the show platform software l2vpn switch command: Page 3Use this command to configure the QoS appropriate for VoIP traffic within the QoS domain. The QoS domain includes the device, the network interior, and edge devices that can classify incoming traffic for QoS. Auto-QoS configures the device for VoIP with Cisco IP phones on device and routed ports and for devices running the Cisco SoftPhone application. These releases support only Cisco IP SoftPhone Version 1.3(3) or later. Connected devices must use Cisco Call Manager Version 4 or later. To take advantage of the auto-QoS defaults, you should enable auto-QoS before you configure other QoS commands. You can fine-tune the auto-QoS configuration after you enable auto-QoS. The device applies the auto-QoS-generated commands as if the commands were entered from the command-line interface (CLI). An existing user configuration can cause the application of the generated commands to fail or to be overridden by the generated commands. These actions occur without warning. If all the generated commands are successfully applied, any user-entered configuration that was not overridden remains in the running configuration. Any user-entered configuration that was overridden can be retrieved by reloading the device without saving the current configuration to memory. If the generated commands fail to be applied, the previous running configuration is restored. If this is the first port on which you have enabled auto-QoS, the auto-QoS-generated global configuration commands are executed followed by the interface configuration commands. If you enable auto-QoS on another port, only the auto-QoS-generated interface configuration commands for that port are executed. When you enter the auto qos voip cisco-phone interface configuration command on a port at the edge of the network that is connected to a Cisco IP phone, the device enables the trusted boundary feature. The device uses the Cisco Discovery Protocol (CDP) to detect the presence of a Cisco IP phone. When a Cisco IP phone is detected, the ingress classification on the port is set to trust the QoS label received in the packet. The device also uses policing to determine whether a packet is in or out of profile and to specify the action on the packet. If the packet does not have a DSCP value of 24, 26, or 46 or is out of profile, the device changes the DSCP value to 0. When a Cisco IP phone is absent, the ingress classification is set to not trust the QoS label in the packet. The policing is applied to those traffic matching the policy-map classification before the device enables the trust boundary feature. You can enable auto-QoS on static, dynamic-access, and voice VLAN access, and trunk ports. When enabling auto-QoS with a Cisco IP phone on a routed port, you must assign a static IP address to the IP phone. When a device running Cisco SoftPhone is connected to a device or routed port, the device supports only one Cisco SoftPhone application per port. After auto-QoS is enabled, do not modify a policy map or aggregate policer that includes AutoQoS in its name. If you need to modify the policy map or aggregate policer, make a copy of it, and change the copied policy map or policer. To use the new policy map instead of the generated one, remove the generated policy map from the interface, and apply the new policy map. To display the QoS configuration that is automatically generated when auto-QoS is enabled, enable debugging before you enable auto-QoS. Use the debug auto qos privileged EXEC command to enable auto-QoS debugging. The following policy maps and class maps are created and applied when running the auto qos voip trust command: AutoQos-4.0-Trust-Cos-Input-Policy AutoQos-4.0-Output-Policy class-default (match-any) AutoQos-4.0-Output-Priority-Queue (match-any) AutoQos-4.0-Output-Control-Mgmt-Queue (match-any) AutoQos-4.0-Output-Multimedia-Conf-Queue (match-any) AutoQos-4.0-Output-Trans-Data-Queue (match-any) AutoQos-4.0-Output-Bulk-Data-Queue (match-any) AutoQos-4.0-Output-Scavenger-Queue (match-any) AutoQos-4.0-Output-Multimedia-Strm-Queue (match-any) The following policy maps and class maps are created and applied when running the auto qos voip cisco-softphone command: AutoQos-4.0-CiscoSoftPhone-Input-Policy AutoQos-4.0-Output-Policy AutoQos-4.0-Voip-Data-Class (match-any) AutoQos-4.0-Voip-Signal-Class (match-any) AutoQos-4.0-Multimedia-Conf-Class (match-any) AutoQos-4.0-Bulk-Data-Class (match-any) AutoQos-4.0-Transaction-Class (match-any) AutoQos-4.0-Scavanger-Class (match-any) AutoQos-4.0-Signaling-Class (match-any) AutoQos-4.0-Default-Class (match-any) class-default (match-any) AutoQos-4.0-Output-Priority-Queue (match-any) AutoQos-4.0-Output-Control-Mgmt-Queue (match-any) AutoQos-4.0-Output-Multimedia-Conf-Queue (match-any) AutoQos-4.0-Output-Trans-Data-Queue (match-any) AutoQos-4.0-Output-Bulk-Data-Queue (match-any) AutoQos-4.0-Output-Scavenger-Queue (match-any) AutoQos-4.0-Output-Multimedia-Strm-Queue (match-any) The following policy maps and class maps are created and applied when running the auto qos voip cisco-phone command: service-policy input AutoQos-4.0-CiscoPhone-Input-Policy service-policy output AutoQos-4.0-Output-Policy class AutoQos-4.0-Voip-Data-CiscoPhone-Class class AutoQos-4.0-Voip-Signal-CiscoPhone-Class class AutoQos-4.0-Default-Class To disable auto-QoS on a port, use the no auto qos voip interface configuration command. Only the auto-QoS-generated interface configuration commands for this port are removed. If this is the last port on which auto-QoS is enabled and you enter the no auto qos voip command, auto-QoS is considered disabled even though the auto-QoS-generated global configuration commands remain (to avoid disrupting traffic on other ports affected by the global configuration). The device configures egress queues on the port according to the settings in this table. Egress Queue Queue Number CoS-to-Queue Map Queue Weight (Bandwidth) Queue (Buffer) Size for Gigabit-Capable Ports Queue (Buffer) Size for 10/100 Ethernet Ports Priority (shaped) 1 4, 5 Up to 100 percent 25 percent 15 percent SRR shared 2 2, 3, 6, 7 10 percent 25 percent 25 percent SRR shared 3 0 60 percent 25 percent 40 percent SRR shared 4 1 20 percent 25 percent 20 percent The following is an example of the auto qos voip trust command and the applied policies and class maps: The following is an example of the auto qos voip cisco-phone command and the applied policies and class maps: The following is an example of the auto qos voip cisco-softphone command and the applied policies and class maps: You can verify your settings by entering the show auto qos interface interface-id privileged EXEC command. Page 4The following is sample output from the show tech-support identity command: Device# show tech-support identity mac 0000.0001.0003 interface gigabitethernet1/0/1 . . . ------------------ show platform software peer forwarding-manager R0 ------------------ IOSD Connection Information: MQIPC (reader) Connection State: Connected, Read-selected Connections: 1, Failures: 22 3897 packet received (0 dropped), 466929 bytes Read attempts: 2352, Yields: 0 BIPC Connection state: Connected, Ready Accepted: 1, Rejected: 0, Closed: 0, Backpressures: 0 36 packets sent, 2808 bytes SMD Connection Information: MQIPC (reader) Connection State: Connected, Read-selected Connections: 1, Failures: 30 0 packet received (0 dropped), 0 bytes Read attempts: 1, Yields: 0 MQIPC (writer) Connection State: Connected, Ready Connections: 1, Failures: 0, Backpressures: 0 0 packet sent, 0 bytes FP Peers Information: Slot: 0 Peer state: connected OM ID: 0, Download attempts: 638 Complete: 638, Yields: 0, Spurious: 0 IPC Back-Pressure: 0, IPC-Log Back-Pressure: 0 Back-Pressure asserted for IPC: 0, IPC-Log: 1 Number of FP FMAN peer connection expected: 7 Number of FP FMAN online msg received: 1 IPC state: unknown Config IPC Context: State: Connected, Read-selected BIPC Handle: 0xdf3d48e8, BIPC FD: 36, Peer Context: 0xdf3e7158 Tx Packets: 688, Messages: 2392, ACKs: 36 Rx Packets: 37, Bytes: 2068 IPC Log: Peer name: fman-log-bay0-peer0 Flags: Recovery-Complete Send Seq: 36, Recv Seq: 36, Msgs Sent: 0, Msgs Recovered: 0 Upstream FMRP IPC Context: State: Connected, Read-selected BIPC Handle: 0xdf3e7308, BIPC FD: 37, Peer Context: 0xdf3e7158 TX Packets: 0, Bytes: 0, Drops: 0 Rx Packets: 0, Bytes: 0 Upstream FMRP-IOSd IPC Context: State: Connected, Read-selected BIPC Handle: 0xdf3f9c38, BIPC FD: 38, Peer Context: 0xdf3e7158 TX Packets: 0, Bytes: 0, Drops: 0 Rx Packets: 37, Bytes: 2864 Rx ACK Requests: 1, Tx ACK Responses: 1 Upstream FMRP-SMD IPC Context: State: Connected, Read-selected BIPC Handle: 0xdf40c568, BIPC FD: 39, Peer Context: 0xdf3e7158 TX Packets: 0, Bytes: 0, Drops: 0 Rx Packets: 0, Bytes: 0 Rx ACK Requests: 0, Tx ACK Responses: 0 Upstream FMRP-WNCD_0 IPC Context: State: Connected BIPC Handle: 0xdf4317c8, BIPC FD: 41, Peer Context: 0xdf3e7158 TX Packets: 0, Bytes: 0, Drops: 0 Rx Packets: 0, Bytes: 0 Rx ACK Requests: 0, Tx ACK Responses: 0 Upstream FMRP-WNCMGRD IPC Context: State: Connected BIPC Handle: 0xdf41ee98, BIPC FD: 40, Peer Context: 0xdf3e7158 TX Packets: 0, Bytes: 0, Drops: 0 Rx Packets: 0, Bytes: 0 Rx ACK Requests: 0, Tx ACK Responses: 0 Upstream FMRP-MOBILITYD IPC Context: State: Connected BIPC Handle: 0xdf4440f8, BIPC FD: 42, Peer Context: 0xdf3e7158 TX Packets: 0, Bytes: 0, Drops: 0 Rx Packets: 0, Bytes: 0 Rx ACK Requests: 0, Tx ACK Responses: 0 Slot: 1 Peer state: connected OM ID: 1, Download attempts: 1 Complete: 1, Yields: 0, Spurious: 0 IPC Back-Pressure: 0, IPC-Log Back-Pressure: 0 Back-Pressure asserted for IPC: 0, IPC-Log: 0 Number of FP FMAN peer connection expected: 7 Number of FP FMAN online msg received: 1 IPC state: unknown Config IPC Context: State: Connected, Read-selected BIPC Handle: 0xdf45e4d8, BIPC FD: 48, Peer Context: 0xdf470e18 Tx Packets: 20, Messages: 704, ACKs: 1 Rx Packets: 2, Bytes: 108 IPC Log: Peer name: fman-log-bay0-peer1 Flags: Recovery-Complete Send Seq: 1, Recv Seq: 1, Msgs Sent: 0, Msgs Recovered: 0 Upstream FMRP IPC Context: State: Connected, Read-selected BIPC Handle: 0xdf470fc8, BIPC FD: 49, Peer Context: 0xdf470e18 TX Packets: 0, Bytes: 0, Drops: 0 Rx Packets: 0, Bytes: 0 Upstream FMRP-IOSd IPC Context: State: Connected, Read-selected BIPC Handle: 0xdf4838f8, BIPC FD: 50, Peer Context: 0xdf470e18 TX Packets: 0, Bytes: 0, Drops: 0 Rx Packets: 0, Bytes: 0 Rx ACK Requests: 0, Tx ACK Responses: 0 Upstream FMRP-SMD IPC Context: State: Connected, Read-selected BIPC Handle: 0xdf496228, BIPC FD: 51, Peer Context: 0xdf470e18 TX Packets: 0, Bytes: 0, Drops: 0 Rx Packets: 0, Bytes: 0 Rx ACK Requests: 0, Tx ACK Responses: 0 Upstream FMRP-WNCD_0 IPC Context: State: Connected BIPC Handle: 0xdf4bb488, BIPC FD: 53, Peer Context: 0xdf470e18 TX Packets: 0, Bytes: 0, Drops: 0 Rx Packets: 0, Bytes: 0 Rx ACK Requests: 0, Tx ACK Responses: 0 Upstream FMRP-WNCMGRD IPC Context: State: Connected BIPC Handle: 0xdf4a8b58, BIPC FD: 52, Peer Context: 0xdf470e18 TX Packets: 0, Bytes: 0, Drops: 0 Rx Packets: 0, Bytes: 0 Rx ACK Requests: 0, Tx ACK Responses: 0 Upstream FMRP-MOBILITYD IPC Context: State: Connected BIPC Handle: 0xdf4cddb8, BIPC FD: 54, Peer Context: 0xdf470e18 TX Packets: 0, Bytes: 0, Drops: 0 Rx Packets: 0, Bytes: 0 Rx ACK Requests: 0, Tx ACK Responses: 0 ------------------ show platform software peer forwarding-manager R0 ------------------ IOSD Connection Information: MQIPC (reader) Connection State: Connected, Read-selected Connections: 1, Failures: 22 3897 packet received (0 dropped), 466929 bytes Read attempts: 2352, Yields: 0 BIPC Connection state: Connected, Ready Accepted: 1, Rejected: 0, Closed: 0, Backpressures: 0 36 packets sent, 2808 bytes SMD Connection Information: MQIPC (reader) Connection State: Connected, Read-selected Connections: 1, Failures: 30 0 packet received (0 dropped), 0 bytes Read attempts: 1, Yields: 0 MQIPC (writer) Connection State: Connected, Ready Connections: 1, Failures: 0, Backpressures: 0 0 packet sent, 0 bytes FP Peers Information: Slot: 0 Peer state: connected OM ID: 0, Download attempts: 638 Complete: 638, Yields: 0, Spurious: 0 IPC Back-Pressure: 0, IPC-Log Back-Pressure: 0 Back-Pressure asserted for IPC: 0, IPC-Log: 1 Number of FP FMAN peer connection expected: 7 Number of FP FMAN online msg received: 1 IPC state: unknown Config IPC Context: State: Connected, Read-selected BIPC Handle: 0xdf3d48e8, BIPC FD: 36, Peer Context: 0xdf3e7158 Tx Packets: 688, Messages: 2392, ACKs: 36 Rx Packets: 37, Bytes: 2068 IPC Log: Peer name: fman-log-bay0-peer0 Flags: Recovery-Complete Send Seq: 36, Recv Seq: 36, Msgs Sent: 0, Msgs Recovered: 0 Upstream FMRP IPC Context: State: Connected, Read-selected BIPC Handle: 0xdf3e7308, BIPC FD: 37, Peer Context: 0xdf3e7158 TX Packets: 0, Bytes: 0, Drops: 0 Rx Packets: 0, Bytes: 0 Upstream FMRP-IOSd IPC Context: State: Connected, Read-selected BIPC Handle: 0xdf3f9c38, BIPC FD: 38, Peer Context: 0xdf3e7158 TX Packets: 0, Bytes: 0, Drops: 0 Rx Packets: 37, Bytes: 2864 Rx ACK Requests: 1, Tx ACK Responses: 1 Upstream FMRP-SMD IPC Context: State: Connected, Read-selected BIPC Handle: 0xdf40c568, BIPC FD: 39, Peer Context: 0xdf3e7158 TX Packets: 0, Bytes: 0, Drops: 0 Rx Packets: 0, Bytes: 0 Rx ACK Requests: 0, Tx ACK Responses: 0 Upstream FMRP-WNCD_0 IPC Context: State: Connected BIPC Handle: 0xdf4317c8, BIPC FD: 41, Peer Context: 0xdf3e7158 TX Packets: 0, Bytes: 0, Drops: 0 Rx Packets: 0, Bytes: 0 Rx ACK Requests: 0, Tx ACK Responses: 0 Upstream FMRP-WNCMGRD IPC Context: State: Connected BIPC Handle: 0xdf41ee98, BIPC FD: 40, Peer Context: 0xdf3e7158 TX Packets: 0, Bytes: 0, Drops: 0 Rx Packets: 0, Bytes: 0 Rx ACK Requests: 0, Tx ACK Responses: 0 Upstream FMRP-MOBILITYD IPC Context: State: Connected BIPC Handle: 0xdf4440f8, BIPC FD: 42, Peer Context: 0xdf3e7158 TX Packets: 0, Bytes: 0, Drops: 0 Rx Packets: 0, Bytes: 0 Rx ACK Requests: 0, Tx ACK Responses: 0 Slot: 1 Peer state: connected OM ID: 1, Download attempts: 1 Complete: 1, Yields: 0, Spurious: 0 IPC Back-Pressure: 0, IPC-Log Back-Pressure: 0 Back-Pressure asserted for IPC: 0, IPC-Log: 0 Number of FP FMAN peer connection expected: 7 Number of FP FMAN online msg received: 1 IPC state: unknown Config IPC Context: State: Connected, Read-selected BIPC Handle: 0xdf45e4d8, BIPC FD: 48, Peer Context: 0xdf470e18 Tx Packets: 20, Messages: 704, ACKs: 1 Rx Packets: 2, Bytes: 108 IPC Log: Peer name: fman-log-bay0-peer1 Flags: Recovery-Complete Send Seq: 1, Recv Seq: 1, Msgs Sent: 0, Msgs Recovered: 0 Upstream FMRP IPC Context: State: Connected, Read-selected BIPC Handle: 0xdf470fc8, BIPC FD: 49, Peer Context: 0xdf470e18 TX Packets: 0, Bytes: 0, Drops: 0 Rx Packets: 0, Bytes: 0 Upstream FMRP-IOSd IPC Context: State: Connected, Read-selected BIPC Handle: 0xdf4838f8, BIPC FD: 50, Peer Context: 0xdf470e18 TX Packets: 0, Bytes: 0, Drops: 0 Rx Packets: 0, Bytes: 0 Rx ACK Requests: 0, Tx ACK Responses: 0 Upstream FMRP-SMD IPC Context: State: Connected, Read-selected BIPC Handle: 0xdf496228, BIPC FD: 51, Peer Context: 0xdf470e18 TX Packets: 0, Bytes: 0, Drops: 0 Rx Packets: 0, Bytes: 0 Rx ACK Requests: 0, Tx ACK Responses: 0 Upstream FMRP-WNCD_0 IPC Context: State: Connected BIPC Handle: 0xdf4bb488, BIPC FD: 53, Peer Context: 0xdf470e18 TX Packets: 0, Bytes: 0, Drops: 0 Rx Packets: 0, Bytes: 0 Rx ACK Requests: 0, Tx ACK Responses: 0 Upstream FMRP-WNCMGRD IPC Context: State: Connected BIPC Handle: 0xdf4a8b58, BIPC FD: 52, Peer Context: 0xdf470e18 TX Packets: 0, Bytes: 0, Drops: 0 Rx Packets: 0, Bytes: 0 Rx ACK Requests: 0, Tx ACK Responses: 0 Upstream FMRP-MOBILITYD IPC Context: State: Connected BIPC Handle: 0xdf4cddb8, BIPC FD: 54, Peer Context: 0xdf470e18 TX Packets: 0, Bytes: 0, Drops: 0 Rx Packets: 0, Bytes: 0 Rx ACK Requests: 0, Tx ACK Responses: 0 ------------------ show platform software VP R0 summary ------------------ Forwarding Manager Vlan Port Information Vlan Intf-ID Stp-state --------------------------------------------------------------------------- 1 7 Forwarding 1 9 Forwarding 1 17 Forwarding 1 27 Forwarding 1 28 Forwarding 1 29 Forwarding 1 30 Forwarding 1 31 Forwarding 1 40 Forwarding 1 41 Forwarding Forwarding Manager Vlan Port Information Vlan Intf-ID Stp-state --------------------------------------------------------------------------- 1 49 Forwarding 1 51 Forwarding 1 63 Forwarding 1 72 Forwarding 1 73 Forwarding 1 74 Forwarding ------------------ show platform software VP R0 summary ------------------ Forwarding Manager Vlan Port Information Vlan Intf-ID Stp-state --------------------------------------------------------------------------- 1 7 Forwarding 1 9 Forwarding 1 17 Forwarding 1 27 Forwarding 1 28 Forwarding 1 29 Forwarding 1 30 Forwarding 1 31 Forwarding 1 40 Forwarding 1 41 Forwarding Forwarding Manager Vlan Port Information Vlan Intf-ID Stp-state --------------------------------------------------------------------------- 1 49 Forwarding 1 51 Forwarding 1 63 Forwarding 1 72 Forwarding 1 73 Forwarding 1 74 Forwarding . . .Page 5To assign an Ethernet port to an EtherChannel group, or to enable an EtherChannel mode, or both, use the channel-group command in interface configuration mode. To remove an Ethernet port from an EtherChannel group, use the no form of this command. For Layer 2 EtherChannels, the channel-group command automatically creates the port-channel interface when the channel group gets its first physical port. You do not have to use the interface port-channel command in global configuration mode to manually create a port-channel interface. If you create the port-channel interface first, the channel-group-number can be the same as the port-channel-number , or you can use a new number. If you use a new number, the channel-group command dynamically creates a new port channel. Although it is not necessary to disable the IP address that is assigned to a physical port that is part of a channel group, we strongly recommend that you do so. You create Layer 3 port channels by using the interface port-channel command followed by the no switchport interface configuration command. Manually configure the port-channel logical interface before putting the interface into the channel group. After you configure an EtherChannel, configuration changes that you make on the port-channel interface apply to all the physical ports assigned to the port-channel interface. Configuration changes applied to the physical port affect only the port where you apply the configuration. To change the parameters of all ports in an EtherChannel, apply configuration commands to the port-channel interface, for example, spanning-tree commands or commands to configure a Layer 2 EtherChannel as a trunk. Active mode places a port into a negotiating state in which the port initiates negotiations with other ports by sending LACP packets. A channel is formed with another port group in either the active or passive mode. Auto mode places a port into a passive negotiating state in which the port responds to PAgP packets it receives but does not start PAgP packet negotiation. A channel is formed only with another port group in desirable mode. When auto is enabled, silent operation is the default. Desirable mode places a port into an active negotiating state in which the port starts negotiations with other ports by sending PAgP packets. An EtherChannel is formed with another port group that is in the desirable or auto mode. When desirable is enabled, silent operation is the default. If you do not specify non-silent with the auto or desirable mode, silent is assumed. The silent mode is used when the switch is connected to a device that is not PAgP-capable and rarely, if ever, sends packets. An example of a silent partner is a file server or a packet analyzer that is not generating traffic. In this case, running PAgP on a physical port prevents that port from ever becoming operational. However, it allows PAgP to operate, to attach the port to a channel group, and to use the port for transmission. Both ends of the link cannot be set to silent. In on mode, a usable EtherChannel exists only when both connected port groups are in the on mode.
Passive mode places a port into a negotiating state in which the port responds to received LACP packets but does not initiate LACP packet negotiation. A channel is formed only with another port group in active mode. Do not configure an EtherChannel in both the PAgP and LACP modes. EtherChannel groups running PAgP and LACP can coexist on the same switch or on different switches in the stack (but not in a cross-stack configuration). Individual EtherChannel groups can run either PAgP or LACP, but they cannot interoperate. If you set the protocol by using the channel-protocol interface configuration command, the setting is not overridden by the channel-group interface configuration command. Do not configure a port that is an active or a not-yet-active member of an EtherChannel as an IEEE 802.1x port. If you try to enable IEEE 802.1x authentication on an EtherChannel port, an error message appears, and IEEE 802.1x authentication is not enabled. Do not configure a secure port as part of an EtherChannel or configure an EtherChannel port as a secure port. For a complete list of configuration guidelines, see the “Configuring EtherChannels” chapter in the software configuration guide for this release.
This example shows how to configure an EtherChannel on a single switch in the stack. It assigns two static-access ports in VLAN 10 to channel 5 with the PAgP mode desirable: Device# configure terminal Device(config)# interface range GigabitEthernet 2/0/1 - 2 Device(config-if-range)# switchport mode access Device(config-if-range)# switchport access vlan 10 Device(config-if-range)# channel-group 5 mode desirable Device(config-if-range)# endThis example shows how to configure an EtherChannel on a single switch in the stack. It assigns two static-access ports in VLAN 10 to channel 5 with the LACP mode active: Device# configure terminal Device(config)# interface range GigabitEthernet 2/0/1 - 2 Device(config-if-range)# switchport mode access Device(config-if-range)# switchport access vlan 10 Device(config-if-range)# channel-group 5 mode active Device(config-if-range)# endThis example shows how to configure a cross-stack EtherChannel in a switch stack. It uses LACP passive mode and assigns two ports on stack member 2 and one port on stack member 3 as static-access ports in VLAN 10 to channel 5: Device# configure terminal Device(config)# interface range GigabitEthernet 2/0/4 - 5 Device(config-if-range)# switchport mode access Device(config-if-range)# switchport access vlan 10 Device(config-if-range)# channel-group 5 mode passive Device(config-if-range)# exit Device(config)# interface GigabitEthernet 3/0/3 Device(config-if)# switchport mode access Device(config-if)# switchport access vlan 10 Device(config-if)# channel-group 5 mode passive Device(config-if)# exitYou can verify your settings by entering the show running-config privileged EXEC command. Page 6To display entries in the Border Gateway Protocol (BGP) routing table, use the show ip bgp command in user EXEC or privileged EXEC mode. show ip bgp [ip-address [mask [longer-prefixes [injected] | shorter-prefixes [length] | best-path-reason | bestpath | multipaths | subnets] | best-path-reason | bestpath | internal | multipaths] | all | oer-paths | prefix-list name | pending-prefixes | route-map name | version {version-number | recent offset-value}]
User EXEC (>) Privileged EXEC (#)
The show ip bgp command is used to display the contents of the BGP routing table. The output can be filtered to display entries for a specific prefix, prefix length, and prefixes injected through a prefix list, route map, or conditional advertisement. When changes are made to the network address, the network version number is incremented. Use the version keyword to view a specific network version. The following sample output displays the BGP routing table: Device#show ip bgp BGP table version is 6, local router ID is 10.0.96.2 Status codes: s suppressed, d damped, h history, * valid, > best, i - internal, r RIB-failure, S Stale, m multipath, b backup-path, x best-external, f RT-Filter, a additional-path Origin codes: i - IGP, e - EGP, ? - incomplete RPKI validation codes: V valid, I invalid, N Not found Network Next Hop Metric LocPrf Weight Path N* 10.0.0.1 10.0.0.3 0 0 3 ? N*> 10.0.3.5 0 0 4 ? Nr 10.0.0.0/8 10.0.0.3 0 0 3 ? Nr> 10.0.3.5 0 0 4 ? Nr> 10.0.0.0/24 10.0.0.3 0 0 3 ? V*> 10.0.2.0/24 0.0.0.0 0 32768 i Vr> 10.0.3.0/24 10.0.3.5 0 0 4 ?The table below describes the significant fields shown in the display.
The following sample output shows the BGP routing table with 4-byte autonomous system numbers, 65536 and 65550, shown under the Path field. This example requires Cisco IOS Release 12.0(32)SY8, 12.0(33)S3, 12.2(33)SRE, 12.2(33)XNE, 12.2(33)SXI1, Cisco IOS XE Release 2.4, or a later release. Device#show ip bgp BGP table version is 4, local router ID is 172.16.1.99 Status codes: s suppressed, d damped, h history, * valid, > best, i - internal, r RIB-failure, S Stale Origin codes: i - IGP, e - EGP, ? - incomplete Network Next Hop Metric LocPrf Weight Path *> 10.1.1.0/24 192.168.1.2 0 0 65536 i *> 10.2.2.0/24 192.168.3.2 0 0 65550 i *> 172.16.1.0/24 0.0.0.0 0 32768 iThe following sample output displays information about the 192.168.1.0 entry in the BGP routing table: Device#show ip bgp 192.168.1.0 BGP routing table entry for 192.168.1.0/24, version 22 Paths: (2 available, best #2, table default) Additional-path Advertised to update-groups: 3 10 10 192.168.3.2 from 172.16.1.2 (10.2.2.2) Origin IGP, metric 0, localpref 100, valid, internal, backup/repair 10 10 192.168.1.2 from 192.168.1.2 (10.3.3.3) Origin IGP, localpref 100, valid, external, best , recursive-via-connectedThe following sample output displays information about the 10.3.3.3 255.255.255.255 entry in the BGP routing table: Device#show ip bgp 10.3.3.3 255.255.255.255 BGP routing table entry for 10.3.3.3/32, version 35 Paths: (3 available, best #2, table default) Multipath: eBGP Flag: 0x860 Advertised to update-groups: 1 200 10.71.8.165 from 10.71.8.165 (192.168.0.102) Origin incomplete, localpref 100, valid, external, backup/repair Only allowed to recurse through connected route 200 10.71.11.165 from 10.71.11.165 (192.168.0.102) Origin incomplete, localpref 100, weight 100, valid, external, best Only allowed to recurse through connected route 200 10.71.10.165 from 10.71.10.165 (192.168.0.104) Origin incomplete, localpref 100, valid, external, Only allowed to recurse through connected routeThe table below describes the significant fields shown in the display.
The following is sample output from the show ip bgp command entered with the all keyword. Information about all configured address families is displayed. Device#show ip bgp all For address family: IPv4 Unicast ***** BGP table version is 27, local router ID is 10.1.1.1 Status codes: s suppressed, d damped, h history, * valid, > best, i - internal, r RIB-failure Origin codes: i - IGP, e - EGP, ? - incomplete Network Next Hop Metric LocPrf Weight Path *> 10.1.1.0/24 0.0.0.0 0 32768 ? *> 10.13.13.0/24 0.0.0.0 0 32768 ? *> 10.15.15.0/24 0.0.0.0 0 32768 ? *>i10.18.18.0/24 172.16.14.105 1388 91351 0 100 e *>i10.100.0.0/16 172.16.14.107 262 272 0 1 2 3 i *>i10.100.0.0/16 172.16.14.105 1388 91351 0 100 e *>i10.101.0.0/16 172.16.14.105 1388 91351 0 100 e *>i10.103.0.0/16 172.16.14.101 1388 173 173 100 e *>i10.104.0.0/16 172.16.14.101 1388 173 173 100 e *>i10.100.0.0/16 172.16.14.106 2219 20889 0 53285 33299 51178 47751 e *>i10.101.0.0/16 172.16.14.106 2219 20889 0 53285 33299 51178 47751 e * 10.100.0.0/16 172.16.14.109 2309 0 200 300 e *> 172.16.14.108 1388 0 100 e * 10.101.0.0/16 172.16.14.109 2309 0 200 300 e *> 172.16.14.108 1388 0 100 e *> 10.102.0.0/16 172.16.14.108 1388 0 100 e *> 172.16.14.0/24 0.0.0.0 0 32768 ? *> 192.168.5.0 0.0.0.0 0 32768 ? *> 10.80.0.0/16 172.16.14.108 1388 0 50 e *> 10.80.0.0/16 172.16.14.108 1388 0 50 e For address family: VPNv4 Unicast ***** BGP table version is 21, local router ID is 10.1.1.1 Status codes: s suppressed, d damped, h history, * valid, > best, i - internal, r RIB-failure Origin codes: i - IGP, e - EGP, ? - incomplete Network Next Hop Metric LocPrf Weight Path Route Distinguisher: 1:1 (default for vrf vpn1) *> 10.1.1.0/24 192.168.4.3 1622 0 100 53285 33299 51178 {27016,57039,16690} e *> 10.1.2.0/24 192.168.4.3 1622 0 100 53285 33299 51178 {27016,57039,16690} e *> 10.1.3.0/24 192.168.4.3 1622 0 100 53285 33299 51178 {27016,57039,16690} e *> 10.1.4.0/24 192.168.4.3 1622 0 100 53285 33299 51178 {27016,57039,16690} e *> 10.1.5.0/24 192.168.4.3 1622 0 100 53285 33299 51178 {27016,57039,16690} e *>i172.17.1.0/24 10.3.3.3 10 30 0 53285 33299 51178 47751 ? *>i172.17.2.0/24 10.3.3.3 10 30 0 53285 33299 51178 47751 ? *>i172.17.3.0/24 10.3.3.3 10 30 0 53285 33299 51178 47751 ? *>i172.17.4.0/24 10.3.3.3 10 30 0 53285 33299 51178 47751 ? *>i172.17.5.0/24 10.3.3.3 10 30 0 53285 33299 51178 47751 ? For address family: IPv4 Multicast ***** BGP table version is 11, local router ID is 10.1.1.1 Status codes: s suppressed, d damped, h history, * valid, > best, i - internal, r RIB-failure Origin codes: i - IGP, e - EGP, ? - incomplete Network Next Hop Metric LocPrf Weight Path *> 10.40.40.0/26 172.16.14.110 2219 0 21 22 {51178,47751,27016} e * 10.1.1.1 1622 0 15 20 1 {2} e *> 10.40.40.64/26 172.16.14.110 2219 0 21 22 {51178,47751,27016} e * 10.1.1.1 1622 0 15 20 1 {2} e *> 10.40.40.128/26 172.16.14.110 2219 0 21 22 {51178,47751,27016} e * 10.1.1.1 2563 0 15 20 1 {2} e *> 10.40.40.192/26 10.1.1.1 2563 0 15 20 1 {2} e *> 10.40.41.0/26 10.1.1.1 1209 0 15 20 1 {2} e *>i10.102.0.0/16 10.1.1.1 300 500 0 5 4 {101,102} e *>i10.103.0.0/16 10.1.1.1 300 500 0 5 4 {101,102} e For address family: NSAP Unicast ***** BGP table version is 1, local router ID is 10.1.1.1 Status codes: s suppressed, d damped, h history, * valid, > best, i - internal, r RIB-failure Origin codes: i - IGP, e - EGP, ? - incomplete Network Next Hop Metric LocPrf Weight Path * i45.0000.0002.0001.000c.00 49.0001.0000.0000.0a00 100 0 ? * i46.0001.0000.0000.0000.0a00 49.0001.0000.0000.0a00 100 0 ? * i47.0001.0000.0000.000b.00 49.0001.0000.0000.0a00 100 0 ? * i47.0001.0000.0000.000e.00 49.0001.0000.0000.0a00The following is sample output from the show ip bgp longer-prefixes command: Device#show ip bgp 10.92.0.0 255.255.0.0 longer-prefixes BGP table version is 1738, local router ID is 192.168.72.24 Status codes: s suppressed, * valid, > best, i - internal Origin codes: i - IGP, e - EGP, ? - incomplete Network Next Hop Metric LocPrf Weight Path *> 10.92.0.0 10.92.72.30 8896 32768 ? * 10.92.72.30 0 109 108 ? *> 10.92.1.0 10.92.72.30 8796 32768 ? * 10.92.72.30 0 109 108 ? *> 10.92.11.0 10.92.72.30 42482 32768 ? * 10.92.72.30 0 109 108 ? *> 10.92.14.0 10.92.72.30 8796 32768 ? * 10.92.72.30 0 109 108 ? *> 10.92.15.0 10.92.72.30 8696 32768 ? * 10.92.72.30 0 109 108 ? *> 10.92.16.0 10.92.72.30 1400 32768 ? * 10.92.72.30 0 109 108 ? *> 10.92.17.0 10.92.72.30 1400 32768 ? * 10.92.72.30 0 109 108 ? *> 10.92.18.0 10.92.72.30 8876 32768 ? * 10.92.72.30 0 109 108 ? *> 10.92.19.0 10.92.72.30 8876 32768 ? * 10.92.72.30 0 109 108 ?The following is sample output from the show ip bgp shorter-prefixes command. An 8-bit prefix length is specified. Device#show ip bgp 172.16.0.0/16 shorter-prefixes 8 *> 172.16.0.0 10.0.0.2 0 ? * 10.0.0.2 0 0 200 ?The following is sample output from the show ip bgp prefix-list command: Device#show ip bgp prefix-list ROUTE BGP table version is 39, local router ID is 10.0.0.1 Status codes:s suppressed, d damped, h history, * valid, > best, i - internal Origin codes:i - IGP, e - EGP, ? - incomplete Network Next Hop Metric LocPrf Weight Path *> 192.168.1.0 10.0.0.2 0 ? * 10.0.0.2 0 0 200 ?The following is sample output from the show ip bgp route-map command: Device#show ip bgp route-map LEARNED_PATH BGP table version is 40, local router ID is 10.0.0.1 Status codes:s suppressed, d damped, h history, * valid, > best, i - internal Origin codes:i - IGP, e - EGP, ? - incomplete Network Next Hop Metric LocPrf Weight Path *> 192.168.1.0 10.0.0.2 0 ? * 10.0.0.2 0 0 200 ?The following output indicates (for each neighbor) whether any of the additional path tags (group-best, all, best 2 or best 3) are applied to the path. A line of output indicates rx pathid (received from neighbor) and tx pathid (announcing to neighbors). Note that the “Path advertised to update-groups:” is now per-path when the BGP Additional Paths feature is enabled. Device#show ip bgp 10.0.0.1 255.255.255.224 BGP routing table entry for 10.0.0.1/28, version 82 Paths: (10 available, best #5, table default) Path advertised to update-groups: 21 25 Refresh Epoch 1 20 50, (Received from a RR-client) 192.0.2.1 from 192.0.2.1 (192.0.2.1) Origin IGP, metric 200, localpref 100, valid, internal, all Originator: 192.0.2.1, Cluster list: 2.2.2.2 mpls labels in/out 16/nolabel rx pathid: 0, tx pathid: 0x9 Updated on Aug 14 2018 18:30:39 PST Path advertised to update-groups: 18 21 Refresh Epoch 1 30 192.0.2.2 from 192.0.2.2 (192.0.2.2) Origin IGP, metric 200, localpref 100, valid, internal, group-best, all Originator: 192.0.2.2, Cluster list: 4.4.4.4 mpls labels in/out 16/nolabel rx pathid: 0x1, tx pathid: 0x8 Updated on Aug 14 2018 18:30:39 PST Path advertised to update-groups: 16 18 19 20 21 22 24 25 27 Refresh Epoch 1 10 192.0.2.3 from 192.0.2.3 (192.0.2.3) Origin IGP, metric 200, localpref 100, valid, external, best2, all mpls labels in/out 16/nolabel rx pathid: 0, tx pathid: 0x7 Updated on Aug 14 2018 18:30:39 PST Path advertised to update-groups: 20 21 22 24 25 Refresh Epoch 1 10 192.0.2.4 from 192.0.2.4 (192.0.2.4) Origin IGP, metric 300, localpref 100, valid, external, best3, all mpls labels in/out 16/nolabel rx pathid: 0, tx pathid: 0x6 Updated on Jun 17 2018 11:12:30 PST Path advertised to update-groups: 10 13 17 18 19 20 21 22 23 24 25 26 27 28 Refresh Epoch 1 10 192.0.2.5 from 192.0.2.5 (192.0.2.5) Origin IGP, metric 100, localpref 100, valid, external, best mpls labels in/out 16/nolabel rx pathid: 0, tx pathid: 0x0 Updated on Jun 17 2018 11:12:30 PST Path advertised to update-groups: 21 Refresh Epoch 1 30 192.0.2.6 from 192.0.2.6 (192.0.2.6) Origin IGP, metric 200, localpref 100, valid, internal, all Originator: 192.0.2.6, Cluster list: 5.5.5.5 mpls labels in/out 16/nolabel rx pathid: 0x1, tx pathid: 0x5 Updated on Jun 17 2018 11:12:30 PST Path advertised to update-groups: 18 23 24 26 28 Refresh Epoch 1 60 40, (Received from a RR-client) 192.0.2.7 from 192.0.2.7 (192.0.2.7) Origin IGP, metric 250, localpref 100, valid, internal, group-best Originator: 192.0.2.7, Cluster list: 3.3.3.3 mpls labels in/out 16/nolabel rx pathid: 0x2, tx pathid: 0x2 Updated on Jun 17 2018 11:12:30 PST Path advertised to update-groups: 25 Refresh Epoch 1 30 40, (Received from a RR-client) 192.0.2.8 from 192.0.2.8 (192.0.2.8) Origin IGP, metric 200, localpref 100, valid, internal, all Originator: 192.0.2.8, Cluster list: 2.2.2.2 mpls labels in/out 16/nolabel rx pathid: 0x1, tx pathid: 0x3 Updated on Jun 17 2018 11:12:30 PST Path advertised to update-groups: 18 21 23 24 25 26 28 Refresh Epoch 1 20 40, (Received from a RR-client) 192.0.2.9 from 192.0.2.9 (192.0.2.9) Origin IGP, metric 200, localpref 100, valid, internal, group-best, all Originator: 192.0.2.9, Cluster list: 2.2.2.2 mpls labels in/out 16/nolabel rx pathid: 0x1, tx pathid: 0x4 Updated on Jun 17 2018 18:34:12 PST Path advertised to update-groups: 21 Refresh Epoch 1 30 40 192.0.2.9 from 192.0.2.9 (192.0.2.9) Origin IGP, metric 100, localpref 100, valid, internal, all Originator: 192.0.2.9, Cluster list: 4.4.4.4 mpls labels in/out 16/nolabel rx pathid: 0x1, tx pathid: 0x1 Updated on Jun 17 2018 18:34:12 PSTThe following is sample output from the show ip bgp command that displays unknown and discarded path attributes: Device#show ip bgp 192.0.2.0/32 BGP routing table entry for 192.0.2.0/32, version 0 Paths: (1 available, no best path) Refresh Epoch 1 Local 192.168.101.2 from 192.168.101.2 (192.168.101.2) Origin IGP, localpref 100, valid, internal unknown transitive attribute: flag 0xE0 type 0x81 length 0x20 value 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 unknown transitive attribute: flag 0xE0 type 0x83 length 0x20 value 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 discarded unknown attribute: flag 0x40 type 0x63 length 0x64 value 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000The following is sample output from the show ip bgp version command: Device#show ip bgp version BGP table version is 5, local router ID is 10.2.4.2 Status codes: s suppressed, d damped, h history, * valid, > best, i - internal, r RIB-failure, S Stale, m multipath, b backup-path, x best-external Origin codes: i - IGP, e - EGP, ? - incomplete Network Next Hop Metric LocPrf Weight Path *> 192.168.34.2/24 10.0.0.1 0 0 1 ? *> 192.168.35.2/24 10.0.0.1 0 0 1 ?The following example shows how to display the network version: Device#show ip bgp 192.168.34.2 | include version BGP routing table entry for 192.168.34.2/24, version 5The following sample output from the show ip bgp version recent command displays the prefix changes in the specified version: Device#show ip bgp version recent 2 BGP table version is 5, local router ID is 10.2.4.2 Status codes: s suppressed, d damped, h history, * valid, > best, i - internal, r RIB-failure, S Stale, m multipath, b backup-path, x best-external Origin codes: i - IGP, e - EGP, ? - incomplete Network Next Hop Metric LocPrf Weight Path *> 192.168.134.1/28 10.0.0.1 0 0 1 ? *> 192.168.134.19/28 10.0.0.1 0 0 1 ? *> 192.168.134.34/28 10.0.0.1 0 0 1 ? Device#show ip bgp 80.230.70.96 best-path-reason BGP routing table entry for 192.168.3.0/24, version 72 Paths: (2 available, best #2, table default) Advertised to update-groups: 2 Refresh Epoch 1 2 10.0.101.1 from 10.0.101.1 (10.0.101.1) Origin IGP, localpref 100, valid, external Extended Community: RT:100:100 rx pathid: 0, tx pathid: 0 Updated on Aug 14 2018 18:34:12 PST Best Path Evaluation: Path is younger Refresh Epoch 1 1 10.0.96.254 from 10.0.96.254 (10.0.96.254) Origin IGP, localpref 100, valid, external, best rx pathid: 0, tx pathid: 0x0 Updated on Aug 14 2018 18:30:39 PST Best Path Evaluation: Overall best pathThe following sample output for the show ip bgp summary command shows the peak watermarks and their time-stamps for the peak number of route entries per neighbor bases: Page 7To enter the Cisco TrustSec Security Group Tag (SGT) Exchange Protocol (CTS-SXP) peer IP address, to specify if a password is used for the peer connection, to specify the global hold-time period for a listener or speaker device, and to specify if the connection is bidirectional, use the cts sxp connection peer command in global configuration mode. To remove these configurations for a peer connection, use the no form of this command. cts sxp connection peer ipv4-address {source | password} {default | none} mode {local | peer} [ [ [listener | speaker] [hold-time minimum-time maximum-time | vrf vrf-name ]] | | both [vrf vrf-name]] cts sxp connection peer ipv4-address {source | password} {default | none} mode {local | peer} [ [ [listener | speaker] [hold-time minimum-time maximum-time | vrf vrf-name ]] | | both [vrf vrf-name]]
The CTS-SXP peer IP address is not configured and no CTS-SXP peer password is used for the peer connection. The default setting for a CTS-SXP connection password is none .
When a CTS-SXP connection to a peer is configured with the cts sxp connection peer command, only the connection mode can be changed. The vrf keyword is optional. If a VRF name is not provided or a VRF name is provided with the default keyword, then the connection is set up in the default routing or forwarding domain. A hold-time maximum-period value is required only when you use the following keywords: peer speaker and local listener . In other instances, only a hold-time minimum-period value is required.
Use the both keyword to configure a bidirectional SXP connection. With the support for bidirectional SXP configuration, a peer can act as both a speaker and a listener and propagate SXP bindings in both directions using a single connection. The following example shows how to enable CTS-SXP and configure the CTS-SXP peer connection on Device_A, a speaker, for connection to Device_B, a listener: Device_A> enable Device_A# configure terminal Device_A#(config)# cts sxp enable Device_A#(config)# cts sxp default password Cisco123 Device_A#(config)# cts sxp default source-ip 10.10.1.1 Device_A#(config)# cts sxp connection peer 10.20.2.2 password default mode local speakerThe following example shows how to configure the CTS-SXP peer connection on Device_B, a listener, for connection to Device_A, a speaker: Device_B> enable Device_B# configure terminal Device_B(config)# cts sxp enable Device_B(config)# cts sxp default password Cisco123 Device_B(config)# cts sxp default source-ip 10.20.2.2 Device_B(config)# cts sxp connection peer 10.10.1.1 password default mode local listenerYou can also configure both peer and source IP addresses for an SXP connection. The source IP address specified in the cts sxp connection command overwrites the default value. Device_A(config)# cts sxp connection peer 51.51.51.1 source 51.51.51.2 password none mode local speaker Device_B(config)# cts sxp connection peer 51.51.51.2 source 51.51.51.1 password none mode local listenerThe following example shows how to enable bidirectional CTS-SXP and configure the SXP peer connection on Device_A to connect to Device_B: Device_A> enable Device_A# configure terminal Device_A#(config)# cts sxp enable Device_A#(config)# cts sxp default password Cisco123 Device_A#(config)# cts sxp default source-ip 10.10.1.1 Device_A#(config)# cts sxp connection peer 10.20.2.2 password default mode local bothPage 8Initially, all the tracelog files are moved from the initial /tmp/<FRU>/trace directory to the /tmp/<FRU>/trace/stage staging directory. The btrace_rotate script then moves these tracelogs from the staging directory to the /crashinfo/tracelogs directory. When the number of files stored in the /crashinfo/tracelogs directory per process reaches the maximum limit, the oldest files for the process are deleted, while the newer files are maintained. This is repeated at every 60 minutes under worst-case situations. There are two other sets of files that are purged from the /crashinfo/tracelogs directory:
The throttling policy has been introduced so that a process with errors does not affect the functioning of the switch. Whenever a process starts logging at a very high rate, for example, if there are more than 16 files in a 4-second interval for the process in the staging directory, the process is throttled. The files do not rotate for the process from /tmp/<FRU>/trace into /tmp/<FRU>/trace/stage, however the files are deleted when they reach the maximum size. Throttling is re-enabled, when the count goes below 8. Page 9This command is used to display the current dynamic and static IPv4 EID-to-RLOC map-cache entries. When no IPv4 EID or IPv4 EID prefix is specified, summary information is listed for all current dynamic and static IPv4 EID-to-RLOC map-cache entries. When an IPv4 EID or IPv4 EID prefix is included, information is listed for the longest-match lookup in the cache. When the detail option is used, detailed (rather than summary) information related to all current dynamic and static IPv4 EID-to-RLOC map-cache entries is displayed. The following are sample outputs from the show lisp instance-id ipv4 map-cache commands: device# show lisp instance-id 102 ipv4 map-cache LISP IPv4 Mapping Cache for EID-table vrf blue (IID 102), 4008 entries 0.0.0.0/0, uptime: 2d14h, expires: never, via static-send-map-request Negative cache entry, action: send-map-request 128.0.0.0/3, uptime: 00:01:44, expires: 00:13:15, via map-reply, unknown-eid-forward PETR Uptime State Pri/Wgt Encap-IID 55.55.55.1 13:32:40 up 1/100 103 55.55.55.2 13:32:40 up 1/100 103 55.55.55.3 13:32:40 up 1/100 103 55.55.55.4 13:32:40 up 1/100 103 55.55.55.5 13:32:40 up 5/100 103 55.55.55.6 13:32:40 up 6/100 103 55.55.55.7 13:32:40 up 7/100 103 55.55.55.8 13:32:40 up 8/100 103 150.150.2.0/23, uptime: 11:47:25, expires: 00:06:30, via map-reply, unknown-eid-forward PETR Uptime State Pri/Wgt Encap-IID 55.55.55.1 13:32:40 up 1/100 103 55.55.55.2 13:32:40 up 1/100 103 55.55.55.3 13:32:40 up 1/100 103 55.55.55.4 13:32:40 up 1/100 103 55.55.55.5 13:32:40 up 5/100 103 55.55.55.6 13:32:40 up 6/100 103 55.55.55.7 13:32:43 up 7/100 103 55.55.55.8 13:32:43 up 8/100 103 150.150.4.0/22, uptime: 13:32:43, expires: 00:05:19, via map-reply, unknown-eid-forward PETR Uptime State Pri/Wgt Encap-IID 55.55.55.1 13:32:43 up 1/100 103 55.55.55.2 13:32:43 up 1/100 103 55.55.55.3 13:32:43 up 1/100 103 55.55.55.4 13:32:43 up 1/100 103 55.55.55.5 13:32:43 up 5/100 103 55.55.55.6 13:32:43 up 6/100 103 55.55.55.7 13:32:43 up 7/100 103 55.55.55.8 13:32:43 up 8/100 103 150.150.8.0/21, uptime: 13:32:35, expires: 00:05:27, via map-reply, unknown-eid-forward PETR Uptime State Pri/Wgt Encap-IID 55.55.55.1 13:32:43 up 1/100 103 55.55.55.2 13:32:43 up 1/100 103 55.55.55.3 13:32:43 up 1/100 103 55.55.55.4 13:32:43 up 1/100 103 55.55.55.5 13:32:43 up 5/100 103 55.55.55.6 13:32:43 up 6/100 103 55.55.55.7 13:32:43 up 7/100 103 55.55.55.8 13:32:45 up 8/100 103 171.171.0.0/16, uptime: 2d14h, expires: never, via dynamic-EID, send-map-request Negative cache entry, action: send-map-request 172.172.0.0/16, uptime: 2d14h, expires: never, via dynamic-EID, send-map-request Negative cache entry, action: send-map-request 178.168.2.1/32, uptime: 2d14h, expires: 09:27:13, via map-reply, complete Locator Uptime State Pri/Wgt Encap-IID 11.11.11.1 2d14h up 1/100 - 178.168.2.2/32, uptime: 2d14h, expires: 09:27:13, via map-reply, complete Locator Uptime State Pri/Wgt Encap-IID 11.11.11.1 2d14h up 1/100 - 178.168.2.3/32, uptime: 2d14h, expires: 09:27:13, via map-reply, complete Locator Uptime State Pri/Wgt Encap-IID 11.11.11.1 2d14h up 1/100 - 178.168.2.4/32, uptime: 2d14h, expires: 09:27:13, via map-reply, complete Locator Uptime State Pri/Wgt Encap-IID 11.11.11.1 2d14h up 1/100 - 178.168.2.5/32, uptime: 2d14h, expires: 09:27:13, via map-reply, complete Locator Uptime State Pri/Wgt Encap-IID 11.11.11.1 2d14h up 1/100 - 178.168.2.6/32, uptime: 2d14h, expires: 09:27:13, via map-reply, complete Locator Uptime State Pri/Wgt Encap-IID device#show lisp instance-id 102 ipv4 map-cache detail LISP IPv4 Mapping Cache for EID-table vrf blue (IID 102), 4008 entries 0.0.0.0/0, uptime: 2d15h, expires: never, via static-send-map-request Sources: static-send-map-request State: send-map-request, last modified: 2d15h, map-source: local Exempt, Packets out: 30531(17585856 bytes) (~ 00:01:36 ago) Configured as EID address space Negative cache entry, action: send-map-request 128.0.0.0/3, uptime: 00:02:02, expires: 00:12:57, via map-reply, unknown-eid-forward Sources: map-reply State: unknown-eid-forward, last modified: 00:02:02, map-source: local Active, Packets out: 9(5184 bytes) (~ 00:00:36 ago) PETR Uptime State Pri/Wgt Encap-IID 55.55.55.1 13:32:58 up 1/100 103 55.55.55.2 13:32:58 up 1/100 103 55.55.55.3 13:32:58 up 1/100 103 55.55.55.4 13:32:58 up 1/100 103 55.55.55.5 13:32:58 up 5/100 103 55.55.55.6 13:32:58 up 6/100 103 55.55.55.7 13:32:58 up 7/100 103 55.55.55.8 13:32:58 up 8/100 103 150.150.2.0/23, uptime: 11:47:43, expires: 00:06:12, via map-reply, unknown-eid-forward Sources: map-reply State: unknown-eid-forward, last modified: 11:47:44, map-source: local Active, Packets out: 4243(2443968 bytes) (~ 00:00:38 ago) PETR Uptime State Pri/Wgt Encap-IID 55.55.55.1 13:33:00 up 1/100 103 55.55.55.2 13:33:00 up 1/100 103 55.55.55.3 13:33:00 up 1/100 103 55.55.55.4 13:33:00 up 1/100 103 55.55.55.5 13:33:00 up 5/100 103 55.55.55.6 13:33:00 up 6/100 103 55.55.55.7 13:33:00 up 7/100 103 55.55.55.8 13:33:00 up 8/100 103 150.150.4.0/22, uptime: 13:33:00, expires: 00:05:02, via map-reply, unknown-eid-forward Sources: map-reply State: unknown-eid-forward, last modified: 13:33:00, map-source: local Active, Packets out: 4874(2807424 bytes) (~ 00:00:38 ago) PETR Uptime State Pri/Wgt Encap-IID 55.55.55.1 13:33:00 up 1/100 103 55.55.55.2 13:33:00 up 1/100 103 55.55.55.3 13:33:00 up 1/100 103 55.55.55.4 13:33:00 up 1/100 103 55.55.55.5 13:33:00 up 5/100 103 55.55.55.6 13:33:00 up 6/100 103 55.55.55.7 13:33:01 up 7/100 103 55.55.55.8 13:33:01 up 8/100 103 150.150.8.0/21, uptime: 13:32:53, expires: 00:05:09, via map-reply, unknown-eid-forward Sources: map-reply State: unknown-eid-forward, last modified: 13:32:53, map-source: local Active, Packets out: 4874(2807424 bytes) (~ 00:00:39 ago) PETR Uptime State Pri/Wgt Encap-IID 55.55.55.1 13:33:01 up 1/100 103 55.55.55.2 13:33:01 up 1/100 103 55.55.55.3 13:33:01 up 1/100 103 55.55.55.4 13:33:01 up 1/100 103 55.55.55.5 13:33:01 up 5/100 103 55.55.55.6 13:33:01 up 6/100 103 55.55.55.7 13:33:01 up 7/100 103 55.55.55.8 13:33:01 up 8/100 103 171.171.0.0/16, uptime: 2d15h, expires: never, via dynamic-EID, send-map-request Sources: NONE State: send-map-request, last modified: 2d15h, map-source: local Exempt, Packets out: 2(1152 bytes) (~ 2d14h ago) Configured as EID address space Configured as dynamic-EID address space Encapsulating dynamic-EID traffic Negative cache entry, action: send-map-request 172.172.0.0/16, uptime: 2d15h, expires: never, via dynamic-EID, send-map-request Sources: NONE State: send-map-request, last modified: 2d15h, map-source: local Exempt, Packets out: 2(1152 bytes) (~ 2d14h ago) Configured as EID address space Configured as dynamic-EID address space Encapsulating dynamic-EID traffic Negative cache entry, action: send-map-request 178.168.2.1/32, uptime: 2d14h, expires: 09:26:55, via map-reply, complete Sources: map-reply State: complete, last modified: 2d14h, map-source: 48.1.1.4 Active, Packets out: 22513(12967488 bytes) (~ 00:00:41 ago) Locator Uptime State Pri/Wgt Encap-IID 11.11.11.1 2d14h up 1/100 - Last up-down state change: 2d14h, state change count: 1 Last route reachability change: 2d14h, state change count: 1 Last priority / weight change: never/never RLOC-probing loc-status algorithm: Last RLOC-probe sent: 2d14h (rtt 92ms) 178.168.2.2/32, uptime: 2d14h, expires: 09:26:55, via map-reply, complete Sources: map-reply State: complete, last modified: 2d14h, map-source: 48.1.1.4 Active, Packets out: 22513(12967488 bytes) (~ 00:00:45 ago) Locator Uptime State Pri/Wgt Encap-IID 11.11.11.1 2d14h up 1/100 - Last up-down state change: 2d14h, state change count: 1 Last route reachability change: 2d14h, state change count: 1 Last priority / weight change: never/never RLOC-probing loc-status algorithm: Last RLOC-probe sent: 2d14h (rtt 91ms) 178.168.2.3/32, uptime: 2d14h, expires: 09:26:51, via map-reply, complete Sources: map-reply State: complete, last modified: 2d14h, map-source: 48.1.1.4 Active, Packets out: 22513(12967488 bytes) (~ 00:00:45 ago) Locator Uptime State Pri/Wgt Encap-IID 11.11.11.1 2d14h up 1/100 - Last up-down state change: 2d14h, state change count: 1 Last route reachability change: 2d14h, state change count: 1 Last priority / weight change: never/never RLOC-probing loc-status algorithm: Last RLOC-probe sent: 2d14h (rtt 91ms) 178.168.2.4/32, uptime: 2d14h, expires: 09:26:51, via map-reply, complete Sources: map-reply State: complete, last modified: 2d14h, map-source: 48.1.1.4 device#show lisp instance-id 102 ipv4 map-cache 178.168.2.3/32 LISP IPv4 Mapping Cache for EID-table vrf blue (IID 102), 4008 entries 178.168.2.3/32, uptime: 2d14h, expires: 09:26:25, via map-reply, complete Sources: map-reply State: complete, last modified: 2d14h, map-source: 48.1.1.4 Active, Packets out: 22519(12970944 bytes) (~ 00:00:11 ago) Locator Uptime State Pri/Wgt Encap-IID 11.11.11.1 2d14h up 1/100 - Last up-down state change: 2d14h, state change count: 1 Last route reachability change: 2d14h, state change count: 1 Last priority / weight change: never/never RLOC-probing loc-status algorithm: Last RLOC-probe sent: 2d14h (rtt 91ms) device#show lisp instance-id 102 ipv4 map-cache 178.168.2.3 LISP IPv4 Mapping Cache for EID-table vrf blue (IID 102), 4008 entries 178.168.2.3/32, uptime: 2d14h, expires: 09:26:14, via map-reply, complete Sources: map-reply State: complete, last modified: 2d14h, map-source: 48.1.1.4 Active, Packets out: 22519(12970944 bytes) (~ 00:00:22 ago) Locator Uptime State Pri/Wgt Encap-IID 11.11.11.1 2d14h up 1/100 - Last up-down state change: 2d14h, state change count: 1 Last route reachability change: 2d14h, state change count: 1 Last priority / weight change: never/never RLOC-probing loc-status algorithm: Last RLOC-probe sent: 2d14h (rtt 91ms) OTT-LISP-C3K-4-xTR2#show lisp instance-id 102 sta OTT-LISP-C3K-4-xTR2#show lisp instance-id 102 stat OTT-LISP-C3K-4-xTR2#show lisp instance-id 102 ipv4 stat OTT-LISP-C3K-4-xTR2#show lisp instance-id 102 ipv4 statistics LISP EID Statistics for instance ID 102 - last cleared: never Control Packets: Map-Requests in/out: 5911/66032 Map-Request receive rate (5 sec/1 min/5 min): 0.00/ 0.00/ 0.00 Encapsulated Map-Requests in/out: 0/60600 RLOC-probe Map-Requests in/out: 5911/5432 SMR-based Map-Requests in/out: 0/0 Extranet SMR cross-IID Map-Requests in: 0 Map-Requests expired on-queue/no-reply 0/0 Map-Resolver Map-Requests forwarded: 0 Map-Server Map-Requests forwarded: 0 Map-Reply records in/out: 64815/5911 Authoritative records in/out: 12696/5911 Non-authoritative records in/out: 52119/0 Negative records in/out: 8000/0 RLOC-probe records in/out: 4696/5911 Map-Server Proxy-Reply records out: 0 WLC Map-Subscribe records in/out: 0/4 Map-Subscribe failures in/out: 0/0 WLC Map-Unsubscribe records in/out: 0/0 Map-Unsubscribe failures in/out: 0/0 Map-Register records in/out: 0/8310 Map-Register receive rate (5 sec/1 min/5 min): 0.00/ 0.00/ 0.00 Map-Server AF disabled: 0 Authentication failures: 0 WLC Map-Register records in/out: 0/0 WLC AP Map-Register in/out: 0/0 WLC Client Map-Register in/out: 0/0 WLC Map-Register failures in/out: 0/0 Map-Notify records in/out: 20554/0 Authentication failures: 0 WLC Map-Notify records in/out: 0/0 WLC AP Map-Notify in/out: 0/0 WLC Client Map-Notify in/out: 0/0 WLC Map-Notify failures in/out: 0/0 Publish-Subscribe in/out: Subscription Request records in/out: 0/6 Subscription Request failures in/out: 0/0 Subscription Status records in/out: 4/0 End of Publication records in/out: 4/0 Subscription rejected records in/out: 0/0 Subscription removed records in/out: 0/0 Subscription Status failures in/out: 0/0 Solicit Subscription records in/out: 0/0 Solicit Subscription failures in/out: 0/0 Publication records in/out: 0/0 Publication failures in/out: 0/0 Errors: Mapping record TTL alerts: 0 Map-Request invalid source rloc drops: 0 Map-Register invalid source rloc drops: 0 DDT Requests failed: 0 DDT ITR Map-Requests dropped: 0 (nonce-collision: 0, bad-xTR-nonce: 0) Cache Related: Cache entries created/deleted: 200103/196095 NSF CEF replay entry count 0 Number of EID-prefixes in map-cache: 4008 Number of rejected EID-prefixes due to limit : 0 Number of negative entries in map-cache: 8 Total number of RLOCs in map-cache: 4000 Average RLOCs per EID-prefix: 1 Forwarding: Number of data signals processed: 199173 (+ dropped 5474) Number of reachability reports: 0 (+ dropped 0) Number of SMR signals dropped: 0 ITR Map-Resolvers: Map-Resolver LastReply Metric ReqsSent Positive Negative No-Reply AvgRTT(5 sec/1 min/5 min) 44.44.44.44 00:03:11 6 62253 19675 8000 0 0.00/ 0.00/10.00 66.66.66.66 never Unreach 0 0 0 0 0.00/ 0.00/ 0.00 ETR Map-Servers: Map-Server AvgRTT(5 sec/1 min/5 min) 44.44.44.44 0.00/ 0.00/ 0.00 66.66.66.66 0.00/ 0.00/ 0.00 LISP RLOC Statistics - last cleared: never Control Packets: RTR Map-Requests forwarded: 0 RTR Map-Notifies forwarded: 0 DDT-Map-Requests in/out: 0/0 DDT-Map-Referrals in/out: 0/0 Errors: Map-Request format errors: 0 Map-Reply format errors: 0 Map-Referral format errors: 0 LISP Miscellaneous Statistics - last cleared: never Errors: Invalid IP version drops: 0 Invalid IP header drops: 0 Invalid IP proto field drops: 0 Invalid packet size drops: 0 Invalid LISP control port drops: 0 Invalid LISP checksum drops: 0 Unsupported LISP packet type drops: 0 Unknown packet drops: 0Page 10
|
What Cisco IOS command is used to display the current status of the Cisco VLAN Trunking Protocol
zusammenhängende Posts
Urheberrechte © © 2024 frojeostern Inc.
