[Contents] [Prev] [Next] [Index] [Report an Error]

# Monitoring BGP/MPLS VPNs

To view BGP/MPLS VPN settings, you can issue the following show commands as well as any of the show ip bgp commands and some of the show bgp ipv6 commands described in Configuring BGP Routing . See Configuring MPLS, for information about show commands to monitor MPLS settings.

Use the debug ip mbgp command to get information about problems with BGP or the network.

| Note: The E120 router and E320 router output for monitor and show commands is identical to output from other E-series routers, except that the E120 and E320 router output also includes information about the adapter identifier in the interface specifier (slot/adapter/port).

debug ip mbgp

- Use to display information about MP-BGP logs for inbound or outbound events, or both.
- Example
  `
  host1#debug ip mbgp
  `
- There is no no version, but you can use the undebug ip mbgp command to disable display of information previously enabled with the debug ip mbgp command.
- See debug ip mbgp.

show ip bgp next-hops

- Use to display information about BGP next hops.
- Specify all VRFs or a particular VRF, and all indirect next hops or a particular indirect next hop.
- Field descriptions
  - Indirect next-hop—BGP next-hop attribute as received in the BGP update message
  - Resolution—Describes where the indirect next hop is resolved: the IP routing table, the IP tunnel routing table, or both, and whether this is in a VR or VRF
  - IP indirect next-hop index—Index number of the IP indirect next hop that this BGP indirect next hop resolves to
  - MPLS indirect next-hop index—Index number of the MPLS indirect next hop that this BGP indirect next hop resolves to
  - Reachable—Indicates whether or not the indirect next hop is reachable.

    For labeled unicast routes, the following rules apply:

    - When it is received from a nonmultihop peer, the indirect next hop is reachable if the MPLS major interface next to the peer IP interface exists and is operationally up.
    - When it is received from other types of peers,the indirect next hop is reachable if an entry exists in the IP tunnel routing table that resolves this indirect next-hop address.

    For unlabeled unicast routes, the following rules apply:

    - When it is received from an nonmultihop peer, the indirect next hop is reachable through the directly connected peer interface.
    - When it is received from other type of peers, the indirect next hop is reachable if an entry exists in the IP routing table that resolves this indirect next-hop address.

    For VPN labeled routes in a VRF, the following rules apply:

    - When it is received in a core VRF from a remote multihop IBGP or EBGP VPN peer, the indirect next hop is reachable if an entry exists in the IP tunnel routing table that resolves the next-hop address.
    - When it is received in a core VRF from a nonmultihop peer, the indirect next hop is reachable if the MPLS major interface next to the peer IP interface exists and is operationally up.
  - Metric—Metric of the BGP indirect next hop
  - Number of direct next-hops—Number of the equal-cost legs of direct next hops that this indirect next hop resolves to
  - Direct next-hop—IP interface and next-hop IP address that resolve the BGP indirect next hop; the direct next hop can also be an IP indirect next hop or an MPLS indirect next hop when chains of next hops are in use
  - Reference count—Number of label mappings of BGP routes that use this next hop
- Examples

      host1:pe2#show ip bgp vpnv4 all next-hops
      Indirect next-hop 10.1.1.1
        Resolution in IP route table of VR
             IP indirect next-hop index 10
             Reachable (metric 3)
             Number of direct next-hops is 1
                    Direct next-hop ATM4/1.20 (10.20.20.1)
        Resolution in IP tunnel-route table of VR
             MPLS indirect next-hop index 17
             Reachable (metric 3)
             Number of direct next-hops is 1
                    Direct next-hop: MPLS next-hop 18
        Reference count is 1

      Indirect next-hop 10.21.21.2
        Resolution in IP route table of VR
             IP indirect next-hop index 5
             Reachable (metric 0)
             Number of direct next-hops is 1
                    Direct next-hop ATM4/0.21 (10.21.21.2)
        Resolution in IP tunnel-route table of VR
             MPLS indirect next-hop index 14
             Reachable (metric 0)
             Number of direct next-hops is 1
                    Direct next-hop ATM4/0.21.mpls
        Reference count is 3

      host1:pe2#show ip bgp vpnv4 vrf pe22 next-hops
      Indirect next-hop 10.61.61.2
        Resolution in IP route table of VRF pe22
             IP indirect next-hop index 3
             Reachable (metric 0)
             Number of direct next-hops is 1
                    Direct next-hop ATM4/0.61 (10.61.61.2)
        Resolution in IP tunnel-route table of VRF pe22
             Not reachable
        Reference count is 2

- See show ip bgp next-hops.

show ip interface vrf

- Use to display information about the interfaces associated with the specified VRF.
- Field descriptions
  - interface—Interface type and interface specifier
  - interface status—Status of the interface
  - line protocol—Status of the line protocol
  - Link up/down trap—Status of SNMP link up/down traps on the interface
  - Internet address—IP address of the interface
  - Operational MTU—Actual MTU for the interface
  - Administrative MTU—Configured MTU for the interface
  - Operational speed—Actual speed
  - Administrative speed—Configured speed
  - Discontinuity Time—Value of sysUpTime the last time the integrity of the interface statistics was compromised
  - Router advertisement—Whether routes are advertised; enabled or disabled
  - Administrative debounce-time—Configured debounce behavior, enabled or disabled. If enabled, indicates time in milliseconds that the router waits before generating an up or down event in response to a state change in the interface. If the state changes back before the debounce timer expires, no state change is reported.
  - Operational debounce-time—Current debounce behavior, enabled or disabled. If enabled, indicates time in milliseconds that the router waits before generating an up or down event in response to a state change in the interface. If the state changes back before the debounce timer expires, no state change is reported.
  - Access routing—When enabled, an access route is installed to the host on the other end of the interface
  - Multipath mode—Algorithm used for ECMP: hashing of destination address and source address, or round-robin
  - In Received Packets, Bytes—Total number of packets and bytes received on an IP interface
    - Unicast—Number of unicast packets and bytes received on an IP interface
    - Multicast—Number of multicast packets and bytes received on an IP interface
  - In Policed Packets—Number of packets discarded on a receive IP interface because of token bucket limiting
  - In Error Packets—Number of packets discarded on a receive IP interface because of IP header errors
  - In Invalid Source Address Packets—Number of packets discarded on a receive IP interface because of invalid IP source address (sa-validate enabled)
  - Out Forwarded Packets, Bytes—Number of packets and bytes forwarded out an IP interface
    - Unicast—Number of unicast packets and bytes forwarded out an IP interface
    - Multicast—Number of multicast packets and bytes forwarded out an IP interface
  - Out Scheduler Drops Committed Packets—Number of committed packets dropped because of out queue threshold limit
  - Out Scheduler Drops Conformed Packets—Number of conformed packets dropped because of out queue threshold limit
  - Out Scheduler Drops Exceeded Packets—Number of exceeded packets dropped because of out queue threshold limit
  - Out Policed Packets—Number of packets discarded on a forwarding IP interface because of token bucket limiting
- Examples

      host1#show ip interface vrf vpn1
      null0 is up, line protocol is up
        Network Protocols: IP
        Internet address is 255.255.255.255/255.255.255.255
        Broadcast address is 255.255.255.255
        Operational MTU = 1500  Administrative MTU = 0
        Operational speed = 100000000  Administrative speed = 0
        Discontinuity Time = 0
        Router advertisement = disabled
        Administrative debounce-time = disabled
        Operational debounce-time    = disabled
        Access routing = disabled
        Multipath mode = hashed

      atm4/0.77 is up, line protocol is up
        Network Protocols: IP
        Internet address is 7.8.7.7/255.255.255.0
        Broadcast address is 255.255.255.255
        Operational MTU = 9180  Administrative MTU = 0
        Operational speed = 155520000  Administrative speed = 0
        Discontinuity Time = 0
        Router advertisement = disabled
        Administrative debounce-time = disabled
        Operational debounce-time    = disabled
        Access routing = disabled
        Multipath mode = hashed

        In Received Packets 0, Bytes 0
          Unicast Packets 0, Bytes 0
          Multicast Packets 0, Bytes 0
        In Policed Packets 0, Bytes 0
        In Error Packets 0
        In Invalid Source Address Packets 0
        Out Forwarded Packets 0, Bytes 0
          Unicast Packets 0, Bytes 0
          Multicast Packets 0, Bytes 0
        Out Scheduler Drops Committed Packets 0, Bytes 0
        Out Scheduler Drops Conformed Packets 0, Bytes 0
        Out Scheduler Drops Exceeded  Packets 0, Bytes 0
        Out Policed Packets 0, Bytes 0

      host1#show ip interface vrf vpn1 brief
      Interface              IP-Address     Status Protocol Description
      null0                  255.255.255.255  up         up
      atm4/0.77              7.8.7.7          up         up

