- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- What might have turned LGI_CALLOUTS to 1?
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
Discussions
Discussions
Forums
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
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-28-2006 05:58 AM
тАО12-28-2006 05:58 AM
a 7.3-2 alpha, Update 8 and the other current
ecos, after rebooting we had a problem which
ended up being LGI_Callouts was turned on,
which disabled telnet connectivity, (running Multinet).
What could have possibly changed the parameter?
Autogen was not run. There were no references to it iny any params.dat
ECOs Installed were
Update_v0800
acrtl_v0300
audserver_v0300
RMS_v0300
SECSRV_v0100
SYS_v1100
TDF_v0400
XFC_v0300
I've seen articles on how it IS set to zero,
but what might NOT be set to zero.
Much thanks.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-28-2006 06:06 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-28-2006 07:48 AM
тАО12-28-2006 07:48 AM
Re: What might have turned LGI_CALLOUTS to 1?
Wouldn't that mean it would come back on reboots?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-28-2006 07:58 AM
тАО12-28-2006 07:58 AM
Re: What might have turned LGI_CALLOUTS to 1?
The command that activates this service and creates MULTINET:START_ACCESS.COM is
$ MULTINET CONFIGURE/ACCESS
if I recall correctly. If you don't have a MULTINET:START_ACCESS.COM file then the service wasn't activated.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-28-2006 08:59 AM
тАО12-28-2006 08:59 AM
Re: What might have turned LGI_CALLOUTS to 1?
had existed for ages. The apparent change
in the sysgen behavior was after the ecos.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-28-2006 09:02 AM
тАО12-28-2006 09:02 AM
Re: What might have turned LGI_CALLOUTS to 1?
The most common reasong for LGI_CALLOUTS to be set to 1 is something like this:
MCR SYSGEN
SYSGEN> SET something
SYSGEN> WRITE CURRENT
Since this copies ACTIVE parameters to CURRENT, it can inadvertently set things that shouldn't be set. Note it doesn't matter what parameter was modified, LGI_CALLOUTS would be taken along for the ride. In general, if you want to use LGI_CALLOUTS you should define the logical name and install the target image FIRST. When it's known to have been successful, THEN set the parameter in the active set.
I thought OpenVMS startup was modified to force LGI_CALLOUTS to 0 because setting it when it shouldn't be set will block all access to the system. I'm not sure what version that happened in. If you're post the change, something in your startup must have turned it on. Maybe turning on SYSGEN auditing and/or alarms might help find it?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-28-2006 09:13 AM
тАО12-28-2006 09:13 AM
Re: What might have turned LGI_CALLOUTS to 1?
just checked...
LGI_CALLOUTS is forced to 0 on V7.3-2 in SYS$SYSTEM:STARTUP.COM. If it's changed, you'll see a console message:
%STDRV-I-LGI_CALLOUTS, forcing system parameter to 0
Maybe try
$ SEARCH SYS$SYSDEVICE:[000000...]*.COM LGI_CALLOUTS
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-28-2006 10:11 AM
тАО12-28-2006 10:11 AM
Re: What might have turned LGI_CALLOUTS to 1?
Will check when back at the shop. I can assure
you it was not changed interactively, as it occured while only I was on it, doing a round of ECOs.
But I'll check the logs.
Bob