Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

...

Code Block
languagenone
% set profiles services dblProfile <DBL Profile name>
	rule <rule name> 
		action <blacklist | watch> 
		actionEffectivePeriod <60-86400 seconds> 
		event <badSipMessage | epCacAggrReject | sipRegistrationFailure> 
		eventPerDayThreshold <0-86400> 
		state <disabled | enabled> 
	state <disabled | enabled> 
	type <sip> 

Command Parameters

The DBLProfile DBL Profile parameters are as showndescribed in the table below:

Caption
0Table
1 DBLProfile DBL Profile parameters

Parameter

Length/Range

Description

dblProfile

1-23

The administrative name of the DBL profile.

rule

N/A

Specifies the DBL rule name within a DBL profile.
Additional parameters are shown below:

  • action – The action to take when a specified event meets the criteria:
    • blacklist
    • watch
  • actionEffectivePeriod – The DBL action enforcement period (in seconds) the DBL policer entry remains effective. (range: 60-86400 / default = 60)
  • event – The type of event to either watch for or blacklist for this DBL rule.
    • badSipMessage – Bad SIP message.
    • epCacAggrReject
    • sipRegistrationFailure
 Each of the above events include two additional arguments:
    • (Endpoint CAC aggregate rejection) –
    • sipRegistrationFailure – SIP Registration failure.
  • eventPerDayThreshold
  • number
  • Number of events per day used as
  • fillrate
  • fill rate of token bucket policer (value: 0-86400, default = 0)
  • eventPerDayThreshold – The number of events per day which is used as fillrate of token bucket policer. (range: 0-86400 / default = 0)
  • state – The administrative state of this rule.
    • disabled (default)
    • enabled
Note

Dynamic Blacklist for event epCacAggrReject is supported for callRate only.


state

N/A

The administrative state of the DBL profile.

  • disabled (default)
  • enabled

type

N/Asip

The type of application being monitored ( automatically defaults to "sip" is the only choice).

Command Examples

The following example sets DBL profile named "DBP-1" with a rule (named "RULE-1) to watch SIP endpoints every 60 seconds for a bad SIP message. If the number of events per day to be used as a token bucket policer fillrate fill rate is 13.

Code Block
languagenone
% set profiles services dblProfile DBP-1 rule RULE-1 action 
	watch actionEffectivePeriod 60 event badSipMessage 
	eventPerDayThreshold 13 state enabled 
 
% show profiles services dblProfile DBP-1 
	rule RULE-1 { 
		state enabled; 
		event badSipMessage; 
		action watch; 
		eventPerDayThreshold 13; 
		actionEffectivePeriod 60;