This document is the SNMP MIB module to manage and provision the
various services of the Nokia SROS system.
Copyright 2003-2018 Nokia. All rights reserved. Reproduction of this
document is authorized on the condition that the foregoing copyright
notice is included.
This SNMP MIB module (Specification) embodies Nokia's
proprietary intellectual property. Nokia retains
all title and ownership in the Specification, including any
revisions.
Nokia grants all interested parties a non-exclusive license to use and
distribute an unmodified copy of this Specification in connection with
management of Nokia products, and without fee, provided this copyright
notice and license appear on all copies.
This Specification is supplied 'as is', and Nokia makes no warranty,
either express or implied, as to the use, operation, condition, or
performance of the Specification.
This trap is sent when a new row is created in the sapBaseInfoTable.
sapDHCPLseStateOverride
.1.3.6.1.4.1.6527.3.1.3.4.3.0.10
The sapDHCPLseStateOverride notification is generated when an existing
DHCP lease state is overridden by a new lease state which has the same
IP address but a different MAC address.
sapDHCPSuspiciousPcktRcvd
.1.3.6.1.4.1.6527.3.1.3.4.3.0.11
The sapDHCPSuspiciousPcktRcvd notification is generated when a DHCP
packet is received with suspicious content.
sapDHCPLseStatePopulateErr
.1.3.6.1.4.1.6527.3.1.3.4.3.0.12
The sapDHCPLseStatePopulateErr notification indicates that the system
was unable to update the DHCP Lease State table with the information
contained in the DHCP ACK message. The DHCP ACK message has been
discarded.
hostConnectivityLost
.1.3.6.1.4.1.6527.3.1.3.4.3.0.13
The hostConnectivityLost notification indicates that the system lost
the connectivity with the indicated host.
The value of hostConnectivityCiAddr is the nominal IP address that
identifies the host.
The value of sapNotifyIpAddr is the IP address that was actually used
for the host connectivity verification; the two may be different for a
host with multiple IP addresses.
hostConnectivityRestored
.1.3.6.1.4.1.6527.3.1.3.4.3.0.14
The hostConnectivityRestored notification indicates that the system
has restored the connectivity with the indicated host.
The value of hostConnectivityCiAddr is the nominal IP address that
identifies the host.
The value of sapNotifyIpAddr is the IP address that was actually used
for the host connectivity verification; the two may be different for a
host with multiple IP addresses.
sapReceivedProtSrcMac
.1.3.6.1.4.1.6527.3.1.3.4.3.0.15
The sapReceivedProtSrcMac notification is generated when a protected
source MAC is received on a TLS SAP with sapTlsRestProtSrcMac 'true',
or if the TLS SAP belongs to an SHG with tlsShgRestProtSrcMac 'true'.
sapStaticHostDynMacConflict
.1.3.6.1.4.1.6527.3.1.3.4.3.0.16
The sapStaticHostDynMacConflict notification indicates that the system
is trying to learn a conflicting IP-only static host dynamic MAC
address (sapStaticHostDynMacAddress).
sapTlsMacMoveExceeded
.1.3.6.1.4.1.6527.3.1.3.4.3.0.17
The sapTlsMacMoveExceeded notification is generated when the SAP
exceeds the TLS svcTlsMacMoveMaxRate.
sapDHCPProxyServerError
.1.3.6.1.4.1.6527.3.1.3.4.3.0.18
The sapDHCPProxyServerError notification indicates that the system was
unable to proxy DHCP requests.
sapDHCPCoAError
.1.3.6.1.4.1.6527.3.1.3.4.3.0.19
The sapDHCPCoAError notification indicates that the system was unable
to process a Change of Authorization (CoA) request from a Radius
server.
sapDeleted
.1.3.6.1.4.1.6527.3.1.3.4.3.0.2
This trap is sent when an existing row is deleted from the
sapBaseInfoTable.
sapDHCPSubAuthError
.1.3.6.1.4.1.6527.3.1.3.4.3.0.20
The sapDHCPSubAuthError notification indicates that the system
encountered a problem while trying to authenticate a subscriber.
sapPortStateChangeProcessed
.1.3.6.1.4.1.6527.3.1.3.4.3.0.21
The sapPortStateChangeProcessed notification indicates that the agent
has finished processing an access port state change event, and that
the operating status of all the affected SAPs has been updated
accordingly. The value of the sapNotifyPortId object indicates the ID
of the port that experienced the state change. The value of the
sapNotifyPortState object indicates the current state of the port.
sapDHCPLseStateMobilityError
.1.3.6.1.4.1.6527.3.1.3.4.3.0.22
The sapDHCPLseStateMobilityError notification indicates that the
system was unable to perform a mobility check for this lease state.
sapCemPacketDefectAlarm
.1.3.6.1.4.1.6527.3.1.3.4.3.0.23
Generated when a CEM SAP alarm condition is detected. It is generated
only when the packet error indicated by 'sapCemReportAlarmStatus'
persists over a 3 second window. tmnxPortCemStatsReportAlarm
specifies, in the case of APS Ports, the physical port raising the
trap, otherwise it is the SAP's port.
sapCemPacketDefectAlarmClear
.1.3.6.1.4.1.6527.3.1.3.4.3.0.24
Generated when a CEM SAP alarm condition is cleared. It is generated
only when the packet error indicated by 'sapCemReportAlarmStatus' no
longer persists over a 10 second window. tmnxPortCemStatsReportAlarm
specifies, in the case of APS Ports, the physical port raising the
trap, otherwise it is the SAP's port.
msapStateChanged
.1.3.6.1.4.1.6527.3.1.3.4.3.0.25
The msapStateChanged notification is generated when a Managed SAP is
'created', 'modified', or 'deleted', with the value of msapStatus
indicated which state it has entered.
msapCreationFailure
.1.3.6.1.4.1.6527.3.1.3.4.3.0.26
The trap msapCreationFailure is sent whenever the system fails to
create a managed SAP. The svcId, svcVpnId, sapPortId and sapEncapValue
are those of the capturing SAP.
The values of sapNotifyPortId and sapNotifyEncapValue correspond to
the managed SAP, and the value of sapTlsNotifyMacAddr is the MAC
address that would have been associated with the managed SAP, if the
creation would have succeeded.
sapHostBGPPeeringSetupFailed
.1.3.6.1.4.1.6527.3.1.3.4.3.0.27
The sapHostBGPPeeringSetupFailed notification indicates that the
system was unable to create a BGP neighbor and set up BGP peering for
the given host.
sapTlsDataSapInstStatusChgd
.1.3.6.1.4.1.6527.3.1.3.4.3.0.28
The sapTlsDataSapInstStatusChgd notification is generated when there
is a change in the value of sapTlsDataSapInstStatus object.
sapTlsDataSapInstLastErr provides information related to
sapTlsDataSapInstStatus object.
tmnxGreTunnelOperRemIpChg
.1.3.6.1.4.1.6527.3.1.3.4.3.0.29
[CAUSE] The tmnxGreTunnelOperRemIpChg notification is generated when
there is a change in operational remote address
'tmnxGreTunnelOperRemIpAddr' of the tunnel.
[EFFECT] Operational state of the tunnel is not affected.
[RECOVERY] Operator needs to look at the configuration of
tmnxGreTunnelRemIpAddr and tmnxGreTunnelBackupRemIpAddr.
sapStatusChanged
.1.3.6.1.4.1.6527.3.1.3.4.3.0.3
The sapStatusChanged notification is generated when there is a change
in the administrative or operating status of an SAP.
Notice that this trap is not generated whenever the SAP operating
status change is caused by an operating status change on the
associated access port.
sapTunnelStateChange
.1.3.6.1.4.1.6527.3.1.3.4.3.0.30
[CAUSE] The sapTunnelStateChange notification is generated when
IPsec/GRE tunnel indicated by sapTunnelNotifyName changes state to
'down' due to sapTunnelNotifyReason.
[EFFECT] IPsec/GRE tunnel associated with the SAP will remain in this
state until a corrective action is taken.
[RECOVERY] Depending on the reason indicated by sapTunnelNotifyReason,
corrective action should be taken.
sapAtmPppSessionFailure
.1.3.6.1.4.1.6527.3.1.3.4.3.0.31
[CAUSE] The sapAtmPppSessionFailure notification indicates that the
system could not create a new PPPoA session.
The problem is described in the object sapNotifyReason.
The PPP user name is specified in the sapNotifyName.
[EFFECT] The user that attempted to set up the PPP session cannot
establish the desired connection.
[RECOVERY] Depending on the reason indicated by sapNotifyReason,
corrective action may be necessary. However, it is possible that the
failure is caused by the user's equipment configuration or by
erroneous input by the user.
sapAtmPppNcpFailure
.1.3.6.1.4.1.6527.3.1.3.4.3.0.32
[CAUSE] The sapAtmPppNcpFailure notification indicates that there is a
NCP phase setup problem.
The problem is described in the object sapNotifyReason.
The PPP user name is specified in the sapNotifyName.
[EFFECT] The IP protocol cannot be configured for the user that
attempted to set up the PPP session.
[RECOVERY] Depending on the reason indicated by sapNotifyReason,
corrective action may be necessary. However, it is possible that the
failure is caused by the user's equipment configuration or by
erroneous input by the user.
sapIpipeCeIpAddrChange
.1.3.6.1.4.1.6527.3.1.3.4.3.0.33
[CAUSE] The sapIpipeCeIpAddrChange notification indicates that an IP
address has been discovered for the local end host of a specified
IPIPE SAP. The IP address type is specified by sapIpipeCeIpAddrType.
The IP address is specified by sapIpipeCeIpAddress.
[EFFECT] The IP address specified by sapIpipeCeIpAddress and of type
sapIpipeCeIpAddrType has been discovered for the local end host.
[RECOVERY] No action is required
tmnxIpTunnelOperRemIpChg
.1.3.6.1.4.1.6527.3.1.3.4.3.0.38
[CAUSE] The tmnxIpTunnelOperRemIpChg notification is generated when
there is a change in operational remote address
'tmnxIpTunnelOperRemIpAddr' of the tunnel.
[EFFECT] Operational state of the tunnel is not affected.
[RECOVERY] Operator needs to look at the configuration of
tmnxIpTunnelRemIpAddr and tmnxIpTunnelBackupRemIpAddr.
sapDcpStaticExcd
.1.3.6.1.4.1.6527.3.1.3.4.3.0.39
[CAUSE] The sapDcpStaticExcd notification is generated when the
static-policer on a particular SAP has been detected as non-conformant
to the associated distributed CPU protection policy parameters. This
notification is generated when
TIMETRA-SECURITY-MIB.mib::tmnxDCpuProtStaticPlcrLogEvent is configured
to 'enable' or 'verbose'.
[EFFECT] The affected SAP may be using more resources than expected
and cause the system to underperform. This notification may indicate a
Denial of Service attack or a misconfiguration in the network.
[RECOVERY] Appropriate configuration changes to the distributed CPU
protection policy or to the affected SAP may be required.
sapTlsMacAddrLimitAlarmRaised
.1.3.6.1.4.1.6527.3.1.3.4.3.0.4
The trap sapTlsMacAddrLimitAlarmRaised is sent whenever the number of
MAC addresses stored in the FDB for this SAP increases to reach the
watermark specified by the object svcTlsFdbTableFullHighWatermark.
sapDcpDynamicExcd
.1.3.6.1.4.1.6527.3.1.3.4.3.0.40
[CAUSE] The sapDcpDynamicExcd notification is generated when the
protocol on a particular SAP has been detected as non-conformant to
the associated distributed CPU protection policy parameters. This
notification is generated when
TIMETRA-SECURITY-MIB.mib::tmnxDCpuProtProtocolDynLogEvent is
configured to 'enable' or 'verbose'.
[EFFECT] The affected SAP may be using more resources than expected
and cause the system to underperform. This notification may indicate a
Denial of Service attack or a misconfiguration in the network.
[RECOVERY] Appropriate configuration changes to the distributed CPU
protection policy or to the affected SAP may be required.
sapDcpStaticHoldDownStart
.1.3.6.1.4.1.6527.3.1.3.4.3.0.41
[CAUSE] The sapDcpStaticHoldDownStart notification is generated when a
particular SAP starts hold-down period for an exceeding
static-policer. This notification is generated when
TIMETRA-SECURITY-MIB.mib::tmnxDCpuProtStaticPlcrLogEvent is configured
to 'verbose'.
[EFFECT] The static-policer will treat all packets as non-conformant
during the hold-down period.
[RECOVERY] There is no recovery required for this notification.
sapDcpDynamicHoldDownStart
.1.3.6.1.4.1.6527.3.1.3.4.3.0.42
[CAUSE] The sapDcpDynamicHoldDownStart notification is generated when
a particular SAP starts hold-down period for an exceeding protocol.
This notification is generated when
TIMETRA-SECURITY-MIB.mib::tmnxDCpuProtProtocolDynLogEvent is
configured to 'verbose'.
[EFFECT] The protocol will treat all packets as non-conformant during
the hold-down period.
[RECOVERY] There is no recovery required for this notification.
sapDcpStaticHoldDownEnd
.1.3.6.1.4.1.6527.3.1.3.4.3.0.43
[CAUSE] The sapDcpStaticHoldDownEnd notification is generated when a
particular SAP completes hold-down period for an exceeding
static-policer. This notification is generated when
TIMETRA-SECURITY-MIB.mib::tmnxDCpuProtStaticPlcrLogEvent is configured
to 'verbose'.
[EFFECT] The static-policer for an affected SAP will transition to a
detection-time countdown after the hold-down period is complete.
[RECOVERY] There is no recovery required for this notification.
sapDcpDynamicHoldDownEnd
.1.3.6.1.4.1.6527.3.1.3.4.3.0.44
[CAUSE] The sapDcpDynamicHoldDownEnd notification is generated
when a particular SAP completes hold-down period for an exceeding
protocol. This notification is generated when
TIMETRA-SECURITY-MIB.mib::tmnxDCpuProtProtocolDynLogEvent is configured
to 'verbose'.
[EFFECT] The protocol for an affected SAP will transition to a
detection-time countdown after the hold-down period is complete.
[RECOVERY] There is no recovery required for this notification.
sapDcpStaticConform
.1.3.6.1.4.1.6527.3.1.3.4.3.0.45
[CAUSE] The sapDcpStaticConform notification is generated when the
static-policer for a particular SAP has been detected as conformant
for a period of the configured detection-time after having been
previously detected as exceeding and completed any hold-down period.
This notification is generated when
TIMETRA-SECURITY-MIB.mib::tmnxDCpuProtStaticPlcrLogEvent is configured
to 'enable' or 'verbose'.
[EFFECT] The affected SAP is now in conformance with the parameters
configured for the associated distributed CPU protection policy.
[RECOVERY] There is no recovery required for this notification.
sapDcpDynamicConform
.1.3.6.1.4.1.6527.3.1.3.4.3.0.46
[CAUSE] The sapDcpDynamicConform notification is generated when the
protocol for a particular SAP has been detected as conformant for a
period of the configured detection-time after having been previously
detected as exceeding and completed any hold-down period. This
notification is generated when
TIMETRA-SECURITY-MIB.mib::tmnxDCpuProtStaticPlcrLogEvent is configured
to 'enable' or 'verbose'.
[EFFECT] The affected SAP is now in conformance with the parameters
configured for the associated distributed CPU protection policy.
[RECOVERY] There is no recovery required for this notification.
sapDcpLocMonExcd
.1.3.6.1.4.1.6527.3.1.3.4.3.0.47
[CAUSE] The sapDcpLocMonExcd notification is generated when the
local-monitoring-policer for a particular SAP has transitioned from a
conformant state to a non-conformant state and the system will attempt
to allocate dynamic enforcement policers. This notification is
generated when
TIMETRA-SECURITY-MIB.mib::tmnxDCpuProtLocMonPlcrLogEvent is configured
to 'verbose'.
[EFFECT] The affected SAP may be using more resources than expected
and cause the system to underperform. This notification may indicate a
Denial of Service attack or a misconfiguration in the network.
[RECOVERY] Appropriate configuration changes to the distributed CPU
protection policy or to the affected SAP may be required.
sapDcpLocMonExcdDynResource
.1.3.6.1.4.1.6527.3.1.3.4.3.0.48
[CAUSE] The sapDcpLocMonExcdDynResource notification is generated when
the local-monitoring-policer for a particular SAP has transitioned
from a conformant state to a non-conformant state and the system
cannot allocate all the dynamic enforcements policers associated with
the distributed CPU protection policy . This notification is generated
when TIMETRA-SECURITY-MIB.mib::tmnxDCpuProtLocMonPlcrLogEvent is
configured to 'enable' or 'verbose'.
[EFFECT] The affected SAP may be using more resources than expected
and cause the system to underperform. This notification may indicate a
Denial of Service attack or a misconfiguration in the network.
[RECOVERY] Appropriate configuration changes to the distributed CPU
protection policy or to the affected SAP or to the dynamic enforcement
policer pool(TIMETRA-CHASSIS-MIB.mib::tmnxFPDCpuProtDynEnfrcPlcrPool).
sapDcpLocMonExcdAllDynAlloc
.1.3.6.1.4.1.6527.3.1.3.4.3.0.49
[CAUSE] The sapDcpLocMonExcdAllDynAlloc notification is generated when
all dynamic enforcement policers associated with a non-conformant
local-monitoring-policer have been successfully allocated for a
particular SAP. This notification is generated when
TIMETRA-SECURITY-MIB.mib::tmnxDCpuProtLocMonPlcrLogEvent is configure
to 'verbose'.
[EFFECT] The affected SAP may be using more resources than expected
and cause the system to underperform.
[RECOVERY] Appropriate configuration changes to the distributed CPU
protection policy or to the affected SAP may be required.
sapTlsMacAddrLimitAlarmCleared
.1.3.6.1.4.1.6527.3.1.3.4.3.0.5
The trap sapTlsMacAddrLimitAlarmCleared is sent whenever the number of
MAC addresses stored in the FDB for this SAP drops to the watermark
specified by the object svcTlsFdbTableFullLowWatermark.
sapDcpLocMonExcdAllDynFreed
.1.3.6.1.4.1.6527.3.1.3.4.3.0.50
[CAUSE] The sapDcpLocMonExcdAllDynFreed notification is generated for
a particular SAP when all the previously allocated dynamic enforcement
policers for a particular local-monitoring-policer on the associated
distributed CPU protection policy have been freed up and all the
protocols are once again being monitored by local-monitor. This
notification is generated when
TIMETRA-SECURITY-MIB.mib::tmnxDCpuProtLocMonPlcrLogEvent is configured
to 'verbose'.
[EFFECT] The affected SAP may be using more resources than expected
and cause the system to underperform.
[RECOVERY] There is no recovery required for this notification.
sapDcpDynamicEnforceAlloc
.1.3.6.1.4.1.6527.3.1.3.4.3.0.51
[CAUSE] The sapDcpDynamicEnforceAlloc notification is generated when a
dynamic enforcement policer is allocated on a particular SAP. This
notification is generated when
TIMETRA-SECURITY-MIB.mib::tmnxDCpuProtProtocolDynLogEvent is
configured to 'verbose'.
[EFFECT] The affected SAP is not in conformance with the configured
parameters of the associated distributed CPU protection policy and may
be using more resources than expected and cause the system to
underperform.
[RECOVERY] Appropriate configuration changes to the distributed CPU
protection policy or to the affected SAP may be required.
sapDcpDynamicEnforceFreed
.1.3.6.1.4.1.6527.3.1.3.4.3.0.52
[CAUSE] The sapDcpDynamicEnforceFreed notification is generated when a
dynamic enforcement policer is freed on a particular SAP. This
notification is generated when
TIMETRA-SECURITY-MIB.mib::tmnxDCpuProtProtocolDynLogEvent is
configured to 'verbose'.
[EFFECT] The affected SAP is now in conformance with the configured
parameters of the associated distributed CPU protection policy.
[RECOVERY] There is no recovery required for this notification.
sapTlsMacMoveExceedNonBlock
.1.3.6.1.4.1.6527.3.1.3.4.3.0.53
[CAUSE] The sapTlsMacMoveExceedNonBlock notification is generated when
the SAP exceeds the TLS svcTlsMacMoveMaxRate when sapTlsLimitMacMove
is set to 'nonBlocking'. In case of Provider Backbone Bridging (PBB),
if the MAC address that exceeds the rate is ISID-VPLS(iVpls) FDB and
sap binding that detects the move is in Backbone-VPLS(bVpls), the
notification will be generated with svcId, custId of I-VPLS and B-VPLS
sapId.
[EFFECT] This notification is informational only.
[RECOVERY] User can adjust the value of svcTlsMacMoveMaxRate to reduce
the frequency of this notification.
sapEthLoopbackStarted
.1.3.6.1.4.1.6527.3.1.3.4.3.0.54
[CAUSE] The sapEthLoopbackStarted notification is generated when the
SAP is placed into loopback.
[EFFECT] This notification is informational only.
sapEthLoopbackStopped
.1.3.6.1.4.1.6527.3.1.3.4.3.0.55
[CAUSE] The sapEthLoopbackStopped notification is generated when the
SAP is removed from loopback.
[EFFECT] This notification is informational only.
sapTunnelEncapIpMtuTooSmall
.1.3.6.1.4.1.6527.3.1.3.4.3.0.56
[CAUSE] The sapTunnelEncapIpMtuTooSmall notification is generated when
the addition of tunnel encapsulation to a packet at or near the IP
Tunnel's configured IP MTU may cause it to exceed the tunnel's
configured encapsulated IP MTU.
[EFFECT] The pre-encapsulated packet may be fragmented, and will
require reassembly by the tunnel remote endpoint, causing a
performance impact.
[RECOVERY] Configured IP MTU and/or encapsulated IP MTU may need to be
changed depending on the size of the encapsulation overhead as
indicated in 'sapTunnelNotifyEncapOverhead', and the transmission
capabilities of the tunnel's transport network.
sapHostRipListenerSetupFailed
.1.3.6.1.4.1.6527.3.1.3.4.3.0.57
The sapHostRipListenerSetupFailed notification is generated when the
system was unable to set up a RIP listener for the given host.
[CAUSE]
[EFFECT]
[RECOVERY] No recovery is required on this system.
sapStatHost6DynMacConflict
.1.3.6.1.4.1.6527.3.1.3.4.3.0.58
The sapStatHost6DynMacConflict notification is generated when the
system was unable to update the MAC address of a static IPv6 host.
[CAUSE] The system failed to update the MAC address of a static IPv6
host.
[EFFECT] The static IPv6 host has a MAC address that is not up to
date.
[RECOVERY] The recovery action depends on the exact reason why the
MAC update failed. This is clarified in the sapNotifyReason object.
tmnxIpTunnelOperStateChange
.1.3.6.1.4.1.6527.3.1.3.4.3.0.59
[CAUSE] The tmnxIpTunnelOperStateChange notification is generated when
there is a change in tmnxIpTunnelOperState for an IP tunnel.
[EFFECT] When the tunnel is operationally down, traffic arriving at
the tunnel endpoints will not be encapsulated and transported.
sapTlsDHCPLseStEntriesExceeded
.1.3.6.1.4.1.6527.3.1.3.4.3.0.6
The sapTlsDHCPLseStEntriesExceeded notification is
generated when the number of DHCP lease states
entries on a given SAP reaches a user configurable
upper limit given by sapTlsDhcpLeasePopulate.
svcEvpnMplsMacMoveExceedNonBlock
.1.3.6.1.4.1.6527.3.1.3.4.3.0.60
[CAUSE] The svcEvpnMplsMacMoveExceedNonBlock notification is generated
when the EVPN MPLS destination exceeds the TLS svcTlsMacMoveMaxRate
when sapTlsLimitMacMove is set to 'nonBlocking'.
[EFFECT] This notification is informational only.
[RECOVERY] User can adjust the value of svcTlsMacMoveMaxRate to reduce
the frequency of this notification.
sapIfIgnorePortStateStart
.1.3.6.1.4.1.6527.3.1.3.4.3.0.61
[CAUSE] The sapIfIgnorePortStateStart notification is generated when
system starts to ignore non-operational state of the port associated
with the IP interface.
[EFFECT] This notification is informational only.
[RECOVERY] Set sapL3LoopbackRowStatus to 'destroy' to stop this.
sapIfIgnorePortStateStop
.1.3.6.1.4.1.6527.3.1.3.4.3.0.62
[CAUSE] The sapIfIgnorePortStateStop notification is generated when
system stops to ignore non-operational state of the port associated
with the IP interface.
[EFFECT] This notification is informational only.
[RECOVERY] None required.
sapReceivedPbbProtSrcMac
.1.3.6.1.4.1.6527.3.1.3.4.3.0.63
[CAUSE] The sapReceivedPbbProtSrcMac notification is generated when a
protected source MAC protected in i-vpls is received on SAP in b-vpls
(svcTlsBackboneVplsSvcId) service.
[EFFECT] The frame is discarded.
[RECOVERY] None needed.
sapTlsDHCPLeaseStateOverride
.1.3.6.1.4.1.6527.3.1.3.4.3.0.7
The sapTlsDHCPLeaseStateOverride notification is generated when an
existing DHCP lease state is overridden by a new lease state which has
the same IP address but a different MAC address.
sapTlsDHCPSuspiciousPcktRcvd
.1.3.6.1.4.1.6527.3.1.3.4.3.0.8
The sapTlsDHCPSuspiciousPcktRcvd notification is generated when a DHCP
packet is received with suspicious content.
sapDHCPLeaseEntriesExceeded
.1.3.6.1.4.1.6527.3.1.3.4.3.0.9
The sapDHCPLeaseEntriesExceeded notification is generated when the
number of DHCP lease state entries on a given SAP reaches a user
configurable upper limit. This limit is given by
sapTlsDhcpLeasePopulate for a TLS service and by
TIMETRA-VRTR-MIB::vRtrIfDHCPLeasePopulate for an IES or VPRN service.
topologyChangeSapMajorState
.1.3.6.1.4.1.6527.3.1.3.4.5.0.1
The topologyChangeSapMajorState notification is
generated when a SAP has transitioned its state from
learning to forwarding or from forwarding to blocking
or broken. The spanning tree topology has been modified
and it may denote loss of customer access or
redundancy. Check the new topology against the
provisioned topology to determine the severity of
connectivity loss.
bridgedTLS
.1.3.6.1.4.1.6527.3.1.3.4.5.0.10
The bridgedTLS notification is generated when a
configuration BPDU has been received that identifies
that another TLS with a different VPNID is attempting
to bridge with this TLS. At least one ESR
participating within one of the TLS that is locally
connected must have an active VCP for this to be seen.
The SAP that the configuration BPDU is received on
will be blocked to prevent the TLS to TLS bridging.
Reconfigure the bridged TLS into a single TLS or
remove the connectivity.
sapEncapPVST
.1.3.6.1.4.1.6527.3.1.3.4.5.0.11
The sapEncapPVST notification is generated when the
SAP receives a BPDU that is PVST encapsulated, after
having received BPDUs that were 802.d encapsulated.
The SAP BPDUs will also be PVST encapsulated. No
recovery is needed.
sapEncapDot1d
.1.3.6.1.4.1.6527.3.1.3.4.5.0.12
The sapEncapDot1d notification is generated when the
SAP receives a BPDU that is 802.1d encapsulated after
having received BPDUs that were PVST encapsulated. The
SAP BPDUs will also be 802.1d encapsulated. No
recovery is needed.
sapReceiveOwnBpdu
.1.3.6.1.4.1.6527.3.1.3.4.5.0.13
The sapReceiveOwnBpdu notification is generated when the SAP STP
received it's own BPDU.
newRootSap
.1.3.6.1.4.1.6527.3.1.3.4.5.0.2
The newRootSap notification is generated when the
previous root bridge has been aged out and a new root
bridge has been elected. A new root bridge creates a
new spanning tree topology and it may denote loss of
customer access or redundancy. Check the new topology
against the provisioned topology to determine the
severity of connectivity loss.
sapActiveProtocolChange
.1.3.6.1.4.1.6527.3.1.3.4.5.0.30
The sapActiveProtocolChange notification is generated
when the spanning tree protocol on this SAP changes
from rstp to stp or vice versa. No recovery is
needed.
tmnxStpRootGuardViolation
.1.3.6.1.4.1.6527.3.1.3.4.5.0.35
The tmnxStpRootGuardViolation notification is generated when a SAP
which has root-guard configured is trying to become root (has a better
STP priority vector). The SAP will become alternate and traffic will
be blocked.
tmnxSapStpExcepCondStateChng
.1.3.6.1.4.1.6527.3.1.3.4.5.0.37
The tmnxSapStpExcepCondStateChng notification is generated when the
value of the object sapTlsStpException has changed, i.e. when the
exception condition changes on the indicated SAP.
topologyChangeSapState
.1.3.6.1.4.1.6527.3.1.3.4.5.0.5
The topologyChangeSapState notification is generated
when a SAP has transitioned state to blocking or
broken from a state other than forwarding. This event
complements what is not covered by
topologyChangeSapMajorState. The spanning tree
topology has been modified and it may denote loss of
customer access or redundancy. Check the new topology
against the provisioned topology to determine severity
of connectivity loss.
receivedTCN
.1.3.6.1.4.1.6527.3.1.3.4.5.0.6
The receivedTCN notification is generated when a SAP
has received TCN from another bridge. This bridge will
either have its configured BPDU with the topology
change flag set if it is a root bridge, or it will
pass TCN to its root bridge. Eventually the address
aging timer for the forwarding database will be made
shorter for a short period of time. No recovery is
needed.
higherPriorityBridge
.1.3.6.1.4.1.6527.3.1.3.4.5.0.9
The higherPriorityBridge notification is generated when
a customer's device has been configured with a bridge
priority equal to zero. The SAP that the customer's
device is connected through will be blocked. Remove
the customer's device or reconfigure the customer's
bridge priority with a value greater than zero.
TmnxSapAtmEncapsulation
timetraSvcSapMIBModule 
sapNumEntries 
sapEgrQosSchedStatsTable 
sapEgrQosSchedStatsEntry 
sapEgrQosSchedName 
sapCreated