Menu
▾
▴
Re: [Devmon] Branch with Extra OID Info
|
From: Buchan M. <bg...@st...> - 2008-11-19 07:20:26
|
On Friday 14 November 2008 21:15:14 Geoff Hallford wrote:
> Hi All,
>
> So I have a new DHCP appliance (BlueCat Adonis) in the environment and
> I want to have devmon pull the DHCP info about each scope and display
> and alert on it. The problem I see is that normally a branch OID has
> the last digit incrementally increase but in this case, the OID has a
> the incrementing digital AND the subnet in reverse after it. Is there
> a way that I can use devmon to monitor this?
>
> Here is an example for the 10.2.2.0 pool. You will notice that at the
> end of each OID there is "0.2.2.10", which is the backwards of
> 10.2.2.0 and the digit prior is the incrementing or branching digit
> (1,2,3,4,5,6).
>
> Can devmon handle this?
>
> Name OID
> Value
> ---------------------------------------------------------------------------
>------------------------------------- Pool
> .1.3.6.1.4.1.13315.100.101.1.2.2.3.1.1.0.2.2.10 10.2.2.0 Start IP
> .1.3.6.1.4.1.13315.100.101.1.2.2.3.1.2.0.2.2.10 10.2.2.191
> End IP .1.3.6.1.4.1.13315.100.101.1.2.2.3.1.3.0.2.2.10
> 10.2.3.253 Total IPs
> .1.3.6.1.4.1.13315.100.101.1.2.2.3.1.4.0.2.2.10 319 Used IPs
> .1.3.6.1.4.1.13315.100.101.1.2.2.3.1.5.0.2.2.10 73 Alert Condition
> .1.3.6.1.4.1.13315.100.101.1.2.2.3.1.6.0.2.2.10 0
>
> There are hundreds of OID's like this, all ending with the reverse of
> the pool network at the end.
The Cisco SLB (Server Load Balancer) MIB does something similar:
SNMPv2-
SMI::enterprises.9.9.161.1.3.1.1.4.9.6.90.45.72.84.84.80.192.168.16.230.80 =
INTEGER: 2
SNMPv2-
SMI::enterprises.9.9.161.1.3.1.1.4.9.6.90.45.72.84.84.80.192.168.16.231.80 =
INTEGER: 2
SNMPv2-
SMI::enterprises.9.9.161.1.3.1.1.4.9.6.90.45.72.84.84.80.192.168.16.232.80 =
INTEGER: 2
SNMPv2-
SMI::enterprises.9.9.161.1.3.1.1.4.9.6.90.45.72.84.84.80.192.168.16.233.80 =
INTEGER: 2
SNMPv2-
SMI::enterprises.9.9.161.1.3.1.1.4.9.10.76.68.65.80.70.82.77.46.84.73.192.168.106.77.389
= INTEGER: 2
SNMPv2-
SMI::enterprises.9.9.161.1.3.1.1.4.9.10.76.68.65.80.70.82.77.46.84.73.192.168.106.78.389
= INTEGER: 2
SNMPv2-
SMI::enterprises.9.9.161.1.3.1.1.4.9.10.76.68.65.80.70.82.77.46.84.73.192.168.106.80.389
= INTEGER: 2
SNMPv2-
SMI::enterprises.9.9.161.1.3.1.1.4.9.10.76.68.65.80.70.82.77.46.84.73.192.168.106.81.389
= INTEGER: 2
In this case the last five numbers are the IP and port number of a real
server.
I was planning on adding an operator to extract values out of the oid, maybe
something like:
ipport: OIDREGSUB : {real} /(\d+)\.(\d+)\.(\d+)\.(\d+)\.(\d+)$/$1.$2.$3.$4:$5/
Which, in the first case you hopefully give us something like
192.168.16.230:80
In your case, it could be used as follows:
oids:
used: 1.3.6.1.4.1.13315.100.101.1.2.2.3.1.4.0.2.2.10 : branch
transforms:
poolname: OIDREGSUB : {used} /(\d+)\.(\d+)\.(\d+)\.(\d+)$/$4.$3.$2.$1/
which would hopefully give us 10.2.2.0.
Something like this should be feasible, and I wiill trry and get it working
to the point where it works for the Cisco SLB MIB. It might not do all you
need, but may be enough to get a start.
Regards,
Buchan
|
