- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: LAT always on ewa interface
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-03-2003 10:11 AM
12-03-2003 10:11 AM
LAT always on ewa interface
when we boot our new DS20E the LAT driver is always on the ewa interface. But we want use only one interface (eia0) for DECnetplus, TCP/IP and LAT. We do right now after each (re)boot:
LATCP> delete LINK LAT$LINK
LATCP> create LINK LAT$LINK /DEVICE=EIA0 /STATE=ON
Question: is there another way, to get the LATdriver on the eia interface permanent.
used VMS version 7.3-1 with some patches (issued before dec 2002).
The system disk are from the 3 years old DS20E system; almost the same (beside FW-version,CPU speed,graphics card) and a DE600 (dual port; eia,eib) instead a DE500 (single port); the ewa interface is from KZPCM (dual scsi/net)
Thanks
Erich
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-03-2003 03:57 PM
12-03-2003 03:57 PM
Re: LAT always on ewa interface
the trivial solution should be to put the commands you quote in a script and execute this in the system startup (after lat$startup ,-).
I will investigate tomorrow if there is a more permanent solution.
Greetings, Martin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-03-2003 04:35 PM
12-03-2003 04:35 PM
Re: LAT always on ewa interface
that's what are we doing right now. But it's just a work around.
Thank's
Erich
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-03-2003 06:23 PM
12-03-2003 06:23 PM
Re: LAT always on ewa interface
$define /sys /exec lat$device eia0:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-03-2003 06:24 PM
12-03-2003 06:24 PM
Re: LAT always on ewa interface
Modify LAT$SYSTARTUP.COM accordingly. This is called by LAT$STARTUP.COM and used to create LAT link among other things...
HTH,
Lokesh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-03-2003 09:17 PM
12-03-2003 09:17 PM
Re: LAT always on ewa interface
in LAT$SYSTARTUP.COM HP posted this notice:
$!
$! 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".
HP hints modify LAT$SYSTARTUP.COM to solve your problem.
H.T.H.
Antoniov
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-04-2003 03:24 AM
12-04-2003 03:24 AM
Re: LAT always on ewa interface
I like the define LAT$DEVICE version: I will test this tomorrow. I will respond.
Thanks again.
Erich
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-04-2003 07:14 AM
12-04-2003 07:14 AM
Re: LAT always on ewa interface
OpenVMS Developer & System Manager
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-04-2003 08:27 PM
12-04-2003 08:27 PM
Re: LAT always on ewa interface
D.