Configuring WAN Backhaul Redundancy


This chapter describes how to configure WAN backhaul redundancy for cellular and WiMAX interfaces on the Cisco 1000 Series Connected Grid Routers (hereafter referred to as the Cisco CG-OS router).
The system software for the router is identified as the Cisco CG-OS software.

This chapter includes the following sections:

Information About WAN Backhaul Redundancy

Prerequisites for WAN Backhaul Redundancy

Configuring WAN Backhaul Redundancy

Verifying the WAN Backhaul Configuration

Monitoring Statistics

Configuration Example

Information About WAN Backhaul Redundancy

You can configure the Cisco CG-OS router to have redundant WAN backhauls within an Open Shortest Path First version 2 (OSPFv2) area by assigning link costs to cellular (3G) and WiMAX interfaces. The interface with the lower assigned link cost remains the primary link until that link goes down; and, then traffic automatically goes to the secondary link with the next lowest cost. In cases where the link with the higher cost fails, no redirect of traffic occurs because the Cisco CG-OS router by default routes all traffic to the link with the lowest cost.

IPSec virtual tunnels are configured between the Cisco CG-OS router and the head-end router (such as the Cisco ASR 1000 Series) to encapsulate the interface traffic (cellular and WiMAX). A tunnel for each of the interfaces is configured.

The router employs IKEv2 to authenticate the traffic running between the Cisco CG-OS router and the head-end router by using either pre-shared key (PSK) or RSA authentication.

A Generic Routing Encapsulation (GRE) tunnel (see RFC2784 and RFC2890) is built between the Cisco CG-OS router and the head-end router. The GRE tunnel allows IPv6 traffic within an OSPFv3 area to traverse the tunnel between the two routers without the packets being parsed or examined by either of the routers.

Figure 7-1 WAN Backhaul Redundancy Employing IPSec and GRE Tunnels

Prerequisites for WAN Backhaul Redundancy

When configuring for IPv4 traffic:

Ensure that your OSPFv2 network strategy and planning for your network is complete. For example, you must decide whether your network requires multiple areas.

You must be familiar with routing fundamentals to configure OSPFv2.

Enable the OSPFv2 feature on the Cisco CG-OS router (see Enabling OSPFv2).

Configure at least one interface for IPv4 that can communicate with a remote OSPFv2 neighbor.

When configuring for IPv6 traffic:

Ensure that your OSPFv3 network strategy and planning for your network is complete. For example, you must decide whether your network requires multiple areas.

You must be familiar with routing fundamentals to configure OSPFv3.

Enable the OSPFv3 feature on the Cisco CG-OS router (see Enabling OSPFv3).

Configure at least one interface for IPv6 that can communicate with a remote OSPFv3 neighbor.

Guidelines and Limitations

The Ethernet interface cannot currently be configured as a redundant WAN backhaul.

Configuring WAN Backhaul Redundancy


Tip Cisco recommends that you configure the feature on the Cisco CG-OS router in the order noted below.



Note An example configuration for the head-end router (and Cisco CG-OS router) is provided in the Configuration Example section. For details on configuring the Cisco ASR 1000 Series, refer to the following URL: http://www.cisco.com/en/US/partner/products/ps9343/index.html


BEFORE YOU BEGIN

Ensure that all of the requirements listed in the Prerequisites for WAN Backhaul Redundancy section are met before beginning to configure the Cisco CG-OS router.

DETAILED STEPS

To configure the loopback interface, follow these steps.

 
Command
Purpose

Step 1 

interface loopback number

Creates a path between the Cisco CG-OS router and the head-end router.

Step 2 

ip address ip address

Creates an IP address for the loopback interface.

Step 3 

ip router ospf instance-tag area area-id [secondaries none]

Creates an OSPFv2 area on the interface.

To configure the cellular interface, follow these steps.

 
Command
Purpose

Step 1 

chat-script gsm1 name

Defines the ATDT modem commands when the dialer is initiated to automate the connect procedure.

Step 2 

interface dialer number

Configures an external dialer interface.

Step 3 

dialer persistent

Initiates a dial-out when the connection disconnects to ensure the connection remains active.

Step 4 

dialer pool number

Creates a dialer pool.

Step 5 

dialer string gsm number

Specifies the number or string to call. Reference the name of the chat script in this command for call setup.

Step 6 

interface cellular slot/port

