Tethering Detection Databases; Loading And Upgrading Tethering Detection Databases; Session Recovery Support; Time-Of-Day Activation/Deactivation Of Rules - Cisco ASR 5000 Series Administration Manual

Enhanced Charging Service Overview

Tethering Detection Databases

The Tethering Detection database files must be populated and loaded on to the ASR chassis by the administrator. The
procedure to load the database is the same for all the different databases.
Before the database(s) can be loaded for the first time, tethering detection must be enabled using the
CLI command in the ACS Configuration Mode.
database
For all the databases, only a full upgrade of a database file is supported. Incremental upgrade is not supported. If, for
any particular database, the upgrade procedure fails, the system will revert back to the previous working version of that
database.
In 15.0 and later releases, os-signatures can be collected from TCP SYN even when tethering detection is disabled in the
rulebase. The os-signature will be parsed if an EDR/UDR with an os-signature variable is present in a rulebase or
charging-action in the rulebase. This can be used to collect os-signatures that can then be used to build an OS database
for the tethering detection feature.

Loading and Upgrading Tethering Detection Databases

This section provides an overview of loading and upgrading the databases used in tethering detection.
The database files from MUR must be copied onto the ASR chassis to the following directory path designated for
storing the database files:
/hd-raid/databases/
Any further upgrades to the database files can be done by placing the file named
directory path. ACS auto-detects the presence of files available for upgrade daily. When a new version of a file is found,
the upgrade process is triggered. The upgrade can also be forced by running the upgrade command in the CLI. On a
successful upgrade this file is renamed to

Session Recovery Support

The following Session Recovery features are supported:
 Database recovery after SessCtrl getting killed.
 Database recovery after one or more SessMgrs getting killed.
Note that depending on the size of the database files and the number of SessMgrs operational in the system, it may take
sometime (ranging from five seconds to five minutes) for the database to become available in all the SessMgrs post
recovery/migration.

Time-of-Day Activation/Deactivation of Rules

Within a rulebase, ruledefs/groups-of-ruledefs are assigned priorities. When packets start arriving, as per the priority
order, every ruledef/group-of-ruledefs in the rulebase is eligible for matching regardless of the packet arrival time. By
default, the ruledefs/groups-of-ruledefs are active all the time.
The Time-of-Day Activation/Deactivation of Rules feature uses time definitions (timedefs) to activate/deactivate static
ruledefs/groups-of-ruledefs such that they are available for rule matching only when they are active.
Important:
filename
The time considered for timedef matching is the system's local time.
.
Cisco ASR 5x00 Enhanced Charging Services Administration Guide ▄
Enhanced Features and Functionality ▀
tethering-
in the designated
new-filename
47