- See show ip interface vrf.

show ip protocols

- Use to display information about the routing protocols associated with the VRF.
- You must specify the name of the VRF for which the protocols are displayed; otherwise, the command displays all protocols configured on the router
- Field descriptions
  - For BGP:
    - Redistributing—Protocol to which BGP is redistributing routes
    - Default local preference—Local preference value
    - IGP synchronization—Status of IGP synchronization: enabled, disabled
    - Always compare MED—Status of multiexit discrimination: enabled, disabled
    - Router flap damping—Status of route dampening: enabled, disabled
    - Administrative Distance—External, internal, and local administrative distances
    - Neighbor Address—IP address of the BGP neighbor
    - Neighbor Incoming/Outgoing update distribute list—Number of the access list for outgoing routes
    - Neighbor Incoming/Outgoing update prefix list—Number of the prefix list for incoming or outgoing routes
    - Neighbor Incoming/Outgoing update prefix tree—Number of the prefix tree for incoming or outgoing routes
    - Neighbor Incoming/Outgoing update filter list—Number of filter list for incoming routes
    - Routing for Networks—The network for which BGP is currently injecting routes
  - For IS-IS:
    - System Id—6-byte value of the router
    - IS-Type—Routing type of the router: Level 1, Level 2
    - Distance—Administrative distance for IS-IS learned routes
    - Address Summarization—Aggregate addresses defined in the routing table for multiple groups of addresses at a given level or routes learned from other routing protocols
    - Routing for Networks—Network for which IS-IS is currently injecting routes
  - For OSPF:
    - Router ID—OSPF process ID for the router
    - Distance—Administrative distance for OSPF learned routes
    - Redistributing—Protocol to which OSPF is redistributing routes
    - Address Summarization—Aggregate addresses defined in the routing table for multiple groups of addresses at a given level or routes learned form other routing protocols
    - Routing for Networks—Network for which OSPF is currently injecting routes
  - For RIP:
    - Router Administrative State—RIP protocol state. Enable means it is allowed to send and receive updates. Disable means that it may be configured but it is not allowed to run yet.
    - System Version—RIP versions allowed for sending and receiving RIP updates. The system version is currently set to RIP1, which sends RIP version 1 but will receive version 1 or 2. If the version is set to RIP2, the system will send and receive version 2 only. The default is configured for RIP1.
    - Update interval—Current setting of the update timer (in seconds)
    - Invalid after—Current setting of the invalid timer (in seconds)
    - hold down time—Current setting of the hold down timer (in seconds)
    - flushed interval—Current setting of the flush timer (in seconds)
    - Filter applied to outgoing route update—Access list applied to outgoing RIP route updates
    - Filter applied to incoming route update—Access list applied to incoming RIP route updates
    - Global route map—Route map that specifies all RIP interfaces on the router
    - Distance—Value added to RIP routes added to the IP routing table. The default is 120.
    - Interface—Interface type on which RIP protocol is running
    - Redistributing—Protocol to which RIP is redistributing routes
    - Routing for Networks—Network for which RIP is currently injecting routes
