SMON-MIB Table View

This table describes RMON data sources and port copy
capabilities. An NMS MAY use this table to discover the
identity and attributes of the data sources on a given agent
implementation. Similar to the probeCapabilities object,
actual row-creation operations will succeed or fail based on
the resources available and parameter values used in each
row-creation operation.
          
Upon restart of the RMON agent, the dataSourceTable, ifTable,
and perhaps entPhysicalTable are initialized for the available
dataSources.
          
For each dataSourceCapsEntry representing a VLAN or
entPhysicalEntry the agent MUST create an associated ifEntry
with a ifType value of 'propVirtual(53)'. This ifEntry will be
used as the actual value in RMON control table dataSource
objects. The assigned ifIndex value is copied into the
associated dataSourceCapsIfIndex object.
          
It is understood that dataSources representing VLANs may not
always be instantiated immediately upon restart, but rather as
          
VLAN usage is detected by the agent. The agent SHOULD attempt
to create dataSource and interface entries for all dataSources
as soon as possible.

Controls the setup of VLAN statistics tables.
          
The statistics collected represent a distribution based on
the IEEE 802.1Q VLAN-ID (VID), for each good frame attributed
to the data source for the collection.

Contains the VLAN statistics data.
The statistics collected represent a distribution based
on the IEEE 802.1Q VLAN-ID (VID), for each good frame
attributed to the data source for the collection.
          
This function applies the same rules for attributing frames
to VLAN-based collections. RMON VLAN statistics are collected
after the Ingress Rules defined in section 3.13 of the VLAN
Specification [20] are applied.
          
It is possible that entries in this table will be
garbage-collected, based on agent resources, and VLAN
configuration. Agents are encouraged to support all 4094
index values and not garbage collect this table.

Controls the setup of priority statistics tables.
          
The smonPrioStatsControlTable allows configuration of
collections based on the value of the 3-bit user priority
field encoded in the Tag Control Information (TCI) field
according to [19],[20].
          
Note that this table merely reports priority as encoded in
the VLAN headers, not the priority (if any) given to the
frame for the actual switching purposes.

Contains the priority statistics. The collections are based
on the value of the 3-bit user priority field encoded in the
Tag Control Information (TCI) field according to [19], [20].
Note that this table merely reports priority as encoded in
the VLAN headers, not the priority (if any) given to the
frame for the actual switching purposes.
          
No garbage collection is designed for this table, as there
always are at most eight rows per statistical set, and the
low memory requirements do not justify the implementation of
such a mechanism.

Port Copy provides the ability to copy all frames from a
specified source to specified destination within a switch.
Source and destinations MUST be ifEntries, as defined by [22].
One to one, one to many, many to one and many to many source to
destination relationships may be configured.
          
Applicable counters on the destination will increment for all
packets transiting the port, be it by normal bridging/switching
or due to packet copy.
Note that this table manages no RMON data collection by itself,
and an agent may possibly implement no RMON objects except
objects related to the port copy operation defined by the
portCopyCompliance conformance macro. That allows for a switch
with no other embedded RMON capability to perform port copy
operations to a destination port at which a different external
RMON probe is connected.
          
One to one, many to one and one to many source to destination
relationships may be configured.
          
Each row that exists in this table defines such a
relationship. By disabling a row in this table the port copy
relationship no longer exists.
          
The number of entries and the types of port copies (1-1,
many-1, 1-many) are implementation specific and could
possibly be dynamic due to changing resource availability.
          
In order to configure a source to destination portCopy
relationship, both source and destination interfaces MUST be
present as an ifEntry in the ifTable and their respective
ifAdminStatus and ifOperStatus values MUST be equal to
'up(1)'. If the value of any of those two objects changes
after the portCopyEntry is activated, portCopyStatus will
transition to 'notReady(3)'.
          
The capability of an interface to be source or destination of
a port copy operation is described by the 'copySourcePort(0)'
and 'copyDestPort(1)' bits in dataSourceCopyCaps. Those bits
SHOULD be appropriately set by the agent, in order to allow
for a portCopyEntry to be created.
          
Applicable counters on the destination will increment for all
packets transmitted, be it by normal bridging/switching or
due to packet copy.