SYNOPTICS-ETHERNET-MIB: View SNMP OID List / Download MIB

Does this concentrator have retiming turned on. Writing a 1 will turn off retiming and writing a 2 will turn on retiming. This will change the active state of retiming but will change the value in EEPROM only when agentWriteEeprom is set.The factory default of this state is on. Retiming cannot be disabled in the 2810 concentrator. The 2810 agent will implement this object as read-only. Enumeration: 'on': 2, 'off': 1.

This contains a count of frames that are successfully received by the concentrator. This does not include frames received with a frame-too-long, runt, FCS, or alignment errors. This counter includes broadcast and multicast frames that are received.

Contains a count of data and padding octets in frames that are successfully received by the concentrator. This does not include frames received with a frame-too-long, runt, FCS, or alignment errors. This counter includes octets in broadcast and multicast frames that are received. This counter does not include the octets in the CRC field. The octets in the address and length/type fields are counted.

This contains a count of frames that are successfully received by the concentrator and are directed to an active non-broadcast group address. This does not include frames received with a frame-too-long, runt, FCS, or alignment errors. Only frames that are for a multicast address that this interface is receiving are counted. Broadcast packets are not included.

This contains a count of frames that are successfully received by the concentrator and are directed to the broadcast group address. This does not include frames received with a frame-too-long, runt, FCS, or alignment errors. Multicast packets are not included.

This contains a count of the collisions at the concentrator level. For NMM+ this is a true counter. For other NMMs this is a summation of all the port level collision 'flags' for all ports.

This contains a count of frames that are received by the concentrator and exceed the maximum permitted frame size. This counter is incremented when the frameTooLong error is detected.

This contains a count of frames received by the concentrator that are less than the minimum permitted frame size and have a good FCS.

This contains a count of frames received by the concentrator that are less than the minimum permitted frame size and have a bad FCS or alignment error.

This contains a count of frames received by the concentrator that are not an integral number of octets in length and do not pass the FCS check. This counter is incremented when the alignment Error status is detected.

This contains a count of frames received by the concentrator that are an integral number of octets in length that do not pass the FCS check. This counter is incremented when the frame Check Error status is detected.

This contains a total concentrator count of the late collisions. For NMM+ this is a true counter. For other NMMs this is a summation of all the port level late collision 'flags' for all ports.

This s3EnetConcSecureStatus object indicates whether the security features (both allowed nodes and LattisSecure) for the concentrator are active or inactive. If security is active, this object also indicates whether the allowed nodes feature is controlled at the concentrator, board, or port level. LattisSecure features are always controlled at the port level. (See the Authorized Nodes tables for more information about how the allowed nodes and LattisSecure receive security features are configured.) If this object is set to concSecureOn(2), then the allowed nodes feature is controlled at the concentrator level and activated for every non-LattisSecure Ethernet port in the concentrator. If an authorized node violation occurs on any port, the action specified in s3EnetConcAuthAction is taken. If this object is set to portCheckOn(3), then allowed nodes is controlled at the port level by the s3EnetPortSecureStatus object for that port. The port's s3EnetPortAuthAction determines the action taken when authorized nodes violations occur on that port. If this object is set to slotCheckOn(4), then allowed nodes is controlled at the board level by the s3EnetBoardSecureStatus object for that board. The board's s3EnetBoardAuthAction determines the action taken when authorized nodes violations occur on that board's ports. If this object is set to concentratorOff(5), then all security features, including LattisSecure, are deactivated for the entire concentrator. No matter what the status of this object, the board and port level SecureStatus and AuthAction are not lost even if they are not currently being used. Thus, the user can change a port's status even if this object is slotCheckOn(4). If this object is then changed to portCheckOn(3), then the change will take effect. The agent must support download of this object in the CFG file. In release 4.0, this object was called s3EnetConcAuthStatus. Enumeration: 'slotCheckOn': 4, 'concSecureOff': 5, 'other': 1, 'portCheckOn': 3, 'concSecureOn': 2.

If s3EnetConcSecureStatus is concSecureOn(2) and a violation occurs, then the action specified by this object will take place. On a partition, only the port that the violation occurs on will be partitioned. This object does not apply to LattisSecure ports. The agent must support download of this object in the CFG file. Enumeration: 'sendTrapPartition': 5, 'other': 1, 'partition': 4, 'sendTrap': 3, 'noAction': 2.

If s3EnetConcSecurityLock is locked(2), the agent will refuse all requests to modify the 'security configuration' (defined below) by returning a BadValue return value. If s3EnetConcSecurityLock is notLocked(3), requests to modify security configuration will be handled in the usual manner. SetRequests for objects not included in the security configuration are not affected by the state of this object. Objects that are part of the security configuration are s3EnetConcAuthStatus, s3EnetConcAuthAction, s3EnetBoardAuthStatus, s3EnetBoardAuthAction, s3EnetPortAuthStatus, s3EnetPortAuthAction, s3EnetPortAddrLearnMode, s3EnetPortTxSecurity, and all of the objects in the s3EnetAuthNodesTable. Enumeration: 'notLocked': 3, 'other': 1, 'locked': 2.

Identifies the channel to which this NMM is currently monitoring. Enumeration: 'other': 1, 'enetB': 3, 'enetA': 2.

A table of board-related objects. The number of entries is given by the number of Ethernet host module and network management module boards that are contained in same backplane Ethernet segment as the reporting NMM.

A table containing objects about Ethernet boards which are currently plugged into the 3000 chassis.

A unique value for each board. Its value ranges between 1 and 12. The value for each board must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization.

See s3SlotModuleType Enumeration: 'm3302': 3, 'm3301': 16, 'm3307': 17, 'm3305': 5, 'm331x': 26, 'm3308': 6, 'm3323': 11, 'm3324-ST': 12, 'm3314-ST': 9, 'm3383': 24, 'm3308A': 38, 'm3386': 32, 'm3384': 25, 'other': 2, 'm3314M-ST': 10, 'empty': 1, 'm3313': 7, 'm3307A': 37, 'm3356': 18, 'm3313M': 8, 'm3304-ST': 4, 'm3395': 34, 'm3394': 33, 'm3324S-ST': 36, 'm3323S': 35.

See s3CommonBoardHwVer

See s3CommonBoardStatus Enumeration: 'fail': 2, 'ok': 1.

See s3CommonBoardReset Enumeration: 'reset': 2, 'noReset': 1.

See s3CommonBoardPartStatus Enumeration: 'partition': 2, 'enabled': 1.

See s3CommonBoardCntlStatus Enumeration: 'notNmControl': 1, 'nmControl': 2.

See s3CommonBoardPsStatus Enumeration: 'fail': 2, 'ok': 1.

This contains a count of frames that are successfully received by the board. This does not include frames received with a frame-too-long, runt, FCS, or alignment errors. This counter includes broadcast and multicast frames that are received.

Contains a count of data and padding octets in frames that are successfully received by the board. This does not include frames received with a frame-too-long, runt, FCS, or alignment errors. This counter includes octets in broadcast and multicast frames that are received. This counter does not include the octets in the CRC field. The octets in the address and length/type fields are counted.

This contains a count of frames that are successfully received by the board and are directed to an active non-broadcast group address. This does not include frames received with a frame-too-long, runt, FCS, or alignment errors. Only frames that are for a multicast address that this interface is receiving are counted. Broadcast packets are not included.

This contains a count of frames that are successfully received by the board and are directed to the broadcast group address. This does not include frames received with a frame-too-long, runt, FCS, or alignment errors. Multicast packets are not included.

This contains a board level count of collisions. For NMM+ this is a true counter. For other NMMs this is a summation of all the port level collision 'flags' for this board.

This contains a count of frames that are received by the board and exceed the maximum permitted frame size. This counter is incremented when the frameTooLong error is detected.

This contains a count of frames received by the board that are less than the minimum permitted frame size and have a good FCS.

This contains a count of frames received by the board that are not an integral number of octets in length and do not pass the FCS check. This counter is incremented when the alignmentError status is detected.