- Example

      host1:pe1#show ip protocols vrf pe13
      Routing Protocol is “ ospf 1" with Router ID 13.13.13.1
        Distance is 110
      Redistributing: bgp
        Address Summarization:
          None
        Routing for Networks:
          13.13.13.0/255.255.255.0 area 0.0.0.0

- See show ip protocols.

show ip route vrf

- Use to display the routing table of the specified VRF.
- Field descriptions
  - Protocol/Route type codes—Type of route
  - Prefix/Length—Network prefix for route in VRF routing table
  - Type—Protocol of route
  - Next Hop—IP address of the next hop to reach route
  - Dist/Met—Administrative distance and metric applied to route
  - Intf—Outgoing interface to reach route
- Example

      host1#show ip route vrf vpn2
      Protocol/Route type codes:
      I1- ISIS level 1, I2- ISIS level2,
      I- route type intra, IA- route type inter, E- route type external,
      i- metric type internal, e- metric type external,
      O- OSPF, E1- external type 1, E2- external type2,
      N1- NSSA external type1, N2- NSSA external type2

      Prefix/Length   Type     Next Hop    Dist/Met     Intf
      --------------- -------  ----------  --------      ------------
      45.5.5.5/32     Connect  45.5.5.5    0/1           fastEthernet3/0
      56.5.5.0/24     Connect  56.5.5.5    0/1           atm4/0.21

- See show ip route.

show ip vrf

- Use to display brief information about the VRFs in this virtual router: The route target of each VRF and the interfaces attached to each VRF.
- Specify the VRF name to display the brief information only about that VRF. You must be within the context of the virtual router to which the VRF belongs.
- Field descriptions
  - VRF Name—Name of each VRF
  - Default RD—Default route distinguisher for the VRF
  - Interfaces—Interfaces configured for the VRF
- Examples

      host1#show ip vrf
      VRF Name        Default RD         Interfaces
       vpn1           1:1                null0
                                         atm4/0.77
       vpn2           1:3                null0
                                         fastEthernet3/0
                                         atm4/0.21

      host1#show ip vrf vpn1
      VRF Name        Default RD         Interfaces
       vpn1           1:1                null0
                                         atm4/0.77

- See show ip vrf.

show ip vrf detail

- Use to display detailed information about the VRFs in this virtual router.
- Specify the VRF name to display the brief information only about that VRF. You must be within the context of the virtual router to which the VRF belongs.
- Field descriptions
  - VRF—Name of the VRF
  - Default RD—Default route distinguisher for the VRF
  - VRF IP Router Id—IP address that uniquely identifies the router
  - Default TTL—Time to live value in the IP header
  - Reassemble Timeout—Value to time out reassembled packets
  - Interface Configured—Interface configured for the VRF
  - Import VPN Route Target Extended Communities—List of VPNs from which the VRF accepts routing information
  - Export VPN Route Target Extended Communities—List of VPNs to which the VRF sends update messages
  - Import Route-map—Route map associated with the VRF that filters and modifies routes imported to the VRF from the global BGP VPN RIB. The map applies to both IPv4 and IPv6 routes, unless the field name is preceded by IPv4 (applies the map to only IPv4 routes) or IPv6 (applies the map to only IPv6 routes).
  - Export Route-map—Route map associated with the VRF that modifies and filters routes exported by the VRF to the global BGP VPN RIB. The map applies to both IPv4 and IPv6 routes, unless the field name is preceded by IPv4 (applies the map to only IPv4 routes) or IPv6 (applies the map to only IPv6 routes). The can filter routes text appears only if the filter keyword was issued for export map.
  - Global Import Route-map—Route map associated with the VRF that modifies routes imported to the VRF from the global BGP non-VPN RIB. The map applies to both IPv4 and IPv6 routes, unless the field name is preceded by IPv4 (applies to only IPv4 routes) or IPv6 (applies to only IPv6 routes).
  - Global Export Route-map—Route map associated with the VRF that modifies routes exported by the VRF to the global BGP non-VPN RIB. The map applies to both IPv4 and IPv6 routes, unless the field name is preceded by IPv4 (applies the map to only IPv4 routes) or IPv6 (applies the map to only IPv6 routes).
