cancel
Showing results for 
Search instead for 
Did you mean: 

B3 f/w 6.61.07.0010 with "Could not attach the Policy" Error when configuring DiffServ

B3 f/w 6.61.07.0010 with "Could not attach the Policy" Error when configuring DiffServ

FAQ_User
Extreme Employee
Article ID: 14864

Products
B3-Series; firmware 6.61.07.0010, 6.61.08.0013

Changes
Configuring Diffserv (5848) to perform a class match to an IP-related parameter.

Symptoms
Unable to add the Diffserv service to any ports.
The 'set diffserv service add...' command fails, with error message "Could not attach the policy".
A "code No resources for operation" error appears in syslog ('show logging buffer'); for example:<163>Dec 15 20:50:33 10.30.2.2-1 UPN[117221976]: broad_policy.c(1573) 509 %%
Error creating port policy 20 for unit 2,port 4, code No resources
for operationHere are two examples of such a configuration: set diffserv adminmode enable
set diffserv class create all classDstip
set diffserv class match dstip classDstip 1.2.3.4 255.255.255.255
set diffserv policy create policyDstip in
set diffserv policy class add policyDstip classDstip
set diffserv policy mark ipdscp policyDstip classDstip ef
set diffserv service add in ge.2.1 policyDstip

set diffserv adminmode enable
set diffserv class create all classVoice
set diffserv class match iptos classVoice b8 ff
set diffserv policy create policyPhones in
set diffserv policy class add policyPhones classVoice
set diffserv policy mark ipdscp policyPhones classVoice ef
set diffserv service add in ge.1.1-48 policyPhonesCause
There is a conflict between Diffserv and the possibility of configuring for IPv6, as this would use the same hardware resources.
This Diffserv issue is similar to the Policy issue outlined in 14999.

Solution
Upgrade to firmware 6.61.09.0012 or higher.
Release notes state, in the 'Changes and Enhancements in 6.61.09.0012' section:
code:
17514
code:
Corrected an issue that prevented DiffServ application policies from being applied to hardware. Previously a "set diffserv service add" command resulted in the message, "Could not attach the Policy".


The system now allows the actual configuration of either Diffserv or IPv6 but not both, with either of these error messages possible:
code:
Error, access list ipv6mode is enabled.

code:
Diffserv is already configured on the device, please clear Diffserv to configure ipv6mode.
0 REPLIES 0
GTM-P2G8KFN