This contains a count of frames received by the board that are an integral number of octets in length that do not pass the FCS check. This counter is incremented when the frameCheckError status is detected.

This contains a count of the board level late collisions. For NMM+ this is a true counter. For other NMMs this is a summation of all the port level late collision 'flags' for this board.

This object is only used if s3EnetConcSecureStatus is set to slotCheckOn(4). In this case, turning this object on(2) means that any node that is heard on this board which is not allowed on this board (i.e., not in AuthNode table with the slotIndex equal to this board or 0 for all boards) will cause the action specified in s3EnetBoardAuthAction to take place. If s3EnetConcSecureStatus is set to slotCheckOn(4) but this object is set to off(3), then the authorized nodes feature for this board is deactivated. If s3EnetConcSecureStatus is not set to slotCheckOn(4), then this object will not be used but will maintain its settings unless explicitly changed. This object does not affect the configuration or functioning of security features on LattisSecure Host Modules. Enumeration: 'on': 2, 'other': 1, 'off': 3.

If s3EnetConcSecureStatus is slotCheckOn(4) and s3EnetBoardAuthStatus is on(2) and an authorized nodes violation occurs on the board, then the action specified by this object will take place. On a partition, only the port that the violation occurs on will be partitioned. This object does not apply to LattisSecure ports. Enumeration: 'sendTrapPartition': 5, 'other': 1, 'partition': 4, 'sendTrap': 3, 'noAction': 2.

The time ( in hundredths of a second) that the board was first seen as a member of this NMM's segment.

A table of Local Bridge Board entries. The number of entries is determined by the Concentrator Slot Configuration Table. Only those entries that are Ethernet local bridges will have entries in this list.

A table containing objects about Boards which are local bridges that are currently plugged into the 3000 chassis.

A unique value for each board. Its value ranges between 1 and 12. The value for each board must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization.

Description of the local bridge board.

Number of ports that are on the local bridge board.

Latest Diagnostic LED Status that has been recorded.

The current status of the board as it relates to rebooting. Enumeration: 'reqstToBoot': 2, 'other': 1, 'notReqstToBoot': 3.

This status says whether the local bridge is active or in standby mode. Enumeration: 'standby': 2, 'other': 1, 'notStandby': 3.

A table of Port entries that are part of a local bridge. The number of entries is determined by knowing the number of local bridge boards that are installed by looking at s3ChassisSlotConfigTable and by knowing how many ports are on a local bridge board by looking at s3EnetLocBridgePortCount.

A table containing objects about the ports of the local bridges that are currently plugged into the 3000 chassis.

A unique value for each board. Its value ranges between 1 and 12. The value for each board must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization.

A unique value for each port. Its value ranges between 1 and 12. The value for each port must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization.

Medium dependent ID for the port. See s3SlotModuleMdaId in the SynOptics Common MIB.

Bridge interface types. Enumeration: 'etherEther': 2, 'other': 1, 'etherTokenRing': 3.

A text description of the port.

Operating status of the port. Enumeration: 'standby': 2, 'other': 1, 'notStandby': 3.

A table of Remote Bridge Board entries. The number of entries is determined by the Concentrator Slot Configuration Table. Only those entries that are Ethernet remote bridges will have entries in this list.

A table containing objects about Boards which are remote bridges that are currently plugged into the 3000 chassis.

A unique value for each board. Its value ranges between 1 and 12. The value for each board must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization.

Description of the board.

Number of ports that are on the board.

Latest Diagnostic LED Status that has been recorded.

The current status of the board as it relates to rebooting. Enumeration: 'reqstToBoot': 2, 'other': 1, 'notReqstToBoot': 3.

This status says whether the remote bridge is active or in standby mode. Enumeration: 'standby': 2, 'other': 1, 'notStandby': 3.

A table of Port entries that are part of a remote bridge. The number of entries is determined by knowing the number of remote bridge boards that are installed by looking at s3ChassisSlotConfigTable and by knowing how many ports are on a remote bridge board by looking at s3EnetRemBridgePortCount.

A table containing objects about the ports of the remote bridges that are currently plugged into the 3000 chassis.

A unique value for each board. Its value ranges between 1 and 12. The value for each board must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization.

A unique value for each port. Its value ranges between 1 and 12. The value for each port must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization.

Medium dependent ID for the port. Enumeration: 'x21Barrier': 3, 'v35': 7, 't1': 9, 'rs449': 6, 'x21Unbarrier': 4, 'other': 1, 'g703': 8, 'ethernet': 2, 'rs232': 5.

A text description of the port.

Operating status of the port. Enumeration: 'standby': 2, 'noLink': 4, 'other': 1, 'operational': 3.

Ready to send status of the port. Enumeration: 'notRdySnd': 3, 'other': 1, 'rdySnd': 2.

Clear to send status of the port. Enumeration: 'notClrSnd': 3, 'other': 1, 'clrSnd': 2.

Carrier detect status of the port. Enumeration: 'noCarDt': 3, 'other': 1, 'carDt': 2.

A table of Router Board entries. The number of entries is determined by the Concentrator Slot Configuration Table. Only those entries that are Ethernet routers will have entries in this list.

A table containing objects about Boards which are routers that are currently plugged into the 3000 chassis.

A unique value for each board. Its value ranges between 1 and 12. The value for each board must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization.

Description of the router board.

Latest Diagnostic LED Status that has been recorded.

This status says whether the router is active or in standby mode. Enumeration: 'standby': 2, 'other': 1, 'notStandby': 3.

Information maintained for each Ethernet board. The information can be retrieved for any Ethernet board, even if the board is not on the same backplane Ethernet segment as this NMM. The instance is the slot number of the concentrator that the board occupies.

There is one entry per Ethernet board in this table.

A unique value for each board. Its value ranges between 1 and 12. The value for each board must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization.

The channel to which the board is connected. The primary use of this object is for providing realtime switching of boards between channel A and channel B. It is also returned in the enetChannelChange trap, in which case it indicates a board is switched from one channel to the other. The write capability of this object can only apply to those modules with channel switching function. Any attempt to write this object for a non-switchable board, the agent will return badValue. Enumeration: 'other': 1, 'enetB': 3, 'enetA': 2, 'enetAandEnetB': 4.

The agent will return switchCapable(2) for any Ethernet host board which can be switched between Ethernet channels. The value notSwitchCapable(3) indicates that the Ethernet board can not be switched to another channel. Enumeration: 'switchCapable': 2, 'other': 1, 'notSwitchCapable': 3.

The agent will return redundCapable(2) for any Ethernet host board which can provide hardware and/or software controlled redundancy on the port level. The value notRedundCapable(3) indicates that the Ethernet board can not support port redundancy. Enumeration: 'redundCapable': 2, 'other': 1, 'notRedundCapable': 3.

A list of port entries. The number of entries is given by learning the type of board from the information in the s3ChassisSlotConfigTable.

A table containing objects about the Ports of each board plugged into the 3000 chassis which are on the same backplane Ethernet segment as the reporting NMM.

A unique value for each board. Its value ranges between 1 and 12. The value for each board must remain constant at least from one reinitialization of the entity's network management system to the next reinitialization.

A unique value for each port. Its value is dependent on the board type. The value for each port must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization.

Tells whether the port is receiving link status. Enumeration: 'on': 2, 'other': 3, 'off': 1.

This indicates the operational status of the Port. Writing a partition(2) will partition the port indefinitely and enabled(1) will enable the port. If a timed partition is desired, then writing timedPartition(4) to this object at the same time that a time value is supplied in s3EnetPortPartTime is required. Timed partitions will not survive across a reset. In this case the port will go to the partition(2) state. The value latSecPartition(5) is returned when the port has been automatically partitioned by the LattisSecure Host Module because of a security violation. The value autoPartition(3) is returned when the port has been automatically partitioned by the repeater using the 802.3 repeater auto-partition function. The agent will not allow this object to be set to autoPartition(3) or latSecPartition(5) using an SNMP request. Enumeration: 'latSecPartition': 5, 'autoPartition': 3, 'partition': 2, 'enabled': 1, 'timedPartition': 4.

