Yes. Denika uses a report template system based on MRTG configurations. Templates can be created to trend any SNMP OID.

Please click to access a scan of the 2960 and 2800 mib trees. If you look at the OID for the dial-in page 1.3.6.1.4.1.1768.5.25.0, you can follow it down the page. The word "calldialin 25" tells you it is under the calldialin branch, in this case it is integer 5, and it is variable 25. To get all of the items that you can manage in the 2800, goto the HTTP managment system and click on SNMP. All of the MIBS are there at the top. Click and save all three.

Every row that is created in PostgreSQL gets a unique OID unless created WITHOUT OIDS. OIDs are autotomatically assigned unique 4-byte integers that are unique across the entire installation. However, they overflow at 4 billion, and then the OIDs start being duplicated. PostgreSQL uses OIDs to link its internal system tables together. To uniquely number columns in user tables, it is best to use SERIAL rather than OIDs because SERIAL sequences are unique only within a single table.

YES, T/Mon can receive & process SNMP traps. T/Mon can compile your MIBS and then you can select which alarm you wish to see.

The Denika manual can be accessed by clicking on the SOE button in the Denika web interface. If Denika is not installed you can click here to access our manuals.

SNMP (Simple Network Management Protocol) is the protocol governing network management and the monitoring of network device and their functions. It is not limited to TCP/IP network.

OIDs are PostgreSQL's answer to unique row ids. Every row that is created in PostgreSQL gets a unique OID. All OIDs generated during initdb are less than 16384 (from backend/access/transam.h). All user-created OIDs are equal or greater that this. By default, all these OIDs are unique not only within a table, or database, but unique within the entire PostgreSQL installation. PostgreSQL uses OIDs in its internal system tables to link rows between tables.

OID is stored in the ObjectIdentifierValue class. Only MibValueSymbols have a value and even then not all values are OID:s. The proper way to get the OID is to first check for a MibValueSymbol and then for an ObjectIdentiferValue with the instanceof operator.

If you know in which MIB the OID belongs, you can use the Mib.getSymbolByOid() method. Otherwise you will have to search all loaded MIB:s for the best (longest) match using the same method.

The ObjectIdentifierValue class structures the OID:s in a tree structure. It also provides methods for retrieving the parent and child OID:s, making it possible to traverse the whole OID tree. If you only wish to traverse the OID tree for a certain MIB file, care must be taken to examine the symbols associated with each ObjectIdentifierValue. The OID tree is linked together between all the MIB:s loaded by the same MibLoader, so any OID:s not belonging to the right MIB must be filtered out.

A persistence layer has been developed as part of the WAF for the purpose of encapsulating database access routines. This is desirable for at least two reasons: abstraction and database independence. By encompassing the SQL statements in Java objects, the database access routines are developed in a scalable environment. Also, the applications are isolated from the schema changes (which may occur in future versions) since the database access routines are encapsulated by a standard API.

SNMP aliases are used to maintain a database of SNMP session options for all the SNMP agents. An SNMP alias is a definition of a string which contains one or more SNMP session configuration options. snmp alias toaster { -address 1.2.3.4 -community "white bread" } This example defines an alias toaster which refers to the SNMP agent at IP address 1.2.3.4 and with community white bread. Note, it is possible to reference alias definitions within an alias.

Extremely ! It is a well known tool that defines a structure and set of rules for managing network devices. With SNMP software and managed switches, it allows the user to see' the network and analyze the traffic and perform diagnostics. Unmanaged switches are blind on the network and can not be accessed by the user to diagnose traffic and problems. Some manufacturers advertise that they have mananaged switches, but they are not true SNMP enabled.