| OID | 1.3.6.1.2.1.16.22.1.3.1 |
| Module | SMON-MIB (CISCO) |
| Nom | portCopyTable |
| Status | current |
| Description | 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. |
| Module | SMON-MIB (DELL) |
| Nom | portCopyTable |
| Status | current |
| Description | 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. |
| Module | SMON-MIB (ietf) |
| Nom | portCopyTable |
| Status | current |
| Description | 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. |