Configures the 3G cellular interface. Slot value range is 3 to 6. Port value is 1.

Step 7 

dialer pool-member number

Assigns membership to a defined dialer pool.

Step 8 

no shutdown

Brings up the port, administratively.

Step 9 

exit

Exits to the global configuration mode.

To configure the WiMAX interface, follow these steps.

 
Command
Purpose

Step 1 

wimax scan-list name

Sets a scan-list and enters the scan list mode.

Step 2 

channel {index number | frequency number | bandwidth number}

Configures the channel number, frequency, or bandwidth for the interface.

Step 3 

nap id nap-id priority value channel-index value

Defines the Network Access Provider (NAP) ID, priority, and channel for the interface.

nap-id-Must be in the following format: XX:XX:XX (maximum size of 64).

priority value-Any value in the range of 1 to 250.

channel-index value-Any value in the range of 0 to15.

Step 4 

nsp id nsp-id home

Defines the Network Service Provider (NSP) ID for the interface.

nsp-id-Must be in the following format: XX:XX:XX (maximum size of 64).

Step 5 

interface wimax slot/port

Configures the WiMAX cellular interface. Slot value range is 3 to 6. Port value is 1.

Step 6 

scan-list name

Attaches a scan list to the interface.

Step 7 

ip address ip address

Assigns an IP address to the interface.

Step 8 

no shutdown

Brings up the port, administratively.

Step 9 

exit

Enter exit to return to the global configuration mode.

To enable IKEv2 on the Cisco CG-OS router, follow these steps.

 
Command
Purpose

Step 1 

feature crypto ike

Enables IKEv2 on the Cisco CG-OS router.

Note To prevent loss of the IKEv2 configuration, do not disable IKEv2 when IPSec is enabled on the Cisco CG-OS router.

Step 2 

crypto ike domain ipsec

Configures the IKEv2 domain and enters the IKEv2 configuration submode.

Step 3 

identity hostname

(Optional) Configures the identity of the IKEv2 protocol. By default, the IP address of the Cisco CG-OS router is taken as the identity for IKEv2 protocol.

Note This command is optional when using pre-share key (PSK) authentication.

Step 4 

keepalive value

(Optional) Configures the frequency of keep alive messages sent between peers in the tunnel. Keep alive messages validate the ability of peers to send and receive traffic. Value can be any number between 120 and 86400 seconds. The default value is 3600 seconds.

Step 5 

policy value

Defines IKEv2 priority policy and enters the policy configuration submode. The lower the number, the higher the priority.

Step 6 

authentication method

Specifies the IKEv2 authentication method.

Method options are PSK (pre-share) and RSA signature (rsa-sig) authentication.

Note RSA is the default setting.

Step 7 

encryption enc_algo

(Optional) Specifies the encryption algorithm for the policy.

Options are:

3des-168-bit DES (3DES)

aes-AES-CBC

Default setting for the Cisco CG-OS router is aes.

Step 8 

hash hash_algo

(Optional) Configures the hash algorithm for the IKEv2 policy. Options are:

md5-HMAC-MD5

sha-HMAC-SHA1

Default setting for the Cisco CG-OS router is sha.

Step 9 

group DH_group

Configures the Diffie Hellman group for the policy. Options are:

1-768-bit Diffie Hellman group

2-1024-bit Diffie Hellman group

5-1536-bit Diffie Hellman group

Default setting for the Cisco CG-OS router is 2.

Step 10 

lifetime seconds value

(Optional) Specifies the IKEv2 SA lifetime for the policy. Value is a range from 600 to 86400 seconds. Default setting is 86400 seconds.

Step 11 

exit

Exits to the global configuration mode.

Step 12 

key pre-share key {address ip address | hostname name}

Configures the key that IKEv2 communicates to the peer (head-end router) ip address. The peer must have the same key in its configuration. Maximum per-shared ley length is 128.

To enable IPSec tunnelling on the Cisco CG-OS router and configure its parameters, follow these steps.

 
Command
Purpose

Step 1 

feature crypto ipsec virtual- tunnel

Enables IPSec tunnelling on the Cisco CG-OS router and creates a virtual tunnel interface.

Step 2 

crypto ipsec transform-set tx-form-name {txform | encr_txform auth_txform}

Configures a single transform set that is included within the IPSec protection profile.

Options for txform are:

esp-gcm 128-128-bit AES-GCM authenticated encryption AES-CBC

