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: Table 1. show vlan Command Output Fields
Page 2
To 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 3
Use 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.
Note
Note
Table 3. Auto-QoS Configuration for the Egress Queues
Page 4
The 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 5
To 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. Use care when using the on mode. This is a manual configuration, and ports on both ends of the EtherChannel must have the same configuration. If the group is misconfigured, packet loss or spanning-tree loops can occur. 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. Do not enable Layer 3 addresses on the physical EtherChannel ports. Do not assign bridge groups on the physical EtherChannel ports because it creates loops. 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: 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 LACP mode active: This 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: You can verify your settings by entering the show running-config privileged EXEC command.
Caution
Caution
Page 6
To 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}]
ip-address | (Optional) IP address entered to filter the output to display only a particular host or network in the BGP routing table. | ||
mask | (Optional) Mask to filter or match hosts that are part of the specified network. | ||
longer-prefixes | (Optional) Displays the specified route and all more-specific routes. | ||
injected | (Optional) Displays more-specific prefixes injected into the BGP routing table. | ||
shorter-prefixes | (Optional) Displays the specified route and all less-specific routes. | ||
length | (Optional) The prefix length. The range is a number from 0 to 32. | ||
bestpath | (Optional) Displays the best path for this prefix. | ||
best-path-reason | (Optional) Displays the reason why a path loses to the bestpath.
| ||
internal | (Optional) Displays the internal details for this prefix. | ||
multipaths | (Optional) Displays multipaths for this prefix. | ||
subnets | (Optional) Displays the subnet routes for the specified prefix. | ||
all | (Optional) Displays all address family information in the BGP routing table. | ||
oer-paths | (Optional) Displays Optimized Edge Routing (OER) controlled prefixes in the BGP routing table. | ||
prefix-list name | (Optional) Filters the output based on the specified prefix list. | ||
pending-prefixes | (Optional) Displays prefixes that are pending deletion from the BGP routing table. | ||
route-map name | (Optional) Filters the output based on the specified route map. | ||
version version-number | (Optional) Displays all prefixes with network versions greater than or equal to the specified version number. The range is from 1 to 4294967295. | ||
recent offset-value | (Optional) Displays the offset from the current routing table version. The range is from 1 to 4294967295. |
User EXEC (>)
Privileged EXEC (#)
Cisco IOS XE Everest 16.5.1a | This command was introduced. |
Cisco IOS XE Gibraltar 16.10.1 | The best-path-reason keyword was added to this command. BGP Path Installation Time-Stamp was added to the output of the command. BGP Peak Prefix Watermark was added to the output of the command. |
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.
BGP table version | Internal version number of the table. This number is incremented whenever the table changes. |
local router ID | IP address of the router. |
Status codes | Status of the table entry. The status is displayed at the beginning of each line in the table. It can be one of the following values:
|
Origin codes | Origin of the entry. The origin code is placed at the end of each line in the table. It can be one of the following values:
|
RPKI validation codes | If shown, the RPKI validation state for the network prefix, which is downloaded from the RPKI server. The codes are shown only if the bgp rpki server or neighbor announce rpki state command is configured. |
Network | IP address of a network entity. |
Next Hop | IP address of the next system that is used when forwarding a packet to the destination network. An entry of 0.0.0.0 indicates that the router has some non-BGP routes to this network. |
Metric | If shown, the value of the interautonomous system metric. |
LocPrf | Local preference value as set with the set local-preference route-map configuration command. The default value is 100. |
Weight | Weight of the route as set via autonomous system filters. |
Path | Autonomous system paths to the destination network. There can be one entry in this field for each autonomous system in the path. |
(stale) | Indicates that the following path for the specified autonomous system is marked as “stale” during a graceful restart process. |
Updated on | The time at which the path is received or updated. |
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.
BGP routing table entry for | IP address or network number of the routing table entry. |
version | Internal version number of the table. This number is incremented whenever the table changes. |
Paths | The number of available paths, and the number of installed best paths. This line displays “Default-IP-Routing-Table” when the best path is installed in the IP routing table. |
Multipath | This field is displayed when multipath load sharing is enabled. This field will indicate if the multipaths are iBGP or eBGP. |
Advertised to update-groups | The number of each update group for which advertisements are processed. |
Origin | Origin of the entry. The origin can be IGP, EGP, or incomplete. This line displays the configured metric (0 if no metric is configured), the local preference value (100 is default), and the status and type of route (internal, external, multipath, best). |
Extended Community | This field is displayed if the route carries an extended community attribute. The attribute code is displayed on this line. Information about the extended community is displayed on a subsequent line. |
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:
Device#show ip bgp all summary For address family: IPv4 Unicast BGP router identifier 10.10.10.10, local AS number 1 BGP table version is 27, main routing table version 27 2 network entries using 496 bytes of memory 2 path entries using 272 bytes of memory 1/1 BGP path/bestpath attribute entries using 280 bytes of memory 1 BGP extended community entries using 24 bytes of memory 0 BGP route-map cache entries using 0 bytes of memory 0 BGP filter-list cache entries using 0 bytes of memory BGP using 1072 total bytes of memory BGP activity 58/54 prefixes, 110/106 paths, scan interval 60 secs 20 networks peaked at 00:03:50 Jul 28 2018 PST (00:00:32.833 ago) Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd 11.11.11.11 4 1 0 0 1 0 0 00:20:09 Idle For address family: L2VPN E-VPN BGP router identifier 10.10.10.10, local AS number 1 BGP table version is 183, main routing table version 183 2 network entries using 688 bytes of memory 2 path entries using 416 bytes of memory 2/2 BGP path/bestpath attribute entries using 560 bytes of memory 1 BGP extended community entries using 24 bytes of memory 0 BGP route-map cache entries using 0 bytes of memory 0 BGP filter-list cache entries using 0 bytes of memory BGP using 1688 total bytes of memory BGP activity 58/54 prefixes, 110/106 paths, scan interval 60 secs 30 networks peaked at 00:35:36 Jul 28 2018 PST (00:00:47.321 ago) Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd 11.11.11.11 4 1 0 0 1 0 0 00:20:09 Idle bgp asnotation dot | Changes the default display and the regular expression match format of BGP 4-byte autonomous system numbers from asplain (decimal values) to dot notation. |
clear ip bgp | Resets BGP connections using hard or soft reconfiguration. |
ip bgp community new-format | Configures BGP to display communities in the format AA:NN. |
ip prefix-list | Creates a prefix list or adds a prefix-list entry. |
route-map | Defines the conditions for redistributing routes from one routing protocol into another routing protocol. |
router bgp | Configures the BGP routing process. |
Page 7
To 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]]
ipv4-address | SXP peer IPv4 address. | ||
source | Specifies the source IPv4 address. | ||
password | Specifies that an SXP password is used for the peer connection. | ||
default | Specifies that the default SXP password is used. | ||
none | Specifies no password is used. | ||
mode | Specifies either the local or peer SXP connection mode. | ||
local | Specifies that the SXP connection mode refers to the local device. | ||
peer | Specifies that the SXP connection mode refers to the peer device. | ||
listener | (Optional) Specifies that the device is the listener in the connection. | ||
speaker | (Optional) Specifies that the device is the speaker in the connection. | ||
hold-time minimum-time maximum-time | (Optional) Specifies the hold-time period, in seconds, for the device. The range for minimum and maximum time is from 0 to 65535. A maximum-time value is required only when you use the following keywords: peer speaker and local listener . In other instances, only a minimum-time value is required.
| ||
vrf vrf-name | (Optional) Specifies the virtual routing and forwarding (VRF) instance name to the peer. | ||
both | (Optional) Specifies that the device is both the speaker and the listener in the bidirectional SXP connection. |
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 .
Global configuration (config)
Cisco IOS XE Fuji 16.9.1 | This command was introduced. |
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.
Note | The maximum-period value must be greater than or equal to the minimum-period value. |
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 both cts sxp default password | Configures the Cisco TrustSec SXP default password. |
cts sxp default source-ip | Configures the Cisco TrustSec SXP source IPv4 address. |
cts sxp enable | Enables Cisco TrustSec SXP on a device. |
cts sxp log | Enables logging for IP-to-SGT binding changes. |
cts sxp reconciliation | Changes the Cisco TrustSec SXP reconciliation period. |
cts sxp retry | Changes the Cisco TrustSec SXP retry period timer. |
cts sxp speaker hold-time | Configures the global hold-time period of a speaker device in a Cisco TrustSec SGT SXPv4 network. |
cts sxp listener hold-time | Configures the global hold-time period of a listener device in a Cisco TrustSec SGT SXPv4 network. |
show cts sxp | Displays the status of all Cisco TrustSec SXP configurations. |
Page 8
Initially, 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:
-
Files that do not have the standard naming convention (other than a few exceptions such as fed_python.log)
-
Files older than two weeks
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 9
This 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
- A - B - C - D - E - F - H - I - K - L - M - N - O - P - Q - R - S - T - U - V - X
Index
A
address-family ipv4 (EIGRP MTR)
address-family ipv6 (OSPF)
authentication logging verbose
authentication mac-move permit
B
C
clear cts environment-data
clear cts policy-server statistics
clear diagnostic event-log
clear errdisable interface vlan
clear ip pim snooping vlan
clear ipv6 dhcp relay binding
clear ipv6 multicast aaa authorization
clear ipv6 nd destination
clear ipv6 nd on-link prefix
clear l2protocol-tunnel counters
clear secure-stackwise-virtual interface
clear spanning-tree counters
clear spanning-tree detected-protocols
collect routing next-hop address
collect timestamp absolute
collect transport tcp flags
copy startup-config tftp:
copy tftp: startup-config
cts environment-data enable
cts policy-server device-id
cts policy-server order random
cts policy-server username
cts role-based enforcement
cts role-based permissions
cts role-based sgt-caching
cts sxp default source-ip
cts sxp log binding-changes
cts sxp reconciliation period
D
debug aaa dead-criteria transaction
debug cts environment-data
debug platform condition feature multicast controlplane
debug platform condition mac
debug platform software fed switch active punt packet-capture start
debug secure-stackwise-virtual
debug sw-vlan notification
debug voice diagnostics mac-address
default-information originate (OSPF)
deny (MAC access-list configuration)
device-role (IPv6 nd inspection)
device-role (IPv6 snooping)
diagnostic schedule module
dot1x critical (global configuration)
dot1x supplicant controlled transient
dot1x supplicant force-multicast
dual-active recovery-reload-disable
E
eigrp log-neighbor-changes
enable (interface configuration)
errdisable recovery cause
export-protocol netflow-v5
F
fast-reroute keep-all-paths
fast-reroute load-sharing disable (EIGRP)
fast-reroute per-prefix (EIGRP)
fast-reroute per-prefix enable (OSPF)
fast-reroute per-prefix tie-break (OSPF)
fast-reroute tie-break (EIGRP)
H
hw-module switch usbflash
I
ip access-list role-based
ip authentication key-chain eigrp
ip authentication mode eigrp
ip bandwidth-percent eigrp
ip cef load-sharing algorithm
ip dhcp snooping database
ip dhcp snooping information option format remote-id
ip dhcp snooping verify no-relay-agent-address
ip igmp snooping last-member-query-count
ip igmp snooping report-suppression
ip igmp snooping vlan mrouter
ip igmp snooping vlan static
ip multicast mrinfo-filter
ip ospf database-filter all out
ip ospf fast-reroute per-prefix
ip pim lisp core-group-range
ip pim lisp transport multicast
ip radius source-interface
ipv4 multicast multitopology
ipv6 cef load-sharing algorithm
ipv6 cef optimize neighbor resolution
ipv6 destination-guard policy
ipv6 dhcp binding track ppp
ipv6 dhcp server vrf enable
ipv6 dhcp-relay bulk-lease
ipv6 dhcp-relay option vpn
ipv6 dhcp-relay source-interface
ipv6 local policy route-map
ipv6 multicast group-range
ipv6 multicast pim-passive-enable
ipv6 nd cache interface-limit (global)
ipv6 nd resolution data limit
ipv6 pim neighbor-filter list
ipv6 pim spt-threshold infinity
ipv6 source-guard attach-policy
ipv6 spd queue max-threshold
ipv6 traffic interface-statistics
K
key config-key password-encrypt
key-string (authentication)
L
license smart (global config)
license smart (privileged EXEC)
license smart register idtoken
lldp (interface configuration)
M
mab request format attribute 32
mac address-table move update
match (access-map configuration)
match (class-map configuration)
match ipv4 destination address
match ipv4 source address
match ipv6 destination address
match ipv6 source address
match transport icmp ipv4
match transport icmp ipv6
mka suppress syslogs sak-rekey
mode (power-stack configuration)
monitor capture (interface/control plane)
monitor capture pktlen-range
monitor session destination
mpls ip (global configuration)
mpls ip (interface configuration)
mpls label protocol (global configuration)
mpls label protocol (interface configuration)
mpls ldp logging neighbor-changes
N
neighbor advertisement-interval
neighbor default-originate
neighbor maximum-prefix (BGP)
neighbor peer-group (assigning members)
neighbor peer-group (creating)
network (BGP and multiprotocol BGP)
network-policy profile (global configuration)
O
P
permit (MAC access-list configuration)
policy config-sync prc reload
port-channel load-balance
port-channel load-balance extended
power supply autoLC shutdown
propagate sgt (cts manual)
Q
qos queue-softmax-multiplier
R
radius-server dead-criteria
radius-server directed-request
random-detect precedence-based
redistribute maximum-prefix (OSPF)
redundancy force-switchover
request consent-token accept-response shell-access
request consent-token generate-challenge shell-access
request consent-token terminate-auth
request platform software console attach switch
router routing protocol shutdown l2
S
sap mode-list (cts manual)
secure-stackwise-virtual authorization-key 128-bits
secure-stackwise-virtual zeroize sha1-key
security level (IPv6 snooping)
send-secure-announcements
service private-config-encryption
set platform software fed switch
set platform software nif-mgr switch
show authentication brief
show authentication history
show authentication sessions
show capability feature monitor
show class-map type control subscriber
show cts environment-data
show cts role-based counters
show cts role-based permissions
show diagnostic description
show diagnostic simulation failure
show hw-module switch subslot
show interfaces private-vlan mapping
show interfaces rep detail
show interfaces switchport
show interfaces transceiver
show ip dhcp snooping statistics
show ip igmp snooping groups
show ip igmp snooping mrouter
show ip igmp snooping querier
show ip ospf border-routers
show ip ospf fast-reroute
show ip ospf virtual-links
show ipv6 destination-guard policy
show ipv6 dhcp guard policy
show ipv6 dhcp relay binding
show ipv6 eigrp interfaces
show ipv6 nd on-link prefix
show ipv6 ospf border-routers
show ipv6 ospf graceful-restart
show ipv6 ospf request-list
show ipv6 ospf retransmission-list
show ipv6 ospf statistics
show ipv6 ospf summary-prefix
show ipv6 ospf timers rate-limit
show ipv6 ospf virtual-links
show ipv6 pim join-prune statistic
show ipv6 source-guard policy
show license authorization
show license data conversion
show license history message
show lisp instance-id ipv4 database
show lisp instance-id ipv4 map-cache
show lisp instance-id ipv4 server
show lisp instance-id ipv4 statistics
show lisp instance-id ipv6 database
show lisp instance-id ipv6 map-cache
show lisp instance-id ipv6 server
show lisp instance-id ipv6 statistics
show logging onboard switch
show logging onboard switch uptime
show mac address-table move update
show mgmt-infra trace messages ilpower
show mgmt-infra trace messages ilpower-ha
show mgmt-infra trace messages platform-mgr-poe
show mpls forwarding-table
show mpls static crossconnect
show network-policy profile
show parameter-map type subscriber attribute-to-service
show parser encrypt file status
show platform etherchannel
show platform hardware bluetooth
show platform hardware capacity
show platform hardware fed (TCAM utilization)
show platform hardware fed active fwd-asic resource tcam utilization
show platform hardware fed active vlan ingress
show platform hardware fed switch
show platform hardware fed switch forward
show platform hardware fed switch forward interface
show platform hardware fed switch forward last summary
show platform hardware fed switch fwd-asic counters tla
show platform hardware fpga
show platform pm l2bum-status
show platform pm l2bum-status vlan
show platform software audit
show platform software fed
show platform software fed switch fss bum-opt summary
show platform software fed switch ip wccp
show platform software fed switch ptp
show platform software fed switch punt c
show platform software fed switch punt cpuq
show platform software fed switch punt cpuq rates
show platform software fed switch punt packet-capture display
show platform software fed switch punt rates interfaces
show platform software fed switch qos qsb
show platform software l2vpn
show platform software l2_svl_bum forwarding-manager switch
show platform software memory
show platform software nif-mgr switch
show platform software process list
show platform software process memory
show platform software process slot
show platform software sl-infra
show platform software status control-processor
show platform software swspan
show platform software thread list
show platform sudi certificate
show processes cpu platform
show processes cpu platform history
show processes cpu platform monitor
show processes memory platform
show redundancy config-sync
show secure-stackwise-virtual
show tech-support confidential
show tech-support diagnostic
show tech-support identity
show tech-support license
show tech-support monitor
show tech-support platform
show tech-support platform evpn_vxlan
show tech-support platform fabric
show tech-support platform igmp_snooping
show tech-support platform layer3
show tech-support platform mld_snooping
show tech-support resource
show vlan dot1q tag native
shutdown (monitor session)
snmp ifmib ifindex persist
snmp-server enable traps bridge
snmp-server enable traps bulkstat
snmp-server enable traps call-home
snmp-server enable traps cef
snmp-server enable traps cpu
snmp-server enable traps envmon
snmp-server enable traps errdisable
snmp-server enable traps flash
snmp-server enable traps isis
snmp-server enable traps license
snmp-server enable traps mac-notification
snmp-server enable traps ospf
snmp-server enable traps pim
snmp-server enable traps port-security
snmp-server enable traps snmp
snmp-server enable traps storm-control
snmp-server enable traps stpx
snmp-server enable traps transceiver
snmp-server enable traps vrfmib
snmp-server enable traps vstack
source template type pseudowire
spanning-tree backbonefast
spanning-tree bridge assurance
spanning-tree etherchannel guard misconfig
spanning-tree extend system-id
spanning-tree loopguard default
spanning-tree mst configuration
spanning-tree mst forward-time
spanning-tree mst max-age
spanning-tree mst max-hops
spanning-tree mst pre-standard
spanning-tree mst priority
spanning-tree mst simulate pvst global
spanning-tree pathcost method
spanning-tree port-priority
spanning-tree portfast default
spanning-tree portfast edge bpdufilter default
spanning-tree portfast edge bpduguard default
spanning-tree transmit hold-count
stackwise-virtual dual-active-detection
switchport mode private-vlan
switchport port-security aging
switchport port-security mac-address
switchport port-security maximum
switchport port-security violation
switchport priority extend
system env temperature threshold yellow
T
tunnel mode gre multipoint
U
upgrade rom-monitor capsule
V
vtp (global configuration)
vtp (interface configuration)
X