SMON2-MIB: View SNMP OID List / Download MIB

This item is used to define which SMON applications are using resources at the agent. When the console performs smon application it should read this item in order to know which of the SMON applications are available in this agent. When there is a value of 0 (zero) in the relevant bit it means that the associated application is not running on the agent, When there is a value of 1 (one) in the relevant bit it means that the associated application is suported. D0 - statistics D1 - history D2 - alarm D3 - host D4 - hostTopN D5 - matrix D6 - filter D7 - capture D8 - event D9 - tokenRing D10 - protocolDir D11 -protocolDist D12 -addressMap D13 -nlHost D14 - nlMatrix D15 -alHost D16 -alMatrix D17 -usrHistory D18 - probeConfig D19 -port D20 - portTopN D21 - subnet D22 - subnetMatrix D23 - vlan D24 - vlanMatrix D25 - nlHostTopN D26 - portHistory

A set of parameters that control the creation of a report of the top N network layer host entries according to a selected metric.

A conceptual row in the xsHostTopNControlTable. An example of the indexing of this table is xsHostTopNControlDuration.3

An index that uniquely identifies an entry in the xsHostTopNControlTable. Each such entry defines one top N report prepared for one interface.

The nlHost table for which a top N report will be prepared on behalf of this entry. The nlHost table is identified by the value of the hlHostControlIndex for that table - that value is used here to identify the particular table. This object may not be modified if the associated xsHostTopNControlStatus object is equal to active(1).

The variable for each nlHost entry that the xsHostTopNEntries are sorted by. This object may not be modified if the associated xsHostTopNControlStatus object is equal to active(1). Enumeration: 'xsHostTopNOutOctets': 4, 'xsHostTopNInOctets': 3, 'xsHostTopNInPkts': 1, 'xsHostTopNOutPkts': 2.

The number of seconds left in the report currently being collected. When this object is modified by the management station, a new collection is started, possibly aborting a currently running report. The new value is used as the requested duration of this report, which is loaded into the associated xsHostTopNControlDuration object. When this object is set to a non-zero value, any associated xsHostTopNEntries shall be made inaccessible by the monitor. While the value of this object is non-zero, it decrements by one per second until it reaches zero. During this time, all associated xsHostTopNEntries shall remain inaccessible. At the time that this object decrements to zero, the report is made accessible in the xsHostTopNTable. Thus, the xsHostTopN table needs to be created only at the end of the collection interval.

The number of seconds that this report has collected during the last sampling interval. When the associated HostTopNControlTimeRemaining object is set, this object shall be set by the probe to the same value and shall not be modified until the next time the xsHostTopNControlTimeRemaining is set. This value shall be zero if no reports have been requested for this xsHostTopNControlEntry.

The maximum number of host entries requested for this report. When this object is created or modified, the probe should set xsHostTopNControlGrantedSize as closely to this object as is possible for the particular probe implementation and available resources.

The maximum number of host entries in this report. When the associated xsHostTopNControlRequestedSize object is created or modified, the probe should set this object as closely to the requested value as is possible for the particular implementation and available resources. The probe must not lower this value except as a result of a set to the associated xsHostTopNControlRequestedSize object. If the value of xsHostTopNControlRateBase is equal to xsHostTopNPkts, when the next topN report is generated, matrix entries with the highest value of xsHostTopNPktRate shall be placed in this table in decreasing order of this rate until there is no more room or until there are no more matrix entries. If the value of xsHostTopNControlRateBase is equal to xsHostTopNOctets, when the next topN report is generated, matrix entries with the highest value of xsHostTopNOctetRate shall be placed in this table in decreasing order of this rate until there is no more room or until there are no more matrix entries. It is an implementation-specific matter how entries with the same value of xsHostTopNPktRate or xsHostTopNOctetRate are sorted. It is also an implementation-specific matter as to whether or not zero-valued entries are available.

The value of sysUpTime when this top N report was last started. In other words, this is the time that the associated xsHostTopNControlTimeRemaining object was modified to start the requested report or the time the report was last automatically (re)started. This object may be used by the management station to determine if a report was missed or not.

The entity that configured this entry and is therefore using the resources assigned to it.