esp-gcm 256-256-bit AES-GCM authenticated encryption

Options for encr_txform are:

esp-aes 128 or esp-aes 256 AES-CBC

Options for auth_txform are:

esp-sha1-hmac or esp-sha256-hmac HMAC-SHA

Note The transform-set name (tx-form-name) defined here must match that transform-set name associated with the IPSec profile in below.

Step 3 

crypto ip sec profile profile-name

Configures an IPSec profile for attachment to the tunnel interface.

Step 4 

description text

(Optional) Allows the user to provide a description for the profile. The character limit is 64 characters.

Step 5 

set transform-set txfrom-name

Associates the transformation set to the currently configured IPSec profile (see above).

Step 6 

set pfs group

(Optional) Configures the Diffie-Hillman group for perfect forward secrecy for the IPSec tunnel. Options for group are as follows:

group 1-768-bit mode Diffie-Hillman

group 4-2048-bit mode Diffie-Hillman

group 2-1024-bit mode Diffie-Hillman

group 5-1536-bit mode Diffie-Hillman

By default, PFS is disabled.

Step 7 

set security-association lifetime [seconds] [kilobytes]

(Optional) Specifies the lifetime of the IPSec security association. When the configured lifetime value expires, a new security association is negotiated.

Lifetime can be expressed in both time (seconds, 120 to 86400) and data volume (kilobytes, 2560 to 4292967295).

The default time value is 3600 seconds.

The default data volume is 4608000 kilobytes.

Step 8 

exit

Exits to the global configuration mode.

To enable OSPFv2 processing on the Cisco CG-OS router, enter the following command in the global configuration mode.

 
Command
Purpose

Step 1 

router ospf instance-tag

Creates an OSPFv2 routing instance.

instance-tag-Internal identifier for the routing instance and can be an alphanumeric word or positive integer.

To enable OSPFv3 processing on the Cisco CG-OS router, enter the following command in the global configuration mode.

 
Command
Purpose

Step 1 

router ospfv3 instance-tag

Creates an OSPFv3 routing instance.

instance-tag-Internal identifier for the routing instance and can be an alphanumeric word or positive integer.

To enable tunneling on the Cisco CG-OS router, enter the following command in the global configuration mode.

 
Command
Purpose

Step 1 

feature tunnel

Enables tunneling on the Cisco CG-OS router.

To create an IPSec tunnel on the Cisco CG-OS router and define an OSPFv2 area on each of the interfaces (cellular and WiMAX), follow these steps to configure each interface.

An individual tunnel must be configured for each of the interfaces, cellular and WiMAX (see Figure 7-1).

 
Command
Purpose

Step 1 

interface tunnel number

Creates a virtual tunnel.

When configuring a 3G or WiMAX interface, number is any value from 1 to 4095.

Step 2 

ip address ip address

Assigns an IP address for the tunnel.

Step 3 

ip ospf cost interface-cost

Specifies the cost of sending a packet on an interface.

Step 4 

ip ospf dead-interval seconds

Sets the interval during which a router must receive at least one hello packet before the router declares that neighbor as down. The range in seconds is from 1 to 65535.

Step 5 

ip ospf hello-interval seconds

Sets the interval between hello packets that OSPFv2 sends on the interface. The range in seconds is from 1 to 65535.

Step 6 

ip ospf mtu-ignore

Disables the OSPFv2 MTU mismatch detection on database descriptor (DBD) packets.

Note This parameter allows systems with Cisco IOS (such as the head-end router) and the Cisco CG-OS router to communicate and must be configured.

Step 7 

ip router ospf instance-tag area area-id [secondaries none]

Creates an OSPFv2 area on the interface.

Step 8 

tunnel mode ipsec ipv4

Configures the encapsulation mode for the tunnel.

Step 9 

tunnel source {ip-address | interface-type slot-port}

Configures the source endpoint for the tunnel.

Step 10 

tunnel destination {ip-address | host-name}

Configures the destination endpoint for the tunnel.

Step 11 

no keepalive value

(Optional) Disables the keepalive value on the Cisco CG-OS router.

The keepalive value command configures the frequency of keep alive messages sent between peers in the tunnel. Keep alive messages validate the ability of peers to send and receive traffic. Value can be any number between 120 and 86400 seconds. The default value is 3600 seconds.

Step 12 

tunnel protection ipsec profile profile-name