Tells whether the DTE connected to the Port is jabbering or not. Enumeration: 'ok': 1, 'jabbering': 2.

This contains a count of frames that are successfully received by the port. This does not include frames received with a frame-too-long, runt, FCS, or alignment errors. This counter includes broadcast and multicast frames that are received.

Contains a count of data and padding octets in frames that are successfully received by the port. This does not include frames received with a frame-too-long, runt, FCS, or alignment errors. This counter includes octets in broadcast and multicast frames that are received. This counter does not include the octets in the CRC field. The octets in the address and length/type fields are counted.

This contains a count of frames that are successfully received by the port and are directed to an active non-broadcast group address. This does not include frames received with a frame-too-long, runt, FCS, or alignment errors. Only frames that are for a multicast address that this interface is receiving are counted. Broadcast packets are not included.

This contains a count of frames that are successfully received by the port and are directed to the broadcast group address. This does not include frames received with a frame-too-long, runt, FCS, or alignment errors. Multicast packets are not included.

This contains a count of collisions. For NMM+ this is a true counter. For other NMMs this is a count of the collision flags.

This contains a count of frames that are received by the port and exceed the maximum permitted frame size. This counter is incremented when the frameTooLong error is detected.

This contains a count of frames received by the port that are less than the minimum permitted frame size and have a good FCS.

This contains a count of frames received by the port that are not an integral number of octets in length and do not pass the FCS check. This counter is incremented when the alignmentError status is detected.

This contains a count of frames received the port that are an integral number of octets in length that do not pass the FCS check. This counter is incremented when the frameCheckError status is detected.

This contains a count of late collisions. For NMM+ this is a true counter. For other NMMs this is a count of the late collision flags.

This object is only used if s3EnetConcSecureStatus is set to portCheckOn(3) or if the port is on a LattisSecure Host Module. In this case, turning this object on(2) means that any node that heard on this port which is not allowed on this port will cause the action specified in s3EnetPortAuthAction to take place. This object does not affect the LattisSecure transmit security feature for the port. It is incompatible with LattisSecure continuous learning mode. If the value of s3EnetPortAddrLearnMode for a LattisSecure port is continuousLearn(3), turning this object to on(2) for that port will not have any affect. If s3EnetConcSecureStatus is set to portCheckOn(3) but this object is set to off(3), then all authorized nodes or LattisSecure receive security features for this port are deactivated. If s3EnetConcSecureStatus is not set to portCheckOn(3), then this object will not be used for allowed nodes, but will be used for LattisSecure. Enumeration: 'on': 2, 'other': 1, 'off': 3.

If s3EnetConcSecureStatus is portCheckOn(3) or this port is on a LattisSecure Host Module, and s3EnetPortAuthStatus is on(2) and an authorized nodes violation occurs on this port, then the action specified by this object will take place on this port. If the port is a LattisSecure port, the authorized nodes security will be implemented by the LattisSecure Host Module. Enumeration: 'sendTrapPartition': 5, 'other': 1, 'partition': 4, 'sendTrap': 3, 'noAction': 2.

When partitioning the port for a specified time, s3EnetPortPartStatus must be set with timedpartition(4) and this object must be supplied with the duration value. If a PDU sets s3EnetPortPartStatus and not this object, the port will not be partitioned.

The media connection type for this port. Note that this object was called s3EnetPortMDIXSwitch in the Ethernet 3.3 and 4.0 MIBs. Enumeration: 'tenBaseFLRedund': 10, 'switchMdi': 9, 'aui': 4, 'tenBaseTMdi': 3, 'tenBaseT': 2, 'foirl': 6, 'switch': 8, 'other': 1, 'bnc': 5, 'tenBaseFL': 7.

This object tells whether the port is connected to a host or to an interconnect (defined to be another NMM that is sending hello messages). The NMM agent will assign this object the value other(1) on initialization. If it sees hello messages coming in on the port, it will change the InterconStatus to be interconnect(2). Enumeration: 'other': 1, 'interconnect': 2.

This object tells whether the NMM should collect node address information from this port for the Find Nodes, Show Nodes, and Traffic Matrix (NMM+ only) tables. By default, the node addresses are collected only from ports that are not identified as interconnect ports. In addition, allowed nodes checking is done only on ports that are not interconnect ports. This object provides a means of overriding the default for collection and checking of node addresses. Setting this variable to default(1) tells the NMM to collect and check addresses if and only the port has not been identified as an interconnect port. To disable node address collection and checking on a port, set this object to neverCollect(2). To collect and check node addresses for an interconnect port, set this object to alwaysCollect(3). This object and its default setting has no affect on LattisSecure receive or transmit security features. To restore the 'natural' value for the port, set this object to default(1). Enumeration: 'default': 1, 'neverCollect': 2, 'alwaysCollect': 3.

This object indicates whether the port should automatically learn the port address by reading the source address on the incoming packets. This object applies only to ports on a LattisSecure Host Module. For other ports, the agent returns the value other. A Get will return the current learning mode of the port. Setting to noAutoLearn(2) can be used to turn off continuousLearn (3) or oneShotLearn(4). The value of this object is in effect regardless of the value of s3EnetConcSecureStatus or s3EnetPortAuthStatus. Continuous learning is not compatible with LattisSecure receive security, thus s3EnetPortAddrLearnMode should not be set to continuousLearn(3) when s3EnetPortAuthStatus is on(2). If this combination is set, the receive security will not function. If this object is set to oneShotLearn(4), the agent will store the address (when it is learned) into the allowed nodes tables. This can cause the current address to be written over. Because continuous learning is not compatible with receive security, addresses learned while the port is in continuous learning mode will not be stored in the allowed nodes tables. Attempts to set the value to other(1) on a LattisSecure port will be rejected by the agent. Likewise, attempts to set the value to noAutoLearn(2), continuousLearn(3), or oneShotLearn(4) on a non-LattisSecure port will be rejected. Enumeration: 'oneShotLearn': 4, 'continuousLearn': 3, 'other': 1, 'noAutoLearn': 2.

This value of this object is meaningful only when s3EnetConcSecureStatus is not set to concSecureOff(5) (i.e., if security features are activated on the concentrator). This object applies only to ports on LattisSecure Host Modules. For other ports, the agent will return other(1) in response to a get request. The value off(3) indicates that LattisSecure transmit security is disabled on this LattisSecure port. The value on(2) indicates that LattisSecure transmit security is enabled on this LattisSecure port. Attempts to set the value to other(1) on a LattisSecure port will be rejected by the agent. Likewise, attempts to set the value to on(2) or off(3) on a non-LattisSecure port will be rejected. Enumeration: 'on': 2, 'other': 1, 'off': 3.

This table provides a list of port entries. The number of entries is given for any Ethernet board in the concentrator, even if the board is not on the same Ethernet segment as this NMM.

A table containing objects about the ports of each Ethernet board plugged into the 3000-series chassis.

A unique value for each board. Its value ranges between 1 and 12. The value for each board must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization.

A unique value for each port. Its value is dependent on the board type.

Tells whether the port is receiving link status. Enumeration: 'on': 2, 'other': 3, 'off': 1.

This indicates the operational status of the Port. Writing a partition(2) will partition the port indefinitely and enabled(1) will enable the port. If a timed partition is desired, then writing timedPartition(4) to this object at the same time that a time value is supplied in s3EnetCommonPortPartTime is required. Timed partitions will not survive across a reset. In this case the port will go to the partition(2) state. The value latSecPartition(5) is returned when the port has been automatically partitioned by the LattisSecure Host Module because of a security violation. The value autoPartition(3) is returned when the port has been automatically partitioned by the repeater using the 802.3 repeater auto-partition function. The agent will not allow this object to be set to autoPartition(3) or latSecPartition(5) using an SNMP request. Note that the value timedPartition(4) is returned only when the board is timed partitioned by this NMM. Enumeration: 'latSecPartition': 5, 'autoPartition': 3, 'partition': 2, 'enabled': 1, 'timedPartition': 4.

