Lannet-Trapsv2-MIB: View SNMP OID List / Download MIB

VENDOR: LANNET COMPANY


 Home MIB: Lannet-Trapsv2-MIB
Download as:   
SNMPv2-CONF, SNMPv2-TC, IF-MIB, SNMPv2-MIB, CONFIG-MIB, SNMPv2-SMI, XSWITCH-MIB, IP-MIB, RMON-MIB, GEN-MIB, DS1-MIB, APPLIC-MIB, POLICY-MIB

Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
Keep in mind that standard MIB files can be successfully loaded by systems and programs only if all the required MIB's from the "Imports" section are already loaded.
The tree-like SNMP object navigator requires no explanations because it is very simple to use. And if you stumbled on this MIB from Google note that you can always go back to the home page if you need to perform another MIB or OID lookup.


Object Name OID Type Access Info
 lntTraps 1.3.6.1.4.1.81.38
SMIv2 definition of p330/P130 traps
       lntConfigChangeEvents 1.3.6.1.4.1.81.38.1
Groups together all configuration change related events
           lntConfigChangePrefix 1.3.6.1.4.1.81.38.1.0
The next to last sub- identifier in the name of any newly-defined notification must have the value zero
               lntConfigChangeEvent 1.3.6.1.4.1.81.38.1.0.1
Notification generated in case of configuration change. List of events triggering notitication is TBD
               lntStackMasterReelection 1.3.6.1.4.1.81.38.1.0.82
The trap should be triggered in an event that an election process leads to selection of a different module as a Stack Master
       lntSWRedundancyEvents 1.3.6.1.4.1.81.38.2
Groups together all software redundancy related events
           lntSWRedundancyPrefix 1.3.6.1.4.1.81.38.2.0
The next to last sub- identifier in the name of any newly-defined notification must have the value zero
               lntSoftRedDelEvent 1.3.6.1.4.1.81.38.2.0.12
The trap notifies the manager of the deletion of the specified redundant link, which is identified by the softRedundancyId.
               lntSoftRedNewEvent 1.3.6.1.4.1.81.38.2.0.13
The 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.
       lntTempratureEvents 1.3.6.1.4.1.81.38.3
Groups together all temprature related events
           lntTempratureWarningPrefix 1.3.6.1.4.1.81.38.3.0
The next to last sub- identifier in the name of any newly-defined notification must have the value zero
               lntTempratureWarning 1.3.6.1.4.1.81.38.3.0.14
This trap notifies the management station of the internal board/enclosure temperature fluctuations. It is generated when the temperature exceeds the threshold chHWIntTempThresh.
               lntTempratureOk 1.3.6.1.4.1.81.38.3.0.23
This trap notifies the management station that the internal board/enclosure temperature fluctuations situation is back to normal.
       lntCAMChangeEvents 1.3.6.1.4.1.81.38.4
Groups together all CAM related events
           lntCAMChangePrefix 1.3.6.1.4.1.81.38.4.0
The next to last sub- identifier in the name of any newly-defined notification must have the value zero
               lntPortCAMLastChange 1.3.6.1.4.1.81.38.4.0.22
This trap reports of the occurred CAM changes
       lntPSUEvents 1.3.6.1.4.1.81.38.5
Groups together all Power supply related events
           lntPSUPrefix 1.3.6.1.4.1.81.38.5.0
The next to last sub- identifier in the name of any newly-defined notification must have the value zero
               lntMainPSUFlt 1.3.6.1.4.1.81.38.5.0.2303
An 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
               lntMainPSUOk 1.3.6.1.4.1.81.38.5.0.2304
The network device recovered after a previously reported problem in the operation of the box Main Power Supply
               lntBackupPSUFlt 1.3.6.1.4.1.81.38.5.0.2305
An 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.
               lntBackupPSUOk 1.3.6.1.4.1.81.38.5.0.2306
The network device recovered after a previously reported problem in the operation of the box Backup Power Supply.
       lntL3Events 1.3.6.1.4.1.81.38.6