The status of this xsHostTopNControlEntry. An entry may not exist in the active state unless all objects in the entry have an appropriate value. If this object is not equal to active(1), all associated entries in the xsHostTopNTable shall be deleted by the agent.

A set of statistics for those network layer hosts that have counted the highest number of octets or packets.

A conceptual row in the xsHostTopNTable. The xsHostTopNControlIndex value in the index identifies the xsHostTopNControlEntry on whose behalf this entry was created. An example of the indexing of this table is xsHostTopNPktRate.3.10

An index that uniquely identifies an entry in the xsHostTopNTable among those in the same report. This index is between 1 and N, where N is the number of entries in this report. If the value of xsHostTopNControlRateBase is equal to xsHostTopNInPkts, increasing values of xsHostTopNIndex shall be assigned to entries with decreasing values of xsHostTopNRate until index N is assigned or there are no more xsHostTopNEntries.

The protocolDirLocalIndex of the network layer protocol of this entry's network address.

The network layer address of the host in this collection. This is represented as an octet string with specific semantics and length as identified by the associated xsHostTopN ProtocolDirLocalIndex. For example, if the protocolDirLocalIndex indicates an encapsulation of ip, this object is encoded as a length octet of 4, followed by the 4 octets of the ip address, in network byte order.

The number of packets seen from the source host to the destination host during this sampling interval, counted using the rules for counting the xsHostPkts object. If the value of xsHostTopNControlRateBase is xsHostTopNPkts, this variable will be used to sort this report.

A list of network layer addresses hosts to be monitored through an interface by the RMON II MIB hosts group. The OID of this table is a legitimate value for the hlMatrixControlDataSource, and for LANNET's Groups xsSubnetControlDataSource, xsSubnetMatrixControlDataSource,

An entry in the filter table.

Indicates the type of the filter defined by this entry. Enumeration: 'ipxNet': 3, 'ipSubnet': 2, 'ipHost': 1.

The IP address of a host monitored via the Interface. In case the filter type is not ipHost(1), the value of this entry is not relevant and should return the null string.

The address of a IP subnet monitored via the Interface. In case the filter type is not ipSubnet(2), the value of this entry is not relevant and should return the null string.

The mask of a IP subnet monitored via the Interface. In case the filter type is not ipSubnet(2), the value of this entry is not relevant and should return the null string.

The address of a IPX monitored via the Interface. In case the filter type is not ipxNet(3), the value of this entry is not relevant and should return the null string.

The status of this xsHostFilter entry. Enumeration: 'valid': 1, 'invalid': 4.

Setting the value of this item to clear(2) causes the agent to clear all entries in the HostFilterTable. Enumeration: 'idle': 1, 'clear': 2.

A list of higher layer (i.e. non-MAC) Subnets\Networks table control entries. These entries will enable the collection of the network and application level subnets tables indexed by subnetwork addresses. Entries in the xsSubnetTable will be created on behalf of each entry in this table. Implementations are encouraged to add an entry per monitored interface upon initialization so that a default collection of subnet statistics is available.

A conceptual row in the sSubnetControlTable. An example of the indexing of this entry is xsSubnetControlDataSource.1

An index that uniquely identifies an entry in the xsSubnetControlTable. Each such entry defines a function that collects statistics on a particular interface and places statistics about them in the xsSubnetTable, on behalf of this xsSubnetControlEntry.

The source of data for the associated Subnet tables. The statistics in this group reflect all packets on the local network segment attached to the identified interface.Mostly this instance will be the xsHostFilterTable. This object may not be modified if the associated xsSubnetControlStatus object is equal to active(1).

The number of times an xsSubnet entry has been inserted into the xsSubnet table. If an entry is inserted, then deleted, and then inserted, this counter will be incremented by 2. To allow for efficient implementation strategies, agents may delay updating this object for short periods of time. For example, an implementation strategy may allow internal data structures to differ from those visible via SNMP for short periods of time. This counter may reflect the internal data structures for those short periods of time. Note that the table size can be determined by subtracting xsSubnetControlDeletes from xsSubnetControlInserts.

