Fw: DISMAN REMOPS MIB implementation/deployment report

Hi -

I am please to be able to forward Juniper's implementation
report for RFC 2925, courtesy of Daniel Chuang.

Randy

> From: "Daniel Chuang" <[email protected]>
> To: "Randy Presuhn" <[email protected]>
> Cc: "Steve Moulton" <[email protected]>; <[email protected]>
> Sent: Thursday, July 15, 2004 5:18 PM
> Subject: Re: DISMAN REMOPS MIB implementation/deployment report
>

> Go ahead. It is OK to make it public. Please cc  me since
> I am not in the mailing list.
>
> thanks,
> Daniel
> Randy Presuhn wrote:
>
> >Hi Daniel -
> >
> >Thanks!  May I forward the report to the disman WG mailing
> >list, or would you prefer this report to remain anonymous?
> >
> >Randy
> >
> >----- Original Message ----- 
> >
> >>From: "Daniel Chuang" <[email protected]>
> >>To: <[email protected]>
> >>Cc: "Daniel Chuang" <[email protected]>; "Steve Moulton" <[email protected]>; <[email protected]>
> >>Sent: Thursday, July 15, 2004 4:14 PM
> >>Subject: Re: DISMAN REMOPS MIB implementation/deployment report
> >>
> >
> >>Hi, Randy,
> >>
> >>    I attach the implementation report for rfc 2925 in Juniper.
> >>Hopefully it is not too late.
> >>
> >>thanks,
> >>Daniel
> >>
> >...
> >
> >>    Juniper Implementation report for RFC 2925
> >>
> >>=================================================
> >>
> >>Implementation Survey for RFC 2925,
> >>Definitions of Managed Objects for Remote Ping,
> >>Traceroute, and Lookup Operations
> >>
> >> Module: DISMAN-PING-MIB
> >> Implementation Source: Internal Implementation
> >> Management Application / Agent:
> >>     It is based on Wind River WindManage v9.3
> >>
> >>
> >>GROUPs:
> >>pingGroup (y/n): y
> >>pingNotificationsGroup (y/n): y
> >>pingTimeStampGroup (y/n): y
> >>
> >>OBJECTs:
> >>pingMaxConcurrentRequests (rw/ro): rw
> >>pingCtlStorageType (rw/ro): rw (volatile only)
> >>pingCtlType (rw/ro): rw (pingIcmpEcho, pingUdpEcho, pingTcpConnectionAttempt)
> >>pingCtlByPassRouteTable (rw/ro): rw
> >>pingCtlSourceAddressType (rw/ro): rw
> >>    unknown (y/n): y
> >>    ipv4 (y/n): y
> >>    ipv6 (y/n): n
> >>
> >>pingCtlSourceAddress (rw/ro): rw
> >>pingCtlIfIndex (rw/ro): rw
> >>pingCtlDSField (rw/ro): rw
> >>pingResultsIpTargetAddressType:
> >>    unknown (y/n): y
> >>    ipv4 (y/n): y
> >>    ipv6: n
> >>pingResultsIpTargetAddress:
> >>    0 (y/n): y
> >>    4 (y/n): y
> >>    16 (y/n): n
> >>
> >>
> >>Module: DISMAN-TRACEROUTE-MIB
> >>Implementation Source: Internal Implementation.
> >>Management Application / Agent:
> >>     It is based on Wind River WindManage v9.3
> >>
> >>GROUPs:
> >>traceRouteGroup (y/n): y
> >>traceRouteTimeStampGroup (y/n): y
> >>traceRouteNotificationsGroup (y/n): y
> >>traceRouteHopsTableGroup (y/n): y
> >>
> >>OBJECTs:
> >>traceRouteMaxConcurrentRequests (rw/ro): rw
> >>traceRouteCtlByPassRouteTable (rw/ro): rw
> >>traceRouteCtlSourceAddressType rw/ro): rw
> >>traceRouteCtlSourceAddress (rw/ro): rw
> >>traceRouteCtlIfIndex (rw/ro): rw
> >>traceRouteCtlMiscOptions (rw/ro): rw
> >>traceRouteCtlStorageType (rw/ro): rw (volatile only)
> >>traceRouteCtlDSField (rw/ro): rw
> >>traceRouteCtlType (rw/ro): rw
> >>traceRouteResultsIpTgtAddrType
> >>    unknown (y/n): y
> >>    ipv4 (y/n): y
> >>    ipv6 (y/n): n
> >>traceRouteResultsIpTgtAddr
> >>    0 (y/n): y
> >>    4 (y/n): y
> >>    16 (y/n): n
> >>traceRouteProbeHistoryHAddrType
> >>    unknown (y/n): y
> >>    ipv4 (y/n): y
> >>    ipv6 (y/n): n
> >>traceRouteProbeHistoryHAddr
> >>    0 (y/n): y
> >>    4 (y/n): y
> >>    16 (y/n): n
> >>traceRouteHopsIpTgtAddressType
> >>    unknown (y/n): y
> >>    ipv4 (y/n): y
> >>    ipv6 (y/n): n
> >>traceRouteHopsIpTgtAddress
> >>    0 (y/n): y
> >>    4 (y/n): y
> >>    16 (y/n): n
> >>
> >>
> >>Module: DISMAN-NSLOOKUP-MIB
> >>Implementation Source: Not supported.
> >>Management Application / Agent:
> >>
> >>GROUPs
> >>lookupGroup (y/n): n
> >>
> >>OBJECTs:
> >>lookupMaxConcurrentRequests (rw/ro): NA
> >>lookupPurgeTime (rw/ro): NA
> >>
> >>
> >>Deployment / Operational Experience:
> >>
> >>Comments:
> >>
> >>