NetXMS Support Forum

We would like the ability to monitor  Switch ports in more depth.  Below I listed a group of OID's that we would like to monitor for threshold alerts.  Most of these would need some form of a template, macro or table based ability to manage SNMP interfaces.  I know you have talked about adding table support.  I don't know exactly what that means, but we would like to be able to customize the OID's that require an interface to include some or all of the below and to be able to easily customize a threshold for these.  For instance most of the error and collisions OID's we would want an alert if they increment at all.

So on a 24 port switch, if say only 16 ports are active at the time, it could monitor those 16 ports for any increase in the appropriate OID's from below.  Now another interesting thought, is do you dynamically or statically define which interfaces you monitor?  You could dynamically gather the "up" interfaces and apply these to that by default and then override that setting with any specific entries.  Then you could maybe monitor the whole array of interfaces and alert separately whenever an interface goes up or down.  In our particular case, we are talking about switches full of server ports, some of them teamed and some on LAG groups.  So we in particular went 0 errors and no interfaces should be going up or down unless we are rebooting or doing maintenance on a server.

At the same time, you could also monitor the configuration OID's to see if the speed, or duplex setting or some other setting has been changed.  That shouldn't happen, but it would be nice to know right away if somehow one of the interface had its speed setting changed.  We also noticed on one of our switches that a gigabit nic was only linked at 100Mbps.  That would be nice to have a way of detecting the currently active speed against a threshold of what it should be.

I know most of these can be done right now, but to do all of this right now, it would take somewhere in the range of 500 DCI's for a 24 port switch.

One last thought, the data retention for these would most likely be significantly different than in/out bandwidth so these system would need to easily support separate data retention rates for groups.

It almost seems like you need to build a dynamically growing table where you can assign the interface on one side and then the OID's to be applied on the other side and then checkboxes or something of what you want to monitor for each interface and then have the correct DCI parameters applied behind the scene.  You could maybe have a second tab that is a configuration tab, where you could then select multiple interfaces/OID's and apply common DCI parameters to them...

Just some thoughts.

   .1.3.6.1.2.1.10.7.2.1.2  AlignmentErrors
   .1.3.6.1.2.1.10.7.2.1.3  FCSErrors
   .1.3.6.1.2.1.10.7.2.1.4  SingleCollisions
   .1.3.6.1.2.1.10.7.2.1.5  MultipeCollisions
   .1.3.6.1.2.1.10.7.2.1.6  SQETestErrorrs
   .1.3.6.1.2.1.10.7.2.1.7  DeferredTransmissions
   .1.3.6.1.2.1.10.7.2.1.8  LateCollisions
   .1.3.6.1.2.1.10.7.2.1.9  ExcessiveCollisions
   .1.3.6.1.2.1.10.7.2.1.10 InternalMacTransmitErrors
   .1.3.6.1.2.1.10.7.2.1.11 CarrierSenseErrors
   .1.3.6.1.2.1.10.7.2.1.13 FrameTooLong
   .1.3.6.1.2.1.10.7.2.1.16 InternalMacReceiveErrors
   
   .1.3.6.1.2.1.16.1.1.1.3  DropEvents
   .1.3.6.1.2.1.16.1.1.1.8  CRCAlignErrors
   .1.3.6.1.2.1.16.1.1.1.9  undersize Packets
   .1.3.6.1.2.1.16.1.1.1.10 oversize Packets
   .1.3.6.1.2.1.16.1.1.1.11 Fragments
   .1.3.6.1.2.1.16.1.1.1.12 Jabbers
   .1.3.6.1.2.1.16.1.1.1.13 Collisions
   
   .1.3.6.1.2.1.31.1.1.1.15  Inteface Speed (1000, 1000, 10)
   .1.3.6.1.4.1.674.10895.4.1.2.1.1.8 Current Duplex Status(Might be an integer)

In addition to the above, bandwidth utilization per port would be cool as well:

(IfInOctets+IfOutOctets)*8*100/ time*IfSpeed IfSpeed is an estimate of the current bandwidth in bits per second. IfSpeed = 1.3.6.1.2.1.2.2.1.5

Kevin

Currently, the only thing you can easily monitor is interface up/down. System detect all interface state changes and send predefined events: SYS_IF_DOWN and SYS_IF_UP. You can filter and process these events in event processing policy, so you will need to configure only a few rules in EPP.
For other things, there are some work to do

Best regards,
Victor