The number of times an xsSubnet entry has been deleted from the xsSubnet table (for any reason). If an entry is deleted, then inserted, and then deleted, this counter will be incremented by 2. To allow for efficient implementation strategies, agents may delay updating this object for short periods of time. For example, an implementation strategy may allow internal data structures to differ from those visible via SNMP for short periods of time. This counter may reflect the internal data structures for those short periods of time. Note that the table size can be determined by subtracting xsSubnetControlDeletes from xsSubnetControlInserts.

The maximum number of entries that are desired in the xsSubnetable on behalf of this control entry. The probe will not create more than this number of associated entries in the table, but may choose to create fewer entries in this table for any reason including the lack of resources. If this object is set to a value less than the current number of entries, enough entries are chosen in an implementation - dependent manner and deleted so that the number of entries in the table equals the value of this object. If this value is set to -1, the probe may create any number of entries in this table. If the associated xsSubnetControlStatus object is equal to `active', this object may not be modified. This object may be used to control how resources are allocated on the probe for the various RMON functions.

The entity that configured this entry and is therefore using the resources assigned to it.

The status of this xsSubnetControlEntry. An entry may not exist in the active state unless all objects in the entry have an appropriate value. If this object is not equal to active(1), all associated entries in the nlHostTable and alHostTable shall be deleted.

A collection of statistics for a particular subnetwork layer address that has been discovered on an interface of this device. The probe will populate this table for all network layer protocols in the protocol directory table whose value of protocolDirHostConfig is equal to supportedOn(3), and will delete any entries whose protocolDirEntry is deleted or has a protocolDirHostConfig value of supportedOff(2). The probe will add to this table all subnetwork addresses that exist in the xsHostFilter.

A conceptual row in the xsSubnetTable. The xsSubnetControlIndex value in the index identifies the xsSubnetControlEntry on whose behalf this entry was created. The first protocolDirLocalIndex value in the index identifies the network layer protocol the second protocolLocalDirIndex identifies the protocol (network or application layer protocol) to be monitored on that of the xsSubnetAddress. An example of the indexing of this entry is xsSubnetOutPkts.1.783495.18.4.128.2.6.6.4.255.255.255.0.18.This Index indexes The total out IP packets of an Ip Subnet

A TimeFilter for this entry. See the TimeFilter textual convention to see how this works.

The subnetwork address for this xsSubnetEntry. This is represented as an octet string with specific semantics and length as identified by the protocolDirLocalIndex component of the index. For example, if the protocolDirLocalIndex indicates an encapsulation of ip, this object is encoded as a length octet of 4, followed by the 4 octets of the ip address, in network byte order.

The subnetwork mask for this xsSubnetEntry. This is represented as an octet string with specific semantics and length as identified by the protocolDirLocalIndex component of the index. For example, if the protocolDirLocalIndex indicates an encapsulation of ip, this object is encoded as a length octet of 4, followed by the 4 octets of the ip address, in network byte order.

The number of packets without errors transmitted to this subnetwork address since it was added to the xsSubnetTable. Note that this is the number of link-layer packets, so if a single network-layer packet is fragmented into several link-layer frames, this counter is incremented several times.

The number of packets without errors transmitted by this subnetwork address since it was added to the xsSubnetTable. Note that this is the number of link-layer packets, so if a single network-layer packet is fragmented into several link-layer frames, this counter is incremented several times.

The value of sysUpTime when this entry was last activated. This can be used by the management station to ensure that the entry has not been deleted and recreated between polls.

A list of higher layer (i.e. non-MAC) matrix control entries. These entries will enable the collection of the network and application level matrix tables containing conversation statistics indexed by pairs of subnetwork addresses. Entries in the xsSubnetMatrixSDTable and xsSubnetMatrixDSTable will be created on behalf of each entry in this table.

A conceptual row in the xsSubnetMatrixControlTable. An example of indexing of this entry is xsSubnetMatrixControDataSource.1

An index that uniquely identifies an entry in the xsSubnetMatrixControlTable. Each such entry defines a function that discovers conversations on a particular interface and places statistics about them in the xsSubnetMatrixSDTable and the xsSubnetMatrixDSTable, on behalf of this xsSubnetMatrixControlEntry.

The source of the data for the associated matrix tables. The statistics in this group reflect all packets on the local network segment attached to the identified interface.Mostly this instance will be the xsHostFilterTable. This object may not be modified if the associated xsSubnetControlStatus object is equal to active(1).

The number of times an subnetMatrix entry has been inserted into the subnetMatrix tables. If an entry is inserted, then deleted, and then inserted, this counter will be incremented by 2. The addition of a conversation into both the xsSubnetMatrixSDTable and xsSubnetMatrixDSTable shall be counted as two insertions (even though every addition into one table must be accompanied by an insertion into the other).To allow for efficient implementation strategies, agents may delay updating this object for short periods of time. For example, an implementation strategy may allow internal data structures to differ from those visible via SNMP for short periods of time. This counter may reflect the internal data structures for those short periods of time. Note that the sum of then xsSubnetMatrixSDTable and xsSubnetMatrixDSTable sizes can be determined by subtracting xsSubnetMatrixControlNlDeletes from xsSubnetMatrixControlNlInserts.

The number of times an subnetMatrix entry has been deleted from the subnetMatrix tables (for any reason). If an entry is deleted, then inserted, and then deleted, this counter will be incremented by 2. The deletion of a conversation from both the xsSubnetMatrixSDTable and xsSubnetMatrixDSTable shall be counted as two deletions (even though every deletion from one table must be accompanied by a deletion from the other). To allow for efficient implementation strategies, agents may delay updating this object for short periods of time. For example, an implementation strategy may allow internal data structures to differ from those visible via SNMP for short periods of time. This counter may reflect the internal data structures for those short periods of time. Note that the table size can be determined by subtracting xsSubnetMatrixControlNlDeletes from xsSubnetMatrixControlNlInserts.

The maximum number of entries that are desired in the subnetMatrix tables on behalf of this control entry. The probe will not create more than this number of associated entries in the table, but may choose to create fewer entries in this table for any reason including the lack of resources. If this object is set to a value less than the current number of entries, enough entries are chosen in an implementation-dependent manner and deleted so that the number of entries in the table equals the value of this object. If this value is set to -1, the probe may create any number of entries in this table. If the associated xsSubnetMatrixControlStatus object is equal to `active', this object may not be modified. This object may be used to control how resources are allocated on the probe for the various RMON functions.