Binds the IPSec protection profile to the tunnel interfaces.

Note The profile-name defined in this step must match the profile name assigned to the virtual tunnel interface in by using the crypto ip sec profile profile-name command.

Step 13 

no shutdown

(Optional) Brings the port up, administratively.

Step 14 

exit

Exits the interface configuration mode.

To configure a Generic Routing Encapsulation (GRE) tunnel on the Cisco CG-OS router, follow these steps.

 
Command
Purpose

Step 1 

interface tunnel number

Creates a GRE tunnel on an interface.

number-Any value from 1 to 4095.

Step 2 

ip address ip address

Assigns an IPv4 address to the tunnel interface.

Step 3 

ipv6 address addr

Assigns an IPv6 address to the tunnel interface. The format is A:B::C:D/length. The length range is 1 to 128.

Step 4 

ipv6 router ospfv3 instance-tag area area-id [secondaries none]

Creates an OSPFv3 area on the tunnel interface.

Step 5 

tunnel source {ip-address | interface-type slot-port}

Configures the source endpoint for the tunnel.

Step 6 

tunnel destination {ip-address | host-name}

Configures the destination endpoint for the tunnel.

Step 7 

no shutdown

(Optional) Brings the port up, administratively.

EXAMPLE

Cisco CG-OS Router Configuration

The following example shows how to configure the Cisco CG-OS router.

For details on the head-end router configuration, refer to the Head-End Router Configuration.

These commands show how to configure the loopback0 interface, the cellular interface, and the WiMAX interface and their parameters.

router(config)# interface loopback 0
router(config-if)# ip address 20.0.0.2/24
router(config-if)# ip router ospf 2 area 0.0.0.2
router(config-if)# exit
router(config)# chat-script gsm1 PROFILE1
router(config)# interface dialer 1
router(config-if)# dialer persistent
router(config-if)# dialer pool 1
router(config-if)# dialer string gsm 1
router(config-if)# exit
router(config)# interface cellular 3/1
router(config-if)# dialer pool-member 1
router(config-if)# no shutdown
router(config-if)# exit
router(config)# wimax scan-list aaa
router(config-if)# channel index 1 frequency 2550000 bandwidth 10Mhz
router(config-if)# nap id 00:00:01 priority 1 channel-index 1
router(config-if)# nsp id 00:00:01 home
router(config-if)# exit
router(config)# interface wimax 5/1
router(config-if)# scan-list aaa
router(config-if)# ip address 192.10.0.21/16
router(config-if)# no shutdown
router(config-if)# exit
router(config)#
 
   

These commands show how to enable IKEv2 on the Cisco CG-OS router.

router(config)# feature crypto ike
router(config)# crypto ike domain ipsec
router(config-ike-ipsec)# policy 10
router(config-ike-ipsec-policy)# authentication pre-share
router(config-ike-ipsec-policy)# group 5
router(config-ike-ipsec-policy)# exit
router(config-ike-ipsec)# key company123 address 11.0.0.1
router(config-ike-ipsec)# key company123 address 192.10.0.1
router(config-ike-ipsec)# key company123 address 192.168.168.1
router(config-ike-ipsec)# exit
router(config)#
 
   
These commands show how to enable IPSec tunnelling (and configure its parameters) on the  
Cisco CG-OS router.
 
   
router(config)# feature crypto ipsec virtual-tunnel
router(config)# crypto ipsec transform-set MyTransformSet esp-aes 128 esp-shal-hmac
router(config)# crypto ipsec profile MyProfile
router(config-ipsec-profile)# description VTI IPSec Profile
router(config-ipsec-profile)# set transform-set MyTransformSet
router(config-ipsec-profile)# exit
router(config)#
 
   

This command shows how to enable OSPFv2 processing on the Cisco CG-OS router.

router(config)# router ospf 2
 
   

This command shows how to enable OSPFv3 processing on the Cisco CG-OS router.

router(config)# router ospfv3 1
 
   

This command shows how to enable tunneling on the Cisco CG-OS router.

