Notification generated in case of configuration change.
List of events triggering notitication is TBD

The trap should be triggered in an event that an election process 
leads to selection of a different module as a Stack Master

The trap reports on a cascading up connection lost. 
It is sent when genGroupCascadUpStatus changed to rld(2).

The trap reports that the cascading up connection lost 
was cleared. It is sent when genGroupCascadUpStatus changed from rld(2) to ok(1).

The trap reports on a cascading down connection lost. 
It is sent when genGroupCascadDownStatus changed to rld(2).

The trap reports that the cascading down connection lost 
was cleared. It is sent when genGroupCascadDownStatus 
changed from rld(2) to ok(1).

The trap reports a change in the active list specific for a 
policy-enabled box or module

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.

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

The port recovered from a previously reported
connectivity problem. (Bit 4 in the genPortFaultMask set to off, 
scEthPortAutoNegotiationStatus = ok)

The port recovered from a previously reported
connectivity problem. (Bit 4 in the genPortFaultMask set to off, 
scEthPortAutoNegotiationStatus = ok)

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)

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))

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))

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))

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))

The port recovered from a previously reported auto
partition fault.
(Bit 1 in the genPortFaultMask set to off, 
genPortFunctionalStatus = ok)

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))

The valuable port recovered from a previously 
reported auto partition fault.
(Bit 1 in the genPortFaultMask set to off, 
genPortFunctionalStatus = ok)

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))

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))

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))

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))

Event generated on attempt to accomplish download/upload file 
transfer using SCP/SFTP protocol to unknown host.

After configurable number of failed attempts to authenticate a user, device 
penalized by locking them out for a pre-specified amount of time.

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.

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

This trap notifies the management station that maximum rate of 802.1x 
authentications has been reached in module $1 .

This trap notifies the management station that device with MAC address 
$1 failed to authenticate module/port $2/$3 due to $4

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.

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.

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.

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)

Description.

Description.

Description.

Description.

Description.

Description.

Description.

Description.

The trap notifies the manager of the deletion of the specified 
redundant link, which is identified by the softRedundancyId.

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.

This trap notifies the management station of the internal 
board/enclosure temperature fluctuations. It is generated when
the temperature exceeds the threshold chHWIntTempThresh.

This trap notifies the management station that the internal
board/enclosure temperature fluctuations situation is back to normal.

This trap reports of the occurred CAM changes

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

The network device recovered after a previously reported problem
in the operation of the box Main Power Supply

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.

The network device recovered after a previously reported problem
in the operation of the box Backup Power Supply.

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.

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.

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

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)
)

The port recovered from a previously reported
connectivity problem.
(Bit 7 in the genPortFaultMask set to off, 
genPortFunctionalStatus = ok)

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))

Acknowledegs link up condition on a valuable port.
(Bit 7 in the genPortFaultMask set to off, 
genPortFunctionalStatus = ok)

The trap reports on a LAG connection lost. It is sent when
scGenLinkAggregationFunctionalStatus changed to fail (2).

The trap reports that the LAG connection lost was cleared.
It is sent when scGenLinkAggregationFunctionalStatus changed 
from fail(2) to to ok(1).

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).

The trap reports that the LAG partial connection was cleared. 
It is sent when scGenLinkAggregationFunctionalStatus 
changed from partialFail (3)to to ok(1).

The trap reports on a auto-negotiation results on the LAG ports. 
It is sent when scGenLinkAggregationAutoNegResults 
changed to autoNegInconsistantResults (2).

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).

The trap notifies the manager of the deletion of the specified LAG,
which is identified by the scGenLinkAggregationId.

The trap is generated on the creation of a new LAG,
which is identified by the scGenLinkAggregationId.

The trap reports the failure of one (or more) 
module's Fan. It is sent when scGenGroupFansStatus changed 
to oneFanFailed(2)

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).

The trap reports the failure of one 
(or more) BUPS module's Fan. It is sent when 
scGenGroupBUPSFansStatus changed to 
oneFanFailed(2).

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).