The entity that configured this entry and is therefore using the resources assigned to it.

The status of this xsSubnetMatrixControlEntry. An entry may not exist in the active state unless all objects in the entry have an appropriate value. If this object is not equal to active(1), all associated entries in the xsSubnetMatrixSDTable, xsSubnetMatrixDSTable shall be deleted by the agent.

A list of traffic matrix entries which collect statistics for conversations between two network-level addresses. This table is indexed first by the source address and then by the destination address to make it convenient to collect all conversations from a particular address. The probe will populate this table for all network layer protocols in the protocol directory table whose value of protocolDirMatrixConfig is equal to supportedOn(3), and will delete any entries whose protocolDirEntry is deleted or has a protocolDirMatrixConfig value of supportedOff(2). The probe will add to this table all pairs of addresses seen in all packets with no MAC errors, and will increment octet and packet counts in the table for all packets with no MAC errors. Further, this table will only contain entries that have a corresponding entry in the xsSubnetMatrixDSTable with the same source address and destination address.

A conceptual row in the xsSubnetMatrixSDTable. The xsSubnetMatrixControlIndex value in the index identifies the xsSubnetMatrixControlEntry on whose behalf this entry was created. The first protocolDirLocalIndex value in the index identifies the protocol of the xsSubnetMatrixSDSourceAddress and xsSubnetMatrixSDDestAddress (network layer protocol), the second protocolDirLocalIndex. identifies the protocol to be monitored on that subnet (network or application layer) An example of the indexing of this table is xsSubnetMatrixSDPkts.1.783495.18.4.128.2.6.6.4.255.255.255.0.4.128.3.6.7..4.255.255.255.0.18

A TimeFilter for this entry. See the TimeFilter textual convention to see how this works.