router(config)# feature tunnel
 
   
These commands show how to configure tunnels that transport WiMAX (tunnel 15) and cellular 
(tunnel 15) data within the IPSec virtual tunnel from the Cisco CG-OS router to the head-end router. 
 
   
router(config)# interface tunnel 15
router(config-if)# ip address 23.0.5.2/30
router(config-if)# ip ospf cost 100
router(config-if)# ip ospf dead-interval 20
router(config-if)# ip ospf hello-interval 5
router(config-if)# ip ospf mtu-ignore
router(config-if)# ip router ospf 2 area 0.0.0.2
router(config-if)# tunnel mode ipsec ipv4
router(config-if)# tunnel source wimax 5/1
router(config-if)# tunnel destination 192.10.0.1
router(config-if)# no keepalive
router(config-if)# tunnel protection ipsec profile MyProfile
router(config-if)# no shutdown
router(config-if)# exit
router(config)# interface tunnel 16
router(config-if)# ip address 23.0.6.2/30
router(config-if)# ip ospf cost 500
router(config-if)# ip ospf dead-interval 20
router(config-if)# ip ospf hello-interval 5
router(config-if)# ip ospf mtu-ignore
router(config-if)# ip router ospf 2 area 0.0.0.2
router(config-if)# tunnel mode ipsec ipv4
router(config-if)# tunnel source cellular 3/1
router(config-if)# tunnel destination 192.168.168.1
router(config-if)# no keepalive
router(config-if)# tunnel protection ipsec profile MyProfile
router(config-if)# no shutdown
router(config-if)# exit
router(config)#
 
   
These commands show how to configure a Generic Routing Encapsulation (GRE) tunnel on the  
Cisco CG-OS router.
 
   
router(config)# interface tunnel 1
router(config-if)# ip address 25.0.0.2/24
router(config-if)# ip address 25::2/64
router(config-if)# ipv6 router ospfv3 1 area 0.0.0.1
router(config-if)# tunnel source loopback 0
router(config-if)# tunnel destination 20.0.0.1
router(config-if)# no shutdown
router(config)#

Head-End Router Configuration

The following example shows how to configure the head-end router to communicate with the
Cisco CG-OS router defined above.

This sample configuration is for a Cisco ASR 1000 Series system operating with Cisco IOS. For more details on the Cisco ASR and its configuration, refer to the following URL: http://www.cisco.com/en/US/partner/products/ps9343/index.html

These commands show how to configure the loopback0 interface on the head-end router.

HeadEndRtr(config)# interface loopback 0
HeadEndRtr(config-if)# ip address 20.0.0.1 255.255.255.0
HeadEndRtr(config-if)# exit
HeadEndRtr(config)#
 
   

These commands show how to enable IKEv2 on the head-end router.

HeadEndRtr(config)# crypto ikev2 keyring MyIke2KeyRing
HeadEndRtr(config-ike)# peer wimax-cgr
HeadEndRtr(config-ike)# address 192.10.0.21
HeadEndRtr(config-ike)# pre-shared-key Cisco123
HeadEndRtr(config-ike)# peer cellular-cgr
HeadEndRtr(config-ike)# address 192.168.168.21
HeadEndRtr(config-ike)# pre-shared-key Cisco123
HeadEndRtr(config-ike)# exit
HeadEndRtr(config)# cryto ikev2 profile MyIke2Profile
HeadEndRtr(config-ike)# match fvrf any
HeadEndRtr(config-ike)# match identity remote address 192.10.0.21 255.255.255.255
HeadEndRtr(config-ike)# match identity remote address 192.168.168.19 255.255.255.255 
HeadEndRtr(config-ike)# authentication local pre-share
HeadEndRtr(config-ike)# authentication remote pre-share
HeadEndRtr(config-ike)# keyring MyIke2KeyRing
HeadEndRtr(config-ike)# exit
HeadEndRtr(config)# 
 
   

These commands show how to enable IPSec tunnelling and configure its parameters on the head-end router.

HeadEndRtr(config)# crypto ipsec transform-set AES128SHA1 esp-aes esp-sha-hmac
HeadEndRtr(config)# crypto ipsec profile IPSecProfile
HeadEndRtr(config-ipsec-profile)# set transform-set AES128SHA1
HeadEndRtr(config-ipsec-profile)# set ikev2-profile MyIke2Profile
HeadEndRtr(config-ipsec-profile)# responder-only
HeadEndRtr(config-ipsec-profile)# exit
HeadEndRtr(config)#
 
   

These commands show how to configure tunnels that transport WiMAX (tunnel 15) and
cellular (tunnel 16) data from the head-end router to the Cisco CG-OS router.

