- Table of Contents
- Related Documents
-
Title | Size | Download |
---|---|---|
01-HH3C-POSA-MIB | 160.69 KB |
Contents
HH3C-POSA-MIB
About this MIB
Use this MIB to obtain basic information, collect alarms, and configure parameters for a POS access device.
MIB file name
hh3c-posa.mib
Notifications
hh3cPosaServerStatusChange
Basic information
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
1.3.6.1.4.1.25506.2.92.3.0.1 |
POS access service status change. |
Informational |
Warning |
N/A |
ON |
Notification triggers
This notification is generated when the POS access service is enabled or disabled.
System impact
With the POS access service enabled, POS transactions can be processed. POS transactions cannot be processed if the POS access service is disabled.
Status control
ON
· CLI: Use the snmp-agent trap enable posa server-state-change command.
· MIB: Set hh3cPosaSrvStateChangeTrapEnable to true(1).
OFF
· CLI: Use the undo snmp-agent trap enable posa server-state-change command.
· MIB: Set hh3cPosaSrvStateChangeTrapEnable to false(2).
Objects
OID (object name) |
Description |
Index nodes |
Type |
Value range |
1.3.6.1.4.1.25506.2.92.1.1 (hh3cPosaServerEnable) |
Enabling status of the POS access service. |
N/A |
INTEGER |
disabled(1), enabled(2) |
Recommended action
No action is required because the router runs correctly.
hh3cPosaAppAvailChange
Basic information
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
1.3.6.1.4.1.25506.2.92.3.0.2 |
State change of a POS application template. |
Informational |
Warning |
N/A |
ON |
Notification triggers
This notification might be generated when the following events occur:
· The router is disconnected from the FEP.
· The connection between the router and the FEP is established.
· The interface through which the router connects to the FEP is down or up.
System impact
The POS transaction being processed cannot be processed correctly, and the link between the router and the FEP is disconnected.
Status control
ON
· CLI: Use the snmp-agent trap enable posa app-state-change command.
· MIB: Set hh3cPosaAppStateChangeTrapEnable to true(1).
OFF
· CLI: Use the undo snmp-agent trap enable posa app-state-change command.
· MIB: Set hh3cPosaAppStateChangeTrapEnable to false(2).
Objects
OID (object name) |
Description |
Index nodes |
Type |
Value range |
1.3.6.1.4.1.25506.2.92.2.1.1.1 (hh3cPosaAppID) |
ID of a POS application template. |
hh3cPosaAppID |
Integer32 |
1..1024 |
1.3.6.1.4.1.25506.2.92.3.1.1 (hh3cPosaAppStateChangeObject) |
Status of the POS application template. |
N/A |
INTEGER |
available(1), unavailable(2) |
Recommended action
To resolve this issue:
1. Verify that the router connects to the FEP correctly.
2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact H3C Support for help.
hh3cPosaTerminalHangUp
Basic information
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
1.3.6.1.4.1.25506.2.92.3.0.3 |
POS terminal hangup. |
Informational |
Warning |
N/A |
ON |
Notification triggers
This notification is generated when a POS application template terminates the POS connection established through an FCM interface.
System impact
No impact on services.
Status control
ON
· CLI: Use the snmp-agent trap enable posa terminal-hangup command.
· MIB: Set hh3cPosaTerminalHangUpTrapEnable to true(1).
OFF
· CLI: Use the undo snmp-agent trap enable posa terminal-hangup command.
· MIB: Set hh3cPosaTerminalHangUpTrapEnable to false(2).
Objects
OID (object name) |
Description |
Index nodes |
Type |
Value range |
1.3.6.1.2.1.2.2.1.1 (ifIndex) |
Index of the interface through which the POS terminal connects to the router. |
ifIndex |
InterfaceIndex |
Integer32(1..2147483647) |
1.3.6.1.2.1.2.2.1.2 (ifDescr) |
Name of the interface through which the POS terminal connects to the router. |
ifIndex |
DisplayString |
OCTET STRING (SIZE (0..255)) |
1.3.6.1.4.1.25506.2.92.2.10.1.1 (hh3cPosaCallerStatCallerID) |
POS terminal caller ID. |
hh3cPosaCallerStatCallerID |
OCTET STRING |
OCTET STRING(SIZE (0..64)) |
Recommended action
No action is required because the router runs correctly.
hh3cPosaFcmLinkNegoFailed
Basic information
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
1.3.6.1.4.1.25506.2.92.3.0.4 |
Negotiation failure on the FCM link layer |
Informational |
Warning |
N/A |
ON |
Notification triggers
This notification is generated when the link layer negotiation is failed between the POS terminal and router through an FCM interface.
System impact
POS transactions will be unavailable.
Status control
ON
· CLI: Use the snmp-agent trap enable posa fcm-link-failure command.
· MIB: Set hh3cPosaFcmLnkNegoFailTrapEnable to true(1).
OFF
· CLI: Use the undo snmp-agent trap enable posa fcm-link-failure command.
· MIB: Set hh3cPosaFcmLnkNegoFailTrapEnable to false(2).
Objects
OID (object name) |
Description |
Index nodes |
Type |
Value range |
1.3.6.1.2.1.2.2.1.1 (ifIndex) |
Index of the interface through which the POS terminal connects to the router. |
ifIndex |
InterfaceIndex |
Integer32(1..2147483647) |
1.3.6.1.2.1.2.2.1.2 (ifDescr) |
Name of the interface through which the POS terminal connects to the router. |
ifIndex |
DisplayString |
OCTET STRING (SIZE (0..255)) |
1.3.6.1.4.1.25506.2.92.2.10.1.1 (hh3cPosaCallerStatCallerID) |
POS terminal caller ID. |
hh3cPosaCallerStatCallerID |
OCTET STRING |
OCTET STRING(SIZE (0..64)) |
Recommended action
To resolve this issue:
1. Verify that the FCM interface is configured correctly.
2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact H3C Support for help.
hh3cPosaFcmPhyNegoFailed
Basic information
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
1.3.6.1.4.1.25506.2.92.3.0.5 |
Negotiation failure on the FCM physical layer. |
Informational |
Warning |
N/A |
ON |
Notification triggers
This notification is generated when the physical layer negotiation is failed between the POS terminal and router through an FCM interface.
System impact
POS transactions will be unavailable.
Status control
ON
· CLI: Use the snmp-agent trap enable posa fcm-physical-failure command.
· MIB: Set hh3cPosaFcmPhyNegoFailTrapEnable to true(1).
OFF
· CLI: Use the undo snmp-agent trap enable posa fcm-physical-failure command.
· MIB: Set hh3cPosaFcmPhyNegoFailTrapEnable to false(2).
Objects
OID (object name) |
Description |
Index nodes |
Type |
Value range |
1.3.6.1.2.1.2.2.1.1 (ifIndex) |
Index of the interface through which the POS terminal connects to the router. |
ifIndex |
InterfaceIndex |
Integer32(1..2147483647) |
1.3.6.1.2.1.2.2.1.2 (ifDescr) |
Name of the interface through which the POS terminal connects to the router. |
ifIndex |
DisplayString |
OCTET STRING (SIZE (0..255)) |
1.3.6.1.4.1.25506.2.92.2.10.1.1 (hh3cPosaCallerStatCallerID) |
POS terminal caller ID. |
hh3cPosaCallerStatCallerID |
OCTET STRING |
OCTET STRING(SIZE (0..64)) |
Recommended action
To resolve this issue:
1. Verify that the FCM interface is configured correctly.
2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact H3C Support for help.
hh3cPosaTcpConnectionExceed
Basic information
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
1.3.6.1.4.1.25506.2.92.3.0.6 |
TCP concurrent connections exceeding the threshold. |
Informational |
Major |
N/A |
ON |
Description
This notification is generated when the number of concurrent TCP connections exceeds the threshold.
System impact
When the number of concurrent TCP connections reaches the threshold, subsequent POS transactions might fail.
Status control
ON
· CLI: Use the snmp-agent trap enable posa tcp-connection-exceed command.
· MIB: Set hh3cPosaTcpConnectionTrapEnable to true(1).
OFF
· CLI: Use the undo snmp-agent trap enable posa tcp-connection-exceed command.
· MIB: Set hh3cPosaTcpConnectionTrapEnable to false(2).
Objects
OID (object name) |
Description |
Index nodes |
Type |
Value range |
1.3.6.1.4.1.25506.2.92.1.12 (hh3cPosaTcpConnectionThreshold) |
TCP concurrent connection threshold. |
N/A |
Integer32 |
1..4096 |
Recommended action
To resolve this issue:
1. Verify that the TCP concurrent connection threshold is set to a reasonable value.
2. Execute the posa connection-threshold terminal command to increase the TCP concurrent connection threshold.
3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact H3C Support for help.
hh3cPosaFcmConnectionExceed
Basic information
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
1.3.6.1.4.1.25506.2.92.3.0.7 |
FCM concurrent connections exceeding the threshold. |
Informational |
Warning |
N/A |
ON |
Notification triggers
This notification is generated when the number of concurrent FCM connections exceeds the threshold.
System impact
When the number of concurrent FCM connections reaches the threshold, subsequent POS transactions might fail.
Status control
ON
· CLI: Use the snmp-agent trap enable posa fcm-connection-exceed command.
· MIB: Set hh3cPosaFcmConnectionTrapEnable to true(1).
OFF
· CLI: Use the undo snmp-agent trap enable posa fcm-connection-exceed command.
· MIB: Set hh3cPosaFcmConnectionTrapEnable to false(2).
Objects
OID (object name) |
Description |
Index nodes |
Type |
Value range |
1.3.6.1.4.1.25506.2.92.1.13 (hh3cPosaFcmConnectionThreshold) |
FCM concurrent connection threshold. |
N/A |
Integer32 |
1..1024 |
This table does not contain indexes. For information about the index or indexes of a MIB object instance in an SNMP variable binding, see the section for that MIB object.
Recommended action
To resolve this issue:
1. Verify that the FCM concurrent connection threshold is set to a reasonable value.
2. Execute the posa connection-threshold terminal command to increase the FCM concurrent connection threshold.
3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact H3C Support for help.
hh3cPosaTcpTradeExceed
Basic information
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
1.3.6.1.4.1.25506.2.92.3.0.8 |
TCP concurrent transactions exceeding the threshold. |
Informational |
Major |
N/A |
ON |
Notification triggers
This notification is generated when the number of concurrent TCP transactions over a TCP connection exceeds the threshold.
System impact
Subsequent POS transactions might fail on the TCP connection.
Status control
ON
· CLI: Use the snmp-agent trap enable posa tcp-trade-exceed command.
· MIB: Set hh3cPosaTcpTradeTrapEnable to true(1).
OFF
· CLI: Use the undo snmp-agent trap enable posa tcp-trade-exceed command.
· MIB: Set hh3cPosaTcpTradeTrapEnable to false(2).
Objects
OID (object name) |
Description |
Index nodes |
Type |
Value range |
1.3.6.1.4.1.25506.2.92.1.16 (hh3cPosaTcpTradeLimit) |
TCP concurrent transaction threshold over a TCP connection. |
N/A |
Integer32 |
0..65535 |
1.3.6.1.4.1.25506.2.92.2.2.1.1 (hh3cPosaTerminalID) |
ID of a POS terminal template, which uniquely identifies the POS terminal. |
hh3cPosaTerminalID |
Integer32 |
1..1024 |
Recommended action
To resolve this issue:
1. Verify that the TCP concurrent transaction threshold is set to a reasonable value.
2. Execute the posa connection-threshold terminal command to increase the TCP concurrent connection threshold.
3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact H3C Support for help.
hh3cPosaTradeSuccessFalling
Basic information
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
1.3.6.1.4.1.25506.2.92.3.0.9 |
Transaction success rate on an FEP dropping below the alarm threshold. |
Informational |
Warning |
N/A |
ON |
Notification triggers
This notification might be generated when the following events occur
· Failures occur on the FEP.
· Packet loss occurs due to network errors between the router and the FEP.
· The router suffers from network attacks.
System impact
POS transactions might fail.
Status control
ON
· CLI: Use the snmp-agent trap enable posa trade-failing-enable command.
· MIB: Set hh3cPosaTradeSuccessFallingTrapEnable to true(1).
OFF
· CLI: Use the undo snmp-agent trap enable posa trade-failing-enable command.
· MIB: Set hh3cPosaTradeSuccessFallingTrapEnable to false(2).
Objects
OID (object name) |
Description |
Index nodes |
Type |
Value range |
1.3.6.1.4.1.25506.2.92.2.11.1.1 (hh3cPosaNiiStatIndex) |
TPDU destination address for an FEP. |
hh3cPosaNiiStatIndex |
OCTET STRING |
OCTET STRING(SIZE (4)) |
1.3.6.1.4.1.25506.2.92.1.20 (hh3cPosaTradeSuccessFallingThreshold) |
Alarm threshold for transaction success rate on an FEP. |
N/A |
Integer32 |
1..99 |
Recommended action
To resolve this issue:
1. Verify that the low alarm threshold for transaction success rate is set to a reasonable value.
2. Execute the posa trade-falling-threshold command to decrease the alarm threshold for transaction success rate.
3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact H3C Support for help.
hh3cPosaE1DailFalling
Basic information
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
1.3.6.1.4.1.25506.2.92.3.0.10 |
Dialup success rate on an E1POS interface dropping below the alarm threshold. |
Informational |
Major |
N/A |
ON |
Notification triggers
This notification might be generated when the following events occur
· Packet loss and network latency occur in the POS connection link in FCM dial-up access mode.
· The router suffers from network attacks.
System impact
POS transactions might fail.
Status control
ON
· CLI: Use the snmp-agent trap enable posa e1-dialing-falling command.
· MIB: Set hh3cPosaE1DailFallingTrapEnable to true(1).
OFF
· CLI: Use the undo snmp-agent trap enable posa e1-dialing-falling command.
· MIB: Set hh3cPosaE1DailFallingTrapEnable to false(2).
Objects
OID (object name) |
Description |
Index nodes |
Type |
Value range |
1.3.6.1.2.1.2.2.1.1 (ifIndex) |
Index of the interface through which the POS terminal connects to the router. |
ifIndex |
InterfaceIndex |
Integer32(1..2147483647) |
1.3.6.1.2.1.2.2.1.2 (ifDescr) |
Name of the interface through which the POS terminal connects to the router. |
ifIndex |
DisplayString |
OCTET STRING (SIZE (0..255)) |
1.3.6.1.4.1.25506.2.92.1.22 (hh3cPosaE1DialFallingThreshold) |
Alarm threshold for dialup success rate on an E1POS interface. |
N/A |
Integer32 |
1..99 |
Recommended action
To resolve this issue:
1. Verify that the alarm threshold for dialup success rate is set to a reasonable value.
2. Execute the posa e1-dial-falling-threshold command to decrease the alarm threshold for dialup success rate.
3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact H3C Support for help.
hh3cPosaFcmTradeAbnormal
Basic information
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
1.3.6.1.4.1.25506.2.92.3.0.11 |
Transaction anomaly on an FCM interface. |
Informational |
Warning |
N/A |
ON |
Notification triggers
This notification is generated when anomalies occur on the link between the POS terminal and the router.
System impact
POS transactions fail on the POS terminal.
Status control
ON
· CLI: Use the snmp-agent trap enable posa fcm-trade-abnormal command.
· MIB: Set hh3cPosaE1DailFallingTrapEnable to true(1).
OFF
· CLI: Use the undo snmp-agent trap enable posa fcm-trade-abnormal command.
· MIB: Set hh3cPosaE1DailFallingTrapEnable to false(2).
Objects
OID (object name) |
Description |
Index nodes |
Type |
Value range |
1.3.6.1.2.1.2.2.1.1 (ifIndex) |
Index of the interface through which the POS terminal connects to the router. |
ifIndex |
InterfaceIndex |
Integer32(1..2147483647) |
1.3.6.1.2.1.2.2.1.2 (ifDescr) |
Name of the interface through which the POS terminal connects to the router. |
ifIndex |
DisplayString |
OCTET STRING (SIZE (0..255)) |
1.3.6.1.4.1.25506.2.92.2.10.1.1 (hh3cPosaCallerStatCallerID) |
POS terminal caller ID. |
hh3cPosaCallerStatCallerID |
OCTET STRING |
OCTET STRING(SIZE (0..64)) |
Recommended action
To resolve this issue:
1. Verify that the link between the POS terminal and the router is normal.
2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact H3C Support for help.