The subnetwork source address for this xsSubnetMatrixSDEntry. This is represented as an octet string with specific semantics and length as identified by the protocolDirLocalIndex component of the index. For example, if the protocolDirLocalIndex indicates an encapsulation of ip, this object is encoded as a length octet of 4, followed by the 4 octets of the ip address, in network byte order.

The subnetwork source mask for this xsSubnetMatrixSDEntry. This is represented as an octet string with specific semantics and length as identified by the protocolDirLocalIndex component of the index. For example, if the protocolDirLocalIndex indicates an encapsulation of ip, this object is encoded as a length octet of 4, followed by the 4 octets of the ip address, in network byte order.

The subnetwork destination address for this xsSubnetMatrixSDEntry. This is represented as an octet string with specific semantics and length as identified by the protocolDirLocalIndex component of the index. For example, if the protocolDirLocalIndex indicates an encapsulation of ip, this object is encoded as a length octet of 4, followed by the 4 octets of the ip address, in network byte order.

The subnetwork destination mask for this xsSubnetMatrixSDEntry. This is represented as an octet string with specific semantics and length as identified by the protocolDirLocalIndex component of the index. For example, if the protocolDirLocalIndex indicates an encapsulation of ip, this object is encoded as a length octet of 4, followed by the 4 octets of the ip address, in network byte order.

The number of packets without errors transmitted from the source address to the destination address since this entry was added to the xsSubnetMatrixSDTable. Note that this is the number of link-layer packets, so if a single network-layer packet is fragmented into several link-layer frames, this counter is incremented several times.

The value of sysUpTime when this entry was last activated. This can be used by the management station to ensure that the entry has not been deleted and recreated between polls.

A list of traffic matrix entries which collect statistics for conversations between two subnetwork-level addresses. This table is indexed first by the destination address and then by the source address to make it convenient to collect all conversations to a particular address. The probe will populate this table for all network layer and application layer protocols in the protocol directory table whose value of protocolDirMatrixConfig is equal to supportedOn(3), and will delete any entries whose protocolDirEntry is deleted or has a protocolDirMatrixConfig value of supportedOff(2). The probe will add to this table all pairs of addresses that fits the xsHostFilter. Further, this table will only contain entries that have a corresponding entry in the xsSubnetMatrixSDTable with the same source address and destination address.

A conceptual row in the xsSubnetMatrixDSTable. The hlMatrixControlIndex value in the index identifies the hlMatrixControlEntry on whose behalf this entry was created. The protocolDirLocalIndex value in the index identifies the network layer protocol of the xsSubnetMatrixDSSourceAddress and xsSubnetMatrixDSDestAddress. An example of the indexing of this table is xsSubnetMatrixDSPkts.1.783495.18.4.128.2.6.7.4.255.255.255.0.4.128.3.6.6.4.255.255.255.0.18

A TimeFilter for this entry. See the TimeFilter textual convention to see how this works.

The subnetwork source address for this xsSubnetMatrixDSEntry. This is represented as an octet string with specific semantics and length as identified by the protocolDirLocalIndex component of the index. For example, if the protocolDirLocalIndex indicates an encapsulation of ip, this object is encoded as a length octet of 4, followed by the 4 octets of the ip address, in network byte order.

The subnetwork source mask for this xsSubnetMatrixDSEntry. This is represented as an octet string with specific semantics and length as identified by the protocolDirLocalIndex component of the index. For example, if the protocolDirLocalIndex indicates an encapsulation of ip, this object is encoded as a length octet of 4, followed by the 4 octets of the ip address, in network byte order.

The subnetwork destination address for this xsSubnetMatrixDSEntry. This is represented as an octet string with specific semantics and length as identified by the protocolDirLocalIndex component of the index. For example, if the protocolDirLocalIndex indicates an encapsulation of ip, this object is encoded as a length octet of 4, followed by the 4 octets of the ip address, in network byte order.

The subnetwork destination mask for this xsSubnetMatrixDSEntry. This is represented as an octet string with specific semantics and length as identified by the protocolDirLocalIndex component of the index. For example, if the protocolDirLocalIndex indicates an encapsulation of ip, this object is encoded as a length octet of 4, followed by the 4 octets of the ip address, in network byte order.