- Example

      host1:pe1#show ip vrf detail
      VRF  pe11; Default RD 100:11
        VRF IP Router Id: 10.11.11.1
        Default TTL: 127
        Reassemble Timeout: 30
        Interface Configured:
          null0  ATM2/0.11   tun mpls:vpnEgL17-3  ip dyn-24
        Import VPN Route Target Extended Communities:
           100:1
        Export VPN Route Target Extended Communities:
           100:1
        IPv4 Import Route-map: my-v4-import-map
        IPv6 Import Route-map: my-v6-import-map
        IPv4 Export Route-map: my-v4-export-map (can not filter routes)
        IPv6 Export Route-map: my-v6-export-map (can filter routes)
        IPv4 Global Import Route-map: my-v4-global-import-map (max routes 5000)
        IPv6 Global Import Route-map: my-v6-global-import-map (max routes 1000)
        IPv4 Global Export Route-map: my-global-v4-export-map
        IPv6 Global Export Route-map: my-global-v6-export-map
        VRF  pe12; Default RD 100:12
        VRF IP Router Id: 10.12.12.1
        Default TTL: 127
        Reassemble Timeout: 30
        Interface Configured:
          null0  ATM2/0.12   tun mpls:vpnEgL18-4  ip dyn-25
        Import VPN Route Target Extended Communities:
           100:2
        Export VPN Route Target Extended Communities:
           100:2
        Import Route-map : importmap1
        Export Route-map : exportmap23 (can filter routes)
        Global Import Route-map : globalimportmap2
        Global Export Route-map : globalexportmap3
        VRF  pe13; Default RD 100:13
        VRF IP Router Id: 10.13.13.1
        Default TTL: 127
        Reassemble Timeout: 30
        Interface Configured:
          null0  ATM2/0.13 tun mpls:vpnEgL19-5 ip dyn-26
        Import VPN Route Target Extended Communities:
           100:3
        Export VPN Route Target Extended Communities:
           100:3
        No Import Route-map
        No Export Route-map
        No Global Import Route-map
        No Global Export Route-map

- See show ip vrf.

show ip vrf interfaces