HeadEndRtr(config)# interface tunnel 15
HeadEndRtr(config-if)# ip address 23.0.5.1 255.255.255.252
HeadEndRtr(config-if)# ip ospf cost 100
HeadEndRtr(config-if)# ip ospf hello-interval 5
HeadEndRtr(config-if)# ip ospf mtu-ignore
HeadEndRtr(config-if)# tunnel source GigabitEthernet 0/2
HeadEndRtr(config-if)# tunnel mode ipsec ipv4
HeadEndRtr(config-if)# tunnel destination 192.10.0.21
HeadEndRtr(config-if)# tunnel protection ipsec profile IPSecProfile
HeadEndRtr(config-if)# exit
HeadEndRtr(config)# interface tunnel 16
HeadEndRtr(config-if)# ip address 23.0.6.1 255.255.255.252
HeadEndRtr(config-if)# ip ospf cost 500
HeadEndRtr(config-if)# ip ospf hello-interval 5
HeadEndRtr(config-if)# ip ospf mtu-ignore
HeadEndRtr(config-if)# tunnel source GigabitEthernet 0/1.168
HeadEndRtr(config-if)# tunnel mode ipsec ipv4
HeadEndRtr(config-if)# tunnel destination 192.168.168.21
HeadEndRtr(config-if)# tunnel protection ipsec profile IPSecProfile
HeadEndRtr(config-if)# exit
HeadEndRtr(config)# 
 
   

These command shows how to create a GRE tunnel on the head-end router.

HeadEndRtr(config)# interface tunnel 1
HeadEndRtr(config)# ip address 25.0.0.1 255.255.255.0
HeadEndRtr(config-if)# ip ospf mtu-ignore
HeadEndRtr(config-if)# ip address 25::1/64
HeadEndRtr(config-if)# ipv6 enable
HeadEndRtr(config-if)# ipv6 ospf mtu-ignore
HeadEndRtr(config-if)# ipv6 ospf 1 area 1
HeadEndRtr(config-if)# tunnel source loopback 0
HeadEndRtr(config-if)# tunnel destination 20.0.0.2
HeadEndRtr(config-if)# exit
HeadEndRtr(config)#
 
   

These command shows how to enable OSPFv3 processing, define OSPFv3 areas, and enable the OSPFv3 for IPv6 router configuration mode (which allows you to configure IPv6 parameters) on the head-end router.

HeadEndRtr(config)# router ospf 2
HeadEndRtr(config-router)# network 20.0.0.0 0.0.0.255 area 2
HeadEndRtr(config-router)# network 23.0.5.0 0.0.0.255 area 2
HeadEndRtr(config-router)# network 23.0.6.0 0.0.0.255 area 2
HeadEndRtr(config-router)# exit
HeadEndRtr(config)# ipv6 router ospf 1

Verifying the WAN Backhaul Configuration

To display the WAN backhaul configuration, enter any or all of the following commands on the Cisco CG-OS router:


Note The Cisco CG-OS software does not support the [vrf {vrf-name | all | default | management}] parameter in the commands listed below.


Command
Purpose

show crypto ike domain ipsec

Displays the IKEv2 configuration.

show crypto ike domain ipsec policy

Displays the configured IKEv2 policies.

show crypto ipsec profile profile_name

Displays all defined IPSec profiles.

show crypto ipsec transform set tx-form name

Displays all defined transform-sets.

show file volatile:///bhmgr.tcl

Confirms installation status of the backhaul manager script (loaded during manufacture) and location of the script.

show {ip ospf | ospfv3}

Displays the configuration of the selected option.

show ipv6 ospfv3 interface

Displays configured tunnels and their state and configuration.

show running-config {ospf | ospfv3}

Displays the currently running OSPFv2 or OSPFv3 configuration.

show running-config interface {wimax | cellular} slot/port

Displays the currently running WiMAX or cellular configuration.

show tunnel internal database reachability

Displays the configured tunnel names and IP addresses.


Monitoring Statistics

To display WAN backhaul statistics, enter the following commands:

Command
Purpose

show {ip ospf | ospfv3} policy statistics area area-id filter-list {in | out}

Displays the route policy statistics for an area for the selected option.

show {ip ospf | ospfv3 | ipv6 ospfv3} statistics

Displays event counters for the selected option.

show {ip ospf | opsfv3 | ipv6 ospfv3} traffic [interface-type slot/port]

Displays the packet counters for the selected option.


Configuration Example

See EXAMPLE.