converting snaplus from token ring to ethernet. what to look for?

[Randy Westlake]

I've got a customer that is converting snaplus from token ring to ethernet. Not exactly sure what to check for since I've not worked with sna before.

[Chris Wilshaw]

We use SNA on X25 and Serial links, but not Token Ring / Ethernet, but this may be of some help.

config is in /etc/opt/sna

logs are in /var/opt/sna (sna.aud and sna.err)

[john korterman]

Hi,
it probably depends on how the unix machine are defined in the SNA environment.

Maybe the following does not fit your situation, and I should immediately say that I am not a SNA expert myself, but I once looked over the shoulder of an absolute SNA expert at work on a number of unix machines.

The unix machines were defined as so-called PUs (physical units), on which a number of LUs were defined. One particular entry depended on whether the unix machine was on an ethernet or a TR network, namely HP_ETHER_STATION_ADDRESS[0] in /etc/rc.config.d/hpetherconf
This entry pointed back to the PATH DIALNO entry on the mainframe.
If the unixmachine was on an ethernet then the expert entered the last 12 chars of the PATH DIALNO definition directly in the above entry like e.g:
HP_ETHER_STATION_ADDRESS[0]=0x

However, if the unix machine was on a TR network then the bit pattern of the last 12 chars of the PATH DIALNO had to be turned upside down before entered. Sounds a bit strange, but it is what the attached script does. It asks for a hex value; if you enter the last 12 chars of the PATH DIALNO on the mainframe, you should then hopefully see your entry for HP_ETHER_STATION_ADDRESS on the TR unix machine.

So the outcome of all this is that when changing the unix machine fron TR to ethernet, use the last 12 chars of the PATH DIALNO literally in HP_ETHER_STATION_ADDRESS.
Hope it makes some sense.

regards,
John K.