The media connnection type for this port. Note that this object was called s3EnetPortMDIXSwitch in the Ethernet 3.3 and 4.0 MIBs. Enumeration: 'tenBaseFLRedund': 10, 'switchMdi': 9, 'aui': 4, 'tenBaseTMdi': 3, 'tenBaseT': 2, 'foirl': 6, 'switch': 8, 'other': 1, 'bnc': 5, 'tenBaseFL': 7.

When partitioning the port for a specified time, s3EnetCommonPortPartStatus must be set with timedPartition(4) and this object must be supplied with the duration value. If a PDU sets s3EnetCommonPortPartStatus and not this object, the port will not be partitioned.

A table of ports for each 10BASE-FL board with redundancy capability. The number of boards is determined by checking s3EnetCommonBoardRedund having a value of redundCapable(2) for each board in table s3EnetCommonBoardTable.

An entry in the table of ports on boards with redundancy capability. Entries in the table cannot be created or deleted via SNMP. Row modification via SNMP is allowed only for ports that support either hardware or software redundancy, but the amount of modifications between the two varies. Entries for boards that support hardware-redundancy only allow the objects s3EnetRedPortRedundMode, s3EnetRedPortSwitchoverStatus, and s3EnetRedPortSwitchoverTime to be modified. The object s3EnetRedPortRedundMode can only be modified on certain agent versions (see the description of the object for more details). Entries for boards that support software-redundancy allow the objects s3EnetRedPortRedundMode, s3EnetRedPortCompanionSlotNo, s3EnetRedPortCompanionPortNo, s3EnetRedPortSwitchoverStatus, and s3EnetRedPortSwitchoverTime to be modified. Software-redundant pairs are configured by sending the objects s3EnetRedPortRedundMode, s3EnetRedPortCompanionSlotNo, and s3EnetRedPortCompanionPortNo in the same SNMP SET PDU, with the object s3EnetRedPortRedundMode set to the value of swActive(4) or swStandby(5). When changing an existing software-redundant pair, the existing pair must first be broken up by setting the object s3EnetRedPortRedundMode to standalone(1), and then a new pair must be configured as described above.

The index of the slot containing the board. The value for each board must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization.

The index of the port on the module.

The redundancy mode of the port. The possible values read, which report the redundancy mode of the port, are: standalone(1)...the port is not in any redundant pair. hwActive(2).....the port is the active companion in a hardware-redundant pair. hwStandby(3)....the port is the standby companion in a hardware-redundant pair. swActive(4).....the port is the active companion in a software-redundant pair. swStandby(5)....the port is the standby companion in a software-redundant pair. The values that can be written, which change the redundancy mode, are: standalone(1)...causes the software-redundant pair to be broken up. hwActive(2).....if the previous value was hwStandby(3), this value will cause the port to become the active port in the hardware-redundant pair (i.e., a switchover). hwStandby(3)....if the previous value was hwActive(2), this value will cause the port to become the standby port in the hardware-redundant pair (i.e., a switchover). swActive(4).....if the previous value was swStandby(5), this value will cause the port to become the active port in the software-redundant pair (i.e., a switchover). swStandby(5)....if the previous value was swActive(4), this value will cause the port to become the standby port in the software-redundant pair (i.e., a switchover). Notes: 1.) The value standalone(1) cannot be written to effect hardware-redundant pairs. Enumeration: 'swStandby': 5, 'hwStandby': 3, 'swActive': 4, 'hwActive': 2, 'standAlone': 1.

This object indicates port's redundancy status. The values are: other(1).........none of the following ok(2)............no fault localFault(3)....the local port has sensed a fault condition. remoteFault(4)...the remote port has sensed a fault condition and has signaled the local port accordingly. Either a localFault(3) or remoteFault(4) condition should cause a redundant port pair to switchover. Notes: If the redundant link is generating on 10BASE-FL without remote fault capability, the value remoteFault(4) will not be reported. Enumeration: 'other': 1, 'ok': 2, 'localFault': 3, 'remoteFault': 4.

This object reflects the real time status of the received data from the remote port. A value of snpxFLRemFltCpblPortUp(1) indicates that the remote port is capable of 10BASE-FL signaling, as well as SynOptics proprietary remote fault signaling. A remote fault on such a port is indicated by snpxRemFltCpblPortFault(5). A value of snpxFLFBRemFltCpblPortUp(2) indicates that the remote port is capable of 10BASE-FL, 10BASE-FB and SynOptics proprietary remote fault signaling. A remote fault on such a port is indicated by snpxRemFltCpblPortFault(5). A value of tenBaseFLPortUp(3) indicates that the remote port uses regular idle 10BASE-FL signaling, and is incapable of remote fault signaling. A value of tenBaseFBPortUp(4) indicates that the remote port uses 10BASE-FB synchronous signaling. A remote fault on such a port is indicated by tenBaseFBPortFault(6). A value of unknown(7) indicates that the remote signal received is none of the above. Enumeration: 'snpxFLRemFltCpblPortUp': 1, 'snpxFLFBRemFltCpblPortUp': 2, 'tenBaseFBPortFault': 6, 'unknown': 7, 'tenBaseFBPortUp': 4, 'tenBaseFLPortUp': 3, 'snpxRemFltCpblPortFault': 5.

The slot number of the other port which is in the redundant pair. In the case of a standalone port, a value of 0 will be returned. Note: This object is only writable for ports that support software-redundancy.

The port number of the other port which is in the redundant pair. In the case of a standalone port, a value of 0 will be returned. Note: This object is only writable for ports that support software-redundancy.

The switchover status of the redundant port pair. The following values can be written: timedSwitchover(2)...Immediately causes the active port to become the standby port, and the standby port to become the active port. Then once the value of s3EnetRedPortSwitchoverTime has elapsed to zero, the ports revert back to their orignal roles. The following values can be read: other(1).............The port is NOT undergoing a timed switchover. timedSwitchover(2)...The port is undergoing a timed switchover. Notes: 1.) When writing timedSwitchover(2) to this object, the SET request must also specify a value for the object s3EnetRedSwitchoverTime. 2.) Once the timed switchover has taken place, the value of this object reverts from timedSwitchover(2) to other(1). Enumeration: 'timedSwitchover': 2, 'other': 1.

The length of time before the ports making up the redundant port pair revert back to their orignal active or standby roles as defined before the timed switchover was setup. The value of this object is meaningful (i.e., non-zero) only when the redundant port pair is undergoing a timed switchover, which is indicated by the object s3EnetRedPortSwitchoverStatus having the value of timedSwitchover(2). This object may only be written in the same SET request that changes the object s3EnetRedPortSwitchoverStatus to timedSwitchover(2). Afterwards, it indicates the amount of time left before the timed switchover is completed, at which time another switchover occurs and s3EnetRedPortSwitchoverStatus is changed to other(1). This object has the value of zero if the port is not undergoing a timed switchover, or if the amount of time is unavailable.

The redundancy capability of the port: hwRedOnly(1).........hardware redundancy only. swRedOnly(2).........software redundacy only. notRedunCapable(3)...port not capable of being configured into a redundant port pair. A value of hwRedOnly(1) or swRedOnly(2) means that the port is capable of being configured into a redundant port pair. Enumeration: 'swRedOnly': 2, 'hwRedOnly': 1, 'notRedunCapable': 3.

The value of sysUptime when the last change in the redundant ports table was observed by the agent.

See s3AgentType Enumeration: 'm3314-ST': 4, 'm3138': 6, 'm3313': 2, 'other': 1, 'm3314M-ST': 5, 'm3313M': 3.

See AgentMdaHwVer

See s3AgentFwVer

See s3AgentSwMajor

See s3AgentSwMinor

See s3AgentStatus Enumeration: 'offline': 1, 'online': 2.

See s3AgentMode Enumeration: 'primary': 1, 'secondary': 2.

See s3AgentReset Enumeration: 'reset': 2, 'notreset': 1.

See s3AgentRestart Enumeration: 'notrestart': 1, 'restart': 2.

See s3AgentIpAddr

See s3AgentNetMask

See s3AgentDefaultGateway

See s3AgentBootServerAddr

See s3AgentBootFile

