- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: does SYSMAN from 7.3-2 to 7.2-2 system work?
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
тАО10-25-2005 07:12 AM
тАО10-25-2005 07:12 AM
does SYSMAN from 7.3-2 to 7.2-2 system work?
MCR SYSMAN SET ENV/CLUS does not work on the
7.3-2 system, does work from the (4) 7.2-2 systems. MCR SYSMAN SET ENV/CLUS/USER=xxx *does* work from the 7.3-2 system.
The failure message is SMI-E-ABORT error.
The SYSUAF, NETPROXY logicals look good.
I've restarted SMISERVER several times on all nodes. NCP OBJ SMISERVER (phase IV) seems to have no effect.
HP Support suggested we ensure all the MANAGE patches are up-to-date. They are.
Help, I'm just looking for other means to troubleshoot the thing, if I need to get into ANALYZE/SYSTEM, etc.
thanks for any pointers...
-Ron-
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-25-2005 07:28 AM
тАО10-25-2005 07:28 AM
Re: does SYSMAN from 7.3-2 to 7.2-2 system work?
Do you have a common sysuaf.dat/rightslist with the appropriate logicals defined in your cluster?
Andy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-25-2005 07:54 AM
тАО10-25-2005 07:54 AM
Re: does SYSMAN from 7.3-2 to 7.2-2 system work?
Yup, the logicals SYSUAF, NETPROXY and RIGHTSLIST all point to the same common disk and directory COMMON0:[SYSEXE]
thanks...
-Ron-
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-25-2005 05:47 PM
тАО10-25-2005 05:47 PM
Re: does SYSMAN from 7.3-2 to 7.2-2 system work?
if you use the same username you are logged into on the V7.3-2 system, does it works as well with SET ENV/CLUS/USER=
Does it fails on every kind of command ? Even a simple SYSMAN> SHOW PROFILE ?
The SMISERVER DECnet object is only used, if you use SYSMAN command to a remote node outside your cluster. Having multiple SYSUAFs in a cluster would not be a problem for SMISERVER. Even having different SYSUAFs is not a problem, if the user is not in one of the SYSUAFs, you get an appropriate error from that node, if you try to execute SYSMAN commands there.
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-25-2005 07:39 PM
тАО10-25-2005 07:39 PM
Re: does SYSMAN from 7.3-2 to 7.2-2 system work?
Is SYSTEM having all privs ?
Did you check quotas of SMI server (should not be the problem because /user works but you never know)?
Did you check accounting file for info of the process (may show the real message) ?
Did you check the operator log file ?
Did you check for audit alarms ?
Are all cluster nodes 7.3-2 or is this a mixed cluster ? Is sysuaf shared ?
Wim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-25-2005 09:36 PM
тАО10-25-2005 09:36 PM
Re: does SYSMAN from 7.3-2 to 7.2-2 system work?
just to make sure, because you've written, that the latest patches were instaled.
You have to have VMS722_MANAGE-V0100 which had been superseded by VMS722_UPDATE-V0100. This problem had been described there.
Mike
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-27-2005 03:40 AM
тАО10-27-2005 03:40 AM
Re: does SYSMAN from 7.3-2 to 7.2-2 system work?
First of all, I have a red face. The 7.2 nodes are 7.2-1 not 7.2-2 as I stated originally. I went from one environment to another to compare settings (they are both broken), but my immediacy is on the 7.2-1/7.3-2 environment. I apologize for this screw-up.
All seperate systems disk, with common disk for UAF, RIGHTSLIST, queues, etc.:
On the (4) 7.2-1 systems:
MCR SYSMAN SET ENV/CLUS works to all 5
On the (1) 7.3-2 system:
MCR SYSMAN SET ENV/CLUS/USER=FIELD
works to all 5 nodes
On the (1) 7.3-2 system:
MCR SYSMAN SET ENV/CLUS fails:
$ mc sysman set env/clus
%SYSMAN-I-ENV, current command environment:
Clusterwide on local cluster
Username FIELD will be used on nonlocal nodes
SYSMAN> do sho time
%SYSMAN-I-OUTPUT, command execution on node VM721A
%SYSMAN-I-NODERR, error returned from node VM721A
-SMI-E-ABORT, SMI Server has aborted
%SYSMAN-I-OUTPUT, command execution on node VM721B
%SYSMAN-I-NODERR, error returned from node VM721B
-SMI-E-ABORT, SMI Server has aborted
%SYSMAN-I-OUTPUT, command execution on node VM721C
%SYSMAN-I-NODERR, error returned from node VM721C
-SMI-E-ABORT, SMI Server has aborted
%SYSMAN-I-OUTPUT, command execution on node VM721D
%SYSMAN-I-NODERR, error returned from node VM721D
-SMI-E-ABORT, SMI Server has aborted
%SYSMAN-I-OUTPUT, command execution on node VM732A
27-OCT-2005 11:24:57
SYSMAN>
[Volker]
if you use the same username you are logged into on the V7.3-2 system, does it works as well with SET ENV/CLUS/USER=
Yes
Does it fails on every kind of command ?
Yes, even SHOW PROFILE
Even a simple SYSMAN> SHOW PROFILE ?
thanks for the info on NCP objects
[Wim]
Did you start SMI server with the SYSTEM account (@sys$system:startup SMISERVER) ?
yes I did, I did a STOP/ID and restart
Is SYSTEM having all privs ?
yes
Did you check quotas of SMI server (should not be the problem because /user works but you never know)?
did not check quotas yet
Did you check accounting file for info of the process (may show the real message) ?
no entry in the accounting file
Did you check the operator log file ?
no entry in operator.log
Did you check for audit alarms ?
not yet
Are all cluster nodes 7.3-2 or is this a mixed cluster ? Is sysuaf shared ?
one 7.3-2 can't sysman to four 7.2-1 nodes
all (4) 7.2-1 can sysman to the 7.3-2
yes sysuaf is shared
[Mike]
just to make sure, because you've written, that the latest patches were instaled.
You have to have VMS722_MANAGE-V0100 which had been superseded by VMS722_UPDATE-V0100. This problem had been described there.
good point: actually because I inadvertantly lied about the version, I looked up the patches that the admin installed (both appear to be the latest):
DEC AXPVMS VMS721_MANAGE V2.0
DEC AXPVMS VMS721_UPDATE V3.0
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-27-2005 06:34 AM
тАО10-27-2005 06:34 AM
Re: does SYSMAN from 7.3-2 to 7.2-2 system work?
This is a "non-supported" configuration -- so it's no surprise that it is having issues. The earliest Alpha version supported as interroperable with V7.3-2 is V7.2-2.
I can say from experience that V7.2-2 works pretty well with V7.3-2. I never took the chance to find out about 7.2-1 with 7.3-2.
Robert
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-27-2005 08:28 AM
тАО10-27-2005 08:28 AM
Re: does SYSMAN from 7.3-2 to 7.2-2 system work?
There are compatabilty issues between versions which are sometimes fixed with the MANAGE patches but it may be that for V7.2-1 they did not.
Purely Personal Opinion
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-04-2005 07:53 AM
тАО11-04-2005 07:53 AM
Re: does SYSMAN from 7.3-2 to 7.2-2 system work?
It looks as though the bug fix is included in the VMS722_MANAGE-V0100 patch. The issue is that after a SYSMAN SET ENV/CLUS issuance, the username for the SMISERVER process does not revert back to the (original) SYSTEM account. It is clearly described in the "bug fixes" section.
Unless anyone has a fix (hint hint) for 7.2-1, I would say that the customer is out of luck for now, since upgrading the four 7.2-1 nodes to 7.2-2 can't happen for several months.
thanks so much..
-Ron-
(this is my first foray in this forum, so I'm new to the "protocol")