Groups together routing( L3) related events.
           lntL3FaultsPrefix 1.3.6.1.4.1.81.38.6.0
The next to last sub- identifier in the name of any newly-defined notification must have the value zero
               lntDuplicateIPFlt 1.3.6.1.4.1.81.38.6.0.27
This 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.
               lntVLANViolationEvent 1.3.6.1.4.1.81.38.6.0.28
This 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.
               lntARPViolationEvent 1.3.6.1.4.1.81.38.6.0.70
This 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
       lntLinkEvents 1.3.6.1.4.1.81.38.7
Groups together port link up/down related events.
           lntLinkEventsPrefix 1.3.6.1.4.1.81.38.7.0
The next to last sub- identifier in the name of any newly-defined notification must have the value zero
               lntPortLinkDownEvent 1.3.6.1.4.1.81.38.7.0.3039
The 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) )
               lntPortLinkUpEvent 1.3.6.1.4.1.81.38.7.0.3040
The port recovered from a previously reported connectivity problem. (Bit 7 in the genPortFaultMask set to off, genPortFunctionalStatus = ok)
               lntVPortLinkDownEvent 1.3.6.1.4.1.81.38.7.0.3041
The 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))
               lntVPortLinkUpEvent 1.3.6.1.4.1.81.38.7.0.3042
Acknowledegs link up condition on a valuable port. (Bit 7 in the genPortFaultMask set to off, genPortFunctionalStatus = ok)
       lntLAGEvents 1.3.6.1.4.1.81.38.8
Groups together LAG related events.
           lntLAGPrefix 1.3.6.1.4.1.81.38.8.0
The next to last sub- identifier in the name of any newly-defined notification must have the value zero
               lntLAGConnLostFlt 1.3.6.1.4.1.81.38.8.0.44
The trap reports on a LAG connection lost. It is sent when scGenLinkAggregationFunctionalStatus changed to fail (2).
               lntLAGConnLostOk 1.3.6.1.4.1.81.38.8.0.46
The trap reports that the LAG connection lost was cleared. It is sent when scGenLinkAggregationFunctionalStatus changed from fail(2) to to ok(1).
               lntLAGPartialConnLostFlt 1.3.6.1.4.1.81.38.8.0.48
The 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).
               lntLAGPartialConnLostOk 1.3.6.1.4.1.81.38.8.0.50
The trap reports that the LAG partial connection was cleared. It is sent when scGenLinkAggregationFunctionalStatus changed from partialFail (3)to to ok(1).
               lntLAGAutoNegFlt 1.3.6.1.4.1.81.38.8.0.52
The trap reports on a auto-negotiation results on the LAG ports. It is sent when scGenLinkAggregationAutoNegResults changed to autoNegInconsistantResults (2).
               lntLAGAutoNegOk 1.3.6.1.4.1.81.38.8.0.54
The 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).
               lntLAGDeleteEvent 1.3.6.1.4.1.81.38.8.0.56
The trap notifies the manager of the deletion of the specified LAG, which is identified by the scGenLinkAggregationId.
               lntLAGCreateEvent 1.3.6.1.4.1.81.38.8.0.58
The trap is generated on the creation of a new LAG, which is identified by the scGenLinkAggregationId.
       lntFansEvents 1.3.6.1.4.1.81.38.9
Groups together fans related events.
           lntFansPrefix 1.3.6.1.4.1.81.38.9.0
The next to last sub- identifier in the name of any newly-defined notification must have the value zero
               lntMainFansFlt 1.3.6.1.4.1.81.38.9.0.2307
The trap reports the failure of one (or more) module's Fan. It is sent when scGenGroupFansStatus changed to oneFanFailed(2)
               lntMainFansOK 1.3.6.1.4.1.81.38.9.0.2308
The 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).
               lntBackupFansFlt 1.3.6.1.4.1.81.38.9.0.2309
The trap reports the failure of one (or more) BUPS module's Fan. It is sent when scGenGroupBUPSFansStatus changed to oneFanFailed(2).
               lntBackupFansOK 1.3.6.1.4.1.81.38.9.0.2310
