Lannet-Trapsv2-MIB
AI MIB Summary
The Lannet-Trapsv2-MIB defines the SMIv2 structure for Lannet Networks p330 and P130 hardware devices to generate SNMPv2c trap notifications for critical system events and interface state changes. This module enables network management systems to receive asynchronous alerts regarding device faults, link status transitions, and hardware anomalies specific to the Lannet p330/P130 platform.
SMIv2 definition of p330/P130 traps
Main OID:
lntTraps.1.3.6.1.4.1.81.38
109
Objects
Active
Status
12
Dependencies
Imported Objects
Objects
109 total| Object Name |
|---|
lntTrapsSMIv2 definition of p330/P130 traps MODULE-IDENTITY .1.3.6.1.4.1.81.38 |
lntConfigChangeEventsGroups together all configuration change related events OBJECT IDENTIFIER .1.3.6.1.4.1.81.38.1 |
lntConfigChangePrefixThe next to last sub- identifier in the name of any newly-defined notification
must have the value zero OBJECT IDENTIFIER .1.3.6.1.4.1.81.38.1.0 |
lntConfigChangeEventNotification generated in case of configuration change.
List of events triggering notitication is TBD NOTIFICATION-TYPE .1.3.6.1.4.1.81.38.1.0.1 |
lntStackMasterReelectionThe trap should be triggered in an event that an election process
leads to selection of a different module as a Stack Master NOTIFICATION-TYPE .1.3.6.1.4.1.81.38.1.0.82 |
lntSWRedundancyEventsGroups together all software redundancy related events OBJECT IDENTIFIER .1.3.6.1.4.1.81.38.2 |
lntSWRedundancyPrefixThe next to last sub- identifier in the name of any newly-defined notification
must have the value zero OBJECT IDENTIFIER .1.3.6.1.4.1.81.38.2.0 |
lntSoftRedDelEventThe trap notifies the manager of the deletion of the specified
redundant link, which is identified by the softRedundancyId. NOTIFICATION-TYPE .1.3.6.1.4.1.81.38.2.0.12 |
lntSoftRedNewEventThe trap is generated on the creation of the redundant links for the
specified ports. It gives the logical name of the redundant link the
identification of the main and secondary ports and the status of the
link. The softRedundancyId defines the instances of the above-
mentioned variables. NOTIFICATION-TYPE .1.3.6.1.4.1.81.38.2.0.13 |
lntTempratureEventsGroups together all temprature related events OBJECT IDENTIFIER .1.3.6.1.4.1.81.38.3 |
lntTempratureWarningPrefixThe next to last sub- identifier in the name of any newly-defined notification
must have the value zero OBJECT IDENTIFIER .1.3.6.1.4.1.81.38.3.0 |
lntTempratureWarningThis trap notifies the management station of the internal
board/enclosure temperature fluctuations. It is generated when
the temperature exceeds the threshold chHWIntTempThresh. NOTIFICATION-TYPE .1.3.6.1.4.1.81.38.3.0.14 |
lntTempratureOkThis trap notifies the management station that the internal
board/enclosure temperature fluctuations situation is back to normal. NOTIFICATION-TYPE .1.3.6.1.4.1.81.38.3.0.23 |
lntCAMChangeEventsGroups together all CAM related events OBJECT IDENTIFIER .1.3.6.1.4.1.81.38.4 |
lntCAMChangePrefixThe next to last sub- identifier in the name of any newly-defined notification
must have the value zero OBJECT IDENTIFIER .1.3.6.1.4.1.81.38.4.0 |
lntPortCAMLastChangeThis trap reports of the occurred CAM changes NOTIFICATION-TYPE .1.3.6.1.4.1.81.38.4.0.22 |
lntPSUEventsGroups together all Power supply related events OBJECT IDENTIFIER .1.3.6.1.4.1.81.38.5 |
lntPSUPrefixThe next to last sub- identifier in the name of any newly-defined notification
must have the value zero OBJECT IDENTIFIER .1.3.6.1.4.1.81.38.5.0 |
lntMainPSUFltAn error was reported concerning the Main Power Supply.
Urgent intervention is required by the network administrator
in order to replace the faulty module, or take any other
necessary measures in order to ensure the uninterrupted
operation of the network NOTIFICATION-TYPE .1.3.6.1.4.1.81.38.5.0.2303 |
lntMainPSUOkThe network device recovered after a previously reported problem
in the operation of the box Main Power Supply NOTIFICATION-TYPE .1.3.6.1.4.1.81.38.5.0.2304 |
lntBackupPSUFltAn error was reported concerning the Backup Power Supply.
Urgent intervention is required by the network
administrator in order to replace the faulty module, or
take any other necessary measures in order to ensure the
uninterrupted operation of the network. NOTIFICATION-TYPE .1.3.6.1.4.1.81.38.5.0.2305 |
lntBackupPSUOkThe network device recovered after a previously reported problem
in the operation of the box Backup Power Supply. NOTIFICATION-TYPE .1.3.6.1.4.1.81.38.5.0.2306 |
lntL3EventsGroups together routing( L3) related events. OBJECT IDENTIFIER .1.3.6.1.4.1.81.38.6 |
lntL3FaultsPrefixThe next to last sub- identifier in the name of any newly-defined notification
must have the value zero OBJECT IDENTIFIER .1.3.6.1.4.1.81.38.6.0 |
lntDuplicateIPFltThis trap reports to the Management station on Duplicate IP
identification. CRP identify the new IP on the network.
If it similar to one of its IP interfaces, the CRP will issue a
SNMP trap, containing the MAC of the intruder. NOTIFICATION-TYPE .1.3.6.1.4.1.81.38.6.0.27 |
lntVLANViolationEventThis trap reports to the Management station on IP VLAN violation.
CRP verify the VLAN of the incoming packets. If there is any
inconsistency between the configured VLAN and the VLAN number
found in the IP packet, the CRP will issue a SNMP trap. NOTIFICATION-TYPE .1.3.6.1.4.1.81.38.6.0.28 |
lntARPViolationEventThis trap reports to the Management station when a Sourec IP in an
ARP response does not match the subnets configured on the router
interface through which it has been received.
The trap returns details of the offending packet, as welll as the
expected vs. detected VLAN IDs and interface Names NOTIFICATION-TYPE .1.3.6.1.4.1.81.38.6.0.70 |
lntLinkEventsGroups together port link up/down related events. OBJECT IDENTIFIER .1.3.6.1.4.1.81.38.7 |
lntLinkEventsPrefixThe next to last sub- identifier in the name of any newly-defined notification
must have the value zero OBJECT IDENTIFIER .1.3.6.1.4.1.81.38.7.0 |
lntPortLinkDownEventThe port hardware detects loss of connectivity to
an end station or to another hub or switch. This is not
necessarily a fault condition, as the same signaling is
reported by the port hardware in usual operational cases,
for example, of a non-critical station being
disconnected or turned off at the end of the work day.
(Bit 7 in the genPortFaultMask set to on, genPortFunctionalStatus = rld(2)
) NOTIFICATION-TYPE .1.3.6.1.4.1.81.38.7.0.3039 |
lntPortLinkUpEventThe port recovered from a previously reported
connectivity problem.
(Bit 7 in the genPortFaultMask set to off,
genPortFunctionalStatus = ok) NOTIFICATION-TYPE .1.3.6.1.4.1.81.38.7.0.3040 |
lntVPortLinkDownEventThe port hardware detects the lack of a connection
to an end station or to another hub or switch. While this
may not be necessarily a fault condition, the network
administrator's attention is recommended, because the port
was defined as a valuable port. (Bit 7 in the genPortFaultMask set
to on, genPortFunctionalStatus = rld(2)) NOTIFICATION-TYPE .1.3.6.1.4.1.81.38.7.0.3041 |
lntVPortLinkUpEventAcknowledegs link up condition on a valuable port.
(Bit 7 in the genPortFaultMask set to off,
genPortFunctionalStatus = ok) NOTIFICATION-TYPE .1.3.6.1.4.1.81.38.7.0.3042 |
lntLAGEventsGroups together LAG related events. OBJECT IDENTIFIER .1.3.6.1.4.1.81.38.8 |
lntLAGPrefixThe next to last sub- identifier in the name of any newly-defined notification
must have the value zero OBJECT IDENTIFIER .1.3.6.1.4.1.81.38.8.0 |
lntLAGConnLostFltThe trap reports on a LAG connection lost. It is sent when
scGenLinkAggregationFunctionalStatus changed to fail (2). NOTIFICATION-TYPE .1.3.6.1.4.1.81.38.8.0.44 |
lntLAGConnLostOkThe trap reports that the LAG connection lost was cleared.
It is sent when scGenLinkAggregationFunctionalStatus changed
from fail(2) to to ok(1). NOTIFICATION-TYPE .1.3.6.1.4.1.81.38.8.0.46 |
lntLAGPartialConnLostFltThe trap reports on a LAG partial connection, where some of the ports
are in fault but some are ok. It is sent when
scGenLinkAggregationFunctionalStatus changed to partialFail (3). NOTIFICATION-TYPE .1.3.6.1.4.1.81.38.8.0.48 |
lntLAGPartialConnLostOkThe trap reports that the LAG partial connection was cleared.
It is sent when scGenLinkAggregationFunctionalStatus
changed from partialFail (3)to to ok(1). NOTIFICATION-TYPE .1.3.6.1.4.1.81.38.8.0.50 |
lntLAGAutoNegFltThe trap reports on a auto-negotiation results on the LAG ports.
It is sent when scGenLinkAggregationAutoNegResults
changed to autoNegInconsistantResults (2). NOTIFICATION-TYPE .1.3.6.1.4.1.81.38.8.0.52 |
lntLAGAutoNegOkThe trap reports that the auto-negotiation results on the LAG ports was cleared.
It is sent when this trap is enabled and when scGenLinkAggregationAutoNegResults
changed to ok(1). NOTIFICATION-TYPE .1.3.6.1.4.1.81.38.8.0.54 |
lntLAGDeleteEventThe trap notifies the manager of the deletion of the specified LAG,
which is identified by the scGenLinkAggregationId. NOTIFICATION-TYPE .1.3.6.1.4.1.81.38.8.0.56 |
lntLAGCreateEventThe trap is generated on the creation of a new LAG,
which is identified by the scGenLinkAggregationId. NOTIFICATION-TYPE .1.3.6.1.4.1.81.38.8.0.58 |
lntFansEventsGroups together fans related events. OBJECT IDENTIFIER .1.3.6.1.4.1.81.38.9 |
lntFansPrefixThe next to last sub- identifier in the name of any newly-defined notification
must have the value zero OBJECT IDENTIFIER .1.3.6.1.4.1.81.38.9.0 |
lntMainFansFltThe trap reports the failure of one (or more)
module's Fan. It is sent when scGenGroupFansStatus changed
to oneFanFailed(2) NOTIFICATION-TYPE .1.3.6.1.4.1.81.38.9.0.2307 |
lntMainFansOKThe trap reports that the module's Fan failure
was cleared. It is sent when this trap is
enabled and when scGenGroupFansStatus changed
from oneFanFailed(2) to allFansOK(1). NOTIFICATION-TYPE .1.3.6.1.4.1.81.38.9.0.2308 |
lntBackupFansFltThe trap reports the failure of one
(or more) BUPS module's Fan. It is sent when
scGenGroupBUPSFansStatus changed to
oneFanFailed(2). NOTIFICATION-TYPE .1.3.6.1.4.1.81.38.9.0.2309 |
lntBackupFansOKThe trap reports that the BUPS module's Fan
failure was cleared. It is sent when this trap is
enabled and when scGenGroupBUPSFansStatus changed
from oneFanFailed(2) to allFansOK(1). NOTIFICATION-TYPE .1.3.6.1.4.1.81.38.9.0.2310 |
lntCascadeEventsGroups together stakc module cascading related events. OBJECT IDENTIFIER .1.3.6.1.4.1.81.38.10 |
lntCascadeFaultsPrefixThe next to last sub- identifier in the name of any newly-defined notification
must have the value zero OBJECT IDENTIFIER .1.3.6.1.4.1.81.38.10.0 |
lntCascadUpConnFltThe trap reports on a cascading up connection lost.
It is sent when genGroupCascadUpStatus changed to rld(2). NOTIFICATION-TYPE .1.3.6.1.4.1.81.38.10.0.2315 |
lntCascadUpConnOkThe trap reports that the cascading up connection lost
was cleared. It is sent when genGroupCascadUpStatus changed from rld(2) to ok(1). NOTIFICATION-TYPE .1.3.6.1.4.1.81.38.10.0.2316 |
lntCascadDownConnFltThe trap reports on a cascading down connection lost.
It is sent when genGroupCascadDownStatus changed to rld(2). NOTIFICATION-TYPE .1.3.6.1.4.1.81.38.10.0.2317 |
lntCascadDownConnOkThe trap reports that the cascading down connection lost
was cleared. It is sent when genGroupCascadDownStatus
changed from rld(2) to ok(1). NOTIFICATION-TYPE .1.3.6.1.4.1.81.38.10.0.2318 |
lntPolicyEventsGroups together policy related events. OBJECT IDENTIFIER .1.3.6.1.4.1.81.38.11 |
lntPolicyPrefixThe next to last sub- identifier in the name of any newly-defined notification
must have the value zero OBJECT IDENTIFIER .1.3.6.1.4.1.81.38.11.0 |
lntPolicyChangeEventThe trap reports a change in the active list specific for a
policy-enabled box or module NOTIFICATION-TYPE .1.3.6.1.4.1.81.38.11.0.60 |
lntPolicyAccessControlListLvlRuleTrapThis trap reports to the Management station when a list-level
Policy rule (e.g., ipPolicyListIpOptionOperation)
specifies an operation that includes a 'notify' action.
The trap includes in its varbind information about:
- The entity (slot) where the event occurred,
- The type of the list-level rule that was matched,
- The quintuplet that identifies the matching packet.
- The policy interface on which the event occurred.
- The policy interface sub-context (e.g., the direction)
- sysUpTime at the time the event occured.
A management application would display this trap and the relevant
information in a log entry.
This trap will not be sent at intervals smaller than one
minute for identical information in the varbinds list variables. NOTIFICATION-TYPE .1.3.6.1.4.1.81.38.11.0.62 |
lntPolicyAccessControlViolationFltThis trap reports to the Management station on IP PolicyAccess Control violation.
The trap includes in its varbind information about the slot where the event occurred,
The id of the rule that was violated in the current rules table,
and the quintuplet that identifies the faulty packet.
A management application would display this trap and the relevant information in a log entry.
This trap will not be sent at intervals smaller than one minute for identical information in the
varbinds list variables NOTIFICATION-TYPE .1.3.6.1.4.1.81.38.11.0.64 |
lntEthPortFaultEventsGroups together Etherent port related events. OBJECT IDENTIFIER .1.3.6.1.4.1.81.38.12 |
lntEthPortFaultPrefixThe next to last sub- identifier in the name of any newly-defined notification
must have the value zero OBJECT IDENTIFIER .1.3.6.1.4.1.81.38.12.0 |
lntEthPortAutoNegotiationFltThe port recovered from a previously reported
connectivity problem. (Bit 4 in the genPortFaultMask set to off,
scEthPortAutoNegotiationStatus = ok) NOTIFICATION-TYPE .1.3.6.1.4.1.81.38.12.0.3001 |
lntEthPortAutoNegotiationOKThe port recovered from a previously reported
connectivity problem. (Bit 4 in the genPortFaultMask set to off,
scEthPortAutoNegotiationStatus = ok) NOTIFICATION-TYPE .1.3.6.1.4.1.81.38.12.0.3002 |
lntPortFEFltThe port hardware detects a loss of connectivity
reported by the remote extremity of the link connected to
the port. This indication shows that though the cabling is
at least partially operative, the information transmitted
through the port may not arrive in all its integrity at the
other side of the link. It is recommended that the network
administrator check the link in order to detect the origin
of the problem and prevent its aggravation.
(Bit 10 in the genPortFaultMask set to on) NOTIFICATION-TYPE .1.3.6.1.4.1.81.38.12.0.3005 |
lntPortFEOkA previously detected problem in the integrity of the link,
reported by the remote link circuitry was solved.
(Bit 10 in the genPortFaultMask set to off,
scEthPortFunctionalStatus = ok(1)) NOTIFICATION-TYPE .1.3.6.1.4.1.81.38.12.0.3006 |
lntVPortFEFltThe valuable port hardware detects a loss of connectivity
reported by the remote extremity of the link connected to
the port. This indication shows that though the cabling is
at least partially operative, the information transmitted
through the port may not arrive in all its integrity at the
other side of the link. It is recommended that the network
administrator check the link in order to detect the origin
of the problem and prevent its aggravation.
(Bit 10 in the genPortFaultMask set to on,
scEthPortFunctionalStatus = fail(2)) NOTIFICATION-TYPE .1.3.6.1.4.1.81.38.12.0.3015 |
lntVPortFEOkA previously detected problem in the integrity of the link
to a valuable port, reported by the remote
link circuitry was solved.
(Bit 10 in the genPortFaultMask set to off,
scEthPortFunctionalStatus = ok(1)) NOTIFICATION-TYPE .1.3.6.1.4.1.81.38.12.0.3016 |
lntPortAutoPartFltThe port on the module reports the activation of the auto
partition mechanism. This event means that an excessive
number of errors occurred on the port, and the port is
disconnected from the repeater or switch unit. The network
administrator should check the segment and/or end stations
connected to the port for hardware or misconfiguration problems.
(Bit 1 in the genPortFaultMask set to on,
genPortFunctionalStatus = partition(8)) NOTIFICATION-TYPE .1.3.6.1.4.1.81.38.12.0.3023 |
lntPortAutoPartOkThe port recovered from a previously reported auto
partition fault.
(Bit 1 in the genPortFaultMask set to off,
genPortFunctionalStatus = ok) NOTIFICATION-TYPE .1.3.6.1.4.1.81.38.12.0.3024 |
lntVPortAutoPartFltThe valuable port on the module reports the activation of the
autopartition mechanism. This event means that an
excessive number of errors occurred on the port, and the
port is disconnected from the repeater or switch unit. The
network administrator should check the segment and/or end
stations connected to the port for hardware or
misconfiguration problems.
(Bit 1 in the genPortFaultMask set to on,
genPortFunctionalStatus = partition(8)) NOTIFICATION-TYPE .1.3.6.1.4.1.81.38.12.0.3025 |
lntVPortAutoPartOKThe valuable port recovered from a previously
reported auto partition fault.
(Bit 1 in the genPortFaultMask set to off,
genPortFunctionalStatus = ok) NOTIFICATION-TYPE .1.3.6.1.4.1.81.38.12.0.3026 |
lntEthVPortAutoNegotiationFltThe valuable port hardware detects the lack of a connection
to an end station or to another hub or switch. While this
is may not be necessarily a fault condition, the network
administrator's attention is recommended, because the port
was defined as a port.
(Bit 4 in the genPortFaultMask set to on,
scEthPortAutoNegotiationStatus = fail(2)) NOTIFICATION-TYPE .1.3.6.1.4.1.81.38.12.0.3031 |
lntEthVPortAutoNegotiationOKThe port hardware detects the lack of a connection
to an end station or to another hub or switch. While this
is may not be necessarily a fault condition, the network
administrator's attention is recommended, because the port
was defined as a valuable port.
(Bit 4 in the genPortFaultMask set to on,
scEthPortAutoNegotiationStatus = fail(2)) NOTIFICATION-TYPE .1.3.6.1.4.1.81.38.12.0.3032 |
lntPortInlinePowerFltThe Inline Power (Power-over-Ethernet) port hardware reports that the PD (Powered device)
connected to that port is not receiving Inline Power due to a fault condition.
(Bit 37 in the genPortFaultMask set to on,
pethPsePortDetectionStatus = fault(4) or otherfault(6)) NOTIFICATION-TYPE .1.3.6.1.4.1.81.38.12.0.3933 |
lntPortInlinePowerOKThe Inline Power (Power-over-Ethernet) port hardware reports that the PD (Powered device)
connected to that port is not in a fault condition. It may or not be delievering Inline Power
to the PD.
(Bit 37 in the genPortFaultMask set to on,
pethPsePortDetectionStatus = fault(4) or otherfault(6)) NOTIFICATION-TYPE .1.3.6.1.4.1.81.38.12.0.3934 |
lntSecurityEventsDescription. OBJECT IDENTIFIER .1.3.6.1.4.1.81.38.13 |
lntSecurityPrefixDescription. OBJECT IDENTIFIER .1.3.6.1.4.1.81.38.13.0 |
lntUnAuthAccessEventNotification on unauthorized login attempts.
o For CLI and SNMP login failures:
Both SNMP SSH and WEB management interfaces shall identify
situation and alert.
The reported information should include wrong user name,
host name and IP address of remote host. Passwords is not
reported because of the possibility to reveal password.
o For pre-shared-key (PSK) authentication failure in IKE:
* lntUnauthUserName -
- In IKE AM: the ID sent by the remote peer in the ID
payload.
- In IKE MM: the ID associated with the remote peer IP
in the running configuration.
* lntUnauthIpAddress - the source IP of the packet sent
by the remote peer.
* lntUnauthProtocol - lntIKEAccess(500) NOTIFICATION-TYPE .1.3.6.1.4.1.81.38.13.0.68 |
lntMACSecurityEventThis trap notifies the management station of the security violation.
It gives the slot number of the board, the port on the board and the
source MAC address extracted from the frame that has violated
the security policy. The slot and the port numbers, genPortGroupId
and genPortId respectively, define an instance of the appropriate
source address.For the ring security violation the trap contains the ring ID and the
intruder's MAC address. The trap was previously assigned the specific number 11. NOTIFICATION-TYPE .1.3.6.1.4.1.81.38.13.0.104 |
lntUnknownHostCopyEventEvent generated on attempt to accomplish download/upload file
transfer using SCP/SFTP protocol to unknown host. NOTIFICATION-TYPE .1.3.6.1.4.1.81.38.13.0.1002 |
lntAccountLockoutEventAfter configurable number of failed attempts to authenticate a user, device
penalized by locking them out for a pre-specified amount of time. NOTIFICATION-TYPE .1.3.6.1.4.1.81.38.13.0.1003 |
lntLicenseStartupValidationFltAt start-up, the product validates the license file
scheme and the license signature. On inconsistency the product
issues this tarp and then returns to the factory-default feature activation
settings. NOTIFICATION-TYPE .1.3.6.1.4.1.81.38.13.0.1004 |
lntLicenseDownloadValidationFltDuring the license file download, the product validates the license file
scheme and the license signature. On inconsistency the product
aborts download process, sends this notification and
stay with the existing feature activation settings NOTIFICATION-TYPE .1.3.6.1.4.1.81.38.13.0.1005 |
lntDot1xMaxAuthRateReachedEventThis trap notifies the management station that maximum rate of 802.1x
authentications has been reached in module $1 . NOTIFICATION-TYPE .1.3.6.1.4.1.81.38.13.0.1006 |
lntDot1xAuthFailureEventThis trap notifies the management station that device with MAC address
$1 failed to authenticate module/port $2/$3 due to $4 NOTIFICATION-TYPE .1.3.6.1.4.1.81.38.13.0.1007 |
lntDot1xMaxAuthModuleNumReachedEventThis trap notifies the management station that Authentication denied due to
maximum number of authentication of 802.1x $1 per module $2 has been reached. NOTIFICATION-TYPE .1.3.6.1.4.1.81.38.13.0.1008 |
lntDot1xMaxAuthPortNumReachedEventThis trap notifies the management station that Authentication denied due to
maximum number of authentication of 802.1x $1 per module/port $2/$3 has been reached. NOTIFICATION-TYPE .1.3.6.1.4.1.81.38.13.0.1009 |
lntNotificationVarbindsDescription. OBJECT IDENTIFIER .1.3.6.1.4.1.81.38.14 |
lntConfigChangeValueThe text formatted value of MIB object at the time change
configuration has occuredro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.81.38.14.1 |
lntConfigChangeOIDThis variable used to signal the OID of MIB object that had changed
its status and triggered the Change Configuration eventro OBJECT IDENTIFIER .1.3.6.1.4.1.81.38.14.2 |
lntUnauthUserNameThe name of the user who's attempt to access device was identified as unauthorized.ro OCTET STRING .1.3.6.1.4.1.81.38.14.3 |
lntUnauthIpAddressThe IP address of access violating stationro IpAddress .1.3.6.1.4.1.81.38.14.4 |
lntUnauthProtocolThe management protocol employed for the unauthorized access -
lntSSHAccess(22)
lntTELNETAccess(23),
lntHTTPAccess(80),
lntSNMPAccess(161),
lntHTTPSAccess(443),
lntIKEAccess(500),
lntRASAccess(6889),
lntConsoleAccess(6890),
lntPPPAccess(6891)ro Enumeration .1.3.6.1.4.1.81.38.14.5 |
lntSCPStrictCheckingModeThe SCP setting on validity of the public key reported by the SCP server.
If strict setting is yes - then new keys not registered already in hosts file will
be discard and copy operation is aborted. No - device registers new hosts and proceded with copy operation,
ask - requires interactive sessions with the operator ( must fail the SNMP non interactive request)ro Enumeration .1.3.6.1.4.1.81.38.14.6 |
lntLicenseErrorCodesProduct reports following errors if license validations fails
lntSerialNumMismatch(1), - Serial number mismatch between license file
and gateway hardware
lntInvalidSignature(2), - Invalid digital signature on the license file
lntPlatformTypeMismatch(3), - Mismatch between product platform type defined in
license file (for example G250) and the gateway type (e.g. G350).
lntInvalidLicFeture(4) - Invalid feature setting.ro Enumeration .1.3.6.1.4.1.81.38.14.7 |
scGenPortDot1xFailureStringThe text formatted value of MIB object at the time when 802.1x authentication
is failed.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.81.38.14.8 |
lntWanEventsDescription. OBJECT IDENTIFIER .1.3.6.1.4.1.81.38.15 |
lntWanPrefixDescription. OBJECT IDENTIFIER .1.3.6.1.4.1.81.38.15.0 |
lntWanPhysicalAlarmOnDescription. NOTIFICATION-TYPE .1.3.6.1.4.1.81.38.15.0.30 |
lntWanPhysicalAlarmOffDescription. NOTIFICATION-TYPE .1.3.6.1.4.1.81.38.15.0.31 |
lntWanLocalAlarmOnDescription. NOTIFICATION-TYPE .1.3.6.1.4.1.81.38.15.0.32 |
lntWanLocalAlarmOffDescription. NOTIFICATION-TYPE .1.3.6.1.4.1.81.38.15.0.33 |
lntWanRemoteAlarmOnDescription. NOTIFICATION-TYPE .1.3.6.1.4.1.81.38.15.0.34 |
lntWanRemoteAlarmOffDescription. NOTIFICATION-TYPE .1.3.6.1.4.1.81.38.15.0.35 |
lntWanMinorAlarmOnDescription. NOTIFICATION-TYPE .1.3.6.1.4.1.81.38.15.0.36 |
lntWanMinorAlarmOffDescription. NOTIFICATION-TYPE .1.3.6.1.4.1.81.38.15.0.37 |
lntNotificationGroups OBJECT IDENTIFIER .1.3.6.1.4.1.81.38.10007 |
lntNotificationAgentCapabilities OBJECT IDENTIFIER .1.3.6.1.4.1.81.38.10008 |