Cisco Cisco ASR 5000 技術マニュアル
failure−handling { initial−request | terminate−request | update−request } { continue
[ go−offline−after−tx−expiry | retry−after−tx−expiry ] | retry−and−terminate,
[ retry−after−tx−expiry ] | terminate }
The first section specifies the request type: Initial (CCR−I), Update (CCR−U), and Terminate (CCR−T).
The second section specifies the action that should be performed when the FH mechanism is activated. These
three actions are possible with the FH mechanism:
three actions are possible with the FH mechanism:
Continue This allows the session to continue and converts it to offline. This function uses two
options that are related to Tx−expiry:
options that are related to Tx−expiry:
Go−offline−after−tx−expiry This starts offline charging after the Tx−expiry occurs.
♦
Retry−after−tx−expiry This retries the secondary server after the Tx−expiry occurs.
♦
•
Retry−and−terminate This terminates the session after the system retries the secondary server, if the
secondary server is not available either. This also uses the Retry−after−tx−expiry option, which
retries the secondary server after the Tx−expiry occurs.
secondary server is not available either. This also uses the Retry−after−tx−expiry option, which
retries the secondary server after the Tx−expiry occurs.
•
Terminate This terminates the session without any attempts to contact the secondary server.
•
FH Mechanism Default Behavior
This section describes the FH default behavior when no configuration is present. By default, the FH
mechanism is activated during a Response Timeout (RT), except when the Terminate action is configured.
mechanism is activated during a Response Timeout (RT), except when the Terminate action is configured.
If a Credit−Control−Failure−Handling Attribute Value Pair (AVP) is received from the server, then the
received settings are applied.
received settings are applied.
Here are some examples:
Initial−Request > Terminate
•
Update−Request > Retry−and−Terminate
•
Terminate−Request > Retry−and−Terminate
•
FH Mechanism Detailed Call Flow
This section describes the detailed call flow of the FH mechanism with all possible options.
Initial−Request
CCFH Setting
CLI Command
Behavior
at Tx
Behavior
at RT
Secondary is
Up
Secondary is Down
Continue
initial−request
continue
continue
N/A
Continue
Secondary
takes over
after
RT
takes over
after
RT
Offline after another RT.
No more quota requests are
performed
for any rating group within
the session
after DCCA failure (even if
connectivity to DCCA is
restored)
No more quota requests are
performed
for any rating group within
the session
after DCCA failure (even if
connectivity to DCCA is
restored)