See s3AgentBootMode Enumeration: 'bootp': 2, 'eeprom': 1.

See s3AgentWriteEeprom Enumeration: 'writeEeprom': 2, 'notWriteEeprom': 1.

See s3AgentBaudRate

See s3AgentInitString

See s3AgentLocation

See s3AgentTrapReceiverTable

See s3AgentTrapReceiverEntry

See s3AgentTrapRcvrStatus Enumeration: 'other': 1, 'invalid': 2.

See s3AgentTrapRcvrNetAddress

See s3AgentTrapRcvrComm

See s3AgentAuthTrap Enumeration: 'enable': 2, 'disable': 1.

Table containing a list of all of the nodes that have been active during the aging interval that are currently connected to the network through this concentrator. This table is different from the FindNodes table in that this table is indexed using the slot, port, and MAC address attributes associated with the node. This allows a manager to get all nodes based on slot, slot-port, or slot-port-MAC.

List of nodes active on the concentrator and the slot and port the nodes are on.

The board number the node is on. Valid entries are 1-12.

The port number the node is on. Valid entries are 1-12.

This object contains the MAC address (i.e. the Ethernet address) of the node.

The status of the node. Determines whether the node has actively transmitted or not over the last 5 seconds. Enumeration: 'active': 1, 'inactive': 2.

The vendor type of the adapter seen on this port. If the vendor is unknown other(1) should be returned. Enumeration: 'other': 1, 'threeCom': 2.

The object is used determine how the node was added to this table. If the node was learned by listening to the network then on reads network(2) should be returned. If the node is another NMM or known concentrator device, then nmm(3) is returned. If the device's MAC address is unknown because of some unknown but legal configuration, then other(1) should be returned and s3EnetShowNodesMacAddress should return all zeros. If the node was entered into the AllowedNode list via management control, and was seen on a port that it was authorized to use, then authorized(4) should be returned. Enumeration: 'other': 1, 'network': 2, 'nmm': 3, 'authorized': 4.

The time used for aging of the nodes in tables s3EnetShowNodesTable and s3EnetFindNodesTable. Once a node has completely aged it will be removed from these tables. Note: Agents that implement the s3EnetSdTrafTable and s3EnetDsTrafTable tables and do not implement the the object s3EnetTrafAgeInterval (i.e., agents prior to version 5.3), also use s3EnetNodeAgeInterval to age the nodes in these two tables.

Table containing a list of all of the nodes that have been active during the aging interval that are currently connected to the network through this concentrator. This table is different than the ShowNodes table in that this table is index using only the MAC address attribute associated with the node. This allows a manager to be able to quickly determine if a node with a particular MAC address is located on this concentrator or not.

Entry in the table containing the slot, port and MAC address of a node connected to the Ethernet through this concentrator.

MAC address of node that this entry in the table is for.

The board that the node is connected through.

The port that the node is connected through.

Table containing a list of MAC addresses and the slot and ports that the MAC address is allowed to be heard on, in case the authorized node feature is turned on. If a MAC is allowed on any slot and port then the entry will have the slot=0 and the port=0. If the MAC address is allowed on a particular board then slot=allowed board and port=0. If the MAC is only allowed on one port then the entry will contain a slot value and port value between 1-12. Allowed nodes for LattisSecure ports must be configured for that specific port. The agent will reject an attempt to create a slot-level entry for slot=x, port=0, if the board in slot x is a LattisSecure Host Module. Only a single address may be configured for a LattisSecure port. Adding a second address (with the same LattisSecure slot-port number) to the table will cause the first address to be replaced with the new entry. A MAC address can only appear in the table one time. To determine when a station heard on the network must be verified in this table please read the complete description of the authorized node list feature as described with object S3EnetConcAuthStatus. Entries in this table may be downloaded via the CFG file or can be added via SNMP. All adds via SNMP will be lost when the system is reset.

Entry in the table containing a MAC address of a node that is allowed on the ethernet through this concentrator.

MAC address of node that this entry in the table is for.

The board that the node is allowed to be heard through. If this object is 0, then the MAC address is allowed on any board in the concentrator. In this case s3EnetAuthNodesPortIndex should also be 0. Otherwise, this object describes the slot that the MAC address of this entry is allowed to connect to.

The port that the node is allowed to be heard through. If this object is 0, then the MAC address of this entry is allowed to connect to any port on the board (if s3EnetAuthNodesSlotIndex is not 0) or if s3EnetAuthNodesSlotIndex is 0, then the MAC address is allowed to be heard from any port on the concentrator. Otherwise, this object specifies which port on the s3EnetAuthNodesSlotIndex this MAC address is allowed to be heard on.

The status of the AuthNodes entry. The primary use of this object is for modifying the AuthNodes table. It is also returned in the enetAuthViolation trap, in which case it indicates whether the violating MAC address was found in the AuthNodes table. Setting this entry to invalid(1) causes the entry to be deleted from the table. Setting a new entry with valid(2) causes the entry to be created in the table. The response to a get request or get-next request will always indicate a status of valid(2), since invalid entries are removed from the table. Enumeration: 'valid': 2, 'invalid': 1.

Maximun number of MAC address remembered by the agent on a per port basis, this number should be smaller than the maximum limit imposed by the agent.

A table of the NMM's in the flat network.

Table that contains information about NMMs that are in the same flat network as this NMM.

Slot that the NMM this entry is for can be found using the topology protocol. This is the slot from which a topology message was received.

Port that the NMM this entry is for can be found using the topology protocol. This is the port from which a topology message was received.

IpAddress of the NMM this entry is for. This is the IP address of the NMM that sent a topology message.

MAC Address of the NMM this entry is for.

Concentrator type of the NMM this entry is for. The enumerated values of this object are the same as defined in the common MIB for object s3ChassisType.

Concentrator backplane type of the NMM this entry is for. The enumerated values of this object are the same as defined in the common MIB for object s3ChassisBkplType.

Does this entry NMM exist in the same segment as this (the reporting) NMM. Enumeration: 'false': 2, 'true': 1.

Number of NMMs visible from the slot-port pair that this NMM is seen through.

The module type of the NMM that this entry is for. The values of this object are equivalent to those defined in the common MIB for object s3SlotModuleType.

Number of links through which NMMs are visible on this NMM.

If this NMM has detected any change of topology relative to itself it will set this object to change(1), otherwise noChange(2) will be returned. Enumeration: 'noChange': 2, 'changed': 1.

Hello Time interval used in the topology update protocol.

Encoded octet string of the s3EnetTopNmmTable.

Encoded octet string of the s3EnetTopNmmTable. Instance returned in Response PDU: On GETs: instance specified is the instance returned. On GET-NEXTs: instance returned is the instance of the last record contained in the octet string.

Encoded octet string. On reads it contains an integral number of s3EnetTopNmmEntry records. All entries are the same size. Values are specified in SynOptics technical documents.

A table of Bridges that are in the same segment as this NMM network.

Table that contains information about Bridges that are in the same segment as this NMM.

IP address of the bridge from the Hello PDU.

Bridge Number assigned to this bridge.

MAC Address of this bridge.

Kind of bridge this entry represents. Enumeration: 'other': 1, 'remoteSyn3Port': 3, 'localSyn2Port': 2, 'etherSwitch': 4.

Current operational status of this bridge. Enumeration: 'active': 2, 'standby': 3, 'other': 1.

Slot on the concentrator that the Hello PDU from the bridge was received.

Port on concentrator that the Hello PDU from the bridge was received.

Module type of the board that the Hello PDU from the Bridge was received.

Port Number on the Bridge from which the Hello PDU was sent.

Type of the Port on the Bridge from which the Hello PDU was sent. Enumeration: 't1': 6, 'tokenRing16': 4, 'ether': 2, 'tokenRing4': 3, 'other': 1, 'fddi': 5.

Status of the Port on the Bridge from which the Hello PDU was sent. Enumeration: 'active': 2, 'standby': 3, 'other': 1.

Contains one of the 2 companion MAC addresses of the remote bridge. If this entry is for a local bridge or is unknown, then this object should contain the MAC address of 0:0:0:0:0:0.