- Use to display summary information about all interfaces associated with all VRFs configured in a virtual router.
- Use the detail keyword to display detailed information about the interfaces.
- Field descriptions
  - Interface—Interface type and interface specifier
  - IP-Address—IP address of the interface
  - Status—Status of the interface
  - Protocol—Status of the line protocol
  - VRF—Name of the VRF with which the interface is associated
  - interface status—Status of the interface
  - line protocol—Status of the line protocol
  - Link up/down trap—Status of SNMP link up/down traps on the interface
  - Internet address—IP address of the interface
  - IP Statistics Rcvd:
    - local destination—Frames with this router as their destination
    - hdr errors—Number of packets containing header errors
    - addr errors—Number of packets containing addressing errors
    - unkn proto—Number of packets received containing unknown protocols
    - discards—Number of discarded packets
  - IP Statistics Frags:
    - reasm ok—Number of reassembled packets
    - reasm req—Number of requests for reassembly
    - reasm fails—Number of reassembly failures
    - frag ok—Number of packets fragmented successfully
    - frag creates—Number of frames requiring fragmentation
    - frag fails—Number of packets unsuccessfully fragmented
  - IP Statistics Sent:
    - generated—Number of packets generated
    - no routes—Number of packets that could not be routed
    - discards—Number of packets that could not be routed that were discarded
  - ICMP Statistics Rcvd:
    - errors—Number of error packets received
    - dst unreach—Number of packets received with destination unreachable
    - time exceed—Number of packets received with time-to-live exceeded
    - param probs—Number of packets received with parameter errors
    - src quench—Number of source quench packets received
    - redirect—Number of receive packet redirects
    - echo req—Number of echo request (PING) packets
    - echo rpy—Number of echo replies received
    - timestamp req—Number of requests for a timestamp
    - timestamp rpy—Number of replies to timestamp requests
    - addr mask req—Number of address mask requests
    - addr mask rpy—Number of address mask replies
  - ICMP Statistics Sent:
    - errors—Number of error packets sent
    - dst unreach—Number of packets sent with destination unreachable
    - time excd—Number of packets sent with time-to-live exceeded
    - param probs—Number of packets sent with parameter errors
    - src quench—Number of source quench packets sent
    - redirect—Number of send packet redirects
    - timestamp req—Number of requests for a timestamp
    - timestamp rpy—Number of replies to timestamp requests
    - addr mask req—Number of address mask requests
    - addr mask rpy—Number of address mask replies
  - In Received Packets, Bytes—Total number of packets and bytes received on an IP interface
    - Unicast—Number of unicast packets and bytes received on an IP interface
    - Multicast—Number of multicast packets and bytes received on an IP interface
  - In Forwarded Packets, Bytes—Number of packets and bytes forwarded into an output IP interface
  - In Total Dropped Packets, Bytes—Total number of packets and bytes discarded on a receive IP interface
  - In Policed Packets—Number of packets discarded on a receive IP interface because of token bucket limiting
  - In Invalid Source Address Packets—Number of packets discarded on a receive IP interface because of invalid IP source address (sa-validate enabled)
  - In Error Packets—Number of packets discarded on a receive IP interface because of IP header errors
  - In Discarded Packets—Number of packets discarded on the ingress interface because of a configuration problem rather than a problem with the packet itself
  - In Fabric Dropped Packets—Number of packets discarded on a receive IP interface because of internal fabric congestion
  - Out Forwarded Packets, Bytes—Number of packets and bytes forwarded out an IP interface
    - Unicast—Number of unicast packets and bytes forwarded out an IP interface
    - Multicast—Number of multicast packets and bytes forwarded out an IP interface
  - Out Requested Packets, Bytes—Number of packets and bytes requested to be forwarded out an IP interface
  - Out Total Dropped Packets, Bytes—Total number packets and bytes dropped by an IP interface on output
  - Out Scheduler Drops Committed Packets, Bytes—Number of committed packets and bytes dropped because of out queue threshold limit
  - Out Scheduler Drops Conformed Packets, Bytes—Number of conformed packets and bytes dropped because of out queue threshold limit
  - Out Scheduler Drops Exceeded Packets, Bytes—Number of exceeded packets and bytes dropped because of out queue threshold limit
  - Out Policed Packets—Number of packets discarded on the egress interface because of token bucket limiting
  - Out Discarded Packets—Number of packets discarded on the egress interface because of a configuration problem rather than a problem with the packet itself
  - Out Fabric Dropped Packets—Number of packets dropped because of internal fabric congestion