The 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).
       lntCascadeEvents 1.3.6.1.4.1.81.38.10
Groups together stakc module cascading related events.
             lntCascadeFaultsPrefix 1.3.6.1.4.1.81.38.10.0
The next to last sub- identifier in the name of any newly-defined notification must have the value zero
                 lntCascadUpConnFlt 1.3.6.1.4.1.81.38.10.0.2315
The trap reports on a cascading up connection lost. It is sent when genGroupCascadUpStatus changed to rld(2).
                 lntCascadUpConnOk 1.3.6.1.4.1.81.38.10.0.2316
The trap reports that the cascading up connection lost was cleared. It is sent when genGroupCascadUpStatus changed from rld(2) to ok(1).
                 lntCascadDownConnFlt 1.3.6.1.4.1.81.38.10.0.2317
The trap reports on a cascading down connection lost. It is sent when genGroupCascadDownStatus changed to rld(2).
                 lntCascadDownConnOk 1.3.6.1.4.1.81.38.10.0.2318
The trap reports that the cascading down connection lost was cleared. It is sent when genGroupCascadDownStatus changed from rld(2) to ok(1).
       lntPolicyEvents 1.3.6.1.4.1.81.38.11
Groups together policy related events.
             lntPolicyPrefix 1.3.6.1.4.1.81.38.11.0
The next to last sub- identifier in the name of any newly-defined notification must have the value zero
                 lntPolicyChangeEvent 1.3.6.1.4.1.81.38.11.0.60
The trap reports a change in the active list specific for a policy-enabled box or module
                 lntPolicyAccessControlListLvlRuleTrap 1.3.6.1.4.1.81.38.11.0.62
This 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.
                 lntPolicyAccessControlViolationFlt 1.3.6.1.4.1.81.38.11.0.64
This 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
       lntEthPortFaultEvents 1.3.6.1.4.1.81.38.12
Groups together Etherent port related events.
             lntEthPortFaultPrefix 1.3.6.1.4.1.81.38.12.0
The next to last sub- identifier in the name of any newly-defined notification must have the value zero
                 lntEthPortAutoNegotiationFlt 1.3.6.1.4.1.81.38.12.0.3001
The port recovered from a previously reported connectivity problem. (Bit 4 in the genPortFaultMask set to off, scEthPortAutoNegotiationStatus = ok)
                 lntEthPortAutoNegotiationOK 1.3.6.1.4.1.81.38.12.0.3002
The port recovered from a previously reported connectivity problem. (Bit 4 in the genPortFaultMask set to off, scEthPortAutoNegotiationStatus = ok)
                 lntPortFEFlt 1.3.6.1.4.1.81.38.12.0.3005
The 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)
                 lntPortFEOk 1.3.6.1.4.1.81.38.12.0.3006
A 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))
                 lntVPortFEFlt 1.3.6.1.4.1.81.38.12.0.3015
The 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))
                 lntVPortFEOk 1.3.6.1.4.1.81.38.12.0.3016
A 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))
                 lntPortAutoPartFlt 1.3.6.1.4.1.81.38.12.0.3023
The 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))
                 lntPortAutoPartOk 1.3.6.1.4.1.81.38.12.0.3024
The port recovered from a previously reported auto partition fault. (Bit 1 in the genPortFaultMask set to off, genPortFunctionalStatus = ok)
                 lntVPortAutoPartFlt 1.3.6.1.4.1.81.38.12.0.3025
The 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))
                 lntVPortAutoPartOK 1.3.6.1.4.1.81.38.12.0.3026
The valuable port recovered from a previously reported auto partition fault. (Bit 1 in the genPortFaultMask set to off, genPortFunctionalStatus = ok)
                 lntEthVPortAutoNegotiationFlt 1.3.6.1.4.1.81.38.12.0.3031
The 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))
                 lntEthVPortAutoNegotiationOK 1.3.6.1.4.1.81.38.12.0.3032