Contains one of the 2 companion MAC addresses of the remote bridge. If this entry is for a local bridge or is unknown, then this object should contain the MAC address of 0:0:0:0:0:0.

Encoded octet string of the s3EnetTopBridgeTable.

Encoded octet string of the s3EnetTopBridgeTable. Instance returned in Response PDU: On GETs: instance specified is the instance returned. On GET-NEXTs: instance returned is the instance of the last record contained in the octet string.

Encoded octet string. On reads it contains an integral number of s3EnetTopBridgeEntry records. All entries are the same size. Values are specified in SynOptics technical documents.

The value of sysUpTime the last time an entry in the NMM topology table was added, deleted, or modified. If the NMM topology table has not changed since cold/warm start of the agent, then the value is zero.

The value of sysUpTime the last time an entry in the bridge topology table was added, deleted, or modified. If the bridge topology table has not changed since cold/warm start of the agent, then the value is zero.

The table of thresholds. There are three kinds of thresholds supported in the threshold table: port thresholds, slot thresholds, and concentrator thresholds. The object s3EnetThreshObject in the threshold table is used to specify the kind of threshold for the table entry. When the value of the object s3EnetThreshObject is port(4), the threshold entry applies to a specific port, which is identified by the value of the objects s3EnetThreshSlot and s3EnetThreshPort. The port must be on the same segment as the NMM in order for the NMM to monitor the threshold. When the value of the object s3EnetThreshObject is slot(3), the threshold entry applies to a specific slot, which is identified by the value of the object s3EnetThreshSlot. The slot must be on the same segment as the NMM in order for the NMM to monitor the threshold. When the value of the object s3EnetThreshObject is concentrator(2), the threshold entry applies to the segment the NMM is connected to within the concentrator.

A row in the Ethernet Threshold Table. The following columns must be specified in a SNMP SET request to create a row in the table for each of the three kinds of thresholds (each name is prefixed by s3EnetThresh): PORT SLOT CONCENTRATOR ========= ========= ============ Status=(1) Status=(1) Status=(1) Object=(4) Object=(3) Object=(2) Slot Slot Port Type Type Type Condition Condition Condition SetValue SetValue SetValue Action Action Action *Duration Duration Duration with the object s3EnetThreshStatus set to the value addActive(1). Notes: 1.) The value of s3EnetThreshObject selects the kind of threshold for the row (i.e., for port thresholds it is set to the value port(4), for slot thresholds it is set to the value slot(3), and for concentrator thresholds it is set to the value concentrator(2)). 2.) The object s3EnetThreshPort is not used for creating slot level thresholds, and is set to 0 by the agent when the row is created. 3.) The objects s3EnetThreshPort and s3EnetThreshSlot are not used for creating concentrator level thresholds, and are both set to 0 by the agent when the row is created. 4.) The value of s3EnetThreshDuration is ignored for port level link status thresholds. To delete a row in the table, the object s3EnetThreshStatus needs to be specified in a SNMP SET request with its value equal to delDead(2).

The index into the threshold table.

The status of the threshold. The possible values for a write are: addActive(1)...If the entry does not exist, the entry is created as long as the other necessary objects are in the SNMP SET request. If the entry does exist and is inactive, it is activated. delDead(2).....Causes the entry to be deleted from the table. It could take 5 seconds after delDead(2) is written to actually delete the entry due to task scheduling. The possible values for a read are: addActive(1)...This threshold entry is active. delDead(2).....This threshold entry is inactive and will be deleted in 5 seconds or less. Enumeration: 'delDead': 2, 'addActive': 1.

Specifies the part of the concentrator the threshold applies. The possible values are: other(1)..........Unknown threshold (error) concentrator(2)...The threshold applies to the segment the NMM is connected to within the concentrator slot(3)...........The threshold applies to a specific slot in the concentrator identified by s3EnetThreshSlot port(4)...........The threshold applies to a specific port in the concentrator identified by s3EnetThreshSlot and s3EnetThreshPort All values are read-write with the exception of other(1), which is read-only. See the description of the object s3EnetThreshType for the explanation of which thresholds are applicable to port(4), slot(3), and concentrator(2). Enumeration: 'concentrator': 2, 'slot': 3, 'other': 1, 'port': 4.

If s3EnetThreshObject is slot(3) or port(4), then this contains a valid slot. Otherwise, the contents of this object is meaningless.

If s3EnetThreshObject is port(4), then this contains a valid port. Otherwise, the contents of this object is meaningless.

Determines which type of threshold applies to this entry. The possible values that can be read and written are listed below. Applicable to ALL Thresholds ============================================== goodBytes(2).........Count of good bytes goodPkts(3)..........Count of good packets badPkts(4)...........Count of bad packets crcPkts(5)...........Count of packets with CRC errors misaligned(6)........Count of misaligned packets runtPkts(7)..........Count of runt packets fragPkts(8)..........Count of fragmented packets tooLong(9)...........Count of too long packets collision(10)........Count of collisions lateColls(11)........Count of late collisions multicast(13)........Count of multicast packets broadcast(14)........Count of broadcast packets shortEvents(15)......Count of short events dataRateMismatches(17).... Count of data rate mismatches networkErrors(18)......... Count of short events, late collisions, and data rate mismatches badToGoodPktRatio(19)..... Ratio of bad packets to good packets, where bad packets is the sum of packets with alignment errors, packets with FCS errors, runt packets, and packets that are too long netErrToGoodPktRatio(20)... Ratio of network error packets to good packets, where network error packets is the sum of short event packets, packets with late collisions, and data rate mismatch packets colltoGoodPktRatio(21)..... Ratio of collision packets to good packets Applicable ONLY to Port Thresholds ============================================== linkStatus(12).......Status of the link srcAddrChanges(16)...Count of source address changes Applicable ONLY to Concentrator Thresholds ============================================== collBackOffErr(22)...Count of collision backoff errors Note: 1.) The value other(1) can only be read and it indicates the entry has an invalid or unknown threshold type. Enumeration: 'badPkts': 4, 'dataRateMismatches': 17, 'collBackOffErr': 22, 'collision': 10, 'badToGoodPktRatio': 19, 'networkErrors': 18, 'fragPkts': 8, 'misaligned': 6, 'crcPkts': 5, 'other': 1, 'shortEvents': 15, 'colltoGoodPktRatio': 21, 'multicast': 13, 'broadcast': 14, 'netErrToGoodPktRatio': 20, 'goodBytes': 2, 'linkStatus': 12, 'runtPkts': 7, 'srcAddrChanges': 16, 'tooLong': 9, 'goodPkts': 3, 'lateColls': 11.

Conditions that set off the threshold. The possible values are: other(1)........None of the following crossValue(2)...The value of s3EnetThreshActualValue crosses the value of s3EnetThreshSetValue (i.e., either from lower to higher or from higher to lower) overValue(3)....The value of s3EnetThreshActualValue is greater than s3EnetThreshSetValue overRate(4).....The rate of s3EnetThreshActualValue/sec is greater than s3EnetThreshSetValue/sec linkOn(5).......The link status of the port has changed to ON linkOff(6)......The link status of the port has changed to OFF overRatio(7)....The ratio in s3EnetThreshActualValue is greater than s3EnetThreshSetValue. Both values are in units of 0.01% (i.e., 100 equals 1.0%) The values that the object s3EnetThreshCondition can have is actually dependent on the value of the object s3EnetThreshType. The table below shows the valid combinations between the two objects. If s3EnetThreshType Allowed Values For Is Equal To s3EnetThreshCondition Are =================== ========================= goodBytes(2) 2, 3, 4 goodPkts(3) 2, 3, 4 badPkts(4) 2, 3, 4 crcPkts(5) 2, 3, 4 misaligned(6) 2, 3, 4 runtPkts(7) 2, 3, 4 fragPkts(8) 2, 3, 4 tooLong(9) 2, 3, 4 collision(10) 2, 3, 4 lateColls(11) 2, 3, 4 linkStatus(12) 5, 6 multicast(13) 2, 3, 4 broadcast(14) 2, 3, 4 shortEvents(15) 2, 3, 4 srcAddrChanges(16) 2, 3, 4 dataRateMismatches(17) 2, 3, 4 networkErrors(18) 2, 3, 4 badToGoodPktRatio(19) 7 netErrToGoodPktRatio(20) 7 colltoGoodPktRatio(21) 7 collBackOffErr(22) 2, 3, 4 When the condition specified is crossValue(2) or overValue(3), the value of s3EnetThreshActualValue is accumulated from the beginning of the duration window and is checked every 5 seconds. When the condition specified is overRate(4) or overRatio(5), and the duration is less than or equal to 5 seconds, the value of s3EnetThreshActualValue is based on the data accumulated during the 5 second sampling period. When the condition specified is overRate(4) or overRatio(5), and the duration is greater than 5 seconds, the value of s3EnetThreshActualValue is based on the data accumulated during the entire duration window. Enumeration: 'overRate': 4, 'overValue': 3, 'overRatio': 7, 'linkOff': 6, 'other': 1, 'linkOn': 5, 'crossValue': 2.

