OS2 World.Com Forum

Subject  :  Disk for RPL user guide
Author  :  Sam
Date  :  23 Apr, 2007 on 19:22
Does any one still get the disk "IBM Remote Program Load: 3.5-inch disk and RPL User's Guide" (for IBM Token Ring Network Adapter /A)", product ID 83x8881 ?

If yes, would appreciate to email me that. Just want to see whether it can help to resolve one recently encountered problem. Would like search whether it can explain the code encountered : OP0059.

Thanks in advance


Subject  :  Re:Disk for RPL user guide
Author  :  mobybrick
Date  :  24 Apr, 2007 on 01:00
Hi,

Threw mine out a few months ago I'm afraid - hadn't used it in years. However, there are a few likely candidates:

* Ring in beacon state
* Only device on ring / no NAUN
* Ring speed selection in reference disk/setup is different to the sensed ring speed
* Ring speed selection in reference disk/setup is set to automatic, but there is no other device currently on ring, so speed cannot be set
* A response received from an RPL server, but it was not valid
* No response to RPL requests was received within a timeout period.

From memory I believe OP58 and OP59 were related, and are likely to be beacon/lost token events. My second guess would be ring speed or ring speed detection.

Regards,
Moby.


Subject  :  Re:Disk for RPL user guide
Author  :  Sam
Date  :  24 Apr, 2007 on 02:44
Moby,

Thanks first for the info. 5 of 6 is possible.

1. Ring in beacon state
3. Ring speed selection in reference disk/setup is different to the sensed ring speed
4. Ring speed selection in reference disk/setup is set to automatic, but there is no other device currently on ring, so speed cannot be set
5. A response received from an RPL server, but it was not valid
6. No response to RPL requests was received within a timeout period.

My network is quite simple. Software is Warp server (RPL svr) with PCs (OS/2 RPL client). Network is 8230 hub with LAM and two Routers. Op0059 is displayed in RPL initialisation screen whenever one of the routers (with token ring interface) is connected to 8230. Situation resume normal whenever it is disconnected. No RPL server reboot is required. However, verified that token ring card in router is OK.

Is there any way to further isolate the problem casue (from server or 8230 display) ?

Thanks again.


Subject  :  Re:Disk for RPL user guide
Author  :  mobybrick
Date  :  24 Apr, 2007 on 03:28
Hi,

Does network connectivity in general stop when the router is attached? Or does other traffic continue to flow?

If traffic otherwise continues to flow, it could be, for some reason, that the router is 'lifting' 802.2 packets off the LAN, although unlikely.

There is a way to enable Remoteboot tracing to a debug/trace file. Under the [remoteboot] section of IBMLAN.INI, try adding something like auditingfile=xxxxxxx or tracefile=xxxxxxx and then restart the RPL service. The auditing file should be created (n.b. it is independant of the 'real' auditing feature).

Regards,
Moby


Subject  :  Re:Disk for RPL user guide
Author  :  Sam
Date  :  24 Apr, 2007 on 19:33
Moby,

Based on the continual on of indicator lamps in 8230 hub, I will consider there is traffic flow at that time.

Just not sure whether the same conclusion can be made on the problematic router. Indicator lamp is also on when it is plugged into 8230.

Will see whether remote boot trace option can help.

Besides RPL trace / debug, is there any system log in server I can used to check for the problem cause or locate whether beaconing exist ? The server has FFST installed but trace is off.

Thanks again

Sam


Subject  :  Re:Disk for RPL user guide
Author  :  Sam
Date  :  25 Apr, 2007 on 17:54

mobybrick (24 Apr, 2007 03:2:
There is a way to enable Remoteboot tracing to a debug/trace file. Under the [remoteboot] section of IBMLAN.INI, try adding something like auditingfile=xxxxxxx or tracefile=xxxxxxx and then restart the RPL service. The auditing file should be created (n.b. it is independant of the 'real' auditing feature).

Regards,
Moby


It should be auditingfile=xxxxxx. Can the trace level be customized ?


Subject  :  Re:Disk for RPL user guide
Author  :  mobybrick
Date  :  25 Apr, 2007 on 23:42
I don't think the trace level can be changed... it is an totally undocumented feature AFAIK.

Questions:

1. Does the RPL processes successfully complete and remoteboot occur when the router is not attached?

2. What adapter(s) is in your server, and what version of driver is being used?

3. What adapter card is in the workstation, and it is using an on-board RIPL ROM, or boot disk emulation?

It is important that we need to establish if your ring is continuing to function when the router is attached.

There easiest ways of doing this are:

1. Ping another workstation on the ring (only if TCP/IP is bound, which it probably isn't by the sound of it!) - if ICMP responses stop when the router is attached, then the ring is failing.

2. Do a NET USE on the server to *another* server/workstation on the ring, and try to do a DIR of that resource when the router is attached. If traffic has stopped flowing, the DIR will stop.

If no other server/workstation is available for this test, then we can test by connecting to ourself. This relies on the loopback feature not being available on the adapter in the server - few token ring adapters had this working anyway.

So,
3. Do a NET USE to a share on the same server, and verify that a DIR command will complete after you then attach the router.

You can also periodically check LANTRAN.LOG in the IBMCOM folder to see if other messages have been logged.

I honestly think that the OP-58/59 errors are beacon conditions - it could be that the router's port is set at the wrong ringspeed.

When a beacon event last more than 7 seconds, OS/2 will ask the token-ring adapter to leave the ring, and then attempt to re-join after 3 seconds. When this happens, you should see the server's lobe light change condition, and/or hear its relay click.

If RPL does not work full stop, then please post a zip file containing:

1. Your CONFIG.SYS, PROTOCOL.INI, IBMLAN.INI, LANTRAN.LOG and HPFS386.INI files (if using the Advanced server).
2. Your RPL.MAP file.
3. The contents of "DIR c:\IBMLAN\*.* > dirlist.txt"

mobybrick at hotmail dot co m

Regards,
Moby.


Subject  :  Re:Disk for RPL user guide
Author  :  Sam
Date  :  01 May, 2007 on 16:09
Moby,

Thank you very much for the detail reply. The problem was finally solved : router setting problem.

When I search for the logs you mentioned, discovered something interesting. There are LANTRAN.log with special prefix during the period the problem occurrence. Its format is LANTRAN.log.yyyymmdd.xxx where xxx are three digit number.

Any idea on under what situation(es) will such kind of log be generated ?

Thanks again


Subject  :  Re:Disk for RPL user guide
Author  :  Sam
Date  :  11 May, 2007 on 18:17
Is there anyone else discover this sort on interesting log pattern in your site ?

Thanks


Subject  :  Re:Disk for RPL user guide
Author  :  mobybrick
Date  :  12 May, 2007 on 18:29
The LANTRAN.LOG files usually contain startup error messages. The file will continue to log hard or physical errors with either the adapter or transport layer.

I have seen the lantran.log.yy.dd.mm messages before in the IBMCOM directory, but this actual phenomenon is undocumented. I imagine hard errors are put in there, into files of the date of occurrence, as they happen.

What messages do your files contain?

Moby


Powered by UltraBoard 2000 <www.ub2k.com>