topic Re: Switch LAT to different Card in Operating System - OpenVMS

Switch LAT to different Card

Aaron Lewis_1 — Fri, 23 Feb 2007 07:52:50 GMT

I have a couple of DE600 NICs in an ES80. Currently LAT and DECNET run through EWA & I need to move them to the EWB device. I know I can use NCP to force DECNET onto the B card, but how do I get LAT to move?

Re: Switch LAT to different Card

Uwe Zessin — Fri, 23 Feb 2007 08:08:04 GMT

You can do it with LATCP (CREATE LINK?) or use a logical name LAT$LINK ?

Re: Switch LAT to different Card

Aaron Lewis_1 — Fri, 23 Feb 2007 08:16:58 GMT

Okay, I see in LATCP where LAT is currently running on LAT$LINK EWA3, Would I create it a new LAT$LINK on EWB3, or use EWB0 & LAT will create a new virtual port on the EWB card? Will this make it a permenant change, and prevent LAT from running on the EWA card.

Re: Switch LAT to different Card

Martin Vorlaender — Fri, 23 Feb 2007 08:36:00 GMT

Aaron,

see the LATCP section in the System Management Utilities manual (http://h71000.www7.hp.com/doc/83final/6048/6048pro_039.html#startsubcommand_229 ):

CREATE LINK /DEVICE

If you enter the CREATE LINK command without the /DEVICE qualifier, LATCP attempts to find an available controller by using a list of possible LAT data link device names. HP recommends that you specify a default device name by defining the LAT$DEVICE logical name.

HTH,
Martin

Re: Switch LAT to different Card

Verne Britton — Fri, 23 Feb 2007 09:40:45 GMT

perhaps my lat$systartup.com file is old ... but it does have:

$! ------------------------- Start LAT Protocol -----------------------------
$!
$! *** NOTE ***
$! If you have a system with multiple Ethernet/FDDI controllers, you may want
$! to create a link in this section of LAT$SYSTARTUP.COM before LAT is
$! started.
$!
$! When LAT is started on a system with multiple controllers, and no link is
$! is created, then the LAT driver will pick the first controller from the
$! LAN Data Structures as the default. This controller may not be connected to
$! the wire. LTDRIVER has no way of determining this condition. As a result,
$! it will not display an error message and LAT will hang.
$!
$! To define a link for LAT, do the following:
$! 1. Find out what controller is attached to the Ethernet/FDDI wire.
$! (In this example we will use EXA0)
$! 2. Insert the following command line before LCP SET NODE /STATE=ON command
$! below:
$!
$! LCP CREATE LINK 1ST$LINK /DEVICE=EXA0
$!
$! 3. If you have more then one controller attached to the wire, then
$! repeat the above command line, calling the next controller "2ND$LINK".
$! i.e. -
$! LCP CREATE LINK 1ST$LINK /DEVICE=EXA0
$! LCP CREATE LINK 2ND$LINK /DEVICE="xxx0"
$!
$! Where, xxx0 is the next controller attached to the wire
$! ...
$! etc
$!
$ lcp set node /state=on

Love it when Engineering puts comments inside the DCL command procedures themselves :-)

Verne

Re: Switch LAT to different Card

Kris Clippeleyr — Fri, 23 Feb 2007 09:52:16 GMT

Hi,
How about defining the logical LAT$DEVICE ?
Greetz,
Kris (aka Qkcl)

Re: Switch LAT to different Card

Vladimir Fabecic — Fri, 23 Feb 2007 10:43:17 GMT

Verne gave you a solution.
Put
$ LCP CREATE LINK 1ST$LINK /DEVICE=EWB0
before
$ lcp set node /state=on
in SYS$STARTUP:LAT$SYSTARTUP:COM
and it will work.

Re: Switch LAT to different Card

Volker Halle — Fri, 23 Feb 2007 10:46:20 GMT

Aaron,

you can do all this by using explicit LATCP> CREATE LINK commands, but the simplest solution for moving LAT from EWA to EWB is:

$ DEFINE/SYSTEM LAT$DEVICE EWB

before invoking LAT$STARTUP

Volker.

Re: Switch LAT to different Card

Aaron Lewis_1 — Fri, 23 Feb 2007 11:09:10 GMT

I will add the commands to lat$startup