Appendix E. FireBrick specific SNMP objects
Prev   Next

Appendix E. FireBrick specific SNMP objects

Table of Contents

E.1. Conventions
E.1.1. IP addresses as indices
E.2. Firebrick CPU usage
E.2.1. Structure definitions
E.2.1.1. CPU usage for this Firebrick
E.3. Firebrick system stats
E.3.1. Structure definitions
E.3.1.1. The table of runtime stats for this Firebrick
E.4. Monitoring for general system features
E.4.1. Structure definitions
E.4.1.1. The list of readings for this Firebrick
E.5. System wide status
E.5.1. Structure definitions
E.5.1.1. fbGlobalMemory
E.5.1.2. fbGlobalBuffers
E.6. Firebrick profiles
E.6.1. Structure definitions
E.6.1.1. Profiles status
E.7. Monitoring information (deprecated)

This appendix details the SNMP objects that are specific to the FireBrick.

E.1. Conventions

To avoid writing out very repetitive (and long) OIDs this appendix uses a substitution notation when describing structures. The OIDs contain the names of indices and an X representing the structure field number given by the matching column in the following table. So if the OID given in the manual is iso.1.2.3.4.X.anIndex then the OID for the first item described in the table row with column X = 3 would be: iso.1.2.3.4.3.1

E.1.1. IP addresses as indices

In some structures IP addresses may be used as indices into SNMP tables. When this is the case the IP must be encoded into the OID for the resource. This encoding consists of the following separated by dots:

  1. The IP type: 1 for IPv4, 2 for IPv6.
  2. A length prefixed array of the bytes of the address in network order.

Example E.1. 

For the IPv4 address 10.0.1.12 the IP type is 1 and the length is 4. Therefore the OID fragment 1.4.10.0.1.12 could be used as an index.

Example E.2. 

For the IPv6 address 2001::32 the IP type is 2 and the length is 16. Therefore the OID fragment 2.16.32.1.0.0.0.0.0.0.0.0.0.0.0.0.0.50 could be used as an index.

Prev   Next
Appendix D. VLANs : A primer Home E.2. Firebrick CPU usage