Cisco Cisco Packet Data Interworking Function (PDIF)
Bulk Statistics Configuration Mode Commands
hnbgw-rua-access-hybrid schema ▀
Command Line Interface Reference, StarOS Release 16 ▄
1737
hnbgw-rua-access-hybrid schema
Configures bulk statistics schema for RANAP User Adaptation (RUA) protocol message statistics collection in HNB-
GW session instance in hybrid access mode.
GW session instance in hybrid access mode.
Product
HNB-GW
Privilege
Security Administrator, Administrator
Mode
Exec > Global Configuration > Bulk Statistics Configuration
configure > bulkstats mode
Entering the above command sequence results in the following prompt:
[local]host_name(config-bulkstats)#
Syntax
hnbgw-rua-access-hybrid schema schema_name format schema_format
no hnbgw-rua-access-hyrbid schema schema_name
no
Removes the configured HNB-GW-RUA-ACCESS-HYBRID schema.
schema_name
Specifies a name for the HNB-GW-RUA-ACCESS-HYBRID schema.
schema_name
must be an alphanumeric string of 1 through 31 characters.
format
schema_format
Specifies the schema’s format.
schema_format
must be an alphanumeric string of 1 through “1021 minus “number of characters in rest of
the command, including spaces”” characters. For more information, see the
section.
For information on the schema format’s syntax, see the
For information on the schema format’s syntax, see the
Important:
For a complete list of the statistics that are supported for this schema, refer to the Statistics and
Counters Reference.
Usage
This command defines schemas used for RUA protocol messaging statistics collection in hyrbid access mode.
Multiple HNB-GW-RUA-ACCESS-HYBRID schemas can be created to further categorize bulk statistics. All
of the schemas are processed at each collection interval. To create multiple schemas, re-issue the
Multiple HNB-GW-RUA-ACCESS-HYBRID schemas can be created to further categorize bulk statistics. All
of the schemas are processed at each collection interval. To create multiple schemas, re-issue the
hnbgw-
rua-access-hyrbid schema
schema_name
command using a different schema name.
Example