TIMETRA-OAM-TEST-MIB

TEXTUAL-CONVENTION

A value of type TmnxOamAddressType is an enumerated integer that indicates the type of address used in OAM test requests and responses.

TEXTUAL-CONVENTION

An object of type TmnxOamBierHistoryReturnCode indicates the value copied from the Return Code field of a BIER Echo Reply PDU. Code points include (but are not restricted to) the following. Value Interpretation ----- ------------------------------- 0 No return code 1 Malformed Echo Request received 2 One or more of the TLVs was not understood 3 Replying BFR is the only BFER in header Bitstring 4 Replying BFR is one of the BFER in header Bitstring 5 Packet-Forward-Success 6 Invalid Multipath Info Request 7 <not defined> 8 No matching entry in forwarding table. 9 Set-Identifier Mismatch 10 DDMAP Mismatch Zero is returned if a BIER Echo Reply PDU was not received (e.g. if a timeout occurred).

TEXTUAL-CONVENTION

An object of type TmnxOamBuildPktHeaderType specifies the type of a packet header used by the OAM Egress Finder. Abbreviations DOT1Q: IEEE 802.1Q GPRS: General Packet Radio Service GRE: Generic Routing Encapsulation GTP: GPRS Tunneling Protocol L2TP: Layer 2 Tunneling Protocol PBB: Provider Backbone Bridge

TEXTUAL-CONVENTION

A value of type TmnxOamLTtraceDisStatusBits is an enumerated integer that describes the LDP tree trace discovery status in BITS. This indicates different reason values when the tree discovery of an IP Address FEC is not completely successful. Code points: timeout (0) - one or more trace requests for an IP address FEC timed out maxPath (1) - reached the maximum allowed path limit for an IP address FEC maxHop (2) - reached the maximum allowed hop limit unexploredPath (3) - could not discover all possible paths noResource (4) - the internal resources required to complete the discovery were unavailable

TEXTUAL-CONVENTION

A value of type TmnxOamLspAssocChannel specifies the launched echo request's usage of the Associated Channel (ACH) mechanism, when testing an MPLS-TP LSP. Values: notApplicable(1) Used when the test is not testing an MPLS-TP LSP. nonIp(2) Use the Associated Channel mechanism described in RFC 6426, Section 3.3. none(3) Do not use an Associated Channel, as described in RFC 6426, Section 3.1. ipv4(4) Use the Associated Channel mechanism described in RFC 6426, Section 3.2.

TEXTUAL-CONVENTION

A value of type TmnxOamLspTestSubMode specifies the type of LSP ping or LSP trace route test to perform. LSP test types: static(2) Perform an LSP ping or LSP trace route test using the RFC 6426 'Target FEC Stack' code point 'Static LSP'. bgpLabeledPrefix(3) Perform an LSP ping or LSP trace route test using the RFC 4379 'Target FEC Stack' code point 'BGP labeled IPv4 prefix'. In future, 'bgpLabeledPrefix(3)' will also be used for the RFC 4379 'Target FEC Stack' code point 'BGP labeled IPv6 prefix'. srIsis(4) Perform an LSP ping or LSP trace route test in the Segment Routing (SR) case, where the Interior Gateway Protocol (IGP) is Intermediate System to Intermediate System (IS-IS). srOspf(5) Perform an LSP ping or LSP trace route test in the Segment Routing (SR) case, where the Interior Gateway Protocol (IGP) is Open Shortest Path First (OSPF). srTe(6) Perform an LSP ping or LSP trace route test in the Segment Routing Traffic Engineering (SR-TE) case. srPolicy(7) Perform an LSP ping or LSP trace route test using a Segment Routing policy. srOspf3(8) Perform an LSP ping or LSP trace route test in the SR case, where the IGP is OSPFv3. unspecified(1) Perform any other supported type of LSP ping or trace route test. Examples: an LSP ping or trace route test using the RFC 4379 'Target FEC Stack' code point 'LDP IPv4 prefix'; an LSP ping or trace route test using the RFC 4379 'Target FEC Stack' code point 'RSVP IPv4 LSP'.

TEXTUAL-CONVENTION

An object of type TmnxOamMplsEchoDownMapTlv specifies the type of downstream mapping TLV in an MPLS echo request PDU. 'dsmap(1)' specifies the Downstream Mapping TLV, as described in RFC 4379, Section 3.3. 'ddmap(2)' specifies the Downstream Detailed Mapping TLV, as described in RFC 6424, Section 3.3.

TEXTUAL-CONVENTION

An object of type TmnxOamMplsEchoDownMapTlvOrNone specifies the type of downstream mapping TLV in an MPLS echo request PDU (or no downstream mapping TLV). 'dsmap(1)' specifies the Downstream Mapping TLV, as described in RFC 4379, Section 3.3. 'ddmap(2)' specifies the Downstream Detailed Mapping TLV, as described in RFC 6424, Section 3.3. 'none(3)' specifies none of the above TLVs.

TEXTUAL-CONVENTION

A value of type TmnxOamMplsTpPathType specifies the type of an MPLS-TP path to be tested. Path types: working(1) - test the primary path of the MPLS-TP LSP protect(2) - test the secondary path of the MPLS-TP LSP active(3) - test the currently active path of the MPLS-TP LSP

TEXTUAL-CONVENTION

A value of type TmnxOamPingRtnCode is an enumerated integer that indicates the return code received in the OAM ping response common header. Code points: notApplicable The return code has no significance in the context of the test being conducted. fecEgress Replying router is an egress for the Forwarding Equivalence Class (FEC). fecNoMap Replying router has no mapping for the FEC. notDownstream Replying router is not one of the downstream routers. downstream Replying router is one of the downstream routers and its mapping for this FEC on the received interface is the given label. downstreamNotLabel Replying router is one of the downstream routers but its mapping for this FEC is not the given label. downstreamNotMac Replying router is one of the downstream routers but it does not have the given MAC address downstreamNotMacFlood Replying router is one of the downstream routers but it does not have the given MAC address and is unable to flood the request. malformedEchoRequest A malformed echo request was received. tlvNotUnderstood One or more of the TLVs was not understood. downstreamNotInMfib Replying router is one of the downstream routers but it does not have an MFIB entry for the given source group combination. downstreamMismatched Downstream mapping mismatched. upstreamIfIdUnkn Upstream interface index unknown. noMplsFwd Label switched but no MPLS forwarding at stack-depth. noLabelAtStackDepth No label entry at stack-depth. protoIntfMismatched Protocol not associated with interface at FEC stack-depth. terminatedByOneLabel Premature termination of ping due to label stack shrinking to a single label. seeDDMapForRetCodeSubCode See DDMap TLV for rc and sub-rc. fecStackChange Label switched with FEC stack change.

TEXTUAL-CONVENTION

An object of type TmnxOamResponseStatus indicates the status of an OAM Echo probe operation. responseReceived(1) - Operation completed successfully. unknown(2) - Operation failed due to unknown error. internalError(3) - An implementation detected an error in its own processing that caused an operation to fail. maxConcurrentLimitReached(4) - The maximum number of concurrent active operations would have been exceeded if the corresponding operation was allowed. requestTimedOut(5) - Operation failed to receive a valid reply within the time limit imposed on it. unknownOrigSdpId(6) - Invalid or non-existent originating SDP-ID. downOrigSdpId(7) - The originating SDP-ID is operationally down. requestTerminated(8) - The OAM ping test was terminated by the manager before reply or timeout. invalidOriginatorId(9) - The far-end replied with an invalid originator-ID error. invalidResponderId(10) - The far-end replied with an invalid responder-ID error. unknownRespSdpId(11) - The far-end replied with an invalid response SDP-ID error. downRespSdpId(12) - The far-end replied with down (admin or oper) response SDP-ID. invalidServiceId(13) - Invalid or non-existent originator Service-ID (svc-ping). invalidSdp(14) - Invalid or non-existent SDP for Service (svc-ping). downServiceSdp(15) - SDP for the Service is down. (svc-ping). noServiceEgressLabel(16) - Non-existent Service egress label. (svc-ping). invalidHostAddress(17) - The IP address for a host has been determined to be invalid. Examples of this are broadcast or multicast addresses. (svc-ping). invalidMacAddress(18) - The MAC address specified has been determined to be invalid. (macPing). invalidLspName(19) - The LSP name specified has been determined to be invalid. (lspPing). macIsLocal(20) - MAC Ping or Trace route not sent because the MAC address is on a local SAP or CPU. (MAC-Ping/MAC-TR). farEndUnreachable(21) - No route to the far end of the GRE SDP tunnel. downOriginatorId(22) - The ping originator is operationally down. downResponderId(23) - The ping responder is operationally down. changedResponderId(24) - The ping responder-ID is changed. downOrigSvcId(25) - Service on the originator side is operationally down. (svc-ping). downRespSvcId(26) - Service on the responder side is operationally down. (svc-ping). noServiceIngressLabel(27) - Non-existent service ingress label. (svc-ping). mismatchCustId(28) - Service customer ID mismatch between originator and responder. (svc-ping). mismatchSvcType(29) - Service type mismatch between originator and responder. (svc-ping). mismatchSvcMtu(30) - Service MTU mismatch between originator and responder. (svc-ping). mismatchSvcLabel(31) - Service label mismatch between originator and responder. (svc-ping). noSdpBoundToSvc(32) - No SDP bound to the service. (svc-ping). downOrigSdpBinding(33) - SDP binding is down on the Originator side. (sdp-ping). invalidLspPathName(34) - The LSP path name specified is invalid. (lsp-ping). noLspEndpointAddr(35) - No LSP Endpoint address. (lsp-ping). invalidLspId(36) - No active LSP path found. (lsp-ping). downLspPath(37) - LSP path is operationally down. (lsp-ping). invalidLspProtocol(38) - LSP Protocol is not supported or is invalid. (lsp-ping). invalidLspLabel(39) - LSP label is invalid. (lsp-ping). routeIsLocal(40) - The route is a local route. (vprn-ping). noRouteToDest(41) - There is no route to the destination. (vprn-ping). localExtranetRoute(42) - The route is a local extranet route. (vprn-ping). srcIpInBgpVpnRoute(43) - The source IP belongs to a BGP-VPN route. (vprn-ping). srcIpInvalid(44) - The source IP is invalid or there is no route to the source. (vprn-ping) bgpDaemonBusy(45) - The BGP routing daemon is busy; vprn route target information is not retrievable. (vprn-trace) mcastNotEnabled(46) - Multicast is not enabled. Multicast trace cannot be initiated. (mtrace) mTraceNoSGFlow(47) - No (*,G)/(S,G) flow on the router. Multicast trace cannot be initiated. (mtrace) mTraceSysIpNotCfg(48) - System ip address not configured. It is used as the response address in the multicast trace query. (mtrace) noFwdEntryInMfib(49) - No forwarding entry could be found for the specified source and destination address in the MFIB. (mfib-ping). dnsNameNotFound(50) - The domain name specified in the DNS query does not exist. noSocket(51) - unable to get socket. (icmp-ping). socketOptVprnIdFail(52) - unable to set SO_VPRNID for socket. (icmp-ping). socketOptIfInexFail(53) - unable to set IP_IFINDEX for socket. (icmp-ping). socketOptNextHopFail(54) - unable to set IP_NEXT_HOP for socket. (icmp-ping). socketOptMtuDiscFail(55) - unable to set IP_MTU_DISC for socket. (icmp-ping). socketOptSndbufFail(56) - unable to set SO_SNDBUF for socket. (icmp-ping). socketOptHdrincFail(57) - unable to set IP_HDRINCL for socket. (icmp-ping). socketOptTosFail(58) - unable to set IP_TOS for socket. (icmp-ping). socketOptTtlFail(59) - unable to set IP_TTL for socket. (icmp-ping). bindSocketFail(60) - unable to bind socket. (icmp-ping). noRouteByIntf(61) - no route to destination via the specified interface. (icmp-ping). noIntf(62) - no interface specified. (icmp-ping). noLocalIp(63) - unable to find local IP address. (icmp-ping). sendtoFail(64) - sendto function failed. (icmp-ping). rcvdWrongType(65) - received packet of wrong ICMP type. (icmp-ping). noDirectInterface(66) - no direct interface to reach destination. (icmp-ping). nexthopUnreachable (67) - unable to reach the next-hop. (icmp-ping). socketOptHwTimeStampFail (68) - unable to set IP_TIM_TIME for socket. (icmp-ping). noSpokeSdpInVll (69) - unable to find spoke-sdp given sdp-id:vc-id (vccv-ping). farEndVccvNotSupported (70) - far end does not support the VCCV options. (vccv-ping). noVcEgressLabel (71) - no VC egress label to send vccv-ping. socketOptIpSessionFail (72) - unable to set IP_SESSION for socket. (icmp-ping). rcvdWrongSize(73) - received packet of wrong size. (icmp-ping). dnsLookupFail (74) - DNS lookup failed. (icmp-ping). noIpv6SrcAddrOnIntf (75) - no IPv6 source on the interface (icmp-ping). multipathNotSupported (76) - downstream node does not support multipath. (lsp-trace). nhIntfNameNotFound (77) - Given next-hop interface name not found. (lsp-ping/trace). msPwInvalidReplyMode (78) - MS-PW switching node supports ip-routed reply mode only (vccv-ping). ancpNoAncpString (79) - ANCP string unknown to the system. ancpNoSubscriber (80) - subscriber unknown to the system. ancpNoAncpStringForSubscriber (81) - subscriber has no associated ANCP string. ancpNoAccessNodeforAncpString (82) - no access node is found for the given ANCP string. ancpNoAncpCapabilityNegotiated (83) - ANCP capability not negotiated with the involved DSLAM. ancpOtherTestInProgress (84) - another ANCP test is running for this ANCP string. ancpMaxNbrAncpTestsInProgress (85) - max number of concurrent ANCP tests reached. spokeSdpOperDown (86) - spoke-sdp is operationally down (vccv-ping). noMsPwVccvInReplyDir (87) - Switching node in MS-PW with no VCCV support in echo reply direction. p2mpLspNameOrInstInvalid (88) - P2MP LSP name or instance provided is not valid. p2mpLspS2LPathDown (89) - LSP path to S2L is down. p2mpLspS2LAddressInvalid (90) - One or more S2L address is not valid. p2mpLspNotOperational (91) - P2MP LSP is operationally down. p2mpLspTrMultipleReplies (92) - Probe returned multiple responses. Result may be inconsistent. invalidMepId (93) - The user-configured MEP identifier is not valid. multipleReplies (94) - more than one reply received, when one was expected. packetSizeTooBig (95) - The packet is larger than the network's MTU and cannot be fragmented. For ICMP-ping tests, this results from an ICMPv4 type 3 code 4 or ICMPv6 type 2 message. gtpPingError (96) - General GTP Ping Error. gtpPingRsrcUnavailable (97) - GTP Path management resource unavailable. gtpPingDupRequest (98) - Duplicate request for the same peer. gtpPingCleanUpInProg (99) - GTP Path management clean up in progress. invalidInterface (100) - The egress interface specified does not exist. p2mpLspNotFound (101) - The P2MP-LSP not found given LDP-ID or sender address. ethCfmSlmInLoss(102) - Synthetic Loss Measurement (SLM) probe lost in transit from far-end node to local agent. ethCfmSlmOutLoss(103) - SLM probe lost on transmit from local agent to far-end node. ethCfmSlmUnacknowledged(104) - SLM probe lost but unable to identify loss reason. spokeSdpFecNoBndFound(105) - Spoke-sdp-fec is invalid or has no associated SDP binding yet. mtraceNotSupportedP2mp(106) - mtrace not supported in base routing context when incoming interface is p2mp useFec129Parameters(107) - specify FEC129 parameters for FEC129 PW instead of sdp-id:vc-id dnsServerUnexpectedResponse(108) - nameserver unexpected response. dnsServerResponseFormErr(109) - nameserver responded with FORMERR. dnsServerResponseServFail(110) - nameserver responded with SERVFAIL. dnsServerResponseNotImp(111) - nameserver responded with NOTIMP. dnsServerResponseRefused(112) - nameserver responded with REFUSED. sendFailUndefinedServiceId(113) - The OAM test cannot be performed because the associated service does not exist. sendFailWrongServiceType(114) - The OAM test cannot be performed because the associated service is of the wrong type. sendFailSubnettedService(115) - The OAM test cannot be performed on a service with a specified MAC subnet length. invalidRespServiceId(116) - Invalid or non-existent responder Service-ID. adminDownOrigSdpBind(117) - SDP binding is administratively down on the originator side. operDownRespSdpBind(118) - SDP binding is operationally down on the responder side. adminDownRespSdpBind(119) - SDP binding is administratively down on the responder side. sdpBindVcidMismatch(120) - SDP binding VC ID mismatch between originator and responder. sdpBindTypeMismatch(121) - SDP binding type mismatch between originator and responder. sdpBindVcTypeMismatch(122) - SDP binding VC type mismatch between originator and responder. sdpBindVlanVcTagMismatch(123) - SDP binding VLAN VC tag mismatch between originator and responder. adminDownOrigSvc(124) - Service on the originator side is administratively down. adminDownRespSvc(125) - Service on the responder side is administratively down. adminDownOrigSdpId(126) - The originating SDP-ID is administratively down. adminDownRespSdpId(127) - The responding SDP-ID is administratively down. mTraceSourceIsNotRemote(128) - The multicast trace route test cannot be performed because the source address is not remote. invalidVirtualRouterId(129) - The OAM test cannot be performed because the associated virtual router ID is invalid. ldpPrefixIsLocal(130) - The OAM test cannot be performed because the associated LDP prefix is local to the system. sourceIpIsNotLocal(131) - The OAM test cannot be performed because the associated source address is not local to the system. nextHopIpIsLocal(132) - The OAM test cannot be performed because the associated next hop address is local to the system. targetIpIsLocal(133) - The OAM test cannot be performed because the associated target address is local to the system. invalidControlPlaneOption(134) - The OAM test cannot be performed because the control plane send or receive option is not allowed with the specified service. iomRevisionNotSupported(135) - The OAM test cannot be performed due to a mismatch in supported revision with the provisioned IOMs. invalidSourceMacOption(136) - The OAM test cannot be performed because the source MAC option is not allowed with the specified service. sendFailSpbMgdService(137) - The OAM test cannot be performed on a service which is managed by SPB. useStaticPwParameters(138) - The spoke SDP is configured for static PW. type1Fec129PwNotSupported(139) - The OAM test is not supported on type 1 FEC129 pseudowires. mplsTpLspPathNotOperational(140) - The OAM test cannot be performed because the MPLS-TP LSP path is not operational. invalidStaticMplsTpLsp(141)- The OAM test only supports static MPLS-TP LSPs. controlWordNotValid(142) - The control word for the spoke-sdp is not valid for this OAM test. pwPathIdNotConfigured(143) - The pw-path-id provisioning is not complete. notSupportedOnVcSwitchService(144) - The OAM test is not supported on a vc-switching service. sdpFarEndNotSupported(145) - The OAM test does not support the SDP far end value. mplsTpLspPathShutdown(146) - The MPLS-TP path is currently shutdown. forceOptionIsBlocked(147) - The force option is currently blocked because of the configuration of a related entity. intfForLspPathIsNotOperational(148) - The interface for the LSP path is not operational ttlExpired(149) - The destination could not be reached because the time-to-live (IPv4) or hop limit (IPv6) was too small. This results from an ICMPv4 type 11 code 0 or ICMPv6 type 3 code 0 message. networkUnreachable(150) - The network specified by the destination address is unreachable. This results from an ICMPv4 type 3 code 0 or ICMPv6 type 1 code 0 message. hostUnreachable(151) - The host specified by the destination address is unreachable. This results from an ICMPv4 type 3 code 1 or ICMPv6 type 1 code 3 message. bgpLabelPrefixIsLocal(152) - The OAM test cannot be performed because the associated BGP Label Route prefix is local to the system. bgpLabelPrefixUnknown(153) - The OAM test cannot be performed because the BGP Target FEC prefix entry is not found in the Routing Table. ldpPrefixUnknown(154) - The OAM test cannot be performed because the LDP Target FEC prefix entry is not found in the Routing Table. l2tpv3DeliveryTypeUnsupported(155) - The OAM test cannot be performed because the l2TPv3 delivery type is unsupported. vPingPeerCvNoLspPing(156) - The OAM test cannot be performed because the peer CV bits do not support lsp ping. vPingPeerCcNoCtrlWord(157) - The OAM test cannot be performed because the peer CC bits do not support control word. sendFailEvpnCfgdService(158) - The OAM test cannot be performed on a VPLS service that has EVPN configured. sendFailed(159) - The OAM test cannot send the test packet. minimumPacketSizeNotMet(160) - The OAM test cannot send the test packet as the minimum required packet size exceeds the user supplied packet size. invalidTargetFecType(161) - The OAM test does not support this FEC type. p2mpLspPingNotSupportedOnMgmtRtr(162) - The OAM p2mpLspPing test is not supported on the management router. ipv4SdpFarEndsOnly(163) - The OAM test only supports bindings and SDPs using an IPv4 far end. vxlanEgrBndSvcMismatch(164) - The OAM test cannot send packets to a VXLAN egress binding not owned by the same service as the one sending. vxlanNoMatchingTep(165) - The OAM test can only send to VTEPs that have been configured. vxlanEvpnUnconfigured(166) - The OAM test can only send on a service with EVPN configured. ipv6SdpFarEndsNotSupported(167) - The OAM test does not support bindings and SDPs using an IPv6 far end. oamTestOverSRTunNotSupported(168) - The OAM test is not supported on SR tunnels. sendFailEvpnCfgdPbbService(169) - The OAM test cannot be performed on a VPLS/Epipe service that is associated with a b-vpls that has EVPN configured. txPortDown(170) - The transmit port is operationally down. noTxPort(171) - No transmit port. parentAdminDown(172) - The parent (SPOKE, SAP, service or port) of the MEP is administratively down. destMacResolveFail(173) - Unable to resolve the remote-mepid to a unicast layer2 MAC address. vxlanIpV6TermUnsupported(174) - The OAM test does not support IPv6 tunnel termination points. ipPrefixIsLocal(175) - The OAM test cannot be performed because the associated IP prefix is local to the system. ipPrefixUnknown(176) - The OAM test cannot be performed because the Target FEC prefix entry is not found in the Routing Table. greEthBrdgdDelvryTypeUnsupported(177) - The OAM test cannot be performed because the GRE Ethernet Bridged delivery type is unsupported. mtrace2Disabled(178) - The mtrace2 test cannot be performed because mtrace2 is disabled at the system level. ipv6TunneledNextHopUnsupported(179) - The VPRN ping/trace test has no support for IPv6 tunneled next hops. srTunneledNextHopUnsupported(180) - The VPRN ping/trace test has no support for Segment Routing tunneled next hops. srTeTunneledNextHopUnsupported(181) - The VPRN ping/trace test has no support for Segment Routing Traffic Engineering next hops. nextHopIpIsSubnet(182) - The OAM test cannot be performed because the associated next hop address is a subnet. ipDestAndNextHopComboUnsupported(183) - The IP destination address type and provided next hop type is not a supported combination. resolvedIpDstSrcComboUnsupported(184) - The resolved IP destination address type and provided source address type is not a supported combination. srPolicyNotFound(185) - The SR-POLICY not found given color and endpoint. srPolicySegmentListNotFound(186) - The SR-POLICY's segment list not found given segment list Id. ethCfmUnsupportedTestType(187) - The test type is not valid for the MEP. ipPrefixInvalid(188) - The OAM test cannot be performed because the Target FEC prefix entry is not valid for the test. bierError (189) - The BIER OAM test received a reply with an unsuccessful return code.

TEXTUAL-CONVENTION

A value of type TmnxOamSaaThreshold is a enumerated integer that indicates which type of thresholds should be monitored upon completion of an OAM ping test run. When the corresponding threshold is crossed, a tmnxOamSaaThreshold notification will be generated. noThreshold(0) No threshold type is configured. inJitter (1) Monitor the value of jitter calculated for the inbound, one-way, OAM ping responses received for an OAM ping test run. outJitter (2) Monitor the value of jitter calculated for the outbound, one-way, OAM ping requests sent for an OAM ping test run. rtJitter (3) Monitor the value of jitter calculated for the round trip, two-way, OAM ping requests and replies for an OAM ping test run. inLoss (4) Monitor the number of inbound OAM ping responses not received for an OAM ping test run. outLoss (5) Monitor the number of outbound OAM ping requests that could not be sent for an OAM ping test run. rtLoss (6) Monitor the amount of packet loss for a round trip OAM ping test run. inLatency (7) Monitor the average amount of latency of inbound OAM ping responses for an OAM ping test run. outLatency (8) Monitor the average amount of latency of outbound OAM ping requests for an OAM ping test run. rtLatency (9) Monitor the average amount of round trip latency for an OAM ping test run.

TEXTUAL-CONVENTION

A value of type TmnxOamSignalProtocol indicates the type of label signaling protocol used by a router in a specific Layer 2 mapping entry. Code Points unknown - protocol is unknown static - statically configured Label Switched Path (LSP) bgp - Border Gateway Protocol ldp - Label Distribution Protocol rsvpTe - Resource Reservation Protocol, Traffic Engineering ospf - Open Shortest Path First isis - Intermediate System to Intermediate System

TEXTUAL-CONVENTION

A value of type TmnxOamTestMode is an enumerated integer that indicates the type of OAM test.

TEXTUAL-CONVENTION

A value of type TmnxOamTestResponsePlane is an enumerated integer that indicates the response plane from which the OAM ping or traceroute response was received.

TEXTUAL-CONVENTION

A value of type TmnxOamTestResult is an enumerated integer that describes the result of a ping or trace test run. Code points: undetermined (0) The result is, as yet, unknown. success (1) The test was successful. failed (2) The test failed. aborted (3) The test was terminated before completion. txResourcesUnavail(4) The test did not start because transmit resources are unavailable.

TEXTUAL-CONVENTION

An object of type TmnxOamVcType indicates the type of SDP binding associated with a Virtual Circuit (VC).

TEXTUAL-CONVENTION

A value of type TmnxOamVccvAssocChannel specifies the launched echo request's usage of the Associated Channel (ACH) mechanism, when performing an MPLS-TP VCCV test. Values: notApplicable(1) Used when the test is not an MPLS-TP VCCV test. nonIp(2) Use the Associated Channel mechanism described in RFC 6426, Section 3.3. ipv4(3) Use the Associated Channel mechanism described in RFC 6426, Section 3.2.

TEXTUAL-CONVENTION

An object of type TmnxOamVccvSwitTgtFecType specifies the type of downstream FEC (Forward Equivalence Class) segment to be tested during a VCCV ping or trace route test. The path to be tested starts with a FEC segment, and switches to a FEC segment with the specified (different) type. Values: none(1) The path to be tested does not switch FEC types. fec128(2) Switch to a segment with FEC type 'FEC 128 Pseudowire'. static(3) Switch to a segment with FEC type 'Static Pseudowire'.

TEXTUAL-CONVENTION

A value of type TmnxOamVccvTestSubMode specifies the type of VCCV ping or VCCV trace route test to perform. VCCV test types: static(2) Perform a VCCV ping or VCCV trace route test using the RFC 6426 'Target FEC Stack' code point 'Static Pseudowire'. unspecified(1) Perform any other supported type of VCCV ping or trace route test. Examples: a VCCV ping or VCCV trace route test using the RFC 4379 'Target FEC Stack' code point 'FEC 128 Pseudowire'; a VCCV ping or VCCV trace route test using the RFC 4379 'Target FEC Stack' code point 'FEC 129 Pseudowire'.

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-TYPE

The maximum number of concurrent active OAM ping tests that are allowed within an agent implementation. A value of zero (0) for this object implies that there is no limit for the number of concurrent active tests in effect.

OBJECT-TYPE

tmnxOamPingCtlTable contains configuration and status information for ping tests. tmnxOamDiagCtlTable and tmnxOamTrCtlTable fill the same role for diagnostic tests and trace route tests, respectively.

OBJECT-TYPE

tmnxOamPingCtlEntry contains configuration and status information for one ping test. Rows are created/destroyed using tmnxOamPingCtlRowStatus. The test's test type (e.g. 'icmpPing(15)') is configured using tmnxOamPingCtlTestMode. Depending on the test type, configuration specific to the test type may reside in a child table (e.g. tmnxOamIcmpPingCtlTable or tmnxOamLspPingCtlTable). Test results reside in tmnxOamPingResultsTable, tmnxOamPingHistoryTable, and a set of tables specific to the test type (e.g. tmnxOamVxlanPingResultsTable, tmnxOamMacPingHistoryTable).

OBJECT-TYPE

The value of tmnxOamPingCtlOwnerIndex specifies the owner name of the test.

OBJECT-TYPE

The value of tmnxOamPingCtlTestIndex specifies the test name of the test. The test is identified by the owner name and the test name. One owner typically owns several tests. This indexing method ensures tests created by several owners have unique indices.

OBJECT-TYPE

The value of tmnxOamPingCtlRowStatus specifies the status of the row for the specified ping test. Deleting a row deletes all the child rows with the same owner name and test name, including additional configuration rows (e.g. tmnxOamIcmpPingCtlEntry), and rows containing test results (e.g. tmnxOamVxlanPingHistoryEntry).

OBJECT-TYPE

The storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write access to any columnar objects in the row. This object was marked obsolete in SROS Release 14.0 R1. There is no replacement object.

OBJECT-TYPE

The purpose of this object is to provide a descriptive name of the OAM ping test. This object was marked obsolete in SROS Release 14.0 R1. There is no replacement object.

OBJECT-TYPE

The value of tmnxOamPingCtlTestMode specifies the type of OAM ping test defined by this row. none - the test type is unspecified. sdpPing - tests SDP connectivity and round trip time. mtuPing - tests MTU path size. svcPing - determines the existence and operational state of the service ID on the far end ESR. macPing - determines address mappings for the service ID. macPopulate - populates an OAM MAC address into the FIBs. macPurge - deletes an OAM MAC address from the FIBs. lspPing - tests Label Switched Path (LSP) path connectivity and round trip time. vprnPing - tests IP path connectivity and round trip time within a specified VPRN service. atmPing - tests ATM path connectivity and round trip time on an ATM VCC. mfibPing - tests IP multicast connectivity and round trip time within a specified VPLS service. cpePing - determines IP connectivity to a CPE within a specified VPLS service. mrInfo - get a multicast router's capabilities and the list of interfaces with neighbors. vccvPing - Virtual Circuit Connectivity Verification, testing pseudowire connectivity and round trip time. icmpPing - tests IP connectivity and round trip time. dnsPing - tests DNS name resolution connectivity and round trip time. ancpLoopback - send an OAM loopback test request to the access node. p2mpLspPing - tests P2MP LSP path connectivity and round trip time. ethCfmLoopback - performs Ethernet Connectivity Fault Management (CFM) loopback tests. This MIB supports the SAA form of this test only (the OAM form uses a separate set of objects - see IEEE8021-CFM-MIB). ethCfmTwoWayDelay - performs Ethernet Connectivity Fault Management (CFM) two way delay tests. This MIB supports the SAA form of this test only (the OAM form uses a separate set of objects - see IEEE8021-CFM-MIB). gtpPing - tests GTP (GPRS Tunnelling Protocol) path connectivity. ethCfmTwoWaySlm - performs Ethernet Connectivity Fault Management (CFM) two way Synthetic Loss Measurement (SLM) tests. This MIB supports the SAA form of this test only (the OAM form uses a separate set of objects - see TIMETRA-IEEE8021-CFM-MIB). vxlanPing - tests Virtual Extensible Local Area Network (VXLAN) connectivity, checks the status of configured VXLAN Network IDs (VNIs), and allows validation of connected end systems. bierPing - performs a Bit Index Explicit Replication (BIER) multicast connectivity test. When tmnxOamPingCtlTestMode is set, SROS may automatically create a same-INDEX row in a table used to configure objects specific to the test type (as shown in the following table). tmnxOamPingCtlTestMode Auto-Gen Row for Additional Configuration ---------------------- ----------------------------------------- 'ancpLoopback' tmnxOamAncpTestCtlTable 'atmPing' tmnxOamAtmPingCtlTable 'bierPing' tmnxOamBierPingCtlTable 'cpePing' tmnxOamCpePingCtlTable 'dnsPing' none 'ethCfmLoopback' tmnxOamEthCfmPingCtlTable 'ethCfmTwoWayDelay' tmnxOamEthCfmPingCtlTable 'ethCfmTwoWaySlm' tmnxOamEthCfmPingCtlTable 'gtpPing' tmnxOamMobGtpPingCtlTable 'icmpPing' tmnxOamIcmpPingCtlTable 'lspPing' tmnxOamLspPingCtlTable 'macPing' tmnxOamMacPingCtlTable 'macPopulate' tmnxOamMacPingCtlTable 'macPurge' tmnxOamMacPingCtlTable 'mfibPing' tmnxOamMfibPingCtlTable 'mrInfo' none 'mtuPing' none 'p2mpLspPing' tmnxOamP2mpLspPingCtlTable 'sdpPing' none 'svcPing' none 'vccvPing' tmnxOamVccvPingCtlTable 'vprnPing' tmnxOamVprnPingCtlTable 'vxlanPing' tmnxOamVxlanPingCtlTable The support for Service Assurance Agent (SAA) tests (i.e. tests with tmnxOamSaaCtlTable rows) and OAM tests (i.e. tests without tmnxOamSaaCtlTable rows) varies with the test type, as shown in the following table. tmnxOamPingCtlTestMode SAA Supported OAM Supported ---------------------- ------------- ------------- 'ancpLoopback' No Yes 'atmPing' No Yes 'bierPing' No Yes 'cpePing' Yes Yes 'dnsPing' Yes Yes 'ethCfmLoopback' Yes No 'ethCfmTwoWayDelay' Yes No 'ethCfmTwoWaySlm' Yes No 'gtpPing' No Yes 'icmpPing' Yes Yes 'lspPing' Yes Yes 'macPing' Yes Yes 'macPopulate' No Yes 'macPurge' No Yes 'mfibPing' No Yes 'mrInfo' No Yes 'mtuPing' No Yes 'p2mpLspPing' No Yes 'sdpPing' Yes Yes 'svcPing' No Yes 'vccvPing' Yes Yes 'vprnPing' Yes Yes 'vxlanPing' No Yes

OBJECT-TYPE

The value of tmnxOamPingCtlAdminStatus specifies the administrative state of the specified ping test. An attempt to set tmnxOamPingCtlAdminStatus to 'enabled' will fail if the objects required by the ping test have not been set. When this object has the value 'enabled' an attempt to modify any of the test's configurable objects will fail. Upon completion of a ping test, the agent resets the value of this object to 'disabled'.

OBJECT-TYPE

Specifies the originating SDP-ID to be used for performing a sdp-ping or mtu-ping operation. This parameter is required only if tmnxOamPingCtlTestMode has a value of either 'sdpPing' or 'mtuPing'. The far-end address of the specified SDP-ID is the expected responder-id within each OAM reply message received. The specified SDP-ID defines the encapsulation of the SDP tunnel encapsulation used to reach the far-end. This can be IP/GRE or MPLS. The value of tmnxOamPingCtlFcName is used to define the outgoing forwarding class used for the SDP encapsulation. If the value of tmnxOamPingCtlOrigSdpId is invalid, or the SDP is administratively down, or unavailable, the OAM Echo request message probe is not sent and an appropriate error value is written to tmnxOamPingHistoryStatus for that probe entry. Once the interval timer expires, the next probe attempt will be made if required.

OBJECT-TYPE

Specifies the return SDP-ID to be used by the far-end node for its message reply. This parameter is optional and is valid only if tmnxOamPingCtlTestMode has a value of 'sdpPing'. If this SDP-ID does not exist on the far-end, terminates on another node different than the originating node, or some other issue prevents the far-end from using the specified SDP-ID, the OAM Echo message reply is sent using generic IP/GRE OAM encapsulation. The received forwarding class (as mapped on the ingress network interface for the far-end) defines the forwarding class encapsulation for the reply message.

OBJECT-TYPE

The value of tmnxOamPingCtlFcName specifies the forwarding class to be used when launching the probe(s). The forwarding class name must be present in the index column of TIMETRA-QOS-MIB::tFCNameTable. This object is optional. As shown in the following table: 1. This object is applicable to a subset of the test types, and 2. This object is configurable for a subset of the test types, and 3. The default forwarding class depends on the test type. tmnxOamPingCtlTestMode Applicable? Configurable? Default ---------------------- ----------- ------------- ------- 'cpePing' yes yes 'be' 'bierPing' yes yes 'be' 'ethCfmLoopback' yes yes 'nc' 'ethCfmTwoWayDelay' yes yes 'nc' ethCfmTwoWaySlm' yes yes 'nc' 'icmpPing' yes yes 'nc' 'lspPing' yes yes 'be' 'macPing' yes yes 'be' 'p2mpLspPing' yes yes 'be' 'sdpPing' yes yes 'be' 'svcPing' yes no 'nc' 'vccvPing' yes yes 'be' 'vprnPing' yes yes 'be' 'vxlanPing' yes yes 'be' otherwise no N/A N/A For 'ethCfmLoopback','ethCfmTwoWayDelay', and 'ethCfmTwoWaySlm', the forwarding class depends on whether the request is configured to egress on a network port or an access port. In the network port case, the forwarding class is the forwarding class of the pseudowire. In the access port case, the forwarding class is that of the SAP's egress encapsulation policy. For 'lspPing' this is the forwarding class of the LSP tunnel. For 'macPing' or 'sdpPing' this is the forwarding class of the SDP encapsulation. For 'p2mpLspPing' this is the forwarding class of the P2MP LSP tree. For 'vccvPing' this is the forwarding class of the pseudowire. If forwarding classes are mapped by the applicable QoS policy, the probe(s) may be launched using a different forwarding class than the forwarding class specified by this object.

OBJECT-TYPE

The value of tmnxOamPingCtlProfile specifies the profile to be used with the forwarding class specified in tmnxOamPingCtlFcName. This object is optional. As shown in the following table: 1. This object is applicable to a subset of the test types, and 2. This object is configurable for a subset of the test types, and 3. The default profile value depends on the test type. tmnxOamPingCtlTestMode Applicable? Configurable? Default ---------------------- ----------- ------------- ------- 'cpePing' yes yes 'out(2)' 'bierPing' yes yes 'out(2)' 'ethCfmLoopback' yes yes 'in(1)' 'ethCfmTwoWayDelay' yes yes 'in(1)' 'ethCfmTwoWaySlm' yes yes 'in(1)' 'lspPing' yes yes 'out(2)' 'macPing' yes yes 'out(2)' 'p2mpLspPing' yes yes 'out(2)' 'sdpPing' yes yes 'out(2)' 'svcPing' yes no 'in(1)' 'vccvPing' yes yes 'out(2)' 'vprnPing' yes yes 'out(2)' 'vxlanPing' yes yes 'in(1)' otherwise no N/A N/A

OBJECT-TYPE

The value of tmnxOamPingCtlMtuStartSize specifies the size of the first OAM Echo message sent as part of an 'mtuPing' test. Setting this object to a non-zero value is a prerequisite for starting an 'mtuPing' test. Its value must be less than or equal to the value of tmnxOamPingCtlMtuEndSize. An attempt to set this object from a non-zero value to zero will fail with a wrongValue error. Changing the message size is a method of checking the ability of an SDP to support a particular path-mtu value. The size of the message does not include the SDP encapsulation, VC-Label (if applied) or any DLC headers or trailers.

OBJECT-TYPE

The value of tmnxOamPingCtlMtuEndSize specifies the size of the last OAM Echo message sent as part of an 'mtuPing' test. Setting this object to a non-zero value is a prerequisite for starting an 'mtuPing' test. Its value must be greater than or equal to the value of tmnxOamPingCtlMtuStartSize. An attempt to set this object from a non-zero value to zero will fail with a wrongValue error.

OBJECT-TYPE

Specifies the number of octets by which to increment the OAM Echo message request size for each message request sent when tmnxOamPingCtlTestMode is set equal to 'mtuPing'. If the next incremented message size is greater than tmnxOamPingCtlMtuEndSize, the last message has already been sent. The next size message is not sent until a reply is received or three messages have timed out at the current size. This parameter is optional.

OBJECT-TYPE

This object was obsoleted in release 4.0 and replaced with InetAddress objects tmnxOamPingCtlTgtAddrType and tmnxOamPingCtlTgtAddress.

OBJECT-TYPE

The value of tmnxOamPingCtlServiceId specifies the service ID of the service being tested. The applicability of tmnxOamPingCtlServiceId varies with the test type, as shown in the following table. tmnxOamPingCtlTestMode Applicability Related Virtual Router Object ---------------------- ------------- ----------------------------- 'cpePing' mandatory none 'icmpPing' optional tmnxOamPingCtlVRtrID 'macPing' mandatory none 'macPopulate' mandatory none 'macPurge' mandatory none 'mfibPing' mandatory none 'mrInfo' optional tmnxOamPingCtlVRtrID 'p2mpLspPing' optional tmnxOamPingCtlVRtrID 'svcPing' mandatory none 'vprnPing' mandatory none 'vxlanPing' mandatory none otherwise not applicable none When tmnxOamPingCtlServiceId is mandatory, a non-zero value must be provided. When tmnxOamPingCtlServiceId is optional, it is used to specify a VPRN service. The test must use the VPRN service's virtual router. When a related virtual router object is shown, the interaction is described in the DESCRIPTION clause of the listed object. When tmnxOamPingCtlTestMode is 'icmpPing', tmnxOamPingCtlRouterInstanceName is the preferred object for specifying the service to be tested. Service IDs larger than 2147483647 are internal, so they are excluded from the range. The default value is the null service ID.

OBJECT-TYPE

When the value of tmnxOamPingCtlLocalSdp is 'true', the 'svcPing' test determines an egress SDP-ID that is bound to the service that has the far-end IP address specified in tmnxOamPingCtlTgtAddress assigned to it. The far-end address of the specified SDP-ID is the expected responder-id within the OAM Echo reply message. The SDP-ID defines the encapsulation of the SDP tunnel encapsulation used to reach the far-end. This can be IP/GRE or MPLS. On the originator egress, the Service-ID must have an associated VC-Label to reach the far-end address of the SDP-ID and the SDP-ID must be operational for the message to be sent. This object is optional and valid only when tmnxOamPingCtlTestMode is equal to 'svcPing'.

OBJECT-TYPE

The value of tmnxOamPingCtlRemoteSdp specifies the encapsulation of the ping reply to be sent by the far end node. When tmnxOamPingCtlRemoteSdp is 'false', the far-end node sends the reply using the generic IP/GRE OAM encapsulation. When tmnxOamPingCtlRemoteSdp is 'true', the far-end node sends the reply using the same service tunnel encapsulation labeling used for the associated service traffic. If that labeling cannot be found, the generic IP/GRE OAM encapsulation is used. This object is optional and is applicable only when tmnxOamPingCtlTestMode is equal to 'svcPing'.

OBJECT-TYPE

The value of tmnxOamPingCtlSize specifies (directly or indirectly) the size of the OAM echo request PDU. The supported ranges, etc, for each test type are specified in the following table. tmnxOamPingCtlTestMode Minimum Maximum Default Auto Adjust ---------------------- ------- ------- ------- ----------- 'ethCfmLoopback' 0 1500 0 No 'ethCfmTwoWaySlm' 0 1500 0 No 'icmpPing' 0 16384 56 No 'lspPing' 1 9786 1 Yes 'macPing' 1 9786 72 Yes 'mfibPing' 1 9786 72 Yes 'p2mpLspPing' 1 9786 1 Yes 'sdpPing' 72 9786 72 Yes 'vccvPing' 1 9786 1 Yes 'vprnPing' 1 9786 72 Yes 'vxlanPing' 0 2000 0 No otherwise tmnxOamPingCtlSize is not significant For a test type supporting Auto Adjust, if the tmnxOamPingCtlSize value is too small, SROS automatically chooses the next highest supported PDU size. For example, if tmnxOamPingCtlSize is 1 when a 'vccvPing' test is started on a FEC 128 pseudowire, an 88 octet echo request PDU is sent. For a test type which does not support Auto Adjust, the tmnxOamPingCtlSize value must lead to a valid echo request PDU size. When tmnxOamPingCtlTestMode has the value 'ethCfmLoopback' or 'ethCfmTwoWaySlm', tmnxOamPingCtlSize specifies the number of octets in the Value field of the Data TLV of the applicable Y.1731 PDU. If zero is specified, the packet has no Data TLV. When tmnxOamPingCtlTestMode has the value 'icmpPing', tmnxOamPingCtlSize specifies the payload size following the ICMP header. When tmnxOamPingCtlTestMode has the value 'vxlanPing', tmnxOamPingCtlSize specifies the total size of the Pad TLV added to the launched VXLAN ping request. tmnxOamPingCtlSize = 0 indicates no Pad TLV is added. The smallest Pad TLV is five bytes, so values in the range 1..4 are rejected. IPv4 echo requests sent for an 'icmpPing' test can optionally be fragmented (see tmnxOamIcmpPingCtlDoNotFragment). For all the other ping test types, echo requests are launched without fragmentation.

OBJECT-TYPE

The value of tmnxOamPingCtlTimeOut specifies the timeout value, in seconds, to be used during a test run. Timers (with duration configured using the tmnxOamPingCtlTimeOut value) are used in one of two ways during a test run. 1. Per Probe: a timer is started each time a probe is sent. If the timer expires before the probe response arrives, the probe is declared failed. This is the traditional timeout method for a sequence of probes. OR 2. Per Test: a timer is started once per test run, when the last probe of the test run is sent. ANY probe which does not have a response when the timer expires is declared failed. SROS chooses 'Per Probe' or 'Per Test' based on the tmnxOamPingCtlTestMode value. The choice is not configurable. The accepted minimum, maximum, and default values for tmnxOamPingCtlTimeOut depend on tmnxOamPingCtlTestMode, as shown in the following table. The table also shows the timer usage for the test mode. tmnxOamPingCtlTestMode Min Max Def Timer Usage ---------------------- --- --- --- ----------- 'atmPing' 1 10 5 Per Probe 'bierPing' 1 120 10 Per Probe 'dnsPing' 1 120 5 Per Probe 'ethCfmLoopback' 1 10 5 Per Probe 'ethCfmTwoWayDelay' 1 10 5 Per Test 'ethCfmTwoWaySlm' 1 10 5 Per Test 'gtpPing' 1 10 5 Per Probe 'icmpPing' 1 10 5 Per Test 'lspPing' 1 10 5 Per Probe 'macPing' 1 10 5 Per Probe 'mfibPing' 1 100 5 Per Probe 'mtuPing' 1 10 5 Per Probe 'p2mpLspPing' 1 120 10 Per Probe 'sdpPing' 1 10 5 Per Probe 'vccvPing' 1 10 5 Per Probe 'vprnPing' 1 100 5 Per Probe 'vxlanPing' 1 10 5 Per Probe otherwise ......... the value of tmnxOamPingCtlTimeOut is irrelevant

OBJECT-TYPE

The value of tmnxOamPingCtlProbeCount specifies the number of probes to send during the test. The relevance, range, and default for tmnxOamPingCtlProbeCount depends on tmnxOamPingCtlTestMode, as follows. tmnxOamPingCtlTestMode Relevant? Min Max Default ---------------------- --------- --- --- ------- 'ancpLoopback' Yes 1 32 1 'atmPing' Yes 1 100 1 'cpePing' Yes 1 100 1 'dnsPing' Yes 1 100 1 'ethCfmLoopback' Yes 1 100 1 'ethCfmTwoWayDelay' Yes 1 1000 1 'ethCfmTwoWaySlm' Yes 1 1000 1 'gtpPing' Yes 1 100 1 'icmpPing' Yes 1 100000 5 'lspPing' Yes 1 100 1 'macPing' Yes 1 100 1 'mfibPing' Yes 1 100 1 'sdpPing' Yes 1 100 1 'vccvPing' Yes 1 100 1 'vprnPing' Yes 1 100 1 'vxlanPing' Yes 1 1024 1 otherwise No N/A N/A N/A

OBJECT-TYPE

The value of tmnxOamPingCtlInterval specifies the time to wait between the transmission of one OAM Echo request and the next. The UNITS are specified by tmnxOamPingCtlIntervalUnits. For example, if tmnxOamPingCtlInterval has the value 1, and tmnxOamPingCtlIntervalUnits has the value 'centiseconds(2)', the interval between OAM Echo requests is 0.01 seconds. The applicability, range, and default value of the interval specified using the tmnxOamPingCtlInterval and tmnxOamPingCtlIntervalUnits pair vary with tmnxOamPingCtlTestMode and tmnxOamIcmpPingCtlRapid, as shown in the following table. tmnxOamPingCtlTestMode Supported Values (sec) Default (sec) ------------------------ ------------------------------ ------------- 'bierPing' not applicable 'ethCfmLoopback' 1, 2, .. 10 5 'ethCfmTwoWayDelay' 0.1, 0.2, .. 0.9; 1, 2, .. 10 5 'ethCfmTwoWaySlm' 0.1, 0.2, .. 0.9; 1, 2, .. 10 5 'gtpPing' 1, 2, .. 10 5 'icmpPing' with RAPID 0.01, 0.02, .. 100.00 0.01 'icmpPing' without RAPID 1, 2, .. 10000 1 'p2mpLspPing' not applicable 'vxlanPing' 0.1; 1, 2, .. 10 1 otherwise 1, 2, .. 10 1

OBJECT-TYPE

The maximum number of entries allowed in the tmnxOamPingHistoryTable for this OAM ping test. The agent will remove the oldest entry in the tmnxOamPingHistoryTable to allow the addition of an new entry once the number of rows in the tmnxOamPingHistoryTable reaches this value. Old entries are not removed when a new test is started. Entries are added to the tmnxOamPingHistoryTable until tmnxOamPingCtlMaxRows is reached before entries begin to be removed. 'p2mpLspPing' uses a default value of 400, which is the maximum number of leaves per P2MP LSP tree. A value of 0 for this object disables creation of tmnxOamPingHistoryTable entries. This object was obsoleted in release 6.0R17.

OBJECT-TYPE

The value of tmnxOamPingCtlTrapGeneration specifies the notification(s) to send for a test run. Each bit enables the transmission of one notification, as follows. 'probeFailure(0)': send one tmnxOamPingProbeFailedV3 notification if at least M successive probes failed during the test run. M is configured using tmnxOamPingCtlTrapProbeFailureFilter. 'testFailure(1)': send one tmnxOamPingTestFailedV3 notification if at least N probes failed during the test run. N is configured using tmnxOamPingCtlTrapTestFailureFilter. 'testCompletion(2)': send one tmnxOamPingTestCompletedV3 notification when the test run is complete.

OBJECT-TYPE

The value of tmnxOamPingCtlTrapProbeFailureFilter specifies the threshold for generating a tmnxOamPingProbeFailedV3 notification. The semantics are explained in the tmnxOamPingProbeFailedV3 DESCRIPTION clause. Setting this object to zero is not recommended - results will vary with the test type.

OBJECT-TYPE

The value of tmnxOamPingCtlTrapTestFailureFilter specifies the threshold for generating a tmnxOamPingTestFailedV3 notification. The semantics are explained in the tmnxOamPingTestFailedV3 DESCRIPTION clause. Setting this object to zero is not recommended.

OBJECT-TYPE

The value of tmnxOamPingCtlSAA specifies if this test is an SAA test (Service Assurance Agent; 'true'), or an OAM test ('false'). If there is a tmnxOamSaaCtlTable row with the specified index values, 'true' is returned. Otherwise, 'false' is returned.

OBJECT-TYPE

The value of tmnxOamPingCtlRuns indicates the number of times this OAM ping test has been executed.

OBJECT-TYPE

The value of tmnxOamPingCtlFailures indicates the number of times this OAM ping test has failed.

OBJECT-TYPE

The value of tmnxOamPingCtlLastRunResult indicates the completion status the last time this test was executed. If this OAM test is currently in progress, this object indicates the result of the previous test run, if any.

OBJECT-TYPE

The value of tmnxOamPingCtlLastChanged indicates the time the value of a settable object in this row was last changed.

OBJECT-TYPE

The value of tmnxOamPingCtlVRtrID specifies the virtual router to be used for the test. Zero indicates no virtual router is specified. A non-zero value must be the index of an active row in TIMETRA-VRTR-MIB::vRtrConfTable (i.e. tmnxOamPingCtlVRtrID must match a valid TIMETRA-VRTR-MIB::vRtrID value). This object is applicable if tmnxOamPingCtlTestMode is 'icmpPing', 'gtpPing', 'mrInfo', or 'p2mpLspPing'. The table below shows the supported combinations of system-configured virtual routers and test types. Supported for Supported for Supported for tmnxOamPingCtlTestMode Base ? management ? vpls-management ? ---------------------- ------------- ------------- ----------------- 'icmpPing' Yes Yes Yes 'gtpPing' Yes Yes Yes 'mrInfo' Yes No No 'p2mpLspPing' Yes No No When directing an 'icmpPing' test to use a virtual router, the preferred object is tmnxOamPingCtlRouterInstanceName. When directing an 'mrInfo' or 'p2mpLspPing' test to use a virtual router associated with a VPRN service, the virtual router can be specified using tmnxOamPingCtlVRtrID (with the VPRN's virtual router number) or tmnxOamPingCtlServiceId (with the VPRN's service number). tmnxOamPingCtlServiceId is preferred, because service numbers are constant across an SROS reboot (while virtual routers may be renumbered). If non-default values are specified for both tmnxOamPingCtlVRtrID and tmnxOamPingCtlServiceId, tmnxOamPingCtlServiceId is used.

OBJECT-TYPE

The value of tmnxOamPingCtlTgtAddrType specifies the address type of tmnxOamPingCtlTgtAddress. The values which can be used as part of a successful test depend on tmnxOamPingCtlTestMode, as follows. Test Mode tmnxOamPingCtlTgtAddrType Values Supported ----------- ----------------------------------------------------- 'cpePing' 'ipv4(1)' 'dnsPing' 'ipv4(1)' 'ipv6(2)' 'gtpPing' 'ipv4(1)' 'icmpPing' 'ipv4(1)' 'ipv6(2)' 'ipv6z(4)' 'dns(16)' 'mfibPing' 'ipv4(1)' 'ipv6(2)' 'mrInfo' 'ipv4(1)' 'dns(16)' 'svcPing' 'ipv4(1)' 'vccvPing' 'unknown(0)' 'ipv4(1)' 'vprnPing' 'ipv4(1)' 'ipv6(2)' 'vxlanPing' 'ipv4(1)' otherwise 'unknown(0)'

OBJECT-TYPE

The value of tmnxOamPingCtlTgtAddress specifies the destination host address to be used when performing an OAM ping operation. The corresponding address type is configured using tmnxOamPingCtlTgtAddrType. For 'dnsPing' this is the address of the DNS server host that will be asked to resolve the DNS name specified by tmnxOamPingCtlDnsName.

OBJECT-TYPE

The value of tmnxOamPingCtlSrcAddrType specifies the address type of tmnxOamPingCtlSrcAddress. Only 'ipv4' and 'ipv6' address types are supported.

OBJECT-TYPE

The value of tmnxOamPingCtlSrcAddress specifies the source IP host address to be used when performing an OAM ping operation. The corresponding address type is configured using tmnxOamPingCtlSrcAddrType. This is an optional parameter. It is used when tmnxOamPingCtlTestMode is 'icmpPing', 'dnsPing', 'lspPing', 'p2mpLspPing' (LDP), or 'vccvPing'.

OBJECT-TYPE

The value of tmnxOamPingCtlDnsName specifies the DNS name to be resolved to an IP address. This object is required for 'dnsPing'.

OBJECT-TYPE

The value of tmnxOamPingCtlDNSRecord specifies which DNS record is to be retrieved in this test.

OBJECT-TYPE

The value of tmnxOamPingCtlIntervalUnits specifies the units for tmnxOamPingCtlInterval. For example, if tmnxOamPingCtlIntervalUnits has the value 'centiseconds(2)', and tmnxOamPingCtlInterval has the value 10, the test's interval is 0.1 seconds. The supported combinations of tmnxOamPingCtlIntervalUnits, tmnxOamPingCtlInterval, tmnxOamPingCtlTestMode, and tmnxOamIcmpPingCtlRapid are specified in the tmnxOamPingCtlInterval DESCRIPTION clause. The interaction between this object and tmnxOamIcmpPingCtlRapid is specified in the tmnxOamIcmpPingCtlRapid DESCRIPTION clause.

OBJECT-TYPE

The value of tmnxOamPingCtlSubscriberName specifies the name of the subscriber to be pinged. When a non-default value for this object is specified, a Layer-2-Aware Network Address Translation (NAT) ping is requested. The subscriber name and the target IP address (i.e. tmnxOamPingCtlTgtAddress) are used together to ping the subscriber's device. A valid Layer-2-Aware NAT ping must satisfy all of the following conditions. 1. tmnxOamPingCtlSubscriberName is a valid subscriber name. 2. The test type (i.e. tmnxOamPingCtlTestMode) is 'icmpPing'. 3. The test is not an SAA test (as configured using tmnxOamSaaCtlRowStatus). 4. The target address type (as configured using tmnxOamPingCtlTgtAddrType) is 'ipv4(1)'. 5. The value of each of the following objects is default: tmnxOamIcmpPingCtlBypassRouting, tmnxOamIcmpPingCtlEgrIfIndex, tmnxOamIcmpPingCtlEgrIfName, tmnxOamIcmpPingCtlNhAddrType, tmnxOamIcmpPingCtlRapid.

OBJECT-TYPE

The value of tmnxOamPingCtlRouterInstanceName specifies the name of the service or router instance to be used by an 'icmpPing' test. The following values are supported: 1. '' (i.e. the empty string), 2. 'Base', 3. 'management', 4. 'vpls-management', 5. A VPRN service name (i.e. a TIMETRA-SERV-MIB::svcName, with TIMETRA-SERV-MIB::svcType = 'vprn(4)'). 6. A CPM virtual router name (i.e. a user-configured router name, with TIMETRA-VRTR-MIB::vRtrType = 'vr(3)'). Names other than the names listed above are accepted, but will not lead to a successful test. The service or virtual router to be used by an 'icmpPing' test can be specified using tmnxOamPingCtlVRtrID, tmnxOamPingCtlServiceId, and/or tmnxOamPingCtlRouterInstanceName. The following two combinations of the three objects are supported: 1. tmnxOamPingCtlVRtrID = 0, tmnxOamPingCtlServiceId = 0, tmnxOamPingCtlRouterInstanceName != ''. This is the preferred approach. 2. One or both of tmnxOamPingCtlVRtrID and tmnxOamPingCtlServiceId has a non-zero value, tmnxOamPingCtlRouterInstanceName = ''. An attempt to change TIMETRA-SYSTEM-MIB::tmnxSysMgmtIfWriteMode.0 away from 'classic(1)' is blocked if any tmnxOamPingCtlRouterInstanceName is empty for an 'icmpPing' test. When TIMETRA-SYSTEM-MIB::tmnxSysMgmtIfWriteMode.0 is not 'classic(1)', each 'icmpPing' test must continue to have a non-empty tmnxOamPingCtlRouterInstanceName.

OBJECT-TYPE

tmnxOamPingResultsTable contains the run-level test results for OAM ping tests. Probe-level test results for ping tests reside in tmnxOamPingHistoryTable. Some test types (e.g. 'macPing(5)') have dedicated tables (e.g. tmnxOamMacPingHistoryTable) to hold test results specific to the test type.

OBJECT-TYPE

tmnxOamPingResultsEntry contains the run-level test results for one OAM ping test run. A row is created when a ping test is enabled (using tmnxOamPingCtlAdminStatus). A row is destroyed when: 1. The corresponding test configuration is destroyed (using tmnxOamPingCtlRowStatus), or 2. A new run result is available, and the limit on the number of run results retained (3, currently) has been reached. In that case, the oldest run result row is destroyed.

OBJECT-TYPE

The value of tmnxOamPingResultsOperStatus indicates the operational state of the specified test run. 'enabled(1)' indicates the test is running.

OBJECT-TYPE

The value of tmnxOamPingResultsMinRtt indicates the minimum round trip time for the specified test run. Zero is returned when the information is not available.

OBJECT-TYPE

The value of tmnxOamPingResultsMaxRtt indicates the maximum round trip time for the specified test run. Zero is returned when the information is not available.

OBJECT-TYPE

The value of tmnxOamPingResultsAverageRtt indicates the average round trip time for the specified test run. Zero is returned when the information is not available.

OBJECT-TYPE

The value of tmnxOamPingResultsRttSumOfSquares indicates the least significant 32 bits of tmnxOamPingResultsRttHCSumSquares.

OBJECT-TYPE

This object contains the largest size OAM Echo request message that received a valid reply. The value of this object MUST be reported as 0 when no ping responses have been received or an active test has not yet timed out. When tmnxOamPingCtlTestMode does not have a value of 'mtuPing', this object is not relevant and should contain a value of 0.

OBJECT-TYPE

The value of tmnxOamPingResultsSvcPing indicates the status of the specified test run. When the value is read using an SNMP Get: 1. If the test type is 'svcPing', the status of the test run is returned. 2. If the test type is not 'svcPing', 'undetermined(0)' is returned. When the value is reported in a notification, the status of the test run is reported (for any ping test type).

OBJECT-TYPE

The value of tmnxOamPingResultsProbeResponses indicates the number of responses received for the specified test run.

OBJECT-TYPE

The value of tmnxOamPingResultsSentProbes indicates the number of probes sent for the specified test run.

OBJECT-TYPE

The value of tmnxOamPingResultsLastGoodProbe indicates the date and time when the most recent response was received for the specified test run. 1970-Jan-01 00:00:00 UTC is returned if a response has not been received.

OBJECT-TYPE

A copy of the OAM header of the last response packet received for this OAM ping test. The value of this object MUST be reported as 0 when no probes have been sent. This object was obsoleted in release 8.0R1 and replaced with tmnxOamPingHistoryRespHdr in tmnxOamPingHistoryTable.

OBJECT-TYPE

The value of tmnxOamPingResultsMinTt indicates the minimum outbound trip time for the specified test run. The value is valid if the two nodes have proper clock synchronization. Otherwise, for example, a negative value can be returned. Zero is returned when the information is not available.

OBJECT-TYPE

The value of tmnxOamPingResultsMaxTt indicates the maximum outbound trip time for the specified test run. The value is valid if the two nodes have proper clock synchronization. Otherwise, for example, a negative value can be returned. Zero is returned when the information is not available.

OBJECT-TYPE

The value of tmnxOamPingResultsAverageTt indicates the average outbound trip time for the specified test run. The value is valid if the two nodes have proper clock synchronization. Otherwise, for example, a negative value can be returned. Zero is returned when the information is not available.

OBJECT-TYPE

The value of tmnxOamPingResultsTtSumOfSquares indicates the least significant 32 bits of tmnxOamPingResultsTtHCSumSquares.

OBJECT-TYPE

The value of tmnxOamPingResultsMinInTt indicates the minimum inbound trip time for the specified test run. The value is valid if the two nodes have proper clock synchronization. Otherwise, for example, a negative value can be returned. Zero is returned when the information is not available.

OBJECT-TYPE

The value of tmnxOamPingResultsMaxInTt indicates the maximum inbound trip time for the specified test run. The value is valid if the two nodes have proper clock synchronization. Otherwise, for example, a negative value can be returned. Zero is returned when the information is not available.

OBJECT-TYPE

The value of tmnxOamPingResultsAverageInTt indicates the average inbound trip time for the specified test run. The value is valid if the two nodes have proper clock synchronization. Otherwise, for example, a negative value can be returned. Zero is returned when the information is not available.

OBJECT-TYPE

The value of tmnxOamPingResultsInTtSumOfSqrs indicates the least significant 32 bits of tmnxOamPingResultsInTtHCSumSqrs.

OBJECT-TYPE

The value of tmnxOamPingResultsOutJitter indicates the amount of jitter in the outbound trip times for the specified test run. Zero is returned when the information is not available.

OBJECT-TYPE

The value of tmnxOamPingResultsInJitter indicates the amount of jitter in the inbound trip times for the specified test run. Zero is returned when the information is not available.

OBJECT-TYPE

The value of tmnxOamPingResultsRtJitter indicates the amount of jitter in the round trip times for the specified test run. Zero is returned when the information is not available.

OBJECT-TYPE

The value of tmnxOamPingResultsProbeTimeouts indicates the number of probes that timed out for the specified test run.

OBJECT-TYPE

The value of tmnxOamPingResultsProbeFailures indicates the total number of probes that failed to be transmitted plus the number of probes that timed out.

OBJECT-TYPE

The value of tmnxOamPingResultsTestRunIndex specifies the test run INDEX of the row. The first run of a test is assigned run index 1. The second run of a test is assigned run index 2. Etc.

OBJECT-TYPE

The value of tmnxOamPingResultsRttOFSumSquares indicates the number of times tmnxOamPingResultsRttSumOfSquares overflowed.

OBJECT-TYPE

The value of tmnxOamPingResultsRttHCSumSquares indicates the sum of squares of the round trip times for the specified test run. Its purpose is to enable the standard deviation calculation. Zero is returned when the information is not available.

OBJECT-TYPE

The value of tmnxOamPingResultsTtOFSumSquares indicates the number of times tmnxOamPingResultsTtSumOfSquares overflowed.

OBJECT-TYPE

The value of tmnxOamPingResultsTtHCSumSquares indicates the sum of squares of the outbound trip times for the specified test run. Its purpose is to enable the standard deviation calculation. Zero is returned when the information is not available.

OBJECT-TYPE

The value of tmnxOamPingResultsInTtOFSumSqrs indicates the number of times tmnxOamPingResultsInTtSumOfSqrs overflowed.

OBJECT-TYPE

The value of tmnxOamPingResultsInTtHCSumSqrs indicates the sum of squares of the inbound trip times for the specified test run. Its purpose is to enable the standard deviation calculation. Zero is returned when the information is not available.

OBJECT-TYPE

The value of tmnxOamPingResultsTestRunResult indicates the result of the specified test run.

OBJECT-TYPE

The value of tmnxOamPingResultsOutOfOrder indicates the number of reply PDUs for the specified test run that have arrived out of order. For example, if two probes are sent during the test run (as configured using tmnxOamPingCtlProbeCount), and the two reply PDUs arrive out of order, tmnxOamPingResultsOutOfOrder is 2. This value is supported when tmnxOamPingCtlTestMode is 'vxlanPing'. Zero is returned for all other test types.

OBJECT-TYPE

tmnxOamPingHistoryTable contains the per-probe results for all ping test types (except 'macPing'). tmnxOamMacPingHistoryTable contains the 'macPing' results.

OBJECT-TYPE

tmnxOamPingHistoryEntry contains the results for one ping probe. The first three indices specify the corresponding tmnxOamPingResultsTable row. The fourth index specifies the probe yielding the results. A row is created when one of the following events occurs. 1. A ping echo request cannot be sent (e.g. the destination IP address is unknown). 2. A ping echo reply (triggered by a ping echo request launched by this node) arrives. 3. A timeout occurs while waiting for a ping echo reply. Rows are destroyed when the corresponding tmnxOamPingResultsTable row is destroyed.

OBJECT-TYPE

The value of tmnxOamPingHistoryIndex specifies the probe which yielded the results in this row. For example: 1. For a unicast ping test with a send-count of 10, the row with tmnxOamPingHistoryIndex=10 has the result of the last probe to be sent. 2. For a multicast ping test with 10 destinations, the row with tmnxOamPingHistoryIndex=10 has the result for the last destination to be pinged.

OBJECT-TYPE

The value of tmnxOamPingHistoryResponse indicates the round trip time for the specified probe. Zero is returned when the information is not available (e.g. the probe timed out).

OBJECT-TYPE

The value of tmnxOamPingHistoryOneWayTime indicates the outbound trip time for the specified probe. The value is valid if the two nodes have proper clock synchronization. Otherwise, for example, a negative value can be returned. Zero is returned when the information is not available.

OBJECT-TYPE

The value of tmnxOamPingHistorySize indicates the size of the OAM echo request transmitted for this OAM probe. Zero is returned if no probe was transmitted. When tmnxOamPingCtlTestMode is 'ethCfmLoopback', 'ethCfmTwoWayDelay', or 'ethCfmTwoWaySlm' the value returned is the size of the transmitted layer 2 frame (including the layer 2 header, but excluding the IEEE 802.1Q Tag field(s)). For other tmnxOamPingCtlTestMode values, the size returned is the tmnxOamPingCtlSize value.

OBJECT-TYPE

The value of tmnxOamPingHistoryStatus indicates the outcome of the probe. Example values: 'responseReceived', 'requestTimedOut'.

OBJECT-TYPE

The value of tmnxOamPingHistoryTime indicates the date and time when the outcome of the specified probe was determined.

OBJECT-TYPE

The value of tmnxOamPingHistoryReturnCode indicates the OAM return code received in the probe response. For a 'bierPing' test, 'notApplicable(0)' is returned. The probe's return code can be read using tmnxOamBierPingHistoryReturnCode.

OBJECT-TYPE

This object was obsoleted in release 4.0 and replaced with InetAddress objects tmnxOamPingHistorySrcAddrType and tmnxOamPingHistorySrcAddress.

OBJECT-TYPE

The value of tmnxOamPingHistAddressType indicates the type of binding address information returned in response to the specified probe. 'unknown(0)' is returned when the information is not available.

OBJECT-TYPE

The value of tmnxOamPingHistSapId is the name of the access port of the SAP supporting the requests returned in response to a 'vprnPing', 'mfibPing' or 'cpePing' probe. If the value of tmnxOamPingHistAddressType is not 'sapId', this object is not relevant and MUST have a null string ''.

OBJECT-TYPE

The value of tmnxOamPingHistoryVersion indicates the protocol version for this OAM ping probe reply.

OBJECT-TYPE

tmnxOamPingHistoryCpeMacAddr is set to 0 except in case of a 'cpePing', where it contains the MAC address of the replying CPE for this OAM ping probe reply.

OBJECT-TYPE

The value tmnxOamPingHistoryRespSvcId indicates for an 'mfibPing' the service id to which the SAP responding to the 'mfibPing' probe belongs. If the indicated SAP is part of the same service originating the probe, this value is set to 0. For other types of probes, this value is insignificant and is also set to 0.

OBJECT-TYPE

The value tmnxOamPingHistorySequence indicates this probe's sequence number. If a probe response was received, this object indicates the sequence number of the response.

OBJECT-TYPE

The value of tmnxOamPingHistoryIfIndex indicates the ifIndex of the interface that this probe was transmitted from. Zero is returned when the information is not available.

OBJECT-TYPE

The value of tmnxOamPingHistoryDataLen indicates for an 'lspPing' the UDP data length of the echo reply, and for 'icmpPing' normally the length starting after the IP header of the echo reply. For 'ethCfmLoopback' and 'ethCfmTwoWaySlm' the value is the number of octets in the Value field of the Data TLV of the Ethernet CFM loopback packet (zero if the packet has no Data TLV). For other types of probes, this value is not significant and is set to 0.

OBJECT-TYPE

The value of tmnxOamPingHistoryRespPlane indicates the response plane from which this ping response was received.

OBJECT-TYPE

The value of tmnxOamPingHistoryReqHdr is a copy of the OAM header of the request packet sent for this OAM ping test probe. The request header is reported only when tmnxOamPingCtlTestMode has a value of 'svcPing', 'sdpPing' 'mtuPing', 'ethCfmLoopback', 'ethCfmTwoWayDelay', or 'ethCfmTwoWaySlm'. Otherwise, a zero length OCTET STRING is returned. This object was marked obsolete in SROS release 10.0 R1.

OBJECT-TYPE

The value of tmnxOamPingHistoryRespHdr is a copy of the OAM header of the response packet received for this OAM ping test probe. The response header is reported only when tmnxOamPingCtlTestMode has a value of 'svcPing', 'sdpPing', 'mtuPing', 'icmpPing', 'ethCfmLoopback', 'ethCfmTwoWayDelay', or 'ethCfmTwoWaySlm'. Otherwise, a zero length OCTET STRING is returned. For 'icmpPing' the value reported is the received ICMP message starting from the IP header. The value of this object MUST be reported as a zero length OCTET STRING when no probe response has been received.

OBJECT-TYPE

The value of tmnxOamPingHistoryDnsAddrType indicates the Internet address type stored in tmnxOamPingHistoryDnsAddress. If this was not a 'dnsPing' test or the DNS name specified in tmnxOamPingCtlDnsName could not be resolved, the value of this object will be reported as 'unknown(0)'.

OBJECT-TYPE

The value of tmnxOamPingHistoryDnsAddress indicates the Internet address that was resolved from the name specified in tmnxOamPingCtlDnsName by a 'dnsPing' test. If this was not a 'dnsPing' test or the dns name specified in tmnxOamPingCtlDnsName could not be resolved, the value of this object will be reported as ''H (empty string).

OBJECT-TYPE

The value of tmnxOamPingHistorySrcAddrType indicates the Internet address type of the address stored in tmnxOamPingHistorySrcAddress.

OBJECT-TYPE

The value of tmnxOamPingHistorySrcAddress indicates the Internet address of the remote node targeted by the specified ping probe. In the case of a 'bierPing' test, the remote node's address can be read using tmnxOamBierPingHistoryBfrPfx.

OBJECT-TYPE

The value of tmnxOamPingHistoryInOneWayTime indicates the inbound trip time for the specified probe response. Zero is returned when the information is not available.

OBJECT-TYPE

The value of tmnxOamPingHistoryLspName indicates the name of the LSP that this probe was transmitted on. The empty string is returned when the test mode is not 'vccvPing'. The empty string is returned when the transport tunnel is not RSVP.

OBJECT-TYPE

The value of tmnxOamPingHistNextHopAddrType indicates the Internet address type of the address stored in tmnxOamPingHistNextHopAddress. The value 'unknown(0)' is returned when the test mode is not 'vccvPing'.

OBJECT-TYPE

The value of tmnxOamPingHistNextHopAddress indicates the next hop Internet address that this probe was transmitted to. The empty string is returned when the test mode is not 'vccvPing'.

OBJECT-TYPE

The value of tmnxOamPingHistorySrcGlobalId indicates the source MPLS-TP global identifier of the replying node. The value is copied from the reply's RFC 6426 Source Identifier TLV. If the TLV is absent, zero is returned. This value is relevant when tmnxOamPingCtlTestMode is 'lspPing' or 'vccvPing'. Otherwise, zero is returned.

OBJECT-TYPE

The value of tmnxOamPingHistorySrcNodeId indicates the source MPLS-TP node identifier of the replying node. The value is copied from the reply's RFC 6426 Source Identifier TLV. If the TLV is absent, zero is returned. This value is relevant when tmnxOamPingCtlTestMode is 'lspPing' or 'vccvPing'. Otherwise, zero is returned.

OBJECT-TYPE

The value of tmnxOamPingHistorySdpBindId indicates the SDP binding provided by the remote system. The value of tmnxOamPingHistorySdpBindId is relevant when tmnxOamPingHistAddressType is 'sdpBindId(9)'.

OBJECT-TYPE

The value of tmnxOamPingHistoryRtrnSubcode indicates the value present in an MPLS echo reply's RFC 4379 Return Subcode (RSC) field. A valid value is returned when the test has a tmnxOamPingCtlTestMode value of 'lspPing'. Otherwise, zero is returned.

OBJECT-TYPE

The value of tmnxOamPingHistoryNetworkIfName indicates the network interface name provided by the replying node. Network interface names are configured using TIMETRA-VRTR-MIB::vRtrIfName. The value of this object is the empty string when the value of tmnxOamPingHistAddressType is not 'networkInterface(11)'.

OBJECT-TYPE

Defines the Nokia SROS OAM MAC Ping Control Table for providing, via SNMP, the capability of performing Nokia SROS OAM 'macPing', 'macPopulate', or 'macPurge' test operations. The results of these tests are stored in the tmnxOamPingResultsTable and the tmnxOamMacPingHistoryTable. There will be no entries for these test in the tmnxOamPingHistoryTable.

OBJECT-TYPE

Defines an entry in the tmnxOamMacPingCtlTable. The first index element, tmnxOamPingCtlOwnerIndex, is of type SnmpAdminString, a textual convention that allows for use of the SNMPv3 View-Based Access Control Model (RFC 2575 [11], VACM) and allows a management application to identify its entries. The second index, tmnxOamPingCtlTestIndex, enables the same management application to have multiple outstanding requests.

OBJECT-TYPE

The value of tmnxOamMacPingCtlTargetMacAddr is a 6-octet value that specifies the target MAC address to be used in the query request for performing an OAM ping operation. This parameter is required.

OBJECT-TYPE

The value of tmnxOamMacPingCtlSourceMacAddr is a 6-octet value that specifies the MAC address to be used as the source in the query request for performing an OAM ping operation. This object is optional and is not relevant when tmnxOamPingCtlTestMode has a value other than 'macPing'.

OBJECT-TYPE

The value of tmnxOamMacPingCtlSendControl specifies whether the outbound OAM ping packet will use the data plane or the control plane. When the value is 'false', the packet is sent using the data plane. As of SROS release 13.0 R1, a test cannot be started if tmnxOamMacPingCtlSendControl is 'true'. A test is started using tmnxOamPingCtlAdminStatus. This object will be marked obsolete in a future release.

OBJECT-TYPE

When the value of tmnxOamMacPingCtlReplyControl is 'true', the OAM ping response is returned using the control plane. If its value is 'false', the packet is sent via the data plane. This object is optional and is not relevant when tmnxOamPingCtlTestMode has a value other than 'macPing'.

OBJECT-TYPE

Specifies the vc-label time-to-live value. This object is optional and is not relevant when tmnxOamPingCtlTestMode has a value other than 'macPing'. While performing the test with a TTL of 1 no responses should ever be expected.

OBJECT-TYPE

When the value of tmnxOamMacPingCtlRegister is 'true', the OAM ping request is transmitted that causes each upstream node to delete the MAC address only from its forwarding plane but keep it in its control plane in order to inhibit dynamic learning. If its value is 'false', the MAC address is deleted from both the forwarding and control planes. This object is optional and is not relevant when tmnxOamPingCtlTestMode has a value other than 'macPurge'.

OBJECT-TYPE

When the value of tmnxOamMacPingCtlFlood is 'true', the OAM ping request is transmitted that causes each upstream node to add or delete the MAC address. If its value is 'false', the operation is performed locally. This object is optional and is not relevant when tmnxOamPingCtlTestMode has a value other than 'macPopulate' or 'macPurge'.

OBJECT-TYPE

The value of tmnxOamMacPingCtlForce specifies whether or not to add an override to the test. When tmnxOamPingCtlTestMode is 'macPopulate' and tmnxOamMacPingCtlForce is 'true', the MAC type (i.e. TIMETRA-SERV-MIB::tlsFdbType) of the FIB entry specified by the test parameters is set to 'oam', regardless of its earlier value. When tmnxOamPingCtlTestMode is 'macPurge' and tmnxOamMacPingCtlForce is 'true', the FIB entry specified by the test parameters is purged, even if the requesting node did not populate the entry. When tmnxOamPingCtlTestMode is 'macPing', tmnxOamMacPingCtlForce is irrelevant.

OBJECT-TYPE

The value of tmnxOamMacPingCtlAge specifies the number of seconds to age this OAM MAC address in the FIB. This object is optional and is not relevant when tmnxOamPingCtlTestMode has a value other than 'macPopulate'.

OBJECT-TYPE

The value of tmnxOamMacPingCtlSapPortId is the ID of the access port of the target SAP. This object is optional and is not relevant when tmnxOamPingCtlTestMode has a value other than 'macPopulate'.

OBJECT-TYPE

The value of tmnxOamMacPingCtlSapEncapValue is the label used to identify the target SAP on the port specified in tmnxOamMacPingCtlSapPortId. This object is optional and is not relevant when tmnxOamPingCtlTestMode has a value other than 'macPopulate'.

OBJECT-TYPE

The value of tmnxOamMacPingCtlFibEntryName is the fib entry name to associate with the target MAC address. This object is optional and is not relevant when tmnxOamPingCtlTestMode has a value other than 'macPopulate'. This object was obsoleted in SROS 11.0 R1.

OBJECT-TYPE

Defines a table for storing the results of an OAM 'macPing' probe operation. The number of entries in this table for a test is limited to the results of 3 runs. An entry in this table is created when the result of an OAM 'macPing' probe is determined. An entry is removed from this table when its corresponding tmnxOamPingCtlEntry is deleted.

OBJECT-TYPE

Defines an entry in the tmnxOamMacPingHistoryTable. The first two index elements identify the tmnxOamPingCtlEntry that a tmnxOamMacPingHistoryEntry belongs to. The third index identifies a specific run of the OAM test. The fourth index element selects the group of responses associated with a specific probe attempt. The fifth index selects a single OAM 'macPing' reply.

OBJECT-TYPE

An entry in this table is created when the result of a OAM 'macPing' probe is determined. The initial 2 instance identifier index values identify the tmnxOamPingCtlEntry that a OAM probe result (tmnxOamMacPingHistoryEntry) belongs to. The tmnxOamMacPingHistoryIndex has the value of the sequence number of the request probe and identifies a group of replies received in response to a specific probe transmission. The agent starts assigning tmnxOamMacPingHistoryIndex values at 1 and wraps after exceeding the maximum possible value as defined by the limit of this object.

OBJECT-TYPE

The tmnxOamMacPingReplyIndex is unique within a group of responses received as the result of a OAM 'macPing' probe as specified by having the same value for tmnxOamMacPingHistoryIndex. The agent starts assigning tmnxOamMacPingReplyIndex values at 1 and wraps after exceeding the maximum possible value as defined by the limit of this object.

OBJECT-TYPE

The amount of time measured in microseconds from when a OAM probe was sent to when its response was received or when it timed out. The value of this object is reported as 0 when it is not possible to transmit an OAM probe.

OBJECT-TYPE

The amount of time measured in microseconds from when an OAM probe was sent to when it was received by the replier (outbound one-way time). The value of this object is reported as 0 when it is not possible to transmit an OAM probe or the information is not available.

OBJECT-TYPE

The value of tmnxOamMacPingHistoryStatus is an enumerated integer that indicates the result of a particular OAM probe.

OBJECT-TYPE

Timestamp for when this OAM probe result was determined.

OBJECT-TYPE

The value of tmnxOamMacPingHistoryReturnCode is an enumerated integer that indicates the return code received in the OAM ping response.

OBJECT-TYPE

This object was obsoleted in release 4.0 and replaced with InetAddress objects tmnxOamMacPingHistorySrcAddrType and tmnxOamMacPingHistorySrcAddress.

OBJECT-TYPE

The value of tmnxOamMacPingHistoryAddressType indicates the type of binding address information returned in response to a 'macPing' test.

OBJECT-TYPE

The value of tmnxOamMacPingHistorySapId is the name of the access port of the SAP supporting the requested MAC address returned in response to a 'macPing' probe. If the value of tmnxOamMacPingHistoryAddressType is not 'sapId', this object is not relevant and MUST have a null string ''.

OBJECT-TYPE

The value of tmnxOamMacPingHistorySdpId is the ID of the SDP supporting the requested MAC address returned in response to a 'macPing' probe. If the value of tmnxOamMacPingHistoryAddressType is not 'sdpId', this object is not relevant and MUST return a value of '0'.

OBJECT-TYPE

The value of tmnxOamMacPingHistoryAdminStatus indicates the current administrative state of the SAP or SDP ID returned in response to a 'macPing' test. A value of 'true' indicates the SAP or SDP is administratively 'up'. The value of this object MUST be reported as 'false' when no ping responses have been received or an active test has not yet timed out.

OBJECT-TYPE

The value of tmnxOamMacPingHistoryOperStatus indicates the current operational state of the SAP or SDP ID returned in response to a 'macPing' test. A value of 'true' indicates the SAP or SDP is operationally 'up'. The value of this object MUST be reported as 'false' when no ping responses have been received or an active test has not yet timed out.

OBJECT-TYPE

The value of tmnxOamMacPingHistoryResponsePlane indicates the response plane from which this ping response was received.

OBJECT-TYPE

The value of tmnxOamMacPingHistorySize indicates the size in octets of the user payload in a ping request packet. It does not include the service encapsulation.

OBJECT-TYPE

The amount of time measured in microseconds from when an OAM probe reply was sent to when it was received by this host (inbound one-way time). The value of this object is reported as 0 when the information is not available.

OBJECT-TYPE

The value of tmnxOamMacPingHistorySrcAddrType indicates the Internet address type stored in tmnxOamMacPingHistorySrcAddress.

OBJECT-TYPE

The value of tmnxOamMacPingHistorySrcAddress indicates the Internet address of the remote node that generated this reply to a OAM probe.

OBJECT-TYPE

Defines a table for storing the results of an OAM 'macQuery' probe operation where a L2 mapping TLV is returned. Only one downstream and one upstream L2 mapping entry is returned if the 'macQuery' replier has no egress mapping for the requested MAC address but it does have an SDP binding. Multiple downstream L2 mappings that specify the replier's flooding domain may be returned if the replier has no bindings for the MAC address. An entry in this table is created when the result of an OAM 'macQuery' probe is determined. An entry is removed from this table when its corresponding tmnxOamPingCtlEntry is deleted.

OBJECT-TYPE

Defines an entry in the tmnxOamMacPingL2MapTable. The first two index elements identify the tmnxOamPingCtlEntry that a tmnxOamMacPingL2MapEntry belongs to. The third index element identifies a specific OAM test run. The fourth index element selects the group of responses associated with a specific probe attempt. The fifth index selects a single OAM 'macQuery' reply. Note that in the case of a successful 'macQuery' reply there will be only two row entries created per test run. However there may also be one or more error replies. The sixth index selects a single L2 mapping entry within a specific probe reply.

OBJECT-TYPE

An entry in this table is created when the result of a OAM 'macQuery' probe is determined. The initial 2 instance identifier index values identify the tmnxOamPingCtlEntry that a OAM probe result (tmnxOamMacPingHistoryEntry) belongs to. The tmnxOamMacPingHistoryIndex identifies a group of replies received in response to a specific probe transmission. The tmnxOamMacPingReplyIndex selects a single OAM 'macQuery' reply. The tmnxOamMacPingL2MapIndex selects a single L2 mapping entry within a specific 'macQuery' probe reply. The agent starts assigning tmnxOamMacPingL2MapIndex values at 1.

OBJECT-TYPE

The value of tmnxOamMacPingL2MapRouterID is the router ID for this L2 mapping entry.

OBJECT-TYPE

The value of tmnxOamMacPingL2MapLabel is the label used by the router for the L2FEC or VC ID specified by this L2 mapping entry.

OBJECT-TYPE

The value of tmnxOamMacPingL2MapProtocol is the signaling protocol used by the router for the L2FEC or VC ID specified by this L2 mapping entry.

OBJECT-TYPE

The value of tmnxOamMacPingL2MapVCType specifies the class of VC ID given in tmnxOamMacPingL2MapVCID.

OBJECT-TYPE

The value of tmnxOamMacPingL2MapVCID is the VC ID associated with the label used by the L2FEC specified by this L2 mapping entry.

OBJECT-TYPE

The value of tmnxOamMacPingL2MapDirection specifies the direction that this L2 mapping entry is in relation to the node that returned the 'macQuery' reply.

OBJECT-TYPE

Each row in tmnxOamLspPingCtlTable contains the LSP-specific configuration information needed to launch an LSP (Label Switched Path) ping test. The rest of the configuration information needed to launch the test resides in the corresponding row of tmnxOamPingCtlTable. Results of LSP ping tests are stored in tmnxOamPingResultsTable and tmnxOamPingHistoryTable. Seven types of LSP ping tests are supported. An abbreviated name for each test type is defined in the following table (for use in a subsequent table). The test type's tmnxOamLspPingCtlTestSubMode code point is shown as well. Test Sub Mode Abbreviated Test Type Name(s) --------------------- ------------------------------- 'unspecified (1)' LDP, RSVP 'static (2)' TPST (Transport Profile Static) 'bgpLabeledPrefix(3)' BGP 'srIsis (4)' ISIS 'srOspf (5)' OSPF 'srTe (6)' SRTE 'srPolicy (7)' SRPL 'srOspf3 (8)' OSP3 The following table has a row for each LSP ping test type, showing the mandatory and optional objects applicable to the test type. Test Type Mandatory Objects Optional Objects ---- -------------------------------- --------------------------------- BGP tmnxOamLspPingCtlLdpPrefixType *tmnxOamLspPingCtlNhAddressType tmnxOamLspPingCtlLdpPrefix *tmnxOamLspPingCtlNhAddress tmnxOamLspPingCtlLdpPrefixLen tmnxOamLspPingCtlNhIntfName tmnxOamLspPingCtlTestSubMode #tmnxOamLspPingCtlPathDestType #tmnxOamLspPingCtlPathDest ISIS tmnxOamLspPingCtlLdpPrefixType tmnxOamLspPingCtlIgpInstance tmnxOamLspPingCtlLdpPrefix *tmnxOamLspPingCtlNhAddressType tmnxOamLspPingCtlLdpPrefixLen *tmnxOamLspPingCtlNhAddress tmnxOamLspPingCtlTestSubMode tmnxOamLspPingCtlNhIntfName #tmnxOamLspPingCtlPathDestType #tmnxOamLspPingCtlPathDest LDP tmnxOamLspPingCtlLdpPrefixType *tmnxOamLspPingCtlNhAddressType tmnxOamLspPingCtlLdpPrefix *tmnxOamLspPingCtlNhAddress tmnxOamLspPingCtlLdpPrefixLen tmnxOamLspPingCtlNhIntfName #tmnxOamLspPingCtlPathDestType #tmnxOamLspPingCtlPathDest OSPF tmnxOamLspPingCtlLdpPrefixType tmnxOamLspPingCtlIgpInstance tmnxOamLspPingCtlLdpPrefix *tmnxOamLspPingCtlNhAddressType tmnxOamLspPingCtlLdpPrefixLen *tmnxOamLspPingCtlNhAddress tmnxOamLspPingCtlTestSubMode tmnxOamLspPingCtlNhIntfName #tmnxOamLspPingCtlPathDestType #tmnxOamLspPingCtlPathDest OSP3 tmnxOamLspPingCtlLdpPrefixType tmnxOamLspPingCtlIgpInstance tmnxOamLspPingCtlLdpPrefix *tmnxOamLspPingCtlNhAddressType tmnxOamLspPingCtlLdpPrefixLen *tmnxOamLspPingCtlNhAddress tmnxOamLspPingCtlTestSubMode tmnxOamLspPingCtlNhIntfName #tmnxOamLspPingCtlPathDestType #tmnxOamLspPingCtlPathDest RSVP tmnxOamLspPingCtlLspName tmnxOamLspPingCtlPathName SRPL tmnxOamLspPingCtlSrPlcyColor tmnxOamLspPingCtlSrPlcySegList tmnxOamLspPingCtlSrPlcyEndPtAddr tmnxOamLspPingCtlSrPlcyEndPtAddT tmnxOamLspPingCtlTestSubMode SRTE tmnxOamLspPingCtlLspName *tmnxOamLspPingCtlNhAddressType tmnxOamLspPingCtlTestSubMode *tmnxOamLspPingCtlNhAddress tmnxOamLspPingCtlNhIntfName #tmnxOamLspPingCtlPathDestType #tmnxOamLspPingCtlPathDest tmnxOamLspPingCtlPathName TPST tmnxOamLspPingCtlLspName tmnxOamLspPingCtlAssocChannel tmnxOamLspPingCtlTestSubMode tmnxOamLspPingCtlForce *tmnxOamLspPingCtlMplsTpGlobalId *tmnxOamLspPingCtlMplsTpNodeId tmnxOamLspPingCtlMplsTpPathType ALL none tmnxOamLspPingCtlTtl tmnxOamPingCtlFcName tmnxOamPingCtlInterval tmnxOamPingCtlProbeCount tmnxOamPingCtlProfile tmnxOamPingCtlSize *tmnxOamPingCtlSrcAddrType *tmnxOamPingCtlSrcAddress tmnxOamPingCtlTimeOut ---- -------------------------------- --------------------------------- In the table above, 1. The optional objects in the ALL row apply to all LSP ping test types. 2. Asterisks (*) mark a set of optional objects which must all be specified, or must all be unspecified. 3. Octothorpes (#) mark a separate set of optional objects which must all be specified, or must all be unspecified. 4. There are four supported combinations of tmnxOamLspPingCtlNhAddressType, tmnxOamLspPingCtlNhAddress, tmnxOamLspPingCtlNhIntfName, tmnxOamLspPingCtlPathDestType, and tmnxOamLspPingCtlPathDest, as follows: a) all unspecified b) tmnxOamLspPingCtlPathDestType and tmnxOamLspPingCtlPathDest c) tmnxOamLspPingCtlPathDestType, tmnxOamLspPingCtlPathDest, and tmnxOamLspPingCtlNhIntfName d) tmnxOamLspPingCtlPathDestType, tmnxOamLspPingCtlPathDest, tmnxOamLspPingCtlNhAddressType, and tmnxOamLspPingCtlNhAddress When an object combination other than a combination listed above is specified, values will be rejected or ignored, or the test will fail.

OBJECT-TYPE

The system creates a row in tmnxOamLspPingCtlTable when a row is created in tmnxOamPingCtlTable with tmnxOamPingCtlTestMode set to 'lspPing'. The system deletes a row in tmnxOamLspPingCtlTable when the corresponding row in tmnxOamPingCtlTable is deleted.

OBJECT-TYPE

This object was obsoleted in release 6.0R15 and replaced with tmnxOamPingCtlVRtrID in tmnxOamPingCtlTable.

OBJECT-TYPE

The value of tmnxOamLspPingCtlLspName specifies the name of the LSP for this LSP ping test. When the test is started, if this name is not empty, there must be a TIMETRA-MPLS-MIB::vRtrMplsLspTable row with: 1. tmnxOamLspPingCtlLspName equal to TIMETRA-MPLS-MIB::vRtrMplsLspName, AND 2. TIMETRA-VRTR-MIB::vRtrID equal to 1, AND 3. TIMETRA-MPLS-MIB::vRtrMplsLspType equal to 'dynamic(2)', 'bypassOnly(4)', or 'mplsTp(7)'. Otherwise, the test will fail. The supported object combinations for LSP ping tests are listed in the tmnxOamLspPingCtlTable DESCRIPTION clause.

OBJECT-TYPE

This object was obsoleted in release 4.0.

OBJECT-TYPE

The value of tmnxOamLspPingCtlTtl specifies the outermost label time- to-live value. The supported object combinations for LSP ping tests are listed in the tmnxOamLspPingCtlTable DESCRIPTION clause.

OBJECT-TYPE

The value of tmnxOamLspPingCtlPathName specifies the name of the Path (LSP) for this LSP ping test. When the test is started, if this name is not empty, there must be a matching name in the column MPLS-TE-MIB::mplsTunnelName. Otherwise, the test will fail. The supported object combinations for LSP ping tests are listed in the tmnxOamLspPingCtlTable DESCRIPTION clause.

OBJECT-TYPE

This object was obsoleted in release 4.0 and replaced with InetAddress objects tmnxOamLspPingCtlLdpPrefixType and tmnxOamLspPingCtlLdpPrefix.

OBJECT-TYPE

This object was obsoleted in release 4.0 and replaced with the InetAddress object tmnxOamLspPingCtlLdpPrefixLen.

OBJECT-TYPE

The value of tmnxOamLspPingCtlLdpPrefixType specifies the type of Internet address stored in tmnxOamLspPingCtlLdpPrefix. The supported object combinations for LSP ping tests are listed in the tmnxOamLspPingCtlTable DESCRIPTION clause.

OBJECT-TYPE

The value of tmnxOamLspPingCtlLdpPrefix, along with tmnxOamLspPingCtlLdpPrefixType and tmnxOamLspPingCtlLdpPrefixLen, specifies the destination prefix for this LSP ping test. The supported object combinations for LSP ping tests are listed in the tmnxOamLspPingCtlTable DESCRIPTION clause.

OBJECT-TYPE

The value of tmnxOamLspPingCtlLdpPrefixLen specifies the Internet address prefix length of tmnxOamLspPingCtlLdpPrefix. The supported object combinations for LSP ping tests are listed in the tmnxOamLspPingCtlTable DESCRIPTION clause.

OBJECT-TYPE

The value of tmnxOamLspPingCtlPathDestType specifies the type of Internet address stored in tmnxOamLspPingCtlPathDest. The supported object combinations for LSP ping tests are listed in the tmnxOamLspPingCtlTable DESCRIPTION clause.

OBJECT-TYPE

The value of tmnxOamLspPingCtlPathDest specifies a unique path for this LSP ping to traverse. This address is used as part of a hash key to select the appropriate ECMP path to the destination of an LSP ping test. The supported object combinations for LSP ping tests are listed in the tmnxOamLspPingCtlTable DESCRIPTION clause.

OBJECT-TYPE

The value of tmnxOamLspPingCtlNhIntfName specifies the name of the next hop interface to be used when transmitting an LSP ping. When the test is started, if this name is not empty, there must be a TIMETRA-VRTR-MIB::vRtrIfTable row with: 1. tmnxOamLspPingCtlNhIntfName equal to TIMETRA-VRTR-MIB::vRtrIfName, AND 2. TIMETRA-VRTR-MIB::vRtrID equal to 1. Otherwise, the test will fail. The supported object combinations for LSP ping tests are listed in the tmnxOamLspPingCtlTable DESCRIPTION clause.

OBJECT-TYPE

The value of tmnxOamLspPingCtlNhAddressType specifies the type of Internet address stored in tmnxOamLspPingCtlNhAddress. The supported object combinations for LSP ping tests are listed in the tmnxOamLspPingCtlTable DESCRIPTION clause.

OBJECT-TYPE

The value of tmnxOamLspPingCtlNhAddress specifies the interface address to the next hop which will be used to transmit the LSP ping. The supported object combinations for LSP ping tests are listed in the tmnxOamLspPingCtlTable DESCRIPTION clause.

OBJECT-TYPE

The value of tmnxOamLspPingCtlTestSubMode specifies the type of LSP ping test to perform. When this object is 'unspecified(1)', the type of LSP ping test to be performed is determined when the test is started, from the set of tmnxOamLspPingCtlTable objects configured with non-default values. If there is a mismatch between tmnxOamLspPingCtlTestSubMode and the type of the LSP to be tested, the test will fail. For example, if tmnxOamLspPingCtlTestSubMode is 'static(2)', and tmnxOamLspPingCtlLspName refers to an LSP with TIMETRA-MPLS-MIB::vRtrMplsLspType not equal to 'mplsTp(7)', the test will fail. The supported object combinations for LSP ping tests are listed in the tmnxOamLspPingCtlTable DESCRIPTION clause.

OBJECT-TYPE

The value of tmnxOamLspPingCtlMplsTpPathType specifies the type of the MPLS-TP path to be tested. The supported object combinations for LSP ping tests are listed in the tmnxOamLspPingCtlTable DESCRIPTION clause.

OBJECT-TYPE

The value of tmnxOamLspPingCtlMplsTpGlobalId specifies the target MPLS-TP Global Identifier to be used for the test. The supported object combinations for LSP ping tests are listed in the tmnxOamLspPingCtlTable DESCRIPTION clause.

OBJECT-TYPE

The value of tmnxOamLspPingCtlMplsTpNodeId specifies the target MPLS-TP Node Identifier to be used for the test. A value of zero indicates that no Node Identifier has been configured. The supported object combinations for LSP ping tests are listed in the tmnxOamLspPingCtlTable DESCRIPTION clause.

OBJECT-TYPE

The value of tmnxOamLspPingCtlAssocChannel specifies the launched echo request's usage of the Associated Channel (ACH) mechanism, when testing an MPLS-TP LSP. When tmnxOamLspPingCtlTestSubMode is 'static(2)', the default value for tmnxOamLspPingCtlAssocChannel is 'nonIp(2)'. The supported object combinations for LSP ping tests are listed in the tmnxOamLspPingCtlTable DESCRIPTION clause.

OBJECT-TYPE

The value of tmnxOamLspPingCtlForce specifies whether or not to force the transmission of the 'lspPing' request PDU(s). If tmnxOamLspPingCtlForce is 'true(1)', the test will proceed and request PDU(s) will be sent regardless of the local operational status of the tested LSP path. If tmnxOamLspPingCtlForce is 'false(2)', the test will fail immediately when the local operational status of the tested LSP path is down. The supported object combinations for LSP ping tests are listed in the tmnxOamLspPingCtlTable DESCRIPTION clause.

OBJECT-TYPE

The value of tmnxOamLspPingCtlIgpInstance specifies the Interior Gateway Protocol (IGP) instance to be used for the test. The supported object combinations for LSP ping tests are listed in the tmnxOamLspPingCtlTable DESCRIPTION clause.

OBJECT-TYPE

The value of tmnxOamLspPingCtlSrPlcyColor specifies the Segment Routing (SR) policy color to be used for the test. A color associates an SR policy with an intent (e.g. low latency). tmnxOamLspPingCtlSrPlcyColor, tmnxOamLspPingCtlSrPlcyEndPtAddT, and tmnxOamLspPingCtlSrPlcyEndPtAddr must identify a known SR policy. Otherwise, the test will fail. The color of a static SR policy is defined using TIMETRA-SR-POLICY-MIB::vRtrSrStaticPlcyColor. When configuring an SR policy LSP ping test, the following objects must all be set in one snmpset PDU: tmnxOamLspPingCtlTestSubMode = 'srPolicy(7)', tmnxOamLspPingCtlSrPlcyColor, tmnxOamLspPingCtlSrPlcyEndPtAddT = 'ipv4(1)' or 'ipv6(2)', tmnxOamLspPingCtlSrPlcyEndPtAddr. The supported object combinations for LSP ping tests are listed in the tmnxOamLspPingCtlTable DESCRIPTION clause.

OBJECT-TYPE

The value of tmnxOamLspPingCtlSrPlcyEndPtAddT specifies the type of IP address stored in tmnxOamLspPingCtlSrPlcyEndPtAddr. The supported object combinations for LSP ping tests are listed in the tmnxOamLspPingCtlTable DESCRIPTION clause.

OBJECT-TYPE

The value of tmnxOamLspPingCtlSrPlcyEndPtAddr specifies the Segment Routing (SR) policy endpoint address to be used for the test. tmnxOamLspPingCtlSrPlcyColor, tmnxOamLspPingCtlSrPlcyEndPtAddT, and tmnxOamLspPingCtlSrPlcyEndPtAddr must identify a known SR policy. Otherwise, the test will fail. The endpoint of a static SR policy is defined using TIMETRA-SR-POLICY-MIB::vRtrSrStaticPlcyEndPtAddrType TIMETRA-SR-POLICY-MIB::vRtrSrStaticPlcyEndPtAddr. When configuring an SR policy LSP ping test, the following objects must all be set in one snmpset PDU: tmnxOamLspPingCtlTestSubMode = 'srPolicy(7)', tmnxOamLspPingCtlSrPlcyColor, tmnxOamLspPingCtlSrPlcyEndPtAddT = 'ipv4(1)' or 'ipv6(2)', tmnxOamLspPingCtlSrPlcyEndPtAddr. The supported object combinations for LSP ping tests are listed in the tmnxOamLspPingCtlTable DESCRIPTION clause.

OBJECT-TYPE

The value of tmnxOamLspPingCtlSrPlcySegList specifies the Segment Routing (SR) policy segment list to be used for the test. The supported object combinations for LSP ping tests are listed in the tmnxOamLspPingCtlTable DESCRIPTION clause.

OBJECT-TYPE

Defines the Nokia SROS OAM VPRN Ping Control Table for providing, via SNMP, the capability of performing Nokia SROS OAM 'vprnPing' test operations. The results of these tests are stored in the tmnxOamPingResultsTable and the tmnxOamTrProbeHistoryTable. There will be no entries for these test in the tmnxOamPingHistoryTable.

OBJECT-TYPE

Defines an entry in the tmnxOamVprnPingCtlTable. The first index element, tmnxOamPingCtlOwnerIndex, is of type SnmpAdminString, a textual convention that allows for use of the SNMPv3 View-Based Access Control Model (RFC 2575 [11], VACM) and allows a management application to identify its entries. The second index, tmnxOamPingCtlTestIndex, enables the same management application to have multiple outstanding requests.

OBJECT-TYPE

This object was obsoleted in release 4.0 and replaced with InetAddress objects tmnxOamVprnPingCtlSrcAddrType and tmnxOamVprnPingCtlSrcAddress.

OBJECT-TYPE

When the value of tmnxOamVprnPingCtlReplyControl is 'true', the OAM ping response is returned using the control plane. If its value is 'false', the packet is sent via the data plane. This object is optional and is not relevant when tmnxOamPingCtlTestMode has a value other than 'vprnPing'.

OBJECT-TYPE

Specifies the vc-label time-to-live value. This object is optional and is not relevant when tmnxOamPingCtlTestMode has a value other than 'vprnPing'. While performing the test with a TTL of 1 no responses should ever be expected.

OBJECT-TYPE

The value of tmnxOamVprnPingCtlSrcAddrType specifies the Internet address type stored in tmnxOamVprnPingCtlSrcAddress.

OBJECT-TYPE

The value of tmnxOamVprnPingCtlSrcAddress specifies the Internet address to be used as the source for performing an OAM ping operation when tmnxOamPingCtlTestMode has a value of 'vprnPing'. This parameter is required.

OBJECT-TYPE

Defines the Nokia SROS OAM ATM Ping Control Table for providing, via SNMP, the capability of performing Nokia SROS OAM 'atmPing' test operations. The results of these tests are stored in the tmnxOamPingResultsTable and the tmnxOamPingHistoryTable.

OBJECT-TYPE

Defines an entry in the tmnxOamAtmPingCtlTable. The first index element, tmnxOamPingCtlOwnerIndex, is of type SnmpAdminString, a textual convention that allows for use of the SNMPv3 View-Based Access Control Model (RFC 2575 [11], VACM) and allows a management application to identify its entries. The second index, tmnxOamPingCtlTestIndex, enables the same management application to have multiple outstanding requests.

OBJECT-TYPE

The value of tmnxOamAtmPingCtlPortId is the ID of the access port of the target VC. This parameter is required.

OBJECT-TYPE

The value of tmnxOamAtmPingCtlVpi is the VPI of the VC used to send the OAM ATM ping. This is a required parameter.

OBJECT-TYPE

The value of tmnxOamAtmPingCtlVci is the VCI of the VC used to send the OAM ATM ping. This is a required parameter.

OBJECT-TYPE

The value of tmnxOamAtmPingCtlLpbkLocation specifies the Loopback Location ID used in the ATM OAM loopback cell. If all bits in the Loopback Location ID are '1', the destination of the OAM ATM ping is the far-end destination of the VC. Otherwise the cell is destined to a specific ATM node in the ATM network. This is an optional parameter.

OBJECT-TYPE

The value of tmnxOamAtmPingCtlSegment determines if the ATM OAM loopback cell is destined to the first segment going in the line direction or the PVCC's connection endpoint.

OBJECT-TYPE

Defines the Nokia SROS OAM MFIB Ping Control Table for providing, via SNMP, the capability of performing Nokia SROS OAM 'mfibPing' test operations. The results of these tests are stored in the tmnxOamPingResultsTable and the tmnxOamPingHistoryTable. Rows are created in the tmnxOamMfibPingCtlTable only for those entries in the tmnxOamPingCtlTable where tmnxOamPingCtlTestMode has a value of 'mfibPing'.

OBJECT-TYPE

Defines an entry in the tmnxOamMfibPingCtlTable. The first index element, tmnxOamPingCtlOwnerIndex, is of type SnmpAdminString, a textual convention that allows for use of the SNMPv3 View-Based Access Control Model (RFC 2575 [11], VACM) and allows a management application to identify its entries. The second index, tmnxOamPingCtlTestIndex, enables the same management application to have multiple outstanding requests.

OBJECT-TYPE

This object was obsoleted in release 4.0 and replaced with InetAddress objects tmnxOamMfibPingCtlSrcAddrType and tmnxOamMfibPingCtlSrcAddress.

OBJECT-TYPE

This object was obsoleted in release 4.0 and replaced with InetAddress objects tmnxOamMfibPingCtlDestAddrType and tmnxOamMfibPingCtlDestAddress.

OBJECT-TYPE

When the value of tmnxOamMfibPingCtlReplyControl is 'true', the OAM ping response is returned using the control plane. If its value is 'false', the packet is sent via the data plane. This object is optional and is not relevant when tmnxOamPingCtlTestMode has a value other than 'mfibPing'.

OBJECT-TYPE

Specifies the vc-label time-to-live value. This object is optional and is not relevant when tmnxOamPingCtlTestMode has a value other than 'mfibPing'. While performing the test with a TTL of 1 no responses should ever be expected.

OBJECT-TYPE

The value of tmnxOamMfibPingCtlSrcAddrType specifies the Internet address type stored in tmnxOamMfibPingCtlSrcAddress.

OBJECT-TYPE

The value of tmnxOamMfibPingCtlSrcAddress specifies the Internet address to be used as the source for performing an OAM ping operation when tmnxOamPingCtlTestMode has a value of 'mfibPing' and the value of tmnxOamMfibPingCtlDestMacAddr is all zeros, in which case this parameter is required. If tmnxOamPingCtlTestMode is different from 'mfibPing' this field is ignored.

OBJECT-TYPE

The value of tmnxOamMfibPingCtlDestAddrType specifies the Internet multicast address type stored in tmnxOamMfibPingCtlDestAddress.

OBJECT-TYPE

The value of tmnxOamMfibPingCtlDestAddress specifies the Internet multicast address to be used as the destination for performing an OAM ping operation when tmnxOamPingCtlTestMode has a value of 'mfibPing' and the value of tmnxOamMfibPingCtlDestMacAddr is all zeros, in which case this parameter is required. If tmnxOamPingCtlTestMode is different from 'mfibPing' this field is ignored.

OBJECT-TYPE

The value of tmnxOamMfibPingCtlDestMacAddr specifies the IPv6 multicast MAC address to be used as the destination for performing an OAM ping operation when tmnxOamPingCtlTestMode has a value of 'mfibPing' and objects tmnxOamMfibPingCtlSrcAddrType and tmnxOamMfibPingCtlDestAddrType have a value of 'unknown (0)', in which case this parameter is required. If tmnxOamPingCtlTestMode is different from 'mfibPing' this field is ignored.

OBJECT-TYPE

Defines the Nokia SROS OAM CPE Ping Control Table for providing, via SNMP, the capability of performing Nokia SROS OAM 'cpePing' test operations. The results of these tests are stored in the tmnxOamPingResultsTable and the tmnxOamPingHistoryTable. Rows are created in the tmnxOamCpePingCtlTable only for those entries in the tmnxOamPingCtlTable where tmnxOamPingCtlTestMode has a value of 'cpePing'.

OBJECT-TYPE

Defines an entry in the tmnxOamCpePingCtlTable. The first index element, tmnxOamPingCtlOwnerIndex, is of type SnmpAdminString, a textual convention that allows for use of the SNMPv3 View-Based Access Control Model (RFC 2575 [11], VACM) and allows a management application to identify its entries. The second index, tmnxOamPingCtlTestIndex, enables the same management application to have multiple outstanding requests.

OBJECT-TYPE

This object was obsoleted in release 4.0 and replaced with InetAddress objects tmnxOamCpePingCtlSrcAddrType and tmnxOamCpePingCtlSrcAddress.

OBJECT-TYPE

The value of tmnxOamCpePingCtlSendControl specifies whether the outbound OAM ping packet will use the data plane or the control plane. When the value is 'false', the packet is sent using the data plane. As of SROS release 13.0 R1, a test cannot be started if tmnxOamCpePingCtlSendControl is 'true'. A test is started using tmnxOamPingCtlAdminStatus. This object will be marked obsolete in a future release.

OBJECT-TYPE

When the value of tmnxOamCpePingCtlReplyControl is 'true', the OAM ping response is returned using the control plane. If its value is 'false', the packet is sent via the data plane. This object is optional and is not relevant when tmnxOamPingCtlTestMode has a value other than 'cpePing'.

OBJECT-TYPE

Specifies the vc-label time-to-live value. This object is optional and is not relevant when tmnxOamPingCtlTestMode has a value other than 'cpePing'. When performing the test with a TTL=1, the cpe-ping is only done to the local SAP(s).

OBJECT-TYPE

When set to a non zero value, the system will use the value as source mac address in the ARP request that will be sent to the CPE. If set to 0, the MAC address configured for the CPM is used. This object is optional and is not relevant when tmnxOamPingCtlTestMode has a value other than 'cpePing'.

OBJECT-TYPE

The value of tmnxOamCpePingCtlSrcAddrType specifies the Internet address type stored in tmnxOamCpePingCtlSrcAddress.

OBJECT-TYPE

The value of tmnxOamCpePingCtlSrcAddress specifies the Internet address to be used as the source for performing a CPE ping operation when tmnxOamPingCtlTestMode has a value of 'cpePing'. This parameter is required for 'cpePing' and ignored in all other cases.

OBJECT-TYPE

Defines the Nokia SROS OAM Multicast Router Information Response Table for providing, via SNMP, the capability of performing Nokia SROS OAM 'mrinfo' test operations. The results of these tests are stored in the tmnxOamPingResultsTable, the tmnxOamPingHistoryTable and the tmnxOamMRInfoRespTable.

OBJECT-TYPE

Defines an entry in the tmnxOamMRInfoRespTable. The first index element, tmnxOamPingCtlOwnerIndex, is of type SnmpAdminString, a textual convention that allows for use of the SNMPv3 View-Based Access Control Model (RFC 2575 [11], VACM) and allows a management application to identify its entries. The second index, tmnxOamPingCtlTestIndex, enables the same management application to have multiple outstanding requests.

OBJECT-TYPE

tmnxOamMRInfoRespCapabilities indicates the capabilities of the router responding to the mrinfo request: leaf(0) This is a leaf router prune(1) This router understands pruning genid(2) This router sends Generation Id's mtrace(3) This router handles Mtrace requests snmp(4) This router supports the DVMRP MIB

OBJECT-TYPE

tmnxOamMRInfoRespMinorVersion indicates the minor software version on the router responding to the mrinfo request.

OBJECT-TYPE

tmnxOamMRInfoRespMajorVersion indicates the major software version on the router responding to the mrinfo request.

OBJECT-TYPE

tmnxOamMRInfoRespNumInterfaces indicates the number of interfaces in the mrinfo response packet. These interfaces are listed in the tmnxOamMRInfoRespIfTable.

OBJECT-TYPE

Defines the Nokia SROS OAM Multicast Router Information Interface Table for providing, via SNMP, the capability of performing Nokia SROS OAM 'mrinfo' test operation. The results of these tests are stored in the tmnxOamPingResultsTable, the tmnxOamPingHistoryTable and the tmnxOamMRInfoRespIfTable.

OBJECT-TYPE

Defines an entry in the tmnxOamMRInfoRespIfTable. The first index element, tmnxOamPingCtlOwnerIndex, is of type SnmpAdminString, a textual convention that allows for use of the SNMPv3 View-Based Access Control Model (RFC 2575 [11], VACM) and allows a management application to identify its entries. The second index, tmnxOamPingCtlTestIndex, enables the same management application to have multiple outstanding requests.

OBJECT-TYPE

tmnxOamMRInfoRespIfIndex is the index into the tmnxOamMRInfoRespIfTable. The mrinfo response packet has the router's interfaces on which multicast is enabled. tmnxOamMRInfoRespIfIndex is used to identify those interfaces.

OBJECT-TYPE

This object was obsoleted in release 4.0 and replaced with InetAddress objects tmnxOamMRInfoRespIfAddrType and tmnxOamMRInfoRespIfAddr.

OBJECT-TYPE

tmnxOamMRInfoRespIfMetric indicates the metric on the interface.

OBJECT-TYPE

tmnxOamMRInfoRespIfThreshold indicates the threshold on the interface.

OBJECT-TYPE

tmnxOamMRInfoRespIfFlags indicates the flags associated with an interface: tunnel(0) Neighbor reached via tunnel srcrt(1) Tunnel uses IP source routing reserved1(2) No longer used reserved2(3) No longer used down(4) Operational status down disabled(5) Administrative status down querier(6) Querier for interface leaf(7) No downstream neighbors on interface

OBJECT-TYPE

tmnxOamMRInfoRespIfNbrCount indicates the number of multicast neighbors on the interface. The neighbors are listed in the tmnxOamMRInfoRespIfNbrTable.

OBJECT-TYPE

tmnxOamMRInfoRespIfAddrType indicates the Internet address type stored in tmnxOamMRInfoRespIfAddr.

OBJECT-TYPE

tmnxOamMRInfoRespIfAddr indicates the Internet address of the interface on the router responding to the mrinfo request.

OBJECT-TYPE

Defines the Nokia SROS OAM Multicast Router Information Interface Neighbor Table for providing, via SNMP, the capability of performing Nokia SROS OAM 'mrInfo' test operation. This table contains entries for neighbors on an interface. The results of the mrinfo test are stored in the tmnxOamPingResultsTable, the tmnxOamPingHistoryTable, the tmnxOamMRInfoRespTable, the tmnxOamMRInfoRespIfTable and the tmnxOamMRInfoRespIfNbrTable.

OBJECT-TYPE

Defines an entry in the tmnxOamMRInfoRespIfNbrTable. The first index element, tmnxOamPingCtlOwnerIndex, is of type SnmpAdminString, a textual convention that allows for use of the SNMPv3 View-Based Access Control Model (RFC 2575 [11], VACM) and allows a management application to identify its entries. The second index, tmnxOamPingCtlTestIndex, enables the same management application to have multiple outstanding requests.

OBJECT-TYPE

tmnxOamMRInfoRespIfNbrIndex is used to identify the multicast neighbor on the interface tmnxOamMRInfoRespIfIndex.

OBJECT-TYPE

This object was obsoleted in release 4.0 and replaced with InetAddress objects tmnxOamMRInfoRespIfNbrAddrType and tmnxOamMRInfoRespIfNbrAddr.

OBJECT-TYPE

tmnxOamMRInfoRespIfNbrAddrType indicates the Internet address type stored in tmnxOamMRInfoRespIfNbrAddr.

OBJECT-TYPE

tmnxOamMRInfoRespIfNbrAddr indicates the Internet address of the neighbor on the interface.

OBJECT-TYPE

Each row in tmnxOamVccvPingCtlTable contains the VCCV-specific configuration information needed to launch a VCCV (Virtual Circuit Connectivity Verification) ping test. The rest of the configuration information needed to launch the test resides in the corresponding row of tmnxOamPingCtlTable. Results of VCCV ping tests are stored in tmnxOamPingResultsTable and tmnxOamPingHistoryTable. Four types of VCCV ping tests are supported: AII Type 2, FEC-128 Pseudowire, Spoke SDP FEC, and Transport Profile Static. AII Type 2 and Spoke SDP FEC offer two ways to specify a VCCV ping FEC-129 Pseudowire test. In the Transport Profile Static case, the test type is configured (using tmnxOamVccvPingCtlTestSubMode). In the other three cases, the test type is not configured (i.e. the default tmnxOamVccvPingCtlTestSubMode value 'unspecified(1)' is used). The following table has a row for each VCCV ping test type, showing the mandatory and optional objects applicable to the test type. Abbreviated VCCV ping test type names are used. Test Type Mandatory Objects Optional Objects ------ ------------------------------ --------------------------------- aiiTY2 tmnxOamVccvPingCtlSaiiAcId *tmnxOamPingCtlSrcAddrType tmnxOamVccvPingCtlSaiiGlobalId *tmnxOamPingCtlSrcAddress tmnxOamVccvPingCtlSaiiPrefix *tmnxOamPingCtlTgtAddrType tmnxOamVccvPingCtlTaiiAcId *tmnxOamPingCtlTgtAddress tmnxOamVccvPingCtlTaiiGlobalId tmnxOamVccvPingCtlReplyMode tmnxOamVccvPingCtlTaiiPrefix FEC128 tmnxOamVccvPingCtlSdpIdVcId *tmnxOamPingCtlSrcAddrType *tmnxOamPingCtlSrcAddress *tmnxOamPingCtlTgtAddrType *tmnxOamPingCtlTgtAddress *tmnxOamVccvPingCtlPwId tmnxOamVccvPingCtlReplyMode #tmnxOamVccvPingCtlSwitTgtFecType #tmnxOamVccvPgTgStaticCtlAgi #tmnxOamVccvPgTgStaticCtlSaiiGlbl #tmnxOamVccvPgTgStaticCtlSaiiNode #tmnxOamVccvPgTgStaticCtlSaiiAcId #tmnxOamVccvPgTgStaticCtlTaiiGlbl #tmnxOamVccvPgTgStaticCtlTaiiNode #tmnxOamVccvPgTgStaticCtlTaiiAcId sdpFEC tmnxOamVccvPingCtlSpokeSdpId *tmnxOamPingCtlSrcAddrType *tmnxOamPingCtlSrcAddress *tmnxOamPingCtlTgtAddrType *tmnxOamPingCtlTgtAddress #tmnxOamVccvPingCtlSaiiAcId #tmnxOamVccvPingCtlSaiiGlobalId #tmnxOamVccvPingCtlSaiiPrefix #tmnxOamVccvPingCtlTaiiAcId #tmnxOamVccvPingCtlTaiiGlobalId #tmnxOamVccvPingCtlTaiiPrefix tmnxOamVccvPingCtlReplyMode TPST tmnxOamVccvPingCtlSdpIdVcId *tmnxOamPingCtlSrcAddrType tmnxOamVccvPingCtlTestSubMode *tmnxOamPingCtlSrcAddress tmnxOamVccvPingCtlAssocChannel #tmnxOamVccvPingCtlMplsTpGlobalId #tmnxOamVccvPingCtlMplsTpNodeId ^tmnxOamVccvPingCtlSwitTgtFecType ^tmnxOamVccvPgTgFec128CtlSrcAddrT ^tmnxOamVccvPgTgFec128CtlSrcAddr ^tmnxOamVccvPgTgFec128CtlDstAddrT ^tmnxOamVccvPgTgFec128CtlDstAddr ^tmnxOamVccvPgTgFec128CtlPwId ^tmnxOamVccvPgTgFec128CtlPwType ALL N/A tmnxOamPingCtlFcName tmnxOamPingCtlInterval tmnxOamPingCtlProbeCount tmnxOamPingCtlProfile tmnxOamPingCtlSize tmnxOamPingCtlTimeOut tmnxOamVccvPingCtlTtl ------ ------------------------------ --------------------------------- In the table above, 1. The optional objects in the ALL row apply to all four VCCV ping test types. 2. The characters '*', '#', and '^' each mark an independent set of optional objects which must all be specified, or must all be unspecified. When an object combination other than a combination listed above is specified, values will be rejected or ignored, or the test will fail.

OBJECT-TYPE

The system creates a row in tmnxOamVccvPingCtlTable when a row is created in tmnxOamPingCtlTable with tmnxOamPingCtlTestMode set to 'vccvPing'. The system deletes a row in tmnxOamVccvPingCtlTable when the corresponding row in tmnxOamPingCtlTable is deleted.

OBJECT-TYPE

The value of tmnxOamVccvPingCtlSdpIdVcId specifies the SDP binding of the pseudowire to be tested by a VCCV ping test. The all-zeros value indicates an unused SDP binding. The supported object combinations for VCCV ping tests are listed in the tmnxOamVccvPingCtlTable DESCRIPTION clause.

OBJECT-TYPE

The value of tmnxOamVccvPingCtlReplyMode specifies the band to be used by the echo reply PDU. ip(2) out-of-band reply controlChannel(4) inband reply The supported object combinations for VCCV ping tests are listed in the tmnxOamVccvPingCtlTable DESCRIPTION clause.

OBJECT-TYPE

The value of tmnxOamVccvPingCtlPwId specifies the pseudowire identifier to be used when performing a VCCV ping test on a FEC 128 pseudowire. The pseudowire Id is a non-zero 32-bit connection ID required by FEC 128, as defined in RFC 4379. A value of zero indicates that no pseudowire Id has been configured. The supported object combinations for VCCV ping tests are listed in the tmnxOamVccvPingCtlTable DESCRIPTION clause.

OBJECT-TYPE

The value of tmnxOamVccvPingCtlTtl specifies the time-to-live value for the vc-label of the echo request message. The outer label TTL is set to 255, regardless of this value. The supported object combinations for VCCV ping tests are listed in the tmnxOamVccvPingCtlTable DESCRIPTION clause.

OBJECT-TYPE

The value of tmnxOamVccvPingCtlSpokeSdpId specifies the spoke SDP identifier to be used when performing a VCCV ping test on a FEC 129 pseudowire. A value of zero indicates that no spoke SDP identifier has been configured. The supported object combinations for VCCV ping tests are listed in the tmnxOamVccvPingCtlTable DESCRIPTION clause.

OBJECT-TYPE

The value of tmnxOamVccvPingCtlSaiiGlobalId specifies the global identifier of the Source Attachment Individual Identifier (SAII) to be used when testing a FEC 129 AII Type 2 pseudowire. A value of zero indicates that no global identifier has been configured. The supported object combinations for VCCV ping tests are listed in the tmnxOamVccvPingCtlTable DESCRIPTION clause.

OBJECT-TYPE

The value of tmnxOamVccvPingCtlSaiiPrefix specifies the prefix of the Source Attachment Individual Identifier (SAII) to be used when testing a FEC 129 AII Type 2 pseudowire. A value of zero indicates that no prefix has been configured. The supported object combinations for VCCV ping tests are listed in the tmnxOamVccvPingCtlTable DESCRIPTION clause.

OBJECT-TYPE

The value of tmnxOamVccvPingCtlSaiiAcId specifies the attachment circuit identifier of the Source Attachment Individual Identifier (SAII) to be used when testing a FEC 129 AII Type 2 pseudowire. A value of zero indicates that no attachment circuit identifier has been configured. The supported object combinations for VCCV ping tests are listed in the tmnxOamVccvPingCtlTable DESCRIPTION clause.

OBJECT-TYPE

The value of tmnxOamVccvPingCtlTaiiGlobalId specifies the global identifier of the Target Attachment Individual Identifier (TAII) to be used when testing a FEC 129 AII Type 2 pseudowire. A value of zero indicates that no global identifier has been configured. The supported object combinations for VCCV ping tests are listed in the tmnxOamVccvPingCtlTable DESCRIPTION clause.

OBJECT-TYPE

The value of tmnxOamVccvPingCtlTaiiPrefix specifies the prefix of the Target Attachment Individual Identifier (TAII) to be used when testing a FEC 129 AII Type 2 pseudowire. A value of zero indicates that no prefix has been configured. The supported object combinations for VCCV ping tests are listed in the tmnxOamVccvPingCtlTable DESCRIPTION clause.

OBJECT-TYPE

The value of tmnxOamVccvPingCtlTaiiAcId specifies the attachment circuit identifier of the Target Attachment Individual Identifier (TAII) to be used when testing a FEC 129 AII Type 2 pseudowire. A value of zero indicates that no attachment circuit identifier has been configured. The supported object combinations for VCCV ping tests are listed in the tmnxOamVccvPingCtlTable DESCRIPTION clause.

OBJECT-TYPE

The value of tmnxOamVccvPingCtlMplsTpGlobalId specifies the target MPLS-TP Global Identifier to be used for the test. The supported object combinations for VCCV ping tests are listed in the tmnxOamVccvPingCtlTable DESCRIPTION clause.

OBJECT-TYPE

The value of tmnxOamVccvPingCtlMplsTpNodeId specifies the target MPLS-TP Node Identifier to be used for the test. A value of zero indicates that no Node Identifier has been configured. The supported object combinations for VCCV ping tests are listed in the tmnxOamVccvPingCtlTable DESCRIPTION clause.

OBJECT-TYPE

The value of tmnxOamVccvPingCtlTestSubMode specifies the type of VCCV ping test to perform. When this object is 'unspecified(1)', the type of VCCV ping test to be performed is determined when the test is started, from the set of tmnxOamVccvPingCtlTable objects configured with non-default values. If there is a mismatch between tmnxOamVccvPingCtlTestSubMode and the type of the pseudowire to be tested, the test will fail. For example, if tmnxOamVccvPingCtlTestSubMode is 'static(2)', and there is no TIMETRA-SDP-MIB::sdpBindPwPathTable row for the test's SDP binding, the test will fail. The supported object combinations for VCCV ping tests are listed in the tmnxOamVccvPingCtlTable DESCRIPTION clause.

OBJECT-TYPE

The value of tmnxOamVccvPingCtlAssocChannel specifies the launched echo request's usage of the Associated Channel (ACH) mechanism, when performing an MPLS-TP VCCV ping test. When tmnxOamVccvPingCtlTestSubMode is 'static(2)', the default value for tmnxOamVccvPingCtlAssocChannel is 'nonIp(2)'. The supported object combinations for VCCV ping tests are listed in the tmnxOamVccvPingCtlTable DESCRIPTION clause.

OBJECT-TYPE

The value of tmnxOamVccvPingCtlSwitTgtFecType specifies the type of downstream FEC (Forward Equivalence Class) segment to be tested. This object must be set to a non-default value when the path to be tested starts with a FEC segment, and switches to a FEC segment with a different type. For example, if the path to be tested starts with a static FEC, and switches to FEC 128, this object must be set to 'fec128(2)'.

OBJECT-TYPE

tmnxOamIcmpPingCtlTable (along with tmnxOamPingCtlTable) contains the configuration information for ICMP ping tests. Test results are stored in tmnxOamPingResultsTable and tmnxOamPingHistoryTable.

OBJECT-TYPE

tmnxOamIcmpPingCtlEntry (along with tmnxOamPingCtlEntry) contains the configuration information for an ICMP ping test. A row is created when the corresponding tmnxOamPingCtlTestMode is set to 'icmpPing'. A row is destroyed when the corresponding tmnxOamPingCtlTable row is destroyed (using tmnxOamPingCtlRowStatus). The values in a particular row in this table cannot be changed when the corresponding tmnxOamPingCtlAdminStatus is 'enabled(1)'.

OBJECT-TYPE

The value of tmnxOamIcmpPingCtlRapid specifies whether or not to send ICMP ping probes in rapid sequence. Changing tmnxOamIcmpPingCtlRapid from 'false(2)' to 'true(1)' implicitly sets tmnxOamPingCtlIntervalUnits to 'centiseconds(2)'. For example, if tmnxOamPingCtlInterval is 1, that makes the interval for the test 0.01 seconds. Changing tmnxOamIcmpPingCtlRapid from 'true(1)' to 'false(2)' implicitly sets tmnxOamPingCtlIntervalUnits to 'seconds(1)'. For example, if tmnxOamPingCtlInterval is 1, that makes the interval for the test 1 second. tmnxOamIcmpPingCtlRapid = 'true(1)' and tmnxOamSaaCtlContinuous = 'true(1)' is an unsupported combination.

OBJECT-TYPE

The value of tmnxOamIcmpPingCtlTtl specifies the initial time-to-live value for the ICMP ping packets.

OBJECT-TYPE

The value of tmnxOamIcmpPingCtlDSField specifies the value to load in the Type of Service (TOS) octet or the Traffic Class (TC) octet of the launched ICMP echo request(s). The TOS octet is a field in the IPv4 packet header. The TC octet is a field in the IPv6 packet header. The value in the TOS or TC octet may influence the route, latency, and/or probability of loss for the echo request (and, by inference, for the associated data flow). This object is optional.

OBJECT-TYPE

The value of tmnxOamIcmpPingCtlPattern specifies a two-octet value to be repeated to fill the Data field of the ICMP ping packet. When the value -1 is specified, the Data field will be filled with positional values.

OBJECT-TYPE

The value of tmnxOamIcmpPingCtlNhAddrType specifies the address type of the tmnxOamIcmpPingCtlNhAddress Internet address.

OBJECT-TYPE

The value of tmnxOamIcmpPingCtlNhAddress specifies the Internet address of the next-hop. Only one of tmnxOamIcmpPingCtlNhAddress, tmnxOamIcmpPingCtlEgrIfIndex, tmnxOamIcmpPingCtlEgrIfName, or tmnxOamIcmpPingCtlBypassRouting may be set to a non-default value. Otherwise, 'inconsistentValue' is returned.

OBJECT-TYPE

The value of tmnxOamIcmpPingCtlEgrIfIndex specifies the ifIndex of the interface to use to transmit the ICMP ping packets. If a non-zero value is Set, it must be a known ifIndex. The value stored is the corresponding interface name string. When tmnxOamIcmpPingCtlEgrIfIndex is read, the stored interface name string is converted to an ifIndex (zero, if the interface no longer exists), and the ifIndex is returned. When tmnxOamIcmpPingCtlEgrIfName is read, the stored interface name string is returned. If zero is Set, the empty string is stored in the interface name string. When tmnxOamIcmpPingCtlEgrIfIndex is read, zero is returned. When tmnxOamIcmpPingCtlEgrIfName is read, the empty string is returned. Only one of tmnxOamIcmpPingCtlNhAddress, tmnxOamIcmpPingCtlEgrIfIndex, tmnxOamIcmpPingCtlEgrIfName, or tmnxOamIcmpPingCtlBypassRouting may be set to a non-default value. Otherwise, 'inconsistentValue' is returned. When tmnxOamPingCtlRouterInstanceName is non-default, tmnxOamIcmpPingCtlEgrIfIndex cannot be set to a non-default value. Managers are encouraged to use tmnxOamIcmpPingCtlEgrIfName (instead of tmnxOamIcmpPingCtlEgrIfIndex) because tmnxOamIcmpPingCtlEgrIfIndex will be deleted in a future release.

OBJECT-TYPE

The value of tmnxOamIcmpPingCtlBypassRouting specifies whether or not to send the ping request to a host on a directly attached network, bypassing the routing table. Only one of tmnxOamIcmpPingCtlNhAddress, tmnxOamIcmpPingCtlEgrIfIndex, tmnxOamIcmpPingCtlEgrIfName, or tmnxOamIcmpPingCtlBypassRouting may be set to a non-default value. Otherwise, 'inconsistentValue' is returned.

OBJECT-TYPE

The value of tmnxOamIcmpPingCtlDoNotFragment specifies whether or not the IPv4 'DF' (Don't Fragment) bit is set in the ICMP ping packet(s) launched for the test. When tmnxOamIcmpPingCtlDoNotFragment is 'true(1)', the 'DF' bit is set. This object is significant if: 1. The target address type for the test (i.e. tmnxOamPingCtlTgtAddrType) is 'ipv4(1)', or 2. tmnxOamPingCtlTgtAddrType is 'dns(16)', and the DNS name resolves to an IPv4 address. Otherwise, this object is ignored.

OBJECT-TYPE

The value of tmnxOamIcmpPingCtlEgrIfName specifies the name of the interface to use to transmit the ICMP ping packets. The value provided is accepted whether or not it is a known interface name (validation is done as part of executing the test). When tmnxOamIcmpPingCtlEgrIfName is Set, the given interface name string is stored. When tmnxOamIcmpPingCtlEgrIfName is read, the interface name string is returned. When tmnxOamIcmpPingCtlEgrIfIndex is read, the interface name string is converted to an ifIndex (zero if the interface name string is the empty string, or cannot be converted to an ifIndex), and the ifIndex is returned. Only one of tmnxOamIcmpPingCtlNhAddress, tmnxOamIcmpPingCtlEgrIfIndex, tmnxOamIcmpPingCtlEgrIfName, or tmnxOamIcmpPingCtlBypassRouting may be set to a non-default value. Otherwise, 'inconsistentValue' is returned.

OBJECT-TYPE

Defines the Nokia SROS OAM ANCP Control Table for providing, via SNMP, the capability of performing Nokia SROS OAM 'ANCP loopback' test operations. The results of these tests are stored in the tmnxOamPingResultsTable and the tmnxOamAncpTestHistoryTable. There will be no entries for these tests in the tmnxOamPingHistoryTable.

OBJECT-TYPE

Defines an entry in the tmnxOamAncpTestCtlTable. The first index element, tmnxOamPingCtlOwnerIndex, is of type SnmpAdminString, a textual convention that allows for use of the SNMPv3 View-Based Access Control Model (RFC 2575 [11], VACM) and allows a management application to identify its entries. The second index, tmnxOamPingCtlTestIndex, enables the same management application to have multiple outstanding requests.

OBJECT-TYPE

The object tmnxOamAncpTestTarget specifies how to interpret the value of the object tmnxOamAncpTestTargetId. If set to 'subscriberId', the object tmnxOamAncpTestTargetId is a printable character string which contains the subscriber-id. If set to 'ancpString', the object tmnxOamAncpTestTargetId is a printable character string which contains the ancp-string. If set to 'none', no value is specified, the object tmnxOamAncpTestTargetId is an empty string, and no ancp loopback test can be performed.

OBJECT-TYPE

The object tmnxOamAncpTestTargetId contains the ID of the subscriber for which the ANCP loopback test must be performed. The content of the field is interpreted as being a subscriber-id of max 32 chars (in case the object tmnxOamAncpTestTarget is set to 'subscriberId'), or as being an acnp-string of max 63 chars (in case the object tmnxOamAncpTestTarget is set to 'ancpString').

OBJECT-TYPE

The value of tmnxOamAncpTestcount specifies the number of messages the access node will use to test the circuit. If set to 0, the number of messages will be determined by the access node. Following settings are allowed: tmnxOamAncpTestcount tmnxOamAncpTestTimeout 0 0 1..32 0 1..32 1..255

OBJECT-TYPE

The value of tmnxOamAncpTestTimeout specifies the number of seconds the controlling node will wait for a reply. This timeout value is also sent to the access node. If set to 0, the access node will pick a default value, while the control node will assume a value of 255 seconds. Following settings are allowed: tmnxOamAncpTestcount tmnxOamAncpTestTimeout 0 0 1..32 0 1..32 1..255

OBJECT-TYPE

Defines a table for storing the results of an OAM ANCP test. The number of entries in this table for a test is limited to the results of 3 runs. An entry in this table is created when the result of an OAM ANCP test is determined. An entry is removed from this table when its corresponding tmnxOamPingCtlEntry is deleted.

OBJECT-TYPE

Defines an entry in the tmnxOamAncpTestHistoryTable. The first two index elements identify the tmnxOamPingCtlEntry that a tmnxOamAncpTestHistoryTable belongs to. The third index identifies a specific run of the OAM test. The fourth index element selects a single OAM ANCP test result.

OBJECT-TYPE

An entry in this table is created when the result of a OAM ANCP test is determined. The initial 2 instance identifier index values identify the tmnxOamPingCtlEntry that This ANCP test result belongs to. The tmnxOamAncpHistoryIndex element selects a single OAM probe result. The agent starts assigning tmnxOamAncpHistoryIndex values at 1 and wraps after exceeding the maximum possible value as defined by the limit of this object.

OBJECT-TYPE

The object tmnxOamAncpHistoryAncpString indicates the value of the ancp string used while running this ANCP test.

OBJECT-TYPE

The object tmnxOamAncpHistoryAccNodeCode indicates, if different from 0, the return code received from the ANCP access node. The value of this field corresponds to the error codes defined in the draft-wadhwa-gsmp-l2control-configuration-01: - 0x500 Specified access line does not exist - 0x501 Loopback test timed out - 0x502 Reserved - 0x503 DSL line status showtime - 0x504 DSL line status idle - 0x505 DSL line status silent - 0x506 DSL line status training - 0x507 DSL line integrity error - 0x508 DSLAM resource not available - 0x509 Invalid test parameter

OBJECT-TYPE

The object tmnxOamAncpHistoryAccNodeResult indicates, if different from 0, the return result received from the ANCP access node. The value of this field corresponds to the result codes defined in the draft-wadhwa-gsmp-l2control-configuration-01: { - 1: NoSuccessAck - 2: AckAll - 3: Success - 4: Failure - 5: More - 6: ReturnReceipt }

OBJECT-TYPE

The object tmnxOamAncpHistoryAccNodeRspStr indicates, if different from the empty string, the OAM-loopback-Test-Response-String received from the access node, as reply to the requested test.

OBJECT-TYPE

tmnxOamP2mpLspPingCtlTable (along with tmnxOamPingCtlTable) contains the configuration information for Point-to-Multipoint (P2MP) Label Switched Path (LSP) ping tests.

OBJECT-TYPE

tmnxOamP2mpLspPingCtlEntry (along with tmnxOamPingCtlEntry) contains the configuration information for a P2MP LSP Ping test. A row is created when the corresponding tmnxOamPingCtlTestMode is set to 'p2mpLspPing'. A row is destroyed when the corresponding tmnxOamPingCtlTable row is destroyed (using tmnxOamPingCtlRowStatus). The values in a particular row in this table cannot be changed when the corresponding tmnxOamPingCtlAdminStatus is 'enabled(1)'. The results of a 'p2mpLspPing' test are available using tmnxOamPingResultsEntry and tmnxOamPingHistoryEntry.

OBJECT-TYPE

The value of tmnxOamP2mpLspPingCtlLspName specifies the administrative name of the target RSVP P2MP Labeled Switch Path (LSP) for this OAM P2MP LSP Ping test. The LSP name must be unique within the base router instance. The objects tmnxOamP2mpLspPingCtlLspName and tmnxOamP2mpLspPingCtlP2MPId are mutually exclusive. An 'inconsistentValue' error is returned when attempting to set the value of the tmnxOamP2mpLspPingCtlLspName object to a non default value while the value of the tmnxOamP2mpLspPingCtlP2MPId object is already set to non default value. An 'inconsistentValue' error is returned when the value of tmnxOamPingCtlAdminStatus is set to 'enabled' if both the value of tmnxOamP2mpLspPingCtlLspName and the value of tmnxOamP2mpLspPingCtlP2MPId objects are set to default values.

OBJECT-TYPE

This parameter identifies an instance of a P2MP LSP, either a primary or secondary instance of a RSVP P2MP LSP Tree.

OBJECT-TYPE

Specifies the outermost label time-to-live value. This is an optional parameter for RSVP P2MP LSP. This parameter is not applicable for LDP P2MP LSP

OBJECT-TYPE

The value of tmnxOamP2mpLspPingCtlP2MPId specifies the identifier of a Point to Multipoint (LDP P2MP) Label Switch Path (LSP) for this OAM P2MP LSP ping test. The objects tmnxOamP2mpLspPingCtlP2MPId and tmnxOamP2mpLspPingCtlLspName are mutually exclusive. An 'inconsistentValue' error is returned when attempting to set the value of the tmnxOamP2mpLspPingCtlP2MPId object to a non default value while the value of the tmnxOamP2mpLspPingCtlLspName object is already set to non default value. An 'inconsistentValue' error is returned when the value of tmnxOamPingCtlAdminStatus is set to 'enabled' if both the value of tmnxOamP2mpLspPingCtlP2MPId and the value of tmnxOamP2mpLspPingCtlLspName objects are set to default values.

OBJECT-TYPE

The value of tmnxOamP2mpLspPingCtlSrcAddrType specifies the address type of tmnxOamP2mpLspPingCtlSrcAddr. When tmnxOamPingCtlAdminStatus is to set to 'enable', objects tmnxOamP2mpLspPingCtlSrcAddrType, tmnxOamP2mpLspPingCtlSrcAddr, tmnxOamP2mpLspPingCtlGrpAddrType, and tmnxOamP2mpLspPingCtlGrpAddr should all have default values or should all have non-default values.

OBJECT-TYPE

The value of tmnxOamP2mpLspPingCtlSrcAddr specifies the source address of a Point to Multipoint (LDP P2MP) Label Switch Path (LSP) for this OAM P2MP LSP ping test. This IP address must be valid unicast address. The objects tmnxOamP2mpLspPingCtlSrcAddr and tmnxOamP2mpLspPingCtlP2MPId are mutually exclusive. When tmnxOamPingCtlAdminStatus is to set to 'enable', objects tmnxOamP2mpLspPingCtlSrcAddrType, tmnxOamP2mpLspPingCtlSrcAddr, tmnxOamP2mpLspPingCtlGrpAddrType, and tmnxOamP2mpLspPingCtlGrpAddr should all have default values or should all have non-default values.

OBJECT-TYPE

The value of tmnxOamP2mpLspPingCtlGrpAddrType specifies the address type of tmnxOamP2mpLspPingCtlGrpAddr. When tmnxOamPingCtlAdminStatus is to set to 'enable', objects tmnxOamP2mpLspPingCtlSrcAddrType, tmnxOamP2mpLspPingCtlSrcAddr, tmnxOamP2mpLspPingCtlGrpAddrType, and tmnxOamP2mpLspPingCtlGrpAddr should all have default values or should all have non-default values.

OBJECT-TYPE

The value of tmnxOamP2mpLspPingCtlGrpAddr specifies the group address of a Point to Multipoint (LDP P2MP) Label Switch Path (LSP) for this OAM P2MP LSP ping test. This IP address must be valid multicast address. The objects tmnxOamP2mpLspPingCtlGrpAddr and tmnxOamP2mpLspPingCtlP2MPId are mutually exclusive. When tmnxOamPingCtlAdminStatus is to set to 'enable', objects tmnxOamP2mpLspPingCtlSrcAddrType, tmnxOamP2mpLspPingCtlSrcAddr, tmnxOamP2mpLspPingCtlGrpAddrType, and tmnxOamP2mpLspPingCtlGrpAddr should all have default values or should all have non-default values.

OBJECT-TYPE

The value of tmnxOamP2mpLspPingCtlOptionalTLV specifies which optional Type/Length/Value (TLV) structure to include in the MPLS echo request launched for the specified test. 'vpnRecursiveFec(2)' specifies the proprietary inclusion of an RFC 6512 'VPN-Recursive FEC Element'. 'vpnRecursiveFec(2)' is required to successfully ping a P2MP leaf with the following characteristics: 1. The path between the P2MP root and the targeted leaf is a Virtual Private Network (VPN), e.g. an SROS Virtual Private Routed Network (VPRN) service. And .. 2. The VPN has an RFC 4364 'Option B' boundary between two Border Gateway Protocol (BGP) Autonomous Systems. And .. 3. The leaf resides on an SROS node (with support for this object) on the far side of the boundary (with respect to the root). A leaf residing on a non-SROS node may not respond (or may respond with an error) when 'vpnRecursiveFec(2)' is specified. 'none(1)' specifies the inclusion of none of the optional TLVs described above.

OBJECT-TYPE

Defines the Nokia SROS OAM P2MP LSP ping IP Address Table for providing, via SNMP, the capability of performing Nokia SROS OAM 'p2mpLspPing' test operations. This table provides the ability to add multiple IP Address destinations for the 'p2mpLspPing' test. The results of these tests are stored in the tmnxOamPingResultsTable and the tmnxOamPingHistoryTable.

OBJECT-TYPE

Defines an entry in the tmnxOamP2mpLspPingIPAddressTable. The first index element, tmnxOamPingCtlOwnerIndex, is of type SnmpAdminString, a textual convention that allows for use of the SNMPv3 View-Based Access Control Model (RFC 2575 [11], VACM) and allows a management application to identify its entries. The second index, tmnxOamPingCtlTestIndex, enables the same management application to have multiple outstanding requests. The third and fourth index, tmnxOamP2mpLspPingCtlIpAddrType and tmnxOamP2mpLspPingCtlIpAddr enables the same management application to have multiple IP address destinations.

OBJECT-TYPE

The object tmnxOamP2mpLspPingCtlIpAddrIndex specifies the numerical row-order in the table.

OBJECT-TYPE

The object tmnxOamP2mpLspPingCtlIpRowStatus allows for the creation and deletion of rows in the tmnxOamP2mpLspPingIPAddressTable.

OBJECT-TYPE

The value of tmnxOamP2mpLspPingCtlIpAddrType specifies the type of Internet address stored in tmnxOamP2mpLspPingCtlIpAddr.

OBJECT-TYPE

The value of tmnxOamP2mpLspPingCtlIpAddr specifies a remote Internet address to send P2MP LSP Ping packets for a particular test.

OBJECT-TYPE

tmnxOamEthCfmPingCtlTable contains Ethernet CFM-specific configuration information for 'ethCfmLoopback', 'ethCfmTwoWayDelay', and 'ethCfmTwoWaySlm' tests. This table extends the tmnxOamPingCtlTable. A row is automatically created in this table when a row is created in tmnxOamPingCtlTable with tmnxOamPingCtlTestMode set to 'ethCfmLoopback', 'ethCfmTwoWayDelay', or 'ethCfmTwoWaySlm'. Deleting a row in tmnxOamPingCtlTable automatically deletes the row (if any) with the same index values in tmnxOamEthCfmPingCtlTable. Test results are stored in tmnxOamPingResultsTable and tmnxOamPingHistoryTable.

OBJECT-TYPE

tmnxOamEthCfmPingCtlEntry defines an entry in the tmnxOamEthCfmPingCtlTable. Each index is an object in tmnxOamPingCtlTable.

OBJECT-TYPE

The value of tmnxOamEthCfmPingCtlTgtMacAddr specifies the destination MAC address for the test. A non-zero destination MAC address is required in each test frame sent for the test. The tmnxOamEthCfmPingCtlTgtMacAddr must be assigned a non-default value. Otherwise, an attempt to administratively enable the test (using tmnxOamSaaCtlAdminStatus) will fail.

OBJECT-TYPE

The value of tmnxOamEthCfmPingCtlSrcMdIndex specifies the source CFM maintenance domain index for the test. Zero is the null CFM maintenance domain index.

OBJECT-TYPE

The value of tmnxOamEthCfmPingCtlSrcMaIndex specifies the source CFM maintenance association index for the test. Zero is the null CFM maintenance association index.

OBJECT-TYPE

The value of tmnxOamEthCfmPingCtlSrcMepId specifies the source Maintenance association End Point Identifier (MEP ID) for the test. Zero is the null MEP ID.

OBJECT-TYPE

The value of tmnxOamEthCfmPingCtlRemoteMepId specifies the remote Maintenance association End Point Identifier (MEP ID) for the test. A non-zero destination MAC address is required in each test frame sent for the test. The destination MAC address can be specified directly (using tmnxOamEthCfmPingCtlTgtMacAddr) or indirectly (using this object). Exactly one of tmnxOamEthCfmPingCtlTgtMacAddr and tmnxOamEthCfmPingCtlRemoteMepId must be assigned a non-default value. Otherwise, an attempt to administratively enable the test (using tmnxOamSaaCtlAdminStatus) will fail. Suppose this object is assigned a non-default value. Then, at the start of each test run, SROS reads TIMETRA-IEEE8021-CFM-MIB::tmnxDot1agCfmLearnedRmtMacAddr to find the destination MAC address to use for the test run. The following index values are used for the read: tmnxOamEthCfmPingCtlSrcMdIndex, tmnxOamEthCfmPingCtlSrcMaIndex, tmnxOamEthCfmPingCtlSrcMepId, tmnxOamEthCfmPingCtlRemoteMepId. If a destination MAC address is not found, no test frames will be sent for the test run. The number of frames to be sent during a test run is configured using tmnxOamPingCtlProbeCount. Configuring tmnxOamEthCfmPingCtlRemoteMepId (instead of tmnxOamEthCfmPingCtlDestMacAddr) has the following advantage: if the hardware hosting the test's far end is replaced (meaning a new destination MAC address is present), the test does not need to be reconfigured.

OBJECT-TYPE

tmnxOamVccvPgTgFec128CtlTable contains the target information for VCCV (Virtual Circuit Connectivity Verification) ping tests which switch to downstream FEC (Forward Equivalence Class) 128 segments.

OBJECT-TYPE

tmnxOamVccvPgTgFec128CtlEntry contains the target information for a VCCV ping test which switches to a downstream FEC 128 segment. The values in a row are used to fill a 'FEC 128 Pseudowire' sub-TLV (Type, Length, Value) within the 'Target FEC Stack' TLV within the launched VCCV ping request. A row is created when the test's tmnxOamVccvPingCtlSwitTgtFecType is set to 'fec128(2)'. A row is destroyed when the tmnxOamVccvPingCtlTable row is destroyed. All the objects in a row must be set in one SNMP Set PDU. Otherwise, the SNMP Set PDU will be rejected.

OBJECT-TYPE

The value of tmnxOamVccvPgTgFec128CtlSrcAddrT specifies the address type of tmnxOamVccvPgTgFec128CtlSrcAddr.

OBJECT-TYPE

The value of tmnxOamVccvPgTgFec128CtlSrcAddr specifies the value to be copied into the Sender's PE Address (Sender's Provider Edge Address) field of the 'FEC 128 Pseudowire' sub-TLV within the 'Target FEC Stack' TLV within the launched VCCV ping request.

OBJECT-TYPE

The value of tmnxOamVccvPgTgFec128CtlDstAddrT specifies the address type of tmnxOamVccvPgTgFec128CtlDstAddr.

OBJECT-TYPE

The value of tmnxOamVccvPgTgFec128CtlDstAddr specifies the value to be copied into the 'Remote PE Address' (Remote Provider Edge Address) field of the 'FEC 128 Pseudowire' sub-TLV within the 'Target FEC Stack' TLV within the launched VCCV ping request.

OBJECT-TYPE

The value of tmnxOamVccvPgTgFec128CtlPwId specifies the value to be copied into the 'PW ID' (Pseudowire Identifier) field of the 'FEC 128 Pseudowire' sub-TLV within the 'Target FEC Stack' TLV within the launched VCCV ping request. Zero indicates no Pseudowire Identifier has been configured.

OBJECT-TYPE

The value of tmnxOamVccvPgTgFec128CtlPwType specifies the value to be copied into the 'PW Type' (Pseudowire Type) field of the 'FEC 128 Pseudowire' sub-TLV within the 'Target FEC Stack' TLV within the launched VCCV ping request. The code points are defined in RFC 4446. SROS supports services corresponding to the following RFC 4446 PW Type code points. PW Type Description ------- --------------------------------------- 2 ATM AAL5 SDU VCC transport 3 ATM transparent cell transport 5 Ethernet 9 ATM n-to-one VCC cell transport 10 ATM n-to-one VPC cell transport 17 Structure-agnostic E1 over packet 18 Structure-agnostic T1 (DS1) over packet 21 CES over PSN basic mode 23 CES over PSN TDM with CAS Zero indicates no Pseudowire Type has been configured.

OBJECT-TYPE

tmnxOamVccvPgTgStaticCtlTable contains the target information for VCCV (Virtual Circuit Connectivity Verification) ping tests which switch to downstream static (i.e. MPLS-TP) segments.

OBJECT-TYPE

tmnxOamVccvPgTgStaticCtlEntry contains the target information for a VCCV ping test which switches to a downstream static (i.e. MPLS-TP) segment. The values in a row are used to fill a 'Static Pseudowire' sub-TLV (Type, Length, Value) within the 'Target FEC Stack' TLV within the launched VCCV ping request. A row is created when the test's tmnxOamVccvPingCtlSwitTgtFecType is set to 'static(3)'. A row is destroyed when the tmnxOamVccvPingCtlTable row is destroyed. All the objects in a row must be set in one SNMP Set PDU. Otherwise, the SNMP Set PDU will be rejected.

OBJECT-TYPE

The value of tmnxOamVccvPgTgStaticCtlAgi specifies the value to be copied into the 'Service Identifier' field of the 'Static Pseudowire' sub-TLV within the 'Target FEC Stack' TLV within the launched VCCV ping request. As specified in RFC 6426, the 'Service Identifier' field may be filled with an AGI (Attachment Group Identifier). The all-zeroes value indicates no Service Identifier has been configured.

OBJECT-TYPE

The value of tmnxOamVccvPgTgStaticCtlSaiiGlbl specifies the value to be copied into the 'Source Global ID' field of the 'Static Pseudowire' sub-TLV within the 'Target FEC Stack' TLV within the launched VCCV ping request. Zero indicates no Source Global ID has been configured.

OBJECT-TYPE

The value of tmnxOamVccvPgTgStaticCtlSaiiNode specifies the value to be copied into the 'Source Node ID' field of the 'Static Pseudowire' sub-TLV within the 'Target FEC Stack' TLV within the launched VCCV ping request. Zero indicates no Source Node ID has been configured.

OBJECT-TYPE

The value of tmnxOamVccvPgTgStaticCtlSaiiAcId specifies the value to be copied into the 'Source AC-ID' (Source Attachment Circuit Identifier) field of the 'Static Pseudowire' sub-TLV within the 'Target FEC Stack' TLV within the launched VCCV ping request. Zero indicates no Source AC-ID has been configured.

OBJECT-TYPE

The value of tmnxOamVccvPgTgStaticCtlTaiiGlbl specifies the value to be copied into the 'Destination Global ID' field of the 'Static Pseudowire' sub-TLV within the 'Target FEC Stack' TLV within the launched VCCV ping request. Zero indicates no Destination Global ID has been configured.

OBJECT-TYPE

The value of tmnxOamVccvPgTgStaticCtlTaiiNode specifies the value to be copied into the 'Destination Node ID' field of the 'Static Pseudowire' sub-TLV within the 'Target FEC Stack' TLV within the launched VCCV ping request. Zero indicates no Destination Node ID has been configured.

OBJECT-TYPE

The value of tmnxOamVccvPgTgStaticCtlTaiiAcId specifies the value to be copied into the 'Destination AC-ID' (Destination Attachment Circuit Identifier) field of the 'Static Pseudowire' sub-TLV within the 'Target FEC Stack' TLV within the launched VCCV ping request. Zero indicates no Destination AC-ID has been configured.

OBJECT-TYPE

tmnxOamVxlanPingCtlTable (along with tmnxOamPingCtlTable) contains the configuration information for VXLAN (Virtual Extensible Local Area Network) ping tests.

OBJECT-TYPE

tmnxOamVxlanPingCtlEntry (along with tmnxOamPingCtlEntry) contains the configuration information for a VXLAN ping test. A row is created when the corresponding tmnxOamPingCtlTestMode is set to 'vxlanPing'. A row is destroyed when the corresponding tmnxOamPingCtlTable row is destroyed (using tmnxOamPingCtlRowStatus). The values in a particular row in this table cannot be changed when the corresponding tmnxOamPingCtlAdminStatus is 'enabled(1)'.

OBJECT-TYPE

The value of tmnxOamVxlanPingCtlNetworkId specifies the VXLAN Network Identifier (VNI) of the VXLAN network to be tested. The value is copied into the VXLAN Network Identifier field of the VXLAN Header of the launched OAM echo request. Zero indicates no VXLAN Network Identifier has been configured. The test will fail if tmnxOamVxlanPingCtlNetworkId is zero.

OBJECT-TYPE

The value of tmnxOamVxlanPingCtlReplyMode specifies the encapsulation to be used in the OAM echo reply. The value is copied into the Reply Mode field of the Generic Overlay OAM structure of the launched OAM echo request. The replying node uses the value to choose the encapsulation of the OAM echo reply. Code points: udp(2) - reply using an IPv4 UDP packet overlay(3) - reply via the overlay segment. The Jain draft's 'Do Not Reply' option (i.e. the Reply Mode with code point 1) is not supported.

OBJECT-TYPE

The value of tmnxOamVxlanPingCtlIFlag specifies the I flag value to be used for the test. The value is copied into the I flag field of the VXLAN Header of the launched OAM echo request.

OBJECT-TYPE

The value of tmnxOamVxlanPingCtlTestId specifies a unique identifier for the test. The value is copied into the Originator Handle field of the Generic Overlay OAM structure of the launched OAM echo request. Zero indicates no VXLAN Test Identifier has been configured. The test will fail if tmnxOamVxlanPingCtlTestId is zero.

OBJECT-TYPE

The value of tmnxOamVxlanPingCtlOutSrcUdpPt specifies the outer source UDP port to be used for the test. If tmnxOamVxlanPingCtlOutSrcUdpPt is zero, an SROS-computed UDP port number is copied into the Source Port field of the Outer UDP Header of the launched OAM echo request. If tmnxOamVxlanPingCtlOutSrcUdpPt is non-zero, the given value is copied into the Source Port field of the Outer UDP Header of the launched OAM echo request.

OBJECT-TYPE

The value of tmnxOamVxlanPingCtlOutIpTtl specifies the outer IP Time To Live value to be used for the test. The value is copied into the Time To Live field of the Outer IPv4 Header of the launched OAM echo request.

OBJECT-TYPE

The value of tmnxOamVxlanPingCtlInL2DestMac specifies the inner Destination MAC address to be used for the test. The value is copied into the Inner Destination MAC Address field of the Inner Ethernet Header of the launched OAM echo request.

OBJECT-TYPE

The value of tmnxOamVxlanPingCtlInIpSrcAddrT specifies the type of address in tmnxOamVxlanPingCtlInIpSrcAddr.

OBJECT-TYPE

The value of tmnxOamVxlanPingCtlInIpSrcAddr specifies the inner source IP address to be used for the test. The value is copied into the Source IP Address field of the Inner IP Header of the launched OAM Echo request. If this object has its default value when the test is started, SROS selects a value to be used as the inner source IP address.

OBJECT-TYPE

The value of tmnxOamVxlanPingCtlInIpDstAddrT specifies the type of address in tmnxOamVxlanPingCtlInIpDstAddr.

OBJECT-TYPE

The value of tmnxOamVxlanPingCtlInIpDstAddr specifies the inner destination IP address to be used for the test. The value is copied into the Destination IP Address field of the Inner IP Header of the launched OAM Echo request. Addresses in the address block 127.0.0.0/8 are accepted. The default address is 127.0.0.1.

OBJECT-TYPE

The value of tmnxOamVxlanPingCtlEndSysMacAddr specifies the end system MAC address to be verified by the test. The value is copied into the MAC Address #1 field of the End-System MAC Sub-TLV of the launched OAM Echo request.

OBJECT-TYPE

The value of tmnxOamVxlanPingCtlReflectPad specifies whether or not to copy the pad TLV from the OAM echo request to the OAM echo response. The combination of tmnxOamVxlanPingCtlReflectPad='true(1)' and tmnxOamPingCtlSize=0 is rejected, because tmnxOamPingCtlSize=0 indicates there is no pad TLV to be copied. The combination of tmnxOamVxlanPingCtlReflectPad='true(1)' and tmnxOamVxlanPingCtlReplyMode='udp(2)' is rejected.

OBJECT-TYPE

tmnxOamVxlanPingHistoryTable (along with tmnxOamPingHistoryTable) contains the information obtained from Virtual Extensible Local Area Network (VXLAN) Echo Reply PDUs.

OBJECT-TYPE

tmnxOamVxlanPingHistoryEntry (along with tmnxOamPingHistoryEntry) contains the information obtained from one VXLAN Echo Reply PDU. A row is created when a VXLAN Echo Reply PDU (associated with a managed 'vxlanPing' test) arrives. A row is destroyed when the corresponding tmnxOamPingHistoryEntry is destroyed. The first two indices specify a 'vxlanPing' test. The third index specifies a test run (started using tmnxOamPingCtlAdminStatus). The fourth index specifies a VXLAN Echo Reply PDU.

OBJECT-TYPE

The value of tmnxOamVxlanPingHistReturnCode indicates the value copied from the Return Code field of the Generic Overlay OAM Packet structure of the VXLAN Echo Reply PDU. Code points include (but are not restricted to) the following. Value Interpretation ----- ------------------------------- 0 no return code 1 malformed echo request received 2 overlay segment not present 3 overlay segment not operational 4 OK

OBJECT-TYPE

The value of tmnxOamVxlanPingHistRtrnSubCode indicates the value copied from the Return Subcode field of the Generic Overlay OAM Packet structure of the VXLAN Echo Reply PDU.

OBJECT-TYPE

The value of tmnxOamVxlanPingHistValidationRC indicates the value copied from the 'Return Code #1' field of the 'Sub-TLV for Validating End-System MAC Address' of the VXLAN Echo Reply PDU.

OBJECT-TYPE

The value of tmnxOamVxlanPingHistNetworkId indicates the value of the VXLAN Network Identifier (VNI) field of the VXLAN Header of the VXLAN Echo Reply PDU.

OBJECT-TYPE

The value of tmnxOamVxlanPingHistOutIpTtl indicates the value of the Time To Live field of the Outer IPv4 Header of the VXLAN Echo Reply PDU.

OBJECT-TYPE

tmnxOamBfdOnLspPingResultsTable contains the information obtained during the RFC 5884 procedures used to bootstrap and periodically verify Bidirectional Forwarding Detection (BFD) sessions on Label Switched Paths (LSPs). The bootstrap and verification procedures use LSP ping echo request and reply packets.

OBJECT-TYPE

tmnxOamBfdOnLspPingResultsEntry contains the information obtained during the RFC 5884 procedures used to bootstrap and periodically verify a BFD session on an LSP. A row is created when an RFC 5884 BFD-on-LSP session starts its bootstrap procedure. A row is destroyed when the BFD-on-LSP session disconnects.

OBJECT-TYPE

The value of tmnxOamBfdOnLspLocalBfdDiscrim specifies the local BFD discriminator for a BFD-on-LSP session. The local discriminator is this system's identifier of the BFD session.

OBJECT-TYPE

The value of tmnxOamBfdOnLspRemoteBfdDiscrim indicates the remote BFD discriminator for the BFD-on-LSP session identified by tmnxOamBfdOnLspLocalBfdDiscrim. The remote discriminator is the far end system's identifier of the BFD session. Zero is returned if the bootstrap has not completed successfully.

OBJECT-TYPE

The value of tmnxOamBfdOnLspRemoteAddressType indicates the type of address stored in tmnxOamBfdOnLspRemoteAddress.

OBJECT-TYPE

The value of tmnxOamBfdOnLspRemoteAddress (in conjunction with tmnxOamBfdOnLspRemoteAddressType) indicates the IP address of the node which sent the most recent LSP ping echo reply for the BFD-on-LSP session identified by tmnxOamBfdOnLspLocalBfdDiscrim. If the LSP is operating correctly, the reply is sent by the far end of the BFD-on-LSP session.

OBJECT-TYPE

The value of tmnxOamBfdOnLspLspName indicates the LSP name associated with the Resource Reservation Protocol (RSVP) BFD-on-LSP session identified by tmnxOamBfdOnLspLocalBfdDiscrim. LSP names are configured using TIMETRA-MPLS-MIB::vRtrMplsLspName. When the value of tmnxOamBfdOnLspFecType is not 'rsvp(1)', the value of this object is the empty string.

OBJECT-TYPE

The value of tmnxOamBfdOnLspPingReturnCode indicates the status of the most recent LSP ping echo reply received for the BFD-on-LSP session identified by tmnxOamBfdOnLspLocalBfdDiscrim.

OBJECT-TYPE

The value of tmnxOamBfdOnLspPingReturnSubcode indicates the value present in the RFC 4379 Return Subcode (RSC) field of the most recent LSP ping echo reply for the BFD-on-LSP session identified by tmnxOamBfdOnLspLocalBfdDiscrim.

OBJECT-TYPE

The value of tmnxOamBfdOnLspPingTxCount indicates the number of LSP ping echo request packets sent for the BFD-on-LSP session identified by tmnxOamBfdOnLspLocalBfdDiscrim.

OBJECT-TYPE

The value of tmnxOamBfdOnLspPingRxCount indicates the number of LSP ping echo reply packets received for the BFD-on-LSP session identified by tmnxOamBfdOnLspLocalBfdDiscrim.

OBJECT-TYPE

The value of tmnxOamBfdOnLspPathState indicates the state of the path hosting the RSVP BFD-on-LSP session identified by tmnxOamBfdOnLspLocalBfdDiscrim. Code points: unknown (1) - the state of the path hosting the BFD-on-LSP session is unknown active (2) - the BFD-on-LSP session is running on the active path inactive (3) - the BFD-on-LSP session is running on the inactive path When the value of tmnxOamBfdOnLspFecType is not 'rsvp(1)', the value of this object is 'unknown(1)'.

OBJECT-TYPE

The value of tmnxOamBfdOnLspPingTxInterval indicates the transmission interval for LSP ping request PDUs sent during periodic verification of the BFD-on-LSP session identified by tmnxOamBfdOnLspLocalBfdDiscrim. This value is configured using TIMETRA-MPLS-MIB::vRtrMplsLspBfdPingIntvl. A read-only copy of the value is available here for the convenience of a manager wishing to read the value using a local BFD discriminator as the index.

OBJECT-TYPE

The value of tmnxOamBfdOnLspBootStrRetryCount indicates the current number of retries started while attempting to bootstrap the BFD-on-LSP session identified by tmnxOamBfdOnLspLocalBfdDiscrim. If the bootstrap completed successfully on the first attempt, zero is returned.

OBJECT-TYPE

The value of tmnxOamBfdOnLspFecType indicates the Forwarding Equivalence Class (FEC) type of the BFD-on-LSP session identified by tmnxOamBfdOnLspLocalBfdDiscrim. This release supports code points 'rsvp(1)' and 'ldp(2)'.

OBJECT-TYPE

The value of tmnxOamBfdOnLspPrefixType indicates the type of address stored in tmnxOamBfdOnLspPrefix.

OBJECT-TYPE

The value of tmnxOamBfdOnLspPrefix indicates (in conjunction with tmnxOamBfdOnLspPrefixType and tmnxOamBfdOnLspPrefixLen) the prefix which identifies the Label Distribution Protocol (LDP) LSP which hosts the BFD-on-LSP session identified by tmnxOamBfdOnLspLocalBfdDiscrim. When tmnxOamBfdOnLspFecType is 'rsvp(1)', the three prefix objects have the following values. tmnxOamBfdOnLspPrefixType : 'unknown(0)' tmnxOamBfdOnLspPrefix : empty tmnxOamBfdOnLspPrefixLen : 0.

OBJECT-TYPE

The value of tmnxOamBfdOnLspPrefixLen indicates the number of significant bits in the prefix defined by tmnxOamBfdOnLspPrefixType, tmnxOamBfdOnLspPrefix, and tmnxOamBfdOnLspPrefixLen.

OBJECT-TYPE

The value of tmnxOamBfdOnLspSourceAddressType indicates the type of address stored in tmnxOamBfdOnLspSourceAddress.

OBJECT-TYPE

The value of tmnxOamBfdOnLspSourceAddress (in conjunction with tmnxOamBfdOnLspSourceAddressType) indicates the source IP address of the BFD-on-LSP session identified by tmnxOamBfdOnLspLocalBfdDiscrim.

OBJECT-TYPE

The value of tmnxOamBfdOnLspOperState indicates the operational state (with respect to the RFC 5884 LSP Ping procedures) of the BFD-on-LSP session identified by tmnxOamBfdOnLspLocalBfdDiscrim. Code Points 'bootstrapInProg(1)' - the session is being bootstrapped using LSP ping, as described in RFC 5884 Section 6. 'bootstrappedNoPeriodicVerif(2)' - the bootstrap completed successfully. This is the success state for a session which has periodic verification of the LSP (using LSP ping) disabled. Periodic verification is disabled by setting the session's LSP ping interval (e.g. TIMETRA-LDP-NG-MIB::vRtrLdpNgBfdOnLspPfxListPingIntv) to zero. 'bootstrappedSendingPeriodicVerif(3)' - the bootstrap completed successfully, and the session is sending LSP pings to periodically verify the LSP (as described in RFC 5884 Section 3.2). This is the success state for a session which has periodic verification of the session enabled. The BFD-level operational state of a BFD-on-LSP session is given by TIMETRA-BFD-MIB::tmnxBfdOnLspSessOperState.

OBJECT-TYPE

tmnxOamVxlanPingResultsTable contains results of VXLAN (Virtual Extensible Local Area Network) ping tests.

OBJECT-TYPE

tmnxOamVxlanPingResultsEntry contains results of one 'vxlanPing' test run. tmnxOamPingResultsEntry contains additional results for the test run. A tmnxOamVxlanPingResultsEntry is created/destroyed when a tmnxOamPingResultsEntry is created/destroyed for a 'vxlanPing' test. tmnxOamPingCtlEntry and tmnxOamVxlanPingCtlEntry are used to configure and start a 'vxlanPing' test. tmnxOamVxlanPingHistoryEntry contains per-probe results for a 'vxlanPing' test run.

OBJECT-TYPE

The value of tmnxOamVxlanPingResOutSrcAddrTyp indicates the address type of tmnxOamVxlanPingResOutSrcAddress.

OBJECT-TYPE

The value of tmnxOamVxlanPingResOutSrcAddress indicates the outer source IP address (as selected by SROS) used for the specified 'vxlanPing' test run. The value was copied into the Outer Source IPv4 Address field of the VXLAN Header of each OAM echo request launched for the specified test run. IPv6 may be supported in a future release.

OBJECT-IDENTITY

OBJECT-TYPE

The value of tmnxOamBfdOnLspSessBootstrInProg indicates the current number of BFD-on-LSP sessions with OAM operational state (i.e. tmnxOamBfdOnLspOperState) 'bootstrapInProg(1)'.

OBJECT-TYPE

The value of tmnxOamBfdOnLspSessBootstrNoPV indicates the current number of BFD-on-LSP sessions with OAM operational state (i.e. tmnxOamBfdOnLspOperState) 'bootstrappedNoPeriodicVerif(2)'.

OBJECT-TYPE

The value of tmnxOamBfdOnLspSessBootstrSendPV indicates the current number of BFD-on-LSP sessions with OAM operational state (i.e. tmnxOamBfdOnLspOperState) 'bootstrappedSendingPeriodicVerif(3)'.

OBJECT-TYPE

tmnxOamBierPingCtlTable (along with tmnxOamPingCtlTable) contains the configuration information for BIER (Bit Index Explicit Replication) ping tests.

OBJECT-TYPE

tmnxOamBierPingCtlEntry (along with tmnxOamPingCtlEntry) contains the configuration information for a BIER ping test. A row is created when the corresponding tmnxOamPingCtlTestMode is set to 'bierPing'. A row is destroyed when the corresponding tmnxOamPingCtlTable row is destroyed (using tmnxOamPingCtlRowStatus). The values in a particular row in this table cannot be changed when the corresponding tmnxOamPingCtlAdminStatus is 'enabled(1)'.

OBJECT-TYPE

The value of tmnxOamBierPingCtlSubDomain specifies the BIER sub-domain to be tested. Zero indicates the default sub-domain.

OBJECT-TYPE

The value of tmnxOamBierPingCtlBfrId specifies the identifier of the Bit-Forwarding Router (BFR) to be pinged. The BFR-ID must be a member of the tested sub-domain (as configured using tmnxOamBierPingCtlSubDomain). Otherwise, the test will fail. Zero indicates no BFR-ID has been configured. There are three methods to configure the destination(s) to be pinged: 1. tmnxOamBierPingCtlBfrId. 2. tmnxOamBierPingCtlBfrIdStart, tmnxOamBierPingCtlBfrIdEnd. 3. tmnxOamBierPingBfrPfxCtlAddrType, tmnxOamBierPingBfrPfxCtlAddress. Exactly one of the methods must be used. Otherwise, the test will fail.

OBJECT-TYPE

The value of tmnxOamBierPingCtlBfrIdStart specifies the start of a contiguous range of Bit-Forwarding Router (BFR) identifiers to be pinged. tmnxOamBierPingCtlBfrIdEnd specifies the end of the range. Each BFR-ID in the range must be a member of the tested sub-domain (as configured using tmnxOamBierPingCtlSubDomain). Otherwise, the test will fail. Zero indicates no start for the BFR-ID range has been configured. The following objects must be set together in one SNMP Set PDU: tmnxOamBierPingCtlBfrIdStart, tmnxOamBierPingCtlBfrIdEnd. There are three methods to configure the destination(s) to be pinged: 1. tmnxOamBierPingCtlBfrId. 2. tmnxOamBierPingCtlBfrIdStart, tmnxOamBierPingCtlBfrIdEnd. 3. tmnxOamBierPingBfrPfxCtlAddrType, tmnxOamBierPingBfrPfxCtlAddress. Exactly one of the methods must be used. Otherwise, the test will fail.

OBJECT-TYPE

The value of tmnxOamBierPingCtlBfrIdEnd specifies the end of a contiguous range of Bit-Forwarding Router (BFR) identifiers to be pinged. tmnxOamBierPingCtlBfrIdStart specifies the start of the range. Each BFR-ID in the range must be a member of the tested sub-domain (as configured using tmnxOamBierPingCtlSubDomain). Otherwise, the test will fail. Zero indicates no end for the BFR-ID range has been configured. The following objects must be set together in one SNMP Set PDU: tmnxOamBierPingCtlBfrIdStart, tmnxOamBierPingCtlBfrIdEnd. There are three methods to configure the destination(s) to be pinged: 1. tmnxOamBierPingCtlBfrId. 2. tmnxOamBierPingCtlBfrIdStart, tmnxOamBierPingCtlBfrIdEnd. 3. tmnxOamBierPingBfrPfxCtlAddrType, tmnxOamBierPingBfrPfxCtlAddress. Exactly one of the methods must be used. Otherwise, the test will fail.

OBJECT-TYPE

The value of tmnxOamBierPingCtlTtl specifies the MPLS Time To Live (TTL) to be used for the test.

OBJECT-TYPE

tmnxOamBierPingBfrPfxCtlTable contains IP destination addresses (i.e. Bit-Forwarding Router (BFR) prefixes) for BIER ping tests.

OBJECT-TYPE

tmnxOamBierPingBfrPfxCtlEntry contains one BFR prefix. A BIER ping test can have several BFR prefixes. Each BFR prefix is an IP destination address for the test. A row is created/destroyed using tmnxOamBierPingBfrPfxCtlRowState. Rows in this table belonging to a particular test cannot be added, changed, or deleted when the test's tmnxOamPingCtlAdminStatus is 'enabled(1)'.

OBJECT-TYPE

The value of tmnxOamBierPingPfxIndex specifies a BFR prefix index. The index allows one test to have several BFR prefixes.

OBJECT-TYPE

The value of tmnxOamBierPingBfrPfxCtlRowState specifies the status of the row for the specified BFR prefix.

OBJECT-TYPE

The value of tmnxOamBierPingBfrPfxCtlAddrType specifies the address type of tmnxOamBierPingBfrPfxCtlAddress.

OBJECT-TYPE

The value of tmnxOamBierPingBfrPfxCtlAddress specifies a BFR prefix used as a destination address for a BIER ping test. There are three methods to configure the destination(s) to be pinged: 1. tmnxOamBierPingCtlBfrId. 2. tmnxOamBierPingCtlBfrIdStart, tmnxOamBierPingCtlBfrIdEnd. 3. tmnxOamBierPingBfrPfxCtlAddrType, tmnxOamBierPingBfrPfxCtlAddress. Exactly one of the methods must be used. Otherwise, the test will fail.

OBJECT-TYPE

tmnxOamBierPingHistoryTable (along with tmnxOamPingHistoryTable) contains the per-probe results for Bit Index Explicit Replication (BIER) ping tests.

OBJECT-TYPE

tmnxOamBierPingHistoryEntry (along with tmnxOamPingHistoryEntry) contains the results for one BIER ping probe. A row is created/destroyed when the corresponding tmnxOamPingHistoryEntry is created/destroyed. The first two indices specify a 'bierPing' test. The third index specifies a test run (started using tmnxOamPingCtlAdminStatus). The fourth index specifies a Bit-Forwarding Router (BFR) with results to report. All the indices match the corresponding tmnxOamPingHistoryEntry indices.

OBJECT-TYPE

The value of tmnxOamBierPingHistoryBfrId indicates the identifier of the Bit-Forwarding Router (BFR) targeted by the launched BIER Echo Request. Zero is returned if the BFR-ID cannot be determined.

OBJECT-TYPE

The value of tmnxOamBierPingHistoryBfrPfxType indicates the IP address type of the address read using tmnxOamBierPingHistoryBfrPfx.

OBJECT-TYPE

The value of tmnxOamBierPingHistoryBfrPfx indicates the IP address of the Bit-Forwarding Router (BFR) targeted by the launched BIER Echo Request.

OBJECT-TYPE

The value of tmnxOamBierPingHistoryReturnCode indicates the value copied from the Return Code field of the BIER Echo Reply PDU. Zero (i.e. 'No Return Code') is returned if a BIER Echo Reply PDU did not arrive (e.g. in the case of a timeout).

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-TYPE

The maximum number of concurrent active trace route requests that are allowed within an agent implementation. A value of 0 for this object implies that there is no limit for the number of concurrent active requests in effect.

OBJECT-TYPE

tmnxOamTrCtlTable contains configuration and status information for trace tests.

OBJECT-TYPE

tmnxOamTrCtlEntry contains configuration and status information for one trace test. Rows are created/destroyed using tmnxOamTrCtlRowStatus. The test's test type (e.g. 'lspTraceRoute(2)') is configured using tmnxOamTrCtlTestMode. Depending on the test type, configuration specific to the test type may reside in a child table (e.g. tmnxOamLspTrCtlTable). Test results reside in tmnxOamTrResultsTable,tmnxOamTrProbeHistoryTable, tmnxOamTrHopsTable, and a set of tables specific to the test type (e.g. tmnxOamLspTrMapTable, tmnxOamMcastTrRespTable).

OBJECT-TYPE

The value of tmnxOamTrCtlOwnerIndex specifies the owner name of the test.

OBJECT-TYPE

The value of tmnxOamTrCtlTestIndex specifies the test name of the test. The test is identified by the owner name and the test name. One owner typically owns several tests. This indexing method ensures tests created by several owners have unique indices.

OBJECT-TYPE

The value of tmnxOamTrCtlRowStatus specifies the status of the row for the specified trace test. Deleting a row deletes all the child rows with the same owner name and test name, including additional configuration rows (e.g. tmnxOamLspTrCtlTable), and rows containing test results (e.g. tmnxOamTrHopsTable).

OBJECT-TYPE

The storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write access to any columnar objects in the row. This object was marked obsolete in SROS Release 14.0 R1. There is no replacement object.

OBJECT-TYPE

The purpose of this object is to provide a descriptive name of the Nokia SROS OAM Trace Route test. This object was marked obsolete in SROS Release 14.0 R1. There is no replacement object.

OBJECT-TYPE

The value of tmnxOamTrCtlTestMode specifies the type of trace route test defined by this row. Code points: 'bierTrace' - Bit Index Explicit Replication (BIER) trace route test. 'ethCfmLinkTrace' - Ethernet Connectivity Fault Management (CFM) trace route test. 'icmpTraceRoute' - traceroute test (receives Internet Control Message Protocol (ICMP) responses). 'ldpTreeTrace' - Label Distribution Protocol (LDP) Tree Trace test. 'lspTraceRoute' - Label Switched Path (LSP) trace route test. 'macTraceRoute' - Ethernet Media Access Control (MAC) trace route test. 'mcastTraceRoute' - mtrace test (i.e. IP multicast trace route test, using IETF draft-ietf-idmr-traceroute-ipm (IGMP-based)). OR Mtrace2 test (i.e. IP multicast trace route test, using IETF draft-ietf-mboned-mtrace-v2 (UDP-based)). 'none' - no test type. 'p2mpLspTrace' - Point-to-Multipoint Label Switched Path (LSP) trace route test. 'vccvTraceRoute' - Virtual Circuit Connectivity Verification (VCCV) trace route test. 'vprnTraceRoute' - Virtual Private Routed Network (VPRN) trace route test. When tmnxOamTrCtlTestMode is set, SROS may automatically create a same-INDEX row in a table used to configure objects specific to the test type (as shown in the following table). tmnxOamTrCtlTestMode Auto-Gen Row for Additional Configuration -------------------- ----------------------------------------- 'bierTrace' tmnxOamBierTrCtlTable 'ethCfmLinkTrace' tmnxOamEthCfmTrCtlTable 'icmpTraceRoute' none 'ldpTreeTrace' tmnxOamLTtraceCtlTable 'lspTraceRoute' tmnxOamLspTrCtlTable 'macTraceRoute' tmnxOamMacTrCtlTable 'mcastTraceRoute' tmnxOamMcastTrCtlTable 'p2mpLspTrace' tmnxOamP2mpLspTrCtlTable 'vccvTraceRoute' tmnxOamVccvTrCtlTable 'vprnTraceRoute' tmnxOamVprnTrCtlTable The support for Service Assurance Agent (SAA) tests (i.e. tests with tmnxOamSaaCtlTable rows) and OAM tests (i.e. tests without tmnxOamSaaCtlTable rows) varies with the test type, as shown in the following table. tmnxOamTrCtlTestMode SAA Supported OAM Supported -------------------- ------------- ------------- 'bierTrace' No Yes 'ethCfmLinkTrace' Yes No 'icmpTraceRoute' Yes Yes 'ldpTreeTrace' No Yes 'lspTraceRoute' Yes Yes 'macTraceRoute' Yes Yes 'mcastTraceRoute' No Yes 'p2mpLspTrace' No Yes 'vccvTraceRoute' Yes Yes 'vprnTraceRoute' Yes Yes

OBJECT-TYPE

The value of tmnxOamTrCtlAdminStatus specifies the administrative state of the specified trace test. An attempt to set tmnxOamTrCtlAdminStatus to 'enabled' will fail if the objects required by the trace test have not been set. When this object has the value 'enabled' an attempt to modify any of the test's configurable objects will fail. Upon completion of a trace test, the agent resets the value of this object to 'disabled'.

OBJECT-TYPE

The value of tmnxOamTrCtlFcName specifies the forwarding class to be used when launching the probe(s). The forwarding class name must be present in the index column of TIMETRA-QOS-MIB::tFCNameTable. This object is optional. As shown in the following table 1. This object is applicable to a subset of the test types, and 2. The default forwarding class depends on the test type. tmnxOamTrCtlTestMode Applicable? Default -------------------- ----------- ------- bierTrace yes 'be' ethCfmLinkTrace yes 'nc' ldpTreeTrace yes 'be' lspTraceRoute yes 'be' macTraceRoute yes 'be' p2mpLspTrace yes 'be' vccvTraceRoute yes 'be' vprnTraceRoute yes 'be' otherwise no N/A For 'ethCfmLinkTrace', the forwarding class depends on whether the request is configured to egress on a network port or an access port. In the network port case, the forwarding class is the forwarding class of the pseudowire. In the access port case, the forwarding class is that of the SAP's egress encapsulation policy. For 'lspTraceRoute' this is the forwarding class of the LSP tunnel. For 'macTraceRoute' this is the forwarding class of the SDP encapsulation. For 'p2mpLspTrace' this is the forwarding class of the P2MP LSP tree. If forwarding classes are mapped by the applicable QoS policy, the probe(s) may be launched using a different forwarding class than the forwarding class specified by this object.

OBJECT-TYPE

The value of tmnxOamTrCtlProfile specifies the profile to be used with the forwarding class specified in tmnxOamTrCtlFcName. This object is optional. As shown in the following table 1. This object is applicable to a subset of the test types, and 2. The default profile value depends on the test type. tmnxOamTrCtlTestMode Applicable? Default -------------------- ----------- ------- bierTrace yes 'out(2)' ethCfmLinkTrace yes 'in(1)' ldpTreeTrace yes 'out(2)' lspTraceRoute yes 'out(2)' macTraceRoute yes 'out(2)' p2mpLspTrace yes 'out(2)' vccvTraceRoute yes 'out(2)' vprnTraceRoute yes 'out(2)' otherwise no N/A

OBJECT-TYPE

This object was obsoleted in release 4.0 and replaced with InetAddress objects tmnxOamTrCtlTgtAddrType and tmnxOamTrCtlTgtAddress.

OBJECT-TYPE

The value of tmnxOamTrCtlServiceId specifies the service ID of the service being tested. The applicability of tmnxOamTrCtlServiceId varies with the test type, as shown in the following table. tmnxOamTrCtlTestMode Applicability Related Virtual Router Object -------------------- ------------- ----------------------------- 'icmpTraceRoute' optional tmnxOamTrCtlVRtrID 'macTraceRoute' mandatory none 'mcastTraceRoute' optional tmnxOamMcastTrCtlVRtrID 'vprnTraceRoute' mandatory none otherwise not applicable none When tmnxOamTrCtlServiceId is mandatory, a non-zero value must be provided. When tmnxOamTrCtlServiceId is optional, it is used to specify a VPRN service. The test must use the VPRN service's virtual router. When a related virtual router object is shown, the interaction is described in the DESCRIPTION clause of the listed object. When tmnxOamTrCtlTestMode is 'icmpTraceRoute', tmnxOamTrCtlRouterInstanceName is the preferred object for specifying the service to be tested. Service IDs larger than 2147483647 are internal, so they are excluded from the range. The default value is the null service ID.

OBJECT-TYPE

The value of tmnxOamTrCtlDataSize specifies (directly or indirectly) the size of the trace PDU. The relevance of tmnxOamTrCtlDataSize varies with the test type, as shown in the following table. tmnxOamTrCtlTestMode Relevant? -------------------- --------- 'lspTraceRoute' yes 'macTraceRoute' yes 'p2mpLspTrace' yes 'vccvTraceRoute' yes 'vprnTraceRoute' yes otherwise no If the request PDU required for the specified test is larger than the PDU size indicated by tmnxOamTrCtlDataSize, SROS sends the smallest valid PDU larger than the size indicated. For example, if tmnxOamTrCtlDataSize is 1 when a 'vccvTraceRoute' test is started on a FEC 128 pseudowire, an 88 octet request PDU is sent. Trace route requests are sent unfragmented.

OBJECT-TYPE

The value of tmnxOamTrCtlTimeOut specifies the timeout for an OAM trace probe. For 'ethCfmLinkTrace', this is the timeout for the whole test. The minimum, maximum, and default values of this object vary with the test type, as follows. tmnxOamTrCtlTestMode Minimum Maximum Default -------------------- ------- ------- ------- 'icmpTraceRoute' N/A N/A N/A 'ethCfmLinkTrace' 1 10 5 otherwise 1 60 3 If tmnxOamTrCtlTestMode is 'ethCfmLinkTrace', the value of tmnxOamTrCtlTimeOut must be less than or equal to the value of tmnxOamTrCtlInterval.

OBJECT-TYPE

The value of tmnxOamTrCtlProbesPerHop specifies the number of OAM trace probes to send per TTL. This object is not configurable for 'icmpTraceRoute'; a default value of 3 is used.

OBJECT-TYPE

The value of tmnxOamTrCtlMaxTtl specifies the maximum time-to-live value. This parameter is optional. The applicability and default vary with tmnxOamTrCtlTestMode, as shown in the following table. tmnxOamTrCtlTestMode Applicable? Default -------------------- ----------- ------- 'bierTrace' yes 30 'ethCfmLinkTrace' yes 64 'icmpTraceRoute' yes 30 'ldpTreeTrace' yes 30 'lspTraceRoute' yes 30 'macTraceRoute' yes 4 'mcastTraceRoute' no N/A 'p2mpLspTrace' yes 30 'vccvTraceRoute' yes 8 'vprnTraceRoute' yes 4

OBJECT-TYPE

The value of tmnxOamTrCtlInitialTtl specifies the initial TTL value to use. This enables bypassing the initial (often well known) portion of a path. This parameter is optional. This parameter is not configurable for 'icmpTraceRoute'; the default value 1 is used. This parameter is not used with 'ethCfmLinkTrace'. This parameter does not affect the test execution for 'vccvTraceRoute', but applications may use the value to filter results for that test type.

OBJECT-TYPE

The value of tmnxOamTrCtlDSField specifies the value to load in the Type of Service (TOS) octet or the Traffic Class (TC) octet of the launched ICMP echo request(s). The TOS octet is a field in the IPv4 packet header. The TC octet is a field in the IPv6 packet header. The value in the TOS or TC octet may influence the route, latency, and/or probability of loss for the echo request (and, by inference, for the associated data flow). This object is supported when tmnxOamTrCtlTestMode is 'icmpTraceRoute'. Otherwise, it is ignored.

OBJECT-TYPE

The value of tmnxOamTrCtlMaxFailures specifies the maximum number of consecutive timeouts allowed before terminating a trace route test. As shown in the following table 1. This object is applicable to a subset of the test types, and 2. The range and default value depend on the test type. tmnxOamTrCtlTestMode Applicable? Lower Bound Upper Bound Default -------------------- ----------- ----------- ----------- ------- 'bierTrace' yes 5 5 5 'icmpTraceRoute' yes 90 90 90 'lspTraceRoute' yes 1 255 5 'p2mpLspTrace' yes 1 10 5 'vccvTraceRoute' yes 1 255 5 otherwise no N/A N/A N/A

OBJECT-TYPE

The value of tmnxOamTrCtlInterval specifies the number of seconds to wait before repeating an Nokia SROS OAM Trace Route test as defined by the value of the various objects in the corresponding row. This parameter is optional. The number of hops in a single Nokia SROS OAM Trace Route test is determined by the value of the corresponding tmnxOamTrCtlProbesPerHop object. After a single test completes, the number of seconds as defined by the value of tmnxOamTrCtlInterval MUST elapse before the next Nokia SROS OAM Trace Route test is started. The applicability, range, and default value of this object vary with tmnxOamTrCtlTestMode, as shown in the following table. tmnxOamTrCtlTestMode Min Max Default -------------------- --- --- ------- 'ethCfmLinkTrace' 1 10 5 'icmpTraceRoute' not applicable 'vccvTraceRoute' 1 255 1 otherwise 1 10 1

OBJECT-TYPE

The value of tmnxOamTrCtlMaxRows specifies the maximum number of entries allowed in the tmnxOamTrProbeHistoryTable. The oldest entry in the tmnxOamTrProbeHistoryTable is removed to allow the addition of an new entry once the number of rows in the tmnxOamTrProbeHistoryTable reaches this value. Old entries are not removed when a new test is started. Entries are added to the tmnxOamTrProbeHistoryTable until tmnxOamTrCtlMaxRows is reached before entries begin to be removed. A value of 0 for this object disables creation of tmnxOamTrProbeHistoryTable entries. This object was obsoleted in release 6.0R17.

OBJECT-TYPE

The value of tmnxOamTrCtlTrapGeneration specifies when and if to generate a notification for this entry: pathChange(0) - Generate a tmnxOamTrPathChange notification when the current path varies from a previously determined path. testFailure(1) - Generate a tmnxOamTrTestFailed notification when the full path to a target can't be determined. testCompletion(2) - Generate a tmnxOamTrTestCompleted notification when the test is completed.

OBJECT-TYPE

The value of tmnxOamTrCtlCreateHopsEntries specifies whether or not the current path for an Nokia SROS OAM Trace Route test is kept in the tmnxOamTrHopsTable on a per hop basis. tmnxOamTrHopsTable provides a current path topology based on the results of the OAM Trace Route tests. If this feature is not supported tmnxOamTrCtlCreateHopsEntries will always be set to false(2) and any attempt to change its value to true(1) will be denied.

OBJECT-TYPE

The value of tmnxOamTrCtlSAA specifies if this test is an SAA test (Service Assurance Agent; 'true'), or an OAM test ('false'). If there is a tmnxOamSaaCtlTable row with the specified index values, 'true' is returned. Otherwise, 'false' is returned.

OBJECT-TYPE

The value of tmnxOamTrCtlRuns indicates the number of times this OAM trace route test has been executed.

OBJECT-TYPE

The value of tmnxOamTrCtlFailures indicates the number of times this OAM trace route test has failed.

OBJECT-TYPE

The value of tmnxOamTrCtlLastRunResult indicates the completion status the last time this test was executed. If this OAM test is currently in progress, this object indicates the result of the previous test run, if any.

OBJECT-TYPE

The value of tmnxOamTrCtlLastChanged indicates the time the value of a settable object in this row was last changed.

OBJECT-TYPE

The value of tmnxOamTrCtlVRtrID specifies the virtual router to be used for the test. Zero indicates no virtual router is specified. A non-zero value must be the index of an active row in TIMETRA-VRTR-MIB::vRtrConfTable (i.e. tmnxOamTrCtlVRtrID must match a valid TIMETRA-VRTR-MIB::vRtrID value). This object is applicable if tmnxOamTrCtlTestMode is 'icmpTraceRoute'. The table below shows the supported combinations of system-configured virtual routers and test types. Supported for Supported for Supported for tmnxOamTrCtlTestMode Base ? management ? vpls-management ? -------------------- ------------- ------------- ----------------- 'icmpTraceRoute' Yes Yes Yes When directing an 'icmpTraceRoute' test to use a virtual router, the preferred object is tmnxOamTrCtlRouterInstanceName.

OBJECT-TYPE

The value of tmnxOamTrCtlTgtAddrType specifies the address type of tmnxOamTrCtlTgtAddress. The values which can be used as part of a successful test depend on tmnxOamTrCtlTestMode, as follows. Test Mode tmnxOamTrCtlTgtAddrType Values Supported ---------------- ------------------------------------------ 'icmpTraceRoute' 'ipv4(1)' 'ipv6(2)' 'dns(16)' 'vprnTraceRoute' 'ipv4(1)' 'ipv6(2)' otherwise 'unknown(0)'

OBJECT-TYPE

The value of tmnxOamTrCtlTgtAddress specifies the destination host address to be used when performing an OAM trace route operation. The corresponding address type is configured using tmnxOamTrCtlTgtAddrType.

OBJECT-TYPE

The value of tmnxOamTrCtlSrcAddrType specifies the type of Internet address stored in tmnxOamTrCtlSrcAddress.

OBJECT-TYPE

The value of tmnxOamTrCtlSrcAddress specifies the IP host address to be used as the source when performing an OAM Trace Route operation. This object is valid only when the tmnxOamTrCtlTestMode has a value of 'icmpTraceRoute', 'lspTraceRoute', or 'vccvTraceRoute'.

OBJECT-TYPE

The value of tmnxOamTrCtlWaitMilliSec specifies the time in milliseconds to wait for a response before sending the next probe. This object is valid only for 'icmpTraceRoute' tests.

OBJECT-TYPE

The value of tmnxOamTrCtlRouterInstanceName specifies the name of the service or router instance to be used by an 'icmpTraceRoute' test. The following values are supported: 1. '' (i.e. the empty string), 2. 'Base', 3. 'management', 4. 'vpls-management', 5. A VPRN service name (i.e. a TIMETRA-SERV-MIB::svcName, with TIMETRA-SERV-MIB::svcType = 'vprn(4)'). 6. A CPM virtual router name (i.e. a user-configured router name, with TIMETRA-VRTR-MIB::vRtrType = 'vr(3)'). Names other than the names listed above are accepted, but will not lead to a successful test. The service or virtual router to be used by an 'icmpTraceRoute' test can be specified using tmnxOamTrCtlVRtrID, tmnxOamTrCtlServiceId, and/or tmnxOamTrCtlRouterInstanceName. The following two combinations of the three objects are supported: 1. tmnxOamTrCtlVRtrID = 0, tmnxOamTrCtlServiceId = 0, tmnxOamTrCtlRouterInstanceName != ''. This is the preferred approach. 2. One or both of tmnxOamTrCtlVRtrID and tmnxOamTrCtlServiceId has a non-zero value, tmnxOamTrCtlRouterInstanceName = ''. An attempt to change TIMETRA-SYSTEM-MIB::tmnxSysMgmtIfWriteMode.0 away from 'classic(1)' is blocked if any tmnxOamTrCtlRouterInstanceName is empty for an 'icmpTraceRoute' test. When TIMETRA-SYSTEM-MIB::tmnxSysMgmtIfWriteMode.0 is not 'classic(1)', each 'icmpTraceRoute' test must continue to have a non-empty tmnxOamTrCtlRouterInstanceName.

OBJECT-TYPE

tmnxOamTrResultsTable contains the run-level test results for OAM trace tests. TTL-level test results for trace tests reside in tmnxOamTrHopsTable. Probe-level test results for trace tests reside in tmnxOamTrProbeHistoryTable.

OBJECT-TYPE

tmnxOamTrResultsEntry contains the run-level test results for one OAM trace test run. A row is created when a trace test is enabled (using tmnxOamTrCtlAdminStatus). A row is destroyed when: 1. The corresponding test configuration is destroyed (using tmnxOamTrCtlRowStatus), or 2. A new run result is available, and the limit on the number of run results retained (3, currently) has been reached. In that case, the oldest run result row is destroyed.

OBJECT-TYPE

The value of tmnxOamTrResultsOperStatus indicates the operational state of the specified test run. 'enabled(1)' indicates the test is running.

OBJECT-TYPE

Reflects the current TTL value (range from 0 to 255) for an Nokia SROS OAM Trace Route operation. Maximum TTL value is determined by tmnxOamTrCtlMaxTtl. Zero is returned only in the case of an aborted 'ethCfmLinkTrace' test.

OBJECT-TYPE

Reflects the current probe count (1..10) for an Nokia SROS OAM Trace Route operation. The maximum probe count is determined by tmnxOamTrCtlProbesPerHop.

OBJECT-TYPE

This object was obsoleted in release 4.0 and replaced with InetAddress objects tmnxOamTrResultsTgtAddrType and tmnxOamTrResultsTgtAddress.

OBJECT-TYPE

The current number of attempts to determine a path to a target. The value of this object MUST be started at 0. This object was made obsolete in the 3.0 release. Originally this table was used to report a summary of the results of all traceroute test for the configured test. An additional index, tmnxOamTrResultsTestRunIndex, has been added to this table and a row in this table now represents the results of a single traceroute test run. The new object tmnxOamTrCtlRuns in the tmnxOamTrCtlTable indicates the number of times this traceroute test has been run.

OBJECT-TYPE

The current number of attempts to determine a path to a target that have succeeded. The value of this object MUST be reported as 0 when no attempts have succeeded. This object was made obsolete in the 3.0 release. Originally this table was used to report a summary of the results of all traceroute test for the configured test. An additional index, tmnxOamTrResultsTestRunIndex, has been added to this table and a row in this table now represents the results of a single traceroute test run. The new object tmnxOamTrCtlFailures in the tmnxOamTrCtlTable indicates the number of times an attempt to run this traceroute test has failed. The number of successful runs can be calculated as (tmnxOamTrCtlRuns - tmnxOamTrCtlFailures).

OBJECT-TYPE

The value of tmnxOamTrResultsLastGoodPath indicates the date and time when the last complete path was determined. 1970-Jan-01 00:00:00 UTC is returned when a complete path was not determined.

OBJECT-TYPE

The value of tmnxOamTrResultsTestRunIndex specifies the test run INDEX of the row. The first run of a test is assigned run index 1. The second run of a test is assigned run index 2. Etc.

OBJECT-TYPE

The value of tmnxOamTrResultsTgtAddrType indicates the Internet address type stored in tmnxOamTrResultsTgtAddress.

OBJECT-TYPE

The value of tmnxOamTrResultsTgtAddress indicates the IP destination address of the test. If the configured destination address of the test has type 'dns(16)', this is the corresponding IPv4 or IPv6 address (if available). tmnxOamTrResultsTgtAddrType is 'unknown(0)' when an IP destination address for the test is unavailable.

OBJECT-TYPE

The value of tmnxOamTrResultsTestRunResult indicates the result of the specified test run.

OBJECT-TYPE

tmnxOamTrProbeHistoryTable contains per-probe results for trace route tests. This table is not used for tests which have tmnxOamTrCtlTestMode set to 'ldpTreeTrace'.

OBJECT-TYPE

A tmnxOamTrProbeHistoryEntry is created by the system when the result of a trace route probe launch is determined. Rows are destroyed when the corresponding tmnxOamTrHopsTable row is destroyed.

OBJECT-TYPE

The value of tmnxOamTrProbeHistoryIndex specifies a probe belonging to an OAM Trace Route test run. The probes are numbered sequentially, starting at one. Two indexing methods for uniquely identifying a probe are provided: 1. tmnxOamTrCtlOwnerIndex, tmnxOamTrCtlTestIndex, tmnxOamTrResultsTestRunIndex, tmnxOamTrProbeHistoryIndex. 2. tmnxOamTrCtlOwnerIndex, tmnxOamTrCtlTestIndex, tmnxOamTrResultsTestRunIndex, tmnxOamTrProbeHistoryHopIndex, tmnxOamTrProbeHistoryProbeIndex.

OBJECT-TYPE

The value of tmnxOamTrProbeHistoryHopIndex specifies the number of hops travelled by the outbound trace route request. The initial value used for a particular test is configured using tmnxOamTrCtlInitialTtl.

OBJECT-TYPE

The value of tmnxOamTrProbeHistoryProbeIndex specifies a trace route reply, in the context of a hop. Two indexing methods for uniquely identifying a probe are provided: 1. tmnxOamTrCtlOwnerIndex, tmnxOamTrCtlTestIndex, tmnxOamTrResultsTestRunIndex, tmnxOamTrProbeHistoryIndex. 2. tmnxOamTrCtlOwnerIndex, tmnxOamTrCtlTestIndex, tmnxOamTrResultsTestRunIndex, tmnxOamTrProbeHistoryHopIndex, tmnxOamTrProbeHistoryProbeIndex. The number of probes per hop for a particular test is configured using tmnxOamTrCtlProbesPerHop.

OBJECT-TYPE

This object was obsoleted in release 4.0 and replaced with InetAddress objects tmnxOamTrProbeHistoryAddrType and tmnxOamTrProbeHistoryAddress.

OBJECT-TYPE

The value of tmnxOamTrProbeHistoryResponse indicates the round trip time for the specified probe. Zero is returned when the information is not available (e.g. the probe timed out).

OBJECT-TYPE

The value of tmnxOamTrProbeHistoryOneWayTime indicates the outbound trip time for the specified probe. The value is valid if the two nodes have proper clock synchronization. Otherwise, for example, a negative value can be returned. Zero is returned when the information is not available.

OBJECT-TYPE

The value of tmnxOamTrProbeHistoryStatus indicates the outcome of the probe. Example values: 'responseReceived', 'requestTimedOut'.

OBJECT-TYPE

The last implementation method specific reply code received. The Nokia SROS OAM Trace Route is usually implemented by transmitting a series of probe packets with increasing time-to-live values. A probe packet is a UDP datagram encapsulated into an IP packet. Each hop in a path to the target (destination) host rejects the probe packets (probe's TTL too small, ICMP reply) until either the maximum TTL is exceeded or the target host is received. For 'icmpTraceRoute', the ICMP code and ICMP type is contained in the least significant 16 bits of tmnxOamTrProbeHistoryLastRC. Bits 0 to 7 contain the ICMP type and bits 8 to 15 contain the ICMP code.

OBJECT-TYPE

The value of tmnxOamTrProbeHistoryTime indicates the date and time when the outcome of the specified probe was determined.

OBJECT-TYPE

The value of tmnxOamTrProbeHistoryResponsePlane indicates the type of response plane this trace route response was received on.

OBJECT-TYPE

The value of tmnxOamTrProbeHistoryAddressType indicates the type of binding address information returned in response to a test. When the test has the tmnxOamTrCtlTestMode value 'ethCfmLinkTrace', 'unknown' is returned. For 'macTraceRoute', three types of address are applicable - 'sapId', 'localCpu', and 'sdpId'. Address type of 'sdpId' is a special case used specifically to indicate that the probe was traversing a b-vpls node in a PBB network (but where destination MAC is not necessarily known to the b-vpls node).

OBJECT-TYPE

The value of tmnxOamTrProbeHistorySapId indicates the name of the access port of the SAP supporting the requested IP address returned in response to a 'vprnTraceRoute' probe. If the value of tmnxOamTrProbeHistoryAddressType is not 'sapId', this object is not relevant and MUST have a null string ''.

OBJECT-TYPE

The value of tmnxOamTrProbeHistoryVersion indicates the protocol version for this OAM ping reply.

OBJECT-TYPE

The value tmnxOamTrProbeHistoryRouterID indicates the downstream router ID of the node that provided this ping reply. This object is valid only when tmnxOamTrCtlTestMode has a value of 'lspTraceRoute'. This object was made obsolete in SROS release 13.0 R1.

OBJECT-TYPE

The value of tmnxOamTrProbeHistoryIfIndex indicates for a 'lspTraceRoute' or 'vccvTraceRoute' probe the ifIndex value of the interface that this probe was transmitted from. For other types of probes, this value is not significant and zero is returned.

OBJECT-TYPE

The value of tmnxOamTrProbeHistoryDataLen indicates the UDP data length of the echo reply. A valid value is returned when the test has a tmnxOamTrCtlTestMode value of 'icmpTraceRoute', 'lspTraceRoute', 'p2mpLspTrace', or 'vccvTraceRoute'. Otherwise, this value is not significant and zero is returned.

OBJECT-TYPE

The value of tmnxOamTrProbeHistorySize indicates the size in octets of the user payload in the probe request packet. It does not include the service encapsulation. Zero is returned if no probe was transmitted.

OBJECT-TYPE

The value of tmnxOamTrProbeHistoryInOneWayTime indicates the inbound trip time for the specified probe. The value is valid if the two nodes have proper clock synchronization. Otherwise, for example, a negative value can be returned. Zero is returned when the information is not available.

OBJECT-TYPE

The value of tmnxOamTrProbeHistoryAddrType indicates the address type of tmnxOamTrProbeHistoryAddress.

OBJECT-TYPE

The value of tmnxOamTrProbeHistoryAddress indicates the IP address of the replying node for the specified trace request.

OBJECT-TYPE

The value of tmnxOamTrProbeHistorySrcGlobalId indicates the source MPLS-TP global identifier of the replying node. The value is copied from the reply's RFC 6426 Source Identifier TLV. If the TLV is absent, zero is returned. This value is relevant when tmnxOamTrCtlTestMode is 'lspTraceRoute' or 'vccvTraceRoute'. Otherwise, zero is returned.

OBJECT-TYPE

The value of tmnxOamTrProbeHistorySrcNodeId indicates the source MPLS-TP node identifier of the replying node. The value is copied from the reply's RFC 6426 Source Identifier TLV. If the TLV is absent, zero is returned. This value is relevant when tmnxOamTrCtlTestMode is 'lspTraceRoute' or 'vccvTraceRoute'. Otherwise, zero is returned.

OBJECT-TYPE

The value of tmnxOamTrProbeHistorySdpBindId indicates the SDP binding provided by the remote system. The value of tmnxOamTrProbeHistorySdpBindId is relevant when tmnxOamTrProbeHistoryAddressType is 'sdpBindId(9)'.

OBJECT-TYPE

The value of tmnxOamTrProbeHistoryRtrnSubcode indicates the value present in an MPLS echo reply's RFC 4379 Return Subcode (RSC) field. A valid value is returned when the test has a tmnxOamTrCtlTestMode value of 'lspTraceRoute' or 'ldpTreeTrace'. Otherwise, zero is returned.

OBJECT-TYPE

The value of tmnxOamTrProbeHistoryNtwrkIfName indicates the network interface name provided by the replying node. Network interface names are configured using TIMETRA-VRTR-MIB::vRtrIfName. The value of this object is the empty string when the value of tmnxOamTrProbeHistoryAddressType is not 'networkInterface(11)'.

OBJECT-TYPE

tmnxOamTrHopsTable contains the TTL-level test results for OAM trace tests. Run-level test results for trace tests reside in tmnxOamTrResultsTable. Probe-level test results for trace tests reside in tmnxOamTrProbeHistoryTable.

OBJECT-TYPE

tmnxOamTrHopsEntry contains the TTL-level test results for one TTL of one OAM trace test run. A row is created when a TTL is probed by a trace test run. Rows are destroyed when the corresponding tmnxOamTrResultsTable row is destroyed.

OBJECT-TYPE

The value of tmnxOamTrHopsHopIndex specifies the TTL of the trace test run results reported by this row.

OBJECT-TYPE

This object was obsoleted in release 4.0 and replaced with InetAddress objects tmnxOamTrHopsTgtAddrType and tmnxOamTrHopsTgtAddrType.

OBJECT-TYPE

The value of tmnxOamTrHopsMinRtt indicates the minimum round trip time for the specified TTL of the specified test run. Zero is returned when the information is not available.

OBJECT-TYPE

The value of tmnxOamTrHopsMaxRtt indicates the maximum round trip time for the specified TTL of the specified test run. Zero is returned when the information is not available.

OBJECT-TYPE

The value of tmnxOamTrHopsAverageRtt indicates the average round trip time for the specified TTL of the specified test run. Zero is returned when the information is not available.

OBJECT-TYPE

The value of tmnxOamTrHopsRttSumOfSquares indicates the least significant 32 bits of tmnxOamTrHopsRttHCSumSquares.

OBJECT-TYPE

The value of tmnxOamTrHopsMinTt indicates the minimum outbound trip time for the specified TTL of the specified test run. The value is valid if the two nodes have proper clock synchronization. Otherwise, for example, a negative value can be returned. Zero is returned when the information is not available.

OBJECT-TYPE

The value of tmnxOamTrHopsMaxTt indicates the maximum outbound trip time for the specified TTL of the specified test run. The value is valid if the two nodes have proper clock synchronization. Otherwise, for example, a negative value can be returned. Zero is returned when the information is not available.

OBJECT-TYPE

The value of tmnxOamTrHopsAverageTt indicates the average outbound trip time for the specified TTL of the specified test run. The value is valid if the two nodes have proper clock synchronization. Otherwise, for example, a negative value can be returned. Zero is returned when the information is not available.

OBJECT-TYPE

The value of tmnxOamTrHopsTtSumOfSquares indicates the least significant 32 bits of tmnxOamTrHopsTtHCSumSquares.

OBJECT-TYPE

The value of tmnxOamTrHopsSentProbes indicates the number of probes sent for the specified TTL of the specified test run.

OBJECT-TYPE

The value of tmnxOamTrHopsProbeResponses indicates the number of responses received for the specified TTL of the specified test run.

OBJECT-TYPE

The value of tmnxOamTrHopsLastGoodProbe indicates the date and time when the most recent response was received for the specified TTL of the specified test run. 1970-Jan-01 00:00:00 UTC is returned if a response has not been received.

OBJECT-TYPE

The value of tmnxOamTrHopsMinInTt indicates the minimum inbound trip time for the specified TTL of the specified test run. The value is valid if the two nodes have proper clock synchronization. Otherwise, for example, a negative value can be returned. Zero is returned when the information is not available.

OBJECT-TYPE

The value of tmnxOamTrHopsMaxInTt indicates the maximum inbound trip time for the specified TTL of the specified test run. The value is valid if the two nodes have proper clock synchronization. Otherwise, for example, a negative value can be returned. Zero is returned when the information is not available.

OBJECT-TYPE

The value of tmnxOamTrHopsAverageInTt indicates the average inbound trip time for the specified TTL of the specified test run. The value is valid if the two nodes have proper clock synchronization. Otherwise, for example, a negative value can be returned. Zero is returned when the information is not available.

OBJECT-TYPE

The value of tmnxOamTrHopsInTtSumOfSqrs indicates the least significant 32 bits of tmnxOamTrHopsInTtHCSumSqrs.

OBJECT-TYPE

The value of tmnxOamTrHopsOutJitter indicates the amount of jitter in the outbound trip times for the specified TTL of the specified test run. Zero is returned when the information is not available.

OBJECT-TYPE

The value of tmnxOamTrHopsInJitter indicates the amount of jitter in the inbound trip times for the specified TTL of the specified test run. Zero is returned when the information is not available.

OBJECT-TYPE

The value of tmnxOamTrHopsRtJitter indicates the amount of jitter in the round trip times for the specified TTL of the specified test run. Zero is returned when the information is not available.

OBJECT-TYPE

The value of tmnxOamTrHopsProbeTimeouts indicates the number of probes that timed out for the specified TTL of the specified test run.

OBJECT-TYPE

The value of tmnxOamTrHopsProbeFailures indicates the number of probes that failed to be transmitted plus the number of probes that timed out.

OBJECT-TYPE

The value of tmnxOamTrHopsTgtAddrType indicates the address type of tmnxOamTrHopsTgtAddress.

OBJECT-TYPE

The value of tmnxOamTrHopsTgtAddress indicates the IP address of the replying node for the specified TTL of the specified test run.

OBJECT-TYPE

The value of tmnxOamTrHopsRttOFSumSquares indicates the number of times tmnxOamTrHopsRttSumOfSquares overflowed.

OBJECT-TYPE

The value of tmnxOamTrHopsRttHCSumSquares indicates the sum of squares of the round trip times for the specified TTL of the specified test run. Its purpose is to enable the standard deviation calculation. Zero is returned when the information is not available.

OBJECT-TYPE

The value of tmnxOamTrHopsTtOFSumSquares indicates the number of times tmnxOamTrHopsTtSumOfSquares overflowed.

OBJECT-TYPE

The value of tmnxOamTrHopsTtHCSumSquares indicates the sum of squares of the outbound trip times for the specified TTL of the specified test run. Its purpose is to enable the standard deviation calculation. Zero is returned when the information is not available.

OBJECT-TYPE

The value of tmnxOamTrHopsInTtOFSumSqrs indicates the number of times tmnxOamTrHopsInTtSumOfSqrs overflowed.

OBJECT-TYPE

The value of tmnxOamTrHopsInTtHCSumSqrs indicates the sum of squares of the inbound trip times for the specified TTL of the specified test run. Its purpose is to enable the standard deviation calculation. Zero is returned when the information is not available.

OBJECT-TYPE

Defines the Nokia SROS OAM MAC Trace Route Control Table for providing, via SNMP, the capability of performing Nokia SROS OAM 'macTraceRoute' test operations. The results of these tests are stored in the tmnxOamTrResultsTable, tmnxOamTrProbeHistoryTable and the tmnxOamMacTrL2MapTable.

OBJECT-TYPE

Defines an entry in the tmnxOamMacTrCtlTable. The first index element, tmnxOamTrCtlOwnerIndex, is of type SnmpAdminString, a textual convention that allows for use of the SNMPv3 View-Based Access Control Model (RFC 2575 [11], VACM) and allows a management application to identify its entries. The second index, tmnxOamTrCtlTestIndex, enables the same management application to have multiple outstanding requests.

OBJECT-TYPE

The value of tmnxOamMacTrCtlTargetMacAddr is a 6-octet value that specifies the target MAC address to be used in the query request for performing an OAM Mac Trace Route operation when tmnxOamTrCtlTestMode has a value of 'macTraceRoute'.

OBJECT-TYPE

The value of tmnxOamMacTrCtlSourceMacAddr is a 6-octet value that specifies the MAC address to be used as the source in the query request for performing an OAM MAC Trace Route operation when tmnxOamTrCtlTestMode has a value of 'macTraceRoute'.

OBJECT-TYPE

The value of tmnxOamMacTrCtlSendControl specifies whether the outbound MAC trace route packet will use the data plane or the control plane. When the value is 'false', the packet is sent using the data plane. As of SROS release 13.0 R1, a test cannot be started if tmnxOamMacTrCtlSendControl is 'true'. A test is started using tmnxOamTrCtlAdminStatus. This object will be marked obsolete in a future release.

OBJECT-TYPE

When the value of tmnxOamMacTrCtlReplyControl is 'true', the OAM Mac Trace Route response is returned using the control plane. If its value is 'false', the packet is sent via the data plane.

OBJECT-TYPE

Defines a table for storing the results of an OAM 'macTraceRoute' probe operation when a L2 Mapping TLV was returned. Each row represents a single L2FEC TLV within the L2 Mapping TLV. A single L2 mapping entry is returned if the 'macTraceRoute' replier knows the requested VPN ID and has a binding for the requested MAC address. Multiple downstream L2 mappings that specify the replier's flooding domain may be returned if the replier has no bindings for the MAC address. An entry in this table is created when the result of an OAM 'macTraceRoute' probe is determined. An entry is removed from this table when its corresponding tmnxOamTrCtlEntry is deleted.

OBJECT-TYPE

Defines an entry in the tmnxOamMacTrL2MapTable. The first two index elements identify the tmnxOamTrCtlEntry that a tmnxOamMacTrL2MapEntry belongs to. The third index element identifies a particular OAM trace route test run. The fourth index element selects the group of responses associated with a specific probe attempt. The fifth and sixth indexes select the hop and the probe at that hop for a particular Nokia SROS OAM Trace Route operation. Note that in the case of a successful 'macTraceRoute' reply there will be only one row entry created. However there may also be one or more error replies. The seventh index selects a single L2 mapping entry within a specific probe reply.

OBJECT-TYPE

The tmnxOamMacTrL2MapIndex selects a single L2 mapping entry within a specific 'macTraceRoute' probe reply. The agent starts assigning tmnxOamMacTrL2MapIndex values at 1.

OBJECT-TYPE

The value of tmnxOamMacTrL2MapRouterID is the router ID for this L2 mapping entry.

OBJECT-TYPE

The value of tmnxOamMacTrL2MapLabel is the label used by the router for the L2FEC or VC ID specified by this L2 mapping entry.

OBJECT-TYPE

The value of tmnxOamMacTrL2MapProtocol is the signaling protocol used by the router for the L2FEC or VC ID specified by this L2 mapping entry.

OBJECT-TYPE

The value of tmnxOamMacTrL2MapVCType indicates the class of VC ID given in tmnxOamMacTrL2MapVCID.

OBJECT-TYPE

The value of tmnxOamMacTrL2MapVCID is the VC ID associated with the label used by the L2FEC specified by this L2 mapping entry.

OBJECT-TYPE

The value of tmnxOamMacTrL2MapDirection indicates the direction that this L2 mapping entry is in relation to the node that returned the 'macTraceRoute' reply.

OBJECT-TYPE

The value of tmnxOamMacTrL2MapSdpId indicates the ID of the SDP supporting the L2 mapping entry that returned the reply. If this mapping is not a SDP, this object is not relevant and MUST return a value of '0'.

OBJECT-TYPE

The value of tmnxOamMacTrL2MapSapName indicates the SAP name when the downstream of the responder is a SAP. If the downstream responder is not a SAP, this object is not relevant and MUST return a zero length empty string.

OBJECT-TYPE

Each row in tmnxOamLspTrCtlTable contains the LSP-specific configuration information needed to launch an LSP (Label Switched Path) trace route test. The rest of the configuration information needed to launch the test resides in the corresponding row of tmnxOamTrCtlTable. Results of LSP trace route tests are stored in tmnxOamTrResultsTable, tmnxOamTrProbeHistoryTable, tmnxOamTrHopsTable, tmnxOamLspTrMapTable, and tmnxOamLspTrDSLabelTable. Seven types of LSP trace route tests are supported. An abbreviated name for each test type is defined in the following table (for use in a subsequent table). The test type's tmnxOamLspTrCtlTestSubMode code point is shown as well. Test Sub Mode Abbreviated Test Type Name(s) --------------------- ------------------------------- 'unspecified (1)' LDP, RSVP 'static (2)' TPST (Transport Profile Static) 'bgpLabeledPrefix(3)' BGP 'srIsis (4)' ISIS 'srOspf (5)' OSPF 'srTe (6)' SRTE 'srPolicy (7)' SRPL 'srOspf3 (8)' OSP3 The following table has a row for each LSP trace route test type, showing the mandatory and optional objects applicable to the test type. Test Type Mandatory Objects Optional Objects ---- -------------------------------- --------------------------------- BGP tmnxOamLspTrCtlLdpPrefixType *tmnxOamLspTrCtlNhAddressType tmnxOamLspTrCtlLdpPrefix *tmnxOamLspTrCtlNhAddress tmnxOamLspTrCtlLdpPrefixLen tmnxOamLspTrCtlNhIntfName tmnxOamLspTrCtlTestSubMode #tmnxOamLspTrCtlPathDestType #tmnxOamLspTrCtlPathDest ISIS tmnxOamLspTrCtlLdpPrefixType tmnxOamLspTrCtlIgpInstance tmnxOamLspTrCtlLdpPrefix *tmnxOamLspTrCtlNhAddressType tmnxOamLspTrCtlLdpPrefixLen *tmnxOamLspTrCtlNhAddress tmnxOamLspTrCtlTestSubMode tmnxOamLspTrCtlNhIntfName #tmnxOamLspTrCtlPathDestType #tmnxOamLspTrCtlPathDest LDP tmnxOamLspTrCtlLdpPrefixType *tmnxOamLspTrCtlNhAddressType tmnxOamLspTrCtlLdpPrefix *tmnxOamLspTrCtlNhAddress tmnxOamLspTrCtlLdpPrefixLen tmnxOamLspTrCtlNhIntfName #tmnxOamLspTrCtlPathDestType #tmnxOamLspTrCtlPathDest OSPF tmnxOamLspTrCtlLdpPrefixType tmnxOamLspTrCtlIgpInstance tmnxOamLspTrCtlLdpPrefix *tmnxOamLspTrCtlNhAddressType tmnxOamLspTrCtlLdpPrefixLen *tmnxOamLspTrCtlNhAddress tmnxOamLspTrCtlTestSubMode tmnxOamLspTrCtlNhIntfName #tmnxOamLspTrCtlPathDestType #tmnxOamLspTrCtlPathDest OSP3 tmnxOamLspTrCtlLdpPrefixType tmnxOamLspTrCtlIgpInstance tmnxOamLspTrCtlLdpPrefix *tmnxOamLspTrCtlNhAddressType tmnxOamLspTrCtlLdpPrefixLen *tmnxOamLspTrCtlNhAddress tmnxOamLspTrCtlTestSubMode tmnxOamLspTrCtlNhIntfName #tmnxOamLspTrCtlPathDestType #tmnxOamLspTrCtlPathDest RSVP tmnxOamLspTrCtlLspName tmnxOamLspTrCtlPathName SRPL tmnxOamLspTrCtlSrPlcyColor tmnxOamLspTrCtlSrPlcySegList tmnxOamLspTrCtlSrPlcyEndPtAddr tmnxOamLspTrCtlSrPlcyEndPtAddT tmnxOamLspTrCtlTestSubMode SRTE tmnxOamLspTrCtlLspName *tmnxOamLspTrCtlNhAddressType tmnxOamLspTrCtlTestSubMode *tmnxOamLspTrCtlNhAddress tmnxOamLspTrCtlNhIntfName #tmnxOamLspTrCtlPathDestType #tmnxOamLspTrCtlPathDest tmnxOamLspTrCtlPathName TPST tmnxOamLspTrCtlLspName tmnxOamLspTrCtlAssocChannel tmnxOamLspTrCtlTestSubMode tmnxOamLspTrCtlForce tmnxOamLspTrCtlMplsTpPathType ALL none tmnxOamLspTrCtlDownstreamMapTlv tmnxOamTrCtlDataSize tmnxOamTrCtlFcName tmnxOamTrCtlInitialTtl tmnxOamTrCtlInterval tmnxOamTrCtlMaxFailures tmnxOamTrCtlMaxTtl tmnxOamTrCtlProbesPerHop tmnxOamTrCtlProfile *tmnxOamTrCtlSrcAddrType *tmnxOamTrCtlSrcAddress tmnxOamTrCtlTimeOut ---- -------------------------------- --------------------------------- In the table above, 1. The optional objects in the ALL row apply to all LSP trace route test types. 2. Asterisks (*) mark a set of optional objects which must all be specified, or must all be unspecified. 3. Octothorpes (#) mark a separate set of optional objects which must all be specified, or must all be unspecified. 4. There are four supported combinations of tmnxOamLspTrCtlNhAddressType, tmnxOamLspTrCtlNhAddress, tmnxOamLspTrCtlNhIntfName, tmnxOamLspTrCtlPathDestType, and tmnxOamLspTrCtlPathDest, as follows: a) all unspecified b) tmnxOamLspTrCtlPathDestType and tmnxOamLspTrCtlPathDest c) tmnxOamLspTrCtlPathDestType, tmnxOamLspTrCtlPathDest, and tmnxOamLspTrCtlNhIntfName d) tmnxOamLspTrCtlPathDestType, tmnxOamLspTrCtlPathDest, tmnxOamLspTrCtlNhAddressType, and tmnxOamLspTrCtlNhAddress When an object combination other than a combination listed above is specified, values will be rejected or ignored, or the test will fail.

OBJECT-TYPE

The system creates a row in tmnxOamLspTrCtlTable when a row is created in tmnxOamTrCtlTable with tmnxOamTrCtlTestMode set to 'lspTraceRoute'. The system deletes a row in tmnxOamLspTrCtlTable when the corresponding row in tmnxOamTrCtlTable is deleted.

OBJECT-TYPE

tmnxOamLspTrCtlVRtrID was obsoleted in release 6.0R15 and replaced with tmnxOamTrCtlVRtrID in tmnxOamTrCtlTable.

OBJECT-TYPE

The value of tmnxOamLspTrCtlLspName specifies the name of the LSP for this LSP trace route test. When the test is started, if this name is not empty, there must be a TIMETRA-MPLS-MIB::vRtrMplsLspTable row with: 1. tmnxOamLspTrCtlLspName equal to TIMETRA-MPLS-MIB::vRtrMplsLspName, AND 2. TIMETRA-VRTR-MIB::vRtrID equal to 1, AND 3. TIMETRA-MPLS-MIB::vRtrMplsLspType equal to 'dynamic(2)', 'bypassOnly(4)', or 'mplsTp(7)'. Otherwise, the test will fail. The supported object combinations for LSP trace route tests are listed in the tmnxOamLspTrCtlTable DESCRIPTION clause.

OBJECT-TYPE

The value of tmnxOamLspTrCtlPathName specifies the name of the Path (LSP) for this LSP trace route test. When the test is started, if this name is not empty, there must be a matching name in the column MPLS-TE-MIB::mplsTunnelName. Otherwise, the test will fail. The supported object combinations for LSP trace route tests are listed in the tmnxOamLspTrCtlTable DESCRIPTION clause.

OBJECT-TYPE

tmnxOamLspTrCtlLdpIpPrefix was obsoleted in release 4.0 and replaced with InetAddress objects tmnxOamLspTrCtlLdpPrefixType and tmnxOamLspTrCtlLdpPrefix.

OBJECT-TYPE

tmnxOamLspTrCtlLdpIpPrefixLen was obsoleted in release 4.0 and replaced with InetAddress object tmnxOamLspTrCtlLdpPrefixLen.

OBJECT-TYPE

The value of tmnxOamLspTrCtlLdpPrefixType specifies the type of Internet address stored in tmnxOamLspTrCtlLdpPrefix. The supported object combinations for LSP trace route tests are listed in the tmnxOamLspTrCtlTable DESCRIPTION clause.

OBJECT-TYPE

The value of tmnxOamLspTrCtlLdpPrefix, along with tmnxOamLspTrCtlLdpPrefixType and tmnxOamLspTrCtlLdpPrefixLen, specifies the destination prefix for this LSP trace route test. The supported object combinations for LSP trace route tests are listed in the tmnxOamLspTrCtlTable DESCRIPTION clause.

OBJECT-TYPE

The value of tmnxOamLspTrCtlLdpPrefixLen specifies the Internet address prefix length of tmnxOamLspTrCtlLdpPrefix. The supported object combinations for LSP trace route tests are listed in the tmnxOamLspTrCtlTable DESCRIPTION clause.

OBJECT-TYPE

The value of tmnxOamLspTrCtlPathDestType specifies the type of Internet address stored in tmnxOamLspTrCtlPathDest. The supported object combinations for LSP trace route tests are listed in the tmnxOamLspTrCtlTable DESCRIPTION clause.

OBJECT-TYPE

The value of tmnxOamLspTrCtlPathDest specifies a unique path in a multipath setup for this OAM LSP trace route to traverse. This address is used as part of a hash key to select the appropriate ECMP to the destination. The supported object combinations for LSP trace route tests are listed in the tmnxOamLspTrCtlTable DESCRIPTION clause.

OBJECT-TYPE

The value of tmnxOamLspTrCtlNhIntfName specifies the name of the next hop interface to be used when launching the LSP trace route test. When the test is started, if this name is not empty, there must be a TIMETRA-VRTR-MIB::vRtrIfTable row with: 1. tmnxOamLspTrCtlNhIntfName equal to TIMETRA-VRTR-MIB::vRtrIfName, AND 2. TIMETRA-VRTR-MIB::vRtrID equal to 1. Otherwise, the test will fail. The supported object combinations for LSP trace route tests are listed in the tmnxOamLspTrCtlTable DESCRIPTION clause.

OBJECT-TYPE

The value of tmnxOamLspTrCtlNhAddressType specifies the type of Internet address stored in tmnxOamLspTrCtlNhAddress. The supported object combinations for LSP trace route tests are listed in the tmnxOamLspTrCtlTable DESCRIPTION clause.

OBJECT-TYPE

The value of tmnxOamLspTrCtlNhAddress specifies the interface address to the next hop which will be used to launch the LSP trace route test. The supported object combinations for LSP trace route tests are listed in the tmnxOamLspTrCtlTable DESCRIPTION clause.

OBJECT-TYPE

The value of tmnxOamLspTrCtlDownstreamMapTlv specifies the type of downstream mapping TLV to insert in the MPLS echo request PDU when launching the test. When an LSP trace route test is created, the value of this object defaults to the value of the global configuration object tmnxOamMplsEchoDownstreamMapTlv. The supported object combinations for LSP trace route tests are listed in the tmnxOamLspTrCtlTable DESCRIPTION clause.

OBJECT-TYPE

The value of tmnxOamLspTrCtlTestSubMode specifies the type of LSP trace route test to perform. When this object is 'unspecified(1)', the type of LSP trace route test to be performed is determined when the test is started, from the set of tmnxOamLspTrCtlTable objects configured with non-default values. If there is a mismatch between tmnxOamLspTrCtlTestSubMode and the type of the LSP to be tested, the test will fail. For example, if tmnxOamLspTrCtlTestSubMode is 'static(2)', and tmnxOamLspTrCtlLspName refers to an LSP with TIMETRA-MPLS-MIB::vRtrMplsLspType not equal to 'mplsTp(7)', the test will fail. The supported object combinations for LSP trace route tests are listed in the tmnxOamLspTrCtlTable DESCRIPTION clause.

OBJECT-TYPE

The value of tmnxOamLspTrCtlMplsTpPathType specifies the type of the MPLS-TP path to be tested. The supported object combinations for LSP trace route tests are listed in the tmnxOamLspTrCtlTable DESCRIPTION clause.

OBJECT-TYPE

The value of tmnxOamLspTrCtlAssocChannel specifies the launched echo request's usage of the Associated Channel (ACH) mechanism, when testing an MPLS-TP LSP. When tmnxOamLspTrCtlTestSubMode is 'static(2)', the default value for tmnxOamLspTrCtlAssocChannel is 'nonIp(2)'. The supported object combinations for LSP trace route tests are listed in the tmnxOamLspTrCtlTable DESCRIPTION clause.

OBJECT-TYPE

The value of tmnxOamLspTrCtlForce specifies whether or not to force the transmission of the 'lspTraceRoute' request PDU(s). If tmnxOamLspTrCtlForce is 'true(1)', the test will proceed and request PDU(s) will be sent regardless of the local operational status of the tested LSP path. If tmnxOamLspTrCtlForce is 'false(2)', the test will fail immediately when the local operational status of the tested LSP path is down. The supported object combinations for LSP trace route tests are listed in the tmnxOamLspTrCtlTable DESCRIPTION clause.

OBJECT-TYPE

The value of tmnxOamLspTrCtlIgpInstance specifies the Interior Gateway Protocol (IGP) instance to be used for the test. The supported object combinations for LSP trace route tests are listed in the tmnxOamLspTrCtlTable DESCRIPTION clause.

OBJECT-TYPE

The value of tmnxOamLspTrCtlSrPlcyColor specifies the Segment Routing (SR) policy color to be used for the test. A color associates an SR policy with an intent (e.g. low latency). tmnxOamLspTrCtlSrPlcyColor, tmnxOamLspTrCtlSrPlcyEndPtAddT, and tmnxOamLspTrCtlSrPlcyEndPtAddr must identify a known SR policy. Otherwise, the test will fail. The color of a static SR policy is defined using TIMETRA-SR-POLICY-MIB::vRtrSrStaticPlcyColor. When configuring an SR policy LSP trace test, the following objects must all be set in one snmpset PDU: tmnxOamLspTrCtlTestSubMode = 'srPolicy(7)', tmnxOamLspTrCtlSrPlcyColor, tmnxOamLspTrCtlSrPlcyEndPtAddT = 'ipv4(1)' or 'ipv6(2)', tmnxOamLspTrCtlSrPlcyEndPtAddr. The supported object combinations for LSP trace tests are listed in the tmnxOamLspTrCtlTable DESCRIPTION clause.

OBJECT-TYPE

The value of tmnxOamLspTrCtlSrPlcyEndPtAddT specifies the type of IP address stored in tmnxOamLspTrCtlSrPlcyEndPtAddr. The supported object combinations for LSP trace tests are listed in the tmnxOamLspTrCtlTable DESCRIPTION clause.

OBJECT-TYPE

The value of tmnxOamLspTrCtlSrPlcyEndPtAddr specifies the Segment Routing (SR) policy endpoint address to be used for the test. tmnxOamLspTrCtlSrPlcyColor, tmnxOamLspTrCtlSrPlcyEndPtAddT, and tmnxOamLspTrCtlSrPlcyEndPtAddr must identify a known SR policy. Otherwise, the test will fail. The endpoint of a static SR policy is defined using TIMETRA-SR-POLICY-MIB::vRtrSrStaticPlcyEndPtAddrType TIMETRA-SR-POLICY-MIB::vRtrSrStaticPlcyEndPtAddr. When configuring an SR policy LSP trace test, the following objects must all be set in one snmpset PDU: tmnxOamLspTrCtlTestSubMode = 'srPolicy(7)', tmnxOamLspTrCtlSrPlcyColor, tmnxOamLspTrCtlSrPlcyEndPtAddT = 'ipv4(1)' or 'ipv6(2)', tmnxOamLspTrCtlSrPlcyEndPtAddr. The supported object combinations for LSP trace tests are listed in the tmnxOamLspTrCtlTable DESCRIPTION clause.

OBJECT-TYPE

The value of tmnxOamLspTrCtlSrPlcySegList specifies the Segment Routing (SR) policy segment list to be used for the test. The supported object combinations for LSP trace tests are listed in the tmnxOamLspTrCtlTable DESCRIPTION clause.

OBJECT-TYPE

tmnxOamLspTrMapTable contains the information obtained from RFC 4379 Downstream Mapping TLVs and/or RFC 6424 Downstream Detailed Mapping TLVs within reply PDUs for active 'lspTraceRoute' tests.

OBJECT-TYPE

tmnxOamLspTrMapEntry contains the information obtained from one RFC 4379 Downstream Mapping TLV (or one RFC 6424 Downstream Detailed Mapping TLV) within one 'lspTraceRoute' reply PDU. The first six indices specify an 'lspTraceRoute' reply PDU. The seventh index specifies one Downstream [Detailed] Mapping TLV within the PDU. Rows are created when a managed 'lspTraceRoute' reply PDU arrives containing one or more Downstream [Detailed] Mapping TLVs. Rows are deleted when the parent tmnxOamTrProbeHistoryTable row is deleted.

OBJECT-TYPE

The value of tmnxOamLspTrMapIndex specifies one RFC 4379 Downstream Mapping TLV (or one RFC 6424 Downstream Detailed Mapping TLV) within the reply PDU specified by the other indices. The agent starts assigning tmnxOamLspTrMapIndex values at 1.

OBJECT-TYPE

The value of tmnxOamLspTrMapDSIPv4Addr indicates the IPv4 address of the downstream LSR that this entry in the tmnxOamLspTrMapTable describes. If the interface to the downstream LSR is numbered, then the tmnxOamLspTrMapDSIPv4Addr can either be the downstream LSR's Router ID or the interface address of the downstream LSR. If the interface to the downstream LSR is unnumbered, the value of tmnxOamLspTrMapDSIPv4Addr indicates the downstream LSR's Router ID. This object was marked obsolete in release 13.0 R1.

OBJECT-TYPE

The value of tmnxOamLspTrMapAddrType indicates the type of addressing used on the replying interface. The value is copied from the Address Type field of the specified RFC 4379 Downstream Mapping TLV (or RFC 6424 Downstream Detailed Mapping TLV), and then mapped from the RFC code point number to the SROS code point number. The supported SROS code points are listed in the following table. Code Point Definition ------------------- ---------- 'ipv4Address (1)' RFC 4379 'ipv4Unnumbered(7)' RFC 4379 'ipv6Address (2)' RFC 4379 'ipv6Unnumbered(8)' RFC 4379 'nonIp (10)' RFC 6426 The supported combinations of tmnxOamLspTrMapAddrType, tmnxOamLspTrMapDsEgrIfNum, tmnxOamLspTrMapDsIngIfNum, tmnxOamLspTrMapDsIpAddressType, and tmnxOamLspTrMapDsIfAddressType are listed in the following table. _AddrType _EgrIfNum _IngIfNum _IpAddressType _IfAddressType ---------------- --------- --------- -------------- -------------- 'ipv4Address' zero zero 'ipv4' 'ipv4' 'ipv4Unnumbered' zero positive 'ipv4' 'unknown' 'ipv6Address' zero zero 'ipv6' 'ipv6' 'ipv6Unnumbered' zero positive 'ipv6' 'unknown' 'nonIp' positive positive 'unknown' 'unknown' In the table above, zero is the null interface number.

OBJECT-TYPE

When tmnxOamLspTrMapAddrType has a value of 'ipv4Address' tmnxOamLspTrMapDSIfAddr indicates the downstream LSR's interface address. When tmnxOamLspTrMapAddrType has a value of 'unnumbered', tmnxOamLspTrMapDSIfAddr indicates the index assigned by the upstream LSR to the interface. This object was marked obsolete in release 13.0 R1.

OBJECT-TYPE

The value of tmnxOamLspTrMapMTU indicates the largest MPLS frame (including the label stack) that fits on the interface to the downstream LSR (Label Switching Router). The value is copied from the MTU (Maximum Transmission Unit) field of the specified RFC 4379 Downstream Mapping TLV (or RFC 6424 Downstream Detailed Mapping TLV).

OBJECT-TYPE

The value of tmnxOamLspTrMapDSIndex indicates the unique index assigned to the pair of downstream router and interface addresses represented by this row in the tmnxOamLspTrMapTable. tmnxOamLspTrMapDSIndex was made obsolete in release 5.0.

OBJECT-TYPE

The value of tmnxOamLspTrMapDsEgrIfNum indicates the egress interface number reported by the replying node. This value is copied from the Downstream IP Address field of the specified RFC 4379 Downstream Mapping TLV (or the Downstream Address field of the specified RFC 6424 Downstream Detailed Mapping TLV). See the DESCRIPTION clause of tmnxOamLspTrMapAddrType for more information.

OBJECT-TYPE

The value of tmnxOamLspTrMapDsIngIfNum indicates the ingress interface number reported by the replying node. This value is copied from the Downstream Interface Address field of the specified RFC 4379 Downstream Mapping TLV (or RFC 6424 Downstream Detailed Mapping TLV). See the DESCRIPTION clause of tmnxOamLspTrMapAddrType for more information.

OBJECT-TYPE

The value of tmnxOamLspTrMapDsIpAddressType indicates the type of address in tmnxOamLspTrMapDsIpAddress. See the DESCRIPTION clause of tmnxOamLspTrMapAddrType for more information.

OBJECT-TYPE

The value of tmnxOamLspTrMapDsIpAddress indicates the Downstream IP Address field in the specified RFC 4379 Downstream Mapping TLV (or the Downstream Address field in the specified RFC 6424 Downstream Detailed Mapping TLV).

OBJECT-TYPE

The value of tmnxOamLspTrMapDsIfAddressType indicates the type of address in tmnxOamLspTrMapDsIfAddress. See the DESCRIPTION clause of tmnxOamLspTrMapAddrType for more information.

OBJECT-TYPE

The value of tmnxOamLspTrMapDsIfAddress indicates the Downstream Interface Address field in the specified RFC 4379 Downstream Mapping TLV (or RFC 6424 Downstream Detailed Mapping TLV).

OBJECT-TYPE

Defines the Nokia SROS OAM VPRN Trace Route Control Table for providing, via SNMP, the capability of performing Nokia SROS OAM 'vprnTraceRoute' test operations. The results of these tests are stored in the tmnxOamTrResultsTable, the tmnxOamTrProbeHistoryTable, the tmnxOamVprnTrRTTable and the tmnxOamVprnTrNextHopTable.

OBJECT-TYPE

Defines an entry in the tmnxOamVprnTrCtlTable. The first index element, tmnxOamTrCtlOwnerIndex, is of type SnmpAdminString, a textual convention that allows for use of the SNMPv3 View-Based Access Control Model (RFC 2575 [11], VACM) and allows a management application to identify its entries. The second index, tmnxOamTrCtlTestIndex, enables the same management application to have multiple outstanding requests.

OBJECT-TYPE

This object was obsoleted in release 4.0 and replaced with InetAddress objects tmnxOamVprnTrCtlSrcAddrType and tmnxOamVprnTrCtlSrcAddress.

OBJECT-TYPE

When the value of tmnxOamVprnTrCtlReplyControl is 'true', the OAM 'vprnTraceRoute' response is returned using the control plane. If its value is 'false', the packet is sent via the data plane. This object is optional and is not relevant when tmnxOamTrCtlTestMode has a value other than 'vprnTraceRoute'.

OBJECT-TYPE

The value of tmnxOamVprnTrCtlSrcAddrType specifies the type of Internet address stored in tmnxOamVprnTrCtlSrcAddress.

OBJECT-TYPE

The value of tmnxOamVprnTrCtlSrcAddress specifies the Internet address to be used as the source for performing an OAM 'vprnTraceRoute' operation when tmnxOamTrCtlTestMode has a value of 'vprnTraceRoute'. This parameter is required.

OBJECT-TYPE

Defines a table for storing the results of an OAM 'vprnTraceRoute' probe operation. The number of entries for a test in this table is limited to the results of 3 runs. An entry in this table is created when the result of an OAM 'vprnTraceRoute' probe is determined. An entry is removed from this table when its corresponding tmnxOamTrCtlEntry is deleted.

OBJECT-TYPE

Defines an entry in the tmnxOamVprnTrL3MapTable. The first two index elements identify the tmnxOamTrCtlEntry that a tmnxOamVprnTrL3MapEntry belongs to. The third index element identifies an OAM trace route test run. The fourth index element selects a single Nokia SROS OAM 'vprnTraceRoute' operation result. The fifth and sixth indexes select the hop and the probe at that hop for a particular Nokia SROS OAM 'vprnTraceRoute' operation. The seventh index selects either the requestor's or responder's L3 route information.

OBJECT-TYPE

The value of tmnxOamVprnTrL3MapReporter specifies who reported the route information in this row entry. It may have come from the 'vprnTraceRoute' requestor's local information or it may be from the remote 'vprnTraceRoute' responder.

OBJECT-TYPE

The value of tmnxOamVprnTrL3MapRouterID indicates the router ID of the node, requestor or responder, that provided this route information.

OBJECT-TYPE

This object was obsoleted in release 4.0 and replaced with InetAddress objects tmnxOamVprnTrL3MapDestAddrType and tmnxOamVprnTrL3MapDestAddrType.

OBJECT-TYPE

This object was obsoleted in release 4.0 and replaced with InetAddress object tmnxOamVprnTrL3MapDestMaskLen.

OBJECT-TYPE

The value of tmnxOamVprnTrL3MapRteVprnLabel indicates the VPRN label associated with the route information returned in this 'vprnTraceRoute' reply.

OBJECT-TYPE

The value of tmnxOamVprnTrL3MapRteMetrics indicates the metrics to be used with this vprnTraceRoute route.

OBJECT-TYPE

The value of tmnxOamVprnTrL3MapRteLastUp indicates the time this route was last added or modified by the protocol.

OBJECT-TYPE

The value of tmnxOamVprnTrL3MapRteOwner indicates the protocol that owns this route. It may be a local or remote route.

OBJECT-TYPE

The value of tmnxOamVprnTrL3MapRtePref indicates the route preference value for this route.

OBJECT-TYPE

The value of tmnxOamVprnTrL3MapRteDist is the route distinguisher associated with the route information returned in this 'vprnTraceRoute' reply.

OBJECT-TYPE

The value of tmnxOamVprnTrL3MapNumNextHops indicates the number of entries in the tmnxOamVprnTrNextHopTable for this route.

OBJECT-TYPE

The value of tmnxOamVprnTrL3MapNumRteTargets indicates the number of entries in the tmnxOamVprnTrRTTable for this route.

OBJECT-TYPE

The value of tmnxOamVprnTrL3MapDestAddrType indicates the type of internet address stored in tmnxOamVprnTrL3MapDestAddress.

OBJECT-TYPE

The value of tmnxOamVprnTrL3MapDestAddress indicates the Internet address to be advertised for the route information returned by this 'vprnTraceRoute' reply. When used together with tmnxOamVprnTrL3MapDestMaskLen and tmnxOamVprnTrL3MapRteVprnLabel, a customer route can be identified.

OBJECT-TYPE

The value of tmnxOamVprnTrL3MapDestMaskLen indicates the number of prefix bits (prefix width) to be &-ed with the IP address in tmnxOamVprnTrL3MapDestAddress.

OBJECT-TYPE

Defines a table for storing the results of an OAM 'vprnTraceRoute' probe operation where a L3 route next hop list is returned. An entry in this table is created when the result of an OAM 'vprnTraceRoute' probe is determined. An entry is removed from this table when its corresponding tmnxOamTrCtlEntry is deleted.

OBJECT-TYPE

Defines an entry in the tmnxOamVprnTrNextHopTable. The first two index elements identify the tmnxOamTrCtlEntry that a tmnxOamVprnTrNextHopEntry belongs to. The third index element identifies an OAM trace route test run. The fourth, fifth and sixth index elements select a single OAM 'vprnTraceRoute' reply. The seventh index selects either the requestor's or responder's route information. The eighth index selects a single L3 next hop entry within a specific 'vprnTraceRoute' probe reply route information.

OBJECT-TYPE

The tmnxOamVprnTrNextHopIndex selects a single L3 next hop entry associated with the router information returned within a specific 'vprnTraceRoute' probe reply. The agent starts assigning tmnxOamVprnTrNextHopIndex values at 1.

OBJECT-TYPE

This object was obsoleted in release 6.0 and replaced with InetAddress objects tmnxOamVprnTrNextHopAddrType and tmnxOamVprnTrNextHopAddress.

OBJECT-TYPE

The value of tmnxOamVprnTrNextHopType indicates whether the route owner is a local route or a remote, BGP-VPRN, route.

OBJECT-TYPE

When the value of tmnxOamVprnTrNextHopType is 'remote' the value of tmnxOamVprnTrNextHopTunnelID indicates the tunnel ID used to reach this BGP next hop.

OBJECT-TYPE

When the value of tmnxOamVprnTrNextHopType is 'remote' the value of tmnxOamVprnTrNextHopTunnelType indicates the type of tunnel used to reach this BGP next hop.

OBJECT-TYPE

When the value of tmnxOamVprnTrNextHopType is 'local' the value of tmnxOamVprnTrNextHopIfIndex indicates the interface used to reach this ECMP next hop.

OBJECT-TYPE

tmnxOamVprnTrNextHopAddrType indicates the type of Internet address stored in tmnxOamVprnTrNextHopAddress. Address types 'unknown(0)', 'ipv4(1)', 'ipv6(2)', and 'ipv6z(4)' are supported.

OBJECT-TYPE

The value of tmnxOamVprnTrNextHopAddress is the Internet address for this L3 next hop entry.

OBJECT-TYPE

Defines a table for storing the results of an OAM 'vprnTraceRoute' probe operation where a L3 route target list is returned. An entry in this table is created when the result of an OAM 'vprnTraceRoute' probe is determined. An entry is removed from this table when its corresponding tmnxOamTrCtlEntry is deleted.

OBJECT-TYPE

Defines an entry in the tmnxOamVprnTrRTTable. The first two index elements identify the tmnxOamTrCtlEntry that a tmnxOamVprnTrRTEntry belongs to. The third index element identifies an OAM trace route test run. The fourth, fifth and sixth index elements select a single OAM 'vprnTraceRoute' reply. The seventh index selects either the probe requestor's or probe replier's route information. The eighth index selects successive L3 route target entries contained in a specific 'vprnTraceRoute' requestor or probe reply route information.

OBJECT-TYPE

The tmnxOamVprnTrRTIndex selects a single L3 route target entry associated with the router information returned within a specific 'vprnTraceRoute' probe reply. The agent starts assigning tmnxOamVprnTrRTIndex values at 1.

OBJECT-TYPE

The value of tmnxOamVprnTrRouteTarget is the route target ID for this L3 route target entry.

OBJECT-TYPE

Defines a table for storing the results of an OAM 'lspTraceRoute' probe operation when a Downstream Mapping TLV was returned. Each row represents a single downstream label within a returned downstream L2 mapping TLV. An entry in this table is created when the result of an OAM 'lspTraceRoute' probe is determined. An entry is removed from this table when its corresponding tmnxOamTrCtlEntry is deleted.

OBJECT-TYPE

Defines an entry in the tmnxOamLspTrDSLabelTable. The first two index elements identify the tmnxOamTrCtlEntry that a tmnxOamLspTrMapEntry belongs to. The third index element identifies a OAM trace route test run. The fourth index element selects the group of responses associated with a specific probe attempt. The fifth and sixth indexes select the hop and the probe at that hop for a particular Nokia SROS OAM Trace Route operation. The seventh index selects a single downstream L2 map entry within the specific probe reply. The eighth index selects successive downstream L2 label entries contained in a specific probe reply.

OBJECT-TYPE

The tmnxOamLspTrDSLabelIndex selects a single downstream L2 label entry within a specific L2 mapping entry reply. The agent starts assigning tmnxOamLspTrDSLabelIndex values at 1.

OBJECT-TYPE

The value of tmnxOamLspTrDSLabelLabel is the label used by the downstream router specified by this downstream L2 label entry.

OBJECT-TYPE

The value of tmnxOamLspTrDSLabelProtocol is the signaling protocol used by the router for the label specified by this downstream L2 label entry.

OBJECT-TYPE

Each row in tmnxOamMcastTrCtlTable contains the multicast-trace-route- specific configuration information needed to launch a multicast trace route test. The rest of the configuration information needed to launch the test resides in the corresponding row of tmnxOamTrCtlTable. Results of multicast trace route tests are stored in tmnxOamTrResultsTable, tmnxOamTrProbeHistoryTable, and tmnxOamMcastTrRespTable.

OBJECT-TYPE

The system creates a row in tmnxOamMcastTrCtlTable when a test's type (i.e. tmnxOamTrCtlTestMode) is set to 'mcastTraceRoute'. The system deletes a row in tmnxOamMcastTrCtlTable when the corresponding row in tmnxOamTrCtlTable is deleted.

OBJECT-TYPE

The value of tmnxOamMcastTrCtlVRtrID specifies the virtual router to be used for the test. The value specified must be the index of an active row in TIMETRA-VRTR-MIB::vRtrConfTable (i.e. tmnxOamMcastTrCtlVRtrID must match a valid TIMETRA-VRTR-MIB::vRtrID value). The only system-generated TIMETRA-VRTR-MIB::vRtrID value supported by tmnxOamMcastTrCtlVRtrID is 1 (i.e. the Base virtual router). tmnxOamTrCtlVRtrID (i.e. the equivalent object in the parent table) is irrelevant when the test type is 'mcastTraceRoute'. When directing an 'mcastTraceRoute' test to use a virtual router associated with a VPRN service, the virtual router can be specified using tmnxOamMcastTrCtlVRtrID (with the VPRN's virtual router number) or tmnxOamTrCtlServiceId (with the VPRN's service number). tmnxOamTrCtlServiceId is preferred, because service numbers are constant across an SROS reboot (while virtual routers may be renumbered). If non-default values are specified for both tmnxOamMcastTrCtlVRtrID and tmnxOamTrCtlServiceId, tmnxOamTrCtlServiceId is used.

OBJECT-TYPE

tmnxOamMcastTrCtlSrcIpAddr was obsoleted in release 4.0 and replaced with InetAddress objects tmnxOamMcastTrCtlSrcAddrType and tmnxOamMcastTrCtlSrcAddress.

OBJECT-TYPE

tmnxOamMcastTrCtlDestIpAddr was obsoleted in release 4.0 and replaced with InetAddress objects tmnxOamMcastTrCtlDestAddrType and tmnxOamMcastTrCtlDestAddress.

OBJECT-TYPE

tmnxOamMcastTrCtlRespIpAddr was obsoleted in release 4.0 and replaced with InetAddress objects tmnxOamMcastTrCtlRespAddrType and tmnxOamMcastTrCtlRespAddress.

OBJECT-TYPE

tmnxOamMcastTrCtlGrpIpAddr was obsoleted in release 4.0 and replaced with InetAddress objects tmnxOamMcastTrCtlGrpAddrType and tmnxOamMcastTrCtlGrpAddress.

OBJECT-TYPE

The value of tmnxOamMcastTrCtlHops specifies the maximum number of hops that will be traced along the path to the source. This object is optional.

OBJECT-TYPE

The value of tmnxOamMcastTrQueryId indicates the 24 bit random number that uniquely identifies the multicast trace query. When the router receives the response back from the first hop router, it maps the response to the query by looking at the query id in the packet.

OBJECT-TYPE

The value of tmnxOamMcastTrCtlSrcAddrType specifies the type of IP address stored in tmnxOamMcastTrCtlSrcAddress.

OBJECT-TYPE

The value of tmnxOamMcastTrCtlSrcAddress specifies the IP address to be used as the source address for the test. A non-empty address must be specified before the test is enabled.

OBJECT-TYPE

The value of tmnxOamMcastTrCtlDestAddrType specifies the type of IP address stored in tmnxOamMcastTrCtlDestAddress.

OBJECT-TYPE

The value of tmnxOamMcastTrCtlDestAddress specifies the IP address to be used as the destination address for the test. The multicast trace query is sent to this destination address. When the test is administratively enabled (using tmnxOamTrCtlAdminStatus), if tmnxOamMcastTrCtlDestAddrType is 'unknown(0)', SROS assigns a value to tmnxOamMcastTrCtlDestAddrType and tmnxOamMcastTrCtlDestAddress.

OBJECT-TYPE

The value of tmnxOamMcastTrCtlRespAddrType indicates the type of IP address stored in tmnxOamMcastTrCtlRespAddress.

OBJECT-TYPE

The value of tmnxOamMcastTrCtlRespAddress indicates the IP address to be used as the response address for the test.

OBJECT-TYPE

The value of tmnxOamMcastTrCtlGrpAddrType specifies the type of IP address stored in tmnxOamMcastTrCtlGrpAddress.

OBJECT-TYPE

The value of tmnxOamMcastTrCtlGrpAddress specifies the IP multicast group address for the test. A non-empty address must be specified before the test is enabled.

OBJECT-TYPE

The value of tmnxOamMcastTrCtlTestSubMode specifies the type of IP multicast trace route to be performed. 'mcastTraceRouteV1(1)' specifies an Internet Group Management Protocol (IGMP-based) multicast trace route test, using IETF draft-ietf-idmr-traceroute-ipm. 'mcastTraceRouteV2(2)' specifies a UDP-based multicast trace route test, using IETF draft-ietf-mboned-mtrace-v2.

OBJECT-TYPE

tmnxOamMcastTrRespTable contains multicast-specific information learned from probe responses for 'mcastTraceRoute' tests. tmnxOamTrProbeHistoryTable contains the remainder of the information learned from probe responses for the tests.

OBJECT-TYPE

tmnxOamMcastTrRespEntry contains multicast-specific information learned from one probe response of a 'mcastTraceRoute' test. A row is created when a tmnxOamTrProbeHistoryTable row is created for a 'mcastTraceRoute' test. A row is deleted when the corresponding tmnxOamTrProbeHistoryTable row is deleted.

OBJECT-TYPE

The value of tmnxOamMcastTrRespQueryArrivalTime indicates the time at which the specified hop received the multicast trace query/request. The timestamp is in 32 bit Network Time Protocol (NTP) format, as described in draft-ietf-idmr-traceroute-ipm.

OBJECT-TYPE

This object was obsoleted in release 4.0 and replaced with InetAddress objects tmnxOamMcastTrRespInIfAddrType and tmnxOamMcastTrRespInIfAddress.

OBJECT-TYPE

This object was obsoleted in release 4.0 and replaced with InetAddress objects tmnxOamMcastTrRespOutIfAddrType and tmnxOamMcastTrRespOutIfAddress.

OBJECT-TYPE

This object was obsoleted in release 4.0 and replaced with InetAddress objects tmnxOamMcastTrRespPhRtrAddrType and tmnxOamMcastTrRespPhRtrAddress.

OBJECT-TYPE

The value of tmnxOamMcastTrRespInPktCount indicates the number of multicast packets received for all groups and sources on the test's incoming interface. 2^32-1 is returned if no count can be reported. This counter has the same value as IF-MIB::ifInMulticastPkts for the test's incoming interface. This object is relevant when tmnxOamMcastTrCtlTestSubMode is 'mcastTraceRouteV1(1)'.

OBJECT-TYPE

The value of tmnxOamMcastTrRespOutPktCount indicates the number of multicast packets that have been transmitted or queued for transmission for all groups and sources on the test's outgoing interface. 2^32-1 is returned if no count can be reported. This counter has the same value as IF-MIB::ifOutMulticastPkts for the test's outgoing interface. This object is relevant when tmnxOamMcastTrCtlTestSubMode is 'mcastTraceRouteV1(1)'.

OBJECT-TYPE

The value of tmnxOamMcastTrRespSGPktCount indicates the number of packets from the test's source forwarded by this router to the test's group. 2^32-1 is returned if no count can be reported. The value of tmnxOamMcastTrRespSrcBit and tmnxOamMcastTrRespSrcMask influence the interpretation of the counter. This object is relevant when tmnxOamMcastTrCtlTestSubMode is 'mcastTraceRouteV1(1)'.

OBJECT-TYPE

The value of tmnxOamMcastTrRespRtgProtocol indicates the routing protocol in use between this router and the previous-hop router. This object is relevant when tmnxOamMcastTrCtlTestSubMode is 'mcastTraceRouteV1(1)'.

OBJECT-TYPE

The value of tmnxOamMcastTrRespFwdTtl indicates the TTL that a packet is required to have before it will be forwarded over the test's outgoing interface. This object is irrelevant when both 1. tmnxOamMcastTrCtlTestSubMode is 'mcastTraceRouteV2(2)'. 2. The test's IP address family (i.e. tmnxOamMcastTrCtlGrpAddrType) is IPv6.

OBJECT-TYPE

The value of tmnxOamMcastTrRespMBZBit indicates the Must Be Zero (MBZ) bit of an 'mcastTraceRoute' response probe. Zero is expected. This object is relevant when tmnxOamMcastTrCtlTestSubMode is 'mcastTraceRouteV1(1)'.

OBJECT-TYPE

The value of tmnxOamMcastTrRespSrcBit indicates how to interpret the packet counters tmnxOamMcastTrRespSGPktCount and tmnxOamMcastTrRespSGPktCountHC. If tmnxOamMcastTrRespSrcBit is zero, SROS counts the packets from the test's source address forwarded by this router to the test's group address. Otherwise, SROS counts the packets from the test's source prefix forwarded by this router to the test's group address. The source prefix is the source address, masked using tmnxOamMcastTrRespSrcMask.

OBJECT-TYPE

The value of tmnxOamMcastTrRespSrcMask indicates the prefix length used with the test's source address (i.e. tmnxOamMcastTrCtlSrcAddrType and tmnxOamMcastTrCtlSrcAddress) when computing tmnxOamMcastTrRespSGPktCount or tmnxOamMcastTrRespSGPktCountHC. If the router is forwarding solely on group state, then this value is larger than the maximum prefix length for the test's address family (i.e. 32 for IPv4; 128 for IPv6). This value is irrelevant if tmnxOamMcastTrRespSrcBit is zero.

OBJECT-TYPE

The value of tmnxOamMcastTrRespFwdCode indicates a forwarding information/error code: noError (0) - No error wrongIf (1) - Traceroute request arrived on an interface to which this router would not forward for this source,group,destination. pruneSent (2) - This router has sent a prune upstream which applies to the source and group in the traceroute request. pruneRecvd (3) - This router has stopped forwarding for this source and group in response to a request from the next hop router. scoped (4) - The group is subject to administrative scoping at this hop. noRoute (5) - This router has no route for the source or group and no way to determine a potential route. wrongLastHop (6) - This router is not the proper last-hop router. notForwarding(7) - This router is not forwarding this source,group out the outgoing interface for an unspecified reason. reachedRP (8) - Reached Rendezvous Point or Core. rpfIf (9) - Traceroute request arrived on the expected RPF interface for this source,group. noMulticast (10) - Traceroute request arrived on an interface which is not enabled for multicast. infoHidden (11) - One or more hops have been hidden from this trace. reachedGW (12) - Mtrace2 Request arrived on a gateway (e.g. a NAT or firewall) that hides the information between this router and the Mtrace2 client. unknownQuery(13) - A non-transitive Extended Query Type was received by a router which does not support the type. fatalError (128) - Router may know the previous hop but cannot forward the message to it. noSpace (129) - There was not enough room to insert another response data block in the packet. oldRouter (130) - The previous hop router does not understand traceroute requests. adminProhib(131) - Traceroute is administratively prohibited. unknown (132) - Unknown forwarding code received.

OBJECT-TYPE

The value of tmnxOamMcastTrRespInIfAddrType indicates the type of IP address stored in tmnxOamMcastTrRespInIfAddress.

OBJECT-TYPE

The value of tmnxOamMcastTrRespInIfAddress indicates the IP address of the interface on which packets from the test's source and group are expected to arrive. In the case of an mtrace test, the value is copied from the Incoming Interface Address field of the Response Data segment. In the case of an Mtrace2 IPv4 test, the value is copied from the Incoming Interface Address field of the IPv4 Mtrace2 Standard Response Block. The IPv4 address 0.0.0.0 is returned if the address is unknown. This object is irrelevant when both 1. tmnxOamMcastTrCtlTestSubMode is 'mcastTraceRouteV2(2)'. 2. The test's IP address family (i.e. tmnxOamMcastTrCtlGrpAddrType) is IPv6.

OBJECT-TYPE

The value of tmnxOamMcastTrRespOutIfAddrType indicates the type of IP address stored in tmnxOamMcastTrRespOutIfAddress.

OBJECT-TYPE

The value of tmnxOamMcastTrRespOutIfAddress indicates the IP address of the interface on which packets from the test's source and group flow to the specified destination. In the case of an mtrace test, the value is copied from the Outgoing Interface Address field of the Response Data segment. In the case of an Mtrace2 IPv4 test, the value is copied from the Outgoing Interface Address field of the IPv4 Mtrace2 Standard Response Block. The IPv4 address 0.0.0.0 is returned if the address is unknown. This object is irrelevant when both 1. tmnxOamMcastTrCtlTestSubMode is 'mcastTraceRouteV2(2)'. 2. The test's IP address family (i.e. tmnxOamMcastTrCtlGrpAddrType) is IPv6.

OBJECT-TYPE

The value of tmnxOamMcastTrRespPhRtrAddrType indicates the type of IP address stored in tmnxOamMcastTrRespPhRtrAddress.

OBJECT-TYPE

The value of tmnxOamMcastTrRespPhRtrAddress indicates the IP address of the router from which this router expects packets for this source. This may be a multicast group (e.g. ALL-[protocol]-ROUTERS.MCAST.NET) if the previous hop is not known because of the workings of the multicast routing protocol. In the case of an mtrace test, the value is copied from the Previous-Hop Router Address field of the Response Data segment. In the case of an Mtrace2 IPv4 test, the value is copied from the Upstream Router Address field of the IPv4 Mtrace2 Standard Response Block. In the case of an Mtrace2 IPv6 test, the value is copied from the Remote Address field of the IPv6 Mtrace2 Standard Response Block. If the address is unknown, an all-zeros IPv4 or IPv6 address is returned.

OBJECT-TYPE

The value of tmnxOamMcastTrRespInPktCountHC indicates the number of multicast packets received for all groups and sources on the test's incoming interface. 2^64-1 is returned if no count can be reported. This counter has the same value as IF-MIB::ifHCInMulticastPkts for the test's incoming interface. This object is relevant when tmnxOamMcastTrCtlTestSubMode is 'mcastTraceRouteV2(2)'.

OBJECT-TYPE

The value of tmnxOamMcastTrRespOutPktCountHC indicates the number of multicast packets that have been transmitted or queued for transmission for all groups and sources on the test's outgoing interface. 2^64-1 is returned if no count can be reported. This counter has the same value as IF-MIB::ifHCOutMulticastPkts for the test's outgoing interface. This object is relevant when tmnxOamMcastTrCtlTestSubMode is 'mcastTraceRouteV2(2)'.

OBJECT-TYPE

The value of tmnxOamMcastTrRespSGPktCountHC indicates the number of packets from the test's source forwarded by this router to the test's group. 2^64-1 is returned if no count can be reported. The value of tmnxOamMcastTrRespSrcBit and tmnxOamMcastTrRespSrcMask influence the interpretation of the counter. This object is relevant when tmnxOamMcastTrCtlTestSubMode is 'mcastTraceRouteV2(2)'.

OBJECT-TYPE

The value of tmnxOamMcastTrRespRtgProtocol2 indicates the unicast routing protocol running between this router and the upstream router. The code points are the IANA-RTPROTO-MIB::IANAipRouteProtocol code points, with 'unknown(0)' added. This object is relevant when tmnxOamMcastTrCtlTestSubMode is 'mcastTraceRouteV2(2)'.

OBJECT-TYPE

The value of tmnxOamMcastTrRespMcastRtgProto indicates the multicast routing protocol in use between this router and the upstream router. The code points are the IANA-RTPROTO-MIB::IANAipMRouteProtocol code points, with 'unknown(0)' added. This object is relevant when tmnxOamMcastTrCtlTestSubMode is 'mcastTraceRouteV2(2)'.

OBJECT-TYPE

The value of tmnxOamMcastTrRespInIfIndex indicates the value in the Incoming Interface ID field of the IPv6 Mtrace2 Standard Response Block. In the case of an IPv6 Mtrace2 Standard Response Block provided by a router running SROS, the value returned is a global interface identifier (i.e. a TIMETRA-VRTR-MIB::vRtrIfGlobalIndex value). This object is relevant when both 1. tmnxOamMcastTrCtlTestSubMode is 'mcastTraceRouteV2(2)'. 2. The test's IP address family (i.e. tmnxOamMcastTrCtlGrpAddrType) is IPv6.

OBJECT-TYPE

The value of tmnxOamMcastTrRespOutIfIndex indicates the value in the Outgoing Interface ID field of the IPv6 Mtrace2 Standard Response Block. In the case of an IPv6 Mtrace2 Standard Response Block provided by a router running SROS, the value returned is a global interface identifier (i.e. a TIMETRA-VRTR-MIB::vRtrIfGlobalIndex value). This object is relevant when both 1. tmnxOamMcastTrCtlTestSubMode is 'mcastTraceRouteV2(2)'. 2. The test's IP address family (i.e. tmnxOamMcastTrCtlGrpAddrType) is IPv6.

OBJECT-TYPE

The value of tmnxOamMcastTrRespLocalAddrType indicates the type of IP address stored in tmnxOamMcastTrRespLocalAddress.

OBJECT-TYPE

The value of tmnxOamMcastTrRespLocalAddress indicates the IP address of the router that provided this 'mcastTraceRoute(4)' response. The value is copied from the Local Address field of the IPv6 Mtrace2 Standard Response Block. This object is relevant when both 1. tmnxOamMcastTrCtlTestSubMode is 'mcastTraceRouteV2(2)'. 2. The test's IP address family (i.e. tmnxOamMcastTrCtlGrpAddrType) is IPv6.

OBJECT-TYPE

Each row in tmnxOamLTtraceCtlTable contains the LDP-tree-trace-specific configuration information needed to launch a foreground LDP (Label Distribution Protocol) tree trace test. The rest of the configuration information needed to launch the test resides in the corresponding row of tmnxOamTrCtlTable. Results of LDP tree trace tests are stored in tmnxOamLTtraceResultsTable and tmnxOamLTtraceHopInfoTable.

OBJECT-TYPE

The system creates a row in tmnxOamLTtraceCtlTable when a row is created in tmnxOamTrCtlTable with tmnxOamTrCtlTestMode set to 'ldpTreeTrace'. The system deletes a row in tmnxOamLTtraceCtlTable when the corresponding row in tmnxOamTrCtlTable is deleted.

OBJECT-TYPE

The value of tmnxOamLTtraceCtlLdpPrefixType specifies the type of Internet address stored in tmnxOamLTtraceCtlLdpPrefix.

OBJECT-TYPE

The value of tmnxOamLTtraceCtlLdpPrefix specifies the Internet address prefix for the LDP based LSP for this LDP tree trace test.

OBJECT-TYPE

The value of tmnxOamLTtraceCtlLdpPrefixLen specifies the Internet address prefix length for the LDP based LSP for this LDP tree trace test. The value of this parameter is valid only when the LDP prefix (tmnxOamLTtraceCtlLdpPrefix) has been specified.

OBJECT-TYPE

The value of tmnxOamLTtraceCtlMaxPath specifies the maximum number of paths that can be discovered for the given LDP Prefix (tmnxOamLTtraceCtlLdpPrefix).

OBJECT-TYPE

The value of tmnxOamLTtraceCtlDownstreamMpTlv specifies the type of downstream mapping TLV to insert in the MPLS echo request PDUs when launching the test. When an LDP tree trace test is created, the value of this object defaults to the value of the global configuration object tmnxOamMplsEchoDownstreamMapTlv.

OBJECT-TYPE

The value of tmnxOamLTtraceMaxConRequests indicates the maximum number of concurrent LDP Tree Trace manual discovery sessions that are allowed within an agent implementation.

OBJECT-TYPE

tmnxOamLTtraceResultsTable defines the Nokia SROS OAM Trace Route Test Results Table for keeping track of the status of a tmnxOamTrCtlEntry having tmnxOamTrCtlTestMode as ldpTreeTrace. An entry is added to the tmnxOamLTtraceResultsTable when an tmnxOamTrCtlEntry is created with tmnxOamTrCtlTestMode having value 'ldpTreeTrace'. An entry is removed from the tmnxOamTrResultsTable when such a corresponding entry, tmnxOamTrCtlEntry, is deleted.

OBJECT-TYPE

tmnxOamLTtraceResultsEntry represents a row in the tmnxOamLTtraceResultsTable. The two indices of the tmnxOamLTtraceResultsTable are the same as that in the tmnxOamTrCtlTable in order for a tmnxOamLTtraceResultsEntry to correspond to the tmnxOamTrCtlEntry that caused it to be created.

OBJECT-TYPE

The value of tmnxOamLTtraceResultsDisPaths indicates the number of discovered ECMP paths in this OAM LDP Tree discovery test.

OBJECT-TYPE

The value of tmnxOamLTtraceResultsFailedHops indicates the number of hops from which no successful response was received during this OAM LDP Tree discovery test.

OBJECT-TYPE

The value of tmnxOamLTtraceResultsDisState indicates the current state of the discovery process for the LDP IP prefix (tmnxOamLTtraceCtlLdpPrefix) in this OAM LDP Tree discovery test.

OBJECT-TYPE

The value of tmnxOamLTtraceResultsDisStatus indicates the current discovery status bits for the LDP IP prefix (tmnxOamLTtraceCtlLdpPrefix) in this OAM LDP Tree discovery test.

OBJECT-TYPE

tmnxOamLTtraceHopInfoTable defines the Nokia SROS OAM LDP Trace Hops table for keeping track of the results of an LDP Tree Trace test on a per hop basis. An entry is added to the tmnxOamLTtraceHopInfoTable when a hop is discovered after setting the tmnxOamTrCtlAdminStatus object of the tmnxOamTrCtlEntry (having tmnxOamTrCtlTestMode as ldpTreeTrace) to 'enabled(1)'. An entry is removed from the tmnxOamLTtraceHopInfoTable when its corresponding tmnxOamTrCtlEntry is deleted.

OBJECT-TYPE

tmnxOamLTtraceHopInfoEntry represents a row in the tmnxOamLTtraceHopInfoTable. The first two indices of the tmnxOamLTtraceHopInfoTable are the same as the tmnxOamTrCtlTable in order for a tmnxOamLTtraceHopInfoEntry to correspond to the tmnxOamTrCtlEntry that caused it to be created. The third index element, tmnxOamLTtraceHopIndex, selects a hop in an Nokia SROS LDP Tree Trace discovered path.

OBJECT-TYPE

The value of tmnxOamLTtraceHopIndex indicates the hop index for an Nokia SROS OAM Trace hop for an LDP Tree Trace test. The hop index values are assigned starting at 1.

OBJECT-TYPE

The value of tmnxOamLTtraceUpStreamHopIndex indicates the hop index (tmnxOamLTtraceHopIndex) of its upstream hop discovered during the LDP Tree Trace test. The value of tmnxOamLTtraceUpStreamHopIndex is 0 for the hops which are the root of the different discovered paths for the LDP Tree Trace test.

OBJECT-TYPE

The value of tmnxOamLTtraceHopAddrType indicates the type of Internet address stored in tmnxOamLTtraceHopAddr.

OBJECT-TYPE

The value of tmnxOamLTtraceHopAddr indicates the IP address of a hop for a given LDP based LSP associated with the OAM LDP Tree trace test.

OBJECT-TYPE

The value of tmnxOamLTtraceHopDstAddrType indicates the type of Internet address stored in tmnxOamLTtraceHopDstAddr.

OBJECT-TYPE

The value of tmnxOamLTtraceHopDstAddr indicates the destination IP address (127 Address) of a path associated with the hop.

OBJECT-TYPE

The value of tmnxOamLTtraceHopEgrNhAddrType indicates the type of Internet address stored in tmnxOamLTtraceHopEgrNhAddr.

OBJECT-TYPE

The value of tmnxOamLTtraceHopEgrNhAddr indicates the next hop IP address (wrt the ingress router), which is used to reach this Hop (tmnxOamLTtraceHopAddr).

OBJECT-TYPE

The value of tmnxOamLTtraceHopDisTtl indicates the label time-to-live value used to discover this hop.

OBJECT-TYPE

The value of tmnxOamLTtraceHopLastRc indicates the OAM return code received in the OAM trace response.

OBJECT-TYPE

The value of tmnxOamLTtraceHopDiscoveryState indicates the current discovery state of this hop.

OBJECT-TYPE

The value of tmnxOamLTtraceHopDiscoveryTime indicates the sysUpTime when the hop was discovered.

OBJECT-TYPE

The value of tmnxOamLTtraceHopLabel1 indicates the first (top of the label stack) label for this hop.

OBJECT-TYPE

The value of tmnxOamLTtraceHopLabel2 indicates the second label for this hop.

OBJECT-TYPE

The value of tmnxOamLTtraceHopLabel3 indicates the third label for this hop.

OBJECT-TYPE

The value of tmnxOamLTtraceHopLabel4 indicates the fourth label for this hop.

OBJECT-TYPE

The value of tmnxOamLTtraceHopLabel5 indicates the fifth label for this hop.

OBJECT-TYPE

The value of tmnxOamLTtraceHopLabel6 indicates the sixth label for this hop.

OBJECT-TYPE

The value of tmnxOamLTtraceHopIfAddrType indicates the IP address type for the interface IP address for this hop.

OBJECT-TYPE

The value of tmnxOamLTtraceHopIfAddress indicates the IP Address for the interface for this hop.

OBJECT-TYPE

The value of tmnxOamLTtraceHopRouterIdType indicates the IP address type for the Router ID for this hop.

OBJECT-TYPE

The value of tmnxOamLTtraceHopRouterId indicates the IP Address for the Router ID for this hop.

OBJECT-TYPE

tmnxOamLTtraceAutoConfigTable contains an entry for configuration information about each instance of Automatic (background) LDP Tree Trace.

OBJECT-TYPE

tmnxOamLTtraceAutoConfigEntry represents a row in the tmnxOamLTtraceAutoConfigTable. Each entry represents the Automatic LDP Tree Trace instance running on a virtual router. A row entry can be created and deleted through the tmnxOamLTtraceAutoRowStatus object.

OBJECT-TYPE

The value of tmnxOamLTtraceAutoRowStatus specifies the row status of the Auto LDP Tree Trace instance for the virtual router. A row with default attribute values is created by setting tmnxOamLTtraceAutoRowStatus to 'createAndGo'. A row entry can be destroyed by setting tmnxOamLTtraceAutoRowStatus to 'destroy'. An attempt to destroy a row will fail if tmnxOamLTtraceAutoAdminState is not set to 'outOfService'. Deletion of an entry in this table results in deletion of all the corresponding tables: tmnxOamLTtraceAutoStatusTable, tmnxOamLTtraceFecInfoTable, and tmnxOamLTtracePathInfoTable.

OBJECT-TYPE

The value of tmnxOamLTtraceAutoLastChanged indicates the last time the value of a writable object in this row was modified.

OBJECT-TYPE

The value of tmnxOamLTtraceAutoStorageType specifies the storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write access to any columnar objects in the row. This object was marked obsolete in SROS Release 14.0 R1. There is no replacement object.

OBJECT-TYPE

The value of tmnxOamLTtraceAutoAdminState specifies the state based on which the Auto LDP Tree Discovery process starts or stops. When the tmnxOamLTtraceAutoAdminState becomes 'inService', the Auto LDP Tree Discovery process starts, and periodic path-probing on the previously discovered paths, if any, continues. When the tmnxOamLTtraceAutoAdminState becomes 'outOfService', the Auto LDP Tree Discovery process and periodic path-probing on the discovered paths stop. At the start of the Auto discovery process, it selects the address FECs imported from LDP peers (TIMETRA-LDP-MIB:: vRtrLdpAddrFecTable) provided the FECs pass the configured policies (tmnxOamLTtraceAutoPolicy1..tmnxOamLTtraceAutoPolicy5). For all the FECs (tmnxOamLTtraceAutoTotalFecs), it automatically creates entries from the tmnxOamLTtraceFecInfoTable. As a part of the auto discovery process, it creates entries from the tmnxOamLTtracePathInfoTable for each discovered path.

OBJECT-TYPE

The value of tmnxOamLTtraceAutoFcName specifies the forwarding class of the MPLS Echo request packets. The forwarding class name must be one of those defined in the tFCNameTable in TIMETRA-QOS-MIB. The agent creates predefined entries in the tFCNameTable for 'premium', 'assured', and 'be' (for best-effort) forwarding classes. The actual forwarding class encoding is controlled by the network egress LSP-EXP mappings.

OBJECT-TYPE

The value of tmnxOamLTtraceAutoProfile specifies the profile value to be used with the forwarding class specified in tmnxOamLTtraceAutoFcName. The profile value must be consistent with the specified forwarding class: 'assured' = 'in' or 'out' 'premium' = 'in' 'be' = 'out'

OBJECT-TYPE

The value of tmnxOamLTtraceAutoDiscIntvl specifies number of minutes to wait before repeating LDP Tree Auto Discovery process.

OBJECT-TYPE

The value of tmnxOamLTtraceAutoMaxPath specifies the maximum number of paths that can be discovered for a selected IP Address FEC (tmnxOamLTtraceAutoTotalFecs).

OBJECT-TYPE

The value of tmnxOamLTtraceAutoTrMaxTtl specifies the maximum label time-to-live value for an LSP trace request during the tree discovery.

OBJECT-TYPE

The value of tmnxOamLTtraceAutoTrTimeOut specifies the timeout value, in seconds, for an lsp trace request during the tree discovery.

OBJECT-TYPE

The value of tmnxOamLTtraceAutoTrMaxFailures specifies the maximum number of consecutive timeouts allowed before terminating an lsp trace request to a hop.

OBJECT-TYPE

The value of tmnxOamLTtraceAutoPolicy1 specifies the first policy used to filter LDP imported Address FECs.

OBJECT-TYPE

The value of tmnxOamLTtraceAutoPolicy2 specifies the second policy used to filter LDP imported Address FECs.

OBJECT-TYPE

The value of tmnxOamLTtraceAutoPolicy3 specifies the third policy used to filter LDP imported Address FECs.

OBJECT-TYPE

The value of tmnxOamLTtraceAutoPolicy4 specifies the fourth policy used to filter LDP imported Address FECs.

OBJECT-TYPE

The value of tmnxOamLTtraceAutoPolicy5 specifies the fifth policy used to filter LDP imported Address FECs.

OBJECT-TYPE

The value of tmnxOamLTtraceAutoProbeIntvl specifies the number of minutes to wait before repeating probing (pinging) a discovered path.

OBJECT-TYPE

The value of tmnxOamLTtraceAutoPrTimeOut specifies the timeout value, in minutes, for a ping request during probing. tmnxOamLTtraceAutoPrTimeOut cannot be greater than tmnxOamLTtraceAutoProbeIntvl.

OBJECT-TYPE

The value of tmnxOamLTtraceAutoPrMaxFailures specifies the maximum number of consecutive timeouts allowed before failing a path probe (ping).

OBJECT-TYPE

tmnxOamLTtraceAutoStatusTable contains an entry for operational information about each instance of Automatic (background) LDP Tree Trace.

OBJECT-TYPE

tmnxOamLTtraceAutoStatusEntry represents a row in the tmnxOamLTtraceAutoStatusTable. Entries cannot be created or deleted via SNMP Set operations. An entry is created whenever a row is created in tmnxOamLTtraceAutoConfigTable.

OBJECT-TYPE

The value of tmnxOamLTtraceAutoDiscoveryState indicates the current state of the discovery process.

OBJECT-TYPE

The value of tmnxOamLTtraceAutoTotalFecs indicates the number of Address FECs that have been selected for discovery during the current discovery process. An Address FEC imported from an LDP peer (TIMETRA-LDP-MIB::vRtrLdpAddrFecTable) is selected if it passes the associated policies (tmnxOamLTtraceAutoPolicy1.. tmnxOamLTtraceAutoPolicy5).

OBJECT-TYPE

The value of tmnxOamLTtraceAutoDisFecs indicates the number of selected Address FECs that have been discovered successfully during the current discovery process.

OBJECT-TYPE

The value of tmnxOamLTtraceAutoLastDisStart indicates the sysUpTime when the last Auto discovery process started. If no discovery process has started, the value will be 0.

OBJECT-TYPE

The value of tmnxOamLTtraceAutoLastDisEnd indicates the sysUpTime when the last Auto discovery process ended. Before the first discovery process ends, it would be 0. At the end of a discovery this value is set. This value is not reset during starting/restarting.

OBJECT-TYPE

The value of tmnxOamLTtraceAutoLastDisDur indicates the time (in seconds) it took to finish the last discovery process. If no test has been finished, the value is 0. This value is updated only when a discovery ends.

OBJECT-TYPE

tmnxOamLTtraceFecInfoTable contains entries for the operational information about the automatically selected FECs.

OBJECT-TYPE

tmnxOamLTtraceFecInfoEntry represents a row in the tmnxOamLTtraceFecInfoTable. Entries cannot be created and deleted via SNMP SET operations.

OBJECT-TYPE

The value of tmnxOamLTtraceFecPrefixType specifies the type of remote IP address stored in tmnxOamLTtraceFecPrefix. Currently only ipv4 type is supported.

OBJECT-TYPE

The value of tmnxOamLTtraceFecPrefix indicates the Internet address prefix for an LDP based LSP associated with the OAM LDP Tree trace test.

OBJECT-TYPE

The value of tmnxOamLTtraceFecPrefLen indicates the Internet address prefix length for the LDP based LSP associated with the OAM LDP Tree trace test.

OBJECT-TYPE

The value of tmnxOamLTtraceFecDiscoveryState indicates the current state of the discovery process for the Address FEC.

OBJECT-TYPE

The value of tmnxOamLTtraceFecDisStatusBits indicates the current discovery status bits for the Address FEC.

OBJECT-TYPE

The value of tmnxOamLTtraceFecDisPaths indicates the number of discovered ECMP paths for the Address FEC.

OBJECT-TYPE

The value of tmnxOamLTtraceFecFailedHops indicates the number of hops from which no successful response was received.

OBJECT-TYPE

The value of tmnxOamLTtraceFecLastDisEnd indicates the sysUpTime when the FEC was last discovered.

OBJECT-TYPE

The value of tmnxOamLTtraceFecFailedProbes indicates the number of discovered paths which are in failed probing state.

OBJECT-TYPE

The value of tmnxOamLTtraceFecProbeState indicates the current overall probing state for the discovered paths of the Address FEC. The tmnxOamLTtraceFecProbeState is considered as 'oK' when probing on all the associated discovered paths is OK. It is considered as 'failed' when probing on all the associated discovered paths failed. It is considered as partially failed when probing on one or more, but not all, discovered paths failed.

OBJECT-TYPE

The value of tmnxOamLTtraceFecSendErrProbes indicates the number of discovered paths which are experiencing problems in sending probe (ping) requests.

OBJECT-TYPE

tmnxOamLTtracePathInfoTable contains entries with operational information about the automatically discovered ECMP paths.

OBJECT-TYPE

tmnxOamLTtracePathInfoEntry represents a row in the tmnxOamLTtracePathInfoTable. Entries cannot be created and deleted via SNMP SET operations.

OBJECT-TYPE

The value of tmnxOamLTtracePathDstAddrType indicates the type of Internet address stored in tmnxOamLTtracePathDstAddr.

OBJECT-TYPE

The value of tmnxOamLTtracePathDstAddr indicates the destination IP address (127 Address) of a path for a given LDP based LSP associated with the OAM LDP Tree trace test.

OBJECT-TYPE

The value of tmnxOamLTtracePathRemAddrType indicates the type of Internet address stored in tmnxOamLTtracePathRemoteAddr.

OBJECT-TYPE

The value of tmnxOamLTtracePathRemoteAddr indicates the associated interface IP address or the router ID of the egress router.

OBJECT-TYPE

The value of tmnxOamLTtracePathEgrNhAddrType indicates the type of Internet address stored in tmnxOamLTtracePathEgrNhAddr.

OBJECT-TYPE

The value of tmnxOamLTtracePathEgrNhAddr indicates the next hop IP address (wrt the ingress router) used to reach the associated ECMP path endpoint.

OBJECT-TYPE

The value of tmnxOamLTtracePathDisTtl indicates the label time-to-live value used to discover the egress router for the path.

OBJECT-TYPE

The value of tmnxOamLTtracePathLastDisTime indicates the sysUpTime when the path was last discovered.

OBJECT-TYPE

The value of tmnxOamLTtracePathLastRc indicates the OAM return code received in the OAM ping response.

OBJECT-TYPE

The value of tmnxOamLTtracePathProbeState indicates the current probing (ping) state for the discovered ECMP path. The tmnxOamLTtracePathProbeState is considered as 'failed' when number of consecutive timeouts for the ping request reached its maximum allowed limit (tmnxOamLTtraceAutoPrMaxFailures). The tmnxOamLTtracePathProbeState is considered as 'oK' after receiving a successful ping response for the associated path.

OBJECT-TYPE

The value of tmnxOamLTtracePathProbeTmOutCnt indicates the number of consecutive timeouts for the associated ping request. This tmnxOamLTtracePathProbeTmOutCnt is reset to 0 after receiving a successful ping response from the path destination.

OBJECT-TYPE

The value of tmnxOamLTtracePathProbeSendErr indicates the state of the last path probe (ping) request. The tmnxOamLTtracePathProbeSendErr is considered as 'failed' if the last probe (ping) request could not be sent due to some local failure else it is 'oK'.

OBJECT-TYPE

Each row in tmnxOamVccvTrCtlTable contains the VCCV-specific configuration information needed to launch a VCCV (Virtual Circuit Connectivity Verification) trace route test. The rest of the configuration information needed to launch the test resides in the corresponding row of tmnxOamTrCtlTable. Results of VCCV trace route tests are stored in tmnxOamTrResultsTable, tmnxOamTrProbeHistoryTable, and tmnxOamVccvTrNextPwSegmentTable. Four types of VCCV trace route tests are supported: AII Type 2, FEC-128 Pseudowire, Spoke SDP FEC, and Transport Profile Static. AII Type 2 and Spoke SDP FEC offer two ways to specify a VCCV trace route FEC-129 Pseudowire test. In the Transport Profile Static case, the test type is configured (using tmnxOamVccvTrCtlTestSubMode). In the other three cases, the test type is not configured (i.e. the default tmnxOamVccvTrCtlTestSubMode value 'unspecified(1)' is used). The following table has a row for each VCCV trace route test type, showing the mandatory and optional objects applicable to the test type. Abbreviated VCCV trace route test type names are used. Test Type Mandatory Objects Optional Objects ------ ------------------------------ --------------------------------- aiiTY2 tmnxOamVccvTrCtlSaiiAcId tmnxOamVccvTrCtlReplyMode tmnxOamVccvTrCtlSaiiGlobalId tmnxOamVccvTrCtlSaiiPrefix tmnxOamVccvTrCtlTaiiAcId tmnxOamVccvTrCtlTaiiGlobalId tmnxOamVccvTrCtlTaiiPrefix FEC128 tmnxOamVccvTrCtlSdpIdVcId tmnxOamVccvTrCtlReplyMode *tmnxOamVccvTrCtlSwitTgtFecType *tmnxOamVccvTrTgStaticCtlAgi *tmnxOamVccvTrTgStaticCtlSaiiGlbl *tmnxOamVccvTrTgStaticCtlSaiiNode *tmnxOamVccvTrTgStaticCtlSaiiAcId *tmnxOamVccvTrTgStaticCtlTaiiGlbl *tmnxOamVccvTrTgStaticCtlTaiiNode *tmnxOamVccvTrTgStaticCtlTaiiAcId sdpFEC tmnxOamVccvTrCtlSpokeSdpId *tmnxOamVccvTrCtlSaiiAcId *tmnxOamVccvTrCtlSaiiGlobalId *tmnxOamVccvTrCtlSaiiPrefix *tmnxOamVccvTrCtlTaiiAcId *tmnxOamVccvTrCtlTaiiGlobalId *tmnxOamVccvTrCtlTaiiPrefix tmnxOamVccvTrCtlReplyMode TPST tmnxOamVccvTrCtlSdpIdVcId *tmnxOamTrCtlSrcAddrType tmnxOamVccvTrCtlTestSubMode *tmnxOamTrCtlSrcAddress tmnxOamVccvTrCtlAssocChannel #tmnxOamVccvTrCtlSwitTgtFecType #tmnxOamVccvTrTgFec128CtlSrcAddrT #tmnxOamVccvTrTgFec128CtlSrcAddr #tmnxOamVccvTrTgFec128CtlDstAddrT #tmnxOamVccvTrTgFec128CtlDstAddr #tmnxOamVccvTrTgFec128CtlPwId #tmnxOamVccvTrTgFec128CtlPwType ALL N/A tmnxOamTrCtlDataSize tmnxOamTrCtlFcName tmnxOamTrCtlInitialTtl tmnxOamTrCtlInterval tmnxOamTrCtlMaxFailures tmnxOamTrCtlMaxTtl tmnxOamTrCtlProbesPerHop tmnxOamTrCtlProfile tmnxOamTrCtlTimeOut ------ ------------------------------ --------------------------------- In the table above, 1. The optional objects in the ALL row apply to all four VCCV trace route test types. 2. The characters '*' and '#' each mark an independent set of optional objects which must all be specified, or must all be unspecified. When an object combination other than a combination listed above is specified, values will be rejected or ignored, or the test will fail.

OBJECT-TYPE

The system creates a row in tmnxOamVccvTrCtlTable when a row is created in tmnxOamTrCtlTable with tmnxOamTrCtlTestMode set to 'vccvTraceRoute'. The system deletes a row in tmnxOamVccvTrCtlTable when the corresponding row in tmnxOamTrCtlTable is deleted.

OBJECT-TYPE

The value of tmnxOamVccvTrCtlSdpIdVcId specifies the SDP binding of the pseudowire to be tested by a VCCV trace route test. The all-zeros value indicates an unused SDP binding. The supported object combinations for VCCV trace route tests are listed in the tmnxOamVccvTrCtlTable DESCRIPTION clause.

OBJECT-TYPE

The value of tmnxOamVccvTrCtlReplyMode specifies the band to be used by the echo reply. ip (2) out-of-band reply controlChannel (4) inband reply The supported object combinations for VCCV trace route tests are listed in the tmnxOamVccvTrCtlTable DESCRIPTION clause.

OBJECT-TYPE

The value of tmnxOamVccvTrCtlSpokeSdpId specifies the spoke SDP identifier to be used when performing a VCCV trace route test on a FEC 129 pseudowire. A value of zero indicates that no spoke SDP identifier has been configured. The supported object combinations for VCCV trace route tests are listed in the tmnxOamVccvTrCtlTable DESCRIPTION clause.

OBJECT-TYPE

The value of tmnxOamVccvTrCtlSaiiGlobalId specifies the global identifier of the Source Attachment Individual Identifier (SAII) to be used when testing a FEC 129 AII Type 2 pseudowire. A value of zero indicates that no global identifier has been configured. The supported object combinations for VCCV trace route tests are listed in the tmnxOamVccvTrCtlTable DESCRIPTION clause.

OBJECT-TYPE

The value of tmnxOamVccvTrCtlSaiiPrefix specifies the prefix of the Source Attachment Individual Identifier (SAII) to be used when testing a FEC 129 AII Type 2 pseudowire. A value of zero indicates that no prefix has been configured. The supported object combinations for VCCV trace route tests are listed in the tmnxOamVccvTrCtlTable DESCRIPTION clause.

OBJECT-TYPE

The value of tmnxOamVccvTrCtlSaiiAcId specifies the attachment circuit identifier of the Source Attachment Individual Identifier (SAII) to be used when testing a FEC 129 AII Type 2 pseudowire. A value of zero indicates that no attachment circuit identifier has been configured. The supported object combinations for VCCV trace route tests are listed in the tmnxOamVccvTrCtlTable DESCRIPTION clause.

OBJECT-TYPE

The value of tmnxOamVccvTrCtlTaiiGlobalId specifies the global identifier of the Target Attachment Individual Identifier (TAII) to be used when testing a FEC 129 AII Type 2 pseudowire. A value of zero indicates that no global identifier has been configured. The supported object combinations for VCCV trace route tests are listed in the tmnxOamVccvTrCtlTable DESCRIPTION clause.

OBJECT-TYPE

The value of tmnxOamVccvTrCtlTaiiPrefix specifies the prefix of the Target Attachment Individual Identifier (TAII) to be used when testing a FEC 129 AII Type 2 pseudowire. A value of zero indicates that no prefix has been configured. The supported object combinations for VCCV trace route tests are listed in the tmnxOamVccvTrCtlTable DESCRIPTION clause.

OBJECT-TYPE

The value of tmnxOamVccvTrCtlTaiiAcId specifies the attachment circuit identifier of the Target Attachment Individual Identifier (TAII) to be used when testing a FEC 129 AII Type 2 pseudowire. A value of zero indicates that no attachment circuit identifier has been configured. The supported object combinations for VCCV trace route tests are listed in the tmnxOamVccvTrCtlTable DESCRIPTION clause.

OBJECT-TYPE

The value of tmnxOamVccvTrCtlTestSubMode specifies the type of VCCV trace route test to perform. When this object is 'unspecified(1)', the type of VCCV trace route test to be performed is determined when the test is started, from the set of tmnxOamVccvTrCtlTable objects configured with non-default values. If there is a mismatch between tmnxOamVccvTrCtlTestSubMode and the type of the pseudowire to be tested, the test will fail. For example, if tmnxOamVccvTrCtlTestSubMode is 'static(2)', and there is no TIMETRA-SDP-MIB::sdpBindPwPathTable row for the test's SDP binding, the test will fail. The supported object combinations for VCCV trace route tests are listed in the tmnxOamVccvTrCtlTable DESCRIPTION clause.

OBJECT-TYPE

The value of tmnxOamVccvTrCtlAssocChannel specifies the launched echo request's usage of the Associated Channel (ACH) mechanism, when performing an MPLS-TP VCCV trace route test. When tmnxOamVccvTrCtlTestSubMode is 'static(2)', the default value for tmnxOamVccvTrCtlAssocChannel is 'nonIp(2)'. The supported object combinations for VCCV trace route tests are listed in the tmnxOamVccvTrCtlTable DESCRIPTION clause.

OBJECT-TYPE

The value of tmnxOamVccvTrCtlSwitTgtFecType specifies the type of downstream FEC (Forward Equivalence Class) segment to be tested. This object must be set to a non-default value when the path to be tested starts with a FEC segment, and switches to a FEC segment with a different type. For example, if the path to be tested starts with a static FEC, and switches to FEC 128, this object must be set to 'fec128(2)'.

OBJECT-TYPE

Defines a table for storing the results of an OAM 'vccvTraceRoute' probe operation where a VCCV next hop list is returned. An entry in this table is created when the result of an OAM 'vccvTraceRoute' probe is determined. An entry is removed from this table when its corresponding tmnxOamTrCtlEntry is deleted.

OBJECT-TYPE

Defines an entry in the tmnxOamVccvTrNextPwSegmentTable. The first two index elements identify the tmnxOamTrCtlEntry that a tmnxOamVccvTrNextPwSegmentEntry belongs to. The third index element identifies an OAM trace route test run. The fourth, fifth and sixth index elements select a single OAM 'vccvTraceRoute' reply.

OBJECT-TYPE

The value of tmnxOamVccvTrNextPwID indicates the next-hop pseudo-wire in the trace route operation for a specific 'vccvTraceRoute' probe reply. A value of '0' indicates that there are no further next-hops for a specific trace route operation.

OBJECT-TYPE

The value of tmnxOamVccvTrNextPwType indicates the next-hop pseudo-wire type in the trace route operation for a specific 'vccvTraceRoute' probe reply.

OBJECT-TYPE

The value of tmnxOamVccvTrNextSenderAddrType indicates the next-hop sender IP address type in the trace route operation for a specific 'vccvTraceRoute' probe reply.

OBJECT-TYPE

The value of tmnxOamVccvTrNextSenderAddr indicates the next-hop sender IP address in the trace route operation for a specific 'vccvTraceRoute' probe reply.

OBJECT-TYPE

The value of tmnxOamVccvTrNextRemoteAddrType indicates the next-hop remote IP address type in the trace route operation for a specific 'vccvTraceRoute' probe reply.

OBJECT-TYPE

The value of tmnxOamVccvTrNextRemoteAddr indicates the next-hop remote IP address in the trace route operation for a specific 'vccvTraceRoute' probe reply.

OBJECT-TYPE

The value of tmnxOamVccvTrNextSaiiGlobalId indicates the global identifier of the Source Attachment Individual Identifier (SAII) of a specific 'vccvTraceRoute' probe reply. A non-zero value is returned if a FEC 129 AII Type 2 pseudowire was probed. Otherwise, zero is returned.

OBJECT-TYPE

The value of tmnxOamVccvTrNextSaiiPrefix indicates the prefix of the Source Attachment Individual Identifier (SAII) of a specific 'vccvTraceRoute' probe reply. A non-zero value is returned if a FEC 129 AII Type 2 pseudowire was probed. Otherwise, zero is returned.

OBJECT-TYPE

The value of tmnxOamVccvTrNextSaiiAcId indicates the attachment circuit identifier of the Source Attachment Individual Identifier (SAII) of a specific 'vccvTraceRoute' probe reply. A non-zero value is returned if a FEC 129 AII Type 2 pseudowire was probed. Otherwise, zero is returned.

OBJECT-TYPE

The value of tmnxOamVccvTrNextTaiiGlobalId indicates the global identifier of the Target Attachment Individual Identifier (TAII) of a specific 'vccvTraceRoute' probe reply. A non-zero value is returned if a FEC 129 AII Type 2 pseudowire was probed. Otherwise, zero is returned.

OBJECT-TYPE

The value of tmnxOamVccvTrNextTaiiPrefix indicates the prefix of the Target Attachment Individual Identifier (TAII) of a specific 'vccvTraceRoute' probe reply. A non-zero value is returned if a FEC 129 AII Type 2 pseudowire was probed. Otherwise, zero is returned.

OBJECT-TYPE

The value of tmnxOamVccvTrNextTaiiAcId indicates the attachment circuit identifier of the Target Attachment Individual Identifier (TAII) of a specific 'vccvTraceRoute' probe reply. A non-zero value is returned if a FEC 129 AII Type 2 pseudowire was probed. Otherwise, zero is returned.

OBJECT-TYPE

The value of tmnxOamVccvTrNextTpAgi indicates the Service Identifier field of the RFC 6426 Static Pseudowire Sub-TLV of the reply PDU. If a pseudowire other than an MPLS-TP pseudowire was probed, the all-zeros value is returned.

OBJECT-TYPE

The value of tmnxOamVccvTrNextTpSaiiGlobalId indicates the Source Global ID field of the RFC 6426 Static Pseudowire Sub-TLV of the reply PDU. If a pseudowire other than an MPLS-TP pseudowire was probed, zero is returned.

OBJECT-TYPE

The value of tmnxOamVccvTrNextTpSaiiNodeId indicates the Source Node ID field of the RFC 6426 Static Pseudowire Sub-TLV of the reply PDU. If a pseudowire other than an MPLS-TP pseudowire was probed, zero is returned.

OBJECT-TYPE

The value of tmnxOamVccvTrNextTpSaiiAcId indicates the Source Attachment Circuit ID field of the RFC 6426 Static Pseudowire Sub-TLV of the reply PDU. If a pseudowire other than an MPLS-TP pseudowire was probed, zero is returned.

OBJECT-TYPE

The value of tmnxOamVccvTrNextTpTaiiGlobalId indicates the Destination Global ID field of the RFC 6426 Static Pseudowire Sub-TLV of the reply PDU. If a pseudowire other than an MPLS-TP pseudowire was probed, zero is returned.

OBJECT-TYPE

The value of tmnxOamVccvTrNextTpTaiiNodeId indicates the Destination Node ID field of the RFC 6426 Static Pseudowire Sub-TLV of the reply PDU. If a pseudowire other than an MPLS-TP pseudowire was probed, zero is returned.

OBJECT-TYPE

The value of tmnxOamVccvTrNextTpTaiiAcId indicates the Destination Attachment Circuit ID field of the RFC 6426 Static Pseudowire Sub-TLV of the reply PDU. If a pseudowire other than an MPLS-TP pseudowire was probed, zero is returned.

OBJECT-TYPE

Defines the Nokia SROS OAM P2MP LSP Trace Control Table for providing, via SNMP, the capability of performing Nokia SROS OAM 'p2mpLspTrace' test operations for a single leaf egress node of an P2MP LSP. The results of these tests are stored in the tmnxOamTrResultsTable and the tmnxOamTrProbeHistoryTable.

OBJECT-TYPE

Defines an entry in the tmnxOamP2mpLspTrCtlTable. The first index element, tmnxOamTrCtlOwnerIndex, is of type SnmpAdminString, a textual convention that allows for use of the SNMPv3 View-Based Access Control Model (RFC 2575 [11], VACM) and allows a management application to identify its entries. The second index, tmnxOamTrCtlTestIndex, enables the same management application to have multiple outstanding requests.

OBJECT-TYPE

Administrative name of the target P2MP Labeled Switch Path (LSP) for this OAM P2MP LSP Trace test. This parameter is mandatory.

OBJECT-TYPE

This parameter identifies an instance of a P2MP LSP, either a primary or secondary instance of a P2MP LSP Tree.

OBJECT-TYPE

The value of tmnxOamP2mpLspTrCtlLeafIpAddr specifies the Internet address of the egress leaf node of a P2MP LSP Tree. This parameter is mandatory.

OBJECT-TYPE

The value of tmnxOamP2mpLspTrCtlLeafIpAddrType specifies the type of Internet address stored in tmnxOamP2mpLspTrCtlLeafIpAddr.

OBJECT-TYPE

Defines a table for storing the results of an OAM 'p2mpLspTrace' probe operation when a Downstream Mapping TLV was returned. Each row represents a single label map within the returned downstream mapping TLV. An entry in this table is created when the result of an OAM 'p2mpLspTrace' probe is determined. An entry is removed from this table when its corresponding tmnxOamTrCtlEntry is deleted.

OBJECT-TYPE

Defines an entry in the tmnxOamP2mpLspTrMapTable. The first two index elements identify the tmnxOamTrCtlEntry that a tmnxOamP2mpLspTrMapEntry belongs to. The third index element identifies an OAM trace route test run. The fourth index element selects the group of responses associated with a specific probe attempt. The fifth and sixth indexes select the hop and the probe at that hop for a particular Nokia SROS OAM Trace Route operation. The seventh index selects a single downstream L2 map entry within the specific probe reply.

OBJECT-TYPE

The value of tmnxOamP2mpLspTrMapIndex specifies a single L2 mapping entry within a specific 'p2mpLspTrace' probe reply. The agent starts assigning tmnxOamP2mpLspTrMapIndex values at 1.

OBJECT-TYPE

The value of tmnxOamP2mpLspTrMapDSIPv4Addr indicates the IPv4 address of the downstream LSR that this entry in the tmnxOamP2mpLspTrMapTable describes. If the interface to the downstream LSR is numbered, then the tmnxOamP2mpLspTrMapDSIPv4Addr can either be the downstream LSR's Router ID or the interface address of the downstream LSR. If the interface to the downstream LSR is unnumbered, the value of tmnxOamP2mpLspTrMapDSIPv4Addr indicates the downstream LSR's Router ID.

OBJECT-TYPE

The value of tmnxOamP2mpLspTrMapAddrType indicates the type of downstream interface address specified by tmnxOamP2mpLspTrMapDSIfAddr. The only valid values for tmnxOamP2mpLspTrMapAddrType are 'ipv4Address', 'ipv4Unnumbered', 'ipv6Address' and 'ipv6Unnumbered'.

OBJECT-TYPE

When tmnxOamP2mpLspTrMapAddrType has a value of 'ipv4Address' tmnxOamP2mpLspTrMapDSIfAddr indicates the downstream LSR's interface address. When tmnxOamP2mpLspTrMapAddrType has a value of 'unnumbered', tmnxOamP2mpLspTrMapDSIfAddr indicates the index assigned by the upstream LSR to the interface.

OBJECT-TYPE

The value of tmnxOamP2mpLspTrMapMTU indicates the largest MPLS frame (including the label stack) that fits on the interface to the downstream LSR.

OBJECT-TYPE

When the value of tmnxOamP2mpLspTrMapP2mpBranch is 'true', the 'p2mpLspTrace' response indicates that the responding router is a branch node of the P2MP LSP tree.

OBJECT-TYPE

When the value of tmnxOamP2mpLspTrMapP2mpBud is 'true', the 'p2mpLspTrace' response indicates that the responding router is a bud node of the P2MP LSP tree.

OBJECT-TYPE

Defines a table for storing the results of an OAM 'p2mpLspTrace' probe operation when a Downstream Mapping TLV was returned. Each row represents a single downstream label within a returned downstream L2 mapping TLV. An entry in this table is created when the result of an OAM 'p2mpLspTrace' probe is determined. An entry is removed from this table when its corresponding tmnxOamTrCtlEntry is deleted.

OBJECT-TYPE

Defines an entry in the tmnxOamP2mpLspTrDSLabelTable. The first two index elements identify the tmnxOamTrCtlEntry that a tmnxOamLspTrMapEntry belongs to. The third index element identifies a OAM trace route test run. The fourth index element selects the group of responses associated with a specific probe attempt. The fifth and sixth indexes select the hop and the probe at that hop for a particular Nokia SROS OAM Trace Route operation. The seventh index selects a single downstream L2 map entry within the specific probe reply. The eighth index selects successive downstream L2 label entries contained in a specific probe reply.

OBJECT-TYPE

The tmnxOamP2mpLspTrDSLabelIndex selects a single downstream L2 label entry within a specific L2 mapping entry reply. The agent starts assigning tmnxOamP2mpLspTrDSLabelIndex values at 1.

OBJECT-TYPE

The value of tmnxOamP2mpLspTrDSLabelLabel is the label used by the downstream router specified by this downstream L2 label entry.

OBJECT-TYPE

The value of tmnxOamP2mpLspTrDSLabelProtocol is the signaling protocol used by the router for the label specified by this downstream L2 label entry.

OBJECT-TYPE

tmnxOamEthCfmTrCtlTable contains Ethernet CFM-specific configuration information for 'ethCfmLinkTrace' tests. This table extends the tmnxOamTrCtlTable. A row is automatically created in this table when a row in tmnxOamTrCtlTable has tmnxOamTrCtlTestMode set to 'ethCfmLinkTrace'. Deleting a row in tmnxOamTrCtlTable automatically deletes the row (if any) with the same index values in tmnxOamEthCfmTrCtlTable. Test results are stored in tmnxOamTrResultsTable, tmnxOamTrProbeHistoryTable, tmnxOamTrHopsTable, and tmnxOamEthCfmTrPrHistTable.

OBJECT-TYPE

tmnxOamEthCfmTrCtlEntry defines an entry in the tmnxOamEthCfmTrCtlTable. Each index is an object in tmnxOamTrCtlTable.

OBJECT-TYPE

The value of tmnxOamEthCfmTrCtlTgtMacAddr specifies the destination MAC address for the test. A non-zero destination MAC address is required in each test frame sent for the test. The tmnxOamEthCfmTrCtlTgtMacAddr must be assigned a non-default value. Otherwise, an attempt to administratively enable the test (using tmnxOamSaaCtlAdminStatus) will fail.

OBJECT-TYPE

The value of tmnxOamEthCfmTrCtlSrcMdIndex specifies the source CFM maintenance domain index for the test. Zero is the null CFM maintenance domain index.

OBJECT-TYPE

The value of tmnxOamEthCfmTrCtlSrcMaIndex specifies the source CFM maintenance association index for the test. Zero is the null CFM maintenance association index.

OBJECT-TYPE

The value of tmnxOamEthCfmTrCtlSrcMepId specifies the source Maintenance association End Point Identifier (MEP ID) for the test. Zero is the null MEP ID.

OBJECT-TYPE

The value of tmnxOamEthCfmTrCtlRemoteMepId specifies the remote Maintenance association End Point Identifier (MEP ID) for the test. A non-zero destination MAC address is required in each test frame sent for the test. The destination MAC address can be specified directly (using tmnxOamEthCfmTrCtlTgtMacAddr) or indirectly (using this object). Exactly one of tmnxOamEthCfmTrCtlTgtMacAddr and tmnxOamEthCfmTrCtlRemoteMepId must be assigned a non-default value. Otherwise, an attempt to administratively enable the test (using tmnxOamSaaCtlAdminStatus) will fail. Suppose this object is assigned a non-default value. Then, at the start of each test run, SROS reads TIMETRA-IEEE8021-CFM-MIB::tmnxDot1agCfmLearnedRmtMacAddr to find the destination MAC address to use for the test run. The following index values are used for the read: tmnxOamEthCfmTrCtlSrcMdIndex, tmnxOamEthCfmTrCtlSrcMaIndex, tmnxOamEthCfmTrCtlSrcMepId, tmnxOamEthCfmTrCtlRemoteMepId. If the search fails to find a destination MAC address, no test frames will be sent for the test run. The number of frames to be sent during a test run is configured using tmnxOamTrCtlProbesPerHop, tmnxOamTrCtlInitialTtl, and tmnxOamTrCtlMaxTtl. Configuring tmnxOamEthCfmTrCtlRemoteMepId (instead of tmnxOamEthCfmTrCtlDestMacAddr) has the following advantage: if the hardware hosting the test's far end is replaced (meaning a new destination MAC address is present), the test does not need to be reconfigured.

OBJECT-TYPE

tmnxOamEthCfmTrPrHistTable contains Ethernet CFM-specific probe history for 'ethCfmLinkTrace' tests. This table extends the tmnxOamTrProbeHistoryTable. A row is automatically created in this table when a row is created in tmnxOamTrProbeHistoryTable for a test with tmnxOamTrCtlTestMode set to 'ethCfmLinkTrace'. Deleting a row in tmnxOamTrProbeHistoryTable automatically deletes the row (if any) with the same index values in tmnxOamEthCfmTrPrHistTable.

OBJECT-TYPE

Defines an entry in the tmnxOamEthCfmTrPrHistTable. The indices are the same as the tmnxOamTrProbeHistoryTable indices.

OBJECT-TYPE

The value of tmnxOamEthCfmTrPrHistIngressMac indicates the ingress MAC address of the probe.

OBJECT-TYPE

The value of tmnxOamEthCfmTrPrHistEgressMac indicates the egress MAC address of the probe.

OBJECT-TYPE

The value of tmnxOamEthCfmTrPrHistRelayAction indicates the value of the Relay Action field in the Link Trace Reply. 'unknown(0)' is returned when a Link Trace Reply has not arrived, or the Relay Action field in the Link Trace Reply is outside the expected range.

OBJECT-TYPE

The value of tmnxOamEthCfmTrPrHistForwarded indicates if a Link Trace Message was forwarded by the responding Maintenance Point (MP), as returned in the 'FwdYes' flag of the Flags field of the Link Trace Reply.

OBJECT-TYPE

The value of tmnxOamEthCfmTrPrHistTerminalMep indicates whether the forwarded Link Trace Message reached a MEP enclosing its MA, as returned in the Terminal MEP flag of the Flags field of the Link Trace Reply.

OBJECT-TYPE

tmnxOamLspTrFecStackTable has a row for each RFC 6424 FEC (Forwarding Equivalence Class) Stack Change sub-TLV present in a currently managed 'lspTraceRoute' reply PDU. The FEC Stack Change sub-TLV is a component of the RFC 6424 Downstream Detailed Mapping TLV. An 'lspTraceRoute' reply PDU can contain several Downstream Detailed Mapping TLVs. A Downstream Detailed Mapping TLV can contain several FEC Stack Change sub-TLVs. The set of tmnxOamLspTrFecStackTable rows for a reply PDU holds the set of FEC stack changes recorded in the reply PDU, including information about MPLS tunnels and/or LSP stitching on the tested LSP.

OBJECT-TYPE

A row in tmnxOamLspTrFecStackTable is created by the system for each RFC 6424 FEC Stack Change sub-TLV present in a currently managed 'lspTraceRoute' reply PDU. A row is deleted when the corresponding tmnxOamTrCtlTable row is deleted. The first six indices specify an 'lspTraceRoute' reply PDU. The first seven indices specify an RFC 6424 Downstream Detailed Mapping TLV within an 'lspTraceRoute' reply PDU. The eight indices specify an RFC 6424 FEC Stack Change sub-TLV within a Downstream Detailed Mapping TLV within an 'lspTraceRoute' reply PDU.

OBJECT-TYPE

The value of tmnxOamLspTrFecStackFecIndex specifies one RFC 6424 FEC Stack Change sub-TLV within the specified Downstream Detailed Mapping TLV.

OBJECT-TYPE

The value of tmnxOamLspTrFecStackOperType indicates the value of the following Operation Type field (where +-> indicates encapsulation): 'lspTraceRoute' reply PDU +-> RFC 6424 Downstream Detailed Mapping TLV +-> RFC 6424 FEC Stack Change sub-TLV +-> Operation Type field.

OBJECT-TYPE

The value of tmnxOamLspTrFecStackFecSubType indicates the value of the following Subtype field (where +-> indicates encapsulation): 'lspTraceRoute' reply PDU +-> RFC 6424 Downstream Detailed Mapping TLV +-> RFC 6424 FEC Stack Change sub-TLV +-> RFC 4379 Target FEC Stack TLV +-> RFC 4379 FEC-type-specific sub-TLV (e.g. BGP labeled IPv4 prefix sub-TLV) +-> Subtype field. This object maps the numeric value in the Subtype field to an ASCII string. The following examples illustrate the mapping. Subtype Field tmnxOamLspTrFecStackFecSubType -------------- ------------------------------ 1 'LDP IPv4 prefix (1)' 3 'RSVP IPv4 LSP (3)' 12 'BGP labeled IPv4 prefix (12)' 16 'Nil FEC (16)' 99 'Unknown (99)'

OBJECT-TYPE

The value of tmnxOamLspTrFecStackPrefixType indicates the type of address stored in tmnxOamLspTrFecStackPrefix.

OBJECT-TYPE

The value of tmnxOamLspTrFecStackPrefix indicates the value of an IP prefix (or IP address) field with the following encapsulation (where +-> indicates encapsulation): 'lspTraceRoute' reply PDU +-> RFC 6424 Downstream Detailed Mapping TLV +-> RFC 6424 FEC Stack Change sub-TLV +-> RFC 4379 Target FEC Stack TLV +-> RFC 4379 FEC-type-specific sub-TLV (e.g. LDP IPv4 Prefix sub-TLV) +-> FEC-type-specific IP prefix field. For example, the value returned could be the content of one of the fields shown in the following table. Field RFC 4379 Sub-TLV ------------------ ----------------------- Extended Tunnel ID RSVP IPv4 LSP IPv4 Prefix BGP Labeled IPv4 Prefix IPv4 Prefix LDP IPv4 Prefix If no IP prefix field is present in the reply PDU, tmnxOamLspTrFecStackPrefixType contains 'unknown(1)'.

OBJECT-TYPE

The value of tmnxOamLspTrFecStackPrefixLen indicates the value of an IP prefix length field with the following encapsulation (where +-> indicates encapsulation): 'lspTraceRoute' reply PDU +-> RFC 6424 Downstream Detailed Mapping TLV +-> RFC 6424 FEC Stack Change sub-TLV +-> RFC 4379 Target FEC Stack TLV +-> RFC 4379 FEC-type-specific sub-TLV (e.g. LDP IPv4 Prefix sub-TLV) +-> FEC-type-specific IP prefix length field. For example, the value returned could be the content of one of the fields shown in the following table. Field RFC 4379 Sub-TLV ------------- ----------------------- Prefix Length BGP Labeled IPv4 Prefix Prefix Length LDP IPv4 Prefix If no relevant IP prefix length field is present in the reply PDU, tmnxOamLspTrFecStackPrefixLen contains 32 (for an IPv4 address), or 128 (for an IPv6 address).

OBJECT-TYPE

The value of tmnxOamLspTrFecStackRemPeerAddrT indicates the type of address stored in tmnxOamLspTrFecStackRemPeerAddr.

OBJECT-TYPE

The value of tmnxOamLspTrFecStackRemPeerAddr indicates the value contained in the remote peer address field with the following encapsulation (where +-> indicates encapsulation): 'lspTraceRoute' reply PDU +-> RFC 6424 Downstream Detailed Mapping TLV +-> RFC 6424 FEC Stack Change sub-TLV +-> Remote Peer Address field.

OBJECT-TYPE

tmnxOamVccvTrTgFec128CtlTable contains the target information for VCCV (Virtual Circuit Connectivity Verification) trace route tests which switch to downstream FEC (Forward Equivalence Class) 128 segments.

OBJECT-TYPE

tmnxOamVccvTrTgFec128CtlEntry contains the target information for a VCCV trace route test which switches to a downstream FEC 128 segment. The values in a row are used to fill a 'FEC 128 Pseudowire' sub-TLV (Type, Length, Value) within the 'Target FEC Stack' TLV within the launched VCCV trace route request. A row is created when the test's tmnxOamVccvTrCtlSwitTgtFecType is set to 'fec128(2)'. A row is destroyed when the tmnxOamVccvTrCtlTable row is destroyed. All the objects in a row must be set in one SNMP Set PDU. Otherwise, the SNMP Set PDU will be rejected.

OBJECT-TYPE

The value of tmnxOamVccvTrTgFec128CtlSrcAddrT specifies the address type of tmnxOamVccvTrTgFec128CtlSrcAddr.

OBJECT-TYPE

The value of tmnxOamVccvTrTgFec128CtlSrcAddr specifies the value to be copied into the Sender's PE Address (Sender's Provider Edge Address) field of the 'FEC 128 Pseudowire' sub-TLV within the 'Target FEC Stack' TLV within the launched VCCV trace route request.

OBJECT-TYPE

The value of tmnxOamVccvTrTgFec128CtlDstAddrT specifies the address type of tmnxOamVccvTrTgFec128CtlDstAddr.

OBJECT-TYPE

The value of tmnxOamVccvTrTgFec128CtlDstAddr specifies the value to be copied into the 'Remote PE Address' (Remote Provider Edge Address) field of the 'FEC 128 Pseudowire' sub-TLV within the 'Target FEC Stack' TLV within the launched VCCV trace route request.

OBJECT-TYPE

The value of tmnxOamVccvTrTgFec128CtlPwId specifies the value to be copied into the 'PW ID' (Pseudowire Identifier) field of the 'FEC 128 Pseudowire' sub-TLV within the 'Target FEC Stack' TLV within the launched VCCV trace route request. Zero indicates no Pseudowire Identifier has been configured.

OBJECT-TYPE

The value of tmnxOamVccvTrTgFec128CtlPwType specifies the value to be copied into the 'PW Type' (Pseudowire Type) field of the 'FEC 128 Pseudowire' sub-TLV within the 'Target FEC Stack' TLV within the launched VCCV trace route request. The code points are defined in RFC 4446. SROS supports services corresponding to the following RFC 4446 PW Type code points. PW Type Description ------- --------------------------------------- 2 ATM AAL5 SDU VCC transport 3 ATM transparent cell transport 5 Ethernet 9 ATM n-to-one VCC cell transport 10 ATM n-to-one VPC cell transport 17 Structure-agnostic E1 over packet 18 Structure-agnostic T1 (DS1) over packet 21 CES over PSN basic mode 23 CES over PSN TDM with CAS Zero indicates no Pseudowire Type has been configured.

OBJECT-TYPE

tmnxOamVccvTrTgStaticCtlTable contains the target information for VCCV (Virtual Circuit Connectivity Verification) trace route tests which switch to downstream static (i.e. MPLS-TP) segments.

OBJECT-TYPE

tmnxOamVccvTrTgStaticCtlEntry contains the target information for a VCCV trace route test which switches to a downstream static (i.e. MPLS-TP) segment. The values in a row are used to fill a 'Static Pseudowire' sub-TLV (Type, Length, Value) within the 'Target FEC Stack' TLV within the launched VCCV trace route request. A row is created when the test's tmnxOamVccvTrCtlSwitTgtFecType is set to 'static(3)'. A row is destroyed when the tmnxOamVccvTrCtlTable row is destroyed. All the objects in a row must be set in one SNMP Set PDU. Otherwise, the SNMP Set PDU will be rejected.

OBJECT-TYPE

The value of tmnxOamVccvTrTgStaticCtlAgi specifies the value to be copied into the 'Service Identifier' field of the 'Static Pseudowire' sub-TLV within the 'Target FEC Stack' TLV within the launched VCCV trace route request. As specified in RFC 6426, the 'Service Identifier' field may be filled with an AGI (Attachment Group Identifier). The all-zeroes value indicates no Service Identifier has been configured.

OBJECT-TYPE

The value of tmnxOamVccvTrTgStaticCtlSaiiGlbl specifies the value to be copied into the 'Source Global ID' field of the 'Static Pseudowire' sub-TLV within the 'Target FEC Stack' TLV within the launched VCCV trace route request. Zero indicates no Source Global ID has been configured.

OBJECT-TYPE

The value of tmnxOamVccvTrTgStaticCtlSaiiNode specifies the value to be copied into the 'Source Node ID' field of the 'Static Pseudowire' sub-TLV within the 'Target FEC Stack' TLV within the launched VCCV trace route request. Zero indicates no Source Node ID has been configured.

OBJECT-TYPE

The value of tmnxOamVccvTrTgStaticCtlSaiiAcId specifies the value to be copied into the 'Source AC-ID' (Source Attachment Circuit Identifier) field of the 'Static Pseudowire' sub-TLV within the 'Target FEC Stack' TLV within the launched VCCV trace route request. Zero indicates no Source AC-ID has been configured.

OBJECT-TYPE

The value of tmnxOamVccvTrTgStaticCtlTaiiGlbl specifies the value to be copied into the 'Destination Global ID' field of the 'Static Pseudowire' sub-TLV within the 'Target FEC Stack' TLV within the launched VCCV trace route request. Zero indicates no Destination Global ID has been configured.

OBJECT-TYPE

The value of tmnxOamVccvTrTgStaticCtlTaiiNode specifies the value to be copied into the 'Destination Node ID' field of the 'Static Pseudowire' sub-TLV within the 'Target FEC Stack' TLV within the launched VCCV trace route request. Zero indicates no Destination Node ID has been configured.

OBJECT-TYPE

The value of tmnxOamVccvTrTgStaticCtlTaiiAcId specifies the value to be copied into the 'Destination AC-ID' (Destination Attachment Circuit Identifier) field of the 'Static Pseudowire' sub-TLV within the 'Target FEC Stack' TLV within the launched VCCV trace route request. Zero indicates no Destination AC-ID has been configured.

OBJECT-TYPE

tmnxOamIcmpTrLabelStackTable contains the information read from RFC 4950 MPLS Label Stack Objects in ICMPv4 or ICMPv6 replies, received in response to locally initiated 'icmpTraceRoute(5)' tests.

OBJECT-TYPE

tmnxOamIcmpTrLabelStackEntry contains the information present in one member of an RFC 4950 MPLS Label Stack Object, as received in one ICMPv4 or ICMPv6 reply (received in response to a locally initiated 'icmpTraceRoute(5)' test). One ICMPv4 or ICMPv6 reply can contain at most one MPLS Label Stack Object. The MPLS Label Stack Object is a structure in the reply, containing the MPLS encapsulation used for the test. One MPLS Label Stack Object contains one or more members. The first six indices specify the ICMPv4 or ICMPv6 reply. The seventh index specifies the member number within the MPLS Label Stack Object. SROS creates rows in this table when an ICMPv4 or ICMPv6 reply is received (in response to a locally initiated 'icmpTraceRoute(5)' test) containing an MPLS Label Stack Object. One row is created for each member in the MPLS Label Stack Object. SROS destroys rows in this table when the corresponding tmnxOamTrProbeHistoryTable row is destroyed.

OBJECT-TYPE

The value of tmnxOamIcmpTrLabelStackMemberNum specifies the member number within an RFC 4950 MPLS Label Stack Object. The first member within an MPLS Label Stack Object is member number 1. Subsequent members (if any) are numbered consecutively.

OBJECT-TYPE

The value of tmnxOamIcmpTrLabelStackLabel indicates the Label field within the specified RFC 4950 MPLS Label Stack Object member.

OBJECT-TYPE

The value of tmnxOamIcmpTrLabelStackExperimnt indicates the Experimental Use field within the specified RFC 4950 MPLS Label Stack Object member.

OBJECT-TYPE

The value of tmnxOamIcmpTrLabelStackBottom indicates the Bottom of Stack bit within the specified RFC 4950 MPLS Label Stack Object member.

OBJECT-TYPE

The value of tmnxOamIcmpTrLabelStackTtl indicates the Time To Live field within the specified RFC 4950 MPLS Label Stack Object member.

OBJECT-TYPE

tmnxOamBierTrCtlTable (along with tmnxOamTrCtlTable) contains the configuration information for BIER (Bit Index Explicit Replication) trace route tests.

OBJECT-TYPE

tmnxOamBierTrCtlEntry (along with tmnxOamTrCtlEntry) contains the configuration information for a BIER trace route test. A row is created when the corresponding tmnxOamTrCtlTestMode is set to 'bierTrace'. A row is destroyed when the corresponding tmnxOamTrCtlTable row is destroyed (using tmnxOamTrCtlRowStatus). The values in a particular row in this table cannot be changed when the corresponding tmnxOamTrCtlAdminStatus is 'enabled(1)'.

OBJECT-TYPE

The value of tmnxOamBierTrCtlSubDomain specifies the BIER sub-domain to be tested. Zero indicates the default sub-domain.

OBJECT-TYPE

The value of tmnxOamBierTrCtlBfrId specifies the identifier of the Bit-Forwarding Router (BFR) to be traced. The BFR-ID must be a member of the tested sub-domain (as configured using tmnxOamBierTrCtlSubDomain). Otherwise, the test will fail. Zero indicates no BFR-ID has been configured. There are two methods to configure the destination to be traced: 1. tmnxOamBierTrCtlBfrId. 2. tmnxOamBierTrCtlBfrPfxAddrType, tmnxOamBierTrCtlBfrPfxAddress. Exactly one of the methods must be used. Otherwise, the test will fail.

OBJECT-TYPE

The value of tmnxOamBierTrCtlBfrPfxAddrType specifies the address type of tmnxOamBierTrCtlBfrPfxAddress.

OBJECT-TYPE

The value of tmnxOamBierTrCtlBfrPfxAddress specifies a BFR prefix used as a destination address for a BIER trace test. There are two methods to configure the destination to be traced: 1. tmnxOamBierTrCtlBfrId. 2. tmnxOamBierTrCtlBfrPfxAddrType, tmnxOamBierTrCtlBfrPfxAddress. Exactly one of the methods must be used. Otherwise, the test will fail.

OBJECT-TYPE

tmnxOamBierTrProbeHistoryTable (along with tmnxOamTrProbeHistoryTable) contains the per-probe results for Bit Index Explicit Replication (BIER) trace tests.

OBJECT-TYPE

tmnxOamBierTrProbeHistoryEntry (along with tmnxOamTrProbeHistoryEntry) contains the results for one BIER trace probe. A row is created/destroyed when the corresponding tmnxOamTrProbeHistoryEntry is created/destroyed for a 'bierTrace' test. All the indices match the corresponding tmnxOamTrProbeHistoryEntry indices.

OBJECT-TYPE

The value of tmnxOamBierTrHistoryBfrId indicates the identifier of the Bit-Forwarding Router (BFR) targeted by the launched BIER Echo Request. Zero is returned if the BFR-ID cannot be determined. The BFR-Prefix (which is an alternative identifier of the target) can be read using tmnxOamTrProbeHistoryAddress.

OBJECT-TYPE

The value of tmnxOamBierTrHistoryReturnCode indicates the value copied from the Return Code field of the BIER Echo Reply PDU. Zero (i.e. 'No Return Code') is returned if a BIER Echo Reply PDU did not arrive (e.g. in the case of a timeout).

OBJECT-TYPE

The value of tmnxOamBierTrHistoryUpStrIfAddrT indicates the IP address type of the address read using tmnxOamBierTrHistoryUpStrIfAddr.

OBJECT-TYPE

The value of tmnxOamBierTrHistoryUpStrIfAddr indicates the IP address copied from the Upstream Address field of the Upstream Interface TLV of the BIER Echo Reply. When an IP address is not available, tmnxOamBierTrHistoryUpStrIfAddrT is 'unknown'. If the TLV's Upstream Address field contains an interface number (as tagged by the TLV's Address Type field), the interface number is available in tmnxOamBierTrHistoryUpStrIfNum.

OBJECT-TYPE

The value of tmnxOamBierTrHistoryUpStrIfNum indicates the interface number copied from the Upstream Address field of the Upstream Interface TLV of the BIER Echo Reply. When an interface number is not available, tmnxOamBierTrHistoryUpStrIfNum is zero. If the TLV's Upstream Address field contains an IP address (as tagged by the TLV's Address Type field), the IP address is available in tmnxOamBierTrHistoryUpStrIfAddr.

OBJECT-TYPE

The value of tmnxOamBierTrHistoryDnStrAddrTyp indicates the IP address type of the address read using tmnxOamBierTrHistoryDnStrAddr.

OBJECT-TYPE

The value of tmnxOamBierTrHistoryDnStrAddr indicates the IP address copied from the Downstream Address field of the Downstream Mapping TLV of the BIER Echo Reply. When an IP address is not available, tmnxOamBierTrHistoryDnStrAddrTyp is 'unknown'.

OBJECT-TYPE

The value of tmnxOamBierTrHistoryDnStrIfAddrT indicates the IP address type of the address read using tmnxOamBierTrHistoryDnStrIfAddr.

OBJECT-TYPE

The value of tmnxOamBierTrHistoryDnStrIfAddr indicates the IP address copied from the Downstream Interface Address field of the Downstream Mapping TLV of the BIER Echo Reply. When an IP address is not available, tmnxOamBierTrHistoryDnStrIfAddrT is 'unknown'. If the TLV's Downstream Interface Address field contains an interface number (as tagged by the TLV's Address Type field), the interface number is available in tmnxOamBierTrHistoryDnStrIfNum.

OBJECT-TYPE

The value of tmnxOamBierTrHistoryDnStrIfNum indicates the interface number copied from the Downstream Interface Address field of the Downstream Mapping TLV of the BIER Echo Reply. When an interface number is not available, tmnxOamBierTrHistoryDnStrIfNum is zero. If the TLV's Downstream Interface Address field contains an IP address (as tagged by the TLV's Address Type field), the IP address is available in tmnxOamBierTrHistoryDnStrIfAddr.

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-TYPE

tmnxOamSaaCtlTable contains configuration and status information for Service Assurance Agent (SAA) tests. A TIMETRA-OAM-TEST-MIB test has one of two retention types. 1. An SAA test has a tmnxOamSaaCtlTable row. All the configuration information for an SAA test is retained across an SROS CPM activity switch or an SROS CPM reset. 2. An OAM test does not have a tmnxOamSaaCtlTable row. All the configuration information for an OAM test is forgotten across an SROS CPM activity switch or an SROS CPM reset. SAA tests are supported for a subset of the test types, as described in the following DESCRIPTION clauses: tmnxOamPingCtlTestMode tmnxOamTrCtlTestMode. The results of an SAA test run (or an OAM test run) are stored in the ping or trace route results tables (e.g. tmnxOamPingResultsTable, tmnxOamPingHistoryTable, tmnxOamTrResultsTable, tmnxOamTrHopsTable, tmnxOamTrProbeHistoryTable).

OBJECT-TYPE

tmnxOamSaaCtlEntry contains the configuration and status information for one SAA test. Rows are created and destroyed using tmnxOamSaaCtlRowStatus.

OBJECT-TYPE

The value of tmnxOamSaaCtlOwnerIndex specifies the name of the owner of the test.

OBJECT-TYPE

The value of tmnxOamSaaCtlTestIndex specifies the test name of the test. The test is identified by the owner name and the test name. One owner typically owns several tests. This indexing method ensures tests created by several owners have unique indices.

OBJECT-TYPE

The value of tmnxOamSaaCtlRowStatus specifies the row status of the SAA test. When creating an SAA test 1. The tmnxOamSaaCtlTable row must be created first. 2. The tmnxOamPingCtlTable or tmnxOamTrCtlTable row must be created second. Destroying a tmnxOamSaaCtlTable row destroys the corresponding tmnxOamPingCtlTable or tmnxOamTrCtlTable row (if any). An attempt to destroy a tmnxOamSaaCtlTable row will fail if tmnxOamSaaCtlAdminStatus is 'inService(2)'.

OBJECT-TYPE

The storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write access to any columnar objects in the row. This object was marked obsolete in SROS Release 14.0 R1. There is no replacement object.

OBJECT-TYPE

The value of tmnxOamSaaCtlLastChanged indicates the time the value of a settable object in this row was last changed.

OBJECT-TYPE

The value of tmnxOamSaaCtlAdminStatus specifies the administrative state of the SAA test. tmnxOamSaaCtlAdminStatus = 'inService(2)' is a prerequisite for starting an SAA test run. Once that prerequisite is met, the test run can be started by setting the corresponding tmnxOamPingCtlAdminStatus or tmnxOamTrCtlAdminStatus to 'enabled(1)'. When the tmnxOamSaaCtlAdminStatus is 'inService(2)', an attempt to modify any other configurable run-time property of the test (e.g. tmnxOamPingCtlProbeCount, tmnxOamTrCtlFcName) will fail.

OBJECT-TYPE

The value of tmnxOamSaaCtlDescr specifies the description of the SAA test.

OBJECT-TYPE

The value of tmnxOamSaaCtlTestMode indicates the type of SAA test to be performed. When the value of this object is 'notConfigured(0)', no associated row exists in either tmnxOamPingCtlTable or tmnxOamTrCtlTable. When the value of this object is 'ping(1)', an associated row exists in the tmnxOamPingCtlTable. When the value of this object is 'traceroute(2)', an associated row exists in the tmnxOamTrCtlTable.

OBJECT-TYPE

The value of tmnxOamSaaCtlRuns indicates the number of times this SAA test has started.

OBJECT-TYPE

The value of tmnxOamSaaCtlFailures indicates the number of times this SAA test has failed.

OBJECT-TYPE

The value of tmnxOamSaaCtlLastRunResult indicates the completion status the last time this test was executed. If this SAA test is currently in progress, this object indicates the result of the previous test run, if any.

OBJECT-TYPE

The value of tmnxOamSaaCtlAcctPolicyId specifies the accounting policy used to record the information obtained from the results tables. A value of zero specifies no accounting policy. A non-zero accounting policy must be configured with the SAA record generation option. For example, an attempt to set this object to 99 will be rejected if TIMETRA-LOG-MIB::tmnxLogApRecord.99 is not 'saa(32)'.

OBJECT-TYPE

The value of tmnxOamSaaCtlSuppressAccounting specifies whether or not the accounting file update is suppressed. The value 'true(1)' is applicable only when an accounting policy has been specified using tmnxOamSaaCtlAcctPolicyId. Upon completion of a test run, this object is reset to its default value.

OBJECT-TYPE

The value of tmnxOamSaaCtlContinuous specifies whether or not the SAA test is to be executed indefinitely. Setting tmnxOamSaaCtlContinuous to 'true(1)' is accepted for the following ping test types: 'cpePing (12)', 'dnsPing (16)', 'ethCfmLoopback (19)', 'ethCfmTwoWayDelay (20)', 'ethCfmTwoWaySlm (22)', 'icmpPing (15)', 'lspPing ( 8)', 'macPing ( 5)', 'sdpPing ( 1)', 'vccvPing (14)', 'vprnPing ( 9)'. Setting tmnxOamSaaCtlContinuous to 'true(1)' is accepted for the following trace test types: 'ethCfmLinkTrace (9)'.

OBJECT-TYPE

The value of tmnxOamSaaCtlKeepProbeHistoryAdm specifies whether or not per-probe history table rows will be created for this test. A test without per-probe history table rows consumes less CPM RAM. tmnxOamSaaCtlKeepProbeHistoryOpr is a read-only operational value derived from tmnxOamSaaCtlKeepProbeHistoryAdm. The bulk of the tmnxOamSaaCtlKeepProbeHistoryAdm semantics are described in the tmnxOamSaaCtlKeepProbeHistoryOpr DESCRIPTION clause. An attempt to set tmnxOamSaaCtlKeepProbeHistoryAdm to 'drop(2)' when tmnxOamSaaCtlTestMode is not 'ping(1)' returns an 'inconsistentValue' error to the manager.

OBJECT-TYPE

The value of tmnxOamSaaCtlKeepProbeHistoryOpr indicates whether or not per-probe history table rows will be created for this test. A test without per-probe history table rows consumes less CPM RAM. The value of tmnxOamSaaCtlKeepProbeHistoryOpr is derived from the value of`tmnxOamSaaCtlKeepProbeHistoryAdm, as shown in the following table. tmnxOamSaaCtlKeepProbeHistoryAdm tmnxOamSaaCtlKeepProbeHistoryOpr -------------------------------- -------------------------------------- 'keep(1)' 'keep(1)' 'drop(2)' 'drop(2)' 'auto(3)' 'keep(1)' or 'drop(2)', chosen by SROS The history table rows created for the combinations of tmnxOamSaaCtlKeepProbeHistoryOpr and tmnxOamSaaCtlTestMode values are shown in the following table. Configuration Options History Table Rows Created -------------------------- -------------------------- 'keep(1)', 'ping(1)' tmnxOamPingHistoryTable or tmnxOamMacPingHistoryTable 'keep(1)', 'traceroute(2)' tmnxOamTrProbeHistoryTable 'drop(2)', 'ping(1)' none 'drop(2)', 'traceroute(2)' unsupported combination. If tmnxOamSaaCtlTestMode is 'notConfigured(0)', the value of tmnxOamSaaCtlKeepProbeHistoryOpr is insignificant, since a test without a test mode cannot be started. When a Get is performed on tmnxOamSaaCtlKeepProbeHistoryOpr in this case, 'keep(1)' is returned. If tmnxOamSaaCtlKeepProbeHistoryAdm is 'auto(3)': 1. tmnxOamSaaCtlKeepProbeHistoryOpr is 'drop(2)' if a) the test's probe count is greater than 100, OR b) the test's interval is less than one second, OR c) tmnxOamSaaCtlTestMode is 'ping(1)' AND the test is continuous (i.e. tmnxOamSaaCtlContinuous is 'true') AND an accounting policy is specified (i.e. tmnxOamSaaCtlAcctPolicyId is non- zero). 2. Otherwise, tmnxOamSaaCtlKeepProbeHistoryOpr is 'keep(1)'.

OBJECT-TYPE

tmnxOamSaaThresholdTable contains notification threshold information for SAA tests.

OBJECT-TYPE

Defines an entry in the tmnxOamSaaThresholdTable. The first index element, tmnxOamSaaCtlOwnerIndex, is of type SnmpAdminString, a textual convention that allows for use of the SNMPv3 View-Based Access Control Model (RFC 2575 [11], VACM) and allows a management application to identify its entries. The second index, tmnxOamSaaCtlTestIndex, enables the same management application to have multiple outstanding requests. The third index element identifies the type of statistic to be monitored for threshold crossing. The fourth index element identifies which direction, rising or falling, to monitor.

OBJECT-TYPE

The value of tmnxOamSaaTType specifies the type of monitored statistic used to determine if a tmnxOamSaaThreshold notification is generated at the completion of an SAA test run.

OBJECT-TYPE

The value of tmnxOamSaaTDirection specifies whether to monitor this threshold for crossing in the rising or falling direction.

OBJECT-TYPE

The value of tmnxOamSaaTRowStatus controls creation and deletion of row entries in the tmnxOamSaaThresholdTable. When a row in this table is created, tmnxOamSaaTThreshold must also be set or the row creation will fail with an inconsistentValue error.

OBJECT-TYPE

The value of tmnxOamSaaTLastChanged indicates the last time the value of tmnxOamSaaTThreshold was modified.

OBJECT-TYPE

The value of tmnxOamSaaTThreshold specifies the threshold value to monitor to determine when to generate a tmnxOamSaaThreshold notification. A threshold value must be set when the row entry is created.

OBJECT-TYPE

The value of tmnxOamSaaTValue indicates the value of the statistic that last caused a tmnxOamSaaThreshold notification to be generated.

OBJECT-TYPE

The value of tmnxOamSaaTLastSent indicates the last time a tmnxOamSaaThreshold notification was generated as a result of crossing the threshold specified by the value of tmnxOamSaaTThreshold.

OBJECT-TYPE

The value of tmnxOamSaaTTestMode indicates the type of Service Assurance Agent, SAA, test for which a tmnxOamSaaThreshold notification was generated as a result of crossing the threshold specified by the value of tmnxOamSaaTThreshold. When the value of this object is 'notConfigured', no associated entry exists in either the tmnxOamPingCtlTable or tmnxOamTrCtlTable. When the value of this object is 'ping', an associated test entry is configured in the tmnxOamPingCtlTable. When the value of this object is 'traceroute', an associated test entry is configured in the tmnxOamTrCtlTable.

OBJECT-TYPE

The value of tmnxOamSaaTTestRunIndex indicates the test run index of the Service Assurance Agent, SAA, test for which the last tmnxOamSaaThreshold notification was generated as a result of crossing the threshold specified by the value of tmnxOamSaaTThreshold. When the value of tmnxOamSaaTTestMode is 'ping', the value of this object is the value of the tmnxOamPingResultsTestRunIndex that identifies entries for the ping test results of the test run that generated the last tmnxOamSaaThreshold notification. When the value of tmnxOamSaaTTestMode is 'traceroute', the value of this object is the value of the tmnxOamTrResultsTestRunIndex that identifies entries for the traceroute test results of the test run that generated the last tmnxOamSaaThreshold notification. When the value of tmnxOamSaaTTestMode is 'notConfigured', the value of this object is zero.

OBJECT-IDENTITY

OBJECT-TYPE

Defines the Nokia 7x50 SR OAM VPRN Ping Control Table for providing, via SNMP, the capability of performing Nokia 7x50 SR OAM 'gtpPing' test operations. The results of these tests are stored in the tmnxOamPingResultsTable and the tmnxOamPingHistoryTable.

OBJECT-TYPE

Defines an entry in the tmnxOamMobGtpPingCtlTable. The first index element, tmnxOamPingCtlOwnerIndex, is of type SnmpAdminString, a textual convention that allows for use of the SNMPv3 View-Based Access Control Model (RFC 2575 [11], VACM) and allows a management application to identify its entries. The second index, tmnxOamPingCtlTestIndex, enables the same management application to have multiple outstanding requests.

OBJECT-TYPE

The value of tmnxOamMobGtpPingRefPointType specifies the reference point type. This object is required.

OBJECT-TYPE

The value of tmnxOamMobGtpPingVRtrId specifies the virtual router. duplicate of tmnxOamPingCtlVRtrID This object was obsoleted in 16R01.

OBJECT-TYPE

The value of tmnxOamMobGtpPingPort specifies the udp port number of the destination. This object is required.

OBJECT-TYPE

The value of tmnxOamMobGtpPingGateway specifies the mobile gateway id. This object is required.

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-TYPE

The value of tmnxOamMplsPduTimeStampFormat specifies, on a system wide basis: a) the format of the time stamp to be written into an RFC 4379 MPLS Echo Request PDU, when initiating a ping or trace route test, and b) the format of the time stamp to be written into an RFC 4379 MPLS Echo Reply PDU, when replying to an incoming MPLS Echo Request PDU, and c) the format to use when decoding the time stamps in an incoming MPLS Echo Request or MPLS Echo Reply PDU. 'rfc4379(0)' specifies the RFC 4379 time stamp format. The time stamp's 'seconds' field holds the integral number of seconds since 1-Jan-1900 00:00:00 UTC. The time stamp's 'microseconds' field contains a microseconds value in the range 0..999999. This setting is used to interoperate with network elements which are fully compliant with RFC 4379 (e.g. an SROS system with the same setting, or any other RFC 4379 compliant router). 'unix(1)' specifies the Unix time stamp format. The time stamp's 'seconds' field holds a 'Unix time', i.e. the integral number of seconds since 1-Jan-1970 00:00:00 UTC. The time stamp's 'microseconds' field contains a microseconds value in the range 0..999999. This setting is used to interoperate with network elements which send and expect a 1970-based timestamp in MPLS Echo Request/Reply PDUs (e.g. an SROS system with the same setting, or an SROS system running software earlier than R8.0 R4). Prior to SROS Release 8.0 R4, this object was not supported. The Unix time stamp format was always used. This object is applicable for the ldpTreeTrace, lspPing, lspTraceRoute, p2mpLspPing, p2mpLspTrace, vccvPing, and vccvTraceRoute test modes only.

OBJECT-IDENTITY

OBJECT-TYPE

The value of tmnxOamSysPerfOprLimitTx indicates this node's upper bound on the total echo request packet transmission rate. Echo reply packets are not affected by this limit. The upper bound applies to echo request packets sent by the following test types: 1. Background ICMP Bridged Residential Gateway ping test. 2. Filter redirect policy ping test. 3. SDP keep-alive. 4. Static route CPE check. 5. VRRP policy host unreachable ping test. 6. Any OAM or SAA test configured using TIMETRA-OAM-TEST-MIB. 7. Any test configured using TIMETRA-OAM-PM-MIB.

OBJECT-TYPE

The value of tmnxOamSysPerfCfgLimitTx indicates this node's upper bound on the total configured echo request packet transmission rate for a set of test types. The upper bound is enforced to avoid echo request packet transmit overload, i.e. to ensure each enabled test can transmit echo request packets at the test's configured rate. Echo reply packets are not affected by this limit. The upper bound applies to echo request packets sent by the following 'always on' test types: 1. Background ICMP Bridged Residential Gateway ping test. 2. Filter redirect policy ping test. 3. SDP keep-alive. 4. Static route CPE check. 5. VRRP policy host unreachable ping test. 6. SAA continuous test (see tmnxOamSaaCtlContinuous). 7. OAM-PM proactive test (see TIMETRA-OAM-PM-MIB::tmnxOamPmCfgSessType). For example, suppose: a) tmnxOamSysPerfCfgLimitTx has the value 4000 echo request packets per second, and b) several SDP keep-alive sessions are enabled, totalling 1000 echo request packets per second, and c) several SAA continuous tests are enabled, totalling 3000 echo request packets per second. Then, an attempt to enable an additional SAA continuous test would be rejected with a 'resourceUnavailable(13)' error.

OBJECT-TYPE

The value of tmnxOamSysPerfCfgTotalTx indicates this node's current total configured echo request packet transmission rate, for the set of tests listed in the tmnxOamSysPerfCfgLimitTx DESCRIPTION clause. For example, suppose: a) several SDP keep-alive sessions are enabled, totalling 1000 echo request packets per second, and b) several SAA continuous tests are enabled, totalling 2000 echo request packets per second, and c) no other relevant tests are enabled. Then, tmnxOamSysPerfCfgTotalTx will have the value 3000. The value of tmnxOamSysPerfCfgTotalTx will not exceed the value of tmnxOamSysPerfCfgLimitTx.

OBJECT-TYPE

The value of tmnxOamSysPerfLastClearedTime indicates the sysUpTime when the following statistics were cleared: tmnxOamSysPerfLocalTestTx, tmnxOamSysPerfRemoteTestRx, and tmnxOamSysPerfReqTypeTable. If the statistics have not been cleared since the last CPM restart, zero is returned. A packet count which is time stamped by this object can be converted to an average packets per second value using, for example, pps = tmnxOamSysPerfLocalTestTx / [(sysUpTime - tmnxOamSysPerfLastClearedTime)/100].

OBJECT-TYPE

The value of tmnxOamSysPerfLocalTestTx indicates this node's total number of echo request packets transmitted by locally initiated tests (since the last clear). The test types are listed in the tmnxOamSysPerfOprLimitTx DESCRIPTION clause.

OBJECT-TYPE

The value of tmnxOamSysPerfRemoteTestRx indicates this node's total number of echo request packets received from remotely initiated tests (since the last clear).

OBJECT-TYPE

tmnxOamSysPerfReqTypeTable has a row for each relevant OAM echo request packet type. Each row contains packet counters.

OBJECT-TYPE

Rows in tmnxOamSysPerfReqTypeTable are system-generated at CPM restart. Rows cannot be created or destroyed using SNMP.

OBJECT-TYPE

The value of tmnxOamSysPerfReqTypeName specifies the name of an echo request packet type (e.g. 'ICMP'). The name is the index for the row.

OBJECT-TYPE

The value of tmnxOamSysPerfReqTypeLocalTestTx indicates the number of echo request packets transmitted by locally initiated tests (since the last clear) for the echo request packet type specified by tmnxOamSysPerfReqTypeName.

OBJECT-TYPE

The value of tmnxOamSysPerfReqTypeRemoteTstRx indicates the number of echo request packets received from remotely initiated tests (since the last clear) for the echo request packet type specified by tmnxOamSysPerfReqTypeName.

OBJECT-TYPE

The value of tmnxOamSysSessionLimit indicates the maximum number of sessions in the OAM general session pool. OAM general session pool sessions are allocated and freed as described in the tmnxOamSysSessionCount DESCRIPTION clause.

OBJECT-TYPE

The value of tmnxOamSysSessionCount indicates the number of currently allocated sessions in the OAM general session pool. A test with one of the following test types allocates a session from the OAM general session pool: 1. Filter redirect policy ping test. 2. SDP keep-alive. 3. Static route CPE check. 4. VRRP policy host unreachable ping test. 5. Any OAM or SAA test configured using TIMETRA-OAM-TEST-MIB. 6. Any test configured using TIMETRA-OAM-PM-MIB. A session is allocated from the OAM general session pool when a test is configured (in the case of some test types) or activated (in the remaining cases). The session is freed when the test is deactivated or deleted. tmnxOamSysSessionCount will not exceed tmnxOamSysSessionLimit. Configuration or activation of a test (with a test type listed above) will fail when tmnxOamSysSessionCount equals tmnxOamSysSessionLimit.

OBJECT-TYPE

The value of tmnxOamSysBgIcmpBrgSessionLimit indicates the maximum number of background ICMP Bridged Residential Gateway (BRG) OAM test sessions available on this node. Sessions are allocated and freed as described in the tmnxOamSysBgIcmpBrgSessionCount DESCRIPTION clause.

OBJECT-TYPE

The value of tmnxOamSysBgIcmpBrgSessionCount indicates the number of background ICMP Bridged Residential Gateway (BRG) OAM test sessions currently allocated on this node. One session is allocated when BRG functionality is administratively enabled on a group interface (using TIMETRA-SUBSCRIBER-MGMT-MIB:: tmnxSubBrgIfAdminState). The session is freed when the BRG functionality is administratively disabled. tmnxOamSysBgIcmpBrgSessionCount will not exceed tmnxOamSysBgIcmpBrgSessionLimit. Creating a background ICMP BRG OAM test session will fail when tmnxOamSysBgIcmpBrgSessionCount equals tmnxOamSysBgIcmpBrgSessionLimit.

OBJECT-TYPE

The value of tmnxOamSysLspSelfPingSessLimit indicates the maximum number of LSP Self Ping sessions available on this node. Sessions are allocated as described in the tmnxOamSysLspSelfPingSessCount DESCRIPTION clause.

OBJECT-TYPE

The value of tmnxOamSysLspSelfPingSessCount indicates the number of LSP Self Ping sessions currently allocated on this node. One session is allocated as required after LSP Self Ping is administratively enabled on an LSP (using TIMETRA-MPLS-MIB::vRtrMplsLspExtSelfPing). tmnxOamSysLspSelfPingSessCount will not exceed tmnxOamSysLspSelfPingSessLimit. Creating an LSP Self Ping session will fail when tmnxOamSysLspSelfPingSessCount equals tmnxOamSysLspSelfPingSessLimit.

OBJECT-TYPE

The value of tmnxOamSysPerfCfgLspSelfTxLimit indicates this node's upper bound on the total configured echo request packet transmission rate for LSP Self Pings. The upper bound is enforced to avoid echo request packet transmit overload, i.e. to ensure each enabled test can transmit echo request packets at the test's configured rate. Echo reply packets are not affected by this limit.

OBJECT-TYPE

The value of tmnxOamSysPerfCfgLspSelfTxTotal indicates this node's current total configured echo request packet transmission rate for LSP Self Pings. An LSP Self Ping is started as required after LSP Self Ping is administratively enabled on an LSP (using TIMETRA-MPLS-MIB::vRtrMplsLspExtSelfPing). The value of tmnxOamSysPerfCfgLspSelfTxTotal will not exceed the value of tmnxOamSysPerfCfgLspSelfTxLimit.

OBJECT-TYPE

The value of tmnxOamMplsEchoDownstreamMapTlv specifies the system value for the type of downstream map TLV to be inserted when launching MPLS echo requests. The value of tmnxOamMplsEchoDownstreamMapTlv is used on three occasions: 1. When a background LDP tree trace test is started (using tmnxOamLTtraceAutoAdminState), the value of tmnxOamMplsEchoDownstreamMapTlv specifies the type of downstream map TLV used during the test. 2. When a test of type 'lspTraceRoute' is created, with no value specified for the test's tmnxOamLspTrCtlDownstreamMapTlv object, tmnxOamLspTrCtlDownstreamMapTlv is set to the value of tmnxOamMplsEchoDownstreamMapTlv. 3. When a test of type 'ldpTreeTrace' is created, with no value specified for the test's tmnxOamLTtraceCtlDownstreamMpTlv object, tmnxOamLTtraceCtlDownstreamMpTlv is set to the value of tmnxOamMplsEchoDownstreamMapTlv. Example usage, for the second and third cases: suppose every node in this node's network supports the MPLS Echo Request/Reply DDMAP TLV, and the network operator wishes to use the enhanced functionality offered by the DDMAP TLV. Then, setting tmnxOamMplsEchoDownstreamMapTlv to 'ddmap(2)' simplifies configuration. The simplification: the tmnxOamLspTrCtlDownstreamMapTlv and tmnxOamLTtraceCtlDownstreamMpTlv objects need not be set when creating tests.

OBJECT-IDENTITY

OBJECT-TYPE

tmnxOamDiagCtlTable contains configuration information for diagnostic tests. tmnxOamPingCtlTable and tmnxOamTrCtlTable fill the same role for ping tests and trace route tests, respectively.

OBJECT-TYPE

tmnxOamDiagCtlEntry contains configuration information for one diagnostic test. Rows are created/destroyed using tmnxOamDiagCtlRowStatus.

OBJECT-TYPE

The value of tmnxOamDiagCtlOwnerIndex specifies the owner name of the test.

OBJECT-TYPE

The value of tmnxOamDiagCtlTestIndex specifies the test name of the test. The test is identified by the owner name and the test name. One owner typically owns several tests. This indexing method ensures tests created by several owners have unique indices.

OBJECT-TYPE

The value of tmnxOamDiagCtlRowStatus specifies the row status of the specified test.

OBJECT-TYPE

The value of tmnxOamDiagCtlLastChanged indicates the most recent time the value of a writable object in this row was modified.

OBJECT-TYPE

The value of tmnxOamDiagCtlTestMode specifies the type of OAM diagnostic test defined by this row. Code Points ------------------------------------------------------------------ none - the test type is unspecified findEgressDiag - find the egress port, etc, for a user-configured packet The support for Service Assurance Agent (SAA) tests (i.e. tests with tmnxOamSaaCtlTable rows) and OAM tests (i.e. tests without tmnxOamSaaCtlTable rows) varies with the test type, as shown in the following table. tmnxOamDiagCtlTestMode SAA Supported OAM Supported ---------------------- ------------- ------------- 'findEgressDiag' No Yes

OBJECT-TYPE