The number of packets without errors transmitted from the source address to the destination address since this entry was added to the xsSubnetMatrixDSTable. Note that this is the number of link-layer packets, so if a single network-layer packet is fragmented into several link-layer frames, this counter is incremented several times.

The value of sysUpTime when this entry was last activated. This can be used by the management station to ensure that the entry has not been deleted and recreated between polls.

This attribute contains the number of protocols in the protocolDirTable.

This attribute contains the value of sysUpTime at the time protocolDistStats counters were calculated.

This attribute contains the value of sysUpTime at the time nlHost counters were calculated.

This attribute contains the value of sysUpTime at the time xsSubnetStats counters were calculated.

The Active Applications bit mask is representing every active application from the first 1024 'well defined' applications. Each application is represented by a single bit in the string. Application number 1 is represented by the first bit in the string. Bit value '1' means, the protocol is active. Bit value '0' means, the protocol is inactive. For example the FTP data application, assigned as number 20. If the FTP application is active, then the bit number 20 will be set to '1'.

This table contain the 'active applications' from the 1024 'well defined' applications. For each active application, there is a global counter indicates the number of packets in the specific application monitored by the probe.

The entry for the xsActiveApplicationsTable. For each active application, there is a global counter indicates the number of packets in the specific application monitored by the probe.

The number of the application.

The number of packets of the specified application, monitored by the probe.

This item is set to value operate(1) when SMON is running on the probe and paused(2) when SMON is paused. The status is in operate(1) value whenever there is a valid control or when a Console set this item to operate(1). The status is in paused(2) value when there is no valid control and the Console didnot set this item to operate(1). Enumeration: 'paused': 2, 'operate': 1.

A table configuring SMON-2 operation for each router module in a device.

A conceptual row in the drSmonControlTable. Configures the SMON-2 operation for a particular module in the device. The row is statically created by the agent if the module is inserted.

The module group number (=slot number). Used as index.

Controls whether the embedded SMON application populates the matrix Rows with automatically-learned addresses in addition to those specified in the filter table. enable(1) - turns auto-learn on disable(2) - turns auto-learn off This toggle is meaningless in modes other than nl/al matrix. Enumeration: 'notSupported': 255, 'enable': 1, 'disable': 2.

The number of packets routed by the 3rd-layer forwarding hardware of this module.

This attribute contains the value of sysUpTime at the time protocolDistStats counters were determined by the agent.

The number of rows in the device entity matrix/table for the current counting mode. Applicable to counting mode capable of supporting one or more of the following statistics: nlHost, nlMatrix, alHost and alMatrix. For modes not supporting entity (host, subnet, or RNR group) tables/ matrices, this counter will be 0

The number of columns in the device entity matrix/table for the current counting mode. Applicable to counting mode capable of supporting one or more of the following statistics: nlHost, nlMatrix, alHost and alMatrix. For modes not supporting entity (host, subnet, or RNR group) tables/ matrices, this counter will be 0

A table containging a set of tables. Each table reports the placment of entities in the counter matrix/table of a particular module. Entities could be IP hosts, IP subnets, or other 3rd layer groups specified in IP-address/SubnetMask format, for which the device is capable of assigning an entry in its counter matrix/table.

A conceptual row in the drSmonEntityPlacementTable. Reports the index of a entity in the device's counter marix/table. Reports the creator of this entity - filter table or device's internal auto-learn process.

The module group number (=slot number). Used as index.

The placment index of the particular entity. The index determines the position of the entity in the counter matrix/table. Example: For a matrix of A rows x B columns and index i: If i

The IP address of an entity to explicitly monitor

The subnet mask of an entity. The value 255.255.255.255 signifies that this entity is a host.

The Type of this entity: empty(1) - Contains no relevant information. Not yet allocated to a specific entity. autoLearn(2) - The entity was learned by the auto-learn process of the device. filter(3) - The entity was created by a relevant filter entry in the filter table. Enumeration: 'autoLearn': 2, 'filter': 3, 'empty': 1.

A table with protocolDirLastChange per module.

A conceptual row in the drSmonProtocolDirLastChangeTable. Contains information for a particular module.

The module group number (=slot number). Used as index.

