Cisco Bug: CSCuq97911 - Smoke2:For Local policy based RB change, RB change not hapenning
Last Modified
Jan 30, 2017
Products (1)
- Cisco ASR 5000 Series
Known Affected Releases
17.1.0.57497 18.0.B0.56863
Description (partial)
Symptom: Local-policy based rulebase change is being triggered for service-flow condition.Due to this no rulebase change happens when configured condition is hit. local-policy-service local-policy ruledef apn-match condition priority 1 apn match .* #exit ruledef temp condition priority 1 apn match .* #exit actiondef disable-dfa-session action priority 1 deactivate-rulebase name consumer-dfa-active action priority 2 activate-rulebase name consumer #exit actiondef enable-dfa-session action priority 1 allow-requested-qos action priority 2 activate-flow-detection initiation ruledef http-200-OK #exit eventbase default rule priority 1 event new-call ruledef apn-match actiondef enable-dfa-session continue rule priority 2 event service-flow ruledef temp actiondef disable-dfa-session <<<<<<<<<<< #exit #exit Conditions: This issue occurs when we have service-flow condition configured in local-policy. In following config there are 2 events new-call and service-flow New-call event is triggered and then upon receiving http 200-ok response from IMS the service-flow should trigger and corresponding actiondef enable-dfa-session should be executed. local-policy-service local-policy ruledef apn-match condition priority 1 apn match .* #exit ruledef temp condition priority 1 apn match .* #exit actiondef disable-dfa-session action priority 1 deactivate-rulebase name consumer-dfa-active action priority 2 activate-rulebase name consumer #exit actiondef enable-dfa-session action priority 1 allow-requested-qos action priority 2 activate-flow-detection initiation ruledef http-200-OK #exit eventbase default rule priority 1 event new-call ruledef apn-match actiondef enable-dfa-session continue rule priority 2 event service-flow ruledef temp actiondef disable-dfa-session #exit #exit
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Status
- Severity
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases