[Devmon] Template qos and CHAIN

[Audry, O. <Oli...@co...>]

hello

I'm very happy to use the CHAIN key word for cisco qos template.

I'm trying to improve the template to show the interface name and the
traffic way (in/out).

I add the following :

oids 
cbQosCMName		: .1.3.6.1.4.1.9.9.166.1.7.1.1.1	: branch
cbQosConfigIndex	: .1.3.6.1.4.1.9.9.166.1.5.1.1.2	: branch
cbQosCMPostPolicyByte64	: .1.3.6.1.4.1.9.9.166.1.15.1.1.10	: branch
cbQosCMDropByte64	: .1.3.6.1.4.1.9.9.166.1.15.1.1.17	: branch
cbQosIfIndex			: .1.3.6.1.4.1.9.9.166.1.1.1.1.4	: branch
cbQosPolicyDirection		: .1.3.6.1.4.1.9.9.166.1.1.1.1.3	: branch
ifDescr				: .1.3.6.1.2.1.2.2.1.2			: branch

transforms
cbQosConfigName   	: CHAIN    	: {cbQosConfigIndex} {cbQosCMName}
cbQosCMDropByte64Delta  : DELTA 	: {cbQosCMDropByte64}
cbQosIfName		: CHAIN 	: {cbQosIfIndex} {ifDescr}
cbQosCMPostPolicyOps    : DELTA         : {cbQosCMPostPolicyByte64}
cbQosCMPostPolicyBps	: MATH 		: {cbQosCMPostPolicyOps} x 8
cbQosCMPostPolicySpeed 	: SPEED         : {cbQosCMPostPolicyBps}

message 
Policy drop alert : red={cbQosCMDropByte64Delta.thresh:red}

TABLE:rrd(DS:ds0:cbQosCMPostPolicyByte64:COUNTER;
DS:ds1:cbQosCMDropByte64:COUNTER)
Qos Name|Qos Index|Interface|Traffic (bytes)|Dropped traffic (Bytes) |
Delta
{cbQosConfigName}| -
|{cbQosIfName}|{cbQosCMPostPolicySpeed}|{cbQosCMDropByte64}|{cbQosCMDropByte64Delta.color}{cbQosCMDropByte64Delta}

When I drop {cbQosIfName} from message the array is full of information.
But with {cbQosIfName} I got no information. I know that cbQosIfName		:
CHAIN 	: {cbQosIfIndex} {ifDescr}
do the right request because à tcpdump devmon and I see the right oid
get.

Any idee. Can y do CHAIN multiple times in the same template ?

oau

[Colt Disclaimer] 
This email is from an entity of the Colt group of companies. 
Colt Group S.A., K2 Building, Forte 1, 2a rue Albert Borschette, L-1246 Luxembourg, R.C.S. B115679.  
Corporate and contact information for our entities can be found at 
http://colt.net/uk/en/Colt-Group-of-Companies/index.htm. 
Internet communications are not secure and Colt does not accept 
responsibility for the accurate transmission of this message. Content 
of this email or its attachments is not legally or contractually binding 
unless expressly previously agreed in writing by Colt