The 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))
                 lntPortInlinePowerFlt 1.3.6.1.4.1.81.38.12.0.3933
The 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))
                 lntPortInlinePowerOK 1.3.6.1.4.1.81.38.12.0.3934
The 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))
       lntSecurityEvents 1.3.6.1.4.1.81.38.13
Description.
             lntSecurityPrefix 1.3.6.1.4.1.81.38.13.0
Description.
                 lntUnAuthAccessEvent 1.3.6.1.4.1.81.38.13.0.68
Notification 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)
                 lntMACSecurityEvent 1.3.6.1.4.1.81.38.13.0.104
This 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.
                 lntUnknownHostCopyEvent 1.3.6.1.4.1.81.38.13.0.1002
Event generated on attempt to accomplish download/upload file transfer using SCP/SFTP protocol to unknown host.
                 lntAccountLockoutEvent 1.3.6.1.4.1.81.38.13.0.1003
After configurable number of failed attempts to authenticate a user, device penalized by locking them out for a pre-specified amount of time.
                 lntLicenseStartupValidationFlt 1.3.6.1.4.1.81.38.13.0.1004
At 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.
                 lntLicenseDownloadValidationFlt 1.3.6.1.4.1.81.38.13.0.1005
During 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
                 lntDot1xMaxAuthRateReachedEvent 1.3.6.1.4.1.81.38.13.0.1006
This trap notifies the management station that maximum rate of 802.1x authentications has been reached in module $1 .
                 lntDot1xAuthFailureEvent 1.3.6.1.4.1.81.38.13.0.1007
This trap notifies the management station that device with MAC address $1 failed to authenticate module/port $2/$3 due to $4
                 lntDot1xMaxAuthModuleNumReachedEvent 1.3.6.1.4.1.81.38.13.0.1008
This trap notifies the management station that Authentication denied due to maximum number of authentication of 802.1x $1 per module $2 has been reached.
                 lntDot1xMaxAuthPortNumReachedEvent 1.3.6.1.4.1.81.38.13.0.1009
This 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.
       lntNotificationVarbinds 1.3.6.1.4.1.81.38.14
Description.
             lntConfigChangeValue 1.3.6.1.4.1.81.38.14.1 displaystring no-access
The text formatted value of MIB object at the time change configuration has occured
             lntConfigChangeOID 1.3.6.1.4.1.81.38.14.2 object identifier no-access
This variable used to signal the OID of MIB object that had changed its status and triggered the Change Configuration event
             lntUnauthUserName 1.3.6.1.4.1.81.38.14.3 octet string no-access
The name of the user who's attempt to access device was identified as unauthorized.
             lntUnauthIpAddress 1.3.6.1.4.1.81.38.14.4 ipaddress no-access
The IP address of access violating station
             lntUnauthProtocol 1.3.6.1.4.1.81.38.14.5 integer no-access
The management protocol employed for the unauthorized access - lntSSHAccess(22) -- SSH protocol lntTELNETAccess(23), --Telnet protocol lntHTTPAccess(80), -- HTTP protocol lntSNMPAccess(161), -- SNMP protocol lntHTTPSAccess(443), -- HTTPS protocol over TLS sockets lntIKEAccess(500), -- IKE protocol - PSK authentication failure lntRASAccess(6889), -- RAS access over dial-up connection lntConsoleAccess(6890), -- Access from the Console port lntPPPAccess(6891) -- Access to PPP over modem Enumeration: 'lntHTTPSAccess': 443, 'lntRASAccess': 6889, 'lntPPPAccess': 6891, 'lntConsoleAccess': 6890, 'lntTELNETAccess': 23, 'lntIKEAccess': 500, 'lntSSHAccess': 22, 'lntHTTPAccess': 80, 'lntSNMPAccess': 161.
             lntSCPStrictCheckingMode 1.3.6.1.4.1.81.38.14.6 integer no-access
The 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) Enumeration: 'ask': 3, 'yes': 1, 'no': 2.
             lntLicenseErrorCodes 1.3.6.1.4.1.81.38.14.7 integer no-access