Threshold setting value.

Current value of the threshold counter. This object is set to zero at the begining of each duration window.

Determines what action is to take place if the threshold condition occurs. The possible values that can be read and written are listed below. Applicable to ALL Thresholds ============================================== noAction(2)............Take no action sendTrap(3)............Send a trap Applicable ONLY to Port Thresholds ============================================== partSlot(6)............Partition the slot identified by s3EnetThreshSlot partSlotPort(7)........Partition the port identified by s3EnetThreshSlot and s3EnetThreshPort Applicable ONLY to Slot Thresholds ============================================== trapPartSlot(10).......Send a trap and partition the slot identified by s3EnetThreshSlot trapPartSlotPort(11)...Send a trap and partition the port identified by s3EnetThreshSlot and s3EnetThreshPort Notes: 1.) The value other(1) can only be read and it indicates the entry has an invalid or unknown threshold action. 2.) The values res4(4), res5(5), res8(8), and res9(9) are no longer used and should never be read or written. The timing and frequency of the action taken when the threshold condition is met is dependent upon the type of condition (i.e., s3EnetThreshCondition) and the length of the duration window (i.e., s3EnetThreshDuration). If the threshold conditionis crossValue(2), the action will be taken only ONCE during the duration window at the sampling period the condition is first met. If the threshold condition is overValue(3), linkOn(5), or linkOff(6), the action will be taken at each sampling period the condition is met until the end of the duration window. If the threshold condition is overRate(4) or overRatio(5) the action will be taken only ONCE at the end of the duration window if the condition is met. Enumeration: 'res8': 8, 'res9': 9, 'trapPartSlotPort': 11, 'res4': 4, 'res5': 5, 'trapPartSlot': 10, 'partSlot': 6, 'sendTrap': 3, 'partSlotPort': 7, 'noAction': 2, 'other': 1.

Counter for how many times the selected threshold has reached its setting value.

Length of window over which threshold counts are summed, specified in intervals of 500 TimeTicks (i.e., 5 seconds). This window is broken down into 5 second sampling periods for purposes of checking the threshold conditions, and determining when the actions specified need to take place when the condition occurs. If this object is written with a value that is not evenly divisible by 500, the agent will internally round the value up to the closest integral of 500 before it is used in threshold calculations (i.e., a value of 12 can be written, but will be interpreted as 15). Notes: 1.) A value of zero indicates an infinite duration window if the value of s3EnetThreshCondition is crossValue(2) or overValue(3). 2.) If the value of s3EnetThreshCondition is overRate(4) or overRatio(5), a value of zero is equivalent to a duration window of 5 seconds. 3.) If the value of s3EnetThreshType is linkStatus(12), this value of this object is ignore and assumed to be infinite.

The maximum number of entries in the table s3EnetThreshTable.

This table contains a list of entries which provide SA-DA traffic information. Specifically frame and byte counter values are provided per unique SA-DA pair. The indexing scheme of this table allows an SA list to be retrieved using GETNEXT. An SA list is a list of entries that have a common SA, however, different DAs.

An entry in the SA-DA traffic table.

Source MAC address.

Destination MAC address.

The number of good frames received by the concentrator for a SA-DA pair.

The number of bytes in good frames received by the concentrator for a SA-DA pair.

This table contains a list of entries which provide DA-SA traffic information. Specifically frame and byte counter values are provided per unique DA-SA pair. The indexing scheme of this table allows a DA list to be retrieved using GETNEXT. A DA list is a list of entries that have a common DA, however, different SAs.

An entry in the DA-SA table.

Destination MAC address.

Source MAC address.

The number of good frames received by the concentrator for a DA-SA pair.

The number of bytes in good frames received by the concentrator for a DA-SA pair.

This table contains a list of entries for the 'paged' Traffic Matrix table.

A 'paged' entry in the Traffic Matrix table.

A specific page in the Traffic Matrix table.

This OCTET STRING contains up to 20 valid Traffic Matrix table entries. The entries will not be in any logical order. Each entry consists of a 20-byte octet string including a 6-byte source MAC address, a 6-byte destination MAC address, a received good frame count, and a byte count in good frames received. The counters are 4-bytes each where the first one is high-order byte and the last one is low-order byte.

The time used for aging of the nodes in tables s3EnetSdTrafTable and s3EnetDsTrafTable. Once a node has completely aged it will be removed from these tables. Note: Agents that do not implement this object (i.e., agents prior to version 5.3) use the object s3EnetNodeAgeInterval to perform this function.

This table provides a list of entries, each entry providing information related to frame MAC level error conditions per port. This table is conceptually an extension to the s3EnetPortTable and is only implemented by the 3313S and 3314S NMMs.

An entry in the Plus Port table.

A unique value for each board. Its value ranges between 1 and 12. (This is the slot number.)

A unique value for each port. Its value typically ranges between 1 and 12.

This contains a count of fragments received by the board between 80-512 bits (64 bytes), inclusively, with invalid FCS or alignment errors. (These commonly represent collision fragments, and are not errors. Collision fragments were called FragErrors in the rev 3.x MIB, and were counted only on a per-board basis.)

This contains a count of fragments received by the port shorter than 80 bits.

This contains a count of times the ports on the board have autopartitioned due to excessive collisions (more than 32 consecutive collisions). This count is an approximation and may be less than the total count.

This contains a count of the occurrences of out of spec bit rates. This indicates the number of times FIFO buffer over-runs or underruns due to transmission rate errors.

This contains a count of the times that MAU jabber lockup protection (MJLP) was invoked because transmission of data from this port exceeded 5 msec in duration. This information can be useful in identifying faulty stations.

This is the source address of the last packet received through this port.

This is the number of times that the s3EnetPortLastSrcAddr object for this has changed.

This table provides a list of entries, each entry providing information related to frame MAC level error conditions per board. This table is conceptually an extension to the s3EnetboardTable and is only implemented by the 3313S and 3314S NMMs.

An entry in the Plus Board table.

The board number part of an index.

This contains a count of fragments received by the board between 80-512 bits (64 bytes), inclusively, with invalid FCS or alignment errors. (These commonly represent collision fragments, and are not errors. Collision fragments were called FragErrors in the rev 3.x MIB, and were counted only on a per-concentrator basis.)

This contains a count of fragments received by the board shorter than 80 bits.

This contains a count of times the ports on this board have been autopartitioned due to excessive collisions (more than 32 consecutive collisions). This count is an approximation and may be less than the total count.

This contains a count of the occurrences of out of spec bit rates. This indicates the number of times FIFO buffer over-runs or underruns due to transmission rate errors.

This contains a count of the times that MAU jabber lockup protection (MJLP) was invoked because transmission of data from a port on this board exceeded 5 msec in duration. This information can be useful in identifying faulty stations.

This contains a count of fragments received by the concentrator shorter than 80 bits.

This contains a count of times the ports on this concentrator have been autopartitioned due to excessive collisions (more than 32 consecutive collisions). This count is based on a one-bit counter (flag) per port in the host modules, and will not always represent the total count.

