Cisco Broadband Wireless Gateway 2.2 Command Reference, IOS Release 12.4(24)YG2
Available Languages
Table Of Contents
Cisco Broadband Wireless Gateway 2.2 Command Reference, IOS Release 12.4(24)YG2
aaa accounting (wimax agw user group-list submode)
aaa accounting start wait-response
clear wimax agw redundancy statistics
maximum-traffic-rate-sustained
radius-server vsa send accounting wimax
radius-server vsa send authentication wimax
reference-point r6 keepalive max-failures-allowed
reference-point r6 keepalive timeout
reference-point r6 response retransmits
reference-point r6 response timeout
security subscriber address-filtering ingress
service-flow pre-defined profile
show wimax agw redundancy status
user-group (user group list configuration submode)
vlan (service flow direction cs-type submode)
vrf (user group configuration submode)
wimax agw r6 maximum base-station
wimax agw r6 maximum subscriber
wimax agw service-flow pak-classify-rule profile
wimax agw service-flow profile
wimax agw service-flow profile qos-info
Cisco Broadband Wireless Gateway 2.2 Command Reference, IOS Release 12.4(24)YG2
09 April 2010•
aaa accounting (wimax agw user group-list submode)
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
aaa accounting
To enable authentication, authorization, and accounting (AAA) accounting of requested services for billing or security purposes when you use RADIUS or TACACS+, use the aaa accounting command in global configuration mode. To disable AAA accounting, use the no form of this command.
aaa accounting {auth-proxy | system | network | exec | connection | commands level | dot1x} {default | list-name} [vrf vrf-name] {start-stop | stop-only | none} [broadcast] group group-name
no aaa accounting {auth-proxy | system | network | exec | connection | commands level | dot1x} {default | list-name} [vrf vrf-name] {start-stop | stop-only | none} [broadcast] group group-name
Syntax Description
Defaults
AAA accounting is disabled.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
General Information
Use the aaa accounting command to enable accounting and to create named method lists that define specific accounting methods on a per-line or per-interface basis.
Table 6 contains descriptions of keywords for AAA accounting methods.
In Table 6, the group radius and group tacacs+ methods refer to a set of previously defined RADIUS or TACACS+ servers. Use the radius-server host and tacacs-server host commands to configure the host servers. Use the aaa group server radius and aaa group server tacacs+ commands to create a named group of servers.
Cisco IOS software supports the following two methods of accounting:
•
•
Method lists for accounting define the way accounting will be performed. Named accounting method lists enable you to designate a particular security protocol to be used on specific lines or interfaces for particular types of accounting services. Create a list by entering values for the list-name argument where list-name is any character string used to name this list (excluding the names of methods, such as RADIUS or TACACS+) and method list keywords to identify the methods to be tried in sequence as given.
If the aaa accounting command for a particular accounting type is issued without a named method list specified, the default method list is automatically applied to all interfaces or lines (where this accounting type applies) except those that have a named method list explicitly defined. (A defined method list overrides the default method list.) If no default method list is defined, then no accounting takes place.
Note
For minimal accounting, include the stop-only keyword to send a "stop" record accounting notice at the end of the requested user process. For more accounting, you can include the start-stop keyword, so that RADIUS or TACACS+ sends a "start" accounting notice at the beginning of the requested process and a "stop" accounting notice at the end of the process. Accounting is stored only on the RADIUS or TACACS+ server. The none keyword disables accounting services for the specified line or interface.
To specify an accounting configuration for a particular VRF, specify a default system accounting method list, and use the vrf keyword and vrf-name argument. System accounting does not have knowledge of VRF unless specified.
When AAA accounting is activated, the network access server monitors either RADIUS accounting attributes or TACACS+ AV pairs pertinent to the connection, depending on the security method you have implemented. The network access server reports these attributes as accounting records, which are then stored in an accounting log on the security server. For a list of supported RADIUS accounting attributes, see the appendix "RADIUS Attributes" in the Cisco IOS Security Configuration Guide. For a list of supported TACACS+ accounting AV pairs, see the appendix "TACACS+ Attribute-Value Pairs" in the Cisco IOS Security Configuration Guide.
Note
Cisco Service Selection Gateway Broadcast Accounting
To configure Cisco Service Selection Gateway (SSG) broadcast accounting, use ssg_broadcast_accounting for the list-name argument. For more information about configuring SSG, see the chapter "Configuring Accounting for SSG" in the Cisco IOS Service Selection Gateway Configuration Guide, Release 12.4.
Layer 2 LAN Switch Port
You must configure the RADIUS server to perform accounting tasks, such as logging start, stop, and interim-update messages and time stamps. To turn on these functions, enable logging of "Update/Watchdog packets from this AAA client" in your RADIUS server Network Configuration tab. Next, enable "CVS RADIUS Accounting" in your RADIUS server System Configuration tab.
You must enable AAA before you can enter the aaa accounting command. To enable AAA and 802.1X (port-based authentication), use the following global configuration mode commands:
•
•
•
Use the show radius statistics command to display the number of RADIUS messages that do not receive the accounting response message.
Examples
The following example defines a default commands accounting method list, where accounting services are provided by a TACACS+ security server, set for privilege level 15 commands with a stop-only restriction.
aaa accounting commands 15 default stop-only group tacacs+The following example defines a default auth-proxy accounting method list, where accounting services are provided by a TACACS+ security server with a start-stop restriction. The aaa accounting command activates authentication proxy accounting.
aaa new-modelaaa authentication login default group tacacs+aaa authorization auth-proxy default group tacacs+aaa accounting auth-proxy default start-stop group tacacs+The following example defines a default system accounting method list, where accounting services are provided by RADIUS security server "server1" with a start-stop restriction. The aaa accounting command specifies accounting for vrf "vrf1."
aaa accounting system default vrf1 water start-stop group server1The following example defines a default IEEE 802.1x accounting method list, where accounting services are provided by a RADIUS server. The aaa accounting command activates IEEE 802.1x accounting.
aaa new modelaaa authentication dot1x default group radiusaaa authorization dot1x default group radiusaaa accounting dot1x default start-stop group radiusThe following example shows how to enable network accounting and send tunnel and tunnel-link accounting records to the RADIUS server. (Tunnel-Reject and Tunnel-Link-Reject accounting records are automatically sent if either start or stop records are configured.)
aaa accounting network tunnel start-stop group radiusaaa accounting network session start-stop group radiusThe following example shows how to enable IEEE 802.1x accounting:
aaa accounting dot1x default start-stop group radiusaaa accounting system default start-stop group radiusRelated Commands
aaa accounting (wimax agw user group-list submode)
To enable various flows on the BWG, use the aaa accounting command in wimax user group-list submode. Use the no form of this command to disable the various flows.
aaa accounting [ start | flow {start [include-framed-ip [delay]]} | host | method-list | update [handover]]
no aaa accounting [start | flow {start [include-framed-ip [delay]]} | host | method-list | update [handover]]
Syntax Description
Defaults
The accounting update handover is enabled by default. Sending the Framed-IP-Address field in the accounting start record is disabled by default.
Command Modes
Wimax agw user group-list configuration (config-gw-ug)
Command History
12.4(15)XL
This command was introduced.
12.4(15)XL3
The host keyword was added.
12.4(24)YG2
The start include-framed-ip and update handover keywords were added.
Usage Guidelines
Both flow-based and host-based accounting can be enabled or disabled under the user group. Further, both host and flow modes can be enabled simultaneously.
If host accounting is enabled for a user group, and every time a host (default host is known as the CPE, DHCP host behind the CPE is known as a Static Host) gets created on BWG, BWG initiates accounting by sending an Accounting Start request to the RADIUS server. An accounting stop request is sent if the session gets de-registered or the host gets deleted.
Framed-IP is often not included in the accounting start record for flow-accounting. In case of the initial service flow, the accounting start record is sent at the time of flow creation much before the subscriber host is created. From BWG release 2.2, you can delay the sending of the accounting start record until a host is created.
Examples
Here is a configuration and usage example of the aaa accounting host command:
router(config)#wimax agw user group-list wimaxrouter(config-gw-ugl)#user-group domain cisco2.comrouter(config-gw-ug)#aaa accounting ?flow User group AAA accounting flow commandshost User group AAA accounting host commandsmethod-list User group AAA accounting method list configuration commandsrouter(config-gw-ug)#aaa accounting host ?enable Enable User group AAA accounting per hostrouter(config-gw-ug)#aaa accounting host enableuser-group domain cisco2.comaaa accounting method-list agwsla profile-name goldip static-allowedsecurity subscriber address-filtering ingresssubscriber network-behindaaa accounting host enable!The following example shows how to enable the framed IP delay feature with the default delay of 3 seconds:
router(config-gw-ug)#aaa accounting flow start include-framed-ipThe following example shows how to enable the framed IP delay feature with the delay of 10 seconds:
router(config-gw-ug)#aaa accounting flow start include-framed-ip 10The following example shows how to disable the interim accounting update during handoffs:
router(config-gw-ug)#no aaa accounting update handoverThe following example shows how to include the Framed-IP-Address to the accounting start record:
user-group domain eapTls.comaaa accounting method-list agw-method_acct_1aaa accounting flow start include-framed-ip 20aaa accounting host enableaaa authentication method-list agw_method_eap-tls_auth_1sla profile-name eapTls.comdhcp gateway address 20.3.5.50dhcp server primary 22.3.5.50timeout cache-session 240vrf wimax-vrf1aaa accounting start wait-response
To configure the BWG to wait for a response of Accounting Start (both host and flow) from the AAA server, use the aaa accounting start wait-response command in User group configuration sub mode. Use the no form of the command to disable this feature. If no response is received from the AAA server, the related session is torn down.
aaa accounting start wait-response
no aaa accounting start wait-response
Syntax Description
There are no keyword or arguments for this command.
Defaults
There are no default values.
Command Modes
User group configuration sub mode.
Command History
Usage Guidelines
This feature closes a loophole, in that a subscriber will not be able to get a free use of the service when the AAA server is down or not reachable.
Examples
The following example illustrates how to enable the aaa accounting start wait-response command:
router(config-gw-ug# aaa accounting start wait-responseaaa accounting update
To enable periodic interim accounting records to be sent to the accounting server, use the aaa accounting update command in global configuration mode. To disable interim accounting updates, use the no form of this command.
aaa accounting update [newinfo] [periodic number [jitter {maximum max-value}]]
no aaa accounting update
Syntax Description
Defaults
Disabled
Command Modes
Global configuration
Command History
Usage Guidelines
•
•
•
•
•
•
Caution
Examples
The following example sends PPP accounting records to a remote RADIUS server. When IPCP completes negotiation, this command sends an interim accounting record to the RADIUS server that includes the negotiated IP address for this user; it also sends periodic interim accounting records to the RADIUS server at 30-minute intervals.
aaa accounting network default start-stop group radiusaaa accounting update newinfo periodic 30The following example sends periodic interim accounting records to the RADIUS server at 30-minute intervals and disables jitter:
aaa accounting update newinfo periodic 30 jitter maximum 0Related Commands
aaa accounting
Enables AAA accounting of requested services for billing or security purposes.
gw-accounting aaa
Enables VoIP gateway accounting through the AAA system.
aaa authentication
To specify one or more authentication, authorization, and accounting (AAA) methods for use on interfaces running IEEE 802.1X, use the aaa authentication dot1x command in global configuration mode. To disable authentication, use the no form of this command
aaa authentication dot1x {default | listname} method1 [method2...]
no aaa authentication dot1x {default | listname} method1 [method2...]
Syntax Description
Defaults
No authentication is performed.
Command Types
Global configuration
Command History
Usage Guidelines
The method argument identifies the list of methods that the authentication algorithm tries in the given sequence to validate the password provided by the client. The only method that is truly 802.1X-compliant is the group radius method, in which the client data is validated against a RADIUS authentication server. The remaining methods enable AAA to authenticate the client by using locally configured data. For example, the local and local-case methods use the username and password that are saved in the Cisco IOS configuration file. The enable and line methods use the enable and line passwords for authentication.
If you specify group radius, you must configure the RADIUS server by entering the radius-server host global configuration command. If you are not using a RADIUS server, you can use the local or local-case methods, which access the local username database to perform authentication. By specifying the enable or line methods, you can supply the clients with a password to provide access to the switch.
Use the show running-config privileged EXEC command to display the configured lists of authentication methods.
The aaa authentication method-list default indicates if the RADIUS Access Request is to be initiated from the BWG for the unauthenticated group, or not. In the absence of this command under an unauthenticated user group then, the BWG will not send an Access-Request to the AAA and the proxy realm password, and user auto-provisioned commands will not hold importance.
Examples
The following example shows how to create an authentication list. This authentication first tries to contact a RADIUS server. If this action returns an error, the user is allowed access with no authentication:
service wimax agwaaa new-model!!aaa authentication dot1x agw group radiusaaa authorization network default group radiusaaa accounting update periodic 1aaa accounting network agw start-stop group radius!!aaa session-id uniqueclock timezone PST -8clock calendar-validRelated Commands
aaa authentication ppp
To specify one or more authentication, authorization, and accounting (AAA) authentication methods for use on serial interfaces that are running PPP, use the aaa authentication ppp command in global configuration mode. To disable authentication, use the no form of this command.
aaa authentication ppp {default}
no aaa authentication ppp {default}
Syntax Description
default
Uses the listed authentication methods that follow this keyword as the default list of methods when a user logs in.
Defaults
If the default list is not set, only the local user database is checked. This has the same effect as that created by the following command:
aaa authentication ppp default localCommand Modes
Global configuration
Command History
Usage Guidelines
Note
The lists that you create with the aaa authentication ppp command are used with the ppp authentication command. These lists contain up to four authentication methods that are used when a user tries to log in to the serial interface.
Create a list by entering the aaa authentication ppp list-name method command, where list-name is any character string used to name this list MIS-access. The method argument identifies the list of methods that the authentication algorithm tries in the given sequence. You can enter up to four methods. Method keywords are described in Table 7.
The additional methods of authentication are used only if the previous method returns an error, not if it fails. Specify none as the final method in the command line to have authentication succeed even if all methods return an error.
If authentication is not specifically set for a function, the default is none and no authentication is performed. Use the more system:running-config command to display currently configured lists of authentication methods.
Note
Cisco 10000 Series Router
The device supports a maximum of 2,000 AAA method lists. If you configure more than 2,000 AAA method lists, traceback messages appear on the console.
Examples
The following example shows how to create a AAA authentication list called MIS-access for serial lines that use PPP. This authentication first tries to contact a TACACS+ server. If this action returns an error, the user is allowed access with no authentication.
aaa authentication ppp MIS-access group tacacs+ noneHere is a sample configuration command for PAP authentication on the BWG.
!aaa authentication ppp default group radius!Related Commands
aaa pod server
To configure the POD feature on the BWG, use the aaa pod server global configuration command. Use the no form of the command to disable this feature.
aaa pod server [port port-number] [auth-type {any| all | session-key}] server-key [encryption-type] string
no aaa pod server [port port-number] [auth-type {any| all | session-key}] server-key [encryption-type] string
Syntax Description
Defaults
The default value for the port-number is 1700.
Command Modes
Global configuration.
Command History
Examples
The following example illustrates how to enable the aaa pod server command:
router(config)# aaa pod serverbridge group
To configure a bridge group in the BWG, use the bridge group command. Use the no form of this command to disable this function.
bridge group [value] {source learning | transparent-vlan [vlan-tag]}
no bridge group [value] {source learning | transparent-vlan [vlan-tag]}
Syntax Description
Defaults
There are no default values.
Command Modes
Privileged EXEC configuration (config).
Command History
Usage Guidelines
To enable bridging on a Wimax user group, the user group needs to be added to a bridge group. After the user group is added, a virtual Wimax interface (Wimax<bridge-grp>) is created. This virtual Wimax interface represents the user group in the bridge group. You cannot add Multiple user groups to the same bridge group.
Examples
The following example shows how to configure a bridge group and enable source learning:
router(config)#bridge group 23 source learningThe following example show how to configure L2-L2 bridging:
bridge irb!interface Ethernet1/1description Interface belong to bridge-group 1bridge-group 2no bridge-group 2 source-learningno ip address!bridge 2 protocol ieee!wimax agw user group-list wimaxuser-group anyaaa authentication method-list agwaaa accounting method-list agwsla profile-name silverbridge-group 2no bridge-group 2 source-learningbridge-group 2 transparent-vlan vlan-tagclear ip slb sticky asn msid
To clear the sticky entry in the BWG sticky database corresponding to the msid specified, use the clear ip slb sticky asn msid command in Privileged EXEC mode. Use the no form of the command to disable this function.
clear ip slb sticky asn msid {macid}
no clear ip slb sticky asn msid {macid}
Syntax Description
Defaults
There are no default values.
Command Modes
Privileged EXEC
Command History
Examples
The following example illustrates how to enable the clear ip slb sticky asn msid command:
router# clear ip slb sticky asn msidclear wimax agw path
To clear all the subscribers that belongs to a BS, or to re-sync the sessions with a specific BS, use the clear wimax agw path command in privileged EXEC mode. .
clear wimax agw path bs-ip-addr [local] [reset-bs] [dm-action [ms-reset | action-code 0-FFFF]]
Syntax Description
Defaults
There are no default values.
Command Modes
Privileged EXEC
Command History
12.4(15)XL
This command was introduced.
12.4(15)XL4
The reset-bs option was introduced
12.4(24)YG
The dm-action option was introduced.
Examples
The following example illustrates how to enable the clear wimax agw path command:
router#clear wimax agw path 10.10.10.10router#clear wimax agw path 10.10.10.10 localrouter#clear wimax agw path 10.10.10.10 reset-bsrouter#clear wimax agw path 10.10.10.10 dm-action ms-resetrouter#clear wimax agw path 10.10.10.10 dm-action action-code 0clear wimax agw redundancy statistics
To clear redundancy specific statistics, use the clear wimax agw redundancy statistics command in privileged EXEC configuration mode.
clear wimax agw redundancy statistics
Syntax Description
This command has no keywords or arguments.
Defaults
There are no default values.
Command Modes
Privileged EXEC configuration.
Command History
Usage Guidelines
You can use the clear wimax agw redundancy statistics command on the standby card without producing a warning message, but the redundancy statistics on the active and standby will not be in sync.
Examples
The following example clears all BWG redundancy statistics:
router#clear wimax agw redundancy statisticsclear wimax agw statistics
To clear statistics on the BWG, use the clear wimax agw statistics command in privileged EXEC configuration mode.
clear wimax agw statistics
Syntax Description
There are no keywords or arguments
Defaults
There are no default values.
Command Modes
Privileged EXEC configuration.
Command History
Usage Guidelines
You can use the clear wimax agw statistics command on the standby card without producing a warning message, but the statistics on the active and standby will not be in sync.
Examples
The following example illustrates the clear wimax agw statistics command:
router# clear wimax agw statisticsclear wimax agw subscriber
To clear the subscriber on the BWG, use the clear wimax agw subscriber command in privileged EXEC configuration mode.
clear wimax agw subscriber [msidac-id mac-id ] user-group [name group-name | any | unauthenticated] [local]
Syntax Description
Defaults
There are no default values.
Command Modes
Privileged EXEC configuration.
Command History
12.4(15)XL
This command was introduced.
12.4(15)XL4
The name, any, and unauthenticated keywords were added.
Usage Guidelines
Note
For example:
router#clear wimax agw subscriber allThis is STANDBY unit. This command must be issued on the ACTIVE unitExamples
The following example clears subscribers locally:
clear wimax agw subscriber localcs-type
To specify the cs-type profile under the corresponding direction, use the cs-type sub command. The no version of the command removes the cs-type information from the corresponding direction. Configuring the command opens a sub configuration mode to configure various cs-type commands.
cs-type {ethernet-cs | ip-cs}
no cs-type {ethernet-cs | ip-cs}
Syntax Description
ethernet-cs
Specifies ethernet as the convergence sublayer.
ip-cs
Specifies IP as the convergence sublayer.
Defaults
There are no default values.
Command Modes
Service flow direction configuration submode.
Command History
Usage Guidelines
Configuring the command opens a sub configuration mode to configure various cs-type commands.
Examples
The following example configures both cs-types:
wimax agw service-flow profile isfdirection downlinkcs-type ip-cspak-classify-rule isf-classifier-downlinkprecedence 1cs-type ethernet-cspak-classify-rule isf-classifier-downlinkprecedence 2qos-info isf-qos-downlink!direction uplinkcs-type ip-cspak-classify-rule isf-classifier-uplinkprecedence 1cs-type ethernet-cspak-classify-rule isf-classifier-uplinkprecedence 2vlan 2 vrf vrf_1vlan range 3 10 vrf vrf_2vrf-default vrf_1qos-info isf-qos-uplinkdata-delivery-service
To configure data delivery service associated with certain predefined set of QoS-related service flow parameters, use the data-delivery-service command in global configuration mode. Use the no form of the command to disable this feature.
data-delivery-service {unsolicited-grant | real-time-variable-rate | non-real-time-variable-rate | best-effort | extended-real-time-variable-rate}
no data-delivery-service
Syntax Description
Defaults
The default setting is unsolicited-grant.
Command Modes
Service flow QoS info configuration mode.
Command History
Examples
The following example illustrates how to configure the data-delivery-service command:
wimax agw service-flow qos-info profile isf-qos-downlinkdata-delivery-service real-time-variable-ratemaximum-latency 1maximum-traffic-burst 2maximum-traffic-rate-sustained 3media-flow-type 012041424344minimum-traffic-rate-reserved 4policy-transmission-request 5sdu-size 6tolerated-jitter 7traffic-priority 1unsolicited-interval-grant 8unsolicited-interval-polling 9wimax agw service-flow qos-info profile isf-qos-uplinkdata-delivery-service unsolicited-grantmaximum-latency 11maximum-traffic-burst 21maximum-traffic-rate-sustained 31minimum-traffic-rate-reserved 41policy-transmission-request 51sdu-size 61tolerated-jitter 71traffic-priority 3unsolicited-interval-grant 81unsolicited-interval-polling 91!wimax agw service-flow qos-info profile downlink-qos-02data-delivery-service real-time-variable-ratemedia-flow-type 05abcddebug aaa pod
To enable POD debugging on the BWG, use the debug aaa pod Privileged EXEC command.
debug aaa pod
Syntax Description
There are no keywords or arguments for this command.
Defaults
There are no default values.
Command Modes
Privileged EXEC.
Command History
Examples
The following example enables POD debugging on the BWG:
router# debug aaa poddebug condition
To enable conditional debugging on the BWG, use the debug condition command in privileged EXEC mode.
debug condition [mac-address mac-id-of-subscriber] [ip bs-ip-address]
Syntax Description
mac-address mac-id-of-subscriber]
based on the Subscriber MAC-ID
ip bs-ip-address
based on the BS IP address
Defaults
There are no default values.
Command Modes
Privileged EXEC.
Command History
Usage Guidelines
When there is option to branch in the debug CLI, all the options after the keyword can be enabled by using the carriage-return. For example:
To enable all the WiMAX BWG related debugs, enter:
router#debug wimax agwTo enable all the WiMAX BWG session related debugs, enter:
router#debug wimax agw sessionExamples
The following example enables conditional debugging on the BWG:
Router#debug condition mac-address mac-id-of-subscriberRotuer#debug condition ip bs-ip-addressdebug eap
To display debug output for EAP related events and errors, use the debug eap command in privileged EXEC mode. Use the no version of command to turn off debug output.
debug eap {all | authenticator | errors | events | packets | peer | sm}
no debug eap {all | authenticator | errors | events | packets | peer | sm}
Syntax Description
Defaults
No default values.
Command Modes
Privileged EXEC.
Command History
Examples
Here is sample output for the debug eap events command:
Router#debug eap eventsEAP authenticator events debugging is onEAP peer events debugging is onRouter#*Feb 22 08:58:46.351: EAP-EVENT: Received context create from lower layer (0x59000003)*Feb 22 08:58:46.351: EAP-AUTH-EVENT: Received AAA ID 0x00000005 from LL*Feb 22 08:58:46.351: EAP-AUTH-AAA-EVENT: Assigning AAA ID 0x00000005*Feb 22 08:58:46.351: EAP-EVENT: Allocated new EAP context (handle = 0xB4000003)*Feb 22 08:58:46.351: EAP-EVENT: Received event 'EAP_AUTHENTICATOR_START' on handle 0xB4000003*Feb 22 08:58:46.351: EAP-AUTH-EVENT: Current method = Identity*Feb 22 08:58:46.351: EAP-AUTH-EVENT: Sending packet to lower layer for context 0xB4000003*Feb 22 08:58:46.351: EAP-EVENT: Started 'Authenticator ReqId Retransmit' timer (5s) for EAP sesion handle 0xB4000003*Feb 22 08:58:46.351: EAP-EVENT: Started EAP tick timer*Feb 22 08:58:46.351: EAP-EVENT: Sending lower layer event 'EAP_TX_PACKET' on handle 0xB4000003*Feb 22 08:58:46.355: EAP-EVENT: Received event 'EAP_RX_PACKET' on handle 0xB4000003*Feb 22 08:58:46.355: EAP-AUTH-EVENT: EAP Response received by contextBWG# 0xB4000003*Feb 22 08:58:46.355: EAP-AUTH-EVENT: EAP Response type = Identity*Feb 22 08:58:46.355: EAP-EVENT: Stopping 'Authenticator ReqId Retransmit' timer for EAP sesion handle 0xB4000003*Feb 22 08:58:46.355: EAP-AUTH-EVENT: Received peer identity: swimeap@wimax.org*Feb 22 08:58:46.355: EAP-EVENT: Sending lower layer event 'EAP_GET_AAA_METHOD_LISTS' on handle 0xB4000003*Feb 22 08:58:46.355: EAP-EVENT: Sending lower layer event 'EAP_GET_PEER_MAC_ADDRESS' on handle 0xB4000003*Feb 22 08:58:46.355: EAP-EVENT: Sending lower layer event 'EAP_CUSTOMIZE_AAA_REQUEST' on handle 0xB4000003*Feb 22 08:58:46.355: EAP-AUTH-AAA-EVENT: Request sent successfully*Feb 22 08:58:46.359: EAP-EVENT: eap_aaa_reply*Feb 22 08:58:46.359: EAP-AUTH-AAA-EVENT: Server status: GET_CHALLENGE_RESPONSE*Feb 22 08:58:46.359: EAP-EVENT: Received event 'EAP_AAA_RX_PACKET' on handle 0xB4000003*Feb 22 08:58:46.359: EAP-AUTH-EVENT: Current method = 13*Feb 22 08:58:46.359: EAP-AUTH-EVENT: Sending packet to lower layerfor context 0xB4000003*Feb 22 08:58:46.359: EAP-EVENT: Started 'Authenticator Retransmit' timer (5s) for EAP sesion handle 0xB4000003*Feb 22 08:58:46.359: EAP-EVENT: Started EAP tick timer*Feb 22 08:58:46.359: EAP-EVENT: Sending lower layer event 'EAP_TX_PACKET' on handle 0xB4000003Router#Router#*Feb 22 08:58:51.479: EAP-EVENT: 'Authenticator Retransmit' timer expired for EAP sesion handle 0xB4000003*Feb 22 08:58:51.479: EAP-AUTH-EVENT: Resending last packet for context 0xB4000003*Feb 22 08:58:51.479: EAP-AUTH-EVENT: Sending packet to lower layer for context 0xB4000003*Feb 22 08:58:51.479: EAP-EVENT: Started 'Authenticator Retransmit' timer (5s) for EAP sesion handle*Feb 22 08:59:11.959: EAP-EVENT: Sending lower layer event 'EAP_TX_PACKET' on handle 0xB4000003*Feb 22 08:59:11.959: EAP-EVENT: Received event 'EAP_RX_PACKET' on handle 0xB4000003*Feb 22 08:59:11.959: EAP-EVENT: Sending lower layer event 'EAP_TX_PACKET' on handle 0xB4000003Router#*Feb 22 08:59:17.079: EAP-EVENT: 'Authenticator Retransmit' timer expired for EAP sesion handle 0xB4000003*Feb 22 08:59:17.079: EAP-EVENT: Sending lower layer event 'EAP_TIMEOUT' on handle 0xB4000003*Feb 22 08:59:17.079: EAP-EVENT: Received free context (0xB4000003) from lower layer*Feb 22 08:59:17.079: EAP-EVENT: Received event 'EAP_DELETE' on handle 0xB4000003*Feb 22 08:59:17.079: EAP-AUTH-EVENT: Freed EAP auth context*Feb 22 08:59:17.079: EAP-EVENT: Freed EAP contextBWG#*Feb 22 08:59:18.103: EAP-EVENT: Stopped EAP tick timerdebug eap authenticator
To display debug output for EAP authenticator related events and errors, use the debug eap authenticator command in privileged EXEC mode. Use the no version of command to turn off debug output.
debug eap authenticator {all | errors | events | packets | sm}
no debug eap authenticator {all | errors | events | packets | sm}
Syntax Description
all
Displays all eap debug information.
errors
Displays eap errors.
events
Displays eap events.
packets
Displays eap packet information
sm
Displays EAP state machine errors.
Defaults
There are no default values.
Command Modes
Privileged EXEC.
Command History
Examples
Here is sample output for the debug eap authenticator errors command:
Router#debug eap authenticator errorsEAP authenticator errors debugging is onRouter#*Feb 23 07:30:09.546: EAP-AUTH-ERROR: Invalid response id 2 (current id = 3)Here is sample output for thedebug eap authenticator events command:
Router#debug eap authenticator eventsEAP authenticator events debugging is onRouter#*Feb 23 07:36:08.258: EAP-EVENT: Received context create from lower layer (0x67000006)*Feb 23 07:36:08.258: EAP-AUTH-EVENT: Received AAA ID 0x00000009 from LL*Feb 23 07:36:08.258: EAP-AUTH-AAA-EVENT: Assigning AAA ID 0x00000009*Feb 23 07:36:08.258: EAP-EVENT: Allocated new EAP context (handle = 0x27000006)*Feb 23 07:36:08.258: EAP-EVENT: Received event 'EAP_AUTHENTICATOR_START' on handle 0x27000006*Feb 23 07:36:08.258: EAP-AUTH-EVENT: Current method = Identity*Feb 23 07:36:08.258: EAP-AUTH-EVENT: Sending packet to lower layer for context 0x27000006*Feb 23 07:36:08.258: EAP-EVENT: Started 'Authenticator ReqId Retransmit' timer (5s) for EAP sesion handle 0x27000006*Feb 23 07:36:08.258: EAP-EVENT: Started EAP tick timer*Feb 23 07:36:08.258: EAP-EVENT: Sending lower layer event 'EAP_TX_PACKET' on handle 0x27000006*Feb 23 07:36:08.258: EAP-EVENT: Received event 'EAP_RX_PACKET' on handle 0x27000006*Feb 23 07:36:08.258: EAP-AUTH-EVENT: EAP Response received by contextRouter# 0x27000006*Feb 23 07:36:08.258: EAP-AUTH-EVENT: EAP Response type = Identity*Feb 23 07:36:08.258: EAP-EVENT: Stopping 'Authenticator ReqId Retransmit' timer for EAP sesion handle 0x27000006*Feb 23 07:36:08.258: EAP-AUTH-EVENT: Received peer identity: swimeap@wimax.org*Feb 23 07:36:08.258: EAP-EVENT: Sending lower layer event 'EAP_GET_AAA_METHOD_LISTS' on handle 0x27000006*Feb 23 07:36:08.258: EAP-EVENT: Sending lower layer event 'EAP_GET_PEER_MAC_ADDRESS' on handle 0x27000006*Feb 23 07:36:08.258: EAP-EVENT: Sending lower layer event 'EAP_CUSTOMIZE_AAA_REQUEST' on handle 0x27000006*Feb 23 07:36:08.258: EAP-AUTH-AAA-EVENT: Request sent successfully*Feb 23 07:36:08.266: EAP-EVENT: eap_aaa_reply*Feb 23 07:36:08.266: EAP-AUTH-AAA-EVENT: Server status: GET_CHALLENGE_RESPONSE*Feb 23 07:36:08.266: EAP-EVENT: Received event 'EAP_AAA_RX_PACKET' on handle 0x27000006*Feb 23 07:36:08.266: EAP-AUTH-EVENT: Current method = 13*Feb 23 07:36:08.266: EAP-AUTH-EVENT: Sending packet to lower layer for context 0x27000006*Feb 23 07:36:08.266: EAP-EVENT: Started 'Authenticator Retransmit' timer (5s) for EAP sesion handle 0x27000006*Feb 23 07:36:08.266: EAP-EVENT: Started EAP tick timer*Feb 23 07:36:08.266: EAP-EVENT: Sending lower layer event 'EAP_TX_PACKET' on handle 0x27000006*Feb 23 07:36:08.274: EAP-EVENT: Received event 'EAP_RX_PACKET' on handle 0x27000006*Feb 23 07:36:08.274: EAP-AUTH-EVENT: EAP Response received by context 0x27000006*Feb 23 07:36:08.274: EAP-AUTH-EVENT: EAP Response type = Method (13)*Feb 23 07:36:08.274: EAP-EVENT: Stopping 'Authenticator Retransmit' timer for EAP sesion handle 0x27000006*Feb 23 07:36:08.274: EAP-EVENT: Sending lower layer event 'EAP_GET_AAA_METHOD_LISTS' on handle 0x27000006*Feb 23 07:36:08.274: EAP-EVENT: Sending lower layer event 'EAP_CUSTOMIZE_AAA_REQUEST' on handle 0x27000006*Feb 23 07:36:08.274: EAP-AUTH-AAA-EVENT: Request sent successfully*Feb 23 07:36:08.282: EAP-EVENT: eap_aaa_reply*Feb 23 07:36:08.282: EAP-AUTH-AAA-EVENT: Server status: GET_CHALLENGE_RESPONSE*Feb 23 07:36:08.282: EAP-EVENT: Received event 'EAP_AAA_RX_PACKET' on handle 0x27000006*Feb 23 07:36:08.282: EAP-AUTH-EVENT: Current method = 13debug ip packet
To display general IP debugging information and IP security option (IPSO) security transactions, use the debug ip packet command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ip packet [access-list-number] [detail] [dump]
no debug ip packet [access-list-number]
Syntax Description
Command Modes
Privileged EXEC
Usage Guidelines
If a communication session is closing when it should not be, an end-to-end connection problem can be the cause. The debug ip packet command is useful for analyzing the messages traveling between the local and remote hosts. IP packet debugging captures the packets that are process switched including received, generated and forwarded packets. IP packets that are switched in the fast path are not captured.
IPSO security transactions include messages that describe the cause of failure each time a datagram fails a security test in the system. This information is also sent to the sending host when the router configuration allows it.
Caution
Caution
Examples
The following is sample output from the debug ip packet command:
Router# debug ip packetIP packet debugging is onIP: s=172.69.13.44 (Fddi0), d=10.125.254.1 (Serial2), g=172.69.16.2, forwardIP: s=172.69.1.57 (Ethernet4), d=10.36.125.2 (Serial2), g=172.69.16.2, forwardIP: s=172.69.1.6 (Ethernet4), d=255.255.255.255, rcvd 2IP: s=172.69.1.55 (Ethernet4), d=172.69.2.42 (Fddi0), g=172.69.13.6, forwardIP: s=172.69.89.33 (Ethernet2), d=10.130.2.156 (Serial2), g=172.69.16.2, forwardIP: s=172.69.1.27 (Ethernet4), d=172.69.43.126 (Fddi1), g=172.69.23.5, forwardIP: s=172.69.1.27 (Ethernet4), d=172.69.43.126 (Fddi0), g=172.69.13.6, forwardIP: s=172.69.20.32 (Ethernet2), d=255.255.255.255, rcvd 2IP: s=172.69.1.57 (Ethernet4), d=10.36.125.2 (Serial2), g=172.69.16.2, access deniedThe output shows two types of messages that the debug ip packet command can produce; the first line of output describes an IP packet that the router forwards, and the third line of output describes a packet that is destined for the router. In the third line of output, rcvd 2 indicates that the router decided to receive the packet.
Table 8 describes the significant fields shown in the display.
The following is sample output from the debug ip packet command enabled with the detail keyword:
Router# debug ip packet detailIP packet debugging is on (detailed)001556: 19:59:30: CEF: Try to CEF switch 10.4.9.151 from FastEthernet0/0001557: 19:59:30: IP: s=10.4.9.6 (FastEthernet0/0), d=10.4.9.151 (FastEthernet03001558: 19:59:30: TCP src=179, dst=11001, seq=3736598846, ack=2885081910, wH001559: 20:00:09: CEF: Try to CEF switch 10.4.9.151 from FastEthernet0/0001560: 20:00:09: IP: s=10.4.9.4 (FastEthernet0/0), d=10.4.9.151 (FastEthernet03001561: 20:00:09: TCP src=179, dst=11000, seq=163035693, ack=2948141027, wiH001562: 20:00:14: CEF: Try to CEF switch 10.4.9.151 from FastEthernet0/0001563: 20:00:14: IP: s=10.4.9.6 (FastEthernet0/0), d=10.4.9.151 (FastEthernet03001564: 20:00:14: ICMP type=8, code=0001565: 20:00:14: IP: s=10.4.9.151 (local), d=10.4.9.6 (FastEthernet0/0), len 1g001566: 20:00:14: ICMP type=0, code=0The format of the output with detail keyword provides additional information, such as the packet type, code, some field values, and source and destination port numbers.
Table 9 describes the significant fields shown in the display.
The following is sample output from the debug ip packet command enabled with the dump keyword:
Router# debug ip packet dumpIP packet debugging is on (detailed) (dump)21:02:42: IP: s=10.4.9.6 (FastEthernet0/0), d=10.4.9.4 (FastEthernet0/0), len 1307003A00: 0005 00509C08 ...P..07003A10: 0007855B 4DC00800 45000064 001E0000 ...[M@..E..d....07003A20: FE019669 0A040906 0A040904 0800CF7C ~..i..........O|07003A30: 0D052678 00000000 0A0B7145 ABCDABCD ..&x......qE+M+M07003A40: ABCDABCD ABCDABCD ABCDABCD ABCDABCD +M+M+M+M+M+M+M+M07003A50: ABCDABCD ABCDABCD ABCDABCD ABCDABCD +M+M+M+M+M+M+M+M07003A60: ABCDABCD ABCDABCD ABCDABCD ABCDABCD +M+M+M+M+M+M+M+M07003A70: ABCDABCD ABCDABCD ABCDABCD +M+M+M+M+M+M21:02:42: IP: s=10.4.9.4 (local), d=10.4.9.6 (FastEthernet0/0), len 100, sending07003A00: 0005 00509C08 ...P..07003A10: 0007855B 4DC00800 45000064 001E0000 ...[M@..E..d....07003A20: FF019569 0A040904 0A040906 0000D77C ...i..........W|07003A30: 0D052678 00000000 0A0B7145 ABCDABCD ..&x......qE+M+M07003A40: ABCDABCD ABCDABCD ABCDABCD ABCDABCD +M+M+M+M+M+M+M+M07003A50: ABCDABCD ABCDABCD ABCDABCD ABCDABCD +M+M+M+M+M+M+M+M07003A60: ABCDABCD ABCDABCD ABCDABCD ABCDABCD +M+M+M+M+M+M+M+M07003A70: ABCDABCD ABCDABCD ABCDABCD +M+M+M+M+M+M21:02:42: CEF: Try to CEF switch 10.4.9.4 from FastEthernet0/021:02:42: IP: s=10.4.9.6 (FastEthernet0/0), d=10.4.9.4 (FastEthernet0/0), len 1307003380: 0005 00509C08 ...P..07003390: 0007855B 4DC00800 45000064 001F0000 ...[M@..E..d....070033A0: FE019668 0A040906 0A040904 0800CF77 ~..h..........Ow070033B0: 0D062678 00000000 0A0B7149 ABCDABCD ..&x......qI+M+M070033C0: ABCDABCD ABCDABCD ABCDABCD ABCDABCD +M+M+M+M+M+M+M+M070033D0: ABCDABCD ABCDABCD ABCDABCD ABCDABCD +M+M+M+M+M+M+M+M070033E0: ABCDABCD ABCDABCD ABCDABCD ABCDABCD +M+M+M+M+M+M+M+M070033F0: ABCDABCD ABCDABCD ABCDABCD +M+M+M+M+M+M
Note
The output from the debug ip packet command, when the dump keyword is enabled, provides raw packet data in hexadecimal and ASCII forms. This additional output is displayed in addition to the standard output. The dump keyword can be used with all of the available configuration options of this command.
Table 10 describes the significant fields shown in the display.
The calculation on whether to send a security error message can be somewhat confusing. It depends upon both the security label in the datagram and the label of the incoming interface. First, the label contained in the datagram is examined for anything obviously wrong. If nothing is wrong, assume the datagram to be correct. If something is wrong, the datagram is treated as unclassified genser. Then the label is compared with the interface range, and the appropriate action is taken, as Table 11 describes.
The security code can only generate a few types of Internet Control Message Protocol (ICMP) error messages. The only possible error messages and their meanings follow:
•
•
•
•
Note
When an IP packet is rejected due to an IP security failure, an audit message is sent via Department of Defense Intelligence Information System Network Security for Information Exchange (DNSIX) Network Address Translation (NAT). Also, any debug ip packet output is appended to include a description of the reason for rejection. This description can be any of the following:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
debug ip slb
To display debugging messages for the Cisco IOS Server Load Balancing (SLB) feature, use the debug ip slb command in privileged EXEC mode. To disable debug output, use the no form of this command.To display the packet path inside ASNLB, use the debug ip slb asnr6 command.
debug ip slb [conns | dfp | icmp | asnr6 | reals | all | sticky asn msid ]
no debug ip slb [conns | dfp | icmp | asnr6 | reals | all | sticky asn msid]
Syntax Description
Command Default
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
See the following caution before using debug commands.
Caution
Examples
Here is an example of the debug ip slb command:
Router# debug ip slb allSLB All debugging is onThe following example stops all debugging:
Router# no debug allAll possible debugging has been turned offdebug radius
To display debugging output for RADIUS parameters, use the debug radius command in privileged EXEC mode. Use the no version of command to disable this feature.
debug radius {brief | hex}
no debug radius {brief | hex}
Syntax Description
brief
(Optional) Displays abbreviated debug output.
hex
(Optional) Displays debugging output in hexadecimal notation.
Defaults
Debugging output in ASCII format is enabled.
Command Modes
Privileged EXEC.
Command History
Usage Guidelines
RADIUS is a distributed security system that secures networks against unauthorized access. Cisco supports RADIUS under the authentication, authorization, and accounting (AAA) security system. When RADIUS is used on the router, you can use the debug radius command to display detailed debugging and troubleshooting information in ASCII format. Use the debug radius brief command for abbreviated output displaying client/server interaction and minimum packet information. Use the debug radius hex command to display packet dump information that has not been truncated in hex format.
Examples
Here is sample output for the debug radius brief command:
Router#debug radius briefRadius protocol debugging is onRadius protocol brief debugging is onRadius protocol verbose debugging is offRadius packet hex dump debugging is offRadius packet protocol debugging is offRadius elog debugging debugging is offRadius packet retransmission debugging is offRadius server fail-over debugging is offRadius elog debugging debugging is offRouter#*Feb 22 08:33:03.259: RADIUS/ENCODE(00000002):Orig. component type = DOT1X*Feb 22 08:33:03.259: RADIUS/ENCODE: NAS PORT sending disabled*Feb 22 08:33:03.259: RADIUS(00000002): Config NAS IP: 0.0.0.0*Feb 22 08:33:03.259: RADIUS(00000002): Config NAS IP: 0.0.0.0*Feb 22 08:33:03.259: RADIUS: Attribute 55 not sent, as system clock is not set*Feb 22 08:33:03.259: RADIUS/ENCODE: Best Local IP-Address 1.8.84.1 for Radius-Server 1.8.91.8*Feb 22 08:33:03.259: RADIUS(00000002): Send Access-Request to 1.8.91.8:1645 id 1645/1, len 231Router#*Feb 22 08:33:08.007: RADIUS: Retransmit to (1.8.91.8:1645,1646) for id 1645/1*Feb 22 08:33:08.011: RADIUS: Received from id 1645/1 1.8.91.8:1645, Access-Challenge, len 75*Feb 22 08:33:08.011: RADIUS/DECODE: EAP-Message fragments, 29, total 29 bytes*Feb 22 08:33:08.011: RADIUS/ENCODE(00000002):Orig. component type = DOT1X*Feb 22 08:33:08.011: RADIUS/ENCODE: NAS PORT sending disabled*Feb 22 08:33:08.011: RADIUS(00000002): Config NAS IP: 0.0.0.0*Feb 22 08:33:08.011: RADIUS(00000002): Config NAS IP: 0.0.0.0*Feb 22 08:33:08.011: RADIUS: Attribute 55 not sent, as system clock is not set*Feb 22 08:33:08.011: RADIUS/ENCODE: Best Local IP-Address 1.8.84.1 for Radius-Server 1.8.91.8*Feb 22 08:33:08.011: RADIUS(00000002): Send Access-Request to 1.8.91.8:1645 id 1645/2, len 227*Feb 22 08:33:08.019: RADIUS: Received from id 1645/2 1.8.91.8:1645, Access-Accept, len 99*Feb 22 08:33:08.019: RADIUS/DECODE: EAP-Message fragments, 4, total 4 bytes*Feb 22 08:33:08.031: RADIUS/ERouter#NCODE(00000003):Orig. component type = AGW*Feb 22 08:33:08.031: RADIUS/ENCODE: NAS PORT sending disabled*Feb 22 08:33:08.031: RADIUS(00000003): Config NAS IP: 0.0.0.0*Feb 22 08:33:08.031: RADIUS/ENCODE: Best Local IP-Address 1.8.84.1 for Radius-Server 1.8.91.8*Feb 22 08:33:08.031: RADIUS(00000003): Send Accounting-Request to 1.8.91.8:1646 id 1646/1, len 206*Feb 22 08:33:08.115: RADIUS: Received from id 1646/1 1.8.91.8:1646, Accounting-response, len 20Router#*Feb 22 08:34:10.623: RADIUS/ENCODE(00000003):Orig. component type = AGW*Feb 22 08:34:10.623: RADIUS/ENCODE: NAS PORT sending disabled*Feb 22 08:34:10.623: RADIUS(00000003): Config NAS IP: 0.0.0.0*Feb 22 08:34:10.623: RADIUS/ENCODE: Best Local IP-Address 1.8.84.1 for Radius-Server 1.8.91.8*Feb 22 08:34:10.623: RADIUS(00000003): Send Accounting-Request to 1.8.91.8:1646 id 1646/2, len 236*Feb 22 08:34:10.675: RADIUS: Received from id 1646/2 1.8.91.8:1646, Accounting-response, len 20debug wimax agw aaa
To display AAA authentication or accounting related events or errors, use the debug wimax agw aaa command in privileged EXEC mode. Use the no version of the command to disable debugging.
debug wimax agw aaa {accounting | authentication} {events | errors}
no debug wimax agw aaa {accounting | authentication} {events | errors}
Syntax Description
Defaults
There are no default values.
Command Modes
Privileged EXEC.
Command History
Examples
Here is sample output for AAA authentication events:
Router#debug wim agw aaa authentication eventsWiMAX AGW AAA authentication events debugging is onRouter#*Feb 23 07:53:49.397: AGW-Aaa: <1000003B0009>Allocated AAA unqiue id = 12*Feb 23 07:53:49.397: AGW-Auth: <1000003B0009>Created AAA Auth context with UID 0xC*Feb 23 07:53:49.397: AGW-Auth: <1000003B0009>Creating EAP LowerLayer context*Feb 23 07:53:49.397: AGW-Auth: <1000003B0009>Created EAP lower layer handle with 0x9000007*Feb 23 07:53:49.397: AGW-Auth: <1000003B0009>Received EAP evt EAP_TX_PACKET(0)*Feb 23 07:53:49.397: AGW-Auth: <1000003B0009>Received EAP evt EAP_GET_AAA_METHOD_LISTS(10)*Feb 23 07:53:49.397: AGW-Auth: <1000003B0009>EAP evt EAP_GET_AAA_METHOD_LISTS(10) - usrgrp set*Feb 23 07:53:49.397: AGW-Auth: <1000003B0009>Received EAP evt EAP_GET_PEER_MAC_ADDRESS(8)*Feb 23 07:53:49.397: AGW-Auth: <1000003B0009>Received EAP evt EAP_CUSTOMIZE_AAA_REQUEST(7)*Feb 23 07:53:49.405: AGW-Auth: <1000003B0009>Received EAP evt EAP_TX_PACKET(0)*Feb 23 07:53:49.405: AGW-Auth: <1000003B0009>Received EAP evt EAP_TX_PACKET(0)*Feb 23 07:53:49.409: AGW-Auth: <1000003B0009>Received EAP evt EAP_GET_AAA_METHOD_LISTS(10)*Feb 23 07:53:49.413: AGW-Auth: <10asn#00003B0009>EAP evt EAP_GET_AAA_METHOD_LISTS(10) - Ignoring [usrgrp already set]*Feb 23 07:53:49.413: AGW-Auth: <1000003B0009>Received EAP evt EAP_CUSTOMIZE_AAA_REQUEST(7)*Feb 23 07:53:49.417: AGW-Auth: <1000003B0009>Received EAP evt EAP_TX_PACKET(0)*Feb 23 07:53:49.421: AGW-Auth: <1000003B0009>Received EAP evt EAP_GET_AAA_METHOD_LISTS(10)*Feb 23 07:53:49.421: AGW-Auth: <1000003B0009>EAP evt EAP_GET_AAA_METHOD_LISTS(10) - Ignoring [usrgrp already set]*Feb 23 07:53:49.421: AGW-Auth: <1000003B0009>Received EAP evt EAP_CUSTOMIZE_AAA_REQUEST(7)*Feb 23 07:53:49.425: AGW-Auth: <1000003B0009>Received EAP evt EAP_TX_PACKET(0)*Feb 23 07:53:49.425: AGW-Auth: <1000003B0009>Received EAP evt EAP_GET_AAA_METHOD_LISTS(10)*Feb 23 07:53:49.425: AGW-Auth: <1000003B0009>EAP evt EAP_GET_AAA_METHOD_LISTS(10) - Ignoring [usrgrp already set]*Feb 23 07:53:49.685: AGW-Auth: <1000003B0009>Received EAP evt EAP_CUSTOMIZE_AAA_REQUEST(7)*Feb 23 07:53:49.689: AGW-Auth: <1000003B0009>Received EAP evt EAP_KEY_AVAILABLE(3)*Feb 23 07:53:49.689: AGW-Auth: <1000003B0009>Received EAP evt EAP_SUCCESS(1)*Feb 23 07:53:49.689: AGW-Auth: <1000003B0009>Received Class attr (class-wimax-changed)*Feb 23 07:53:49.689: AGW-Auth: <1000003B0009>Recevied Absolute(session) timeout 1500 secs*Feb 23 07:53:49.689: AGW-Auth: <1000003B0009>Recevied Idle timeout 600 secs*Feb 23 07:53:49.689: AGW-Auth: <1000003B0009>Received termination action 1*Feb 23 07:53:49.689: AGW-Auth: <1000003B0009>Received MS-MPPE-Send-Key, length 50, key length 32*Feb 23 07:53:49.689: AGW-Auth: <1000003B0009>Received MS-MPPE-Recv-Key, length 50, key length 32*Feb 23 07:53:49.689: AGW-Auth: <1000003B0009>Received AAA Session ID*Feb 23 07:53:49.689: AGW-Auth: <1000003B0009>Deleting EAP LowerLayer context with handle 0x9000007*Feb 23 07:53:49.701: AGW-Aaa: <1000003B0009><F[5]>Allocated AAA unqiue id = 13Here is an example of an accounting message on MS open:
Router#debug wimax agw aaa accounting eventsWiMAX AGW AAA accounting events debugging is on router#*Feb 23 08:09:37.521: AGW-Acct: <1000000B0002><F[4]>Invokedget dynamic attributes for path Unknownrouter#*Feb 23 08:09:43.181: AGW-Aaa: <100000310009><F[6]>AllocatedAAA unqiue id = 15*Feb 23 08:09:43.181: AGW-Acct: <100000310009><F[6]>Invokedget dynamic attributes for path Start*Feb 23 08:09:43.181: AGW-Acct: <100000310009><F[6]>Startedaccounting for uid 15 with uname swimeap@wimax.orgrouter#
Note
Here is an example of an accounting message on MS close:
Router#debug wimax agw aaa accounting eventsWiMAX AGW AAA accounting events debugging is on router#BWG#*Feb 23 08:11:54.829: AGW-Acct: <100000310009><F[6]>Invokedget dynamic attributes for path Stop*Feb 23 08:11:54.829: AGW-Acct: <100000310009><F[6]>Stoppedaccounting for uid 15 with uname swimeap@wimax.org
Note
debug wimax agw message
To enable conditional debugging for various types of BWG messages, use the debug wimax agw message command in privileged EXEC mode.
debug wimax agw message [events | errors | dump]
Syntax Description
Defaults
There are no default values.
Command Modes
Privileged EXEC.
Command History
Examples
The following example displays a successful message open:
Router#debug wimax agw message dump*Feb 23 08:29:28.344: AGW-Msg: <067622242222> Rx (GigabitEthernet0/1)*Feb 23 08:29:28.344: AGW-Msg: <067622242222> IP: Src: 10.1.1.70, Dst: 2.2.2.2*Feb 23 08:29:28.344: AGW-Msg: <067622242222> Version: 0x4, IHL: 0x5, TOS: 0xC0*Feb 23 08:29:28.344: AGW-Msg: <067622242222> Total Length: 0x4A, ID: 0x1A*Feb 23 08:29:28.344: AGW-Msg: <067622242222> Flags: Reserved: 0x0, DontFrag: 0x0, MoreFrag: 0x0*Feb 23 08:29:28.344: AGW-Msg: <067622242222> Fragment offset: 0x0, TTL: 0xFE, Protocol: 0x11*Feb 23 08:29:28.344: AGW-Msg: <067622242222> Checksum: 0xAC7E*Feb 23 08:29:28.344: AGW-Msg: <067622242222> UDP: Src Port: 0x8B7, Dst Port: 0x8B7*Feb 23 08:29:28.344: AGW-Msg: <067622242222> Checksum: 0x7E1B, Length: 0x36*Feb 23 08:29:28.344: AGW-Msg: <067622242222> Message: Type 0x090F (0x09, 0x0F)*Feb 23 08:29:28.344: AGW-Msg: <067622242222> FT: MS State Change, MT: Pre Attachment Request*Feb 23 08:29:28.344: AGW-Msg: <067622242222> Version: 0x01, Flags: 0x00, Type 0x90F*Feb 23 08:29:28.344: AGW-Msg: <067622242222> MSID: 067622242222, Reserved_1: 0x0000, Len: 0x2E*Feb 23 08:29:28.344: AGW-Msg: <067622242222> TransactionID: 0x0001, Reserved_2: 0x0000,*Feb 23 08:29:28.344: AGW-Msg: <067622242222> Rx (GigabitEthernet0/1)*Feb 23 08:29:28.344: AGW-Msg: <067622242222> IP: Src: 10.1.1.70, Dst: 2.2.2.2*Feb 23 08:29:28.344: AGW-Msg: <067622242222> Version: 0x4, IHL: 0x5, TOS: 0xC0*Feb 23 08:29:28.344: AGW-Msg: <067622242222> Total Length: 0x30, ID: 0x1B*Feb 23 08:29:28.344: AGW-Msg: <067622242222> Flags: Reserved: 0x0, DontFrag: 0x0, MoreFrag: 0x0*Feb 23 08:29:28.344: AGW-Msg: <067622242222> Fragment offset: 0x0, TTL: 0xFE, Protocol: 0x11*Feb 23 08:29:28.344: AGW-Msg: <067622242222> Checksum: 0xAC97*Feb 23 08:29:28.344: AGW-Msg: <067622242222> UDP: Src Port: 0x8B7, Dst Port: 0x8B7*Feb 23 08:29:28.344: AGW-Msg: <067622242222> Checksum: 0x8A1B, Length: 0x1C*Feb 23 08:29:28.344: AGW-Msg: <067622242222> Message: Type 0x0911 (0x09, 0x11)*Feb 23 08:29:28.344: AGW-Msg: <067622242222> FT: MS State Change, MT: Pre Attachment ACKHere is sample Message Events output on a successful MS Close:
Router#debug wimax agw message events*Feb 23 08:33:49.064: AGW-Msg: <100022230001>Rx SrcAddr: 10.1.1.70, SrcPort: 2231, TID: 0x3, Type: 0x304, Len: 0x38, Flag: 0x2, FT: Data Path(0x3), MT: Deregistration Request(0x4)*Feb 23 08:33:49.064: AGW-Msg: <100022230001>[Decode] FT/MT: 3/4, Ref pt: 3, TID rcvd 0X3(3), peer 0X2(2)[9/8], our 0X8002(32770)[3/12], Previous peer 0x1(1)[9/15], Previous our 0X8001(32769)[3/12],TID RC: 1*Feb 23 08:33:49.064: AGW-Msg: <100022230001>[Decode] Req FT/MT: 3/4, Ref pt: 3, TID RC: 1, RC: Success(0)*Feb 23 08:33:49.064: AGW-Msg: <100022230001>Tx DstAddr: 10.1.1.70, SrcPort: 2231, TID: 0x3, Type: 0x305, Len: 0x38, Flag: 0x0, FT: Data Path(0x3), MT: Deregistration Response(0x5)*Feb 23 08:33:49.064: AGW-Msg: <100022230001>[Decode] FT/MT: 3/4, Ref pt: 3, Retcode = Success(0)*Feb 23 08:33:49.064: AGW-Msg: <100022230001>Rx SrcAddr: 10.1.1.70, SrcPort: 2231, TID: 0x3, Type: 0x306, Len: 0x1C, Flag: 0x0, FT: Data Path(0x3), MT: Deregistration Ack(0x6)*Feb 23 08:33:49.064: AGW-Msg: <100022230001>[Decode] FT/MT: 3/6, Ref pt: 3, TID rcvd 0X3(3), peer 0X3(3)[3/4], our 0X8002(32770)[3/12], Previous peer 0x2(2)[9/8], Previous our 0X8001(32769)[3/12],TID RC: 1*Feb 23 08:33:49.064: AGW-Msg: <100022230001>[Decode] Req FT/MT: 3/6, Ref pt: 3, TID RC: 1, RC: Success(0)*Feb 23 08:33:49.064: AGW-Msg: <100022230001>Deleting the R6 TID 0X65A3B46C, 10.1.1.70/2.2.2.2/0*Feb 23 08:33:49.064: AGW-Msg: <100022230001>[Decode] FT/MT: 3/6, Ref pt: 3, Retcode = Success(0)Here is sample Message Events output when MS open fails:
Router#debug wimax agw message events*Feb 23 11:00:40.408: AGW-Msg: <067611141111>Rx SrcAddr: 10.1.1.70, SrcPort: 2231, TID: 0x1, Type: 0x90F, Len: 0x2E, Flag: 0x0, FT: MS State Change(0x9), MT: Pre Attachment Request(0xF)*Feb 23 11:00:40.408: AGW-Msg: <067611141111>[Decode] Req FT/MT: 9/15, Ref pt: 3, TID RC: 6, RC: Success(0)*Feb 23 11:00:40.408: AGW-Msg: <067611141111>[Decode] Created the R6 TID 0X65A3B4A8, 10.1.1.70/2.2.2.2/9*Feb 23 11:00:40.408: AGW-Msg: <067611141111>Tx DstAddr: 10.1.1.70, SrcPort: 2231, TID: 0x1, Type: 0x910, Len: 0x36, Flag: 0x0, FT: MS State Change(0x9), MT: Pre Attachment Response(0x10)*Feb 23 11:00:40.408: AGW-Msg: <067611141111>[Decode] FT/MT: 9/15, Ref pt: 3, Retcode = Success(0)*Feb 23 11:00:40.408: AGW-Msg: <067611141111>Rx SrcAddr: 10.1.1.70, SrcPort: 2231, TID: 0x1, Type: 0x911, Len: 0x14, Flag: 0x0, FT: MS State Change(0x9), MT: Pre Attachment ACK(0x11)*Feb 23 11:00:40.408: AGW-Msg: <067611141111>[Decode] FT/MT: 9/17, Ref pt: 3, TID rcvd 0X1(1), peer 0X1(1)[9/15], our 0X8000(32768)[0/0], Previous peer 0x0(0)[0/0], Previous our 0X0(0)[0/0],TID RC: 1*Feb 23 11:00:40.408: AGW-Msg: <067611141111>[Decode] Req FT/MT: 9/17, Ref pt: 3, TID RC: 1, RC: Success(0)*Feb 23 11:00:40.408: AGW-Msg: <067611141111>[Decode] FT/MT: 9/17, Ref pt: 3, Retcode = Success(0)*Feb 23 11:00:40.408: AGW-Msg: <067611141111>FT/MT: 8/2, generated TID 0X8001(32769), 10.1.1.70/2.2.2.2/8*Feb 23 11:00:40.408: AGW-Msg: <067611141111>Tx DstAddr: 10.1.1.70, SrcPort: 2231, TID: 0x8001, Type: 0x802, Len: 0x1D, Flag: 0x0, FT: Auth Relay(0x8), MT: EAP Transfer(0x2)*Feb 23 11:00:40.412: AGW-Msg: <067611141111>Rx SrcAddr: 10.1.1.70, SrcPort: 2231, TID: 0x2, Type: 0x802, Len: 0x31, Flag: 0x0, FT: Auth Relay(0x8), MT: EAP Transfer(0x2)*Feb 23 11:00:40.468: AGW-Msg: <067611141111>Tx DstAddr: 10.1.1.70, SrcPort: 2231, TID: 0x8006, Type: 0x304, Len: 0x38, Flag: 0x2, FT: Data Path(0x3), MT: Deregistration Request(0x4)*Feb 23 11:00:40.468: AGW-Msg: <067611141111>Rx SrcAddr: 10.1.1.70, SrcPort: 2231, TID: 0x8006, Type: 0x305, Len: 0x38, Flag: 0x0, FT: Data Path(0x3), MT: Deregistration Response(0x5)*Feb 23 11:00:40.468: AGW-Msg: <067611141111>[Decode] FT/MT: 3/5, Ref pt: 3, TID rcvd 0X8006(32774), peer 0X6(6)[8/2], our 0X8006(32774)[3/4], Previous peer 0x5(5)[8/2], Previous our 0X8005(32773)[8/2],TID RC: 1*Feb 23 11:00:40.468: AGW-Msg: <067611141111>[Decode] Req FT/MT: 3/5, Ref pt: 3, TID RC: 1, RC: Success(0)*Feb 23 11:00:40.468: AGW-Msg: <067611141111>Tx DstAddr: 10.1.1.70, SrcPort: 2231, TID: 0x8006, Type: 0x306, Len: 0x1C, Flag: 0x0, FT: Data Path(0x3), MT: Deregistration Ack(0x6)*Feb 23 11:00:40.468: AGW-Msg: <067611141111>Deleting the R6 TID 0X65A3B4A8, 10.1.1.70/2.2.2.2/0*Feb 23 11:00:40.468: AGW-Msg: <067611141111>[Decode] FT/MT: 3/5, Ref pt: 3, Retcode = Success(0)Here is sample Message Events output when handoff fails:
Router#debug wimax agw message events*Feb 23 12:35:52.003: AGW-Msg: <100022230001>Rx SrcAddr: 10.1.1.72, SrcPort: 2231, TID: 0x1, Type: 0x401, Len: 0x2C, Flag: 0x0, FT: Context Delivery(0x4), MT: Context Delivery Request(0x1)*Feb 23 12:35:52.003: AGW-Msg: <100022230001>[Decode] Req FT/MT: 4/1, Ref pt: 3, TID RC: 5, RC: Success(0)*Feb 23 12:35:52.003: AGW-Msg: <100022230001>[Decode] Created the R6 TID 0X65A3B3F4, 10.1.1.72/2.2.2.2/4*Feb 23 12:35:52.003: AGW-Msg: <100022230001>Tx DstAddr: 10.1.1.72, SrcPort: 2231, TID: 0x1, Type: 0x402, Len: 0x69, Flag: 0x0, FT: Context Delivery(0x4), MT: Context Delivery Report(0x2)*Feb 23 12:35:52.003: AGW-Msg: <100022230001>[Decode] FT/MT: 4/1, Ref pt: 3, Retcode = Success(0)*Feb 23 12:35:52.007: AGW-Msg: <100022230001>Rx SrcAddr: 10.1.1.72, SrcPort: 2231, TID: 0x2, Type: 0x30C, Len: 0x1D2, Flag: 0x0, FT: Data Path(0x3), MT: Registration Request(0xC)*Feb 23 12:35:52.007: AGW-Msg: <100022230001>[Decode] FT/MT: 3/12, Ref pt: 3, TID rcvd 0X2(2), peer 0X1(1)[4/1], our 0X8000(32768)[0/0], Previous peer 0x0(0)[0/0], Previous our 0X0(0)[0/0],TID RC: 1*Feb 23 12:35:52.007: AGW-Msg: <100022230001>[Decode] Req FT/MT: 3/12, Ref pt: 3, TID RC: 1, RC: Success(0)*Feb 23 12:35:52.007: AGW-Msg: <100022230001><F[41]>Tx DstAddr: 10.1.1.72, SrcPort: 2231, TID: 0x2, Type: 0x30D, Len: 0xC0, Flag: 0x0, FT: Data Path(0x3), MT: Registration Response(0xD)*Feb 23 12:35:52.007: AGW-Msg: <100022230001><F[42]>[Decode] FT/MT: 3/12, Ref pt: 3, Retcode = Success(0)*Feb 23 12:35:52.007: AGW-Msg: <100022230001>Rx SrcAddr: 10.1.1.72, SrcPort: 2231, TID: 0x2, Type: 0x30E, Len: 0x1C, Flag: 0x0, FT: Data Path(0x3), MT: Registration Ack(0xE)*Feb 23 12:35:52.007: AGW-Msg: <100022230001>[Decode] FT/MT: 3/14, Ref pt: 3, TID rcvd 0X2(2), peer 0X2(2)[3/12], our 0X8000(32768)[0/0], Previous peer 0x2(2)[3/12], Previous our 0X0(0)[0/0],TID RC: 1*Feb 23 12:35:52.007: AGW-Msg: <100022230001>[Decode] Req FT/MT: 3/14, Ref pt: 3, TID RC: 1, RC: Success(0)*Feb 23 12:35:52.007: AGW-Msg: <100022230001>FT/MT: 3/4, generated TID 0X8003(32771), 10.1.1.70/2.2.2.2/3*Feb 23 12:35:52.007: AGW-Msg: <100022230001><F[41]>Tx DstAddr: 10.1.1.70, SrcPort: 2231, TID: 0x8003, Type: 0x304, Len: 0x38, Flag: 0x0, FT: Data Path(0x3), MT: Deregistration Request(0x4)*Feb 23 12:35:52.007: AGW-Msg: <100022230001><F[42]>[Decode] FT/MT: 3/14, Ref pt: 3, Retcode = Success(0)*Feb 23 12:35:52.007: AGW-Msg: <100022230001>Rx SrcAddr: 10.1.1.72, SrcPort: 2231, TID: 0x3, Type: 0x402, Len: 0x69, Flag: 0x0, FT: Context Delivery(0x4), MT: Context Delivery Report(0x2)*Feb 23 12:35:52.007: AGW-Msg: <100022230001>[Decode] FT/MT: 4/2, Ref pt: 3,"Retcode = Fail - Abort(1)"debug wimax agw message tlv
To display various BWG TLV messages, use the debug wimax agw message tlv command in privileged EXEC mode.
debug wimax agw message tlv [events | errors | dump]
Syntax Description
Defaults
There are no default values.
Command Modes
Privileged EXEC
Command History
Examples
The following example displays TLV events on a successful MS Open:
Router#debug wimax agw message tlv events*Feb 23 08:37:59.864: AGW-Tlv: <100022230001> Type: MS Information(0x0001), Length: 0x0006*Feb 23 08:37:59.864: AGW-Tlv: <100022230001> Type: Authorization Policy(0x0028), Length: 0x0002*Feb 23 08:37:59.864: AGW-Tlv: <100022230001> Type: Base Station Information(0x0002), Length: 0x000C*Feb 23 08:37:59.864: AGW-Tlv: <100022230001> Type: Base Station ID(0x0014), Length: 0x0008*Feb 23 08:37:59.864: AGW-Tlv: <100022230001> Type: MS Information(0x0001), Length: 0x0026*Feb 23 08:37:59.864: AGW-Tlv: <100022230001> Type: Key Change Indicator(0x005F), Length: 0x0001*Feb 23 08:37:59.864: AGW-Tlv: <100022230001> Type: Registration Context(0x0058), Length: 0x001D*Feb 23 08:37:59.864: AGW-Tlv: <100022230001> Type: MTG Profile(0x0069), Length: 0x0001*Feb 23 08:37:59.864: AGW-Tlv: <100022230001> Type: CS Type(0x0068), Length: 0x0002*Feb 23 08:37:59.864: AGW-Tlv: <100022230001> Type: Number of Downlink CIDs(0x006A), Length: 0x0002*Feb 23 08:37:59.864: AGW-Tlv: <100022230001> Type: Number of Uplink CIDs(0x006B), Length: 0x0002*Feb 23 08:37:59.864: AGW-Tlv: <100022230001> Type: Number of Uplink Classifiers(0x006C), Length: 0x0002*Feb 23 08:37:59.864: AGW-Tlv: <100022230001> Type: Base Station Information(0x0002), Length: 0x000C*Feb 23 08:37:59.864: AGW-Tlv: <100022230001> Type: Base Station ID(0x0014), Length: 0x0008*Feb 23 08:37:59.868: AGW-Tlv: <100022230001> Type: Registration Type(0x002E), Length: 0x0004*Feb 23 08:37:59.868: AGW-Tlv: <100022230001> Type: MS Information(0x0001), Length: 0x004C*Feb 23 08:37:59.868: AGW-Tlv: <100022230001> Type: Anchor Gateway ID(0x001B), Length: 0x0004*Feb 23 08:37:59.868: AGW-Tlv: <100022230001> Type: SF Information(0x0003), Length: 0x0014*Feb 23 08:37:59.868: AGW-Tlv: <100022230001> Type: Direction(0x005E), Length: 0x0002*Feb 23 08:37:59.868: AGW-Tlv: <100022230001> Type: Service Flow Identifier(0x003B), Length: 0x0004*Feb 23 08:37:59.868: AGW-Tlv: <100022230001> Type: Reservation Result(0x0065), Length: 0x0002*Feb 23 08:37:59.868: AGW-Tlv: <100022230001> Type: SF Information(0x0003), Length: 0x0028*Feb 23 08:37:59.868: AGW-Tlv: <100022230001> Type: Direction(0x005E), Length: 0x0002*Feb 23 08:37:59.868: AGW-Tlv: <100022230001> Type: Service Flow Identifier(0x003B), Length: 0x0004*Feb 23 08:37:59.868: AGW-Tlv: <100022230001> Type: Reservation Result(0x0065), Length: 0x0002*Feb 23 08:37:59.868: AGW-Tlv: <100022230001> Type: DP Information(0x0008), Length: 0x0010*Feb 23 08:37:59.868: AGW-Tlv: <100022230001> Type: DP Identifier(GRE Key)(0x0023), Length: 0x0004*Feb 23 08:37:59.868: AGW-Tlv: <100022230001> Type: Data Path End point Identifier(0x0024), Length: 0x0004The following example displays TLV events on a successful MS close:
Router#debug wimax agw message tlv dump*Feb 23 08:39:54.424: AGW-Tlv: <100022230001> Type: Registration Type(0x002E), Length: 0x0004*Feb 23 08:39:54.424: AGW-Tlv: <100022230001> Value: 4*Feb 23 08:39:54.424: AGW-Tlv: <100022230001> Type: Anchor Gateway ID(0x001B), Length: 0x0004*Feb 23 08:39:54.424: AGW-Tlv: <100022230001> Hex: < 02 02 02 02 >*Feb 23 08:39:54.424: AGW-Tlv: <100022230001> Type: Base Station ID(0x0014), Length: 0x0008*Feb 23 08:39:54.424: AGW-Tlv: <100022230001> Hex: < 0A 01 01 46 00 00 00 00 >*Feb 23 08:39:54.428: AGW-Tlv: <100022230001> Type: Registration Type(0x002E), Length: 0x0004*Feb 23 08:39:54.428: AGW-Tlv: <100022230001> Value: 4debug wimax agw path
To display BS path related messages, use the debug wimax agw path command in privileged EXEC mode.
debug wimax agw path [events | errors]
Syntax Description
events
Displays information on BS path related events.
errors
Displays information on BS path related errors
Defaults
There are no default values.
Command Modes
Privileged EXEC
Command History
Examples
Here is sample Path Events output on a successful MS Open:
Router#debug wimax agw path events*Feb 23 10:32:36.496: AGW-Path: <(SU)-10.1.1.70>State transition Purging -> Ready*Feb 23 10:32:36.496: AGW-Path: <(SU)-10.1.1.70>Stopping purge timer*Feb 23 10:32:36.496: AGW-Path: <(SU)-10.1.1.70>Enqueuing pak of size 54 (refcount 1) with resend required 1*Feb 23 10:32:36.496: AGW-Path: <(SU)-10.1.1.70>Enqueuing pak of size 29 (refcount 1) with resend required 0*Feb 23 10:32:36.504: AGW-Path: <(SU)-10.1.1.70>Enqueuing pak of size 53 (refcount 1) with resend required 0*Feb 23 10:32:36.512: AGW-Path: <(SU)-10.1.1.70>Enqueuing pak of size 42 (refcount 1) with resend required 1*Feb 23 10:32:36.512: AGW-Path: <(SU)-10.1.1.70>Enqueuing pak of size 81 (refcount 1) with resend required 1*Feb 23 10:32:36.512: AGW-Path: <(SU)-10.1.1.70>Enqueuing pak of size 252 (refcount 1) with resend required 1*Feb 23 10:32:36.516: AGW-Path: <(DG)-10.1.1.70>Stopping purge timer*Feb 23 10:32:36.516: AGW-Path: <(SU)-10.1.1.70>Enqueuing pak of size 28 (refcount 1) with resend required 0*Feb 23 10:32:36.520: AGW-Path: <(SU)-10.1.1.70>Enqueuing pak of size 274 (refcount 1) with resend required 1*Feb 23 10:32:36.520: AGW-Path: <(SU)-10.1.1.70>Enqueuing pak of size 28 (refcount 1) with resend required 0Here is sample Path Events output when an MS open fails:
Router#debug wimax agw path events*Feb 23 10:35:05.196: AGW-Path: <(SU)-10.1.1.70>State transition Idle -> Ready*Feb 23 10:35:05.196: AGW-Path: <(SU)-10.1.1.70>Created path with handle 0x6B000016*Feb 23 10:35:05.196: AGW-Path: <(SU)-10.1.1.70>Enqueuing pak of size 54 (refcount 1) with resend required 1*Feb 23 10:35:05.200: AGW-Path: <(SU)-10.1.1.70>Enqueuing pak of size 29 (refcount 1) with resend required 0*Feb 23 10:35:05.204: AGW-Path: <(SU)-10.1.1.70>Enqueuing pak of size 30 (refcount 1) with resend required 0*Feb 23 10:35:05.216: AGW-Path: <(SU)-10.1.1.70>Enqueuing pak of size 1048 (refcount 1) with resend required 0*Feb 23 10:35:05.220: AGW-Path: <(SU)-10.1.1.70>Enqueuing pak of size 1048 (refcount 1) with resend required 0*Feb 23 10:35:05.228: AGW-Path: <(SU)-10.1.1.70>Enqueuing pak of size 922 (refcount 1) with resend required 0*Feb 23 10:35:05.256: AGW-Path: <(SU)-10.1.1.70>Enqueuing pak of size 56 (refcount 1) with resend required 1*Feb 23 10:35:05.256: AGW-Path: <(SU)-10.1.1.70>Enqueuing pak of size 28 (refcount 1) with resend required 0*Feb 23 10:35:05.256: AGW-Path: <(SU)-10.1.1.70>State transition Ready -> Purging*Feb 23 10:35:05.256: AGW-Path: <(SU)-10.1.1.70>Starting purge timer for 20000 msecs*Feb 23 10:35:25.428: AGW-Path: <(SU)-10.1.1.70>Expired purge timer after 20000 msecs*Feb 23 10:35:25.428: AGW-Path: <(SU)-10.1.1.70>Deleting the path with handle 0x6B000016Here is sample Path Events output on a successful MS Close:
Router#debug wimax agw path events*Feb 23 10:34:12.204: AGW-Path: <(SU)-10.1.1.70>Enqueuing pak of size 56 (refcount 1) with resend required 1*Feb 23 10:34:12.208: AGW-Path: <(DG)-10.1.1.70>Starting purge timer for 20000 msecs*Feb 23 10:34:12.208: AGW-Path: <(SU)-10.1.1.70>State transition Ready -> Purging*Feb 23 10:34:12.208: AGW-Path: <(SU)-10.1.1.70>Starting purge timer for 20000 msecs*Feb 23 10:34:32.392: AGW-Path: <(DG)-10.1.1.70>Expired purge timer after 20000 msecs*Feb 23 10:34:32.392: AGW-Path: <(DG)-10.1.1.70>Deleting the path with handle 0x35000015*Feb 23 10:34:32.392: AGW-Path: <(SU)-10.1.1.70>Expired purge timer after 20000 msecs*Feb 23 10:34:32.392: AGW-Path: <(SU)-10.1.1.70>Deleting the path with handle 0x63000013debug wimax agw r6 flow
To display BWG flow information, use the debug wimax agw r6 flow command in Privileged EXEC mode.
debug wimax agw r6 flow [events | errors | fsm events | fsm errors]
Syntax Description
Defaults
There are no default values.
Command Modes
Privileged EXEC.
Command History
Examples
Here is sample R6 flow output for a successful MS Open:
Router#debug wimax agw r6 flow events*Feb 23 10:18:00.992: AGW-Flow: <100022230001><F[21]>[Downlink] Predefined SF QoS info set*Feb 23 10:18:00.992: AGW-Flow: <100022230001><F[21]>[Downlink] Predefined SF IPv4 TFT set*Feb 23 10:18:00.992: AGW-Flow: <100022230001><F[21]>[Uplink] Predefined SF QoS info set*Feb 23 10:18:00.992: AGW-Flow: <100022230001><F[21]>[Uplink] Predefined SF IPv4 TFT set*Feb 23 10:18:00.992: AGW-Flow: <100022230001><F[21]>Created flow with handle 0xD0000015, local Id 0x15 for session handle 0xE500000F*Feb 23 10:18:00.992: AGW-Flow: <100022230001><F[21]>[ISF] Created flow with index 0*Feb 23 10:18:00.992: AGW-Flow: <100022230001><F[22]>[Downlink] Predefined SF QoS info set*Feb 23 10:18:00.992: AGW-Flow: <100022230001><F[22]>[Downlink] Predefined SF IPv4 TFT set*Feb 23 10:18:00.992: AGW-Flow: <100022230001><F[22]>[Uplink] Predefined SF QoS info set*Feb 23 10:18:00.992: AGW-Flow: <100022230001><F[22]>[Uplink] Predefined SF IPv4 TFT set*Feb 23 10:18:00.992: AGW-Flow: <100022230001><F[22]>Created flow with handle 0x62000016, local Id 0x16 for session handle 0xE500000F*Feb 23 10:18:00.992: AGW-Flow: <100022230001><F[22]>[SF] Created flow with index 1*Feb 23 10:18:00.992: AGW-Flow: <100022230001><F[21]>Creating the sigpak resend details 0x207497F0, max resend 10, timeout 10000 msecs, timer type 2(16)*Feb 23 10:18:00.996: AGW-Flow: <100022230001><F[21]>Starting pak resend timer 0x207497F0 for 10000 msecs with max resend 10, current resend 0, timer type 2(16)*Feb 23 10:18:00.996: AGW-Flow: <100022230001><F[21]>Deleting the sigpak resend details 0x207497F0*Feb 23 10:18:00.996: AGW-Flow: <100022230001><F[21]>Stopping pak resend timer 0x207497F0 for 10000 msecs with max resend 10, current resend 0, timer type 2(16)*Feb 23 10:18:00.996: AGW-Flow: <100022230001><F[21]><(DG)-10.1.1.70>Link the flow to the pathHere is sample R6 flow output for a successful MS Close:
Router#debug wimax agw r6 flow events*Feb 23 10:17:08.868: AGW-Flow: <100022230001><F[17]>Deleting flow with handle 0x87000011 for session handle 0x7900000D*Feb 23 10:17:08.868: AGW-Flow: <100022230001><F[17]><(DG)-10.1.1.70>Delink the flow from the path*Feb 23 10:17:08.868: AGW-Flow: <100022230001><F[17]>Deallocating the Downlink SF details*Feb 23 10:17:08.868: AGW-Flow: <100022230001><F[17]>Deallocating the Uplink SF details*Feb 23 10:17:08.868: AGW-Flow: <100022230001><F[17]>Deleting flow*Feb 23 10:17:08.868: AGW-Flow: <100022230001><F[18]>Deleting flow with handle 0x3F000012 for session handle 0x7900000D*Feb 23 10:17:08.868: AGW-Flow: <100022230001><F[18]><(DG)-10.1.1.70>Delink the flow from the path*Feb 23 10:17:08.868: AGW-Flow: <100022230001><F[18]>Deallocating the Downlink SF details*Feb 23 10:17:08.868: AGW-Flow: <100022230001><F[18]>Deallocating the Uplink SF details*Feb 23 10:17:08.868: AGW-Flow: <100022230001><F[18]>Deleting flowHere is sample R6 Flow FSM Events output for a successful MS Open:
Router#debug wimax agw r6 flow fsm events*Feb 23 10:25:44.324: AGW-FlowFSM:<067622272222><F[27]>SF Idle(0) -> SF Establishing(1) on event Tx Reg Req(4) with retcode Ok(0)*Feb 23 10:25:44.328: AGW-FlowFSM:<067622272222><F[27]>SF Establishing(1) -> SF Establishing(1) on event Rx Reg Rsp(5) with retcode Ok(0)*Feb 23 10:25:44.328: AGW-FlowFSM:<067622272222><F[27]>SF Establishing(1) -> ISF Wait For Addr Alloc(2) on event Tx Reg Ack(6) with retcode ISF - Ok(5)*Feb 23 10:25:44.328: AGW-FlowFSM:<067622272222><F[27]>ISF Wait For Addr Alloc(2) -> SF Ready(4) on event SF Addr Assigned(7) with retcode Ok(0)*Feb 23 10:25:44.328: AGW-FlowFSM:<067622272222><F[27]>SF Ready(4) -> SF Ready(4) on event Up(1) with retcode Ok(0)*Feb 23 10:25:44.332: AGW-FlowFSM:<067622272222><F[28]>SF Idle(0) -> SF Establishing(1) on event Tx Reg Req(4) with retcode Ok(0)*Feb 23 10:25:44.332: AGW-FlowFSM:<067622272222><F[28]>SF Establishing(1) -> SF Establishing(1) on event Rx Reg Rsp(5) with retcode Ok(0)*Feb 23 10:25:44.332: AGW-FlowFSM:<067622272222><F[28]>SF Establishing(1) -> SF Ready(4) on event Tx Reg Ack(6) with retcode Ok(0)*Feb 23 10:25:44.332: AGW-FlowFSM:<067622272222><F[28]>SF Ready(4) -> SF Ready(4) on event Up(1) with retcode Ok(0)Here is sample R6 Flow FSM Events output for a successful MS Close:
Router#debug wimax agw r6 flow fsm events*Feb 23 10:24:06.592: AGW-FlowFSM:<067622262222><F[19]>SF Ready(4) -> SF Cleanup(7) on event Session Closed(2) with retcode Ok(0)*Feb 23 10:24:06.592: AGW-FlowFSM:<067622262222><F[19]>SF Cleanup(7) -> SF Cleanup(7) on event Session Closed(2) with retcode Ok(0)*Feb 23 10:24:06.592: AGW-FlowFSM:<067622262222><F[20]>SF Ready(4) -> SF Cleanup(7) on event Session Closed(2) with retcode Ok(0)*Feb 23 10:24:06.592: AGW-FlowFSM:<067622262222><F[20]>SF Cleanup(7) -> SF Cleanup(7) on event Session Closed(2) with retcode Ok(0)debug wimax agw r6 session
To display BWG R6 session information, use the debug wimax agw r6 session command in Privileged EXEC mode.
debug wimax agw r6 session [events | errors | fsm events | fsm errors]
Syntax Description
Defaults
There are no default values.
Command Modes
Privileged EXEC.
Command History
Examples
Here is sample output for R6 session events on a successful MS Open:
Router#debug wimax agw r6 session events*Feb 23 12:55:34.715: AGW-Sess: <1000222A0001>Created session with handle 0x61000022, Id 0x22 for subscriber handle 0x83000022*Feb 23 12:55:34.715: AGW-Sess: <1000222A0001><(SU)-10.1.1.70>:Link the session to the path*Feb 23 12:55:34.715: AGW-Sess: <1000222A0001>Created session*Feb 23 12:55:34.715: AGW-Sess: <1000222A0001>Found usrgrp **unauthenticated** based on domain for user*Feb 23 12:55:34.715: AGW-Sess: <1000222A0001>Creating the sigpak resend details 0x654986B8, max resend 10, timeout 10000 msecs, timer type 1(2)*Feb 23 12:55:34.715: AGW-Sess: <1000222A0001>Starting pak resend timer 0x654986B8 for 10000 msecs with max resend 10, current resend 0, timer type 1(2)*Feb 23 12:55:34.715: AGW-Sess: <1000222A0001>Deleting the sigpak resend details 0x654986B8*Feb 23 12:55:34.715: AGW-Sess: <1000222A0001>Stopping pak resend timer 0x654986B8 for 10000 msecs with max resend 10, current resend 0, timer type 1(2)*Feb 23 12:55:34.715: AGW-Sess: <1000222A0001>Starting protect timer Rx attach req for 110 secs*Feb 23 12:55:34.715: AGW-Sess: <1000222A0001>Creating the sigpak resend details 0x2034967C, max resend 10, timeout 10000 msecs, timer type 1(8)*Feb 23 12:55:34.715: AGW-Sess: <1000222A0001>Starting pak resend timer 0x2034967C for 10000 msecs with max resend 10, current resend 0, timer type 1(8)*Feb 23 12:55:34.715: AGW-Sess: <1000222A0001>Stopping protect timer Rx attach req*Feb 23 12:55:34.715: AGW-Sess: <1000222A0001>Deleting the sigpak resend details 0x2034967C*Feb 23 12:55:34.715: AGW-Sess: <1000222A0001>Stopping pak resend timer 0x2034967C for 10000 msecs with max resend 10, current resend 0, timer type 1(8)*Feb 23 12:55:34.723: AGW-Sess: <1000222A0001><F[45]>Adding Host address 2.2.0.16*Feb 23 12:55:34.723: AGW-Sess: <1000222A0001><F[45]>Static route IPv4 addr 2.2.0.16, aggr mask 255.255.255.255*Feb 23 12:55:34.723: AGW-Sess: <1000222A0001><F[45]>Created new host for the session*Feb 23 12:55:34.723: AGW-Sess: <1000222A0001><F[45]>Set host IPv4 address 2.2.0.16 for the session*Feb 23 12:55:34.723: AGW-Sess: <1000222A0001>Starting Lease timer for host 2.2.0.16 with timeout 3540 seconds*Feb 23 12:55:34.723: AGW-Sess: <1000222A0001>Inserting static route 2.2.0.16 255.255.255.255 via 0.0.0.0, idb Virtual-Access2, tableid 0*Feb 23 12:55:34.723: AGW-Sess: <1000222A0001>Added static route/inserted address 2.2.0.16 255.255.255.255/0*Feb 23 12:55:34.723: AGW-Sess: <1000222A0001>Ready to switch traffic for sessionHere is sample output for R6 session events when MS open fails:
Router#debug wimax agw r6 session events*Feb 23 08:51:02.728: AGW-Sess: <067611141111>Created session with handle 0x74000009, Id 0x9 for subscriber handle 0xA3000009*Feb 23 08:51:02.728: AGW-Sess: <067611141111><(SU)-10.1.1.70>:Link the session to the path*Feb 23 08:51:02.728: AGW-Sess: <067611141111>Created session*Feb 23 08:51:02.728: AGW-Sess: <067611141111>Creating the sigpak resend details 0x65AEF5B4, max resend 10, timeout 10000 msecs, timer type 1(2)*Feb 23 08:51:02.728: AGW-Sess: <067611141111>Starting pak resend timer 0x65AEF5B4 for 10000 msecs with max resend 10, current resend 0, timer type 1(2)*Feb 23 08:51:02.732: AGW-Sess: <067611141111>Deleting the sigpak resend details 0x65AEF5B4*Feb 23 08:51:02.732: AGW-Sess: <067611141111>Stopping pak resend timer 0x65AEF5B4 for 10000 msecs with max resend 10, current resend 0, timer type 1(2)*Feb 23 08:51:02.732: AGW-Sess: <067611141111>Username pushetty@eap-tls.com, domain is eap-tls.com, user is pushetty, delimiter @*Feb 23 08:51:02.732: AGW-Sess: <067611141111>Found usrgrp eap-tls.com based on domain eap-tls.com for user pushetty@eap-tls.com*Feb 23 08:51:02.788: AGW-Sess: <067611141111>[Authenticating / Auth Result Obtained]*Feb 23 08:51:02.788: AGW-Sess: <067611141111>Creating the sigpak resend details 0x654986B8, max resend 10, timeout 10000 msecs, timer type 1(10)*Feb 23 08:51:02.788: AGW-Sess: <067611141111>Starting pak resend timer 0x654986B8 for 10000 msecs with max resend 10, current resend 0, timer type 1(10)*Feb 23 08:51:02.788: AGW-Sess: <067611141111>Deleting the sigpak resend details 0x654986B8*Feb 23 08:51:02.788: AGW-Sess: <067611141111>Stopping pak resend timer 0x654986B8 for 10000 msecs with max resend 10, current resend 0, timer type 1(10)*Feb 23 08:51:02.788: AGW-Sess: <067611141111>Deleting session with handle 0x74000009 for subscriber handle 0xA3000009*Feb 23 08:51:02.788: AGW-Sess: <067611141111><(SU)-10.1.1.70>Delink the session from the path*Feb 23 08:51:02.788: AGW-Sess: <067611141111>Deleting session from usergroup*Feb 23 08:51:02.788: AGW-Sess: <067611141111>Deleting sessionHere is sample output for R6 session events when MS successfully closes:
Router#debug wimax agw r6 session events*Feb 23 08:54:17.556: AGW-Sess: <067622242222>Creating the sigpak resend details 0x65F35C00, max resend 10, timeout 10000 msecs, timer type 1(11)*Feb 23 08:54:17.556: AGW-Sess: <067622242222>Starting pak resend timer 0x65F35C00 for 10000 msecs with max resend 10, current resend 0, timer type 1(11)*Feb 23 08:54:17.556: AGW-Sess: <067622242222>Deleting session with handle 0x49000008 for subscriber handle 0x6000008*Feb 23 08:54:17.556: AGW-Sess: <067622242222>Deleting the sigpak resend details 0x65F35C00*Feb 23 08:54:17.556: AGW-Sess: <067622242222>Stopping pak resend timer 0x65F35C00 for 10000 msecs with max resend 10, current resend 0, timer type 1(11)*Feb 23 08:54:17.556: AGW-Sess: <067622242222><(SU)-10.1.1.70>Delink the session from the path*Feb 23 08:54:17.556: AGW-Sess: <067622242222>Deleting session from usergroup*Feb 23 08:54:17.556: AGW-Sess: <067622242222>Stopping session timer*Feb 23 08:54:17.556: AGW-Sess: <067622242222>Deleting sessionHere is sample output for R6 FSM Session Events on a successful MS Open:
Router#debug wimax agw r6 session fsm events*Feb 23 08:56:35.700: AGW-Sess: <100022230001>Created session with handle 0x9C00000A, Id 0xA for subscriber handle 0x200000A*Feb 23 08:56:35.700: AGW-Sess: <100022230001><(SU)-10.1.1.70>:Link the session to the path*Feb 23 08:56:35.700: AGW-Sess: <100022230001>Created session*Feb 23 08:56:35.700: AGW-Sess: <100022230001>Found usrgrp **unauthenticated** based on domain for user*Feb 23 08:56:35.700: AGW-SessFSM:<100022230001>Idle(0) -> Authorizing(1) on event Rx Pre Attach Req(1) with retcode Ok(0)*Feb 23 08:56:35.700: AGW-Sess: <100022230001>Creating the sigpak resend details 0x65F35C00, max resend 10, timeout 10000 msecs, timer type 1(2)*Feb 23 08:56:35.700: AGW-Sess: <100022230001>Starting pak resend timer 0x65F35C00 for 10000 msecs with max resend 10, current resend 0, timer type 1(2)*Feb 23 08:56:35.700: AGW-SessFSM:<100022230001>Authorizing(1) -> Authorizing(1) on event Tx Pre Attach Rsp(2) with retcode Ok(0)*Feb 23 08:56:35.700: AGW-Sess: <100022230001>Deleting the sigpak resend details 0x65F35C00*Feb 23 08:56:35.700: AGW-Sess: <100022230001>Stopping pak resend timer 0x65F35C00 for 10000 msecs with max resend 10, current resend 0, timer type 1(2)*Feb 23 08:56:35.700: AGW-Sess: <100022230001>Starting protect timer Rx attach req for 110 secs*Feb 23 08:56:35.700: AGW-SessFSM:<100022230001>Authorizing(1) -> Registering(6) on event Rx Pre Attach Ack(3) with retcode Authentication Skipped(4)*Feb 23 08:56:35.700: AGW-SessFSM:<100022230001>Registering(6) -> Registering(6) on event Rx Attach Req(12) with retcode Ok(0)*Feb 23 08:56:35.700: AGW-Sess: <100022230001>Creating the sigpak resend details 0x65F35C00, max resend 10, timeout 10000 msecs, timer type 1(8)*Feb 23 08:56:35.700: AGW-Sess: <100022230001>Starting pak resend timer 0x65F35C00 for 10000 msecs with max resend 10, current resend 0, timer type 1(8)*Feb 23 08:56:35.700: AGW-Sess: <100022230001>Stopping protect timer Rx attach req*Feb 23 08:56:35.700: AGW-SessFSM:<100022230001>Registering(6) -> Registering(6) on event Tx Attach Rsp(13) with retcode Ok(0)*Feb 23 08:56:35.700: AGW-Sess: <100022230001>Deleting the sigpak resend details 0x65F35C00*Feb 23 08:56:35.700: AGW-Sess: <100022230001>Stopping pak resend timer 0x65F35C00 for 10000 msecs with max resend 10, current resend 0, timer type 1(8)*Feb 23 08:56:35.700: AGW-SessFSM:<100022230001>Registering(6) -> Ready(7) on event Rx Attach Ack(14) with retcode Ok(0)*Feb 23 08:56:35.700: AGW-SessFSM:<100022230001>Ready(7) -> Ready(7) on event Rx Attach Ack(14) with retcode Ok(0)Here is sample output for R6 FSM Session Events when MS Open fails:
Router#debug wimax agw r6 session fsm eventsGW-Sess: <067611141111><(SU)-10.1.1.70>:Link the session to the path*Feb 23 08:59:07.448: AGW-Sess: <067611141111>Created session*Feb 23 08:59:07.448: AGW-SessFSM:<067611141111>Idle(0) -> Authorizing(1) on event Rx Pre Attach Req(1) with retcode Ok(0)*Feb 23 08:59:07.448: AGW-Sess: <067611141111>Creating the sigpak resend details 0x65F35C00, max resend 10, timeout 10000 msecs, timer type 1(2)*Feb 23 08:59:07.448: AGW-Sess: <067611141111>Starting pak resend timer 0x65F35C00 for 10000 msecs with max resend 10, current resend 0, timer type 1(2)*Feb 23 08:59:07.448: AGW-SessFSM:<067611141111>Authorizing(1) -> Authorizing(1) on event Tx Pre Attach Rsp(2) with retcode Ok(0)*Feb 23 08:59:07.448: AGW-Sess: <067611141111>Deleting the sigpak resend details 0x65F35C00*Feb 23 08:59:07.448: AGW-Sess: <067611141111>Stopping pak resend timer 0x65F35C00 for 10000 msecs with max resend 10, current resend 0, timer type 1(2)*Feb 23 08:59:07.448: AGW-SessFSM:<067611141111>Authorizing(1) -> Authenticating(2) on event Rx Pre Attach Ack(3) with retcode Ok(0)*Feb 23 08:59:07.448: AGW-SessFSM:<067611141111>Authenticating(2) -> Authenticating(2) on event Tx EAP Pkt(5) with retcode Ok(0)*Feb 23 08:59:07.452: AGW-SessFSM:<067611141111>Authenticating(2) -> Authenticating(2) on event Rx EAP Pkt(4) with retcode Ok(0)*Feb 23 08:59:07.452: AGW-Sess: <067611141111>Username pushetty@eap-tls.com, domain is eap-tls.com, user is pushetty, delimiter @*Feb 23 08:59:07.452: AGW-Sess: <067611141111>Found usrgrp eap-tls.com based on domain eap-tls.com for user pushetty@eap-tls.com*Feb 23 08:59:07.456: AGW-SessFSM:<067611141111>Authenticating(2) -> Authenticating(2) on event Tx EAP Pkt(5) with retcode Ok(0)*Feb 23 08:59:07.504: AGW-SessFSM:<067611141111>Authenticating(2) -> Deleting(8) on event Auth Result Obtained(7)*Feb 23 08:59:07.504: AGW-Sess: <067611141111>Creating the sigpak resend details 0x506F3A88, max resend 10, timeout 10000 msecs, timer type 1(10)*Feb 23 08:59:07.504: AGW-Sess: <067611141111>Starting pak resend timer 0x506F3A88 for 10000 msecs with max resend 10, current resend 0, timer type 1(10)*Feb 23 08:59:07.504: AGW-SessFSM:<067611141111>Deleting(8) -> Deleting(8) on event Tx Dereg Req(22) with retcode Ok(0)*Feb 23 08:59:07.508: AGW-SessFSM:<067611141111>Deleting(8) -> Deleting(8) on event Rx Dereg Rsp(23) with retcode Ok(0)*Feb 23 08:59:07.508: AGW-Sess: <067611141111>Deleting the sigpak resend details 0x506F3A88*Feb 23 08:59:07.508: AGW-Sess: <067611141111>Stopping pak resend timer 0x506F3A88 for 10000 msecs with max resend 10, current resend 0, timer type 1(10)*Feb 23 08:59:07.508: AGW-SessFSM:<067611141111>Deleting(8) -> Cleanup(9) on event Tx Dereg Ack(24) with retcode Ok(0)Here is sample output for R6 FSM Session Events when the MS successfully closes:
Router#debug wimax agw r6 session fsm events*Feb 23 08:57:13.696: AGW-SessFSM:<100022230001>Ready(7) -> Deleting(8) on event Rx Dereq Req(19) with retcode Ok(0)*Feb 23 08:57:13.696: AGW-SessFSM:<100022230001>Deleting(8) -> Deleting(8) on event Rx Dereq Req(19) with retcode Ok(0)*Feb 23 08:57:13.696: AGW-Sess: <100022230001>Creating the sigpak resend details 0x65F35C00, max resend 10, timeout 10000 msecs, timer type 1(11)*Feb 23 08:57:13.696: AGW-Sess: <100022230001>Starting pak resend timer 0x65F35C00 for 10000 msecs with max resend 10, current resend 0, timer type 1(11)*Feb 23 08:57:13.696: AGW-SessFSM:<100022230001>Deleting(8) -> Deleting(8) on event Tx DeReg Rsp(20) with retcode Ok(0)*Feb 23 08:57:13.696: AGW-SessFSM:<100022230001>Deleting(8) -> Cleanup(9) on event Rx Dereg Ack(21) with retcode Ok(0)*Feb 23 08:57:13.696: AGW-Sess: <100022230001>Deleting session with handle 0x9C00000A for subscriber handle 0x200000A*Feb 23 08:57:13.700: AGW-Sess: <100022230001>Deleting the sigpak resend details 0x65F35C00*Feb 23 08:57:13.700: AGW-Sess: <100022230001>Stopping pak resend timer 0x65F35C00 for 10000 msecs with max resend 10, current resend 0, timer type 1(11)*Feb 23 08:57:13.700: AGW-Sess: <100022230001><(SU)-10.1.1.70>Delink the session from the path*Feb 23 08:57:13.700: AGW-Sess: <100022230001>Deleting session from usergroup*Feb 23 08:57:13.700: AGW-Sess: <100022230001>Deleting sessiondebug wimax agw r6 subscriber
To display BWG R6 subscriber information, use the debug wimax agw r6 subscriber command in Privileged EXEC mode.
debug wimax agw r6 subscriber [events | errors]
Syntax Description
events
Display information on subscriber creation and deletion.
errors
Display details of any subscriber related errors.
Defaults
There are no default values.
Command Modes
Privileged EXEC.
Command History
Examples
Here is sample R6 Subscriber Events output on a successful MS Open:
Router#debug wimax agw r6 subscriber events*Feb 23 10:29:03.804: AGW-Subs: <067622242222>Created subscriber with handle 0x29000016*Feb 23 10:29:03.804: AGW-Subs: <067622242222>Created subscriber*Feb 23 10:29:03.820: AGW-Subs: <067622242222>Starting subscriber wait for address allocation timer for 300 secs*Feb 23 10:29:03.824: AGW-Subs: <067622242222>Stopping subscriber wait for address allocation timerHere is sample R6 Subscriber Events output on a successful MS Close:
Router#debug wimax agw r6 subscriber eventsGW-Subs: <067622272222>Deleting subscriber*Feb 23 10:27:38.924: AGW-Subs: <067622272222>Deleting a subscriber with handle 0x77000013debug wimax agw redundancy
To display BWG redundancy information, use the debug wimax agw redundancy command in Privileged EXEC mode.
debug wimax agw redundancy [events | errors | tlv | packets]
Syntax Description
Defaults
There are no default values.
Command Modes
Privileged EXEC.
Command History
Examples
The following example displays BWG redundancy information:
debug wimax agw redundancy eventsOutput on ACTIVE BWG for MS Open for Ethernet-cs/Ip-cs
router#*May 19 18:00:53.420: AGW-SR: Type AGW_MAC_ID(0), Length 6, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <0032234AABCD>*May 19 18:00:53.420: AGW-SR: Type AGW_SUB_AUTH_POLICY(1), Length 2, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <0>*May 19 18:00:53.420: AGW-SR: Type AGW_SUB_AUTH_AK_CONTEXT_PRESENT(9), Length 1, Class Optional*May 19 18:00:53.420: AGW-SR: Value <0>*May 19 18:00:53.420: AGW-SR: Type UGW_SESSION_ID_CTRL_REMOTE(0), Length 4, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <0>*May 19 18:00:53.420: AGW-SR: Type UGW_SESSION_ID_CTRL_LOCAL(1), Length 4, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <4>*May 19 18:00:53.420: AGW-SR: Type UGW_SESSION_LOCAL_ADDR_SIG(2), Length 4, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <33686018>*May 19 18:00:53.420: AGW-SR: Type UGW_SESSION_REMOTE_ADDR_SIG(3), Length 4, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <167838022>*May 19 18:00:53.420: AGW-SR: Type UGW_SESSION_LOCAL_UDPPORT_SIG(4), Length 2, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <2231>*May 19 18:00:53.420: AGW-SR: Type UGW_SESSION_REMOTE_UDPPORT_SIG(5), Length 2, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <2231>*May 19 18:00:53.420: AGW-SR: Type UGW_SESSION_CS_TYPE(7), Length 2, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <0>*May 19 18:00:53.420: AGW-SR: Type UGW_SESSION_CS_TYPE_CAPABLITY(8), Length 4, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <8>*May 19 18:00:53.420: AGW-SR: Type UGW_SESSION_SLA_PROFILE_NAME(9), Length 6, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <73696C766572>*May 19 18:00:53.420: AGW-SR: Type UGW_SESSION_FLAG_UNAUTHENTICATED(45), Length 1, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <1>*May 19 18:00:53.420: AGW-SR: Type UGW_SESSION_MAX_FLOWS_SUPPORTED(48), Length 1, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <1>*May 19 18:00:53.420: AGW-SR: Type UGW_SESSION_SESSION_TIMEOUT(50), Length 4, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <0>*May 19 18:00:53.420: AGW-SR: Type UGW_SESSION_IDLE_TIMEOUT(51), Length 4, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <180>*May 19 18:00:53.420: AGW-SR: Type UGW_SESSION_SESSION_START_TIME(52), Length 4, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <1211220053>*May 19 18:00:53.420: AGW-SR: Type UGW_SESSION_SEQ_ENABLED_FOR_SIGNALING(53), Length 1, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <0>*May 19 18:00:53.420: AGW-SR: Type UGW_SESSION_IDS_REQUIRED_SIGNALLING(54), Length 1, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <0>*May 19 18:00:53.420: AGW-SR: Type UGW_SESSION_IDLE_TIMEOUT_DIRECECTION_INBOUND(55), Length 1, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <0>*May 19 18:00:53.420: AGW-SR: Type UGW_SESSION_READY_FOR_SWITCHING_TRAFFIC(56), Length 1, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <1>*May 19 18:00:53.420: AGW-SR: Type UGW_SESSION_IS_SESSION_SYNCED(57), Length 1, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <0>*May 19 18:00:53.420: AGW-SR: Type UGW_SESSION_BSID(17), Length 8, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <0A01014600000000>*May 19 18:00:53.420: AGW-SR: Type UGW_SESSION_USRGRP_DOMAIN_NAME(43), Length 15, Class Optional*May 19 18:00:53.420: AGW-SR: Value <756E61757468656E74696361746564>*May 19 18:00:53.420: AGW-SR: Type UGW_SESSION_FLAG_AUTO_PROVISIONED(12), Length 1, Class Optional*May 19 18:00:53.420: AGW-SR: Value <0>*May 19 18:00:53.420: AGW-SR: Type UGW_PATH_BSID(104), Length 8, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <0A01014600000000>*May 19 18:00:53.420: AGW-SR: Type UGW_FLOW_INDEX(60), Length 1, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <0>*May 19 18:00:53.420: AGW-SR: Type UGW_FLOW_ID_DATA_LOCAL(62), Length 4, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <4>*May 19 18:00:53.420: AGW-SR: Type UGW_FLOW_ID_DATA_REMOTE(63), Length 4, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <5>*May 19 18:00:53.420: AGW-SR: Type UGW_FLOW_REMOTE_ADDR_DATA(61), Length 4, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <167838022>*May 19 18:00:53.420: AGW-SR: Type UGW_FLOW_START_TIME(64), Length 4, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <1211220053>*May 19 18:00:53.420: AGW-SR: Type UGW_FLOW_CREATE_TIME(65), Length 8, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <0000000000000000>*May 19 18:00:53.420: AGW-SR: Type UGW_FLOW_FASTSWITCHABLE(66), Length 1, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <0>*May 19 18:00:53.420: AGW-SR: Type UGW_FLOW_SEQ_ENABLED_DATA(67), Length 1, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <0>*May 19 18:00:53.420: AGW-SR: Type UGW_FLOW_IS_FLOW_SYNCED(68), Length 1, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <0>*May 19 18:00:53.420: AGW-SR: Type UGW_FLOW_ACCT_SENDING_ACCT_RECORD(92), Length 4, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <0>*May 19 18:00:53.420: AGW-SR: Type UGW_FLOW_ACCT_PATH_SEND(93), Length 4, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <0>*May 19 18:00:53.420: AGW-SR: Type UGW_FLOW_ACCT_LAST_ACCT_RECORD(94), Length 4, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <0>*May 19 18:00:53.420: AGW-SR: Type UGW_FLOW_ACCT_TERMINATE_CAUSE(95), Length 1, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <0>*May 19 18:00:53.420: AGW-SR: Type UGW_FLOW_ACCT_ACCT_START_SENT(97), Length 1, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <0>*May 19 18:00:53.420: AGW-SR: Type UGW_FLOW_ACCT_DISCARD(98), Length 1, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <0>*May 19 18:00:53.420: AGW-SR: Type UGW_FLOW_ACCT_SESSION_ID(103), Length 4, Class Optional*May 19 18:00:53.420: AGW-SR: Value <5>*May 19 18:00:53.420: AGW-SR: Type UGW_FLOW_SF_ID(69), Length 4, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <8>*May 19 18:00:53.420: AGW-SR: Type UGW_FLOW_SF_QOS_DATA_DELIVERY_SERVICE(70), Length 1, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <1>*May 19 18:00:53.420: AGW-SR: Type UGW_FLOW_SF_QOS_MAX_LATENCY(71), Length 4, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <11>*May 19 18:00:53.420: AGW-SR: Type UGW_FLOW_SF_QOS_MAX_TRAFFIC_BURST(72), Length 4, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <0>*May 19 18:00:53.420: AGW-SR: Type UGW_FLOW_SF_QOS_MAX_TRAFFIC_RATE_SUSTAINED(73), Length 4, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <0>*May 19 18:00:53.420: AGW-SR: Type UGW_FLOW_SF_QOS_MIN_TRAFFIC_RATE_RESERVED(74), Length 4, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <41>*May 19 18:00:53.420: AGW-SR: Type UGW_FLOW_SF_QOS_POLICY_TRANSMISSION_REQUEST(75), Length 4, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <51>*May 19 18:00:53.420: AGW-SR: Type UGW_FLOW_SF_QOS_SDU_SIZE(76), Length 1, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <61>*May 19 18:00:53.420: AGW-SR: Type UGW_FLOW_SF_QOS_TOLERATED_JITTER(77), Length 4, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <71>*May 19 18:00:53.420: AGW-SR: Type UGW_FLOW_SF_QOS_TRAFFIC_PRIORITY(78), Length 1, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <0>*May 19 18:00:53.420: AGW-SR: Type UGW_FLOW_SF_QOS_UNSOLICITED_INTERVAL_GRANT(79), Length 4, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <81>*May 19 18:00:53.420: AGW-SR: Type UGW_FLOW_SF_QOS_UNSOLICITED_INTERVAL_POLLING(80), Length 4, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <0>*May 19 18:00:53.420: AGW-SR: Type UGW_FLOW_SF_QOS_REDUCED_RESOURCES_CODE(81), Length 4, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <0>*May 19 18:00:53.420: AGW-SR: Type UGW_FLOW_SF_QOS_MEDIA_FLOW_TYPE(82), Length 0, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <>*May 19 18:00:53.420: AGW-SR: Type UGW_FLOW_SF_QOS_SET_TYPE(83), Length 1, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <0>*May 19 18:00:53.420: AGW-SR: Type UGW_FLOW_SF_QOS_SET_VALUE(84), Length 1, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <184>*May 19 18:00:53.420: AGW-SR: Type UGW_FLOW_SF_CS_TYPE(85), Length 2, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <3>*May 19 18:00:53.420: AGW-SR: Type UGW_FLOW_SF_VALID_CFG(86), Length 1, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <1>*May 19 18:00:53.420: AGW-SR: Type UGW_FLOW_SF_QOS_INFO_PRESENT(87), Length 1, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <1>*May 19 18:00:53.420: AGW-SR: Type UGW_FLOW_SF_CLASSIFIER_PRESENT(88), Length 1, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <1>*May 19 18:00:53.420: AGW-SR: Type UGW_FLOW_SF_CS_TYPE_PRESENT(89), Length 1, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <1>*May 19 18:00:53.420: AGW-SR: Type UGW_FLOW_SF_QOS_SET_VALUE_PRESENT(90), Length 1, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <0>*May 19 18:00:53.420: AGW-SR: Type UGW_FLOW_SF_ID(69), Length 4, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <7>*May 19 18:00:53.420: AGW-SR: Type UGW_FLOW_SF_QOS_DATA_DELIVERY_SERVICE(70), Length 1, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <2>*May 19 18:00:53.420: AGW-SR: Type UGW_FLOW_SF_QOS_MAX_LATENCY(71), Length 4, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <1>*May 19 18:00:53.420: AGW-SR: Type UGW_FLOW_SF_QOS_MAX_TRAFFIC_BURST(72), Length 4, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <2>*May 19 18:00:53.420: AGW-SR: Type UGW_FLOW_SF_QOS_MAX_TRAFFIC_RATE_SUSTAINED(73), Length 4, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <3>*May 19 18:00:53.420: AGW-SR: Type UGW_FLOW_SF_QOS_MIN_TRAFFIC_RATE_RESERVED(74), Length 4, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <4>*May 19 18:00:53.420: AGW-SR: Type UGW_FLOW_SF_QOS_POLICY_TRANSMISSION_REQUEST(75), Length 4, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <5>*May 19 18:00:53.420: AGW-SR: Type UGW_FLOW_SF_QOS_SDU_SIZE(76), Length 1, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <49>*May 19 18:00:53.420: AGW-SR: Type UGW_FLOW_SF_QOS_TOLERATED_JITTER(77), Length 4, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <0>*May 19 18:00:53.420: AGW-SR: Type UGW_FLOW_SF_QOS_TRAFFIC_PRIORITY(78), Length 1, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <1>*May 19 18:00:53.420: AGW-SR: Type UGW_FLOW_SF_QOS_UNSOLICITED_INTERVAL_GRANT(79), Length 4, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <0>*May 19 18:00:53.420: AGW-SR: Type UGW_FLOW_SF_QOS_UNSOLICITED_INTERVAL_POLLING(80), Length 4, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <9>*May 19 18:00:53.420: AGW-SR: Type UGW_FLOW_SF_QOS_REDUCED_RESOURCES_CODE(81), Length 4, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <0>*May 19 18:00:53.420: AGW-SR: Type UGW_FLOW_SF_QOS_MEDIA_FLOW_TYPE(82), Length 0, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <>*May 19 18:00:53.420: AGW-SR: Type UGW_FLOW_SF_QOS_SET_TYPE(83), Length 1, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <0>*May 19 18:00:53.420: AGW-SR: Type UGW_FLOW_SF_QOS_SET_VALUE(84), Length 1, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <120>*May 19 18:00:53.420: AGW-SR: Type UGW_FLOW_SF_CS_TYPE(85), Length 2, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <3>*May 19 18:00:53.420: AGW-SR: Type UGW_FLOW_SF_VALID_CFG(86), Length 1, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <1>*May 19 18:00:53.420: AGW-SR: Type UGW_FLOW_SF_QOS_INFO_PRESENT(87), Length 1, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <1>*May 19 18:00:53.420: AGW-SR: Type UGW_FLOW_SF_CLASSIFIER_PRESENT(88), Length 1, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <1>*May 19 18:00:53.420: AGW-SR: Type UGW_FLOW_SF_CS_TYPE_PRESENT(89), Length 1, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <1>*May 19 18:00:53.420: AGW-SR: Type UGW_FLOW_SF_QOS_SET_VALUE_PRESENT(90), Length 1, Class Mandatory*May 19 18:00:53.420: AGW-SR: Value <0>*May 19 18:00:53.420: AGW-SR:03652A60: 00000267 00140015 00000006 0032234A ...g.........2#J03652A70: ABCD0001 00020000 00090001 00001500 +M..............03652A80: A3000000 04000000 00000100 04000000 #...............03652A90: 04000200 04020202 02000300 040A0101 ................03652AA0: 46000400 0208B700 05000208 B7000700 F.....7.....7...03652AB0: 02000000 08000400 00000800 09000673 ...............s03652AC0: 696C7665 72002D00 01010030 00010100 ilver.-....0....03652AD0: 32000400 00000000 33000400 0000B400 2.......3.....4.03652AE0: 34000448 31C05500 35000100 00360001 4..H1@U.5....6..03652AF0: 00003700 01000038 00010100 39000100 ..7....8....9...03652B00: 00110008 0A010146 00000000 002B000F .......F.....+..03652B10: 756E6175 7468656E 74696361 74656400 unauthenticated.03652B20: 0C000100 0016000C 00680008 0A010146 .........h.....F03652B30: 00000000 0017018B 00000187 003C0001 .............<..03652B40: 00003E00 04000000 04003F00 04000000 ..>.......?.....03652B50: 05003D00 040A0101 46004000 044831C0 ..=.....F.@..H1@03652B60: 55004100 08000000 00000000 00004200 U.A...........B.03652B70: 01000043 00010000 44000100 005C0004 ...C....D....\..03652B80: 00000000 005D0004 00000000 005E0004 .....].......^..03652B90: 00000000 005F0001 00006100 01000062 ....._....a....b03652BA0: 00010000 67000400 00000500 45000400 ....g.......E...03652BB0: 00000800 46000101 00470004 0000000B ....F....G......03652BC0: 00480004 00000000 00490004 00000000 .H.......I......03652BD0: 004A0004 00000029 004B0004 00000033 .J.....).K.....303652BE0: 004C0001 3D004D00 04000000 47004E00 .L..=.M.....G.N.03652BF0: 0100004F 00040000 00510050 00040000 ...O.....Q.P....03652C00: 00000051 00040000 00000052 00000053 ...Q.......R...S03652C10: 00010000 540001B8 00550002 00030056 ....T..8.U.....V03652C20: 00010100 57000101 00580001 01005900 ....W....X....Y.03652C30: 0101005A 00010000 45000400 00000700 ...Z....E.......03652C40: 46000102 00470004 00000001 00480004 F....G.......H..03652C50: 00000002 00490004 00000003 004A0004 .....I.......J..03652C60: 00000004 004B0004 00000005 004C0001 .....K.......L..03652C70: 31004D00 04000000 00004E00 0101004F 1.M.......N....O03652C80: 00040000 00000050 00040000 00090051 .......P.......Q03652C90: 00040000 00000052 00000053 00010000 .......R...S....03652CA0: 54000178 00550002 00030056 00010100 T..x.U.....V....03652CB0: 57000101 00580001 01005900 0101005A W....X....Y....Z03652CC0: 00010000 18000000 ........*May 19 18:00:53.420: AGW-SR: <0032234AABCD><F[4]>Session (Setup) Sync to Standby*May 19 18:00:53.444: AGW-SR: Type UGW_HOST_ALLOCATED_ADDR(19), Length 4, Class Mandatory*May 19 18:00:53.444: AGW-SR: Value <33685507>*May 19 18:00:53.444: AGW-SR: Type UGW_HOST_TABLE_ID(20), Length 0, Class Mandatory*May 19 18:00:53.444: AGW-SR: Value <>*May 19 18:00:53.444: AGW-SR: Type UGW_HOST_ADDR_ALLOC_SOURCE(21), Length 4, Class Mandatory*May 19 18:00:53.444: AGW-SR: Value <5>*May 19 18:00:53.444: AGW-SR: Type UGW_HOST_ADDR_REAL_LENGTH(22), Length 2, Class Mandatory*May 19 18:00:53.444: AGW-SR: Value <1040>*May 19 18:00:53.444: AGW-SR: Type UGW_HOST_ALLOCATED_PREFIX_LENGTH(23), Length 1, Class Mandatory*May 19 18:00:53.444: AGW-SR: Value <16>*May 19 18:00:53.444: AGW-SR: Type UGW_HOST_AGGREGATE_PREFIX_LENGTH(24), Length 1, Class Mandatory*May 19 18:00:53.444: AGW-SR: Value <32>*May 19 18:00:53.444: AGW-SR: Type UGW_HOST_ADDR_ORG_TYPE(25), Length 1, Class Mandatory*May 19 18:00:53.444: AGW-SR: Value <1>*May 19 18:00:53.444: AGW-SR: Type UGW_HOST_ADDR_TYPE_NUM(26), Length 1, Class Mandatory*May 19 18:00:53.444: AGW-SR: Value <33>*May 19 18:00:53.444: AGW-SR: Type UGW_HOST_ADDR_STATIC_ROUTE_ADDED(33), Length 1, Class Mandatory*May 19 18:00:53.444: AGW-SR: Value <1>*May 19 18:00:53.444: AGW-SR: Type UGW_HOST_ADDR_TYPE_STATIC_ALLOCATED(34), Length 1, Class Mandatory*May 19 18:00:53.444: AGW-SR: Value <0>*May 19 18:00:53.444: AGW-SR: Type UGW_HOST_ADDR_DYNAMIC_ADDR_ALLOCATED(35), Length 1, Class Mandatory*May 19 18:00:53.444: AGW-SR: Value <1>*May 19 18:00:53.444: AGW-SR: Type UGW_HOST_ADDR_DYNAMIC_ADDR_REQUEST(36), Length 1, Class Mandatory*May 19 18:00:53.444: AGW-SR: Value <0>*May 19 18:00:53.444: AGW-SR: Type UGW_HOST_IP_KEY(37), Length 8, Class Mandatory*May 19 18:00:53.444: AGW-SR: Value <0202000300000000>*May 19 18:00:53.444: AGW-SR: Type UGW_HOST_DHCP_SERVER_ADDR(27), Length 4, Class Optional*May 19 18:00:53.444: AGW-SR: Value <0>*May 19 18:00:53.444: AGW-SR: Type UGW_HOST_DHCP_SERVER_XID(28), Length 4, Class Optional*May 19 18:00:53.444: AGW-SR: Value <2095>*May 19 18:00:53.444: AGW-SR: Type UGW_HOST_DHCP_HARDWARE_ADDRESS_TYPE(29), Length 1, Class Optional*May 19 18:00:53.444: AGW-SR: Value <1>*May 19 18:00:53.444: AGW-SR: Type UGW_HOST_HARDWARE_ADDRESS_LEN(30), Length 1, Class Optional*May 19 18:00:53.444: AGW-SR: Value <6>*May 19 18:00:53.444: AGW-SR: Type UGW_HOST_DHCP_CLIENT_ADDR_LEASE_TIME(31), Length 4, Class Optional*May 19 18:00:53.444: AGW-SR: Value <3540>*May 19 18:00:53.444: AGW-SR: Type UGW_HOST_CLIENT_HARDWARE_ADDRESS(32), Length 16, Class Optional*May 19 18:00:53.444: AGW-SR: Value <0032234AABCD00000000000000000000>*May 19 18:00:53.444: AGW-SR: Type UGW_HOST_ETHER_TYPE(38), Length 4, Class Optional*May 19 18:00:53.444: AGW-SR: Value <2>*May 19 18:00:53.444: AGW-SR: Type UGW_SR_HOST_ETHER_HDR(39), Length 30, Class Optional*May 19 18:00:53.444: AGW-SR: Value <0032234AABCD00000C07AC0181000003025CAAAA03000000080000000000>*May 19 18:00:53.444: AGW-SR: Type UGW_HOST_ETHER_HDR_LEN(40), Length 2, Class Optional*May 19 18:00:53.444: AGW-SR: Value <26>*May 19 18:00:53.444: AGW-SR: Type UGW_HOST_STATIC_HOST(41), Length 1, Class Optional*May 19 18:00:53.444: AGW-SR: Value <0>*May 19 18:00:53.444: AGW-SR: Attr Type:UGW_HOST_FLOW_INDEX Length: 1 Value: 0*May 19 18:00:53.444: AGW-SR:03653100: 000600CA ...J03653110: 00140000 001900C2 000000BE 00130004 .......B...>....03653120: 02020003 00140000 00150004 00000005 ................03653130: 00160002 04100017 00011000 18000120 ...............03653140: 00190001 01001A00 01210021 00010100 .........!.!....03653150: 22000100 00230001 01002400 01000025 "....#....$....%03653160: 00080202 00030000 0000001B 00040000 ................03653170: 0000001C 00040000 082F001D 00010100 ........./......03653180: 1E000106 001F0004 00000DD4 00200010 ...........T. ..03653190: 0032234A ABCD0000 00000000 00000000 .2#J+M..........036531A0: 00260004 00000002 0027001E 0032234A .&.......'...2#J036531B0: ABCD0000 0C07AC01 81000003 025CAAAA +M....,......\**036531C0: 03000000 08000000 00000028 0002001A ...........(....036531D0: 00290001 000012 .).....*May 19 18:00:53.444: AGW-SR: <0032234AABCD><F[4]>Host 2.2.0.3 create synced to standbyBWG#Standby - For MS open (ethernet-cs)====================================asn#*May 19 18:00:53.431: AGW-SR:036566D0: 00140015 00000006 0032234A ABCD0001 .........2#J+M..036566E0: 00020000 00090001 00001500 A3000000 ............#...036566F0: 04000000 00000100 04000000 04000200 ................03656700: 04020202 02000300 040A0101 46000400 ............F...03656710: 0208B700 05000208 B7000700 02000000 ..7.....7.......03656720: 08000400 00000800 09000673 696C7665 ...........silve03656730: 72002D00 01010030 00010100 32000400 r.-....0....2...03656740: 00000000 33000400 0000B400 34000448 ....3.....4.4..H03656750: 31C05500 35000100 00360001 00003700 1@U.5....6....7.03656760: 01000038 00010100 39000100 00110008 ...8....9.......03656770: 0A010146 00000000 002B000F 756E6175 ...F.....+..unau03656780: 7468656E 74696361 74656400 0C000100 thenticated.....03656790: 0016000C 00680008 0A010146 00000000 .....h.....F....036567A0: 0017018B 00000187 003C0001 00003E00 .........<....>.036567B0: 04000000 04003F00 04000000 05003D00 ......?.......=.036567C0: 040A0101 46004000 044831C0 55004100 ....F.@..H1@U.A.036567D0: 08000000 00000000 00004200 01000043 ..........B....C036567E0: 00010000 44000100 005C0004 00000000 ....D....\......036567F0: 005D0004 00000000 005E0004 00000000 .].......^......03656800: 005F0001 00006100 01000062 00010000 ._....a....b....03656810: 67000400 00000500 45000400 00000800 g.......E.......03656820: 46000101 00470004 0000000B 00480004 F....G.......H..03656830: 00000000 00490004 00000000 004A0004 .....I.......J..03656840: 00000029 004B0004 00000033 004C0001 ...).K.....3.L..03656850: 3D004D00 04000000 47004E00 0100004F =.M.....G.N....O03656860: 00040000 00510050 00040000 00000051 .....Q.P.......Q03656870: 00040000 00000052 00000053 00010000 .......R...S....03656880: 540001B8 00550002 00030056 00010100 T..8.U.....V....03656890: 57000101 00580001 01005900 0101005A W....X....Y....Z036568A0: 00010000 45000400 00000700 46000102 ....E.......F...036568B0: 00470004 00000001 00480004 00000002 .G.......H......036568C0: 00490004 00000003 004A0004 00000004 .I.......J......036568D0: 004B0004 00000005 004C0001 31004D00 .K.......L..1.M.036568E0: 04000000 00004E00 0101004F 00040000 ......N....O....036568F0: 00000050 00040000 00090051 00040000 ...P.......Q....03656900: 00000052 00000053 00010000 54000178 ...R...S....T..x03656910: 00550002 00030056 00010100 57000101 .U.....V....W...03656920: 00580001 01005900 0101005A 00010000 .X....Y....Z....03656930: 18000000 19000000 ........*May 19 18:00:53.431: AGW-SR: Type AGW_MAC_ID(0), Length 6, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <0032234AABCD>*May 19 18:00:53.431: AGW-SR: Type AGW_SUB_AUTH_POLICY(1), Length 2, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <0>*May 19 18:00:53.431: AGW-SR: Type AGW_SUB_AUTH_AK_CONTEXT_PRESENT(9), Length 1, Class Optional*May 19 18:00:53.431: AGW-SR: Value <0>*May 19 18:00:53.431: AGW-SR: Usar Name not found*May 19 18:00:53.431: AGW-SR: Type UGW_SESSION_ID_CTRL_REMOTE(0), Length 4, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <0>*May 19 18:00:53.431: AGW-SR: Type UGW_SESSION_ID_CTRL_LOCAL(1), Length 4, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <4>*May 19 18:00:53.431: AGW-SR: Type UGW_SESSION_LOCAL_ADDR_SIG(2), Length 4, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <33686018>*May 19 18:00:53.431: AGW-SR: Type UGW_SESSION_REMOTE_ADDR_SIG(3), Length 4, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <167838022>*May 19 18:00:53.431: AGW-SR: Type UGW_SESSION_LOCAL_UDPPORT_SIG(4), Length 2, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <2231>*May 19 18:00:53.431: AGW-SR: Type UGW_SESSION_REMOTE_UDPPORT_SIG(5), Length 2, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <2231>*May 19 18:00:53.431: AGW-SR: Type UGW_SESSION_CS_TYPE(7), Length 2, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <0>*May 19 18:00:53.431: AGW-SR: Type UGW_SESSION_CS_TYPE_CAPABLITY(8), Length 4, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <8>*May 19 18:00:53.431: AGW-SR: Type UGW_SESSION_SLA_PROFILE_NAME(9), Length 6, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <73696C766572>*May 19 18:00:53.431: AGW-SR: Type UGW_SESSION_FLAG_UNAUTHENTICATED(45), Length 1, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <1>*May 19 18:00:53.431: AGW-SR: Type UGW_SESSION_MAX_FLOWS_SUPPORTED(48), Length 1, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <1>*May 19 18:00:53.431: AGW-SR: Type UGW_SESSION_SESSION_TIMEOUT(50), Length 4, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <0>*May 19 18:00:53.431: AGW-SR: Type UGW_SESSION_IDLE_TIMEOUT(51), Length 4, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <180>*May 19 18:00:53.431: AGW-SR: Type UGW_SESSION_SESSION_START_TIME(52), Length 4, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <1211220053>*May 19 18:00:53.431: AGW-SR: Type UGW_SESSION_SEQ_ENABLED_FOR_SIGNALING(53), Length 1, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <0>*May 19 18:00:53.431: AGW-SR: Type UGW_SESSION_IDS_REQUIRED_SIGNALLING(54), Length 1, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <0>*May 19 18:00:53.431: AGW-SR: Type UGW_SESSION_IDLE_TIMEOUT_DIRECECTION_INBOUND(55), Length 1, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <0>*May 19 18:00:53.431: AGW-SR: Type UGW_SESSION_READY_FOR_SWITCHING_TRAFFIC(56), Length 1, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <1>*May 19 18:00:53.431: AGW-SR: Type UGW_SESSION_IS_SESSION_SYNCED(57), Length 1, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <0>*May 19 18:00:53.431: AGW-SR: Type UGW_SESSION_BSID(17), Length 8, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <0A01014600000000>*May 19 18:00:53.431: AGW-SR: Type UGW_SESSION_USRGRP_DOMAIN_NAME(43), Length 15, Class Optional*May 19 18:00:53.431: AGW-SR: Value <756E61757468656E74696361746564>*May 19 18:00:53.431: AGW-SR: Type UGW_SESSION_FLAG_AUTO_PROVISIONED(12), Length 1, Class Optional*May 19 18:00:53.431: AGW-SR: Value <0>*May 19 18:00:53.431: AGW-SR: Type UGW_PATH_BSID(104), Length 8, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <0A01014600000000>*May 19 18:00:53.431: AGW-SR: Type UGW_FLOW_INDEX(60), Length 1, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <0>*May 19 18:00:53.431: AGW-SR: Type UGW_FLOW_ID_DATA_LOCAL(62), Length 4, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <4>*May 19 18:00:53.431: AGW-SR: Type UGW_FLOW_ID_DATA_REMOTE(63), Length 4, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <5>*May 19 18:00:53.431: AGW-SR: Type UGW_FLOW_REMOTE_ADDR_DATA(61), Length 4, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <167838022>*May 19 18:00:53.431: AGW-SR: Type UGW_FLOW_START_TIME(64), Length 4, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <1211220053>*May 19 18:00:53.431: AGW-SR: Type UGW_FLOW_CREATE_TIME(65), Length 8, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <0000000000000000>*May 19 18:00:53.431: AGW-SR: Type UGW_FLOW_FASTSWITCHABLE(66), Length 1, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <0>*May 19 18:00:53.431: AGW-SR: Type UGW_FLOW_SEQ_ENABLED_DATA(67), Length 1, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <0>*May 19 18:00:53.431: AGW-SR: Type UGW_FLOW_IS_FLOW_SYNCED(68), Length 1, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <0>*May 19 18:00:53.431: AGW-SR: Type UGW_FLOW_ACCT_SENDING_ACCT_RECORD(92), Length 4, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <0>*May 19 18:00:53.431: AGW-SR: Type UGW_FLOW_ACCT_PATH_SEND(93), Length 4, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <0>*May 19 18:00:53.431: AGW-SR: Type UGW_FLOW_ACCT_LAST_ACCT_RECORD(94), Length 4, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <0>*May 19 18:00:53.431: AGW-SR: Type UGW_FLOW_ACCT_TERMINATE_CAUSE(95), Length 1, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <0>*May 19 18:00:53.431: AGW-SR: Type UGW_FLOW_ACCT_ACCT_START_SENT(97), Length 1, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <0>*May 19 18:00:53.431: AGW-SR: Type UGW_FLOW_ACCT_DISCARD(98), Length 1, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <0>*May 19 18:00:53.431: AGW-SR: Type UGW_FLOW_ACCT_SESSION_ID(103), Length 4, Class Optional*May 19 18:00:53.431: AGW-SR: Value <5>*May 19 18:00:53.431: AGW-SR: Type UGW_FLOW_SF_ID(69), Length 4, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <8>*May 19 18:00:53.431: AGW-SR: Type UGW_FLOW_SF_QOS_DATA_DELIVERY_SERVICE(70), Length 1, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <1>*May 19 18:00:53.431: AGW-SR: Type UGW_FLOW_SF_QOS_MAX_LATENCY(71), Length 4, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <11>*May 19 18:00:53.431: AGW-SR: Type UGW_FLOW_SF_QOS_MAX_TRAFFIC_BURST(72), Length 4, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <0>*May 19 18:00:53.431: AGW-SR: Type UGW_FLOW_SF_QOS_MAX_TRAFFIC_RATE_SUSTAINED(73), Length 4, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <0>*May 19 18:00:53.431: AGW-SR: Type UGW_FLOW_SF_QOS_MIN_TRAFFIC_RATE_RESERVED(74), Length 4, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <41>*May 19 18:00:53.431: AGW-SR: Type UGW_FLOW_SF_QOS_POLICY_TRANSMISSION_REQUEST(75), Length 4, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <51>*May 19 18:00:53.431: AGW-SR: Type UGW_FLOW_SF_QOS_SDU_SIZE(76), Length 1, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <61>*May 19 18:00:53.431: AGW-SR: Type UGW_FLOW_SF_QOS_TOLERATED_JITTER(77), Length 4, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <71>*May 19 18:00:53.431: AGW-SR: Type UGW_FLOW_SF_QOS_TRAFFIC_PRIORITY(78), Length 1, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <0>*May 19 18:00:53.431: AGW-SR: Type UGW_FLOW_SF_QOS_UNSOLICITED_INTERVAL_GRANT(79), Length 4, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <81>*May 19 18:00:53.431: AGW-SR: Type UGW_FLOW_SF_QOS_UNSOLICITED_INTERVAL_POLLING(80), Length 4, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <0>*May 19 18:00:53.431: AGW-SR: Type UGW_FLOW_SF_QOS_REDUCED_RESOURCES_CODE(81), Length 4, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <0>*May 19 18:00:53.431: AGW-SR: Type UGW_FLOW_SF_QOS_MEDIA_FLOW_TYPE(82), Length 0, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <>*May 19 18:00:53.431: AGW-SR: Type UGW_FLOW_SF_QOS_SET_TYPE(83), Length 1, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <0>*May 19 18:00:53.431: AGW-SR: Type UGW_FLOW_SF_QOS_SET_VALUE(84), Length 1, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <184>*May 19 18:00:53.431: AGW-SR: Type UGW_FLOW_SF_CS_TYPE(85), Length 2, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <3>*May 19 18:00:53.431: AGW-SR: Type UGW_FLOW_SF_VALID_CFG(86), Length 1, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <1>*May 19 18:00:53.431: AGW-SR: Type UGW_FLOW_SF_QOS_INFO_PRESENT(87), Length 1, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <1>*May 19 18:00:53.431: AGW-SR: Type UGW_FLOW_SF_CLASSIFIER_PRESENT(88), Length 1, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <1>*May 19 18:00:53.431: AGW-SR: Type UGW_FLOW_SF_CS_TYPE_PRESENT(89), Length 1, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <1>*May 19 18:00:53.431: AGW-SR: Type UGW_FLOW_SF_QOS_SET_VALUE_PRESENT(90), Length 1, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <0>*May 19 18:00:53.431: AGW-SR: Type UGW_FLOW_SF_ID(69), Length 4, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <7>*May 19 18:00:53.431: AGW-SR: Type UGW_FLOW_SF_QOS_DATA_DELIVERY_SERVICE(70), Length 1, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <2>*May 19 18:00:53.431: AGW-SR: Type UGW_FLOW_SF_QOS_MAX_LATENCY(71), Length 4, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <1>*May 19 18:00:53.431: AGW-SR: Type UGW_FLOW_SF_QOS_MAX_TRAFFIC_BURST(72), Length 4, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <2>*May 19 18:00:53.431: AGW-SR: Type UGW_FLOW_SF_QOS_MAX_TRAFFIC_RATE_SUSTAINED(73), Length 4, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <3>*May 19 18:00:53.431: AGW-SR: Type UGW_FLOW_SF_QOS_MIN_TRAFFIC_RATE_RESERVED(74), Length 4, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <4>*May 19 18:00:53.431: AGW-SR: Type UGW_FLOW_SF_QOS_POLICY_TRANSMISSION_REQUEST(75), Length 4, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <5>*May 19 18:00:53.431: AGW-SR: Type UGW_FLOW_SF_QOS_SDU_SIZE(76), Length 1, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <49>*May 19 18:00:53.431: AGW-SR: Type UGW_FLOW_SF_QOS_TOLERATED_JITTER(77), Length 4, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <0>*May 19 18:00:53.431: AGW-SR: Type UGW_FLOW_SF_QOS_TRAFFIC_PRIORITY(78), Length 1, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <1>*May 19 18:00:53.431: AGW-SR: Type UGW_FLOW_SF_QOS_UNSOLICITED_INTERVAL_GRANT(79), Length 4, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <0>*May 19 18:00:53.431: AGW-SR: Type UGW_FLOW_SF_QOS_UNSOLICITED_INTERVAL_POLLING(80), Length 4, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <9>*May 19 18:00:53.431: AGW-SR: Type UGW_FLOW_SF_QOS_REDUCED_RESOURCES_CODE(81), Length 4, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <0>*May 19 18:00:53.431: AGW-SR: Type UGW_FLOW_SF_QOS_MEDIA_FLOW_TYPE(82), Length 0, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <>*May 19 18:00:53.431: AGW-SR: Type UGW_FLOW_SF_QOS_SET_TYPE(83), Length 1, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <0>*May 19 18:00:53.431: AGW-SR: Type UGW_FLOW_SF_QOS_SET_VALUE(84), Length 1, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <120>*May 19 18:00:53.431: AGW-SR: Type UGW_FLOW_SF_CS_TYPE(85), Length 2, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <3>*May 19 18:00:53.431: AGW-SR: Type UGW_FLOW_SF_VALID_CFG(86), Length 1, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <1>*May 19 18:00:53.431: AGW-SR: Type UGW_FLOW_SF_QOS_INFO_PRESENT(87), Length 1, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <1>*May 19 18:00:53.431: AGW-SR: Type UGW_FLOW_SF_CLASSIFIER_PRESENT(88), Length 1, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <1>*May 19 18:00:53.431: AGW-SR: Type UGW_FLOW_SF_CS_TYPE_PRESENT(89), Length 1, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <1>*May 19 18:00:53.431: AGW-SR: Type UGW_FLOW_SF_QOS_SET_VALUE_PRESENT(90), Length 1, Class Mandatory*May 19 18:00:53.431: AGW-SR: Value <0>*May 19 18:00:53.439: AGW-SR:03656C20: 00140000 001900C2 .......B03656C30: 000000BE 00130004 02020003 00140000 ...>............03656C40: 00150004 00000005 00160002 04100017 ................03656C50: 00011000 18000120 00190001 01001A00 ....... ........03656C60: 01210021 00010100 22000100 00230001 .!.!...."....#..03656C70: 01002400 01000025 00080202 00030000 ..$....%........03656C80: 0000001B 00040000 0000001C 00040000 ................03656C90: 082F001D 00010100 1E000106 001F0004 ./..............03656CA0: 00000DD4 00200010 0032234A ABCD0000 ...T. ...2#J+M..03656CB0: 00000000 00000000 00260004 00000002 .........&......03656CC0: 0027001E 0032234A ABCD0000 0C07AC01 .'...2#J+M....,.03656CD0: 81000003 025CAAAA 03000000 08000000 .....\**........03656CE0: 00000028 0002001A 00290001 00001200 ...(.....)......03656CF0: 010000 ...*May 19 18:00:53.439: AGW-SR: Type UGW_HOST_ALLOCATED_ADDR(19), Length 4, Class Mandatory*May 19 18:00:53.439: AGW-SR: Value <33685507>*May 19 18:00:53.439: AGW-SR: Type UGW_HOST_TABLE_ID(20), Length 0, Class Mandatory*May 19 18:00:53.439: AGW-SR: Value <>*May 19 18:00:53.439: AGW-SR: Type UGW_HOST_ADDR_ALLOC_SOURCE(21), Length 4, Class Mandatory*May 19 18:00:53.439: AGW-SR: Value <5>*May 19 18:00:53.439: AGW-SR: Type UGW_HOST_ADDR_REAL_LENGTH(22), Length 2, Class Mandatory*May 19 18:00:53.439: AGW-SR: Value <1040>*May 19 18:00:53.439: AGW-SR: Type UGW_HOST_ALLOCATED_PREFIX_LENGTH(23), Length 1, Class Mandatory*May 19 18:00:53.439: AGW-SR: Value <16>*May 19 18:00:53.439: AGW-SR: Type UGW_HOST_AGGREGATE_PREFIX_LENGTH(24), Length 1, Class Mandatory*May 19 18:00:53.439: AGW-SR: Value <32>*May 19 18:00:53.439: AGW-SR: Type UGW_HOST_ADDR_ORG_TYPE(25), Length 1, Class Mandatory*May 19 18:00:53.439: AGW-SR: Value <1>*May 19 18:00:53.439: AGW-SR: Type UGW_HOST_ADDR_TYPE_NUM(26), Length 1, Class Mandatory*May 19 18:00:53.439: AGW-SR: Value <33>*May 19 18:00:53.439: AGW-SR: Type UGW_HOST_ADDR_STATIC_ROUTE_ADDED(33), Length 1, Class Mandatory*May 19 18:00:53.439: AGW-SR: Value <1>*May 19 18:00:53.439: AGW-SR: Type UGW_HOST_ADDR_TYPE_STATIC_ALLOCATED(34), Length 1, Class Mandatory*May 19 18:00:53.439: AGW-SR: Value <0>*May 19 18:00:53.439: AGW-SR: Type UGW_HOST_ADDR_DYNAMIC_ADDR_ALLOCATED(35), Length 1, Class Mandatory*May 19 18:00:53.439: AGW-SR: Value <1>*May 19 18:00:53.439: AGW-SR: Type UGW_HOST_ADDR_DYNAMIC_ADDR_REQUEST(36), Length 1, Class Mandatory*May 19 18:00:53.439: AGW-SR: Value <0>*May 19 18:00:53.439: AGW-SR: Type UGW_HOST_IP_KEY(37), Length 8, Class Mandatory*May 19 18:00:53.439: AGW-SR: Value <0202000300000000>*May 19 18:00:53.439: AGW-SR: Type UGW_HOST_DHCP_SERVER_ADDR(27), Length 4, Class Optional*May 19 18:00:53.439: AGW-SR: Value <0>*May 19 18:00:53.439: AGW-SR: Type UGW_HOST_DHCP_SERVER_XID(28), Length 4, Class Optional*May 19 18:00:53.439: AGW-SR: Value <2095>*May 19 18:00:53.439: AGW-SR: Type UGW_HOST_DHCP_HARDWARE_ADDRESS_TYPE(29), Length 1, Class Optional*May 19 18:00:53.439: AGW-SR: Value <1>*May 19 18:00:53.439: AGW-SR: Type UGW_HOST_HARDWARE_ADDRESS_LEN(30), Length 1, Class Optional*May 19 18:00:53.439: AGW-SR: Value <6>*May 19 18:00:53.439: AGW-SR: Type UGW_HOST_DHCP_CLIENT_ADDR_LEASE_TIME(31), Length 4, Class Optional*May 19 18:00:53.439: AGW-SR: Value <3540>*May 19 18:00:53.439: AGW-SR: Type UGW_HOST_CLIENT_HARDWARE_ADDRESS(32), Length 16, Class Optional*May 19 18:00:53.439: AGW-SR: Value <0032234AABCD00000000000000000000>*May 19 18:00:53.439: AGW-SR: Type UGW_HOST_ETHER_TYPE(38), Length 4, Class Optional*May 19 18:00:53.439: AGW-SR: Value <2>*May 19 18:00:53.439: AGW-SR: Type UGW_SR_HOST_ETHER_HDR(39), Length 30, Class Optional*May 19 18:00:53.439: AGW-SR: Value <0032234AABCD00000C07AC0181000003025CAAAA03000000080000000000>BWG#*May 19 18:00:53.439: AGW-SR: Type UGW_HOST_ETHER_HDR_LEN(40), Length 2, Class Optional*May 19 18:00:53.439: AGW-SR: Value <26>*May 19 18:00:53.439: AGW-SR: Type UGW_HOST_STATIC_HOST(41), Length 1, Class Optional*May 19 18:00:53.439: AGW-SR: Value <0>*May 19 18:00:53.439: AGW-SR: <0032234AABCD><F[4]>Subscriber 2.2.0.3 synced from activeOutput on STANDBY BWG for MS Open
Mar 4 20:09:29.224: AGW-SR:20135C40: 001400A9 ...)20135C50: 00000006 06761112 11110001 00020012 .....v..........20135C60: 00030014 1EB253DD E845CFF0 C5281F33 .....2S]hEOpE(.320135C70: AF951520 22FE51FF 00020004 00000001 /.. "~Q.........20135C80: 00040008 E0D148B4 9E578601 00050002 ....`QH4.W......20135C90: 3A980006 00020001 00070001 00000800 :...............20135CA0: 01000009 00010100 0A000E0A 01014602 ..............F.20135CB0: 02020206 76111211 11000B00 02800900 ....v...........20135CC0: 0C000103 000D0001 0C000E00 02800800 ................20135CD0: 0F000108 00100001 05001100 02000900 ................20135CE0: 12000109 00130001 08001400 02000800 ................20135CF0: 15000108 00160001 02001500 F3000000 ............s...20135D00: 04000000 00000100 04000000 05000200 ...............20135D10: 04020202 02000300 040A0101 46000400 ............F...20135D20: 0208B700 05000208 B7001E00 01000020 ..7.....7......20135D30: 00010000 22000100 00210001 01002300 ...."....!....#.20135D40: 0400003A 98002400 04000000 00002500 ...:..$.......%.20135D50: 08000000 0010B765 E8002600 01000027 ......7eh.&....'20135D60: 00010000 28000100 00290001 01002A00 ....(....)....*.20135D70: 0100001F 00403C9E 68DEDCDD 94126A63 .....@<.h^\]..jc20135D80: B21697BC 95E0140C E89BFD1D 31DB19B8 2..<.`..h.}.1[.820135D90: F95C8E1A ECC83CCE 2F570CD8 176637C4 y\..lH<N/W.X.f7D20135DA0: D8AD4E43 7DEA7D88 8BDC44DC 35FEFC20 X-NC}j}..\D\5~|20135DB0: 679740D4 028B001B 00147075 73686574 g.@T......pushet20135DC0: 74794065 61702D74 6C732E63 6F6D001C ty@eap-tls.com..20135DD0: 00072A2A 616E792A 2A000600 13636C61 ..**any**....cla20135DE0: 73732D77 696D6178 2D636861 6E676564 ss-wimax-changed20135DF0: 0016000C 00550008 0A010146 00000000 .....U.....F....20135E00: 0017017C 00000178 002B0001 00002D00 ...|...x.+....-.20135E10: 04000000 08002E00 04000000 19002F00 ............../.20135E20: 08000000 0010B766 C8003000 08000000 ......7fH.0.....20135E30: 00000000 00003100 01000032 00010000 ......1....2....20135E40: 33000100 00490004 00000001 004A0004 3....I.......J..20135E50: 00000000 004B0004 00000001 004C0001 .....K.......L..20135E60: 00004D00 0102004E 00010100 4F000100 ..M....N....O...20135E70: 00540004 0000000E 00340004 00000010 .T.......4......20135E80: 00350001 01003600 04000000 0B003700 .5....6.......7.20135E90: 04000000 00003800 04000000 00003900 ......8.......9.20135EA0: 04000000 00003A00 04000000 33003B00 ......:.....3.;.20135EB0: 013D003C 00040000 0047003D 00010000 .=.<.....G.=....20135EC0: 3E000400 00005100 3F000400 00000000 >.....Q.?.......20135ED0: 40000400 00000000 41000000 42000100 @.......A...B...20135EE0: 00430001 00004400 01010045 00010100 .C....D....E....20135EF0: 46000101 00470001 00003400 04000000 F....G....4.....20135F00: 0F003500 01020036 00040000 00010037 ..5....6.......720135F10: 00040000 00020038 00040000 00030039 .......8.......920135F20: 00040000 0004003A 00040000 0005003B .......:.......;20135F30: 00013100 3C000400 00000000 3D000101 ..1.<.......=...20135F40: 003E0004 00000000 003F0004 00000009 .>.......?......20135F50: 00400004 00000000 00410000 00420001 .@.......A...B..20135F60: 00004300 01000044 00010100 45000101 ..C....D....E...20135F70: 00460001 01004700 01000017 00028009 .F....G.........20135F80: 00180000 00190094 00000090 00080004 ................20135F90: 02020002 00090002 0000000A 00040000 ................20135FA0: 0005000B 00020420 000C0001 20000D00 ....... .... ...20135FB0: 0120000E 00010100 0F000121 00160001 . .........!....20135FC0: 01001700 01000018 00010100 19000100 ................20135FD0: 001A0008 02020002 00000000 00100004 ................20135FE0: 00000000 00110004 00001415 00120001 ................20135FF0: 01001300 01060014 00100676 11121111 ...........v....20136000: 00000000 00000000 00000015 00040000 ...........20136010: 0DD40007 00010000 56000101 7A .T......V...zMar 4 20:09:29.228: AGW-SR: Type AGW_MAC_ID(0), Length 6, Class MandatoryMar 4 20:09:29.228: AGW-SR: Value <067611121111>Mar 4 20:09:29.228: AGW-SR: Type AGW_SUB_AUTH_POLICY(1), Length 2, Class MandatoryMar 4 20:09:29.228: AGW-SR: Value <18>Mar 4 20:09:29.228: AGW-SR: Type AGW_SUB_AUTH_AK(3), Length 20, Class OptionalMar 4 20:09:29.228: AGW-SR: Value <1EB253DDE845CFF0C5281F33AF95152022FE51FF>Mar 4 20:09:29.228: AGW-SR: Type AGW_SUB_AUTH_AK_METHOD(2), Length 4, Class OptionalMar 4 20:09:29.228: AGW-SR: Value <1>Mar 4 20:09:29.228: AGW-SR: Type AGW_SUB_AUTH_AKID(4), Length 8, Class OptionalMar 4 20:09:29.228: AGW-SR: Value <E0D148B49E578601>Mar 4 20:09:29.228: AGW-SR: Type AGW_SUB_AUTH_AKLIFETIME(5), Length 2, Class OptionalMar 4 20:09:29.228: AGW-SR: Value <15000>Mar 4 20:09:29.228: AGW-SR: Type AGW_SUB_AUTH_CMAC_KEY_COUNT(6), Length 2, Class OptionalMar 4 20:09:29.228: AGW-SR: Value <1>Mar 4 20:09:29.228: AGW-SR: Type AGW_SUB_AUTH_AK_SEQUENCE_NUM(7), Length 1, Class OptionalMar 4 20:09:29.228: AGW-SR: Value <0>Mar 4 20:09:29.228: AGW-SR: Type AGW_SUB_AUTH_PMK_SEQUENCE_NUM(8), Length 1, Class OptionalMar 4 20:09:29.228: AGW-SR: Value <0>Mar 4 20:09:29.228: AGW-SR: Type AGW_SUB_AUTH_AK_CONTEXT_PRESENT(9), Length 1, Class OptionalMar 4 20:09:29.228: AGW-SR: Value <1>Mar 4 20:09:29.228: AGW-SR: Type AGW_TID_HASH_KEY(10), Length 14, Class MandatoryMar 4 20:09:29.228: AGW-SR: Value <0A01014602020202067611121111>Mar 4 20:09:29.228: AGW-SR: Type AGW_OUR_TID(11), Length 2, Class MandatoryMar 4 20:09:29.228: AGW-SR: Value <32777>Mar 4 20:09:29.228: AGW-SR: Type AGW_OUR_TID_FT(12), Length 1, Class MandatoryMar 4 20:09:29.228: AGW-SR: Value <3>Mar 4 20:09:29.228: AGW-SR: Type AGW_OUR_TID_MT(13), Length 1, Class MandatoryMar 4 20:09:29.228: AGW-SR: Value <12>Mar 4 20:09:29.228: AGW-SR: Type AGW_OUR_PREVIOUS_TID(14), Length 2, Class MandatoryMar 4 20:09:29.228: AGW-SR: Value <32776>Mar 4 20:09:29.228: AGW-SR: Type AGW_OUR_PREVIOUS_TID_FT(15), Length 1, Class MandatoryMar 4 20:09:29.228: AGW-SR: Value <8>Mar 4 20:09:29.228: AGW-SR: Type AGW_OUR_PREVIOUS_TID_MT(16), Length 1, Class MandatoryMar 4 20:09:29.228: AGW-SR: Value <5>Mar 4 20:09:29.228: AGW-SR: Type AGW_PEER_TID(17), Length 2, Class MandatoryMar 4 20:09:29.228: AGW-SR: Value <9>Mar 4 20:09:29.228: AGW-SR: Type AGW_PEER_TID_FT(18), Length 1, Class MandatoryMar 4 20:09:29.228: AGW-SR: Value <9>Mar 4 20:09:29.228: AGW-SR: Type AGW_PEER_TID_MT(19), Length 1, Class MandatoryMar 4 20:09:29.228: AGW-SR: Value <8>Mar 4 20:09:29.228: AGW-SR: Type AGW_PEER_PREVIOUS_TID(20), Length 2, Class MandatoryMar 4 20:09:29.228: AGW-SR: Value <8>Mar 4 20:09:29.228: AGW-SR: Type AGW_PEER_PREVIOUS_TID_FT(21), Length 1, Class MandatoryMar 4 20:09:29.228: AGW-SR: Value <8>Mar 4 20:09:29.228: AGW-SR: Type AGW_PEER_PREVIOUS_TID_MT(22), Length 1, Class MandatoryMar 4 20:09:29.228: AGW-SR: Value <2>Mar 4 20:09:29.228: AGW-SR: Type UGW_SESSION_ID_CTRL_REMOTE(0), Length 4, Class MandatoryMar 4 20:09:29.228: AGW-SR: Value <0>Mar 4 20:09:29.228: AGW-SR: Type UGW_SESSION_ID_CTRL_LOCAL(1), Length 4, Class MandatoryMar 4 20:09:29.228: AGW-SR: Value <5>Mar 4 20:09:29.228: AGW-SR: Type UGW_SESSION_LOCAL_ADDR_SIG(2), Length 4, Class MandatoryMar 4 20:09:29.228: AGW-SR: Value <33686018>Mar 4 20:09:29.228: AGW-SR: Type UGW_SESSION_REMOTE_ADDR_SIG(3), Length 4, Class MandatoryMar 4 20:09:29.228: AGW-SR: Value <167838022>Mar 4 20:09:29.228: AGW-SR: Type UGW_SESSION_LOCAL_UDPPORT_SIG(4), Length 2, Class MandatoryMar 4 20:09:29.228: AGW-SR: Value <2231>Mar 4 20:09:29.228: AGW-SR: Type UGW_SESSION_REMOTE_UDPPORT_SIG(5), Length 2, Class MandatoryMar 4 20:09:29.228: AGW-SR: Value <2231>Mar 4 20:09:29.228: AGW-SR: Type UGW_SESSION_FLAG_UNAUTHENTICATED(30), Length 1, Class MandatoryMar 4 20:09:29.228: AGW-SR: Value <0>Mar 4 20:09:29.228: AGW-SR: Type UGW_SESSION_FLAG_NW_BEHIND_MS(32), Length 1, Class MandatoryMar 4 20:09:29.228: AGW-SR: Value <0>Mar 4 20:09:29.228: AGW-SR: Type UGW_SESSION_FLAG_FRAMED_ROUTE_DOWNLOADED(34), Length 1, Class MandatoryMar 4 20:09:29.228: AGW-SR: Value <0>Mar 4 20:09:29.228: AGW-SR: Type UGW_SESSION_MAX_FLOWS_SUPPORTED(33), Length 1, Class MandatoryMar 4 20:09:29.228: AGW-SR: Value <1>Mar 4 20:09:29.228: AGW-SR: Type UGW_SESSION_SESSION_TIMEOUT(35), Length 4, Class MandatoryMar 4 20:09:29.228: AGW-SR: Value <15000>Mar 4 20:09:29.228: AGW-SR: Type UGW_SESSION_IDLE_TIMEOUT(36), Length 4, Class MandatoryMar 4 20:09:29.228: AGW-SR: Value <0>Mar 4 20:09:29.228: AGW-SR: Type UGW_SESSION_SESSION_START_TIME(37), Length 8, Class MandatoryMar 4 20:09:29.228: AGW-SR: Value <0000000010B765E8>Mar 4 20:09:29.228: AGW-SR: Type UGW_SESSION_SEQ_ENABLED_FOR_SIGNALING(38), Length 1, Class MandatoryMar 4 20:09:29.228: AGW-SR: Value <0>Mar 4 20:09:29.228: AGW-SR: Type UGW_SESSION_IDS_REQUIRED_SIGNALLING(39), Length 1, Class MandatoryMar 4 20:09:29.228: AGW-SR: Value <0>Mar 4 20:09:29.228: AGW-SR: Type UGW_SESSION_IDLE_TIMEOUT_DIRECECTION_INBOUND(40), Length 1, Class MandatoryMar 4 20:09:29.228: AGW-SR: Value <0>Mar 4 20:09:29.228: AGW-SR: Type UGW_SESSION_READY_FOR_SWITCHING_TRAFFIC(41), Length 1, Class MandatoryMar 4 20:09:29.228: AGW-SR: Value <1>Mar 4 20:09:29.228: AGW-SR: Type UGW_SESSION_IS_SESSION_SYNCED(42), Length 1, Class MandatoryMar 4 20:09:29.228: AGW-SR: Value <0>Mar 4 20:09:29.228: AGW-SR: Type UGW_SESSION_MASTER_SESSION_KEY(31), Length 64, Class OptionalMar 4 20:09:29.228: AGW-SR: Value <3C9E68DEDCDD94126A63B21697BC95E0140CE89BFD1D31DB19B8F95C8E1AECC83CCE2F570CD8176637C4D8AD4 E437DEA7D888BDC44DC35FEFC20679740D4028B>Mar 4 20:09:29.228: AGW-SR: Type UGW_SESSION_USRGRP_USER_NAME(27), Length 20, Class OptionalMar 4 20:09:29.228: AGW-SR: Value <7075736865747479406561702D746C732E636F6D>Mar 4 20:09:29.228: AGW-SR: Type UGW_SESSION_USRGRP_DOMAIN_NAME(28), Length 7, Class OptionalMar 4 20:09:29.228: AGW-SR: Value <2A2A616E792A2A>Mar 4 20:09:29.228: AGW-SR: Type UGW_SESSION_ACCT_AAA_AT_CLASS(6), Length 19, Class OptionalMar 4 20:09:29.228: AGW-SR: Value <636C6173732D77696D61782D6368616E676564>Mar 4 20:09:29.228: AGW-SR: Type UGW_PATH_BSID(85), Length 8, Class MandatoryMar 4 20:09:29.228: AGW-SR: Value <0A01014600000000>Mar 4 20:09:29.228: AGW-SR: <067611121111><F[0]>Replacing Local Acct Context Session IdReceived From Active: 14Mar 4 20:09:29.228: AGW-SR: Type UGW_FLOW_INDEX(43), Length 1, Class MandatoryMar 4 20:09:29.228: AGW-SR: Value <0>Mar 4 20:09:29.228: AGW-SR: Type UGW_FLOW_ID_DATA_LOCAL(45), Length 4, Class MandatoryMar 4 20:09:29.228: AGW-SR: Value <8>Mar 4 20:09:29.228: AGW-SR: Type UGW_FLOW_ID_DATA_REMOTE(46), Length 4, Class MandatoryMar 4 20:09:29.228: AGW-SR: Value <25>Mar 4 20:09:29.228: AGW-SR: Type UGW_FLOW_START_TIME(47), Length 8, Class MandatoryMar 4 20:09:29.228: AGW-SR: Value <0000000010B766C8>Mar 4 20:09:29.228: AGW-SR: Type UGW_FLOW_CREATE_TIME(48), Length 8, Class MandatoryMar 4 20:09:29.228: AGW-SR: Value <0000000000000000>Mar 4 20:09:29.228: AGW-SR: Type UGW_FLOW_FASTSWITCHABLE(49), Length 1, Class MandatoryMar 4 20:09:29.228: AGW-SR: Value <0>Mar 4 20:09:29.228: AGW-SR: Type UGW_FLOW_SEQ_ENABLED_DATA(50), Length 1, Class MandatoryMar 4 20:09:29.228: AGW-SR: Value <0>Mar 4 20:09:29.228: AGW-SR: Type UGW_FLOW_IS_FLOW_SYNCED(51), Length 1, Class MandatoryMar 4 20:09:29.228: AGW-SR: Value <0>Mar 4 20:09:29.228: AGW-SR: Type UGW_FLOW_ACCT_SENDING_ACCT_RECORD(73), Length 4, Class MandatoryMar 4 20:09:29.228: AGW-SR: Value <1>Mar 4 20:09:29.228: AGW-SR: Type UGW_FLOW_ACCT_PATH_SEND(74), Length 4, Class MandatoryMar 4 20:09:29.228: AGW-SR: Value <0>Mar 4 20:09:29.228: AGW-SR: Type UGW_FLOW_ACCT_LAST_ACCT_RECORD(75), Length 4, Class MandatoryMar 4 20:09:29.228: AGW-SR: Value <1>Mar 4 20:09:29.228: AGW-SR: Type UGW_FLOW_ACCT_TERMINATE_CAUSE(76), Length 1, Class MandatoryMar 4 20:09:29.228: AGW-SR: Value <0>Mar 4 20:09:29.228: AGW-SR: Type UGW_FLOW_ACCT_AIRLINK_STATE(77), Length 1, Class MandatoryMar 4 20:09:29.228: AGW-SR: Value <2>Mar 4 20:09:29.228: AGW-SR: Type UGW_FLOW_ACCT_ACCT_START_SENT(78), Length 1, Class MandatoryMar 4 20:09:29.228: AGW-SR: Value <1>Mar 4 20:09:29.228: AGW-SR: Type UGW_FLOW_ACCT_DISCARD(79), Length 1, Class MandatoryMar 4 20:09:29.232: AGW-SR: Value <0>Mar 4 20:09:29.232: AGW-SR: Type UGW_FLOW_ACCT_SESSION_ID(84), Length 4, Class OptionalMar 4 20:09:29.232: AGW-SR: Value <14>Mar 4 20:09:29.232: AGW-SR: Type AGW_FLOW_CURR_TID_USED(23), Length 2, Class MandatoryMar 4 20:09:29.232: AGW-SR: Value <32777>Mar 4 20:09:29.232: AGW-SR: Type UGW_FLOW_SF_ID(52), Length 4, Class MandatoryMar 4 20:09:29.232: AGW-SR: Value <16>Mar 4 20:09:29.232: AGW-SR: Type UGW_FLOW_SF_QOS_DATA_DELIVERY_SERVICE(53), Length 1, Class MandatoryMar 4 20:09:29.232: AGW-SR: Value <1>Mar 4 20:09:29.232: AGW-SR: Type UGW_FLOW_SF_QOS_MAX_LATENCY(54), Length 4, Class MandatoryMar 4 20:09:29.232: AGW-SR: Value <11>Mar 4 20:09:29.232: AGW-SR: Type UGW_FLOW_SF_QOS_MAX_TRAFFIC_BURST(55), Length 4, Class MandatoryMar 4 20:09:29.232: AGW-SR: Value <0>Mar 4 20:09:29.232: AGW-SR: Type UGW_FLOW_SF_QOS_MAX_TRAFFIC_RATE_SUSTAINED(56), Length 4, Class MandatoryMar 4 20:09:29.232: AGW-SR: Value <0>Mar 4 20:09:29.232: AGW-SR: Type UGW_FLOW_SF_QOS_MIN_TRAFFIC_RATE_RESERVED(57), Length 4, Class MandatoryMar 4 20:09:29.232: AGW-SR: Value <0>Mar 4 20:09:29.232: AGW-SR: Type UGW_FLOW_SF_QOS_POLICY_TRANSMISSION_REQUEST(58), Length 4, Class MandatoryMar 4 20:09:29.232: AGW-SR: Value <51>Mar 4 20:09:29.232: AGW-SR: Type UGW_FLOW_SF_QOS_SDU_SIZE(59), Length 1, Class MandatoryMar 4 20:09:29.232: AGW-SR: Value <61>Mar 4 20:09:29.232: AGW-SR: Type UGW_FLOW_SF_QOS_TOLERATED_JITTER(60), Length 4, Class MandatoryMar 4 20:09:29.232: AGW-SR: Value <71>Mar 4 20:09:29.232: AGW-SR: Type UGW_FLOW_SF_QOS_TRAFFIC_PRIORITY(61), Length 1, Class MandatoryMar 4 20:09:29.232: AGW-SR: Value <0>Mar 4 20:09:29.232: AGW-SR: Type UGW_FLOW_SF_QOS_UNSOLICITED_INTERVAL_GRANT(62), Length 4, Class MandatoryMar 4 20:09:29.232: AGW-SR: Value <81>Mar 4 20:09:29.232: AGW-SR: Type UGW_FLOW_SF_QOS_UNSOLICITED_INTERVAL_POLLING(63), Length 4, Class MandatoryMar 4 20:09:29.232: AGW-SR: Value <0>Mar 4 20:09:29.232: AGW-SR: Type UGW_FLOW_SF_QOS_REDUCED_RESOURCES_CODE(64), Length 4, Class MandatoryMar 4 20:09:29.232: AGW-SR: Value <0>Mar 4 20:09:29.232: AGW-SR: Type UGW_FLOW_SF_QOS_MEDIA_FLOW_TYPE(65), Length 0, Class MandatoryMar 4 20:09:29.232: AGW-SR: Value <>Mar 4 20:09:29.232: AGW-SR: Type UGW_FLOW_SF_QOS_SET_TYPE(66), Length 1, Class MandatoryMar 4 20:09:29.232: AGW-SR: Value <0>Mar 4 20:09:29.232: AGW-SR: Type UGW_FLOW_SF_QOS_SET_VALUE(67), Length 1, Class MandatoryMar 4 20:09:29.232: AGW-SR: Value <0>Mar 4 20:09:29.232: AGW-SR: Type UGW_FLOW_SF_VALID_CFG(68), Length 1, Class MandatoryMar 4 20:09:29.232: AGW-SR: Value <1>Mar 4 20:09:29.232: AGW-SR: Type UGW_FLOW_SF_QOS_INFO_PRESENT(69), Length 1, Class MandatoryMar 4 20:09:29.232: AGW-SR: Value <1>Mar 4 20:09:29.232: AGW-SR: Type UGW_FLOW_SF_CLASSIFIER_PRESENT(70), Length 1, Class MandatoryMar 4 20:09:29.232: AGW-SR: Value <1>Mar 4 20:09:29.232: AGW-SR: Type UGW_FLOW_SF_QOS_SET_VALUE_PRESENT(71), Length 1, Class MandatoryMar 4 20:09:29.232: AGW-SR: Value <0>Mar 4 20:09:29.232: AGW-SR: Type UGW_FLOW_SF_ID(52), Length 4, Class MandatoryMar 4 20:09:29.232: AGW-SR: Value <15>Mar 4 20:09:29.232: AGW-SR: Type UGW_FLOW_SF_QOS_DATA_DELIVERY_SERVICE(53), Length 1, Class MandatoryMar 4 20:09:29.232: AGW-SR: Value <2>Mar 4 20:09:29.232: AGW-SR: Type UGW_FLOW_SF_QOS_MAX_LATENCY(54), Length 4, Class MandatoryMar 4 20:09:29.232: AGW-SR: Value <1>Mar 4 20:09:29.232: AGW-SR: Type UGW_FLOW_SF_QOS_MAX_TRAFFIC_BURST(55), Length 4, Class MandatoryMar 4 20:09:29.232: AGW-SR: Value <2>Mar 4 20:09:29.232: AGW-SR: Type UGW_FLOW_SF_QOS_MAX_TRAFFIC_RATE_SUSTAINED(56), Length 4, Class MandatoryMar 4 20:09:29.232: AGW-SR: Value <3>Mar 4 20:09:29.232: AGW-SR: Type UGW_FLOW_SF_QOS_MIN_TRAFFIC_RATE_RESERVED(57), Length 4, Class MandatoryMar 4 20:09:29.232: AGW-SR: Value <4>Mar 4 20:09:29.232: AGW-SR: Type UGW_FLOW_SF_QOS_POLICY_TRANSMISSION_REQUEST(58), Length 4, Class MandatoryMar 4 20:09:29.232: AGW-SR: Value <5>Mar 4 20:09:29.232: AGW-SR: Type UGW_FLOW_SF_QOS_SDU_SIZE(59), Length 1, Class MandatoryMar 4 20:09:29.232: AGW-SR: Value <49>Mar 4 20:09:29.232: AGW-SR: Type UGW_FLOW_SF_QOS_TOLERATED_JITTER(60), Length 4, Class MandatoryMar 4 20:09:29.232: AGW-SR: Value <0>Mar 4 20:09:29.232: AGW-SR: Type UGW_FLOW_SF_QOS_TRAFFIC_PRIORITY(61), Length 1, Class MandatoryMar 4 20:09:29.232: AGW-SR: Value <1>Mar 4 20:09:29.232: AGW-SR: Type UGW_FLOW_SF_QOS_UNSOLICITED_INTERVAL_GRANT(62), Length 4, Class MandatoryMar 4 20:09:29.232: AGW-SR: Value <0>Mar 4 20:09:29.232: AGW-SR: Type UGW_FLOW_SF_QOS_UNSOLICITED_INTERVAL_POLLING(63), Length 4, Class MandatoryMar 4 20:09:29.232: AGW-SR: Value <9>Mar 4 20:09:29.232: AGW-SR: Type UGW_FLOW_SF_QOS_REDUCED_RESOURCES_CODE(64), Length 4, Class MandatoryMar 4 20:09:29.232: AGW-SR: Value <0>Mar 4 20:09:29.232: AGW-SR: Type UGW_FLOW_SF_QOS_MEDIA_FLOW_TYPE(65), Length 0, Class MandatoryMar 4 20:09:29.232: AGW-SR: Value <>Mar 4 20:09:29.232: AGW-SR: Type UGW_FLOW_SF_QOS_SET_TYPE(66), Length 1, Class MandatoryMar 4 20:09:29.232: AGW-SR: Value <0>Mar 4 20:09:29.232: AGW-SR: Type UGW_FLOW_SF_QOS_SET_VALUE(67), Length 1, Class MandatoryMar 4 20:09:29.232: AGW-SR: Value <0>Mar 4 20:09:29.232: AGW-SR: Type UGW_FLOW_SF_VALID_CFG(68), Length 1, Class MandatoryMar 4 20:09:29.232: AGW-SR: Value <1>Mar 4 20:09:29.232: AGW-SR: Type UGW_FLOW_SF_QOS_INFO_PRESENT(69), Length 1, Class MandatoryMar 4 20:09:29.232: AGW-SR: Value <1>Mar 4 20:09:29.232: AGW-SR: Type UGW_FLOW_SF_CLASSIFIER_PRESENT(70), Length 1, Class MandatoryMar 4 20:09:29.232: AGW-SR: Value <1>Mar 4 20:09:29.232: AGW-SR: Type UGW_FLOW_SF_QOS_SET_VALUE_PRESENT(71), Length 1, Class MandatoryMar 4 20:09:29.232: AGW-SR: Value <0>Mar 4 20:09:29.232: AGW-SR: Type UGW_HOST_ALLOCATED_ADDR(8), Length 4, Class MandatoryMar 4 20:09:29.232: AGW-SR: Value <33685506>Mar 4 20:09:29.232: AGW-SR: Type UGW_HOST_TABLE_ID(9), Length 2, Class MandatoryMar 4 20:09:29.232: AGW-SR: Value <0>Mar 4 20:09:29.232: AGW-SR: Type UGW_HOST_ADDR_ALLOC_SOURCE(10), Length 4, Class MandatoryMar 4 20:09:29.232: AGW-SR: Value <5>Mar 4 20:09:29.232: AGW-SR: Type UGW_HOST_ADDR_REAL_LENGTH(11), Length 2, Class MandatoryMar 4 20:09:29.232: AGW-SR: Value <1056>Mar 4 20:09:29.232: AGW-SR: Type UGW_HOST_ALLOCATED_PREFIX_LENGTH(12), Length 1, Class MandatoryMar 4 20:09:29.232: AGW-SR: Value <32>Mar 4 20:09:29.232: AGW-SR: Type UGW_HOST_AGGREGATE_PREFIX_LENGTH(13), Length 1, Class MandatoryMar 4 20:09:29.232: AGW-SR: Value <32>Mar 4 20:09:29.232: AGW-SR: Type UGW_HOST_ADDR_ORG_TYPE(14), Length 1, Class MandatoryMar 4 20:09:29.232: AGW-SR: Value <1>Mar 4 20:09:29.232: AGW-SR: Type UGW_HOST_ADDR_TYPE_NUM(15), Length 1, Class MandatoryMar 4 20:09:29.232: AGW-SR: Value <33>Mar 4 20:09:29.232: AGW-SR: Type UGW_HOST_ADDR_STATIC_ROUTE_ADDED(22), Length 1, Class MandatoryMar 4 20:09:29.232: AGW-SR: Value <1>Mar 4 20:09:29.232: AGW-SR: Type UGW_HOST_ADDR_TYPE_STATIC_ALLOCATED(23), Length 1, Class MandatoryMar 4 20:09:29.232: AGW-SR: Value <0>Mar 4 20:09:29.232: AGW-SR: Type UGW_HOST_ADDR_DYNAMIC_ADDR_ALLOCATED(24), Length 1, Class MandatoryMar 4 20:09:29.232: AGW-SR: Value <1>Mar 4 20:09:29.232: AGW-SR: Type UGW_HOST_ADDR_DYNAMIC_ADDR_REQUEST(25), Length 1, Class MandatoryMar 4 20:09:29.232: AGW-SR: Value <0>Mar 4 20:09:29.232: AGW-SR: Type UGW_HOST_IP_KEY(26), Length 8, Class MandatoryMar 4 20:09:29.232: AGW-SR: Value <0202000200000000>Mar 4 20:09:29.232: AGW-SR: Type UGW_HOST_DHCP_SERVER_ADDR(16), Length 4, Class OptionalMar 4 20:09:29.232: AGW-SR: Value <0>Mar 4 20:09:29.232: AGW-SR: Type UGW_HOST_DHCP_SERVER_XID(17), Length 4, Class OptionalMar 4 20:09:29.232: AGW-SR: Value <5141>Mar 4 20:09:29.232: AGW-SR: Type UGW_HOST_DHCP_HARDWARE_ADDRESS_TYPE(18), Length 1, Class OptionalMar 4 20:09:29.232: AGW-SR: Value <1>Mar 4 20:09:29.232: AGW-SR: Type UGW_HOST_DHCP_HARDWARE_ADDRESS_LEN(19), Length 1, Class OptionalMar 4 20:09:29.232: AGW-SR: Value <6>Mar 4 20:09:29.232: AGW-SR: Type UGW_HOST_DHCP_CLIENT_HARDWARE_ADDRESS(20), Length 16, Class OptionalMar 4 20:09:29.232: AGW-SR: Value <06761112111100000000000000000000>Mar 4 20:09:29.232: AGW-SR: Type UGW_HOST_DHCP_CLIENT_ADDR_LEASE_TIME(21), Length 4, Class OptionalMar 4 20:09:29.232: AGW-SR: Value <3540>Mar 4 20:09:29.232: AGW-SR: <067611121111><F[8]>Subscriber 2.2.0.2 synced from activedebug wimax agw slb
To display BWG server-load-balancing(SLB) information, use the debug wimax agw slb command in Privileged EXEC mode.
debug wimax agw slb [events | errors | packets]
Syntax Description
events
Displays information on SLB related events.
errors
Displays information on SLB related errors.
packets
Displays information on SLB related message dumps in binary.
Command Default
There are no default values.
Command Modes
Privileged EXEC.
Command History
Examples
The following example displays BWG SLB information:
router#debug wimax agw slb events
debug wimax agw switching
To display BWG switching information, use the debug wimax agw switching command in Privileged EXEC mode.
debug wimax agw switching [errors | events | arp events | arp errors | arp packet [brief | detail]| gre events | gre errors | gre packet [brief | detail] | udp [events | errors] | udp packet [brief | detail] | dhcp [errors | events] | pmip [errors | events | fsm [errors | events] | packet [detail | brief] ] | pppoe [errors | events] ]
Syntax Description
Defaults
There are no default values.
Command Modes
Privileged EXEC.
Command History
12.4(15)XL
This command was introduced.
12.4(24)YG
The pmip and pppoe keywords and options were added.
Examples
The following example displays various BWG switching information:
router#debug wimax agw switchingWiMAX AGW switching events debugging is onWiMAX AGW switching errors debugging is onWiMAX AGW switching UDP events debugging is onWiMAX AGW switching UDP errors debugging is onWiMAX AGW switching UDP packets debugging is onWiMAX AGW switching UDP packet detail dump debugging is onWiMAX AGW switching GRE events debugging is onWiMAX AGW switching GRE errors debugging is onWiMAX AGW switching GRE packets debugging is onWiMAX AGW switching GRE packet detail dump debugging is onWiMAX AGW switching DHCP events debugging is onWiMAX AGW switching DHCP errors debugging is onWiMAX AGW switching DHCP packets debugging is onWiMAX AGW switching DHCP packet detail dump debugging is onThe following sample output illustrates an MS Open:
*Aug 30 22:52:44.012: AGW-UDP: <100022270001><(SU)-10.1.1.70>PROCESS Downstream Session Signal:Sending UDP 54 bytes pak*Aug 30 22:52:44.012: AGW-UDP: <100022270001><(SU)-10.1.1.70>PROCESS Downstream Session Signal:Sending UDP 81 bytes pak*Aug 30 22:52:44.012: AGW-UDP: <100022270001><(SU)-10.1.1.70>PROCESS Downstream Flow Signal:Sending UDP 252 bytes pak*Aug 30 22:52:44.016: AGW-UDP: <100022270001><(SU)-10.1.1.70>PROCESS Downstream Flow Signal:Sending UDP 28 bytes pak*Aug 30 22:52:44.016: AGW-GRE: <100022270001><(DG)-10.1.1.70><F[5]>CEF Upstream Et0/0:Rcvd GRE 646 bytes with flags crKss, version 0x0, procotol 0x800*Aug 30 22:52:44.016: AGW-GRE: <100022270001><(DG)-10.1.1.70><F[5]>CEF Upstream Vi2:Rcvd 604(646) byte pak, TOS 0X0*Aug 30 22:52:44.016: AGW-GRE: <100022270001><(DG)-10.1.1.70><F[5]>PROCESS Upstream Et0/0:Rcvd GRE 646 bytes with flags crKss, version 0x0, procotol 0x800*Aug 30 22:52:44.016: AGW-GRE: <100022270001><(DG)-10.1.1.70><F[5]>PROCESS Upstream Et0/0 Inner pak 646 bytes pak(retval 0x0, is_ours 1)contiguous pak, size 646AA BB CC 03 34 00 AA BB CC 03 35 00 08 00 45 0002 78 00 11 00 00 FD 2F AB FB 0A 01 01 46 02 0202 02 20 00 08 00 00 00 00 05 45 00 02 5C 00 4B00 00 FE 11 B0 3C 05 05 05 05 FF FF FF FF 00 4400 43 02 48 32 06 01 01 ...*Aug 30 22:52:44.016: AGW-DHCP: <100022270001>PROCESS Upstream DHCP from MS:IP Src=5.5.5.5, IP Dst=255.255.255.255, gi=0.0.0.0, len=584, sfid=ox9*Aug 30 22:52:44.016: AGW-DHCP: <100022270001>PROCESS Upstream Decode DHCP DISCOVER:len=576, ci=0.0.0.0, gi=0.0.0.0, si=0.0.0.0, yi=0.0.0.0, sfid=0x9(9)*Aug 30 22:52:44.016: AGW-DHCP: <100022270001>PROCESS Upstream Options for DHCP DISCOVER : 53(1),57(2),61(7),12(13),55(5),255(0),*Aug 30 22:52:44.016: AGW-DHCP: <100022270001>PROCESS Upstream Added Option 82 Subscriber ID: 1000.2227.0001, Circuit ID: 9*Aug 30 22:52:44.016: AGW-GRE: <100022270001><(DG)-10.1.1.70><F[5]>PROCESS Upstream Vi2:Rcvd 620(662) bytes pak, TOS 0X0*Aug 30 22:52:44.016: AGW-GRE: <100022270001><(DG)-10.1.1.70><F[5]>PROCESS Upstream GRE pak Rcvd 620(662) bytes pakcontiguous pak, size 62045 00 02 6C 00 4B 00 00 FE 11 A9 D4 02 02 02 020B 01 01 5D 00 44 00 43 02 58 9C 40 01 01 06 0000 00 08 33 00 00 80 00 00 00 00 00 00 00 00 0000 00 00 00 02 02 02 02 10 00 22 27 00 01 00 0000 00 00 00 00 00 00 00 ...bwg#*Aug 30 22:52:44.600: %RADIUS-4-RADIUS_DEAD: RADIUS server 1.8.91.8:1645,1646 is not responding.*Aug 30 22:52:44.600: %RADIUS-4-RADIUS_ALIVE: RADIUS server 1.8.91.8:1645,1646 is being marked alive.BWG#*Aug 30 22:52:46.032: AGW-DHCP: <100022270001>PROCESS Downstream DHCP to MS:IP Src=2.2.2.2, IP Dst=2.2.2.2, len=308*Aug 30 22:52:46.032: AGW-DHCP: <100022270001>PROCESS Downstream Decode DHCP OFFER:len=300, ci=0.0.0.0, gi=2.2.2.2, si=0.0.0.0, yi=2.2.0.89, sfid=0x9(9)*Aug 30 22:52:46.032: AGW-DHCP: <100022270001>PROCESS Downstream Options for DHCP OFFER : 53(1),54(4),51(4),58(4),59(4),1(4),82(14),255(0),*Aug 30 22:52:46.032: AGW-GRE: <100022270001><(DG)-10.1.1.70><F[5]>PROCESS Downstream Received 328 bytes pakcontiguous pak, size 32845 00 01 48 00 0A 00 00 FF 11 BA 9B 00 00 00 00FF FF FF FF 00 43 00 44 01 34 9D 5D 02 01 06 0000 00 08 33 00 00 80 00 00 00 00 00 02 02 00 5900 00 00 00 00 00 00 00 10 00 22 27 00 01 00 0000 00 00 00 00 00 00 00 ...*Aug 30 22:52:46.032: AGW-GRE: <100022270001><(DG)-10.1.1.70><F[5]>PROCESS Downstream Vi2:Sending 356(328) bytes pak, TOS 0X0*Aug 30 22:52:46.032: AGW-GRE: <100022270001><(DG)-10.1.1.70><F[5]>PROCESS Downstream Vi2:GRE packet of 356 bytescontiguous pak, size 35645 00 01 64 00 0D 00 00 FF 2F AB 13 02 02 02 020A 01 01 46 20 00 08 00 00 00 00 05 45 00 01 4800 0A 00 00 FF 11 BA 9B 00 00 00 00 FF FF FF FF00 43 00 44 01 34 9D 5D 02 01 06 00 00 00 08 3300 00 80 00 00 00 00 00 ...*Aug 30 22:52:46.040: AGW-GRE: <100022270001><(DG)-10.1.1.70><F[5]>CEF Upstream Et0/0:Rcvd GRE 646 bytes with flags crKss, version 0x0, procotol 0x800*Aug 30 22:52:46.040: AGW-GRE: <100022270001><(DG)-10.1.1.70><F[5]>CEF Upstream Vi2:Rcvd 604(646) byte pak, TOS 0X0*Aug 30 22:52:46.040: AGW-GRE: <100022270001><(DG)-10.1.1.70><F[5]>PROCESS Upstream Et0/0:Rcvd GRE 646 bytes with flags crKss, version 0x0, procotol 0x800*Aug 30 22:52:46.040: AGW-GRE: <100022270001><(DG)-10.1.1.70><F[5]>PROCESS Upstream Et0/0 Inner pak 646 bytes pak(retval 0x0, is_ours 1)contiguous pak, size 646AA BB CC 03 34 00 AA BB CC 03 35 00 08 00 45 0002 78 00 12 00 00 FD 2F AB FA 0A 01 01 46 02 0202 02 20 00 08 00 00 00 00 05 45 00 02 5C 00 4D00 00 FE 11 B0 3A 05 05 05 05 FF FF FF FF 00 4400 43 02 48 3D 19 01 01 ...*Aug 30 22:52:46.040: AGW-DHCP: <100022270001>PROCESS Upstream DHCP from MS:IP Src=5.5.5.5, IP Dst=255.255.255.255, gi=0.0.0.0, len=584, sfid=ox9*Aug 30 22:52:46.040: AGW-DHCP: <100022270001>PROCESS Upstream Decode DHCP REQUEST:len=576, ci=0.0.0.0, gi=0.0.0.0, si=0.0.0.0, yi=0.0.0.0, sfid=0x9(9)*Aug 30 22:52:46.040: AGW-DHCP: <100022270001>PROCESS Upstream Options for DHCP REQUEST : 53(1),57(2),61(7),54(4),50(4),51(4),12(13),55(5),255(0),*Aug 30 22:52:46.040: AGW-DHCP: <100022270001>PROCESS Upstream Added Option 82 Subscriber ID: 1000.2227.0001, Circuit ID: 9*Aug 30 22:52:46.040: AGW-GRE: <100022270001><(DG)-10.1.1.70><F[5]>PROCESS Upstream Vi2:Rcvd 620(662) bytes pak, TOS 0X0*Aug 30 22:52:46.040: AGW-GRE: <100022270001><(DG)-10.1.1.70><F[5]>PROCESS Upstream GRE pak Rcvd 620(662) bytes pakcontiguous pak, size 62045 00 02 6C 00 4D 00 00 FE 11 A9 D2 02 02 02 020B 01 01 5D 00 44 00 43 02 58 9E F9 01 01 06 0000 00 08 33 00 00 80 00 00 00 00 00 00 00 00 0000 00 00 00 02 02 02 02 10 00 22 27 00 01 00 0000 00 00 00 00 00 00 00 ...*Aug 30 22:52:46.044: AGW-DHCP: <100022270001>PROCESS Downstream DHCP to MS:IP Src=2.2.2.2, IP Dst=2.2.2.2, len=313*Aug 30 22:52:46.044: AGW-DHCP: <100022270001>PROCESS Downstream Decode DHCP ACK:len=305, ci=0.0.0.0, gi=2.2.2.2, si=0.0.0.0, yi=2.2.0.89, sfid=0x9(9)*Aug 30 22:52:46.044: AGW-DHCP: <100022270001>PROCESS Downstream Options for DHCP ACK : 53(1),54(4),51(4),58(4),59(4),12(13),1(4),82(14),255(0),*Aug 30 22:52:46.044: AGW-GRE: <100022270001><(DG)-10.1.1.70><F[5]>PROCESS Downstream Received 333 bytes pakcontiguous pak, size 33345 00 01 4D 00 0B 00 00 FF 11 BA 95 00 00 00 00FF FF FF FF 00 43 00 44 01 39 13 30 02 01 06 0000 00 08 33 00 00 80 00 00 00 00 00 02 02 00 5900 00 00 00 00 00 00 00 10 00 22 27 00 01 00 0000 00 00 00 00 00 00 00 ...*Aug 30 22:52:46.044: AGW-GRE: <100022270001><(DG)-10.1.1.70><F[5]>PROCESS Downstream Vi3:Sending 361(333) bytes pak, TOS 0X0*Aug 30 22:52:46.044: AGW-GRE: <100022270001><(DG)-10.1.1.70><F[5]>PROCESS Downstream Vi3:GRE packet of 361 bytesBWG#contiguous pak, size 36145 00 01 69 00 0E 00 00 FF 2F AB 0D 02 02 02 020A 01 01 46 20 00 08 00 00 00 00 05 45 00 01 4D00 0B 00 00 FF 11 BA 95 00 00 00 00 FF FF FF FF00 43 00 44 01 39 13 30 02 01 06 00 00 00 08 3300 00 80 00 00 00 00 00 ...*Aug 30 22:52:46.044: AGW-UDP: <100022270001><(SU)-10.1.1.70>PROCESS Downstream Flow Signal:Sending UDP 274 bytes pak*Aug 30 22:52:46.048: AGW-UDP: <100022270001><(SU)-10.1.1.70>PROCESS Downstream Flow Signal:Sending UDP 28 bytes pakHere is an example of ARP related debug information:
Router# debug wimax agw switching arp*Feb*Apr 30 20:14:40.031: AGW-ARP: <00322346ABCD>PROCESS Upstream ARP from MS:IP Src=2.2.0.145, IP Dst=2.2.2.2, MAC Src=0032.2346.abce, MAC Dst=ffff.ffff.ffff, sfid=0x1*Apr 30 20:14:40.031: AGW-ARP: <00322346ABCD>PROCESS Upstream Decode ARP REQUEST:IP Src=2.2.0.145, IP Dst=2.2.2.2, MAC Src=0032.2346.abce, MAC Dst=ffff.ffff.ffff,*Apr 30 20:14:40.031: AGW-ARP: <00322346ABCD>PROCESS Downstream Decode ARP REPLY:IP Src=2.2.2.2, IP Dst=2.2.0.145, MAC Src=0000.0c07.ac01, MAC Dst=0032.2346.abce,*Apr 30 20:14:40.031: AGW-ARP: <00322346ABCD><(DG)-10.1.1.70><F[1]>PROCESS Downstream Vi2:Sending 82(28) bytes pak, TOS 0X0*Apr 30 20:14:40.031: AGW-ARP: <00322346ABCD><(DG)-10.1.1.70><F[1]>PROCESS Downstream Vi2:GRE packet of 82 bytescontiguous pak, size 8245 00 00 52 03 72 00 00 FF 2F A8 C0 02 02 02 020A 01 01 46 20 00 65 58 00 00 00 01 00 32 23 46AB CE 00 00 0C 07 AC 01 81 00 00 03 00 1C AA AA03 00 00 00 08 06 00 01 08 00 06 04 00 02 00 000C 07 AC 01 02 02 02 02 ...Example of ARP Debugs for Static Host reject when host limit reached and idle timer not expired:
Router# debug wimax agw switching arp*Nov 28 05:12:56.909: AGW-ARP: <100022ED1111>PROCESS Upstream ARP from MS:IPSrc=11.1.3.220, IP Dst=11.1.3.3, MAC Src=1000.22ed.111a, MAC Dst=ffff.ffff.ffff,sfid=0x1F*Nov 28 05:12:56.909: AGW-ARP: <100022ED1111>PROCESS Upstream Decode ARP REQUEST:IPSrc=11.1.3.220, IP Dst=11.1.3.3, MAC Src=1000.22ed.111a, MAC Dst=ffff.ffff.ffff, *Nov 28 05:12:56.909: AGW-ARP: <100022ED1111>PROCESS Upstream ARP from MS:IPSrc=11.1.3.3, IP Dst=11.1.3.220, sfid=0x1F, host create failed.Example of ARP Debugs for Static Host accept when host limit reached but idle timer expired
Router# debug wimax agw switching arp*Apr 30 20:21:17.767: AGW-ARP: <00322346ABCD>PROCESS Upstream ARP from MS:IP*Apr 30 21:25:01.903: AGW-ARP: <00322346ABCD>PROCESS Upstream ARP from MS:IP Src=2.2.0.153, IP Dst=2.2.2.2, MAC Src=0032.2346.abd6, MAC Dst=ffff.ffff.ffff, sfid=0x3*Apr 30 21:25:01.903: AGW-ARP: <00322346ABCD>PROCESS Upstream Decode ARP REQUEST:IP Src=2.2.0.153, IP Dst=2.2.2.2, MAC Src=0032.2346.abd6, MAC Dst=ffff.ffff.ffff,*Apr 30 21:25:01.903: AGW-ARP: <00322346ABCD>PROCESS Downstream Decode ARP REPLY:IP Src=2.2.2.2, IP Dst=2.2.0.153, MAC Src=0000.0c07.ac01, MAC Dst=0032.2346.abd6,*Apr 30 21:25:01.903: AGW-ARP: <00322346ABCD><(DG)-10.1.1.70><F[2]>PROCESS Downstream Vi2:Sending 82(28) bytes pak, TOS 0X0*Apr 30 21:25:01.903: AGW-ARP: <00322346ABCD><(DG)-10.1.1.70><F[2]>PROCESSDownstream Vi2:GRE packet of 82 bytescontiguous pak, size 8245 00 00 52 01 5D 00 00 FF 2F AA D5 02 02 02 020A 01 01 46 20 00 65 58 00 00 00 01 00 32 23 46AB D6 00 00 0C 07 AC 01 81 00 00 03 00 1C AA AA03 00 00 00 08 06 00 01 08 00 06 04 00 02 00 000C 07 AC 01 02 02 02 02 ...Example of ARP Debugs when Receiving an Invalid ARP Request:
Router# debug wimax agw switching arp*Nov 28 05:14:49.205: AGW-ARP: <100022ED1111>PROCESS Upstream ARP from MS:IPSrc=11.1.3.220, IP Dst=255.255.255.255, MAC Src=1000.22ed.111a, MAC Dst=ffff.ffff.ffff,sfid=0x1F*Nov 28 05:14:49.205: AGW-ARP: <100022ED1111>PROCESS Upstream Decode ARP REQUEST:IPSrc=11.1.3.220, IP Dst=255.255.255.255, MAC Src=1000.22ed.111a, MAC Dst=ffff.ffff.ffff, *Nov 28 05:14:49.205: AGW-ARP: <100022ED1111>PROCESS Upstream IP Src=11.1.3.220, IPDst=255.255.255.255, Received Invalid ARP request. BWG does not send reply pu-asn# *Nov 28 05:14:49.205: AGW-ARP: <100022ED1111>PROCESS Upstream ARP from MS:IPSrc=11.1.3.220, IP Dst=255.255.255.255, MAC Src=1000.22ed.111a, MAC Dst=ffff.ffff.ffff,sfid=0x1F, decode failedExample of ARP Debugs when Receiving a Gratuitous ARP:
Router# debug wimax agw switching arp*Nov 28 05:18:45.829: AGW-ARP: <100022ED1111>PROCESS Upstream ARP from MS:IPSrc=11.1.3.220, IP Dst=11.1.3.220, MAC Src=1000.22ed.111a, MAC Dst=ffff.ffff.ffff,sfid=0x1F*Nov 28 05:18:45.829: AGW-ARP: <100022ED1111>PROCESS Upstream Decode ARP REQUEST:IPSrc=11.1.3.220, IP Dst=11.1.3.220, MAC Src=1000.22ed.111a, MAC Dst=ffff.ffff.ffff, *Nov 28 05:18:45.829: AGW-ARP: <100022ED1111>PROCESS Upstream IP Src=11.1.3.220, IPDst=11.1.3.220, Received Gratuitous ARP Request. BWG does not send reply *Nov 28 05:18:45.829: AGW-ARP: <100022ED1111>PROCESS Upstream ARP from MS:IPSrc=11.1.3.220, IP Dst=11.1.3.220, MAC Src=1000.22ed.111a, MAC Dst=ffff.ffff.ffff,sfid=0x1F, decode faileddebug wimax agw vtemplate
To display BWG vtemplate information, use the debug wimax agw vtemplate command in Privileged EXEC mode. Use the no version of the command to turn off debugging.
debug wimax agw vtemplate [events | errors]
no debug wimax agw vtemplate
Syntax Description
events
Displays information on Virtual-template related events.
errors
Displays information on Virtual-template related errors.
Defaults
There are no default values.
Command Modes
Privileged EXEC.
Command History
Examples
The following example displays BWG vtemplate information:
router#debug wimax agw vtemplate eventsdefault-gateway
To configure the default-gateway under the PMIP profile configuration, use the default-gateway command. Use the no form of this command to disable this function.
default-gateway ip-address
[no] default-gateway ip-address
Syntax Description
Defaults
There are no default values.
Command Modes
Privileged EXEC configuration (config).
Command History
Examples
The following example shows how to configure the default-gateway under a PMIP profile configuration:
wimax agw pmip profile pmip1proxy-mndns-server primary 10.1.1.1 secondary 10.1.1.2default-gateway 10.1.1.3dhcp gateway address
To specify the IP address of the DHCP relay which the server is supposed to communicate with in the BWG, use the dhcp gateway address command in user group configuration mode. Use the no form of the command to revert to the default gateway IP address.
dhcp gateway address gateway-address
no dhcp gateway address gateway-address
Syntax Description
Defaults
By default the BWG VT primary IP address is used.
Command Modes
User group configuration mode.
Command History
Usage Guidelines
The IP address specified as the gateway address must be the IP address of the BWG Virtual-Template (either primary or one of the secondary IP addresses).
Examples
The following example illustrates how to configure DHCP relay using the dhcp gateway address command:
Router(config-gw-ug)# dhcp gateway address gateway-addressRelated Commands
dhcp server primary
Specifies the external DHCP server used for DHCP IP address allocation.
dhcp release relay-only
To enable the BWG to only handle relayed DHCP RELEASEs from DHCP clients (the BWG will no longer generate a DHCP RELEASE on behalf of subscriber's hosts), use the dhcp release relay-only command in User group configuration sub mode. Use the no form of the command to disable this feature.
dhcp release relay-only
no dhcp release relay-only
Syntax Description
There are no keywords or arguments for this command.
Defaults
The default setting is that this command is disabled.
Command Modes
User group configuration sub mode.
Command History
Examples
The following example enables the command:
router(config-gw-ugl)# dhcp release relay-only
dhcp server primary
To specify the external DHCP servers for IP address allocation, use the dhcp server primary command in user group configuration mode. Use the no form of the command to remove the DHCP server configuration.
dhcp server primary primary-address [backup backup-address] [vrf]
no dhcp server primary primary-address [backup backup-address] [vrf]
Syntax Description
primary-address
Specifies the IP address of the primary DHCP server
backup backup-address
Specifies the IP address of the backup DHCP server.
vrf
Indicates if the address is in the VRF scope.
Defaults
There are no default values.
Command Modes
User group configuration mode.
Command History
Usage Guidelines
The IP address specified as the gateway address must be the IP address of the BWG Virtual-Template (either primary, or one of the secondary IP addresses).
Examples
The following example illustrates how to configure DHCP servers using dhcp server primary command:
router(config-gw-ug)# dhcp server primary 10.10.10.10 backup 10.10.10.11
direction
To specify the direction of the service-flow the configuration is done, and to enter a subcommand mode use the direction command in service flow configuration subcommand mode. Use the no version of this command to remove the corresponding configuration from the direction specified.
direction {uplink | downlink}
Syntax Description
uplink
Service Flow Uplink direction configuration commands.
downlink
Service Flow Downlink direction configuration commands.
Defaults
There are no default values.
Command Modes
Service flow configuration subcommand mode.
Command History
Examples
The following example specifies the service flow direction to the uplink:
router(config-gw-sf)#direction uplinkdns-server
To configure the DNS server under a PMIP profile configuration use the dns-server command. Use the no form of this command to disable this function.
dns-server primary ip-address secondary ip-address
no dns-server primary ip-address secondary ip-address
Syntax Description
Defaults
There are no default values.
Command Modes
Privileged EXEC configuration (config)
Command History
Examples
The following example shows how to configure the primary and secondary dns-servers under a PMIP profile configuration:
wimax agw pmip profile pmip1proxy-mndns-server primary 10.1.1.1 secondary 10.1.1.2encapsulation agw
To clone a Virtual-Access interface of encapsulation type BWG, use the encapsulation agw command in Virtual-Template configuration mode.
encapsulation agw
Syntax Description
This command has no arguments or keywords.
Defaults
There are no default values.
Command Modes
Interface configuration.
Command History
Examples
The following example enables you to clone a Virtual-Access interface of encapsulation type BWG:
router(config)# interface Virtual-Template1ipaddress 2.2.2.2 255.255.0.0router(config-if)# encapsulation agwip mtu 1440no keepaliveThe Gi address is picked from the Virtual Address by default. It can be overridden by the User-Group Configuration.
host-overflow
To enable the DHCP Host Caching feature and configure the size of the cache list and the idle timer, use the host-overflow command in user group configuration submode. Use the no form of the command to disable this feature.
host-overflow [size 1-100] [min-idle 1- 60]
no host-overflow [size 1-100] [min-idle 1- 60]
Syntax Description
Defaults
The size default value is 50. The min-idle timer value default value is 5 minutes.
Command Modes
User group configuration sub mode.
Command History
Usage Guidelines
•
•
•
The memory requirement is higher per session in cases where hot spot CPE usage is higher in the network.
Examples
The following example enables the default values:
router(usr-grp)#host-overflow size 50 min-idle 5ip-addr
To specify the base stations that are allowed to connect to the BWG, and the base station group they belong to, use the ip-addr command in base-station group configuration sub mode. Use the no form of the command to revert to the default behavior.
ip-addr start-ip-addr end-ip-addr
no ip-addr
Syntax Description
Defaults
By default, all IP addresses are allowed for the base-station group.
Command Modes
Base-station group configuration sub mode.
Command History
Examples
Here is an example of the ip-addr command:
router(config-wimax-agw-bs)# ip-addr 11.1.27.1 11.1.27.255ip access-group
To specify IPv4 access permissions between a subscriber and an external host through the BWG at a particular access point, use the ip access-group command in user group configuration mode. Use the no form of the command to disable the input access list.
access-group access-group-number {in | out | passthru}
Syntax Description
Defaults
There are no default values.
Command Modes
User group configuration mode.
Command History
Examples
The following example enables access group number 4:
router# ip access-group 4 inip redirect traffic
To enable the BWG to redirect all upstream traffic to the configured next hop address, use the ip redirect traffic command in wimax gateway user-group submode. Use the no form of the command to disable this feature.
ip redirect traffic all address
no ip redirect traffic
Syntax Description
Defaults
There are no default values.
Command Modes
Gateway user group configuration submode.
Command History
Examples
Here is an example of the ip redirect traffic command:
Router(config)#wimax agw user group-list wimaxRouter(config-gw-ugl)# user-group domain cisco.comRouter(config-gw-ug)#ip redirect ?traffic User group IP redirect traffic configuration commandsRouter(config-gw-ug)#ip redirect traffic ?all Redirect all trafficRouter(config-gw-ug)#ip redirect traffic all ?A.B.C.D Redirect IP addressRouter(config-gw-ug)#ip redirect traffic all 10.1.1.5Router(config-gw-ug)#endwimax agw user group-list wimaxuser-group domain cisco.comsla profile-name silverip redirect traffic all 10.1.1.5ip static-allowedip route aggregate
To aggregate routes automatically based on the mask returned by servers if set to auto, use the ip route aggregate command in global configuration mode. Use the no form of the command to disable route aggregation.
ip route aggregate {A.B.C.D | auto}
no ip route aggregate {A.B.C.D | auto}
Syntax Description
Defaults
There is no default value.
Command Modes
Global configuration mode.
Command History
Usage Guidelines
The following example configures an auto aggregated route:
router(config)# wimax agw user group-list wimaxuser-group anyaaa accounting method-list agwsla profile-name golddhcp server primary 12.1.1.2!user-group domain cisco.comaaa accounting method-list agwsla profile-name goldip static-allowedip route aggregate autoip static-allowed
To allow the creation of static hosts for sessions that are part of a specific user-group, use the ip static-allowed command in usergroup configuration mode. Use the no form of the command to disable this feature.
ip static-allowed
no ip static-allowed
Syntax Description
There are no keywords or arguments.
Defaults
The default value is no ip static hosts are allowed.
Command Modes
User group configuration mode.
Command History
Usage Guidelines
The following example allows static hosts for 2 separate user groups:
user-group domain cisco.comaaa accounting method-list agwsla profile-name goldip static-allowedip route aggregate auto!user-group unauthenticatedaaa accounting method-list agwaaa authentication method-list agwsla profile-name goldip static-alloweduser auto-provisioningproxy realm cisco.com password ciscowaymaximum-latency
To configure the time period between the reception of a packet by the BS or MS on its network interface, and the delivery of the packet to the RF Interface of the peer device, use the maximum-latency subcommand in service flow qos info configuration submode. Use the no form of the command to disable this feature.
maximum-latency maximum-latency-value
Syntax Description
Defaults
Default value is 0.
Command Modes
Global configuration.
Command History
Usage Guidelines
If configured, this parameter represents a service commitment (or admission criteria) at the BS or MS and is guaranteed by the BS or MS. A BS or MS does not have to meet this service commitment for service flows that exceed their minimum reserved rate.
Examples
The following examples configure a maximum latency value of 1 and 11:
wimax agw service-flow qos-info profile isf-qos-downlinkdata-delivery-service real-time-variable-ratemaximum-latency 1maximum-traffic-burst 2maximum-traffic-rate-sustained 3media-flow-type 012041424344minimum-traffic-rate-reserved 4policy-transmission-request 5sdu-size 6tolerated-jitter 7traffic-priority 1unsolicited-interval-grant 8unsolicited-interval-polling 9wimax agw service-flow qos-info profile isf-qos-uplinkdata-delivery-service unsolicited-grantmaximum-latency 11maximum-traffic-burst 21maximum-traffic-rate-sustained 31minimum-traffic-rate-reserved 41policy-transmission-request 51sdu-size 61tolerated-jitter 71traffic-priority 3unsolicited-interval-grant 81unsolicited-interval-polling 91!wimax agw service-flow qos-info profile downlink-qos-02data-delivery-service real-time-variable-ratemedia-flow-type 05abcdmaximum-traffic-burst
To configure the maximum burst size that the service flow can accommodate, use the maximum-traffic-burst subcommand in service flow qos information configuration submode. Use the no form of the command to disable this feature.
maximum-traffic-burst maximum-traffic-burst-value
Syntax Description
maximum-traffic-burst-value
Specifies the maximum burst size of the service flow. Default values is 0.
Defaults
Default values is 0.
Command Modes
Service flow qos information configuration submode.
Command History
Usage Guidelines
Since the physical speed of ingress/egress ports, the air interface, and the backhaul are greater than the maximum-sustained-traffic-rate parameter for a service, this parameter describes the maximum continuous burst the system should accommodate for the service. This assumes the service is not currently using any of its available resources.
Examples
The following examples configure a maximum traffic burst size of 2 and 21:
wimax agw service-flow qos-info profile isf-qos-downlinkdata-delivery-service real-time-variable-ratemaximum-latency 1maximum-traffic-burst 2maximum-traffic-rate-sustained 3media-flow-type 012041424344minimum-traffic-rate-reserved 4policy-transmission-request 5sdu-size 6tolerated-jitter 7traffic-priority 1unsolicited-interval-grant 8unsolicited-interval-polling 9wimax agw service-flow qos-info profile isf-qos-uplinkdata-delivery-service unsolicited-grantmaximum-latency 11maximum-traffic-burst 21maximum-traffic-rate-sustained 31minimum-traffic-rate-reserved 41policy-transmission-request 51sdu-size 61tolerated-jitter 71traffic-priority 3unsolicited-interval-grant 81unsolicited-interval-polling 91!wimax agw service-flow qos-info profile downlink-qos-02data-delivery-service real-time-variable-ratemedia-flow-type 05abcdmaximum-traffic-rate-sustained
To define the peak information rate of the service flow, use the maximum-traffic-rate-sustained subcommand in service flow qos information configuration submode. Use the no form of the command to disable this feature.
maximum-traffic-rate-sustained maximum-traffic-rate-sustained-value
Syntax Description
Defaults
There is no default value.
Command Modes
Service flow qos information configuration subcommand.
Command History
Usage Guidelines
Explicitly, this parameter does not include MAC overhead such as MAC headers or CRCs. This parameter does not limit the instantaneous rate of the service since this is governed by the physical attributes of the ingress port. If this parameter is omitted or set to zero, then there is no explicitly mandated maximum rate. This field specifies only a boundary, not a guarantee that the rate is available.
Examples
The following example specifies different maximum-traffic-rate-sustained values:
wimax agw service-flow qos-info profile isf-qos-downlinkdata-delivery-service real-time-variable-ratemaximum-latency 1maximum-traffic-burst 2maximum-traffic-rate-sustained 3media-flow-type 012041424344minimum-traffic-rate-reserved 4policy-transmission-request 5sdu-size 6tolerated-jitter 7traffic-priority 1unsolicited-interval-grant 8unsolicited-interval-polling 9wimax agw service-flow qos-info profile isf-qos-uplinkdata-delivery-service unsolicited-grantmaximum-latency 11maximum-traffic-burst 21maximum-traffic-rate-sustained 31minimum-traffic-rate-reserved 41policy-transmission-request 51sdu-size 61tolerated-jitter 71traffic-priority 3unsolicited-interval-grant 81unsolicited-interval-polling 91!wimax agw service-flow qos-info profile downlink-qos-02data-delivery-service real-time-variable-ratemedia-flow-type 05abcdmedia-flow-type
To configure the parameter that describes the application type that is used as a hint in admission decisions (for instance, VoIP, video, PTT, gaming, etc.), use the media-flow-type subcommand in service flow qos information configuration submode. Use the no form of the command to disable this functionality.
media-flow-type media-flow-type-hex-string
no media-flow-type
Syntax Description
media-flow-type-hex- string
Specifies the application type that is used as a hint in admission decisions. Application types include VoIP, video, PTT, gaming, etc.
Defaults
There are no default values.
Command Modes
Service flow qos information configuration submode.
Command History
Examples
The following example configures two different media-flow-type values:
wimax agw service-flow qos-info profile isf-qos-downlinkdata-delivery-service real-time-variable-ratemaximum-latency 1maximum-traffic-burst 2maximum-traffic-rate-sustained 3media-flow-type 012041424344minimum-traffic-rate-reserved 4policy-transmission-request 5sdu-size 6tolerated-jitter 7traffic-priority 1unsolicited-interval-grant 8unsolicited-interval-polling 9wimax agw service-flow qos-info profile isf-qos-uplinkdata-delivery-service unsolicited-grantmaximum-latency 11maximum-traffic-burst 21maximum-traffic-rate-sustained 31minimum-traffic-rate-reserved 41policy-transmission-request 51sdu-size 61tolerated-jitter 71traffic-priority 3unsolicited-interval-grant 81unsolicited-interval-polling 91!wimax agw service-flow qos-info profile downlink-qos-02data-delivery-service real-time-variable-ratemedia-flow-type 05abcdminimum-traffic-rate-reserved
To specify the minimum rate reserved for a specific service flow use the minimum-traffic-rate- reserved subcommand in service flow qos information configuration submode. Use the no form of the command to disable this feature.
minimum-traffic-rate-reserved minimum-traffic-rate-reserved-value
no minimum-traffic-rate-reserved minimum-traffic-rate-reserved-value
Syntax Description
Defaults
There are no default values.
Command Modes
Service flow qos information configuration submode.
Command History
Usage Guidelines
The specified rate is only honored when sufficient data is available for scheduling. When sufficient data does not exist, the available data is transmitted as soon as possible.
Examples
The following example configures a minimum-traffic-rate-reserved-value of 4:
wimax agw service-flow qos-info profile isf-qos-downlinkdata-delivery-service real-time-variable-ratemaximum-latency 1maximum-traffic-burst 2maximum-traffic-rate-sustained 3media-flow-type 012041424344minimum-traffic-rate-reserved 4policy-transmission-request 5sdu-size 6tolerated-jitter 7traffic-priority 1unsolicited-interval-grant 8unsolicited-interval-polling 9pak-classify-rule
To specify which packet classification rule profile is associated under the corresponding cs-type, use the pak-classify-rule subcommand in service flow direction cs-type configuration submode. Use the no version of the command to remove the packet classification rule.
pak-classify-rule pak-classify-rule-profile-name
no pak-classify-rule pak-classify-rule-profile-name
Syntax Description
Defaults
There are no default values.
Command Modes
Service flow direction configuration submode.
Command History
Examples
The following example specifies a packet classification rule profile named "uplink2":
router(config-gw-sf-dir)#pak-classify-rule uplink2policy-transmission-request
To specify options for PDU formation, for uplink service flows, and to configure restrictions on the types of bandwidth request options that may be used, use the policy-transmission-request subcommand in service flow QoS information configuration submode. An attribute is enabled by setting the corresponding bit position to 1. Use the no form of the command to disable this functionality.
policy-transmission-request policy-transmission-request-value
no policy-transmission-request policy-transmission-request-value
Syntax Description
Defaults
There are no default values.
Command Modes
Service flow QoS information configuration submode.
Command History
Usage Guidelines
An attribute is enabled by setting the corresponding bit position to 1.
Examples
The following example illustrates how to configure the policy-transmission-request subcommand:
wimax agw service-flow qos-info profile isf-qos-downlinkdata-delivery-service real-time-variable-ratemaximum-latency 1maximum-traffic-burst 2maximum-traffic-rate-sustained 3media-flow-type 012041424344minimum-traffic-rate-reserved 4policy-transmission-request 5sdu-size 6tolerated-jitter 7traffic-priority 1unsolicited-interval-grant 8unsolicited-interval-polling 9wimax agw service-flow qos-info profile isf-qos-uplinkdata-delivery-service unsolicited-grantmaximum-latency 11maximum-traffic-burst 21maximum-traffic-rate-sustained 31minimum-traffic-rate-reserved 41policy-transmission-request 51sdu-size 61tolerated-jitter 71traffic-priority 3unsolicited-interval-grant 81unsolicited-interval-polling 91!wimax agw service-flow qos-info profile downlink-qos-02data-delivery-service real-time-variable-ratemedia-flow-type 05abcdprecedence
To specify the precedence of the cs-type under the direction which it is configured, use the precedence command in service flow direction cs-type submode. The precedence is used as a tie-breaker when an MS can support more than one cs-type. Use the no version of the command to remove the precedence information from the corresponding cs-type.
precedence 1-2
no precedence
Syntax Description
Defaults
The default value is 1.
Command Modes
Service flow direction cs-type configuration submode.
Command History
Examples
The following example specifies a packet classification rule profile named "uplink2" with different precedence set for cs-type ip-cs and cs-type ethernet-cs:
wimax agw service-flow profile isfdirection downlinkcs-type ip-cspak-classify-rule isf-classifier-downlinkprecedence 1cs-type ethernet-cspak-classify-rule isf-classifier-downlinkprecedence 2qos-info isf-qos-downlink!direction uplinkcs-type ip-cspak-classify-rule isf-classifier-uplinkprecedence 1cs-type ethernet-cspak-classify-rule isf-classifier-uplinkprecedence 2vlan 2 vrf vrf_1vlan range 3 10 vrf vrf_2vrf-default vrf_1qos-info isf-qos-uplinkpriority
To set the priority of a packet classification rule under the profile, use the priority subcommand in packet classify rule submode. Use the no form of the command to unconfigure the priority of the packet classification rule.
priority {ip | vlan | ethernet} permit {0-255 | gre | tcp | icmp | udp | ip} {src-address src-mask | any | host src-address} [range src-port-low [src-port-high] {dst-address dst-mask | any | host dst-address} [range dst-port-low [dst-port-high][tos tos-low tos-mask tos-high]
no priority
Syntax Description
Defaults
The default is to use the ISF (Initial Service Flow) to send the packet.
Command Modes
Packet classify rule configuration submode.
Command History
Usage Guidelines
The Cisco BWG currently supports IPv4, Ethernet and VLAN related rules.
Each packet classification rule should have a unique priority associated with it. Each flow can have zero or more classifier rules. The higher the priority, the higher is the rule precedence. If a packet matches a rule, the corresponding flow is chosen to send that packet.
Examples
The following example illustrates the various options under the priority command:
router(config-gw-pak-classify-rule-pr)#priority
IPv4 classifiers===>
ip permit {0-255 | gre | tcp | icmp | udp | ip} {src-address src-mask | any | host src-address} [range src-port-low [src-port-high] {dst-address dst-mask | any | host dst-address} [range dst-port-low [dst-port-high] [tos tos-low tos-mask tos-high]
Ethernet related classifiers ===>
ethernet permit {src_mac src_mac_mask | any} {dst_mac dst_mac_mask | any} {0-FFFF | any | arp | ipv4}]
VLAN related classifiers ===>
vlan permit {2-4095 | any } priority { 0-7 | any | range #start #end }Here is an example of the priority command:
wimax agw service-flow pak-classify-rule profile sec1-classifier-uplinkpriority 0ipv4 permit ip any anyethernet permit any any anyvlan any priority any!priority 1vlan 300 priority 4 7!priority 2ethernet permit 0032.00AE.0023 ffff.ffff.ffff any arp!priority 3ipv4 permit ip 2.2.2.2 255.255.255.0 192.168.102.0 /24 tos 0 255 100!priority 4ethernet permit any 0032.00AE.0023 ffff.ffff.ffff 8100vlan permit 900 priority 4!priority 5ipv4 permit ip 2.2.2.2 255.255.255.0 192.168.102.0 /24 tos 0 255 100ethernet permit 001C.B046.041B ffff.ffff.0000 0032.00AE.0023 ffff.0000.0000 ipv4vlan permit 300 priority range 4 7proxy realm
To specify how the BWG should populate the RADIUS Access Request message for users who support PPP/PAP methods of authentication, use the proxy realm sub command in unauthenticated user group mode. Use the no form of the command to disable this feature.
Note
proxy realm realm-name password password
no proxy realm realm-name password password
Syntax Description
Defaults
There are no default values.
Command Modes
User group configuration submode.
Command History
Usage Guidelines
If configured, the user name and password sent in the Access-Request (since the user is authenticated based on the PAP of PPP) will be set to mac@realm, and given a password respectively.
If the proxy realm is not configured, the user name will be mac, and cisco will be used as password in the Access-Request.
Examples
The following example illustrates how to configure the proxy realm command:
router(config)#user-group unauthenticatedaaa accounting method-list agwaaa authentication method-list agwsla profile-name goldip static-alloweduser auto-provisioningproxy realm cisco.com password ciscowayqos-info
To specify which QoS information profile is associated under the corresponding direction, use the qos-info subcommand in service flow direction configuration submode. Use the no form of the command to remove the QoS information from the corresponding direction.
qos-info qos-profile-name
no qos-info qos-profile-name
Syntax Description
Defaults
There are no default values.
Command Modes
Service flow direction configuration submode.
Command History
Examples
The following example illustrates how to configure the qos-info command:
wimax agw service-flow qos-info profile isf-qos-downlinkdata-delivery-service real-time-variable-ratemaximum-latency 1maximum-traffic-burst 2maximum-traffic-rate-sustained 3media-flow-type 012041424344minimum-traffic-rate-reserved 4policy-transmission-request 5sdu-size 6tolerated-jitter 7traffic-priority 1unsolicited-interval-grant 8unsolicited-interval-polling 9radius-server vsa send accounting wimax
To enable WiMAX RADIUS VSAs to be sent in accounting requests (Start, Int, Stop) from the BWG, use the radius-server vsa send accounting wimax command in global configuration mode. Use the no form of the command to disable this feature.
radius-server vsa send accounting wimax
no radius-server vsa send accounting wimax
Syntax Description
There are no arguments or keywords.
Defaults
This feature is disabled by default.
Command Modes
Global configuration.
Command History
Examples
The following example enables RADIUS VSAs to be sent in accounting requests from the BWG:
Router(config)#radius-server vsa send accounting wimaxradius-server vsa send authentication wimax
To enable the WiMAX RADIUS VSAs to be sent out in authentication requests (Access-Request) from the BWG, use the radius-server vsa send authentication wimax command in global configuration mode. Use the no form of the command to disable this feature.
radius-server vsa send authentication wimax
no radius-server vsa send authentication wimax
Syntax Description
There are no keywords or arguments.
Defaults
There are no default values.
Command Modes
Global configuration.
Command History
Examples
The following example enables the BWG to send RADIUS VSAs out in authentication requests:
Router(config)#radius-server vsa send authentication wimaxreduced-resources-code
To configure the code that indicates that the requesting entity will accept reduced resources if the requested resources are not available, use the reduced-resources-code subcommand in service flow QoS information configuration submode. Use the no form of the command to disable this function.
reduced-resources-code reduced-resources-code-value
no reduced-resources-code
Syntax Description
Defaults
There is no default value.
Command Modes
Service flow QoS information configuration submode.
Command History
Examples
The following example illustrates how to configure the reduced-resources-code command:
router(config-gw-sf-qos-info)#reduced-resources-code reduced-resources-code-valuereference-point r6
To configure various R6 parameters, including keepalive, base station path and response configuration commands, use the reference-point r6 subcommand in base station group configuration submode. Use the no form of the command to disable these parameters.
reference-point r6 [keepalive | path {purge-timeout value} | response | udp ip dscp value | session-maturity-period value]
no reference-point r6
Syntax Description
Defaults
The timeout value is measured in minutes. If the purge timer is not configured, the default value is 24 hours.
Command Modes
Base station group configuration submode.
Command History
12.4(15)XL
This command was introduced.
12.4(24)YG
session-maturity-period sub-option was introduced.
Examples
The following example illustrates how to configure the reference-point r6 command:
BWG(config-wimax-agw-bs)#ref r6 ?keepalive Enable AGW-BS keepalive featurepath WiMAX AGW BS R6 reference point base station pathresponse WiMAX AGW BS R6 reference point responseconfiguration commandssession-maturity-period WiMAX AGW BS R6 reference point time after sessionconsidered matureudp WiMAX AGW BS R6 reference point UDP configurationcommandsBWG(config-wimax-agw-bs)#ref r6 udp ip dscp ?<0-63> WiMAX AGW BS R6 reference point UDP IP set DSCP to value (default 48)BWG(config-wimax-agw-bs)#ref r6 session-maturity-period ?<1-30> Session maturity period value (default 5 seconds)reference-point r6 keepalive max-failures-allowed
To configure the the number of times the BWG attempts to resend the KeepAlive request before tearing down the session, use the reference-point r6 keepalive max-failures-allowed command in base station submode configuration. Use the no form of the command to disable this feature.
reference-point r6 keepalive max-failures-allowed maximum-retries
no reference-point r6 keepalive max-failures-allowed maximum-retries
Syntax Description
maximum-retries
Specifies the number of times the BWG attempts to resend the KeepAlive request before tearing down the session.
Defaults
The default setting is disabled.
Command Modes
Base station configuration submode.
Command History
Examples
The following example illustrates the default behavior for the reference-point r6 keepalive max-failures-allowed command:
wimax agw base-station group defaultreference-point r6 keepalive timeout 30reference-point r6 response retransmit 10reference-point r6 response timeout 10
reference-point r6 keepalive timeout
To specify the keepalive interval in seconds, use the reference-point r6 keepalive timeout command in base station configuration mode. Use the no form of the command to disable this command.
reference-point r6 keepalive timeout interval
no reference-point r6 keepalive timeout interval
Syntax Description
Defaults
The default setting is 60 seconds.
Command Modes
Base station configuration submode.
Command History
Examples
The following example illustrates the default behavior for the reference-point r6 response keepalive timeout command:
wimax agw base-station group defaultreference-point r6 keepalive timeout 30reference-point r6 response retransmit 10reference-point r6 response timeout 10reference-point r6 response retransmits
To specify the number of times the BWG attempts to re-send R6 messages when it does not receive a response from the BS, use the reference-point r6 response retransmits command in base station configuration submode. Use the no form of the command to disable this feature.
reference-point r6 response retransmits retransmit value
no reference-point r6 response retransmits
Syntax Description
retransmit value
Specifies the number of times the AGW attempts to resend R6 messages after no response from the BS. The default value is 5.
Defaults
The default value is 5.
Command Modes
Base station configuration submode.
Command History
Usage Guidelines
The action taken on the maximum retries being reached depends on the timer that expired.
Examples
The following example illustrates the default behavior for the reference-point r6 response retransmits command:
Router(bs-config)#reference-point r6 response retransmits 5reference-point r6 response timeout
To configure the amount of time the BWG waits for a response from the BS after a request has been sent, use the reference-point r6 response timeout command in base station configuration submode. Use the no form of the command to reset the timeout value to its default value of 5 seconds.
reference-point r6 response timeout timeout value
no reference-point r6 response timeout timeout value
Syntax Description
timeout value
Specifies the amount of time the BWG waits for a response from the BS after a request has been sent. The value is measured in seconds. The default value is 5 seconds.
Defaults
The default value is 5 seconds.
Command Modes
Base station configuration submode.
Command History
Usage Guidelines
If a response is not received within the configured interval, the BWG will retransmit the message until the maximum number of retries configured is reached.
Examples
The following example illustrates that the BWG waits for a response from the BS for 10 seconds:
router (config) #reference-point r6 response timeout 10sdu-size
To configure the parameter that represents the number of bytes in the fixed size Service Data Unit (SDU), use the sdu-size subcommand in service flow QoS information configuration submode. Use the no form of the command to disable this feature.
sdu-size sdu-size-value
no sdu-size
Syntax Description
Defaults
The sdu-size-value default value is 49 bytes.
Command Modes
Service flow QoS information configuration submode.
Command History
Examples
The following example illustrates how to configure the sdu-size command:
wimax agw service-flow qos-info profile isf-qos-downlinkdata-delivery-service real-time-variable-ratemaximum-latency 1maximum-traffic-burst 2maximum-traffic-rate-sustained 3media-flow-type 012041424344minimum-traffic-rate-reserved 4policy-transmission-request 5sdu-size 6tolerated-jitter 7traffic-priority 1unsolicited-interval-grant 8unsolicited-interval-polling 9wimax agw service-flow qos-info profile isf-qos-uplinkdata-delivery-service unsolicited-grantmaximum-latency 11maximum-traffic-burst 21maximum-traffic-rate-sustained 31minimum-traffic-rate-reserved 41policy-transmission-request 51sdu-size 61tolerated-jitter 71traffic-priority 3unsolicited-interval-grant 81unsolicited-interval-polling 91!wimax agw service-flow qos-info profile downlink-qos-02data-delivery-service real-time-variable-ratemedia-flow-type 05abcdsecurity subscriber address-filtering ingress
To enable the Ingress address filtering for the subscriber, use the security subscriber address-filtering ingress command in user group configuration mode. Use the no form of the command to disable Ingress address filtering.
security subscriber address-filtering ingress
no security subscriber address-filtering ingress
Syntax Description
There are no keywords or arguments.
Defaults
The feature is disabled.
Command Modes
User group configuration mode.
Command History
Usage Guidelines
When enabled in the upstream path, the source IP address in the packet is verified against the allowed set of addresses that are allocated to the subscriber, or Hosts behind the subscriber, or Framed route attribute (if downloaded from the AAA server). If the source IP address does not match, the packet is dropped for the subscriber.
Examples
The following example enables the security subscriber address-filtering ingress command:
Router(config-gw-ug)#security subscriber address-filtering ingressservice-flow pre-defined profile
To specify the number of pre-defined service flows to be opened for a subscriber, use the service-flow pre-defined profile command in user group configuration mode. Use the no form of the command to disable predefined service flows.
service-flow pre-defined {isf | secondary secondary-index | critical} profile sf-profile-name {cr | encap-type none [cr |vlan-id vlan-number]}
no service-flow pre-defined {isf | secondary secondary-index | critical} profile sf-profile-name {cr | encap-type none [cr |vlan-id vlan-number]}
Syntax Description
Defaults
There are no default values.
Command Modes
SLA profile configuration submode.
Command History
12.4(15)XL
This command was introduced.
12.4(15)XL1
The cr, encap-type none, and vlan-id vlan-number keywords and arguments were added.
12.4(24)YG
The critical keyword was added.
Usage Guidelines
Currently 1 initial service flow and 1 secondary service flow is allowed per subscriber. Each service flow can be associated with a pre-configured service flow for QoS and packet classification rule parameters in the uplink and downlink direction.
The BWG controls the BS's local switching through Data Path Encapsulation Type (NONE) and Data Path ID (Priority + VLAN ID) in the R6 DP Registration Request message. Note that the VLAN ID defined here can be overwritten from AAA. The VLAN Priority (the 3 most significant bits in VLAN tag) comes from DSCP/Precedence defined for the service flow. If DSCP/Precedence is not locally defined, it is calculated based on WiMAX QoS Data Delivery Service Type used for the service flow.
The critical keyworde allows a Service Flow(SF) to be marked as critical for the subscriber. The BWG will successfully create subscriber session if and only if every SF marked "Critical" is created.
The BWG allows you to mark a SF as critical while adding it under SLA profile configuration. If the SF is marked critical, then session will fail to open if such critical SF fails to create. The key point is that every critical flow must be created successfully for a session to open. If a SF is not marked to be critical, or if it is ISF, then there is no change in existing behavior.
During Controlled Handover, if the Target-BS fails to include critical flow(s), then the BWG will fail the Handover. The point is to ensure that the "all or none flow(s)" philosophy gets applied to a subscriber all the time.
By default, a SF is not critical, unless specified as "critical" in a SLA-profile.
The flow details in show wimax agw subscriber will indicate if a flow is critical or not.
Examples
The following example enables the initial service flow:
wimax agw sla profile goldservice-flow pre-defined isf profile isf encap-type none vlan 10service-flow pre-defined secondary profile sec1 encap-type none vlan 10service mode maintenance
To enable the User Group Maintenance mode feature that allows you to to block any new CPE from entering a particular user group so that the you can clear all of the subscribers (if needed), use the service mode maintenance global configuration command. Use the no form of the command to disable this feature.
service mode maintenance
no service mode maintenance
Syntax Description
There are no keywords or arguments for this command.
Defaults
By default, maintenance mode is disabled.
Command Modes
User group configuration submode.
Command History
Examples
Here is a sample configuration:
User group domain name unauthenticatedUser-Group overwritten Counter 0Service mode operationalSessions 2 associatedIP-GRE Traffic Sent 0 packets, 0 bytesIP-GRE Traffic Received 0 packets, 0 bytesEth-GRE Traffic Sent 18 packets, 6138 bytesEth-GRE Traffic Received 18 packets, 10872 bytesIngress Address filtering 0 packets, 0 bytesTraffic Received redirected 0 packets, 0 bytesSessions rejected due to service mode not operational 0 // new line
set
To specify what DSCP or TOS marking needs to be applied for the subscriber packets in the downstream direction, use the set subcommand in service flow direction configuration submode. Use the no form of the command to disable this feature. By default no marking is done.
set [dscp dscp-value | precedence precedence-value | r3 ]
no set [dscp dscp-value | precedence precedence-value | r3 ]
Syntax Description
Defaults
By default, no marking is done. The default value for dscp is 0.
Command Modes
Service flow direction configuration submode.
Command History
Examples
The following example specifies the precedence-value and dscp-value arguments:
router(config-gw-sf-dir)#set dscp ?<0-63> Differentiated services codepoint valueaf11 Match packets with AF11 dscp (001010)af12 Match packets with AF12 dscp (001100)af13 Match packets with AF13 dscp (001110)af21 Match packets with AF21 dscp (010010)af22 Match packets with AF22 dscp (010100)af23 Match packets with AF23 dscp (010110)af31 Match packets with AF31 dscp (011010)af32 Match packets with AF32 dscp (011100)af33 Match packets with AF33 dscp (011110)af41 Match packets with AF41 dscp (100010)af42 Match packets with AF42 dscp (100100)af43 Match packets with AF43 dscp (100110)cs1 Match packets with CS1(precedence 1) dscp (001000)cs2 Match packets with CS2(precedence 2) dscp (010000)cs3 Match packets with CS3(precedence 3) dscp (011000)cs4 Match packets with CS4(precedence 4) dscp (100000)cs5 Match packets with CS5(precedence 5) dscp (101000)cs6 Match packets with CS6(precedence 6) dscp (110000)cs7 Match packets with CS7(precedence 7) dscp (111000)default Match packets with default dscp (000000)ef Match packets with EF dscp (101110)r3 Set GW service flow R6 dscp with R3 dscp value NEWThe next two are new additions for direction uplink. The BWG marks the outbound R3 IP DSCP value either by specifiying a value (set r3 dscp value), or using the outer IP DSCP value (set r3 dscp r6-outer). If either is not specified, the default is to have no change to the inner IP DSCP value. Here is an example:
router(config-gw-sf-dir)#set ?dscp Set GW service flow dscp specific valuesprecedence Set GW service flow Precedence specific valuesr3 Set GW R3 reference point configuration commands NEWrouter(config-gw-sf-dir)#set r3 dscp ? ALL NEW BELOW<0-63> Differentiated services codepoint valueaf11 Match packets with AF11 dscp (001010)af12 Match packets with AF12 dscp (001100)af13 Match packets with AF13 dscp (001110)af21 Match packets with AF21 dscp (010010)af22 Match packets with AF22 dscp (010100)af23 Match packets with AF23 dscp (010110)af31 Match packets with AF31 dscp (011010)af32 Match packets with AF32 dscp (011100)af33 Match packets with AF33 dscp (011110)af41 Match packets with AF41 dscp (100010)af42 Match packets with AF42 dscp (100100)af43 Match packets with AF43 dscp (100110)cs1 Match packets with CS1(precedence 1) dscp (001000)cs2 Match packets with CS2(precedence 2) dscp (010000)cs3 Match packets with CS3(precedence 3) dscp (011000)cs4 Match packets with CS4(precedence 4) dscp (100000)cs5 Match packets with CS5(precedence 5) dscp (101000)cs6 Match packets with CS6(precedence 6) dscp (110000)cs7 Match packets with CS7(precedence 7) dscp (111000)default Match packets with default dscp (000000)ef Match packets with EF dscp (101110)r6-outer Set GW service flow R3 dscp with R6 dscp valuerouter(config-gw-sf-dir)#set precedence precedence-value<0-7> Precedence valuecritical Set packets with critical precedence (5)flash Set packets with flash precedence (3)flash-override Set packets with flash override precedence (4)immediate Set packets with immediate precedence (2)internet Set packets with internetwork control precedence (6)network Set packets with network control precedence (7)priority Set packets with priority precedence (1)routine Set packets with routine precedence (0)service wimax agw
To enable the BWG functionality on the router, use the service wimax agw command in global configuration mode. Use the no version of the command to disable BWG functionality; all configured BWG-specific command lines will also be removed.
service wimax agw
no service wimax agw
Syntax Description
There are no arguments or keywords.
Defaults
There are no default values.
Command Modes
Global configuration.
Command History
Usage Guidelines
The no version of the command will disable the BWG functionality and all the configured BWG-specific command lines will be removed. The no version of the command will be allowed only if there no session being serviced on the BWG.
Examples
The following example enables the BWG:
router(config)#service wimax agwshow ip mobile proxy
To display information about a proxy Mobile IP host, use the show ip mobile proxy command in privileged EXEC mode.
show ip mobile proxy [host [nai string] | registration | traffic]
Syntax Description
Defaults
The command is disabled by default.
Command History
12.2(2)XC
This command was introduced.
12.3(4)T
This command was integrated into Cisco IOS Release 12.3(4)T for PDSN platforms.
Examples
The following is sample output from the show ip mobile proxy registration command:
router# show ip mobile proxy registrationProxy Mobile Node Registrations:100022240001@cisco.com:Registration accepted 06/16/08 18:42:36Next Re-registration 00:21:27Registration sequence number 1Care-of addr 14.1.1.30, HA addr 14.1.1.80, Home addr 5.1.0.2Flags sbdmg-T-, Identification CC01329C.68498C88Lifetime requested 00:50:00 (3000), granted 00:50:00, remaining 00:46:27Revocation negotiatedshow ip slb sessions
To display information about sessions handled by Cisco IOS Server Load Balancing (IOS SLB), use the show ip slb sessions command in privileged EXEC mode.
show ip slb sessions [gtp | gtp-inspect | ipmobile | radius] [vserver virtual-server] [client ip-address netmask] [asnr6] [detail]
Syntax Description
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the show ip slb sessions command for ASN sessions:
router# show ip slb sessions asnr6vserver MSID Base Station real state------------------------------------------------------------------------------10.10.10.10 001646013fc0 5.5.5.5 10.10.1.1 ASNR6_REQrouter# show ip slb session asnr6 detailASN, client = 12.12.12.1:2231, virtual = 3.3.3.3:2231state = ASNR6_ESTAB, real = 2.2.2.2Key = 0000000100020003, retry = 1show ip slb sticky
To display information about load balancing stickiness, use the show ip slb sticky command in Privileged EXEC mode.
show ip slb sticky asn [msid | nai]
Syntax Description
asn msid | nai
(Optional) Displays information about BWG stickiness using the msid or nai arguments.
Defaults
There are no default values for this command.
Command Modes
Privileged EXEC.
Command History
Examples
Here is an example configuration:
show ip slb sticky asn msid <macid>MSID Real Group Id vs_index NAI-------------------------------------------------------ABCD.12FE.3467 10.10.10.1 5 10 abc@cisco.com2247.1130.8642 10.10.10.2 5 10 bcd@abc.com- show ip slb sticky asn nai abc@cisco.comMSID Real Group Id vs_index NAI-------------------------------------------------------ABCD.12FE.3467 10.10.10.1 5 10 abc@cisco.com- show ip slb statsMWTCL06-SW1#sh ip slb statsPkts via normal switching: 101126Pkts via special switching: 0Pkts via slb routing: 0Pkts Dropped: 0Connections Created: 101068Connections Established: 0Connections Destroyed: 101067Connections Reassigned: 0Zombie Count: 0Connections Reused: 0Connection Flowcache Purges: 0Failed Connection Allocs: 0Failed Real Assignments: 0RADIUS framed-ip Sticky Count: 0RADIUS username Sticky Count: 0RADIUS cstn-id Sticky Count: 0GTP imsi Sticky Count: 0Failed Correlation Injects: 0Pkt fragments drops in ssv: 0ASN MSID sticky count: 1router#show ip slb vservers name VS detailVS, state = OPERATIONAL, v_index = 9, interface(s) = <any>virtual = 3.2.3.1/32:2231, UDP, service = ASN, advertise = TRUEserver farm = 7200-FARM, delay = 10, idle = 100asn: request idle = 90asn: delete notif recvd = 2, nai-update notif recvd = 2asn: Notification Errors : Deletes = 1, nai-updates = 0sticky: <none>sticky: group id = 4097 <assigned>synguard counter = 0, synguard period = 0conns = 0, total conns = 156, syns = 0, syn drops = 0standby group = None--------------------------------------------------------| delete | nai-updatesReal commn: |--------+--------+--------+-------------Port = 63082 | Recv | Errors | Recv | Errors---------------+--------+--------+--------+-------------15.15.15.4 1 1 1 015.15.15.5 1 0 1 0Fields to display communication port between the vserver VS and BWG, delete notification received and NAI updates and notification because of stale session in wrong reals will be added as shown above.
router#show ip slb session asn <cr>vserver MSID Base Station real state----------------------------------------------------------------------------10.10.10.10 001646013fc0 5.5.5.5 10.10.1.1 ASN_ESTABshow subscriber msid bs-list
To view the allowed BS list, use the show subscriber msid bs-list command in the Privileged EXEC mode.
show subscriber msid msid bs-list
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC.
Command History
Examples
Here is an example of the show subscriber msid bs-list command:
router#show wimax agw subscriber msid 0900.0502.1000 bs-listMSID 0900.0502.1000Allowed Base Station(s):0A 0A 0A 4DAA AA AAshow wimax agw
To display various system parameters, including BWG software version, number of base stations allowed, number of subscribers allowed, and others, use the show wimax agw privileged EXEC command.
show wimax agw
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC.
Command History
Usage Guidelines
The output of this show command contains the following information:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Examples
The following is sample output for the show wimax agw command:
Broadband wireless gateway version 1.1, service is enabledSignaling UDP port 2231Maximum Number of base station 500 allowedMaximum Number of subscriber 20000 allowedCurrent number of framed routes 0Current number of subscribers using framed routes 0Current number of signalling paths 1Current number of data paths 1Current number of subscribers 1Current number of sessions 1Current number of user auto-provisioned sessions 0Current number of flows 2Current number of hosts 0Current number of sessions with all ip packets redirected 0IP-GRE traffic Sent 0 packets, 0 bytesIP-GRE traffic Rcvd 0 packets, 0 bytesIP-GRE Traffic Rcvd redirected 0 packets, 0 bytesEth-GRE traffic Sent 2 packets, 748 bytesEth-GRE traffic Rcvd 2 packets, 1208 bytesEth-GRE Traffic Rcvd redirected 0 packets, 0 bytesDisplay information about the BWG redundancy specific statistics.
Snapshot:WiMAX BWGBWG Session Redundancy CountersRedundancy Events Counters On ActiveSession EventsSession Up Success : 100Session Down Success : 10Flow EventsFlow Up Success : 200Flow Down Success : 0Host EventsHost Up Success : 300Host Down Success : 100Authentication EventsRe-authentication Update Success : 10Accounting EventsAccounting Update SuccessHere is an example for BWG IOS Release 12.4(15)XL3:
BWG-2#sh wim agwBroadband wireless gateway version 1.2, service is enabledSignaling UDP port 2231Session Redundancy State ACTIVEMaximum Number of base station 500 allowedMaximum Number of subscriber 20000 allowedCurrent number of framed routes 0Current number of subscribers using framed routes 0Current number of signalling paths 1Current number of data paths 1Current number of subscribers 1Current number of sessions 1Current number of user auto-provisioned sessions 0Current number of flows 2Current number of hosts 0Current number of sessions with all ip packets redirected 0IP-GRE traffic Sent 4 packets, 1212 bytesIP-GRE traffic Rcvd 6 packets, 3624 bytesIP-GRE Traffic Rcvd redirected 0 packets, 0 bytesEth-GRE traffic Sent 0 packets, 0 bytesEth-GRE traffic Rcvd 0 packets, 0 bytesEth-GRE Traffic Rcvd redirected 0 packets, 0 bytesshow wimax agw fsm dhcp-proxy
To show how many sessions are in the various states of the DHCP/MIP proxy state machine, use the show wimax agw fsm dhcp-proxy command in privileged EXEC mode.
show wimax agw fsm dhcp-proxy
Syntax Description
There are no keywords or arguments for this command.
Defaults
There are no default values.
Command Modes
Privileged EXEC.
Command History
Examples
The following is sample output for the show wimax agw fsm dhcp-proxy command:
router#show wimax agw fsm dhcp-proxyAGW Proxy FSMNumber of element(s) currently in following states----------------------------------------------------Init(0) = 0, Registering(1) = 0, Registered(2) = 0Deregistering(3) = 0, Assigning(4) = 0, Ready(5) = 1Cleanup(6) = 0show wimax agw message
To display information about the messages supported by the BWG, use the show wimax agw message command in privileged EXEC mode.
show wimax agw message [function-type-no]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC.
Command History
Usage Guidelines
If a Function-Type number is not specified, then the command displays information about all the supported Function-Types.
The output of this show command contains the following information:
•
•
•
•
•
•
•
•
•
Examples
The following is sample output for the show wimax agw message [function-type-no] command:
Message function type Data Path(3/0x3)Highest message type value 16Reference pts on which rcvd/sent BS <-> AGW R6(8)Message type Deregistration Request(4/0x4)Reference pts on which rcvd/sent BS <-> AGW R6(8)Expecting response for this messageMessage type Deregistration Response(5/0x5)Reference pts on which rcvd/sent BS <-> AGW R6(8)Expecting response for this messageMessage type Deregistration Ack(6/0x6)Reference pts on which rcvd/sent BS <-> AGW R6(8)Not expecting response for this messageMessage type Registration Request(12/0xC)Reference pts on which rcvd/sent BS <-> AGW R6(8)Expecting response for this messageMessage type Registration Response(13/0xD)Reference pts on which rcvd/sent BS <-> AGW R6(8)Expecting response for this messageMessage type Registration Ack(14/0xE)Reference pts on which rcvd/sent BS <-> AGW R6(8)Not expecting response for this messageMessage function type Context Delivery(4/0x4)router#sh wimax agw messageMessage function type Data Path(3/0x3)Highest message type value 16Reference pts on which rcvd/sent BS <-> AGW R6(8)Message type Deregistration Request(4/0x4)Reference pts on which rcvd/sent BS <-> AGW R6(8)Expecting response for this messageMessage type Deregistration Response(5/0x5)Reference pts on which rcvd/sent BS <-> AGW R6(8)Expecting response for this messageMessage type Deregistration Ack(6/0x6)Reference pts on which rcvd/sent BS <-> AGW R6(8)Not expecting response for this messageMessage type Registration Request(12/0xC)Reference pts on which rcvd/sent BS <-> AGW R6(8)Expecting response for this messageMessage type Registration Response(13/0xD)Reference pts on which rcvd/sent BS <-> AGW R6(8)Expecting response for this messageMessage type Registration Ack(14/0xE)Reference pts on which rcvd/sent BS <-> AGW R6(8)Not expecting response for this messageMessage function type Context Delivery(4/0x4)Highest message type value 4Reference pts on which rcvd/sent BS <-> AGW R6(8)Message type Context Delivery Request(1/0x1)Reference pts on which rcvd/sent BS <-> AGW R6(8)Expecting response for this messageMessage type Context Delivery Report(2/0x2)Reference pts on which rcvd/sent BS <-> AGW R6(8)Not expecting response for this messageMessage function type Auth Relay(8/0x8)Highest message type value 10Reference pts on which rcvd/sent BS <-> AGW R6(8)Message type EAP Start(1/0x1)Reference pts on which rcvd/sent BS <-> AGW R6(8)Not expecting response for this messageMessage type EAP Transfer(2/0x2)Reference pts on which rcvd/sent BS <-> AGW R6(8)Not expecting response for this messageMessage type Key Change Directive(5/0x5)Reference pts on which rcvd/sent BS <-> AGW R6(8)Expecting response for this messageMessage type Key Change Confirm(6/0x6)Reference pts on which rcvd/sent BS <-> AGW R6(8)Expecting response for this messageMessage type Key Change ACK(7/0x7)Reference pts on which rcvd/sent BS <-> AGW R6(8)Not expecting response for this messageMessage type CMAC Key Count Update(8/0x8)Reference pts on which rcvd/sent BS <-> AGW R6(8)Expecting response for this messageMessage type CMAC Key Count Update Ack(9/0x9)Reference pts on which rcvd/sent BS <-> AGW R6(8)Not expecting response for this messageMessage function type MS State Change(9/0x9)Highest message type value 18Reference pts on which rcvd/sent BS <-> AGW R6(8)Message type Attachment Response(7/0x7)Reference pts on which rcvd/sent BS <-> AGW R6(8)Expecting response for this messageMessage type Attachment Request(8/0x8)Reference pts on which rcvd/sent BS <-> AGW R6(8)Expecting response for this messageMessage type Attachment ACK(9/0x9)Reference pts on which rcvd/sent BS <-> AGW R6(8)Not expecting response for this messageMessage type Pre Attachment Request(15/0xF)Reference pts on which rcvd/sent BS <-> AGW R6(8)Expecting response for this messageMessage type Pre Attachment Response(16/0x10)Reference pts on which rcvd/sent BS <-> AGW R6(8)Expecting response for this messageMessage type Pre Attachment ACK(17/0x11)Reference pts on which rcvd/sent BS <-> AGW R6(8)Not expecting response for this messageMessage function type Keepalive(20/0x14)Highest message type value 3Reference pts on which rcvd/sent BS <-> AGW R6(8)Message type Keepalive Request(1/0x1)Reference pts on which rcvd/sent BS <-> AGW R6(8)Expecting response for this messageMessage type Keepalive Response(2/0x2)Reference pts on which rcvd/sent BS <-> AGW R6(8)Not expecting response for this messageshow wimax agw path
To display base station information, use the show wimax agw path command in privileged EXEC mode.
show wimax agw path [bs-ip-address] [brief]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC.
Command History
Examples
The following is sample output for the show wimax agw path command:
Router#show wimax agw path briefBase station Type Elements State Pkts-Rx Pkts-Tx Bytes-Rx Bytes-Tx10.1.1.84 Sig-UDP 1 Ready 134 135 11196 940410.1.1.84 Data-GRE 1 -- 10811 10816 6983906 386016710.1.1.84 IP-GRE -- 0811 16 6983000 3860000Eth-GRE -- 10000 10800 906 167Router#show wimax agw path dataPath type Data-GRENumber of flows connected 1Address local 2.2.2.2(AF_INET), remote 10.1.1.84(AF_INET)IP Traffic sent 10833 packets, 3866236 bytesIP Traffic received 10828 packets, 6994888 bytesEthernet Traffic sent 10833 packets, 3866236 bytesEthernet Traffic received 10833 packets, 3866236 bytesRouter#show wimax agw path 10.1.1.70Path type Sig-UDPState current Ready, old IdleNumber of sessions connected 1Number of old sessions connected 0Address local 11.1.4.0(AF_INET), remote 10.1.4.77(AF_INET)UDP port local 2231(0x8B7), remote 2231(0x8B7)Identification Peer 0x0A01044D, Our 0x0B010400IP-GRE traffic sent 15 packets, 4643 bytesIP-GRE traffic received 14 packets, 2879 bytesPath type Data-GRENumber of flows connected 2Address local 11.1.4.0(AF_INET), remote 10.1.4.77(AF_INET)Ethernet-GRE traffic sent 2 packets, 832 bytesEthernet-GRE traffic received 2 packets, 1320 bytesIP-GRE traffic sent 0 packets, 0 bytesIP-GRE traffic received 0 packets, 0 bytesshow wimax agw redundancy status
To display session redundancy status on the BWG, use the show wimax agw redundancy status command in privileged EXEC mode.
show wimax agw redundancy status
Syntax Description
There are no keywords or arguments for this command.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC.
Command History
Examples
The following is sample output for the show wimax agw redundancy status command:
Router#show wimax agw redundancy statusWiMAX AGW Session Redundancy is enableWiMAX AGW Session Redundancy system statusAGW state = STANDBY HOTAGW-peer state = ACTIVEWiMAX AGW Session Redundancy Status SummarySynced from activeSubscriber 1Flows 2Hosts 0show wimax agw statistics
To display statistics per reference point, use the show wimax agw statistics command in privileged EXEC mode.
show wimax agw statistics [dfp | dhcp-relay | dhcp-proxy | internal | arp] | [brief]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC.
Command History
Usage Guidelines
In BWG Release 2.0, the following information is added for the show wimax agw statistics internal command:
•
•
•
•
•
•
•
•
For each reference point, the following information will be displayed
•
•
Examples
The following is sample output for the show wimax agw statistics command:
Router#show wimax agw statisticsMessage function type MS State Change(9/0x9)Message type Attachment Response(7/0x7)Number of messages sent 4Number of messages received 0Number of messages resent 0Message type Attachment Request(8/0x8)Number of messages sent 0Number of messages received 4Number of messages resent 0Message type Attachment ACK(9/0x9)Number of messages sent 0Number of messages received 4Number of messages resent 0Message type Pre Attachment Request(15/0xF)Number of messages sent 0Number of messages received 4Number of messages resent 0Message type Pre Attachment Response(16/0x10)Number of messages sent 4Number of messages received 0Number of messages resent 0Message type Pre Attachment ACK(17/0x11)Number of messages sent 0Number of messages received 4Number of messages resent 0Data Path Statistics
Router#show wimax agw statisticsMessage function type Data Path(3/0x3)Message type Deregistration Request(4/0x4)Number of messages sent 1Number of messages received 1Number of messages resent 0Message type Deregistration Response(5/0x5)Number of messages sent 1Number of messages received 0Number of messages resent 0Message type Deregistration Ack(6/0x6)Number of messages sent 0Number of messages received 1Number of messages resent 0Message type Registration Request(12/0xC)Number of messages sent 8Number of messages received 1Number of messages resent 0Message type Registration Response(13/0xD)Number of messages sent 1Number of messages received 8Number of messages resent 0Message type Registration Ack(14/0xE)Number of messages sent 8Number of messages received 1Number of messages resent 0The following information will be displayed for ARP related command
Router# sh wim agw statistics arpTotal number of ARP requests receivedTotal number of ARP reply sentTotal number of ARP packets droppedTimeout Statistics
Message function type Keepalive(20/0x14)Message type Keepalive Request(1/0x1)Number of messages sent 21Number of messages received 0Number of messages resent 0Message type Keepalive Response(2/0x2)Number of messages sent 0Number of messages received 21Number of messages resent 0Here are examples of the show wimax agw statistics dhcp-relay and show wimax agw statistics dhcp-proxy commands:
BWG#sh wim agw statistics dhcp-relayLast clearing of "show wimax agw statistics dhcp-relay" counters neverTx to DHCP server Discover 171, Request 143Tx to DHCP server Release 0, Decline 0Tx to DHCP server Inform 0Rx from DHCP server Offer 115, Ack 116Rx from DHCP server Nak 0, Unknown 0BWG#show wimax agw statistics dhcp-proxyLast clearing of "show wimax agw statistics dhcp-proxy" counters neverRx from DHCP client Discover 24, Request 65Rx from DHCP client Release 0, Decline 0Rx from DHCP client Inform 0Tx to DHCP client Offer 24, Ack 65Tx to DHCP client Nak 0, Unknown 0show wimax agw subscriber
To display subscriber information, use the show wimax agw subscriber command in privileged EXEC mode. If the subscriber macid is not specified, the output displays information about all the subscribers currently connected to the BWG.
show wimax agw subscriber [msid macid [overflowed-host]] [bsid] [brief {flow | host | session | traffic}] [internal]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC.
Command History
Usage Guidelines
The following information will be displayed for each subscriber:
•
•
•
•
•
•
•
•
•
•
•
If the brief keyword is specified, then the output will contain the following information:
•
•
•
•
In Release 2.0 the output reflects the PMIP context information in the BWG. The PMIP tunnel and registry information is obtained from the standard proxy mobile IP commands.
The following information has been added:
•
•
–
–
//if host-config exists,
–
–
–
–
•
–
•
In addition to the above, in BWG Release 2.0, the following information has been added to the wimax agw subscriber internal command:
•
–
–
–
–
–
–
–
–
Examples
The following is sample output for the show wimax agw subscriber command:
BWG-2#sh wim agw subMSID 1000.2227.0001CPE is non-nomadicStatic IP address list downloadedSubscriber Age 000:15:55Base Station ID 0x0E01010300000000Auth policy 0X0(0)PMIP permittedPMIP HA Address 14.1.1.80PMIP Reg Lifetime is 3000PMIP Home Address 5.1.0.1PMIP host cfg dns ext(primary addr) 14.1.1.200PMIP host cfg dns ext(secondary addr) 14.1.1.201PMIP host cfg prefix length 16Subscriber address 5.1.0.1, type IPv4, organization IETFSubscriber address method Dynamic, source DHCP proxySubscriber address assigned using PMIPSubscriber address assigned on flow downlink ID 401Subscriber address prefix len allocated 32, aggregate 0Subscriber address IP-GRE traffic sent 0 packets, 0 bytesSubscriber address IP-GRE traffic received 0 packets, 0 bytesSubscriber address Eth-GRE traffic sent 0 packets, 0 bytesSubscriber address Eth-GRE traffic received 0 packets, 0 bytesSubscriber address DHCP XID 2343, server 0.0.0.0, htype 1Subscriber address DHCP client ID 1000.2227.0001, length 6Subscriber address DHCP Refresh time 3000 secondsSubscriber idle time 00:15:57Subscriber host accounting not enabledSubscriber address format ARPA, type EtherNumber of hosts rejected 0Number of packets dropped due to Static IP Host not authorized by AAA 0Number of packets dropped due to Static IP Host not authorized by HA 0Number of packets dropped due to MIP registration incomplete 1Number of static hosts aged out 0Number of handoff rejected due to unapproved BS 0Number of Host behind 0Number of sessions 1Session details:FSM in state Ready(7) on last event Post Attachment(17)Username 100022270001@unauthenticated.comAuthentication method PAPSession Hotlining InactiveAAA Termination action 0Associated user group unauthenticatedAssociated SLA Profile Name silverSignalling address local 3.3.3.3, remote 14.1.1.3Signalling UDP port local 2231, remote 2231Idle for inbound 00:15:58, outbound 00:15:58Absolute timeout 80000, remaining 22:00:30Ingress Address filtering 0 packets, 0 bytesSession Up for trafficNumber of flows 5Flow details ISF(0)SF Profile name isfFSM in state SF Ready(4) on last event Up(1)Transaction ID used 0X8001(32769)Data ID local 0xC9(201), remote 0xC5(197)Data address local 3.3.3.3, remote 14.1.1.3Data traffic sent 2 packets, 626 bytesData traffic received 3 packets, 1812 bytesAccounting last record sent Start(1)Accounting start response UnknownIdle for inbound 00:15:58, outbound 00:15:58Service Flow information Downlink:Identifier 401Set dscp cs1QoS information:data-delivery-service best-effortmaximum-traffic-rate-sustained 0, traffic-priority 0policy-transmission-request 0reduced-resources-code 0media-flow-type 02123424231412Classifier information:priority 1ipv4 permit ip any anyethernet permit any any anyvlan permit any anyCS Type information:Ethernet CSService Flow information Uplink:Identifier 402Set dscp cs2QoS information:data-delivery-service best-effortmaximum-traffic-rate-sustained 0, traffic-priority 0policy-transmission-request 0reduced-resources-code 0media-flow-type 0a45464748Classifier information:priority 1ipv4 permit ip any anyethernet permit any any anyvlan permit any anyCS Type information:Ethernet CSFlow details Secondary(1)SF Profile name sec1FSM in state SF Ready(4) on last event Up(1)Transaction ID used 0X8002(32770)Data ID local 0xCA(202), remote 0xC6(198)Data address local 3.3.3.3, remote 14.1.1.3Data traffic sent 0 packets, 0 bytesData traffic received 0 packets, 0 bytesAccounting last record sent Start(1)Accounting start response UnknownIdle for inbound 00:16:02, outbound 00:16:02Service Flow information Downlink:Identifier 403Set dscp af11QoS information:data-delivery-service best-effortmaximum-traffic-rate-sustained 0, traffic-priority 0policy-transmission-request 0reduced-resources-code 0media-flow-type 02123424231412Classifier information:priority 2ipv4 permit ip any anyethernet permit any any anyvlan permit any anyCS Type information:Ethernet CSService Flow information Uplink:Identifier 404Set dscp af12QoS information:data-delivery-service best-effortmaximum-traffic-rate-sustained 0, traffic-priority 0policy-transmission-request 0reduced-resources-code 0media-flow-type 0a45464748Classifier information:priority 2ipv4 permit ip any anyethernet permit any any anyvlan permit any anyCS Type information:Ethernet CSFlow details Secondary(2)SF Profile name sec2FSM in state SF Ready(4) on last event Up(1)Transaction ID used 0X8003(32771)Data ID local 0xCB(203), remote 0xC7(199)Data address local 3.3.3.3, remote 14.1.1.3Data traffic sent 0 packets, 0 bytesData traffic received 0 packets, 0 bytesAccounting last record sent Start(1)Accounting start response UnknownIdle for inbound 00:16:03, outbound 00:16:03Service Flow information Downlink:Identifier 405Set dscp af11QoS information:data-delivery-service best-effortmaximum-traffic-rate-sustained 0, traffic-priority 0policy-transmission-request 0reduced-resources-code 0media-flow-type 02123424231412Classifier information:priority 3ipv4 permit ip any anyethernet permit any any anyvlan permit any anyCS Type information:Ethernet CSService Flow information Uplink:Identifier 406Set dscp af12QoS information:data-delivery-service best-effortmaximum-traffic-rate-sustained 0, traffic-priority 0policy-transmission-request 0reduced-resources-code 0media-flow-type 0a45464748Classifier information:priority 3ipv4 permit ip any anyethernet permit any any anyvlan permit any anyCS Type information:Ethernet CSFlow details Secondary(3)SF Profile name sec3FSM in state SF Ready(4) on last event Up(1)Transaction ID used 0X8004(32772)Data ID local 0xCC(204), remote 0xC8(200)Data address local 3.3.3.3, remote 14.1.1.3Data traffic sent 0 packets, 0 bytesData traffic received 0 packets, 0 bytesAccounting last record sent Start(1)Accounting start response UnknownIdle for inbound 00:16:03, outbound 00:16:03Service Flow information Downlink:Identifier 407Set dscp af11QoS information:data-delivery-service best-effortmaximum-traffic-rate-sustained 0, traffic-priority 0policy-transmission-request 0reduced-resources-code 0media-flow-type 02123424231412Classifier information:priority 4ipv4 permit ip any anyethernet permit any any anyvlan permit any anyCS Type information:Ethernet CSService Flow information Uplink:Identifier 408Set dscp af12QoS information:data-delivery-service best-effortmaximum-traffic-rate-sustained 0, traffic-priority 0policy-transmission-request 0reduced-resources-code 0media-flow-type 0a45464748Classifier information:priority 4ipv4 permit ip any anyethernet permit any any anyvlan permit any anyCS Type information:Ethernet CSFlow details Secondary(4)SF Profile name sec4FSM in state SF Ready(4) on last event Up(1)Transaction ID used 0X8005(32773)Data ID local 0xCD(205), remote 0xC9(201)Data address local 3.3.3.3, remote 14.1.1.3Data traffic sent 0 packets, 0 bytesData traffic received 0 packets, 0 bytesAccounting last record sent Start(1)Accounting start response UnknownIdle for inbound 00:16:03, outbound 00:16:03Service Flow information Downlink:Identifier 409Set dscp af11QoS information:data-delivery-service best-effortmaximum-traffic-rate-sustained 0, traffic-priority 0policy-transmission-request 0reduced-resources-code 0media-flow-type 02123424231412Classifier information:priority 5ipv4 permit ip any anyethernet permit any any anyvlan permit any anyCS Type information:Ethernet CSService Flow information Uplink:Identifier 410Set dscp af12QoS information:data-delivery-service best-effortmaximum-traffic-rate-sustained 0, traffic-priority 0policy-transmission-request 0reduced-resources-code 0media-flow-type 0a45464748Classifier information:priority 5ipv4 permit ip any anyethernet permit any any anyvlan permit any anyCS Type information:Ethernet CSBWG# show wimax agw subscriber brief [traffic]MSID Base Station Pkts-Tx Bytes-Tx Pkts-Rx Bytes-Rx1000.2223.0001 10.5.5.3 0 0 0 01000.2224.0001 10.5.5.3 0 0 0 0BWG# show wimax agw subscriber brief flow [traffic]MSSID Base Station Idx Pkts-Tx Bytes-Tx Pkts-Rx Bytes-Rx1000.2223.0001 10.5.5.3 0 0 0 0 01000.2223.0001 10.5.5.3 1 0 0 0 01000.2224.0001 10.5.5.3 0 0 0 0 01000.2224.0001 10.5.5.3 1 0 0 0 0BWG# show wimax agw subscriber brief host [traffic]MSID Base Station Index Pkts-Tx Bytes-Tx Pkts-Rx Bytes-Rx1000.2223.0001 10.5.5.3 1 0 0 0 01000.2224.0001 10.5.5.3 1 0 0 0 0Here is an example of the show wimax agw subscriber command for IOS Release 12.4(15)XL3:
BWG#sh wim agw subs , ms 0032.235F.ABCDMSID 0032.235F.ABCDCPE Settings: 7CPE is nomadicStatic IP addresses permittedSubscriber Age 000:03:39Base Station ID 0x0A010646Auth policy 0X12(18), Single-EAP, CMACAK Ctx method C-MAC(1), Lifetime 65535AK Ctx Seq No. AK 0, PMK 0AK Ctx C-MAC key count 1Subscriber address 11.1.0.2, type IPv4, organization IETFSubscriber address method Dynamic, source DHCP relaySubscriber address assigned on flow downlink ID 9Subscriber address prefix len allocated 16, aggregate 32Subscriber address IP-GRE traffic sent 0 packets, 0 bytesSubscriber address IP-GRE traffic received 0 packets, 0 bytesSubscriber address Eth-GRE traffic sent 0 packets, 0 bytesSubscriber address Eth-GRE traffic received 0 packets, 0 bytesSubscriber address DHCP XID 9148, server 0.0.0.0, htype 1Subscriber address DHCP client ID 0032.235F.ABCD, length 6Subscriber address DHCP Refresh time 18000 secondsSubscriber address format ARPA, type EtherNumber of hosts rejected 0Number of packets dropped due to Static IP Host not allowed 0Number of static hosts aged out 0Number of handoff rejected due to unapproved BS 0Number of Host behind 0Number of sessions 1Session details:FSM in state Ready(7) on last event Rx Attach Ack(16)Username rahumani@eap-tls.comAuthentication method EAPAAA Framed route 5.5.0.0, mask 255.255.0.0AAA Session-id length 4, 0x30313233AAA Termination action 1AAA Class class-wimax-changedReauthentication attempts from subscriber 0, ASNGW 0Associated user group cisco.comAssociated SLA Profile Name silver,platinum,goldSignalling address local 11.1.6.1, remote 10.1.6.70Signalling UDP port local 2231, remote 2231Idle for inbound 00:03:37, outbound 00:03:37Ingress Address filtering 0 packets, 0 bytesNumber of flows 4Flow details ISF(0)SF profile name isfFSM in state SF Ready(4) on last event Up(1)Transaction ID used 0X8009(32777)Data ID local 0x5(5), remote 0xE(14)Data address local 11.1.6.1, remote 10.1.6.70Data traffic sent 2 packets, 748 bytesData traffic received 2 packets, 1208 bytesAccounting disabledIdle for inbound 00:03:37, outbound 00:03:37Service Flow information Downlink:Identifier 9Set DSCP (DDS) 30QoS information:Data-delivery-service real-time-variable-rateMinimum traffic-rate-reserved 4, Maximum latency 1Unsolicited interval-polling 9, Traffic-priority 1Maximum traffic-rate-sustained 3, Request/Transmission-policy 5Maximum traffic-burst-rate 2Reduced-resources-code 0Classifier information:priority 0ipv4 permit ip any anyethernet permit any any anyvlan permit 5 0CS Type information:Ethernet CSService Flow information Uplink:Identifier 10Set DSCP af22QoS information:Data-delivery-service best-effortMaximum traffic-rate-sustained 0 Traffic-priority 0Request/Transmission-policy 51Reduced-resources-code 0Classifier information:priority 0ipv4 permit ip any anyethernet permit any any anyvlan permit 10 anyCS Type information:Ethernet CSFlow details Secondary(1)SF profile name secFSM in state SF Ready(4) on last event Up(1)Transaction ID used 0X800A(32778)Data ID local 0x6(6), remote 0xF(15)Data address local 11.1.6.1, remote 10.1.6.70Data traffic sent 0 packets, 0 bytesData traffic received 0 packets, 0 bytesAccounting disabledIdle for inbound 00:03:39, outbound 00:03:39Service Flow information Downlink:Identifier 11Set DSCP (DDS) 30QoS information:Data-delivery-service real-time-variable-rateMinimum traffic-rate-reserved 0, Maximum latency 0Unsolicited interval-polling 0, Traffic-priority 0Maximum traffic-rate-sustained 0, Request/Transmission-policy 0Maximum traffic-burst-rate 0Reduced-resources-code 0Media-flow-type 05abcdClassifier information:priority 1ethernet permit any 1000.2223.0002 FFFF.FFFF.FFFF anyCS Type information:Ethernet CSService Flow information Uplink:Identifier 12Set DSCP (DDS) 30QoS information:Data-delivery-service real-time-variable-rateMinimum traffic-rate-reserved 0, Maximum latency 0Unsolicited interval-polling 0, Traffic-priority 0Maximum traffic-rate-sustained 0, Request/Transmission-policy 0Maximum traffic-burst-rate 0Reduced-resources-code 0Media-flow-type 05abcdClassifier information:priority 1ethernet permit any any ether_type arpCS Type information:Ethernet CSFlow details Secondary(2)SF profile name sec2FSM in state SF Ready(4) on last event Up(1)Transaction ID used 0X800B(32779)Data ID local 0x7(7), remote 0x10(16)Data address local 11.1.6.1, remote 10.1.6.70Data traffic sent 0 packets, 0 bytesData traffic received 0 packets, 0 bytesAccounting disabledIdle for inbound 00:03:39, outbound 00:03:39Service Flow information Downlink:Identifier 13Set DSCP (DDS) 30QoS information:Data-delivery-service real-time-variable-rateMinimum traffic-rate-reserved 0, Maximum latency 0Unsolicited interval-polling 0, Traffic-priority 0Maximum traffic-rate-sustained 0, Request/Transmission-policy 0Maximum traffic-burst-rate 0Reduced-resources-code 0Media-flow-type 05abcdClassifier information:priority 2ethernet permit any 1000.2223.0003 FFFF.FFFF.FFFF anyCS Type information:Ethernet CSService Flow information Uplink:Identifier 14Set DSCP (DDS) 30QoS information:Data-delivery-service real-time-variable-rateMinimum traffic-rate-reserved 0, Maximum latency 0Unsolicited interval-polling 0, Traffic-priority 0Maximum traffic-rate-sustained 0, Request/Transmission-policy 0Maximum traffic-burst-rate 0Reduced-resources-code 0Media-flow-type 05abcdClassifier information:priority 2ipv4 permit ip any anyCS Type information:Ethernet CSFlow details Secondary(3)SF profile name sec3FSM in state SF Ready(4) on last event Up(1)Transaction ID used 0X800C(32780)Data ID local 0x8(8), remote 0x11(17)Data address local 11.1.6.1, remote 10.1.6.70Data traffic sent 0 packets, 0 bytesData traffic received 0 packets, 0 bytesAccounting disabledIdle for inbound 00:03:39, outbound 00:03:39Service Flow information Downlink:Identifier 15Set DSCP (DDS) 30QoS information:Data-delivery-service real-time-variable-rateMinimum traffic-rate-reserved 0, Maximum latency 0Unsolicited interval-polling 0, Traffic-priority 0Maximum traffic-rate-sustained 0, Request/Transmission-policy 0Maximum traffic-burst-rate 0Reduced-resources-code 0Media-flow-type 05abcdClassifier information:priority 3ethernet permit any 1000.2223.0004 FFFF.FFFF.FFFF anyCS Type information:Ethernet CSService Flow information Uplink:Identifier 16Set DSCP (DDS) 30QoS information:Data-delivery-service real-time-variable-rateMinimum traffic-rate-reserved 0, Maximum latency 0Unsolicited interval-polling 0, Traffic-priority 0Maximum traffic-rate-sustained 0, Request/Transmission-policy 0Maximum traffic-burst-rate 0Reduced-resources-code 0Media-flow-type 05abcdClassifier information:priority 3ipv4 permit ip any anyCS Type information:Ethernet CSHere is an example of the BWG 2.0 show wimax agw subscriber internal command:
SAMI_BWG#sh wim agw statistics inter | in CoATotal CoA requests received 0Total CoA success notifications sent 0Total CoA failure notifications sent 0SAMI_BWG6#sh wim agw statistics inter | inc L2Upstream L2 Data packets dropped due to error 0Downstream L2 Data packets dropped due to error 0SAMI_BWG6#sh wim agw statistics inter | inc ACLTotal uplink packets dropped due to hotlining ACL deny 0Total downlink packets dropped due to hotlining ACL deny 0Total uplink packets dropped due to user-group ACL deny 0Total downlink packets dropped due to user-group ACL deny 0Total downlink packets dropped due to paging ACL deny 0In BWG Release 2.0 the show wimax agw sub brief host command is modified so that at the end of each output line a "D" or "S" is added to indicate if it is dynamic or static host.
Here is an example:
Router#sh wim agw sub br hostMSID Index HostID Address DwnLk-SFID Idle Time1000.2223.0001 1 1000.2223.0002 4.4.0.2 1 00:01:54 D1000.2223.0001 2 ----.----.---- 4.4.0.3 3 00:00:18 SHere is an example of the flow details in show wimax agw subscriber that indicate if a flow is critical or not:
Router#sh wim agw subs msid <>MSID 1000.22BA.0001CPE is nomadicStatic IP addresses not permittedSubscriber Age 000:00:23Base Station ID 0x0A01194B00.......Flow details Secondary(2)(Critical)SF Profile name sec2FSM in state SF Ready(4) on last event Up(1)Transaction ID used 0X8003(32771)Data ID local 0x3(3), remote 0xD(13)Data address local 11.1.25.2, remote 10.1.25.75Data traffic sent 0 packets, 0 bytesData traffic received 0 packets, 0 bytesAccounting disabledIdle for inbound 00:00:31, outbound 00:00:31Service Flow information Downlink:Identifier 5Set DSCP (DDS) 30QoS information:Data-delivery-service real-time-variable-rateMinimum traffic-rate-reserved 0, Maximum latency 0Unsolicited interval-polling 0, Traffic-priority 0Maximum traffic-rate-sustained 0, Request/Transmission-policy 0Maximum traffic-burst-rate 0Reduced-resources-code 0Media-flow-type 05abcdClassifier information:priority 2ethernet permit any 1000.2223.0003 FFFF.FFFF.FFFF anyCS Type information:Ethernet CS
show wimax agw tlv
show wimax agw tlv [cisco | NWG] [tlv-type]
Syntax Description
cisco
Cisco-R6 tlv type.
NWG
BWG-R6 tlv type.
tlv-type
Displays information about the supported TLVs.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC.
Command History
12.4(15)XL
This command was introduced.
12.4(24)YG
The cisco, and NWG options were introduced.
Usage Guidelines
If a TLV type is not specified, the command will display information on all the supported TLVs.
The output of this show command contains the following information:
•
•
•
•
•
Examples
The following is sample output for the show wimax agw tlv command:
router# show wimax agw tlv ciscoTLV name MS Information(1/0x1)Maximum size is 0Storage type is NestedTLV name Base Station Information(2/0x2)Maximum size is 0Storage type is NestedTLV name SF Information(3/0x3)Maximum size is 0Storage type is NestedTLV name RT-VR Data Delivery Service(5/0x5)Maximum size is 0Storage type is NestedTLV name Authentication Complete(6/0x6)Maximum size is 0Storage type is NestedTLV name BE Data Delivery Service(7/0x7)Maximum size is 0Storage type is NestedTLV name DP Information(8/0x8)Maximum size is 0Storage type is NestedTLV name NRT-VR Data Delivery Service(9/0x9)Maximum size is 0Storage type is NestedTLV name UGS Data Delivery Service(13/0xD)Maximum size is 0Storage type is NestedTLV name ERT-VR Data Delivery Service(14/0xE)Maximum size is 0Storage type is NestedTLV name Packet Classification Rule(15/0xF)Maximum size is 0Storage type is NestedTLV name AK Context(16/0x10)Maximum size is 0Storage type is NestedTLV name Base Station ID(20/0x14)Maximum size is 8Storage type is HexadecimalTLV name Reject Cause Code(21/0x15)Maximum size is 4Storage type is Integer - size 4 bytesTLV name AK(22/0x16)Maximum size is 20Storage type is HexadecimalTLV name AK Indentifier(23/0x17)Maximum size is 8Storage type is HexadecimalTLV name AK Life Time(24/0x18)Maximum size is 2Storage type is Integer - size 2 bytesTLV name AK Sequence number(25/0x19)Maximum size is 1Storage type is Integer - size 1 byteTLV name Authentication Result(26/0x1A)Maximum size is 1Storage type is Integer - size 1 byteTLV name Anchor Gateway ID(27/0x1B)Maximum size is 16Storage type is HexadecimalTLV name Authenticator ID(28/0x1C)Maximum size is 16Storage type is HexadecimalTLV name Classifier Action(30/0x1E)Maximum size is 1Storage type is Integer - size 1 byteTLV name Classifier Rule Priority(31/0x1F)Maximum size is 1Storage type is Integer - size 1 byteTLV name DP Identifier(GRE Key)(35/0x23)Maximum size is 4Storage type is Integer - size 4 bytesTLV name Data Path End point Identifier(36/0x24)Maximum size is 4Storage type is HexadecimalTLV name Authorization Policy(40/0x28)Maximum size is 2Storage type is Integer - size 2 bytesTLV name PKMv2 Message Code(42/0x2A)Maximum size is 1Storage type is Integer - size 1 byteTLV name Registration Type(46/0x2E)Maximum size is 4Storage type is Integer - size 4 bytesTLV name QoS Information(48/0x30)Maximum size is 0Storage type is NestedTLV name SDU size(55/0x37)Maximum size is 1Storage type is Integer - size 1 byteTLV name Service Flow Identifier(59/0x3B)Maximum size is 4Storage type is Integer - size 4 bytesTLV name Tolerated jitter(60/0x3C)Maximum size is 4Storage type is Integer - size 4 bytesTLV name Traffic Priority(61/0x3D)Maximum size is 1Storage type is Integer - size 1 byteTLV name Maximum latency(67/0x43)Maximum size is 4Storage type is Integer - size 4 bytesTLV name Maximum sustained traffic rate(68/0x44)Maximum size is 4Storage type is Integer - size 4 bytesTLV name Maximum traffic burst(69/0x45)Maximum size is 4Storage type is Integer - size 4 bytesTLV name Minimum Reserved Traffic Rate(70/0x46)Maximum size is 4Storage type is Integer - size 4 bytesTLV name Media Flow Type(72/0x48)Maximum size is 0Storage type is HexadecimalTLV name IP destination address and mask(73/0x49)Maximum size is 0Storage type is HexadecimalTLV name IP source address and mask(74/0x4A)Maximum size is 0Storage type is HexadecimalTLV name IP TOS/DSCP range and mask(75/0x4B)Maximum size is 3Storage type is HexadecimalTLV name IP Protocol(82/0x52)Maximum size is 0Storage type is HexadecimalTLV name Protocol destination port range(83/0x53)Maximum size is 0Storage type is HexadecimalTLV name EAP Payload(85/0x55)Maximum size is 0Storage type is HexadecimalTLV name Registration Context(88/0x58)Maximum size is 0Storage type is NestedTLV name CMAC Key Count(91/0x5B)Maximum size is 2Storage type is Integer - size 2 bytesTLV name Combined Resources Required(92/0x5C)Maximum size is 2Storage type is Integer - size 2 bytesTLV name Context Purpose Indicator(93/0x5D)Maximum size is 4Storage type is Integer - size 4 bytesTLV name Direction(94/0x5E)Maximum size is 2Storage type is Integer - size 2 bytesTLV name Key Change Indicator(95/0x5F)Maximum size is 1Storage type is Integer - size 1 byteTLV name Protocol source port range(96/0x60)Maximum size is 0Storage type is HexadecimalTLV name Reduced Resources Code(97/0x61)Maximum size is 4Storage type is Integer - size 4 bytesTLV name Request Or Transmission Policy(98/0x62)Maximum size is 4Storage type is Integer - size 4 bytesTLV name Reservation Action(99/0x63)Maximum size is 2Storage type is Integer - size 2 bytesTLV name Reservation Result(101/0x65)Maximum size is 2Storage type is Integer - size 2 bytesTLV name Unsolicited Grant Interval(102/0x66)Maximum size is 2Storage type is Integer - size 2 bytesTLV name Unsolicited Polling Interval(103/0x67)Maximum size is 2Storage type is Integer - size 2 bytesTLV name CS Type(104/0x68)Maximum size is 2Storage type is Integer - size 2 bytesTLV name MTG Profile(105/0x69)Maximum size is 1Storage type is Integer - size 1 byteTLV name Number of Downlink CIDs(106/0x6A)Maximum size is 2Storage type is Integer - size 2 bytesTLV name Number of Uplink CIDs(107/0x6B)Maximum size is 2Storage type is Integer - size 2 bytesTLV name Number of Uplink Classifiers(108/0x6C)Maximum size is 2Storage type is Integer - size 2 bytesshow wimax agw user-group
To display information about user groups configured on the BWG, use the show wimax age user-group command in Privileged EXEC mode.
show wimax age user-group [any | brief | name | unauthenticated]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC.
Command History
12.4(15)XL
This command was introduced.
New CoA counters were added to the show output.
Usage Guidelines
The following information will be displayed for each user-group.
•
•
•
•
•
•
•
•
•
•
If the brief keyword is specified, then the output will contain a list of all the User groups currently connected in column format, as well as the following information
•
•
•
Examples
Here is example output for the show wimax agw user-group command:
router# show wimax agw user-groupAGW User-Group-ListThere are 3 user-groups configured in list wimaxUser group domain name anyService mode operationalSessions 0 associatedTraffic Sent 0 packets, 0 bytesTraffic Received 0 packets, 0 bytesIngress Address filtering 0 packets, 0 bytesUser group domain name ciscoService mode operationalSessions 0 associatedTraffic Sent 0 packets, 0 bytesTraffic Received 0 packets, 0 bytesIngress Address filtering 0 packets, 0 bytesUser group domain name unauthenticatedService mode operationalSessions 0 associatedTraffic Sent 0 packets, 0 bytesTraffic Received 0 packets, 0 bytesIngress Address filtering 0 packets, 0 bytesrouter#show wimax agw user-group brief ?Name Sessions Pkts-Tx Bytes-Tx Pkts-Rx Bytes-Rx VRFany 0 0 0 0 0cisco 0 0 0 0 0unauthenticated 0 0 0 0 0Router#show wimax agw user-group anyUser group domain name anyService mode operationalSessions 0 associatedIP-GRE Traffic Sent 0 packets, 0 bytesIP-GRE Traffic Received 0 packets, 0 bytesEthernet-GRE traffic Sent 0 packets, 0 bytesEthernet-GRE Traffic Received 0 packets, 0 bytesIngress Address filtering 0 packets, 0 bytesIP-GRE Traffic Received redirected 0 packets, 0 bytesEthernet-GRE Traffic Received redirected 0 packets, 0 bytesRouter#show wimax agw user-group anyName Sessions Pkts-Tx Bytes-Tx Pkts-Rx Bytes-Rx VRFany 0 0 0 0 0IP-GRE - 0 0 0 0Eth-GRE - 0 0 0 0wimax.org 0 0 0 0 0IP-GRE - 0 0 0 0Eth-GRE - 0 0 0 0eap-tls.com 0 0 0 0 0IP-GRE - 0 0 0 0Eth-GRE - 0 0 0 0Unauthenticated 2 14166 4659466 14161 8553244IP-GRE - 14000 4650000 161 3244Eth-GRE - 166 9466 14000 8550000Router#show wimax agw statistics arpLast clearing of "show wimax agw statistics arp" counters neverTotal number of ARP requests received 0Total number of ARP reply sent 0Total number of ARP packets dropped 0router#show wimax agw user-group any briefName Sessions Pkts-Tx Bytes-Tx Pkts-Rx Bytes-Rx VRFany 0 0 0 0 0router#show wimax agw user-group name ?WORD Enter User-group Namerouter#show wimax agw user-group name cisco ?brief Brief output| Output modifiers<cr>router#show wimax agw user-group name ciscoUser group domain name cisco--------------------------------------Service mode operationalSessions 0 associatedTraffic Sent 0 packets, 0 bytesTraffic Recevied 0 packets, 0 bytesIngress Address filtering 0 packets, 0 bytesrouter#show wimax agw user-group name cisco brief ?| Output modifiers<cr>router#show wimax agw user-group name cisco briefName Sessions Pkts-Tx Bytes-Tx Pkts-Rx Bytes-Rx VRFcisco 0 0 0 0 0router#show wimax agw user-group unauthenticated ?brief Brief output| Output modifiers<cr>router#show wimax agw user-group unauthenticatedUser group domain name unauthenticated--------------------------------------Service mode operationalSessions 0 associatedTraffic Sent 0 packets, 0 bytesTraffic Recevied 0 packets, 0 bytesIngress Address filtering 0 packets, 0 bytesBWG#sh wimax agw user-group unauthenticated bBWG#sh wimax agw user-group unauthenticated brief ?| Output modifiers<cr>router#show wimax agw user-group unauthenticated briefName Sessions Pkts-Tx Bytes-Tx Pkts-Rx Bytes-Rx VRFunauthenticated 0 0 0 0 0The following example illustrates the new CoA counters in BWG Release 2.0:
SAMI_BWG#sh wim agw user-group unauth | inc CoATotal CoA requests received 0Total CoA success notifications sent 0Total CoA failure notifications sent 0Here is an example that shows new sessions rejected for the user-group by the BWG during maintenance mode:
router#sh wim agw sub user-group name cisco.com brMSID Address Age Flows Hosts Pkts-Tx Pkts-Rx0003.1238.5678 0.0.0.0 000.07.47 1 0 3 30003.123A.5678 11.1.0.5 000.02.32 1 0 2 20003.123B.5678 11.1.0.6 000.02.00 1 0 2 20003.123C.5678 11.1.0.7 000.01.40 1 0 2 20003.123D.5678 11.1.0.8 000.01.40 1 0 2 20003.123E.5678 11.1.0.9 000.01.40 1 0 2 2sla profile-name
To configure the sla profile under a user group under the user group list, and to specify the number of flows that must be used for a session that is opened with this group-list, use the sla profile-name subcommand in user group configuration mode. Use the no form of the command to disable the sla profile.
sla profile-name profile-name
no sla profile-name profile-name
Syntax Description
Defaults
There are no default values.
Command Modes
User group configuration mode.
Command History
Usage Guidelines
This command configures the sla profile under the user group list. The sla profile specifies the number of flows that must be used for a session that is opened with this group-list. The sla profile coming from AAA will override the sla profile configured in user-group, if valid. This can be configured for other user groups as well.
Note
Examples
The following example illustrates the sla profile-name command:
wimax agw user group-list wimaxuser-group anyaaa accounting method-list agwsla profile-name golddhcp server primary 12.1.1.2!user-group domain cisco.comaaa accounting method-list agwsla profile-name goldip static-allowedip route aggregate auto!user-group unauthenticatedaaa accounting method-list agwaaa authentication method-list agwsla profile-name goldip static-alloweduser auto-provisioningproxy realm cisco.com password ciscowaysubscriber redundancy rate
To configure broadband subscriber session redundancy policy for synchronization between high availability (HA) active and standby processors, use the subscriber redundancy command in global configuration mode. To delete the policy, use the no form of this command.
subscriber redundancy [bulk limit cpu percentage delay seconds allow value] [dynamic limit cpu percentage delay seconds allow value] [delay time] [rate sessions time]
no subscriber redundancy
Syntax Description
Command Default
Subscriber redundancy policy applies default values.
Command Modes
Global configuration.
Command History
Usage Guidelines
Cisco IOS HA functionality for broadband protocols and applications allows for stateful switchover (SSO) and in service software upgrade (ISSU) features that minimize planned and unplanned downtime and failures. HA uses the cluster control manager (CCM) to manage the capability to synchronize subscriber session bring up on the standby processor of a redundant processor system. Use the subscriber redundancy bulk command to create and modify redundancy policy used during bulk (startup) synchronization. Use the subscriber redundancy dynamic command to tune subscriber redundancy policies that throttle dynamic synchronization by monitoring CPU usage and sync rates. Use the subscriber redundancy delay command to establish session duration minimums for synchronization and manage dynamic syncing of short duration calls. Use the subscriber redundancy rate command to throttle the number of sessions to be synchronized per period.
Examples
The following example configures 300 sessions to be synchronized per second during bulk and dynamic synchronization:
router(config)# subscriber redundancy rate 300 1timeout authentication
To configure the delay of the attachment response, use the timeout authentication command in user group submode. Use the no version to disable this feature.
timeout authentication 1-20
no timeout authentication 1-20
Syntax Description
1-20
Value in seconds of the timeout authentication response. The range is 1 to 20 seconds. The default value is 4.
Defaults
The default value is 4.
Command Modes
User group configuration sub mode.
Command History
Usage Guidelines
This command is only configurable under the unauthenticated user-group.
By default, the BWG is designed to delay the Attachment Response. The BWG supports this feature only for PAP authenticated users.
Examples
The following example illustrates the use of the timout authentication command:
router(config-gw-ug)#timeout authentication 15
timeout cache-session
To enable the Session Caching feature and to set the cache timeout, use the timeout cache-session command in User Group configuration submode. Use the no form of the command to disable this feature.
timeout cache-session [follow-dhcp-lease | 1-259200]
no timeout cache-session
Syntax Description
Defaults
The default value is the follow-dhcp-lease option.
Command Modes
User group configuration mode.
Command History
Usage Guidelines
The Session_Cache_timeout = MAX (DHCP lease remaining for Dynamic Host [0],
DHCP lease remaining for Dynamic Host [1],
DHCP lease remaining for Dynamic Host [n] )
By default, the session caching feature is enabled with follow-dhcp-lease option, as described above. The detailed show-subscriber command displays the session's CACHED state.
Examples
The following example illustrates the default value of the timeout cache-session command:
router(config-gw-ug)# timeout cache-session follow-dhcp-lease
timeout idle
To specify the idle timeout for a subscriber, use the timeout idle command in user group configuration submode. Use the no form of the command to disable this feature.
timeout idle timeout value [inbound]
Syntax Description
Defaults
There are no default values. The timeout value must be specified in the configuration.
Command Modes
User group configuration mode.
Command History
Usage Guidelines
When configured, the timer starts. If no traffic is seen for the subscriber over the session for specified period of time, then the subscriber is removed by sending a de-registration to the base station. If inbound is configured, the subscriber is assumed to idle if no upstream traffic is seen for the specified period of time. By default, the idle timeout feature is disabled. The idle timeout value can be downloaded from the AAA server as well, and if downloaded the AAA value is given precedence over the configured value.
Examples
The following example illustrates the timeout idle command:
router(config-gw-ug)#timeout idle 15timeout session
To specify the session or absolute timeout value for a subscriber, use the timeout session command in user group configuration submode. Use the no form of the command to delete the timeout session values for a subscriber.
timeout session timeout value
no timeout session
Syntax Description
timeout value
Specifies the timeout session value in seconds. The timeout value range is 1 to 4294967 seconds. There is no default timeout value, it must be specified in the configuration.
Defaults
The session timeout feature is disabled by default. The timeout value range is 1 to 4294967 seconds. There is no default timeout value, it must be specified in the configuration.
Command Modes
User group configuration submode.
Command History
Usage Guidelines
When configured, the session timeout timer is started on the successful authentication of authenticated calls, or when the traffic path is ready for unauthenticated calls. Upon successful reauthentication, the timer is restarted.
Examples
The following example configures a session timeout value of 3600 seconds:
router(config-gw-ug)#timeout session 3600tolerated-jitter
To configure the maximum delay variation (jitter) for the service flow connection, use the tolerated-jitter subcommand in service flow QoS information configuration submode. Use the no form of the command to disable this function.
tolerated-jitter tolerated-jitter-value
no tolerated-jitter tolerated-jitter-value
Syntax Description
tolerated-jitter-value
Specifies the maximum delay variation value for the service flow connection. The range is 0-4294967295 measured in bits per second
Defaults
There are no default values.
Command Modes
Service flow QoS information configuration submode.
Command History
Examples
The following example illustrates the tolerated jitter command:
wimax agw service-flow qos-info profile isf-qos-downlinkdata-delivery-service real-time-variable-ratemaximum-latency 1maximum-traffic-burst 2maximum-traffic-rate-sustained 3media-flow-type 012041424344minimum-traffic-rate-reserved 4policy-transmission-request 5sdu-size 6tolerated-jitter 7traffic-priority 1unsolicited-interval-grant 8unsolicited-interval-polling 9wimax agw service-flow qos-info profile isf-qos-uplinkdata-delivery-service unsolicited-grantmaximum-latency 11maximum-traffic-burst 21maximum-traffic-rate-sustained 31minimum-traffic-rate-reserved 41policy-transmission-request 51sdu-size 61tolerated-jitter 71traffic-priority 3unsolicited-interval-grant 81unsolicited-interval-polling 91!wimax agw service-flow qos-info profile downlink-qos-02data-delivery-service real-time-variable-ratemedia-flow-type 05abcdtraffic-priority
To specify the priority assigned to a service flow, use the traffic-priority subcommand in service flow QoS information configuration submode. Use the no form of the command to disable the command.
traffic-priority traffic-priority-value
no traffic-priority
Syntax Description
traffic-priority-value
Specifies the priority value assigned to a service flow.
The range is 0-7. Higher numbers indicate higher priority. Default value is 0.
Defaults
Default value is 0.
Command Modes
Service flow QoS information configuration submode.
Command History
Usage Guidelines
If two service flows are identical in all QoS parameters except priority, the higher priority service flow is given lower delay, and higher buffering preference. For non-identical service flows, the priority parameter does not take precedence over any conflicting service flow QoS parameter. The specific algorithm for enforcing this parameter is not mandated here.
Examples
The following example sets the service flow priority value to 1 and 3:
wimax agw service-flow qos-info profile isf-qos-downlinkdata-delivery-service real-time-variable-ratemaximum-latency 1maximum-traffic-burst 2maximum-traffic-rate-sustained 3media-flow-type 012041424344minimum-traffic-rate-reserved 4policy-transmission-request 5sdu-size 6tolerated-jitter 7traffic-priority 1unsolicited-interval-grant 8unsolicited-interval-polling 9wimax agw service-flow qos-info profile isf-qos-uplinkdata-delivery-service unsolicited-grantmaximum-latency 11maximum-traffic-burst 21maximum-traffic-rate-sustained 31minimum-traffic-rate-reserved 41policy-transmission-request 51sdu-size 61tolerated-jitter 71traffic-priority 3unsolicited-interval-grant 81unsolicited-interval-polling 91!wimax agw service-flow qos-info profile downlink-qos-02data-delivery-service real-time-variable-ratemedia-flow-type 05abcdunsolicited-interval-grant
To specifies the nominal interval between successive data grant opportunities for this service flow, use the unsolicited-interval-grant command in service flow QoS information configuration submode. Use the no form of the command to disable this feature.
unsolicited-interval-grant unsolicited-interval-grant-value
no unsolicited-interval-grant
Syntax Description
Defaults
No default behavior or values.
Command Modes
Service flow QoS information configuration submode.
Command History
Examples
The following example illustrates the use of the unsolicited-interval-grant command:
wimax agw service-flow qos-info profile isf-qos-downlinkdata-delivery-service real-time-variable-ratemaximum-latency 1maximum-traffic-burst 2maximum-traffic-rate-sustained 3media-flow-type 012041424344minimum-traffic-rate-reserved 4policy-transmission-request 5sdu-size 6tolerated-jitter 7traffic-priority 1unsolicited-interval-grant 8unsolicited-interval-polling 9wimax agw service-flow qos-info profile isf-qos-uplinkdata-delivery-service unsolicited-grantmaximum-latency 11maximum-traffic-burst 21maximum-traffic-rate-sustained 31minimum-traffic-rate-reserved 41policy-transmission-request 51sdu-size 61tolerated-jitter 71traffic-priority 3unsolicited-interval-grant 81unsolicited-interval-polling 91!wimax agw service-flow qos-info profile downlink-qos-02data-delivery-service real-time-variable-ratemedia-flow-type 05abcdunsolicited-interval-polling
To specify the maximal nominal interval between successive polling grant opportunities for a service flow, use the unsolicited-interval-polling command in service flow QoS information configuration submode.
unsolicited-interval-polling unsolicited-interval-polling-value
Syntax Description
unsolicited-interval- polling-value
Specifies the maximal nominal interval between successive polling grant opportunities for a service flow.
The range is 0-65535 measured in milliseconds.
Defaults
There are no default values.
Command Modes
Service flow QoS information configuration submode.
Command History
Examples
The following is sample output for the unsolicited-interval-polling command:
wimax agw service-flow qos-info profile isf-qos-downlinkdata-delivery-service real-time-variable-ratemaximum-latency 1maximum-traffic-burst 2maximum-traffic-rate-sustained 3media-flow-type 012041424344minimum-traffic-rate-reserved 4policy-transmission-request 5sdu-size 6tolerated-jitter 7traffic-priority 1unsolicited-interval-grant 8unsolicited-interval-polling 9wimax agw service-flow qos-info profile isf-qos-uplinkdata-delivery-service unsolicited-grantmaximum-latency 11maximum-traffic-burst 21maximum-traffic-rate-sustained 31minimum-traffic-rate-reserved 41policy-transmission-request 51sdu-size 61tolerated-jitter 71traffic-priority 3unsolicited-interval-grant 81unsolicited-interval-polling 91!wimax agw service-flow qos-info profile downlink-qos-02data-delivery-service real-time-variable-ratemedia-flow-type 05abcduser auto provisioning
To instruct the BWG to allow a user entry even after receiving an Access-Reject from the RADIUS server, use the user auto provisioning command in user configuration mode. Use the no form of the command to disable user auto provisioning.
user auto provisioning
no user auto provisioning
Syntax Description
There are no keywords or arguments.
Defaults
There are no default values.
Command Modes
User group configuration submode.
Command History
Usage Guidelines
If this command is not configured, users will not be allowed to enter.
This command can be configured for other user groups, but configuring it for a user group other that unauthenticated does not enable this feature for those user groups.
Examples
The following example illustrates how to configure unauthenticated users:
user-group unauthenticatedaaa accounting method-list agwaaa authentication method-list agwsla profile-name goldip static-alloweduser auto-provisioningproxy realm cisco.com password ciscowayuser-group (user group list configuration submode)
To configure a user group under the user group list, use the user-group subcommand in user group list configuration submode.
user-group {any | unauthenticated | domain domain-name}
no user-group {any | unauthenticated | domain domain-name}
Syntax Description
Defaults
There are no default values.
Command Modes
User group list configuration submode.
Command History
Usage Guidelines
Release 1.0 of the Cisco BWG supports the user-groups any and unauthenticated.
Examples
The following example illustrates how to configure unauthenticated users:
Router(config-gw-ugl)#user-group unauthenticatedvlan (service flow direction cs-type submode)
To specify the vlan to vrf mapping (frames with a particular vlan-id will be mapped to what vrf-name), use the vlan command in service flow direction cs-type submode. Use the no form of the command to disable vrf mapping.
vlan {2-4095 | range 2-4095 2-4095} vrf vrf-name
no vlan
Syntax Description
range 2-4095 2-4095
(Optional) Specifies the range of vlan-ids mapped to a vrf-name.
vrf vrf-name
Specifies the vrf name.
Defaults
There are no default values.
Command Modes
Service flow direction cs-type configuration submode.
Command History
Usage Guidelines
Note
Examples
The following example illustrates how to configure the vlan command:
router(config-gw-sf-dir-cstype)# direction uplinkcs-type ip-cspak-classify-rule isf-classifier-uplinkprecedence 1cs-type ethernet-cspak-classify-rule isf-classifier-uplinkprecedence 2vlan 2 vrf vrf_1vlan range 3 10 vrf vrf_2vrf-default vrf_1qos-info isf-qos-uplinkvrf (user group configuration submode)
To configure the VRF, use the vrf command in user group configuration submode. Use the no form of the command to delete the VRF.
vrf vrf-name
no vrf vrf-name
Syntax Description
Defaults
By default, no user groups belong to any VRF.
Command Modes
User group configuration submode.
Command History
Usage Guidelines
Multiple user groups can share the VRF.
Examples
The following example illustrates how to configure a vrf named "cisco":
Router(config-gw-ug)#vrf ciscovrf-default
To specify the default vrf mapping, use the vrf-default command in service flow direction cs-type submode. Use the no form of the command to disable vrf mapping.
vrf-default vrf-name
no vrf-default
Syntax Description
Defaults
There are no default values.
Command Modes
Service flow direction cs-type submode configuration submode.
Command History
Usage Guidelines
This is an optional configuration command that specifies the default vrf mapping. Uplink frames without a vlan-id, or with a vlan-id that is not configured under this cs-type with a vlan-vrf mapping will be mapped to the vrf-name configured using the above CLI.
Note
Examples
The following example illustrates how to configure the vrf-default command:
router(config-gw-sf-dir-cstype)# direction uplinkcs-type ip-cspak-classify-rule isf-classifier-uplinkprecedence 1cs-type ethernet-cspak-classify-rule isf-classifier-uplinkprecedence 2vlan 2 vrf vrf_1vlan range 3 10 vrf vrf_2vrf-default vrf_1qos-info isf-qos-uplinkwimax agw
To configure various subcommand modes, use the wimax agw global configuration command.
wimax agw [base-station | idlemode [entry-timout sec | update-timout sec] | maximum | paging-controller word | paging-group | pmip | redundancy | service-flow | sla | slb | user]
Syntax Description
Defaults
The entry-timout default value is 10 seconds, the update-timout default value is 4096 seconds.
Command Modes
Global configuration.
Command History
Usage Guidelines
This CLI is only necessary on a SAMI platform that is using SLB for load balancing. This CLI should not be configured for 7301 platform. This CLI can only be configured if one of the interfaces on the gateway is configured for GLBP because a valid GLBP group-name is input to this CLI. If this CLI is configured on the Cisco 7301, then (by default) GLBP is also configured on one of the interfaces and the entire feature is supported on 7301 platform as well.
wimax agw base-station group
To configure a base-station group, and to ensure that all of the individual base stations configured to belong to this base station group will use the base station group parameters, use the wimax agw base-station group command in global configuration mode. This command also places you in base station configuration submode. Use the no form of the command to delete a base station group.
wimax agw base-station group name
Syntax Description
Defaults
The default behavior is that there are no base station groups.
Command Modes
Global configuration.
Command History
Examples
The following example creates a base station group named "cisco":
router(config)#wimax agw base-station group ciscowimax agw hotline profile
To configure a hotline profile on the BWG, and to enter the GW hotline configuration sub mode, use the wimax agw hotline profile global configuration command. Use the no form of the command to remove the profile.
wimax agw hotline profile profile-name [ip access-group num in | out passthru] [http access-group num redir-url url]
no wimax agw hotline profile
Syntax Description
Defaults
There are no default values.
Command Modes
Global configuration.
Command History
Usage Guidelines
A subscriber can be hot-lined at the start of their packet data service or mid-session with AAA-based CoA. The AAA Access Accept is used to hot-line the user's session at the session startup time. If the session receives a AAA CoA with the hot-lining status on in the middle of the session, the user's data traffic will be re-directed. Similarly the hot-lining status can be removed during mid-session, or at the start of a new session. Hotline profile is selected based on the hotline profile received from the AAA. To disable hot-lining, the AAA server can choose a special profile name called "hotlining-exit" (case insensitive).
Similar to SLA profile, the AAA server simply selects a hotline profile. To disable hot-lining, the AAA server can choose a special profile name called "hotlining-exit" (case insensitive). Once it receives this special profile name, the BWG resumes normal traffic for the subscriber. In order to avoid confusion, this special profile name should not be used as a normal hotline profile name.
Examples
Here is an example of the wimax agw hotline profile command:
BWG#sh run | inc hotlinewimax agw hotline profile XYZip access-group 101 in passthruhttp access-group 102 redir-url www.hotlined.comip access-group 101 out passthruwimax agw pmip profile
To configure a PMIP profile on the BWG, and to enter the GW PMIP configuration sub mode, use the wimax agw pmip profile global configuration command. Use the no form of the command to remove the profile.
wimax agw pmip profile pmip-profile-name
no wimax agw pmip profile pmip-profile-name
Syntax Description
Defaults
There are no default values.
Command Modes
Global configuration.
Command History
Usage Guidelines
The PMIP profile includes all the PMIP attributes used for establishing a PMIP call. You can associate a PMIP profile with a user-group by configuring subcommand pmip profile profile name.
PMIP attributes can be provisioned from AAA and overwrite the user-group PMIP profile defined attributes. You need to define a PMIP profile in the user-group to enable PMIP, or you can enable PMIP by getting the attributes from AAA.
Examples
Here is an example of the wimax agw pmip profile command:
wimax agw pmip profile pmip1home-agentaddress 14.1.1.80ha-rk-key ascii rootcisco spi decimal 258 lifetime 6000proxy-mngre-tunneling-enableno host-config-ext-requestmn-ha-key ascii cisco spi 102 lifetime 3000coa-address 14.1.1.100wimax agw r6 maximum base-station
To specify the maximum number of base stations that are allowed to connect to the AGW, use the wimax agw r6 maximum base-station command in global configuration mode. Use the no form of the command to disable this feature.
wimax agw r6 maximum base-station number
no wimax agw r6 maximum base-station
Syntax Description
Defaults
The maximum number of base stations that are supported on the BWG platform is 500.
Command Modes
Global configuration.
Command History
Usage Guidelines
If you do not configure this command, the number of base stations allowed to connect to the BWG is set to the maximum number supported by the platform.
Examples
The following example allows 240 base stations to connect to the BWG:
wimax agw r6 maximum base-station 240wimax agw r6 maximum subscriber
To specify the maximum number of subscriber sessions allowed on the BWG, use the wimax agw r6 maximum subscriber command in global configuration mode. Use the no form of the command to disable this feature.
wimax agw r6 maximum subscriber number
no wimax agw r6 maximum subscriber number
Syntax Description
Defaults
The default maximum number of subscriber sessions is 20000
Command Modes
Global configuration.
Command History
Usage Guidelines
If you do not configure this command, the number of subscriber sessions supported on the BWG platform is set to its maximum value.
Examples
The following example limits the number of subscriber sessions on the BWG to 50:
Router(config)#wimax agw r6 maximum subscriber 50wimax agw redundancy
To enable session redundancy on the BWG, use the wimax agw redundancy command in global configuration mode. Use the no form of the command to disable this feature. You must clear all subscribers to configure the no form of the command.
wimax agw redundancy
no wimax agw redundancy
Syntax Description
There are no keywords or arguments.
Defaults
This command is disabled by default.
Command Modes
Global configuration.
Command History
Usage Guidelines
You must clear all subscribers to configure no wimax agw redundancy. Here is an example:
AGW-2(config)#no wimax agw redundancyERROR: Clear all subscribers (1) before unconfig. redundancyAGW-2(config)#Examples
The following example enables session redundancy on the BWG:
Router(config)# wimax agw redundancywimax agw service-flow pak-classify-rule profile
To configure a service-flow packet classification rule profile on the BWG, or to enter the service flow packet classify configuration submode, use the wimax agw service-flow pak-classify-rule profile global configuration command. Use the no form of the command to remove the profile, or exit the submode.
wimax agw service-flow pak-classify-rule profile profile-name
no wimax agw service-flow pak-classify-rule profile
Syntax Description
profile- name
Specifies the name of the service-flow packet classification rule profile on the BWG. The profile name is case insensitive.
Defaults
There are no default values.
Command Modes
Global configuration.
Command History
Usage Guidelines
These profiles are configured under the convergence sub layer type (cs-type) in predefined service flows that are to be opened for the subscriber.
Examples
Here is an example of a pre-defined service flow classifier rule profile
wimax agw service-flow pak-classify-rule profile profile_namepriority numberipv4 --> same as beforeethernet permit src_mac | any src_mac_mask | all dst_mac | any dst_mac_mask | all ethernet_typevlan permit number | any priority number | any | range number start number endwimax agw service-flow profile
To configure a service-flow profile on the BWG, and to enter the GW service flow profile configuration submode, use the wimax agw service-flow profile command in global configuration mode. Use the no form of the command to disable this feature and remove the profile.
wimax agw service-flow profile service-flow-profile-name
no wimax agw service-flow profile service-flow-profile-name
Syntax Description
service-flow-profile- name
Specifies the name of the service flow profile. The profile name is case insensitive.
Defaults
There are no default values.
Command Modes
Global configuration.
Command History
Usage Guidelines
These service flows are predefined and are opened for the subscriber.
Configuring the command will open the GW service flow profile configuration submode.
The precedence is used as a tie-breaker when an MS can support more than one CS Type (for example, IPCS and EthCS and VLAN CS). In these scenarios, the BWG selects the CS-type based on precedence.
As an example, consider that the MS sends the CS capability in the attachment request with a bit map set to indicate it only supports eth-cs, and the precedence of the eth-cs in the BWG is 2. Then the BWG would pick CS-type of Ethernet CS. However, if the MS supports both, and the BWG configuration has ip-cs with a precedence set to 1, then the BWG would pick CS-type of IP-CS.
Examples
The following example illustrates a configuration with a predefined service flow profile named "cisco2":
router(config)wimax agw service-flow pak-classify-rule profile cisco 2direction uplinkcs-type ip-cs|ethernet-csprecedence 1/2/pak-classify-rule classifier_profilevlan range 2-4095 2-4095 vrf vrf_namedefault-vrf vrf_nameqos-info-profile namedirection downlink>cs-type ip-cs/ethernet-csprecedence 1/2pak-classify-rule classifier_profileqos-info-profile namewimax agw service-flow profile qos-info
To configure a service-flow QoS information profile on the BWG, or to enter service flow qos info configuration submode, use the wimax agw service-flow profile qos-info command in global configuration mode. Use the no form of the command to remove the profile.
wimax agw service-flow profile qos-info service-flow-qos-info-profile-name
no wimax agw service-flow profile qos-info service-flow-qos-info-profile-name
Syntax Description
Defaults
There are no default values.
Command Modes
Global configuration.
Command History
Usage Guidelines
You can configure a service-flow QoS information profile on the BWG that is associated to predefined service flows that are opened for the subscriber.
Examples
The following example specifies the service flow profile name as "upstreamprofile":
Router(config)#wimax agw service-flow profile qos-info upstreamprofilewimax agw sla profile
To configure the Service level agreement (SLA) on the BWG, and to enter GW SLA configuration sub mode, use the wimax agw sla profile command in global configuration mode. Use the no form of the command to remove the profile.
wimax agw sla profile sla-profile-name
no wimax agw sla profile sla-profile-name
Syntax Description
Defaults
There are no default values.
Command Modes
Global configuration.
Command History
Usage Guidelines
The SLA profile includes all the flows. The BWG will enforce a limit for the number of service flows to 4 for each SLA profile. Attempting to exceed the limit will result in a failure.
For Cisco BWG Release 1.1, the same vlan should be configured in the same SLA profile.
Different service flows get listed under one SLA profile. You can associate an SLA with a user-group by configuring subcommand sla profile profile name. Provisioning the SLA allows you to better manage the service flows.
If not configured, there is no other provision to define flows:
wimax agw sla profile silverservice-flow pre-defined isf profile isfservice-flow pre-defined secondary 1 profile sec1This command moves the ability to configure the service flow commands from the user-group.
You need to configure this sla profile in the user-group, to define how many flows will be allowed for that user-group.
Examples
The following example specifies the service flow profile name as "upstreamprofile":
Router(config)#wimax agw sla profile goldservice-flow pre-defined isf profile isf encap-type none vlan 10service-flow pre-defined secondary profile sec1 encap-type none vlan 10wimax agw slb notify
To enable the BWG to send notification to the SLB, use the wimax agw slb notify global configuration command. Use the no form to disable this feature.
wimax agw slb notify {update | delete}
no wimax agw slb notify {update | delete}
Syntax Description
update
Enables sending of update notification to SLB.
delete
Enables sending of delete notification to SLB.
Defaults
There are no default values.
Command Modes
Global configuration.
Command History
Examples
Here is an example of the wimax agw slb notify command:
router(config)# wimax agw slb notify deletewimax agw slb port
To use the wimax agw slb port global configuration command. Use the no form to disable this function.
wimax agw slb port port vserver vserver [next-hop ip ip_addr vrf vrf_name]
no wimax agw slb port port vserver vserver [next-hop ip ip_addr vrf vrf_name]
Syntax Description
port
Specifies the port number. The range is 49152-65535.
vserver vserver
Specifies the vserver.
next-hop ip ip_addr
Specifies the next hop address.
vrf vrf_name
Specifies the vrf.
Defaults
There are no default values.
Command Modes
Global configuration.
Command History
Usage Guidelines
For session deletion/update notification, this command is required . Both, next-hop ip ip address and vrf vrf name, are optional. In the absence of next-hop ip address, you will have to input a static route to reach the virtual server.
wimax agw user group-list
To configure the User group list on the BWG, and to enter user group list configuration subcommand mode, use the wimax agw user group-list command in global configuration mode. Use the no form of the command to remove the user group lists, or to exit user group list configuration subcommand mode.
wimax agw user group-list user-group-list-name
no wimax agw user group-list user-group-list-name
Syntax Description
Defaults
The default behavior is that there are no configured user group lists.
Command Modes
Global configuration.
Command History
Usage Guidelines
There can be only one user group list allowed on a single processor of the BWG.
The no version of command will remove the user group list. This will create a user group list sub configuration mode to create multiple user groups under the user-group list created.
The aaa authentication method-list xxxx in the example below indicates if the RADIUS Access Request is initiated from the BWG for the group. If the CLI is not configured, the AAA query is not required.
The proxy realm sprint.com password ciscoway instructs the BWG how to populate the RADIUS Access Request message. If configured, the user name is constructed as mac@realm (for example, mac@sprint.com). If the realm is not configured, the user name is simply mac. The cisco argument is used as passwd if not configured. These two CLIs are applicable for other user groups (EAP users) as well. The reply from the AAA server contains the user's real domain name, which is used for selecting a local user group. It should also be noted that the above scheme should not break EAP-authenticated users. In other words, the BWG should allow EAP and non-EAP authenticated users to coexist. For authenticated users, the user name is acquired from CPE through the EAP identity request. EAP uses NAI in Access request to the AAA. If the response from the AAA includes the SLA Profile Name and the User Domain Name for EAP users, the result from the AAA will override those determined earlier.
Examples
The following example configures a user group list named "cisco":
Router(config)#wimax agw user group-list ciscoThe wimax agw user group-list command supports route aggregate at per user-group level. The following example shows how to configure route aggregation:
AGW-1(config)#wimax agw user group-list wimaxAGW-1(config-gw-ugl)#user-group unauthenticatedAGW-1(config-gw-ug)#?GW user group sub configuration commandsaaa User group AAA configuration commandsdefault Set a command to its defaultsdhcp User group DHCP configuration commandsexit Exit user group sub configurationip User group IP configuration commandsno Negate a command or set its defaultssecurity User group security configuration commandsservice-flow User group service-flow configuration commandstimeout User group timeout configuration commandsvrf User group VRF configuration commandsproxy Proxy to enter realm and passwordsla User group service level agreement configuration commandsuser Allow user-autoprovisioningAGW-1(config-gw-ug)#ipAGW-1(config-gw-ug)#ip ?access-group Specify access control for packetsaddress User group address configuration commandsroute User group route confiugration commandsAGW-1(config-gw-ug)#ip rouAGW-1(config-gw-ug)#ip route ?aggregate Configure aggregate rangeAGW-1(config-gw-ug)#ip routeAGW-1(config-gw-ug)#ip route aggregate ?A.B.C.D {/nn || A.B.C.D} IP prefix and prefix maskauto will aggregate routes automatically base on themask return by serversAGW-1(config-gw-ug)#ip route aggregate autoAGW-1(config-gw-ug)#For un-authenticated users, we do not get the user name from the CPE. In this case, the user name, realm and password are based on the following CLI.
!wimax agw user group-list wimaxuser-group unauthenticatedaaa authentication method-list xxxxproxy realm sprint.com passwd ciscowaysla profile-name silver!User Auto-Provisioning
There are occasions when users may be admitted into the network for a short while even if AAA does not have provisioning for them. To enable this feature, the related user group should be properly configured. When it is enabled, the session timer in the user group should be configured to a small value so that free use of the network is limited.
Auto-provisioning is not supported for EAP users. It will not take effect when configured with any user group other than the unauthenticated.
Auto-provision in not supported for hosts with static IP and IPCS.
!wimax agw user group-list wimaxuser-group unauthenticatedaaa accounting method-list agwsla profile-name silveruser auto-provisioningtimeout session 600!!
FeedbackContact Cisco
- Open a Support Case
- (Requires a Cisco Service Contract)