This document is the SNMP MIB module to manage and provision
the Nokia SROS device transport and virtual routers,
their interfaces, and other related features.
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.
The tmnxVRtrMidRouteTCA notification is generated when the number
of routes contained in a VPRN exceeds the value specified by
vRtrMidRouteThreshold. No other notifications of this type
are generated until after the soak period specified by
vRtrRouteThresholdSoakTime has expired.
tmnxVRtrDHCPAFEntriesExceeded
.1.3.6.1.4.1.6527.3.1.3.3.0.10
The tmnxVRtrDHCPAFEntriesExceeded notification is generated when the
number of DHCP 'AutoFilter' entries on a given interface reaches a
user configurable upper limit given by vRtrIfDHCPAutoFilter.
tmnxVRtrMaxRoutes
.1.3.6.1.4.1.6527.3.1.3.3.0.11
The tmnxVRtrMaxRoutes notification is generated when the number of
routes of type vRtrMaxRoutesType contained in a VPRN reaches the value
specified by vRtrMaxNumRoutes.
tmnxVRtrDHCPLseStsExceeded
.1.3.6.1.4.1.6527.3.1.3.3.0.12
The tmnxVRtrDHCPLseStsExceeded notification is
generated when the number of DHCP lease states
entries on a given interface reaches a user configurable
upper limit.
tmnxVRtrDHCPLeaseStateOverride
.1.3.6.1.4.1.6527.3.1.3.3.0.13
The tmnxVRtrDHCPLeaseStateOverride 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.
tmnxVRtrDHCPSuspiciousPcktRcvd
.1.3.6.1.4.1.6527.3.1.3.3.0.14
The tmnxVRtrDHCPSuspiciousPcktRcvd notification is generated when a
DHCP packet is received with suspicious content.
tmnxVRtrDHCPLseStRestoreProblem
.1.3.6.1.4.1.6527.3.1.3.3.0.15
The tmnxVRtrDHCPLseStRestoreProblem notification is generated when an
an error is detected while processing a persistency record.
tmnxVRtrDHCPLseStatePopulateErr
.1.3.6.1.4.1.6527.3.1.3.3.0.16
The tmnxVRtrDHCPLseStatePopulateErr notification indicates that the
system was unable to update the Lease State Table with the information
contained in the DHCP ACK message. The DHCP ACK message has been
discarded.
tmnxVRtrBfdSessionDown
.1.3.6.1.4.1.6527.3.1.3.3.0.17
The tmnxVRtrBfdSessionDown notification is generated when a BFD
session goes down.
tmnxVRtrBfdMaxSessionOnSlot
.1.3.6.1.4.1.6527.3.1.3.3.0.18
The tmnxVRtrBfdMaxSessionOnSlot notification is generated when the
maximum number of BFD sessions has been reached on the slot indicated
in 'vRtrBfdSlotNumber'. When we have IOM based sessions,
vRtrSlotOrCpmFlag is set to 'slot' and when the sessions are
centralized it is set to 'cpm'.
tmnxVRtrBfdPortTypeNotSupported
.1.3.6.1.4.1.6527.3.1.3.3.0.19
The tmnxVRtrBfdPortTypeNotSupported notification is generated when BFD
is not supported on the port specified in 'tmnxPortNotifyPortId'.
tmnxVRtrHighRouteTCA
.1.3.6.1.4.1.6527.3.1.3.3.0.2
The tmnxVRtrHighRouteTCA notification is generated when the number
of routes contained in a VPRN exceeds the value specified by
vRtrHighRouteThreshold. No other notifications of this type
are generated until after the soak period specified by
vRtrRouteThresholdSoakTime has expired.
tmnxVRtrDHCPIfLseStatesExceeded
.1.3.6.1.4.1.6527.3.1.3.3.0.20
The tmnxVRtrDHCPIfLseStatesExceeded notification is generated when the
number of lease states on an interface exceeds
vRtrIfDHCPLeasePopulate.
tmnxVRtrDHCP6RelayLseStExceeded
.1.3.6.1.4.1.6527.3.1.3.3.0.21
The tmnxVRtrDHCP6RelayLseStExceeded notification is generated when the
number of lease states populated by dhcp6 relay on an interface
exceeds vRtrIfDHCP6LeasePopulate.
tmnxVRtrDHCP6ServerLseStExceeded
.1.3.6.1.4.1.6527.3.1.3.3.0.22
The tmnxVRtrDHCP6ServerLseStExceeded notification is generated when
the number of lease states populated by dhcp6 server on an interface
exceeds vRtrIfDHCP6ServerMaxLeaseStates.
tmnxVRtrDHCP6LseStateOverride
.1.3.6.1.4.1.6527.3.1.3.3.0.23
The tmnxVRtrDHCP6LseStateOverride notification is generated when an
existing DHCP6 lease state can be overridden by a new lease state.
This is allowed if the new lease state has the same IP address but a
different client id or mac address. This is not allowed if the new
lease state has the same IP address but a different prefix length.
tmnxVRtrDHCP6RelayReplyStripUni
.1.3.6.1.4.1.6527.3.1.3.3.0.24
The tmnxVRtrDHCP6RelayReplyStripUni notification is generated when a
unicast option is stripped from a message relayed from a server to a
client in a relay reply message.
tmnxVRtrDHCP6IllegalClientAddr
.1.3.6.1.4.1.6527.3.1.3.3.0.25
The tmnxVRtrDHCP6IllegalClientAddr notification is generated when an
incoming message is dropped because the client's source IP does not
match the subnet of the incoming interface.
tmnxVRtrDHCP6AssignedIllegSubnet
.1.3.6.1.4.1.6527.3.1.3.3.0.26
The tmnxVRtrDHCP6AssignedIllegSubnet notification is generated when an
IP address assigned to the client does not match the subnet of the
interface.
tmnxVRtrDHCP6ClientMacUnresolved
.1.3.6.1.4.1.6527.3.1.3.3.0.27
The tmnxVRtrDHCP6ClientMacUnresolved notification is generated when we
receive a relay reply for a client, and the client's MAC address has
not been resolved yet.
tmnxVRtrBfdSessionUp
.1.3.6.1.4.1.6527.3.1.3.3.0.28
The tmnxVRtrBfdSessionUp notification is generated when a BFD session
goes up.
tmnxVRtrIPv6MidRouteTCA
.1.3.6.1.4.1.6527.3.1.3.3.0.29
The tmnxVRtrIPv6MidRouteTCA notification is generated when the number
of IPv6 routes contained in a VPRN exceeds the value specified by
vRtrIPv6MidRouteThreshold. No other notifications of this type are
generated until after the soak period specified by
vRtrIPv6RouteThresholdSoakTime has expired.
tmnxVRtrHighRouteCleared
.1.3.6.1.4.1.6527.3.1.3.3.0.3
The tmnxVRtrHighRouteCleared notification is generated when the number
of routes contained in a VPRN has dropped below the
vRtrHighRouteThreshold value following the generation of a
tmnxVRtrHighRouteTCA notification.
tmnxVRtrIPv6HighRouteTCA
.1.3.6.1.4.1.6527.3.1.3.3.0.30
The tmnxVRtrIPv6HighRouteTCA notification is generated when the number
of IPv6 routes contained in a VPRN exceeds the value specified by
vRtrIPv6HighRouteThreshold. No other notifications of this type are
generated until after the soak period specified by
vRtrIPv6RouteThresholdSoakTime has expired.
tmnxVRtrIPv6HighRouteCleared
.1.3.6.1.4.1.6527.3.1.3.3.0.31
The tmnxVRtrIPv6HighRouteCleared notification is generated when the
number of IPv6 routes contained in a VPRN has dropped below the
vRtrIPv6HighRouteThreshold value following the generation of a
tmnxVRtrIPv6HighRouteTCA notification.
tmnxVRtrStaticRouteCPEStatus
.1.3.6.1.4.1.6527.3.1.3.3.0.32
The tmnxVRtrStaticRouteCPEStatus notification is generated when a CPE
associated with a static route, as specified by the
vRtrInetStatRteCpeNotifyAddr object, becomes reachable or unreachable.
tmnxVRtrBfdSessionDeleted
.1.3.6.1.4.1.6527.3.1.3.3.0.33
The tmnxVRtrBfdSessionDeleted notification is generated when a BFD
session is deleted.
tmnxVRtrBfdSessionProtChange
.1.3.6.1.4.1.6527.3.1.3.3.0.34
The tmnxVRtrBfdSessionProtChange notification is generated when there
is a change in the list of protocols using the BFD session.
tmnxVRtrManagedRouteAddFailed
.1.3.6.1.4.1.6527.3.1.3.3.0.35
The tmnxVRtrManagedRouteAddFailed notification is generated when a
managed route could not be installed.
tmnxVRtrFibOccupancyThreshold
.1.3.6.1.4.1.6527.3.1.3.3.0.36
The tmnxVRtrFibOccupancyThreshold notification is generated when the
FIB on an IOM card transitions between experiencing persistent normal
and high occupancy.
tmnxVRtrInetAddressAttachFailed
.1.3.6.1.4.1.6527.3.1.3.3.0.37
The tmnxVRtrInetAddressAttachFailed notification is generated when an
IP address could not be attached to an interface.
The reason is indicated in the failure description.
A possible cause is that a duplicate address is detected.
If the IP address is a link-local address, the
vRtrIfLinkLocalAddressState of the corresponding entry in the
vRtrIfTable does not reach the state 'preferred'.
If the IP address was configured by the user, the vRiaInetAddrState of
the corresponding entry in the vRtrIpAddrTable does not reach the
state 'preferred'.
The IP address can also be a subnet router anycast address related to
an IP address configured by the user (refer to RFC 4291 IPv6
Addressing Architecture, section 2.6.1 Anycast Addresses).
tmnxVRtrSingleSfmOverloadStateCh
.1.3.6.1.4.1.6527.3.1.3.3.0.38
The notification tmnxVRtrSingleSfmOverloadStateCh is sent when IGP
single-SFM-overload state of a virtual router instance changes.
tmnxVRtrGrtExportLimitReached
.1.3.6.1.4.1.6527.3.1.3.3.0.39
A tmnxVRtrGrtExportLimitReached notification is generated when the
configured value of exported routes, vRtrGrtMaxExportRoutes, is
reached. Additional routes would not be exported into the GRT from the
route table.
tmnxVRtrIllegalLabelTCA
.1.3.6.1.4.1.6527.3.1.3.3.0.4
The tmnxVRtrIllegalLabelTCA notification is generated when the number
of illegal label violations on a VRF has exceeded the value specified
by vRtrIllegalLabelThreshold.
This notification is made obsolete in release 14.0.
tmnxVRtrGrtRoutesExpLimitDropped
.1.3.6.1.4.1.6527.3.1.3.3.0.40
A tmnxVRtrGrtRoutesExpLimitDropped notification is generated when the
number of exported routes drops below the export limit,
vRtrGrtMaxExportRoutes.
tmnxVRtrIfLdpSyncTimerStart
.1.3.6.1.4.1.6527.3.1.3.3.0.41
A tmnxVRtrIfLdpSyncTimerStart notification is generated when the LDP
sync timer, vRtrIfLdpSyncTimer starts for this interface.
tmnxVRtrIfLdpSyncTimerStop
.1.3.6.1.4.1.6527.3.1.3.3.0.42
A tmnxVRtrIfLdpSyncTimerStart notification is generated when the LDP
sync timer, vRtrIfLdpSyncTimer stops for this interface.
tmnxVRtrBfdNoCpmNpResources
.1.3.6.1.4.1.6527.3.1.3.3.0.43
The tmnxVRtrBfdNoCpmNpResources notification is generated when a BFD
session could not be established because the session requires a cpmNp
session termination resource (see vRtrIfBfdExtType), and no cpmNp
session termination resources are available.
tmnxVRtrGrtV6ExportLimitReached
.1.3.6.1.4.1.6527.3.1.3.3.0.44
[CAUSE] A tmnxVRtrGrtV6ExportLimitReached notification is generated
when the configured value of exported routes,
vRtrGrtMaxIpv6ExportRoutes, is reached.
[EFFECT] Additional routes would not be exported into the GRT from the
route table.
[RECOVERY] The export policy and the value of
vRtrGrtMaxIpv6ExportRoutes need to be changed.
tmnxVRtrGrtV6RoutesExpLimDropped
.1.3.6.1.4.1.6527.3.1.3.3.0.45
[CAUSE] A tmnxVRtrGrtV6RoutesExpLimDropped notification is generated
when the number of exported routes drops below the export limit,
vRtrGrtMaxIpv6ExportRoutes.
[EFFECT] There is no effect of this notification.
[RECOVERY] There is no recovery required for this notification.
tmnxVRtrStaticRouteStatusChanged
.1.3.6.1.4.1.6527.3.1.3.3.0.46
[CAUSE] A tmnxVRtrStaticRouteStatusChanged notification is generated
when the status of a static route, vRtrInetStaticRouteStatus changes
from active to inactive or from inactive to active.
[EFFECT] There is no effect of this notification.
[RECOVERY] There is no recovery required for this notification.
vRtrIfDcpStaticExcd
.1.3.6.1.4.1.6527.3.1.3.3.0.47
[CAUSE] The vRtrIfDcpStaticExcd notification is generated when the
static-policer on a particular network-interface 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 network-interface may be using more resources
than expected and cause the system to under perform. 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 network-interface may be
required.
vRtrIfDcpDynamicExcd
.1.3.6.1.4.1.6527.3.1.3.3.0.48
[CAUSE] The vRtrIfDcpDynamicExcd notification is generated when the
protocol on a particular network-interface 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 network-interface may be using more resources
than expected and cause the system to under perform. 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 network-interface may be
required.
vRtrIfDcpStaticHoldDownStart
.1.3.6.1.4.1.6527.3.1.3.3.0.49
[CAUSE] The vRtrIfDcpStaticHoldDownStart notification is generated
when a particular network-interface 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.
tmnxVRtrMcastMidRouteTCA
.1.3.6.1.4.1.6527.3.1.3.3.0.5
The tmnxVRtrMcastMidRouteTCA notification is generated when the number
of multicast routes contained in a VPRN exceeds the value specified by
vRtrMcastMidRouteThreshold. No other notifications of this type
are generated until after the soak period specified by
vRtrRouteThresholdSoakTime has expired.
vRtrIfDcpDynamicHoldDownStart
.1.3.6.1.4.1.6527.3.1.3.3.0.50
[CAUSE] The vRtrIfDcpDynamicHoldDownStart notification is generated
when a particular network-interface 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.
vRtrIfDcpStaticHoldDownEnd
.1.3.6.1.4.1.6527.3.1.3.3.0.51
[CAUSE] The vRtrIfDcpStaticHoldDownEnd notification is generated when
a particular network-interface 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 network-interface will
transition to a detection-time countdown after the hold-down period is
complete.
[RECOVERY] There is no recovery required for this notification.
vRtrIfDcpDynamicHoldDownEnd
.1.3.6.1.4.1.6527.3.1.3.3.0.52
[CAUSE] The vRtrIfDcpDynamicHoldDownEnd notification is generated
when a particular network-interface 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 network-interface will
transition to a detection-time countdown after the hold-down period is
complete.
[RECOVERY] There is no recovery required for this notification.
vRtrIfDcpStaticConform
.1.3.6.1.4.1.6527.3.1.3.3.0.53
[CAUSE] The vRtrIfDcpStaticConform notification is generated when the
static-policer for a particular network-interface 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 network-interface is now in conformance with the
parameters configured for the associated distributed CPU protection
policy.
[RECOVERY] There is no recovery required for this notification.
vRtrIfDcpDynamicConform
.1.3.6.1.4.1.6527.3.1.3.3.0.54
[CAUSE] The vRtrIfDcpDynamicConform notification is generated when the
protocol for a particular network-interface 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 network-interface is now in conformance with the
parameters configured for the associated distributed CPU protection
policy.
[RECOVERY] There is no recovery required for this notification.
vRtrIfDcpLocMonExcd
.1.3.6.1.4.1.6527.3.1.3.3.0.55
[CAUSE] The vRtrIfDcpLocMonExcd notification is generated when the
local-monitoring-policer for a particular network-interface 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 network-interface may be using more resources
than expected and cause the system to under perform. 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 network-interface may be
required.
vRtrIfDcpLocMonExcdDynResource
.1.3.6.1.4.1.6527.3.1.3.3.0.56
[CAUSE] The vRtrIfDcpLocMonExcdDynResource notification is generated
when the local-monitoring-policer for a particular network-interface
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 network-interface may be using more resources
than expected and cause the system to under perform. 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 network-interface or to the
dynamic enforcement policer pool
(TIMETRA-CHASSIS-MIB.mib::tmnxFPDCpuProtDynEnfrcPlcrPool).
vRtrIfDcpLocMonExcdAllDynAlloc
.1.3.6.1.4.1.6527.3.1.3.3.0.57
[CAUSE] The vRtrIfDcpLocMonExcdAllDynAlloc notification is generated
when all dynamic enforcement policers associated with a non-conformant
local-monitoring-policer have been successfully allocated for a
particular network-interface. This notification is generated when
TIMETRA-SECURITY-MIB.mib::tmnxDCpuProtLocMonPlcrLogEvent is configure
to 'verbose'.
[EFFECT] The affected network-interface may be using more resources
than expected and cause the system to under perform.
[RECOVERY] Appropriate configuration changes to the distributed CPU
protection policy or to the affected network-interface may be
required.
vRtrIfDcpLocMonExcdAllDynFreed
.1.3.6.1.4.1.6527.3.1.3.3.0.58
[CAUSE] The vRtrIfDcpLocMonExcdAllDynFreed notification is generated
for a particular network-interface 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 network-interface may be using more resources
than expected and cause the system to under perform.
[RECOVERY] There is no recovery required for this notification.
vRtrIfDcpDynamicEnforceAlloc
.1.3.6.1.4.1.6527.3.1.3.3.0.59
[CAUSE] The vRtrIfDcpDynamicEnforceAlloc notification is generated
when a dynamic enforcement policer is allocated on a particular
network-interface. This notification is generated when
TIMETRA-SECURITY-MIB.mib::tmnxDCpuProtProtocolDynLogEvent is
configured to 'verbose'.
[EFFECT] The affected network-interface 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 under perform.
[RECOVERY] Appropriate configuration changes to the distributed CPU
protection policy or to the affected network-interface may be
required.
tmnxVRtrMcastMaxRoutesTCA
.1.3.6.1.4.1.6527.3.1.3.3.0.6
The tmnxVRtrMcastMaxRoutesTCA notification is generated when the number
of multicast routes contained in a VPRN exceeds the value specified by
vRtrMaxMcastNumRoutes. No other notifications of this type
are generated until after the soak period specified by
vRtrRouteThresholdSoakTime has expired.
vRtrIfDcpDynamicEnforceFreed
.1.3.6.1.4.1.6527.3.1.3.3.0.60
[CAUSE] The vRtrIfDcpDynamicEnforceFreed notification is generated
when a dynamic enforcement policer is freed on a particular
network-interface. This notification is generated when
TIMETRA-SECURITY-MIB.mib::tmnxDCpuProtProtocolDynLogEvent is
configured to 'verbose'.
[EFFECT] The affected network-interface is now in conformance with the
configured parameters of the associated distributed CPU protection
policy.
[RECOVERY] There is no recovery required for this notification.
tmnxVRtrBfdSessExtDown
.1.3.6.1.4.1.6527.3.1.3.3.0.61
[CAUSE] The tmnxVRtrBfdSessExtDown notification is generated when a
BFD session goes down.
[EFFECT] The effect of this session going down is that it either takes
down any protocol that is riding over top of it or it notifies
them that the session has gone down.
[RECOVERY] The session will automatically attempt to re-establish on
its own.
tmnxVRtrBfdSessExtUp
.1.3.6.1.4.1.6527.3.1.3.3.0.62
[CAUSE] The tmnxVRtrBfdSessExtUp notification is generated when a BFD
session goes up.
[EFFECT] There is no effect of this notification.
[RECOVERY] There is no recovery required for this notification.
tmnxVRtrBfdSessExtDeleted
.1.3.6.1.4.1.6527.3.1.3.3.0.63
[CAUSE] The tmnxVRtrBfdSessExtDeleted notification is generated when a
BFD session is deleted.
[EFFECT] There is no effect of this notification.
[RECOVERY] There is no recovery required for this notification.
tmnxVRtrBfdSessExtProtChange
.1.3.6.1.4.1.6527.3.1.3.3.0.64
[CAUSE] The tmnxVRtrBfdSessExtProtChange notification is generated
when there is a change in the list of protocols using the BFD session.
[EFFECT] There is no effect of this notification.
[RECOVERY] There is no recovery required for this notification.
tmnxVRtrBfdExtNoCpmNpResources
.1.3.6.1.4.1.6527.3.1.3.3.0.65
[CAUSE] The tmnxVRtrBfdExtNoCpmNpResources notification is generated
when a BFD session could not be established because the session
requires a cpmNp session termination resource (see vRtrIfBfdExtType),
and no cpmNp session termination resources are available.
[EFFECT] There is no effect of this notification.
[RECOVERY] There is no recovery required for this notification.
tmnxVRtrDnsFault
.1.3.6.1.4.1.6527.3.1.3.3.0.66
[CAUSE] The tmnxVRtrDnsFault notification is generated when this
system detects a fault with a DNS server, or when it detects that the
fault has disappeared.
The virtual router instance and DNS server address are indicated with
vRtrID, vRtrNotifInetAddrType, and vRtrNotifInetAddr.
More details of the fault may be indicated with
vRtrFailureDescription.
[EFFECT] If another DNS server is available in the same virtual router
instance, that DNS server may be used instead.
Otherwise, any application in this virtual router instance that relies
on DNS may be affected.
[RECOVERY] A modification of the conceptual row in the vRtrDnsTable
with the same value for vRtrID, may repair the problem.
tmnxVRtrMacAcctLimitReached
.1.3.6.1.4.1.6527.3.1.3.3.0.67
[CAUSE] The tmnxVRtrMacAcctLimitReached notification is generated when
the system detects that the MAC accounting table is full.
[EFFECT] The MAC accounting table is full and further allocations of
accounting indices will fail.
[RECOVERY] The failure can be cleared when the used MAC entries are
deleted by disabling MAC accounting on a particular interface
or through manual intervention with a user command such as clear
router interface mac.
tmnxVRtrMacAcctLimitCleared
.1.3.6.1.4.1.6527.3.1.3.3.0.68
[CAUSE] The tmnxVRtrMacAcctLimitCleared notification is generated when
one or more MAC entries are deleted following the generation of a
tmnxVRtrMacAcctLimitReached notification.
[EFFECT] Allocation of further MAC entries will be successful up to
the number of entries cleared.
[RECOVERY] No recovery is needed for this notification.
tmnxVRtrNgBfdSessDown
.1.3.6.1.4.1.6527.3.1.3.3.0.69
[CAUSE] The tmnxVRtrNgBfdSessDown notification is generated when a BFD
session goes down.
[EFFECT] The effect of this session going down is that it either takes
down any protocol that is riding over top of it or it notifies them
that the session has gone down.
[RECOVERY] The session will automatically attempt to re-establish on
it's own.
tmnxVRtrMcastMaxRoutesCleared
.1.3.6.1.4.1.6527.3.1.3.3.0.7
The tmnxVRtrMcastMaxRoutesCleared notification is generated when the
number of multicast routes contained in a VPRN has dropped below the
vRtrMaxMcastNumRoutes value following the generation of a
tmnxVRtrMcastMaxRoutesTCA notification.
tmnxVRtrNgBfdSessUp
.1.3.6.1.4.1.6527.3.1.3.3.0.70
[CAUSE] The tmnxVRtrNgBfdSessUp notification is generated when a BFD
session goes up.
[EFFECT] The BFD session will be active.
[RECOVERY] There is no recovery required for this notification.
tmnxVRtrNgBfdSessDeleted
.1.3.6.1.4.1.6527.3.1.3.3.0.71
[CAUSE] The tmnxVRtrNgBfdSessDeleted notification is generated when a
BFD session is deleted.
[EFFECT] The deletion of this session will either take down any
protocol that is riding over top of it or notifies them that the
session has been deleted.
[RECOVERY] There is no recovery required for this notification.
tmnxVRtrNgBfdSessProtChange
.1.3.6.1.4.1.6527.3.1.3.3.0.72
[CAUSE] The tmnxVRtrNgBfdSessProtChange notification is generated when
there is a change in the list of protocols using the BFD session.
[EFFECT] The list of protocols using this session are modified.
[RECOVERY] There is no recovery required for this notification.
tmnxVRtrNgBfdNoCpmNpResources
.1.3.6.1.4.1.6527.3.1.3.3.0.73
[CAUSE] The tmnxVRtrNgBfdNoCpmNpResources notification is generated
when a BFD session could not be established because the session
requires a cpmNp session termination resource (see vRtrIfBfdExtType),
and no cpmNp session termination resources are available.
[EFFECT] The BFD session cannot be established until a cpmNp session
termination resource is available
[RECOVERY] There is no recovery required for this notification.
tmnxVRtrNHRvplsARPHighUsage
.1.3.6.1.4.1.6527.3.1.3.3.0.74
[CAUSE] The tmnxVRtrNHRvplsARPHighUsage notification is generated when
Nexthop RVPLS ARP entries reaches 95% of its limit as indicated by the
value of tmnxVRtrMaxNHRvplsARPEntries.
[EFFECT] ARP table reaches high usage limit and further addition of
Nexthop RVPLS ARP may fail.
[RECOVERY] Reduce the number of ARPs.
tmnxVRtrNHRvplsARPExhaust
.1.3.6.1.4.1.6527.3.1.3.3.0.75
[CAUSE] The tmnxVRtrNHRvplsARPExhaust notification is generated when
Nexthop RVPLS ARP entries reaches 100% of its limit as indicated by
the value of tmnxVRtrMaxNHRvplsARPEntries.
[EFFECT] ARP table reaches high usage limit and further addition of
Nexthop RVPLS ARP will fail.
[RECOVERY] Reduce the number of ARPs.
tmnxVRtrNHRvplsARPHighUsageClr
.1.3.6.1.4.1.6527.3.1.3.3.0.76
[CAUSE] The tmnxVRtrNHRvplsARPHighUsageClr notification is generated
when Nexthop RVPLS ARP entries falls below 90% of its limit following
the generation of tmnxVRtrNHRvplsARPHighUsage notification as
indicated by the value of tmnxVRtrMaxNHRvplsARPEntries.
[EFFECT] Addition of further Nexthop RVPLS ARP entries will be
successful.
[RECOVERY] No recovery is needed for this notification.
tmnxVRtrArpLmt
.1.3.6.1.4.1.6527.3.1.3.3.0.77
[CAUSE] A tmnxVRtrArpLmt notification is generated when the number of
IPv4 ARP entries learned on an IP interface has exceeded the
configured maximum.
[EFFECT] The number of entries have exceeded the configured limit as
specified by vRtrIfArpLimit. No new entries are learned until an entry
expires.
[RECOVERY] Increase the arp-limit.
tmnxVRtrArpThresholdExceeded
.1.3.6.1.4.1.6527.3.1.3.3.0.78
[CAUSE] A tmnxVRtrArpThresholdExceeded notification is generated when
the number of IPv4 ARP entries learned on an IP interface has exceeded
vRtrIfArpThreshold percent of the configured maximum as specified by
vRtrIfArpLimit.
[EFFECT] No direct effect but if the interface continues to learn more
entries then the number of entries may exceed the configured limit as
specified by vRtrIfArpLimit. In that case, no new entries are learned
until an entry expires and traffic to these destinations will be
dropped.
[RECOVERY] Increase the arp-limit.
tmnxVRtrIpv6NbrLmt
.1.3.6.1.4.1.6527.3.1.3.3.0.79
[CAUSE] A tmnxVRtrIpv6NbrLmt notification is generated when the
maximum amount of IPv6 neighbor entries learned on an IP interface has
exceeded the configured maximum.
[EFFECT] The number of entries have exceeded the configured limit as
specified by vRtrIfIpv6NbrLimit. No new entries are learned until an
entry expires.
[RECOVERY] Increase the neighbor limit.
tmnxVRtrMaxArpEntriesTCA
.1.3.6.1.4.1.6527.3.1.3.3.0.8
The tmnxVRtrMaxArpEntriesTCA notification is generated when the number
of ARP entries in a VPRN exceeds the maximum supported.
tmnxVRtrIpv6NbrThresholdExceeded
.1.3.6.1.4.1.6527.3.1.3.3.0.80
[CAUSE] A tmnxVRtrIpv6NbrThresholdExceeded notification is generated
when the number of IPv6 neighbor entries learned on an IP interface
has exceeded vRtrIfIpv6NbrThreshold percent of the configured maximum
as specified by vRtrIfIpv6NbrLimit.
[EFFECT] No direct effect but if the interface continues to learn more
entries then the number of entries may exceed the configured limit as
specified by vRtrIfIpv6NbrLimit. In that case, no new entries are
learned until an entry expires and traffic to these destinations will
be dropped.
[RECOVERY] Increase the neighbor limit.
tmnxVRtrIfIgnorePortState
.1.3.6.1.4.1.6527.3.1.3.3.0.81
[CAUSE] The tmnxVRtrIfIgnorePortState notification is generated when
ignoring non-operational state of the port associated with the IP
interface is changing state.
[EFFECT] This notification is informational only.
[RECOVERY] Set TIMETRA-SAP-MIB::sapL3LoopbackRowStatus to 'destroy' to
stop this.
tmnxVRtrPdnAddrMismatch
.1.3.6.1.4.1.6527.3.1.3.3.0.82
[CAUSE] The tmnxVRtrPdnAddrMismatch notification is generated when the
IP address learned by the PDN interface through the cellular network
could not be installed on the PDN router interface.
For IPv4, this occurs when the parent interface has a mismatching
configured IP address or when the learned PDN IP address overlaps
another IP address in the router instance. The notification will only
be generated when the PDN interface is set unnumbered to the system
interface or any other existing loopback interface.
For IPv6 operation, this occurs when the IPv6 address has a
mismatching subnet to the address configured for the PDN router
interface or if the exact same IPv6 address is configured on the PDN
interface as the address received by the network.
[EFFECT] The PDN Interface will be operationally down.
[RECOVERY] Check the configured IP address for the PDN interface or
parent interface, check the other IP addresses in the router instance,
and/or check the state of the cellular network.
tmnxVRtrPdnAddrMismatchCleared
.1.3.6.1.4.1.6527.3.1.3.3.0.83
[CAUSE] The tmnxVRtrPdnAddrMismatchCleared notification is generated
when the conditions that caused the PDN address mismatch no longer
exist.
[EFFECT] The PDN interface will go operationally up.
[RECOVERY] Not applicable.
tmnxVRtrLeakExportLimitReached
.1.3.6.1.4.1.6527.3.1.3.3.0.84
[CAUSE] The tmnxVRtrLeakExportLimitReached notification is generated
when the leak-export-limit has been exceeded.
[EFFECT] Some routes allowed by the leak-export policies
may not have been leaked to the target VPRNs.
[RECOVERY] Not applicable.
tmnxVRtrLeakExportLimitDropped
.1.3.6.1.4.1.6527.3.1.3.3.0.85
[CAUSE] The tmnxVRtrLeakExportLimitDropped notification
is generated when the number of leaked routes drops below
the leak-export-limit .
[EFFECT] Some routes allowed by the leak-export policies
may not have been leaked to the target VPRNs.
[RECOVERY] Not applicable.
tmnxVRtrDhcpClientStatusChanged
.1.3.6.1.4.1.6527.3.1.3.3.0.86
[CAUSE] The tmnxVRtrDhcpClientStatusChanged notification is sent when
the value of the object vRtrIfDhcpClStateStatus changes.
[EFFECT] While the value of the object vRtrIfDhcpClStateDescription is
not equal to 'established', the DHCP client is not operational.
[RECOVERY] The recovery action, if necessary, depends on the actual
state. When the value is 'failed', details about the failure cause are
specified in the vRtrIfDhcpClStateDescription.
tmnxVRtrDhcp6ClientStatusChanged
.1.3.6.1.4.1.6527.3.1.3.3.0.87
[CAUSE] The tmnxVRtrDhcp6ClientStatusChanged notification is sent when
the value of the object vRtrIfDhcp6ClStateStatus changes.
[EFFECT] While the value of the object vRtrIfDhcp6ClStateDescription
is not equal to 'established', the DHCPv6 client is not operational.
[RECOVERY] The recovery action, if necessary, depends on the actual
state. When the value is 'failed', details about the failure cause are
specified in the vRtrIfDhcp6ClStateDescription.
tmnxVRtrNeDiscovered
.1.3.6.1.4.1.6527.3.1.3.3.0.88
[CAUSE] The tmnxVRtrNeDiscovered notification is sent when a new
Network Element is discovered.
[EFFECT] No effect.
[RECOVERY] No recovery is necessary.
tmnxVRtrNeRemoved
.1.3.6.1.4.1.6527.3.1.3.3.0.89
[CAUSE] The tmnxVRtrNeRemoved notification is sent when a Network
Element is removed.
[EFFECT] No effect.
[RECOVERY] No recovery is necessary.
tmnxVRtrMaxArpEntriesCleared
.1.3.6.1.4.1.6527.3.1.3.3.0.9
The tmnxVRtrMaxArpEntriesCleared notification is generated when the
number of ARP entries contained in a VPRN has dropped below the
maximum value following the generation of a tmnxVRtrMaxArpEntriesTCA
notification.
tmnxVRtrNeModified
.1.3.6.1.4.1.6527.3.1.3.3.0.90
[CAUSE] The tmnxVRtrNeModified notification is sent when a Network
Element is modified.
[EFFECT] No effect.
[RECOVERY] No recovery is necessary.
vRtrIfDhcpClRtStatusChanged
.1.3.6.1.4.1.6527.3.1.3.3.0.91
[CAUSE] The vRtrIfDhcpClRtStatusChanged notification is sent when the
value of the object vRtrIfDhcpClRtStatus changes; that includes when a
row in the vRtrIfDhcpClRtTable is created or destroyed.
[EFFECT] A value of 'installed' indicates the received route is valid,
and is successfully installed in the route table.
[RECOVERY] The recovery action, if necessary, depends on the actual
state.
vRtrIfDhcpClStateDnsChanged
.1.3.6.1.4.1.6527.3.1.3.3.0.92
[CAUSE] The vRtrIfDhcpClStateDnsChanged notification is sent when the
value of any of the DNS addresses of the DHCP client changes.
[EFFECT]
[RECOVERY]
vRtrAutoCfgRaRtStatusChanged
.1.3.6.1.4.1.6527.3.1.3.3.0.93
[CAUSE] The vRtrAutoCfgRaRtStatusChanged notification is sent when the
value of the object vRtrAutoCfgRaRtStatus changes; that includes when
a row in the vRtrAutoCfgRaRtTable is created or destroyed.
[EFFECT] A value of 'installed' indicates the received route is valid,
and is successfully installed in the route table.
[RECOVERY] The recovery action, if necessary, depends on the actual
state.
vRtrIfDhcp6ClStateDnsChanged
.1.3.6.1.4.1.6527.3.1.3.3.0.94
[CAUSE] The vRtrIfDhcp6ClStateDnsChanged notification is sent when the
value of any of the DNS addresses of the DHCP client changes.
[EFFECT]
[RECOVERY]
vRtrIfEthLoopbackStarted
.1.3.6.1.4.1.6527.3.1.3.3.0.96
[CAUSE] The vRtrIfEthLoopbackStarted notification is generated when
the router interface is placed into loopback.
[EFFECT] This notification is informational only.
vRtrIfEthLoopbackStopped
.1.3.6.1.4.1.6527.3.1.3.3.0.97
[CAUSE] The vRtrIfEthLoopbackStopped notification is generated when
the router interface is removed from loopback.
[EFFECT] This notification is informational only.
tmnxVRtrBfdExtNoFreeTxIntrvlSlot
.1.3.6.1.4.1.6527.3.1.3.3.0.98
[CAUSE] The tmnxVRtrBfdExtNoFreeTxIntrvlSlot is generated when a BFD
session of type fp must use another transmit interval than negotiated
with the peer because all transmit interval slots available in
hardware (8) are already in use.
[EFFECT] There is no effect of this notification.
[RECOVERY] The problem can be mitigated by changing the configuration
on this node and its peer nodes to use maximum 8 combinations of local
multiplier, local transmit interval and remote receive interval.
tmnxVRtrFibVPNOccupancyThreshold
.1.3.6.1.4.1.6527.3.1.3.3.0.99
The tmnxVRtrFibVPNOccupancyThreshold notification is generated when
the VPN FIB on an IOM card transitions between experiencing persistent
normal and high occupancy.
TDot1pAppId
timetraVRtrMIBModule 
vRtrConfTable 
vRtrConfEntry 
vRtrID 
tmnxSrlgGroupTblLastCh 
tmnxVRtrMidRouteTCA