- Examples

      host1:PE1#show ip vrf interfaces
      Interface              IP-Address        Status Protocol   VRF
      null0                  255.255.255.255/32  up         up   pe11
      atm4/0.134             4.4.4.2/24          up         up   pe11
      null0                  255.255.255.255/32  up         up   pe12
      ip0                    6.6.6.8/24          up         up   pe12
      null0                  255.255.255.255/32  up         up   pe13
      loopback1              7.7.7.2/24          up         up   pe13

      host1:PE1#show ip vrf interfaces detail
      null0 is up, line protocol is up
        VRF: pe11
        Link up/down trap is disabled

        Internet address is 255.255.255.255/255.255.255.255
      IP statistics:
        Rcvd:  0 local destination
               0 hdr errors, 0 addr errors
               0 unkn proto, 0 discards
        Frags: 0 reasm ok, 0 reasm req, 0 reasm fails
               0 frag ok, 0 frag creates, 0 frag fails
        Sent:  0 generated, 0 no routes, 0 discards
      ICMP statistics:
        Rcvd:  0 errors, 0 dst unreach, 0 time exceed
               0 param probs, 0 src quench, 0 redirect,
               0 echo req, 0 echo rpy
               0 timestmp req, 0 timestmp rpy
               0 addr mask req, 0 addr mask rpy
        Sent:  0 errors, 0 dst unreach, 0 time excd
               0 param probs, 0 src qnch, 0 redirect
               0 timestamp req, 0 timestamp rpy
               0 addr mask req, 0 addr mask rpy

      atm4/0.134 is up, line protocol is up
        VRF: pe11
        Link up/down trap is disabled

        Internet address is 4.4.4.2/255.255.255.0
      IP statistics:
        Rcvd:  0 local destination
               0 hdr errors, 0 addr errors
               0 unkn proto, 0 discards
        Frags: 0 reasm ok, 0 reasm req, 0 reasm fails
               0 frag ok, 0 frag creates, 0 frag fails
        Sent:  0 generated, 0 no routes, 0 discards
      ICMP statistics:
        Rcvd:  0 errors, 0 dst unreach, 0 time exceed
               0 param probs, 0 src quench, 0 redirect,
               0 echo req, 0 echo rpy
               0 timestmp req, 0 timestmp rpy
               0 addr mask req, 0 addr mask rpy
        Sent:  0 errors, 0 dst unreach, 0 time excd
               0 param probs, 0 src qnch, 0 redirect
               0 timestamp req, 0 timestamp rpy
               0 addr mask req, 0 addr mask rpy
      In Received Packets 0, Bytes 0
          Unicast Packets 0, Bytes 0
          Multicast Packets 0, Bytes 0
        In Forwarded Packets 0, Bytes 0
        In Total Dropped Packets 0, Bytes 0
          In Policed Packets 0
          In Invalid Source Address Packets 0
          In Error Packets 0
          In Discarded Packets 0
          In Fabric Dropped Packets 0

        Out Forwarded Packets 0, Bytes 0
          Unicast Packets 0, Bytes 0
          Multicast Packets 0, Bytes 0
        Out Requested Packets 0, Bytes 0
        Out Total Dropped Packets 0, Bytes 0
          Out Scheduler Drops Committed Packets 0, Bytes 0
          Out Scheduler Drops Conformed Packets 0, Bytes 0
          Out Scheduler Drops Exceeded  Packets 0, Bytes 0
          Out Policed Packets 0
          Out Discarded Packets 0
          Out Fabric Dropped Packets 0

- See show ip vrf.

show mpls l2transport load-balancing-group

- Use to display information about load-balanced Martini circuits.
- For a simpler view, the show mpls l2transport interface command displays only the currently active VLAN or S-VLAN subinterface. Because load-balanced circuits are configured on subinterfaces on multiple ports, only one of which is active at a given time, this command does not give a complete picture of the configuration.
- Use the member-circuits keyword to display circuit information for the group.
- Field descriptions
  - routed to/base LSP—Identifies address of the router at the other end of the tunnel and the base tunnel that is selected to forward the traffic
  - load-balancing group—Group number
  - Martini group-id—Martini group ID number for the interface
  - state—State of the interface
  - vc-id—VC ID number for the interface
  - mtu—Maximum transmission unit for the interface
  - In label—Label sent to upstream neighbor for route; statistics below this field are the aggregate statistics for traffic from the core
  - Out label—Label received from downstream neighbor for route; statistics below this field are the aggregate statistics for traffic to the core
  - pkts—Number of packets sent across tunnel
  - hcPkts—Number of high-capacity (64-bit) packets sent across tunnel
  - octets—Number of octets sent across tunnel
  - hcOctets—Number of high-capacity (64-bit) octets sent across tunnel
  - errors—Number of packets dropped for some reason before being sent
  - queue 0—Number of the queue for which statistics are being displayed and whether the queue is under traffic class control
  - traffic class—Name of traffic class
  - bound to—Interface to which queue is bound
  - Queue length—Size of queue in length and bytes
  - Forwarded—Number of forwarded packets and bytes
  - Dropped committed—Number of committed packets and bytes dropped
  - Dropped conformed—Number of conformed packets and bytes dropped
  - Dropped exceeded—Number of exceeded packets and bytes dropped
  - discardPkts—Number of packets discarded due to lack of buffer space before being sent
  - Member Interfaces—Information about the member interfaces for the circuit
  - Interface—Interface specifier and status; active indicates it is being used for traffic from the core; if active is not displayed, interface is not currently being used for traffic, but the statistics may be valid
  - member ports—Number and type of candidate ports configured for the group, including interface specifiers and state
  - member circuits—Number of member circuits configured for each port and for the group
