topic Re: Invalid management response in TSM in Operating System - OpenVMS

Invalid management response in TSM

Wim Van den Wyngaert — Tue, 03 Jan 2006 04:01:22 GMT

I use TSM to manage a decserver 700.
I use VMS 7.3 with decnet+.

When I try "use server xxx", I get
%CCR-E-INVRESP, invalid management response
%TSM-E-CONNECT_FAIL, Connection to terminal server has failed
%TSM-I-DEGFAULT_USAGE, set to default usage

I can access other decservers.

I can use the ports on the decserver via console manager without any issues.

I rebooted the TSM node. The decserver is not to be rebooted by preference. No change.

I can access the decserver with set host/mop. It works as expected but once in a while I get %CCR-F-DEVOFFLINE, device is not in configuration or not available
and the session is aborted.

I checked the network : 10 half. OK.

I checked the csma counters on both ends. Nothing special.

HEEEELLLPPP

Wim

Re: Invalid management response in TSM

Wim Van den Wyngaert — Tue, 03 Jan 2006 05:00:40 GMT

Update.

It worked just a moment ago. I could use the decserver and do some show commands.
But now it's again giving the invalid... message.

Wim

Re: Invalid management response in TSM

Wim Van den Wyngaert — Tue, 03 Jan 2006 06:05:03 GMT

Found it, I think. The message is given when someone already is using the decserver via TSM or set host or whatever.

A process must have locked it with set host/mop during 2 months (the time that TSM access was impossible).

Is there a way to check that except scanning all nodes for processes running net$ccr.exe ?

Wim

Re: Invalid management response in TSM

Ian Miller. — Tue, 03 Jan 2006 09:43:53 GMT

MOP remote console protocol only allows one connection. Only the DECserver knows if someone is connected. The connection could be using TSM, SET HOST/MOP, NCP or LANCP. This unhelpful response sounds like a a feature (bug) of TSM.

You could try connecting using another utility to see if it returns a better error.

Re: Invalid management response in TSM

Rinkens — Wed, 04 Jan 2006 05:52:17 GMT

Hi Wim

I do not think if this happens whne somebody else is logged on the the server.

You get another message
TSM> SHOW SERVER *

Server Address Type Status Partition

EVHLI1 00-00-F8-52-6B-A6 DS700 Available DEFAULT

TOTAL 1 Servers, 1 Available, 0 Unavailable, 0 Circuit Errors

TSM> USE SERVER EVHLI1
%MOP-E-CONBUSY, remote console in use
%TSM-E-CONNECT_FAIL, Connection to terminal server has failed
%TSM-I-DEFAULT_USAGE, Set to default usage, DIRECTORY
TSM>

Is the server not rebooting sometimes check the uptime from the server if possible.

TSM_SVR_EVHLI1> SHOW SERVER

Network Access SW V2.2 for DS700-08 BL29-52 ROM V6.3-0 Uptime: 394 18:34:52

Address: 00-00-F8-52-6B-A6 Name: EVHLI1 Number: 0

Identification:

Circuit Timer: 80 Password Limit: 3
Console Port: 1 Prompt: Local>
Inactivity Timer: 30 Queue Limit: 100
Keepalive Timer: 20 Retransmit Limit: 8
Multicast Timer: 30 Session Limit: 64
Node Limit: 200 Software: WWENG2

Service Groups: 0

Enabled Characteristics:
Announcements, Broadcast, Dump, Lock

Regards Kor

Re: Invalid management response in TSM

Wim Van den Wyngaert — Wed, 04 Jan 2006 05:57:28 GMT

Kor,

I did get the message using TSM 2.1 on VMS7.3. Not when the other session is using TSM too but when set hos/mop is used (I just tested it again).

The decservers over here reboot very rarely, if ever. Up times of over a thousand days are possible.

Wim

Re: Invalid management response in TSM

Dietmar Morneweg — Wed, 04 Jan 2006 06:12:43 GMT

Hi,

being newby to the forum my answer to this question might be too trivial, but when you get one of the following messages, it means the server is already been used/accessed (for administrative/any purpose) by someone/process else.
You can try any way to connect, but it should always be in vain, you will always been rejected, as long as the process is logged off, or the dec-server has been hard resetted.

%TELNET-I-TRYING, Trying ...
%TELNET-E-CONNFAIL, Failed to connect to remote host
-SYSTEM-F-REJECT, connect to network object rejected

$ ftp server76t
%TCPIP-E-FTP_NETERR, I/O error on network device
-SYSTEM-F-REJECT, connect to network object rejected

and many more like these

regards
Dietmar

Re: Invalid management response in TSM

Wim Van den Wyngaert — Wed, 04 Jan 2006 06:15:12 GMT

Dieter,

Were not talking about tcp here.

Wim

Re: Invalid management response in TSM

Robert_Boyd — Wed, 04 Jan 2006 12:47:28 GMT

Wim,

Do you have via console manager a connection to the offending terminal server on a port that you can use as an administrative port? Or do you have all the ports committed as application ports?

If you can connect up to one port and login as with the privileged password, then you can SHOW SESSIONS ALL and SHOW QUEUE. YOu might be able to see an active management connection that way. As I recall on the 8 port servers it would show up as on PORT 9, not sure about the 16 port servers.

Robert

Re: Invalid management response in TSM

Jon Stanley — Mon, 16 Jan 2006 11:25:11 GMT

We are still here in DECserver design and support at DNPG. The question is how many management sessions can be connected to the DECserver at any one time. the answer is one. So MOP / IP can only have one session connected at a time and only one of either MOP or telnet can be connected at any one time.

There can be up to 17 connections to the DECserver 700, (16 remote connections, to ports, and a management connection. There can be 33 connections with the DECserver 732.

With release of DNAS V3.0 you can have up to 4 console connections to a DECserver using IP, but all are "sharing" the same session (Multiplexing feature).

--Jon