SnetSwitch-MIB
AI MIB Summary
Standard SNMP MIB module defining data structures for SnetSwitch-MIB.
114
Objects
Active
Status
4
Dependencies
Imported Objects
Objects
114 total| Object Name |
|---|
tandem OBJECT IDENTIFIER .1.3.6.1.4.1.169 |
RFC1155-SMI Unknown .1.3.6.1.4.1.169 |
serverNet OBJECT IDENTIFIER .1.3.6.1.4.1.169.8 |
snetSwitchLinkAliveChangeThe switch has detected a change in the status of a port.
Possible Cause / Solution:
If Port is nonfunctional,
Disconnected, loose or defective SAN Cable: Reattach or replace cable.
Distant switch or node powered off: apply power to switch or node.
Distant daughter card defective: replace defective daughter card.
If Port is functional,
Port is now active: No action necessary.
If Port is intermittent,
Intermittent problems could be caused by a defective switch, cable or
daughter card. Replace components until problem is isolated. TRAP-TYPE .1.3.6.1.4.1.169.8.0.100 |
snetSwitchNeighborValidationFailedA ServerNet Switch failed neighbor validation on one of its ports.
The offending node will not be able to receive or transmit
ServerNet data packets until the situation is corrected.
Possible Cause / Solution:
Ports not configured: If a port is not configured or disabled,
this event is generated whenever the topology is changed, or
firmware is updated. The snetSwitchNeighborID will indicate that
the link is down with LD. If the snetSwitchNeighborID is AF, this
indicates the specified port is disabled and assumed failed.
If the specified port is not configured, this event may be ignored.
Bad Node: Run diagnostics to validate offending nodes.
Incorrect cabling: verify cabling and correct if necessary.
Incorrect configuration: switch configruation may be incorrect.
Reconfigure switch.
Node not added to SAN: Offending node may not have been added to
the SAN. Run ServerNet II Administrative Utility to add node.
Incorrect SAN installation: Offending node may not have been correctly
added to SAN. Run Administrator GUI to verify status and add if
necessary.
To force the switch to rerun neighbor checks, the user may have to
manually cycle the power on the offending node. TRAP-TYPE .1.3.6.1.4.1.169.8.0.101 |
snetSwitchLinkLevelErrorServerNet Switch has detected link level errors.
Possible Cause / Solution:
Bad node: Run diagnostics to validate offending nodes are
operating correctly.
Loose cable: Check cable connections.
Bad cable: Check for link error and replace cable.
Incorrect configuration: Switch configuration may be incorrect.
Check EFIFO register to make sure it is set correctly for
cable type/length. Reconfigure switch if necessary.
Blabbering Node: Run diagnostics to ensure that nodes at both
ends of the cable are communicating properly. Replace if necessary. TRAP-TYPE .1.3.6.1.4.1.169.8.0.102 |
snetSwitchPacketLevelErrorServerNet Switch has detected packet level errors.
Possible Cause / Solution:
Bad node: Run diagnostics to validate offending nodes are
operating correctly.
Loose cable: Check cable connections.
Bad cable: Check for link error and replace cable.
Incorrect configuration: Switch configuration may be incorrect.
Check router table to make sure it is set. Reconfigure switch
if necessary.
Blabbering Node: Run diagnostics to ensure that nodes at both
ends of the cable are communicating properly. Replace if necessary.
Probing node: A node may be trying to break into the network.
Isolate the node and verify SAN membership. TRAP-TYPE .1.3.6.1.4.1.169.8.0.103 |
snetSwitchIBCErrorServerNet Switch has detected IBC errors.
Possible Cause / Solution:
Firmware upgrade or Configuration change: This event can be
safely ignored if preceding events indicate a firmware upgrade
or configuration change caused the event to be generated.
Bad node: Run diagnostics to validate offending nodes are
operating correctly.
Loose cable: Check cable connections.
Bad cable: Check for link error and replace cable.
Incompatible software version: Ensure that compatible versions
of software and firmware are installed on the offending nodes.
Blabbering node: Run diagnostics to ensure that nodes at both
ends of the cable are communicating properly. Replace if necessary.
Probing node: A node may be trying to break into the network.
Isolate the node and verify SAN membership.
Switch ownership may be incorrect: Check ownership; cycle power on
the offending switch to cause ownership update. TRAP-TYPE .1.3.6.1.4.1.169.8.0.104 |
snetSwitchAccessViolationThe switch has detected a request to or from an invalid id.
Possible Cause / Solution:
Blabbering node: Run diagnostics to ensure that nodes at both
ends of the cable are communicating properly. Replace if necessary.
Probing node: A node may be trying to break into the network.
Isolate the node and verify SAN membership.
Switch ownership may be incorrect: Check ownership; cycle power on
the offending switch to cause ownership update. TRAP-TYPE .1.3.6.1.4.1.169.8.0.105 |
snetSwitchOwnerChangeServerNet Switch Primary Administrative node change.
Possible Cause / Solution:
Primary node failed over: If this was by user request, this is a notification
only and no action is needed. Refer to snetSwitchSANManFailover for other
possibilities.
Administrator changed primary Administrative node: Notification only. No action
is necessary. TRAP-TYPE .1.3.6.1.4.1.169.8.0.106 |
snetSwitchFirmwareUpgradeA firmware upgrade has been performed on the specified switch.
Possible Cause / Solution:
Switch firmware has been upgraded. Notification only. No action
in needed. TRAP-TYPE .1.3.6.1.4.1.169.8.0.107 |
snetSwitchSANManFailoverAdministrative node failover has been detected.
The type of failure detected is reflected in the event type.
Possible Cause / Solution:
Primary or backup administrative node has failed: if powered off, apply power.
If hung, reboot node. If doing maintenance, this is a notification
message only. Restart node when maintenance is complete.
Backup administrative node not configured: use the ServerNet II Administrative Utility
to define a backup. TRAP-TYPE .1.3.6.1.4.1.169.8.0.108 |
snetSwitchTopologyConfigUpdateConfiguration of the ServerNet topology has changed.
Possible Cause / Solution:
Switch or end node configuration has been updated. Notification only,
no action required. May also be generated when switch firmware is upgraded or
new primary or backup nodes are designated. TRAP-TYPE .1.3.6.1.4.1.169.8.0.109 |
snetSwitchFanFailureServerNet Switch detected a fan failure. The power module should be
replaced immediately to prevent switch component damage.
Possible Cause / Solution:
A switch fan has failed: replace switch power module to prevent switch
component damage. TRAP-TYPE .1.3.6.1.4.1.169.8.0.110 |
serverNetSwitch OBJECT IDENTIFIER .1.3.6.1.4.1.169.8.3 |
snetSwitchNetworkData OBJECT IDENTIFIER .1.3.6.1.4.1.169.8.3.1 |
snetSwitchTotalThe number of ServerNet Switches (regardless of state)
known in the network. X and Y fabric switches are
considered separate switches in this Total count.ro INTEGER .1.3.6.1.4.1.169.8.3.1.1 |
snetSwitchRefreshTimeSpecifies the minimum time in seconds between refreshes
of Mib data. Mib data is refreshed each time it is requested
unless the refresh interval time has not yet been reached.
If the specified time interval has not elapsed, the mib data
will be retrieved from cache. Minimum time is 5 seconds.
Default is 60 seconds. Changing this to a low value can have
a negative impact on performance. Changing this to a high
value could allow mib data to become outdated.rw INTEGER .1.3.6.1.4.1.169.8.3.1.2 |
snetSwitchMibRevMajorThe Major Revision level of the Switch MIB.
A change in the major revision level represents a major change
in the architecture of the MIB. A change in the major revision
level may indicate a significant change in the information
supported and/or the meaning of the supported information.
Correct interpretation of data may require a MIB document with
the same major revision level.ro INTEGER .1.3.6.1.4.1.169.8.3.1.3 |
snetSwitchMibRevMinorThe Minor Revision level of the Switch MIB.
A change in the minor revision level may represent some minor
additional support, no changes to any pre-existing information
has occurred.ro INTEGER .1.3.6.1.4.1.169.8.3.1.4 |
snetSwitchIDTableTable containing the Switch IDs of all switches
known in the network. SEQUENCE OF SnetSwitchIDEntry .1.3.6.1.4.1.169.8.3.1.5 |
snetSwitchIDEntryEntry in switch table SnetSwitchIDEntry .1.3.6.1.4.1.169.8.3.1.5.1 |
snetSwitchIDIndexIndex in Switch ServerNet ID Entry Table.ro INTEGER .1.3.6.1.4.1.169.8.3.1.5.1.1 |
snetSwitchIDSwitch ID. The switch id is displayed
as a hexidecimal value.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.169.8.3.1.5.1.2 |
snetSwitchTypeIdentifies the Switch type. Switch can be either a
6-port or 12-port switch.ro Enumeration .1.3.6.1.4.1.169.8.3.1.5.1.3 |
snetSwitchSANMapTableTable containing the System Area Network map information.
This table has an entry for each switch in the network as
indexed by the snetSwitchIDIndex from the snetSwitchIDtable.
There is a separate entry for each port defined on
the switch. SEQUENCE OF SnetSwitchSANMapEntry .1.3.6.1.4.1.169.8.3.1.6 |
snetSwitchSANMapEntryEntry in SAN Map table. SnetSwitchSANMapEntry .1.3.6.1.4.1.169.8.3.1.6.1 |
snetSwitchSANMapPortIndexIdentifies the switch port number.ro INTEGER .1.3.6.1.4.1.169.8.3.1.6.1.1 |
snetSwitchSANNodeTypeIdentifies the type of the Node connected to the switch.
Valid values are
Unknown(1),
End Node(2),
Auto-Configured IO(3),
Manual-Configured IO(4),
Switch(5).ro Enumeration .1.3.6.1.4.1.169.8.3.1.6.1.2 |
snetSwitchSANNodeStateIdentifies the current state of the Node connected to the
switch. Valid values are
Unconfigured(1),
Configured(2).ro Enumeration .1.3.6.1.4.1.169.8.3.1.6.1.3 |
snetSwitchSANNodeDomainIdentifies the domain the node belongs to. If the port
is not configured, Domain will be blank.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.169.8.3.1.6.1.4 |
snetSwitchSANNodeIDFor end nodes, this is the Node ID. For switches, this is
a Switch ID. If port is not configured, NodeID will be 0.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.169.8.3.1.6.1.5 |
snetSwitchSANNodeNameThe ServerNet node name. If the port is not configured,
NodeName will be blank.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.169.8.3.1.6.1.6 |
snetSwitchSANNodeFabricIdentifies the X or Y Fabric this node connects to.
X Fabric(1),
Y Fabric(2),
Both Fabrics(3),
Not Defined(4).ro Enumeration .1.3.6.1.4.1.169.8.3.1.6.1.7 |
snetSwitchSANNodeManufacturingIDThe Manufacturing ID of connected switch or node.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.169.8.3.1.6.1.8 |
snetSwitchSANNodePartNumberPart Number of connected switch or node.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.169.8.3.1.6.1.9 |
snetSwitchSANNodeSerialNumberSerial Number of connected switch or node.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.169.8.3.1.6.1.10 |
snetSwitchTrapEnables OBJECT IDENTIFIER .1.3.6.1.4.1.169.8.3.1.7 |
snetSwitchLinkAliveTrapEnableEnables Link Alive Trap generation. Asynchronous events
can be generated by the switch whenever a change in
link alive is detected.
Valid values are
off(0),
on(1) (default).rw INTEGER .1.3.6.1.4.1.169.8.3.1.7.1 |
snetSwitchNeighborChgTrapEnableEnables Neighbor Change Trap generation. Asynchronous
events can be generated by the switch whenever a change in
neighbor id is detected.
Valid values are
off(0),
on(1) (default).rw INTEGER .1.3.6.1.4.1.169.8.3.1.7.2 |
snetSwitchThresholdErrorTrapEnableEnables Link/Packet Error Trap generation. Asynchronous
events can be generated by the switch whenever a link,
packet, or IBC errors have exceeded a pre-defined threshold.
Valid values are
off(0),
on(1) (default).rw INTEGER .1.3.6.1.4.1.169.8.3.1.7.3 |
snetSwitchAccessViolationTrapEnableEnables AccessViolation Trap generation. Asynchronous events can be
generated by the switch whenever a packet is received from an
unknown ServerNet ID.
Valid values are
off(0),
on(1) (default).rw INTEGER .1.3.6.1.4.1.169.8.3.1.7.4 |
snetSwitchTakeoverTrapEnableEnables notification of switch takeover Trap generation. Asynchronous
events can be generated by the switch whenever the switch
ownership changes.
Valid values are
off(0),
on(1) (default).rw INTEGER .1.3.6.1.4.1.169.8.3.1.7.5 |
snetSwitchSWFWTrapEnableEnables generation of firmware upgrade traps. Asynchronous events can be
generated by the administrative node whenever a firmware upgrade of the
switch occurs.
Valid values are
off(0),
on(1) (default).rw INTEGER .1.3.6.1.4.1.169.8.3.1.7.6 |
snetSwitchPrimarySANManSNetIDIdentifies the ServerNet ID of the current primary
administrative node in the ServerNet SAN.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.169.8.3.1.8 |
snetSwitchBackupSANManSNetIDIdentifies the ServerNet ID of the current backup
administrative node in the ServerNet SAN.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.169.8.3.1.9 |
snetSwitchFailoverEventTypeIndicates the most recent failover event type.
Valid values include
NoFailoversDetected(1),
BackupNotReachable(2),
BackupTookOver(3),
PrimaryNotReachable(4),
PrimaryTookOver(5).ro Enumeration .1.3.6.1.4.1.169.8.3.1.10 |
snetSwitchPrimarySANManNameName of the current primary administrative node in the ServerNet SAN.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.169.8.3.1.11 |
snetSwitchBackupSANManNameName of the current backup administrative node in the ServerNet SAN.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.169.8.3.1.12 |
snetSwitchInfo OBJECT IDENTIFIER .1.3.6.1.4.1.169.8.3.2 |
snetSwitchConfigData OBJECT IDENTIFIER .1.3.6.1.4.1.169.8.3.2.1 |
snetSwitchConfigTableServerNet Switch Configuration data. SEQUENCE OF SnetSwitchConfigEntry .1.3.6.1.4.1.169.8.3.2.1.1 |
snetSwitchConfigEntryAn entry containing ServerNet Switch configuration data. SnetSwitchConfigEntry .1.3.6.1.4.1.169.8.3.2.1.1.1 |
snetSwitchSnetIDSwitch Identifier. The switch id is displayed as a hexidecimal value.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.169.8.3.2.1.1.1.1 |
snetSwitchManufacturingIDThe Manufacturing IDro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.169.8.3.2.1.1.1.2 |
snetSwitchPartNumberSwitch Part Numberro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.169.8.3.2.1.1.1.3 |
snetSwitchSerialNumberSwitch Serial Numberro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.169.8.3.2.1.1.1.4 |
snetSwitchHWMajorRevSwitch Hardware Major Revisionro INTEGER .1.3.6.1.4.1.169.8.3.2.1.1.1.5 |
snetSwitchHWMinorRevSwitch Hardware Minor Revisionro INTEGER .1.3.6.1.4.1.169.8.3.2.1.1.1.6 |
snetSwitchFWReleaseSwitch Firmware Releasero INTEGER .1.3.6.1.4.1.169.8.3.2.1.1.1.7 |
snetSwitchFWMajorRevSwitch Firmware Major Revisionro INTEGER .1.3.6.1.4.1.169.8.3.2.1.1.1.8 |
snetSwitchFWMinorRevSwitch Firmware Minor Revisionro INTEGER .1.3.6.1.4.1.169.8.3.2.1.1.1.9 |
snetSwitchSANManSNetIDServerNet ID of the primary administrative node.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.169.8.3.2.1.1.1.10 |
snetSwitchStateIdentifies the current state of the Switch.
Unconfigured(1),
Configured(2).ro Enumeration .1.3.6.1.4.1.169.8.3.2.1.1.1.11 |
snetSwitchDomainThe domain the switch belongs to. If no domain is defined,
the default is blank.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.169.8.3.2.1.1.1.12 |
snetSwitchNameThe switch name. If no name is defined, this field
will be blank.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.169.8.3.2.1.1.1.13 |
snetSwitchFabricIdentifies the X or Y Fabric this node connects to.
X Fabric(1),
Y Fabric(2),
Both Fabrics(3),
Not Defined(4).ro Enumeration .1.3.6.1.4.1.169.8.3.2.1.1.1.14 |
snetSwitchPortData OBJECT IDENTIFIER .1.3.6.1.4.1.169.8.3.2.2 |
snetSwitchPortErrorStatusTableTable containing error and status information for each
of the configured ports. SEQUENCE OF SnetSwitchPortErrorStatusEntry .1.3.6.1.4.1.169.8.3.2.2.1 |
snetSwitchPortErrorStatusEntryA table of per-port error and status data SnetSwitchPortErrorStatusEntry .1.3.6.1.4.1.169.8.3.2.2.1.1 |
snetSwitchPortErrorStatusIndexIdentifies the switch port number.ro INTEGER .1.3.6.1.4.1.169.8.3.2.2.1.1.1 |
snetSwitchLinkErrorCounterNumber of link errors which have occurred on the selected port.ro Counter .1.3.6.1.4.1.169.8.3.2.2.1.1.2 |
snetSwitchPacketErrorCounterNumber of packet errors which have occurred on the selected port.ro Counter .1.3.6.1.4.1.169.8.3.2.2.1.1.3 |
snetSwitchIBCErrorCounterNumber of IBC errors which have occurred on the selected port.ro Counter .1.3.6.1.4.1.169.8.3.2.2.1.1.4 |
snetSwitchPortStatusCurrent state of the specified port.
Valid values are
Unavailable(1),
Uninstalled(2),
NoLinkAlive(3),
Alive(4).ro Enumeration .1.3.6.1.4.1.169.8.3.2.2.1.1.5 |
snetSwitchDaughterCardTypeDaughter card type installed on the specified port.
Valid values are
Unknown(1), (port can't be reached)
Other (2), (daughter board installed but type not defined)
Not Present(3), (no daughter board installed)
LVDS(4), (Low Voltage Differential Signal)
Fiber Channel(5),
Copper Serial(6),
Long Haul Optical (7),
Short Haul Optical (8),
ECL (9),(Emitter Coupled Logic).ro Enumeration .1.3.6.1.4.1.169.8.3.2.2.1.1.6 |
snetSwitchDaughterCardStatusCurrent status of the specified daughter card
Valid values are
Not Provided(1), (some daughter cards do not provide a status)
Cable Connected (2),
Cable Not Terminated(3).ro Enumeration .1.3.6.1.4.1.169.8.3.2.2.1.1.7 |
snetSwitchRoutingData OBJECT IDENTIFIER .1.3.6.1.4.1.169.8.3.2.3 |
snetSwitchRoutingTableThe routing table is 1024 entries SEQUENCE OF SnetSwitchRoutingTableEntry .1.3.6.1.4.1.169.8.3.2.3.1 |
snetSwitchRoutingTableEntryThe routing table entry has an index and a port address. SnetSwitchRoutingTableEntry .1.3.6.1.4.1.169.8.3.2.3.1.1 |
snetSwitchRoutingTableIndexServerNet Switch Routing Table Index.
An index into the routing table.ro INTEGER .1.3.6.1.4.1.169.8.3.2.3.1.1.1 |
snetSwitchDestA port address.ro INTEGER .1.3.6.1.4.1.169.8.3.2.3.1.1.2 |
snetSwitchRoutingLeafTableThe routing table is 64 entries SEQUENCE OF SnetSwitchRoutingLeafTableEntry .1.3.6.1.4.1.169.8.3.2.3.2 |
snetSwitchRoutingLeafTableEntryThe routing table entry has an index and a port address. SnetSwitchRoutingLeafTableEntry .1.3.6.1.4.1.169.8.3.2.3.2.1 |
snetSwitchRoutingLeafTableIndexServerNet Switch Routing Leaf Table Index.
An index into the routing table.ro INTEGER .1.3.6.1.4.1.169.8.3.2.3.2.1.1 |
snetSwitchLeafDestA port address.ro INTEGER .1.3.6.1.4.1.169.8.3.2.3.2.1.2 |
snetSwitchPerformanceData OBJECT IDENTIFIER .1.3.6.1.4.1.169.8.3.2.4 |
snetSwitchPerfTableThe switch performance data. SEQUENCE OF SnetSwitchPerfTableEntry .1.3.6.1.4.1.169.8.3.2.4.1 |
snetSwitchPerfTableEntryAn entry in the performance table. Performance data is
maintained per switch. SnetSwitchPerfTableEntry .1.3.6.1.4.1.169.8.3.2.4.1.1 |
snetSwitchPerfType1Selects the type of performance count to be run in counter 1.rw INTEGER .1.3.6.1.4.1.169.8.3.2.4.1.1.1 |
snetSwitchPerfType2Selects the type of performance count to be run in counter 2.rw INTEGER .1.3.6.1.4.1.169.8.3.2.4.1.1.2 |
snetSwitchPerfInPort1Input port to be used for performance counts for Performance Counter 1.rw INTEGER .1.3.6.1.4.1.169.8.3.2.4.1.1.3 |
snetSwitchPerfOutPort1Output port to be used for performance counts for Performance Counter 1.rw INTEGER .1.3.6.1.4.1.169.8.3.2.4.1.1.4 |
snetSwitchPerfInPort2Input port to be used for performance counts for Performance Counter 2.rw INTEGER .1.3.6.1.4.1.169.8.3.2.4.1.1.5 |
snetSwitchPerfOutPort2Output port to be used for performance counts for Performance Counter 2.rw INTEGER .1.3.6.1.4.1.169.8.3.2.4.1.1.6 |
snetSwitchPerfTimerSelectSpecifies the duration the performance count should run.
1= 16 nanoseconds per count, maximum 68.72 second timer
2= 256 nanoseconds per count, maximum 18.33 minute timer
3= 1.024 microseconds per count, maximum 73.30 minute timer
4= 8.129 microseconds per count, maximum 9.77 hour timer
This value is automatically determined based on the Performance
timer interval specified by the user.ro INTEGER .1.3.6.1.4.1.169.8.3.2.4.1.1.7 |
snetSwitchPerfTimerIntervalThis is the amount of time the counter will run in milliseconds.
The default is 0 and must be changed before a performance count
will run. The maximum value is 35172000 milliseconds which is
9.77 hours.rw INTEGER .1.3.6.1.4.1.169.8.3.2.4.1.1.8 |
snetSwitchPerfStartSetting this variable to 1 causes the request to start the
performance count to be sent. The Types, Inports, Outports,
and TimerInterval should all be set prior to setting
Start. If they are not set, default values will be used. At a
minimum, the TimerInterval must be reset to a value other than
zero before a performance count will run.rw INTEGER .1.3.6.1.4.1.169.8.3.2.4.1.1.9 |
snetSwitchPerfStatusGETting this variable causes a request to be made to the
switch to retrieve the latest values for the Performance
count status (snetSwitchPerfStatus), Performance counters
(snetSwitchPerfCounter1 and snetSwitchPerfCounter2) and
time left (snetSwitchTimeLeft).
Possible Values for Status:
Data is valid(1),
Counting is still in process(2),
Counter 1 overflowed(3),
Counter 2 overflowed(4),
Timer overflowed(5),
Unknown. Switch not reachable(6).ro Enumeration .1.3.6.1.4.1.169.8.3.2.4.1.1.10 |
snetSwitchPerfElapsedTimeThe amount of time elapsed on the current performance count in milliseconds.
If this value is zero, the performance counters have completed.ro INTEGER .1.3.6.1.4.1.169.8.3.2.4.1.1.11 |
snetSwitchPerfCounter1The result of the last performance count for counter 1. To
check the validity and get the latest Counter1 value from
the switch, first Get the snetSwitchPerfStatus.ro Counter .1.3.6.1.4.1.169.8.3.2.4.1.1.12 |
snetSwitchPerfCounter2The result of the last performance count for counter 2.
To check the validity and get the latest Counter2 value
from the switch, first Get the snetSwitchPerfStatus.ro Counter .1.3.6.1.4.1.169.8.3.2.4.1.1.13 |
snetSwitchErrorStatusData OBJECT IDENTIFIER .1.3.6.1.4.1.169.8.3.2.5 |
snetSwitchErrorStatusTableTable of switch error and status data. SEQUENCE OF SnetSwitchErrorStatusEntry .1.3.6.1.4.1.169.8.3.2.5.1 |
snetSwitchErrorStatusEntryAn entry containing status and error data for each switch. SnetSwitchErrorStatusEntry .1.3.6.1.4.1.169.8.3.2.5.1.1 |
snetSwitchLinkErrorThresholdNumber of link errors which occur before an asynchronous
event notification is generated by the switch.rw INTEGER .1.3.6.1.4.1.169.8.3.2.5.1.1.1 |
snetSwitchPacketErrorThresholdNumber of packet errors which occur before an asynchronous
event notification is generated by the switch.rw INTEGER .1.3.6.1.4.1.169.8.3.2.5.1.1.2 |
snetSwitchIBCErrorThresholdNumber of packet errors which occur before an asynchronous
event notification is generated by the switch.rw INTEGER .1.3.6.1.4.1.169.8.3.2.5.1.1.3 |
snetSwitchNeighborIDThis field contains the latest value of the Neighbor ID
which has changed. Whenever a change in a neighbor ID is
detected by a switch, the switch generates an asynchronous
event. The neighbor ID which was detected by the switch is
saved here. It is valid only for the last event which
occurred. If no neighbor ID changes have occurred, the
value will be blank.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.169.8.3.2.5.1.1.4 |
snetSwitchAccessViolationIDThis field contains the latest value for the invalid ID
which was detected by the switch. Whenever an invalid
id is detected by a switch, the switch generates an
asynchronous event. The ID which was detected by the
switch is saved here. It is valid only for the last event
which occurred. If no invalid IDs have been detected, the
value will be zero(0).ro INTEGER .1.3.6.1.4.1.169.8.3.2.5.1.1.5 |
snetSwitchFWStatusThe Firmware Status for the Switch
Firmware Status OK(1),
Hardware Error Detected(2),
Unknown Firmware Error Detected(3),
Bad Program CheckSum(4),
Current Configuration failed. Switch is using factory default configuration(5),
Switch cannot be reached. Firmware status is unknown(6).ro Enumeration .1.3.6.1.4.1.169.8.3.2.5.1.1.6 |
snetSwitchHWStatusThe Hardware Status for the Switch
Hardware Status OK(1),
SRAM Memory test failed(2),
Flash sector test failed(3),
Bad SEEPROM checksum(4),
SBUSY error(5),
FLASH program error(6),
Switch cannot be reached. Hardware status is unknown.(7),
Other Hardware Error, such as fan failure may be indicated.(8)ro Enumeration .1.3.6.1.4.1.169.8.3.2.5.1.1.7 |
snetSwitchStatusThe Overall Status for the Switch. This is determined by a combination
of port status values and configuration values. If a port is configured,
it should detect Link Alive. If the port is not in LinkAlive state, the
switch status will be degraded. If all configured ports are in
LinkAlive state, the switch status will be ok. Hardware, Firmware and Fan
status are also used to determine switch status as described below.
This represents the overall condition of the specified switch.
Other(1):
Switch not installed or status unknown
OK(2):
All ports, Hardware, Firmware and Fan status are OK.
Degraded(3):
One or more ports are down. Hardware or Firmware status
show an error condition.
Failed(4):
All ports are Failed, switch is not reachable, Fan status
is failed.ro Enumeration .1.3.6.1.4.1.169.8.3.2.5.1.1.8 |
snetSwitchFanStatusThe status of the switch fans.
Other(1): Unknown or not reported. This is the status if
the switch cannot be reached.
OK(2): OK is reported if both fans are working as designed
Degraded(3): This status is not reported but is listed for
consistency with other status fields
Failed(4): One or more fans have failed. The power module
should be replaced immediately to prevent damage
to switch components.ro Enumeration .1.3.6.1.4.1.169.8.3.2.5.1.1.9 |