- Example 1

      host1#show mpls l2transport load-balancing-group 100 member-circuits
      routed to 10.9.1.3  on base LSP  tun mpls:lsp-de090103-32-3e
        load-balancing-group 100
        Martini group-id 2 vc-id 200002 mtu 1500
        State UP
        In  Label 57 on stack
          0 pkts, 0 hcPkts, 0 octets
          0 hcOctets, 0 errors, 0 discardPkts

        Out Label 59 on  tun mpls:lsp-de090103-32-3e
          0 pkts, 0 hcPkts, 0 octets
          0 hcOctets, 0 errors, 0 discardPkts
          queue 0: traffic class best-effort, bound to atm-vc ATM6/0.1
            Queue length 0 bytes
            Forwarded packets 0, bytes 0
            Dropped committed packets 0, bytes 0
            Dropped conformed packets 0, bytes 0
            Dropped exceeded packets 0, bytes 0
        Member Interfaces
          Interface fastEthernet 2/0.2  active
            Incoming Traffic Statistics
              0 pkts, 0 hcPkts, 0 octets
              0 hcOctets, 0 errors, 0 discardPkts
            Outgoing Traffic Statistics
              0 pkts, 0 hcPkts, 0 octets
              0 hcOctets, 0 errors, 0 discardPkts
          Interface fastEthernet 3/0.2
            Incoming Traffic Statistics
              0 pkts, 0 hcPkts, 0 octets
              0 hcOctets, 0 errors, 0 discardPkts
            Outgoing Traffic Statistics
              0 pkts, 0 hcPkts, 0 octets
              0 hcOctets, 0 errors, 0 discardPkts

- Example 2

      host1#show mpls l2transport load-balancing-group member-circuits brief

      4 member ports:
            fastEthernet 2/0  down
            fastEthernet 3/0  30 member circuits
            fastEthernet 4/0  30 member circuits
            fastEthernet 5/0  30 member circuits
          90 member circuits

- See show mpls l2transport load-balancing-group.

show mpls tunnels

- Use to display status and configuration for all tunnels or for a specific tunnel in the current router context.
- A result of Incomplete Configuration in the display indicates either no tunnel endpoint or no label distribution protocol.
- Field descriptions
  - State—Status of tunnel, up or down
  - Out Label—In the default case for a BGP/MPLS VPN, the Variable Interface, which indicates that a packet exiting the interface is going through a variable interface and that one of the labels listed further in the display will be prepended to the packet
  - Mpls Statistics
    - pkts—Number of packets sent across tunnel
    - hcpkts—Number of high-capacity (64-bit) packets sent across tunnel
    - octets—Number of octets sent across tunnel
    - hcoctets—Number of high-capacity (64-bit) octets sent across tunnel
    - errors—Number of packets that are dropped for some reason before being sent
    - discardPkts—Number of packets that are discarded due to lack of buffer space before being sent
  - Labels—List of labels associated with the variable interface; one will be selected to be prepended to packets before being sent across tunnel
- Example

      host12#show mpls tunnels

      LSP vpnIngress-21 to   3.3.3.3
      State:  Up
      Out label is Variable Interface
      102 pkts, 0 hcPkts, 13464 octets
      0 hcOctets, 0 errors, 0 discardPkts
      Labels:
      16 17 18 19

- See show mpls tunnels.

undebug ip mbgp

- Use to disable the display of information about MP-BGP logs that was previously enabled with the debug ip mbgp command.
- Example
  `
  host1#undebug ip mbgp
  `
- There is no no version.
- See undebug ip mbgp.

[Contents] [Prev] [Next] [Index] [Report an Error]