From: Simeon B. <sbe...@mc...> - 2007-12-13 18:06:28
|
Buchan Milne wrote: ... > I've just added the Dell PowerEdge templates I've been testing for a while. > > We created a template a while back for a Cisco FWSM ... so far it looks to use > the same OIDs as yours for the PIX. We didn't have a test for failover > status, but we have an if_stat (mainly informational, so we know the > interface names the firewall team uses). > > The test names we have are conns,cpu,freemem (not sure why I didn't make it > just 'mem',if_stat. Is there a reason to use different names than the > standard Hobbit names? I've avoided using 'builtin' names just to avoid confusion. However, if you use one of the 'builtin' names like 'memory' -and- the message that you send to the status channel is in the same format as what the builtin would send, hobbit will create the expected rrd's and use the same graph definitions. I've only done this when the builtin column wasn't enabled at the same time (not sure what would happen in that case). This also works if there's an existing NCV-style data definition in hobbit{graph,server}.cfg. > > We are graphing connections on our conns test (using my version of the > extra-rrd.pl). I would really like to have CPU utilisation and memory graphs > as well. > > sysdescr for the FWSM is: > SNMPv2-MIB::sysDescr.0 = STRING: Cisco Firewall Services Module Version 3.1(4) > > I have attached the templates I created for our FWSM, let's discuss the > differences, and agree if we should use one template for both pix and FWSM. > > I've added the APC and IBM RSA2 templates. Thanks. Cool. I'll have a look and see if they're compatible and do a comparison. -- S i m e o n B e r k l e y Systems Engineer Mcclatchy Interactive |