Same function as RFC 2021 protocolDirLastChange, but for a particular module.

This table contain a set of protocolDirTables. Each protocolDirTable lists the protocols that a particular module has the capability to decode and count. There is one entry in the per-module table for each such protocol. These protocols represent different network layer, transport layer, and higher-layer protocols.

A conceptual row in the drSmonProtocolDirTable. Represent a protocol to monitor on a particulat module. All fields except for drSmonProtocolDirModuleID have the same function as in RFC 2021 protocolDirTable. An example of the indexing of this entry is drSmonProtocolDirLocalIndex.3.8.0.0.0.1.0.0.8.0.2.0.0, which is a protocol for module 3 with the encoding of a length of 8, followed by 8 subids encoding the drSmonProtocolDirID of 1.2048, followed by a length of 2 and the 2 subids encoding zero-valued parameters.

The module group number (=slot number). Used as index.

A unique identifier for a particular protocol. same as RFC 2021, but for a particular module.

A set of parameters for the associated drSmonProtocolDirID. Same as RFC 2021, but for a particular module.

The locally arbitrary, but unique identifier associated with this drSmonProtocolDir entry. Same as RFC 2021, but for a particular module.

A textual description of the protocol encapsulation. Same as RFC 2021, but for a particular module.

This object describes 2 attributes of this protocol directory entry. Same as RFC 2021, but for a particular module. Bits: 'extensible': 0, 'addressRecognitionCapable': 1.

This object describes and configures the probe's support for address mapping for this protocol. Same as RFC 2021, but for a particular module. Enumeration: 'notSupported': 1, 'supportedOff': 2, 'supportedOn': 3.

This object describes and configures the probe's support for the network layer and application layer host tables for this protocol. Same as RFC 2021, but for a particular module. Enumeration: 'notSupported': 1, 'supportedOff': 2, 'supportedOn': 3.

This object describes and configures the probe's support for the network layer and application layer matrix tables for this protocol. Same as RFC 2021, but for a particular module. Enumeration: 'notSupported': 1, 'supportedOff': 2, 'supportedOn': 3.

The entity that configured this entry and is therefore using the resources assigned to it.

The status of this protocol directory entry. Same as RFC 2021, but for a particular module.

A table containging a set of tables. Each table configure hosts and subnets to explicitly monitor in a particular module.

A conceptual row in the drSmonFilterTable. Configures a host or subnet to monitor in a particular module, at a particular row or column. Typically, the NMS application conifgures these entries.

The module group number (=slot number). Used as index.

The index of the particular host/subnet. The index determines the position of the host/subnet in the counter matrix. Example: For a matrix of A rows x B columns and index i: If i

The IP address of a host or subnet to explicitly monitor

The Mask of a host or subnet to explicitly monitor. The value 255.255.255.255 signifies that this entry is a host entry.

The status of the row, as per SMIv2 (RFC1903). The row is in read-only mode when the status is set to active(1). Only active rows are used as filters.

This table contain the 'active applications' or protocols from all the protocols the modules can detect. 'Activity' is determined and reported by each module, in a sub-table of this table. The table contain entries only for 'Active' protocols. For each active application, there is a global counter indicates the number of packets in the specific application monitored by a module.

The entry for the drSmonActiveApplicationsTable. A set of entries exist for each module. For each active application, a global counter indicates the number of packets in the specific application monitored by the module. Entries exist only for 'active' applications.

The module group number (=slot number). Used as index.

The major type of the application. Note that TCP and UDP are assumed to be over IP. Enumeration: 'ethertype': 1, 'tcpProtocol': 4, 'udpProtocol': 3, 'ipProtocol': 2.

The application's sub-type value depends on the value of the type: Type sub-type value =========== ============== ethertype(1) 1 - Sum of all IP traffic 2 - ARP traffic ipProtocol(2) 1 - ICMP traffic 2 - OSPF traffic 3 - Sum of all UDP traffic 4 - Sum of all TCP traffic 5 - VRRP traffic udpProtocol(3) - The SubType is the UDP port number tcpProtocol(4) - The SubType is the TCP port number

The number of packets of the specified application monitored by the probe.