This contains a count of the occurrences of out of spec bit rates. This indicates the number of times FIFO buffer over-runs or underruns due to transmission rate errors.

This contains a count of the times that MAU jabber lockup protection (MJLP) was invoked because transmission of data from a port on this concentrator exceeded 5 msec in duration. This information can be useful in identifying faulty stations.

This contains a total concentrator count of the collision events that occur during the normal collision window (i.e., the collisions is not a late collision) and do not have a runt error.

This table provides a list of entries, each entry providing information related to frame sizes of packets received on a port. The variables defined for the entries are only supported by 3313S and 3314S NMM.

An entry in the FrSize Port table.

A unique value for each board. Its value ranges between 1 and 12. (This is the slot number.)

A unique value for each port. Its value typically ranges between 1 and 12.

This contains a count of frames received by the port that are in the range of 64 octets to 127 octets, inclusive.

This contains a count of frames received by the port that are in the range of 128 octets to 255 octets, inclusive.

This contains a count of frames received by the port that are in the range of 256 octets to 511 octets, inclusive.

This contains a count of frames received by the port that are in the range of 512 octets to 1023 octets, inclusive.

This contains a count of frames received by the port that are in the range of 1024 octets to 1518 octets, inclusive.

This table provides a list of entries, each entry providing information related to frame MAC level error conditions per board. The variables defined for the entries are only supported by 3313S and 3314S NMMs. The use of any variable in this table for other NMMs will cause the NMMs to return noSuchName error status in the response.

An entry in the FrSize Board table.

A unique value for each board. Its value ranges between 1 and 12. (This is the slot number.)

This contains a count of frames received by the board that are in the range of 64 octets to 127 octets, inclusive.

This contains a count of frames received by the board that are in the range of 128 octets to 255 octets, inclusive.

This contains a count of frames received by the board that are in the range of 256 octets to 511 octets, inclusive.

This contains a count of frames received by the board that are in the range of 512 octets to 1023 octets, inclusive.

This contains a count of frames received by the board that are in the range of 1024 octets to 1518 octets, inclusive.

This contains a count of frames received by the concentrator that are in the range of 64 octets to 127 octets, inclusive.

This contains a count of frames received by the concentrator that are in the range of 128 octets to 255 octets, inclusive.

This contains a count of frames received by the concentrator that are in the range of 256 octets to 511 octets, inclusive.

This contains a count of frames received by the concentrator that are in the range of 512 octets to 1023 octets, inclusive.

This contains a count of frames received by the concentrator that are in the range of 1024 octets to 1518 octets, inclusive.

This table provides a list of entries, each entry providing information related to packet protocol type distributions per port. The variables defined for the entries are only supported by 3313S and 3314S NMMs. The use of any variable in this table for other NMMs will cause the NMMs to return noSuchName error status in the response.

An entry in the Proto Port table.

A unique value for each board. Its value ranges between 1 and 12. (This is the slot number.)

A unique value for each port. Its value typically ranges between 1 and 12.

This contains a count of frames received by the port that are of 802.3 type.

This contains a count of frames received by the port that are of Ethernet type.

This contains a count of frames received by the port that are of types not counted by individual counters below.

This contains a count of frames received by the port that are of SNA type.

This contains a count of frames received by the port that are of IP type.

This contains a count of frames received by the port that are of ISO type.

This contains a count of frames received by the port that are of ARP type.

This contains a count of frames received by the port that are of DECIV type.

This contains a count of frames received by the port that are of DECLAT type.

This contains a count of frames received by the port that are of EtherTalk type.

This contains a count of frames received by the port that are of XNS type.

This contains a count of frames received by the port that are of IPX type.

This contains a count of frames received by the port that are of DEC LAVC type.

This contains a count of frames received by the port that are of NETBIOS type.

This contains a count of frames received by the port that are of Bridge Spanning Tree type.

This table provides a list of entries, each entry providing information related to packet protocol type distribution per board. The variables defined for the entries are only supported by 3313S and 3314S NMMs. The use of any variable in this table for other NMMs will cause the NMMs to return noSuchName error status in the response.

An entry in the Proto Board table.

A unique value for each board. Its value ranges between 1 and 12. (This is the slot number.)

This contains a count of frames received by the board that are of 802.3 type.

This contains a count of frames received by the board that are of Ethernet type.

This contains a count of frames received by the board that are of types not specified below.

This contains a count of frames received by the board that are of SNA type.

This contains a count of frames received by the board that are of IP type.

This contains a count of frames received by the board that are of ISO type.

This contains a count of frames received by the board that are of ARP type.

This contains a count of frames received by the board that are of DECIV type.

This contains a count of frames received by the board that are of DECLAT type.

This contains a count of frames received by the board that are of EtherTalk type.

This contains a count of frames received by the board that are of XNS type.

This contains a count of frames received by the board that are of IPX type.

This contains a count of frames received by the board that are of DEC LAVC type.

This contains a count of frames received by the board that are of NETBIOS type.

This contains a count of frames received by the board that are of Bridge Spanning Tree type.

This contains a count of frames received by the concentrator that are of 802.3 type.

This contains a count of frames received by the concentrator that are of Ethernet type.

This contains a count of frames received by the concentrator that are of types not specified below.

This contains a count of frames received by the concentrator that are of SNA type.

This contains a count of frames received by the concentrator that are of IP type.

This contains a count of frames received by the concentrator that are of ISO type.

This contains a count of frames received by the concentrator that are of ARP type.

This contains a count of frames received by the concentrator that are of DECIV type.

This contains a count of frames received by the concentrator that are of DECLAT type.

This contains a count of frames received by the concentrator that are of EtherTalk type.

This contains a count of frames received by the concentrator that are of XNS type.

This contains a count of frames received by the concentrator that are of IPX type.

This contains a count of frames received by the concentrator that are of DEC LAVC type.

This contains a count of frames received by the concentrator that are of NETBIOS type.

This contains a count of frames received by the concentrator that are of Bridge Spanning Tree type.

The current number of entries in table s3EnetHostTable.

The value of sysUpTime when the last entry was deleted from table s3EnetHostTable due to a shortage of resources. If no deletions have occurred, then the value is zero.

A Table containing MAC/Network address pairs that have been detected on the segment.

A row in the table of MAC/Network address pairs. Entries can not be created or deleted via SNMP operations. New entries are added when a new MAC/Network address pair is detected. An entry is removed to add a new entry when the table is full. The entry that is removed is the one that has been least recently observed.

The index of the MAC/Network address pair. The value is between 1 and N, where N is the value of s3EnetHostTableSize. The association of this index to a pair may change when a pair is removed from the table due to a resource shortage. s3EnetHostLastDeleteTime must be monitored to determine when this condition has occured.

The relative ordering of the MAC/Network adddress pair. There is a global value that starts at 1 and increases by one for each observation of an address pair. When the maximum value of 65535 is reached, the next value will be 1. The global value is used to update this object each time the MAC/Network address pair is observed (and when the entry is initially created). Since the global value starts over again after it reaches its maximum value, there may be more than one entry that has the same value.

The network address (in network order) of the MAC/Network address pair.

The type of address that is stored in the object s3EnetHostNetAddr for this entry. The values are: other(1)...Unknown type ip(2)......IP address ipx(3).....IPX address Enumeration: 'ip': 2, 'ipx': 3, 'other': 1.

The MAC address (in canonical order) of the MAC/Network address pair.

The board index that the host is connected through.

The port index that the host is connected through.

Indicates the method that was used to discover the MAC/Network address pair. The methods that can be used for discovery are shown below. other(1).........Indicates an unknown discovery method. arpRequest(2)....Indicates that ARP request packets were used for discovery. arpResponse(3)...Indicates that ARP response packets were used for discovery. ripRequest(4)....Indicates that RIP request packets were used for discovery. ripResponse(5)...Indicates that RIP response packets were used for discovery. Enumeration: 'arpRequest': 2, 'ripRequest': 4, 'other': 1, 'arpResponse': 3, 'ripResponse': 5.

The value of sysUpTime when the MAC/Network address pair was last observed on the segment.