Monitoring Layer 2 Services over GRE

You can monitor layer 2 services over GRE using the following show cbf connection, show frame-relay subinterface tunnel, and show gre tunnel commands.

    show cbf connection

• Use to display all configured CBF connections.
• Example

host1#show cbf connection

   serial 5/1:1.1 <--> tunnel gre:tunnel0.1

         serial 5/1:1.2 <--> tunnel gre:tunnel1.1

host1#show cbf connection all

     serial 5/1:1.1 --> tunnel gre:tunnel0.1

     serial 5/1:1.2 --> tunnel gre:tunnel1.1

     tunnel gre:tunnel1.1 --> serial 5/1:1.2

     tunnel gre:tunnel0.1 --> serial 5/1:1.1

    show frame-relay subinterface tunnel

• Use to display the state of a Frame Relay subinterface over a specified tunnel.
• The tunnel subinterface can be in one of the following states:

• Up - traffic can flow on the interface
• Offline - traffic cannot flow because hardware is unavailable
• Down - traffic cannot flow because of a problem in the interface at the current protocol layer
• LowerLayerDown - traffic cannot flow because of a problem in an interface at a lower protocol layer
• AdministrativelyDown - traffic cannot flow because of manual administrative intervention
• Dormant - indicates that the CBF-connected DLCI is inactive, possibly caused by a customer misconfiguration

• Use the optional delta keyword to specify that baselined statistics are to be shown.
• The brief keyword displays only the operational status of all configured subinterfaces.
• Field descriptions

• sub-interface - identifies the subinterface in slot/port:channel/subchannel.subinterface format
• status - status of the subinterface
• Time since last status change - time since the last status change on the subinterface
• In bytes - number of inbound bytes received on the subinterface
• In frames - number of inbound frames received on the interface
• In errors - number of inbound errors received on the subinterface
• In discards - number of inbound packets discarded
• In unknown protos - number of packets received on the subinterface with unknown protocols
• Out bytes - number of outbound bytes transmitted on the subinterface
• Out frames - number of outbound frames transmitted on the interface
• Out errors - number of outbound errors transmitted on the subinterface
• Out discards - number of outbound packets discarded

• Example

host1#show frame-relay subinterface tunnel gre:tunnel0.1

Frame relay sub-interface tunnel gre:tunnel0.1, status is up

Number of sub-interface down transitions is 0

Time since last status change 01:42:15

  In bytes: 0                      Out bytes: 0

  In frames: 0                     Out frames: 0

  In errors: 0                     Out errors: 0

  In discards: 0                   Out discards: 0

  In unknown protos: 0

host1#show frame-relay subinterface brief

Frame relay sub-interface hssi2/0.1, status is up

Frame relay sub-interface hssi2/1.1, status is up

Frame relay sub-interface hssi4/0.1, status is up

Frame relay sub-interface tunnel gre:ser60.1, status is up

Frame relay sub-interface tunnel gre:ser61.1, status is up

Frame relay sub-interface hssi4/1.1, status is up

    show gre tunnel

• Use to display information about a GRE tunnel or a list of GRE tunnel subinterfaces.
• You can view the number of GRE tunnels in a specific state.
• You can view the number of GRE tunnels associated with either an IP address or with an IP address on a virtual router.
• Field descriptions

• Tunnel name and status - name of tunnel and status: up or down
• Tunnel mtu - maximum transmission unit for the tunnel
• Tunnel source address - IP address of the source of the tunnel
• Tunnel destination address - IP address of the destination of the tunnel
• Tunnel transport virtual router - virtual router associated with the tunnel
• Tunnel checksum option - state of the checksum feature: enabled or disabled
• Tunnel sequence number option - state of the sequence number option: enabled or disabled
• Tunnel up/down trap - indicates whether or not the ERX system sends traps to SNMP when the operational state of the tunnels changes
• Tunnel server location - location of the tunnel server in slot/port format.
• Tunnel administrative state - configured state of the tunnel: up or down
• Statistics - details of packets received or transmitted by the tunnel
• Packets - number of packets received or transmitted by the tunnel
• Octets - number of octets received or transmitted by the tunnel
• Discards - number of packets not accepted by the tunnel
• Errors - number of packets with errors received or transmitted by the tunnel
• Data rx - received data
• Data tx - transmitted data

• Example

host1#show gre tunnel detail

GRE tunnel ser60 is Up

Tunnel operational configuration

  Tunnel mtu is '10240'

  Tunnel source address is '20.0.0.1'

  Tunnel destination address is '20.0.0.2'

  Tunnel transport virtual router is default

  Tunnel checksum option is disabled

  Tunnel sequence number option is enabled (628 tx / 628 rx)

  Tunnel up/down trap is enabled

  Tunnel-server location is 3/0

  Tunnel administrative state is Up

Statistics    packets              octets               discards   errors

  Data rx     627                  97381                0          0

  Data tx     628                  97423                0          0

GRE tunnel ser61 is Up

Tunnel operational configuration

  Tunnel mtu is '10240'

  Tunnel source address is '20.0.0.2'

  Tunnel destination address is '20.0.0.1'

  Tunnel transport virtual router is vr1

  Tunnel checksum option is disabled

  Tunnel sequence number option is enabled (628 tx / 628 rx)

  Tunnel up/down trap is enabled

  Tunnel-server location is 3/0

  Tunnel administrative state is Up

Statistics    packets              octets               discards   errors

  Data rx     627                  97381                0          0

  Data tx     628                  97381                1          0

2 GRE tunnels found