Product 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. Enumeration: 'lntPlatformTypeMismatch': 3, 'lntInvalidLicFeture': 4, 'lntInvalidSignature': 2, 'lntSerialNumMismatch': 1.
             scGenPortDot1xFailureString 1.3.6.1.4.1.81.38.14.8 displaystring no-access
The text formatted value of MIB object at the time when 802.1x authentication is failed.
       lntWanEvents 1.3.6.1.4.1.81.38.15
Description.
             lntWanPrefix 1.3.6.1.4.1.81.38.15.0
Description.
                 lntWanPhysicalAlarmOn 1.3.6.1.4.1.81.38.15.0.30
Description.
                 lntWanPhysicalAlarmOff 1.3.6.1.4.1.81.38.15.0.31
Description.
                 lntWanLocalAlarmOn 1.3.6.1.4.1.81.38.15.0.32
Description.
                 lntWanLocalAlarmOff 1.3.6.1.4.1.81.38.15.0.33
Description.
                 lntWanRemoteAlarmOn 1.3.6.1.4.1.81.38.15.0.34
Description.
                 lntWanRemoteAlarmOff 1.3.6.1.4.1.81.38.15.0.35
Description.
                 lntWanMinorAlarmOn 1.3.6.1.4.1.81.38.15.0.36
Description.
                 lntWanMinorAlarmOff 1.3.6.1.4.1.81.38.15.0.37
Description.
       lntNotificationGroups 1.3.6.1.4.1.81.38.10007
                   lntConfigChangeVarbinds 1.3.6.1.4.1.81.38.10007.1
varbinds related with config change trap
                   lntLagNotificationGroup 1.3.6.1.4.1.81.38.10007.5
Group of Link aggregation traps
                   lntSWRedundancyNotificationGroup 1.3.6.1.4.1.81.38.10007.6
Group of Software Redundancy traps
                   lntPSUFaultNotificationGroup 1.3.6.1.4.1.81.38.10007.7
PSU related fault traps (main and backup)
                   lntTempratureNotificationGroup 1.3.6.1.4.1.81.38.10007.8
Temperature warning related traps
                   lntL3FaultNotificationGroup 1.3.6.1.4.1.81.38.10007.9
Group of L3 fault traps
                   lntLinkDownNotificationGroup 1.3.6.1.4.1.81.38.10007.10
Link Down/Up traps
                   lntCascadeNotificationGroup 1.3.6.1.4.1.81.38.10007.11
Cascade fault traps
                   lntEthPortNotificationGroup 1.3.6.1.4.1.81.38.10007.12
Eth port fault traps
                   lntCAMNotificationGroup 1.3.6.1.4.1.81.38.10007.13
CAM change related traps
                   lntConfigChangeNotificationGroup 1.3.6.1.4.1.81.38.10007.14
Configuration change related traps
                   lntPolicyNotificationGroup 1.3.6.1.4.1.81.38.10007.15
policy related traps
                   lntFansNotificationGroup 1.3.6.1.4.1.81.38.10007.16
Notifications related with FAN problems
                   lntSecurityNotificationGroup 1.3.6.1.4.1.81.38.10007.17
Description.
                   lntWanNotificationGroup 1.3.6.1.4.1.81.38.10007.18
Description.
       lntNotificationAgentCapabilities 1.3.6.1.4.1.81.38.10008
                   lntP330L3NotificationAgentCapabilities 1.3.6.1.4.1.81.38.10008.1
Trap Capabilities of P330 L3 Device.
                   lntP330L2NotificationAgentCapabilities 1.3.6.1.4.1.81.38.10008.2
Trap capabilities of P330 L2 device.
                   lntP130TrapAgentCapabilities 1.3.6.1.4.1.81.38.10008.3
Trap capabilities of P130 device.
                   lntP330MLNotificationAgentCapabilities 1.3.6.1.4.1.81.38.10008.4
Traps supported by P330ML device.
                   lntG350NotificationAgentCapability 1.3.6.1.4.1.81.38.10008.5
Description.