| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2167.1 | | ABBYRD::RMULAC.DVO.DEC.COM::S_WATTUM | Scott Wattum - FTAM/VT/OSAK Engineering | Wed Apr 23 1997 02:50 | 3 |
| I'm pretty certain there's an oping to go along with Ping The Duck.
But I could be wrong.
'ere's 'oping.
|
| 2167.2 | DU works, AIX does not | CHEFS::DAVIDSONS | | Thu Apr 24 1997 19:55 | 15 |
| Thanks, I tried the following:
oping %x470027814e4c44014d41410984466746
does not work
(destination is an AIX system, I can establish connection via
application using XTI, 'ncl show osi transport port' reveals
that the NSAP selector is 46)
oping %x470027814e4c44014459594f4f4357504f165121
works OK
(destination is a DU system)
Any ideas?
|
| 2167.3 | | ABBYRD::RMULAC.DVO.DEC.COM::S_WATTUM | Scott Wattum - FTAM/VT/OSAK Engineering | Fri Apr 25 1997 12:16 | 4 |
| If you can establish a connection with your application, I would have to guess
that the AIX doesn't support oping, or that it needs to be configured to support
it.
|
| 2167.4 | Thanks. | CHEFS::DAVIDSONS | | Fri Apr 25 1997 19:24 | 4 |
| You're right, a DNU system configured with AIX address responds
to oping.
Is there a standard which covers support of oping?
|
| 2167.5 | | ABBYRD::RMULAC.DVO.DEC.COM::S_WATTUM | Scott Wattum - FTAM/VT/OSAK Engineering | Mon Apr 28 1997 12:01 | 7 |
| Probably not. There's nothing that says a vendor must implement a particular
application except market demand. Even if a vendor implements an application,
you can frequently choose between various options that you need - FTAM for
example has lots of options, not all of which must be implemented. To help with
interoperability, organizations like NIST have stepped in and created profiles
to which you can claim compliance too, etc., but even then, whether or not a
vendor feels the need to make such claims depends on market demand.
|
| 2167.6 | Thanks | CHEFS::DAVIDSONS | | Tue Apr 29 1997 21:17 | 1 |
|
|