[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference azur::mcc

Title:	DECmcc user notes file. Does not replace IPMT.
Notice:	Use IPMT for problems. Newsletter location in note 6187
Moderator:	TAEC::BEROUD

Created:	Mon Aug 21 1989
Last Modified:	Wed Jun 04 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	6497
Total number of notes:	27359

2160.0. "TSAM Message no 00000004" by SNOC01::MISNETWORK (They call me LAT) Wed Jan 22 1992 06:50

I have a problem using TSAM and alarms on a DECserver 200. Basically the alarm 
checks for the software status of the DECservers, but I keep getting the 
following exception error

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Section out of the EXCEPTION log


"MCC 0 ALARMS RULE LIDSB_down"-          !rulename
"LIDSB DECserver no longer in normal state, please check "-          !category
                      "LIDSB DECserver"-          !description
"(terminal_server LIDSB software status <> Normal, at every 00:02:00)"-!expression
"29-NOV-1991 13:06:26.18"-          !time
"The requested operation cannot be completed
>>>>> <EOS>%NONAME-F-NOMSG, Message number 00000004"-          !dtcrtf or error
"user=netmanager"-         !notification params
"SYS$SCRATCH:MCC_ALARMS_DATA_13062618.DAT"    !file that contains 
more info about the rule

When I try to check the attributes of these DECservers, MCC seems to hang, and
after a ^c I get the same message -


mcc>show terminal_server VILSA all attri
				
				Address = 08-00-2b-12-21-3e
				Name    = NRMANM_NS:.VILSA
^c
%MCC-I-CANCEL, cancel
The requested operation cannot be completed
	VMS Routine Error = %NONAME-F-NOMSG, message number 00000004

and at the same time  some TSAM alarms for MUXserver 300s that have been 
running without error come up with the same alarm exception

Below is the TSM output for one of the DECservers -

TSM> SH SERVER

DECserver 200 V3.1 BL37     LAT V5.1   ROM BL20    Uptime: 110 11:32:25

Address:   08-00-2B-0A-DA-0E   Name:   VILSA              Number:     0

Identification:  Villawood DECserver A

Circuit Timer:            80           Password Limit:            3
Console Port:              0           Prompt:             VILSA > 
Inactivity Timer:         30           Queue Limit:              24
Keepalive Timer:          20           Retransmit Limit:         50
Multicast Timer:          30           Session Limit:            32
Node Limit:              100           Software:          PR0801ENG

Service Groups:   0

Enabled Characteristics:

Announcements,  Broadcast,  Dump,  Lock


Any quick ideas would be greatly appreciated !! 

Cheers,
Louis

T.R	Title	User	Personal Name	Date	Lines
2160.1	help....anyone..	SNOC01::MISNETWORK	They call me LAT	`Fri Jan 24 1992 02:50`	4
	Ok, any not so quick ideas ? This is a worry ! CHeers, Louis
2160.2	QAR 2215	TOOK::MINTZ	Erik Mintz, DECmcc Development	`Fri Jan 24 1992 10:43`	2
	Entered as QAR 2215 for the Terminal Server AM
2160.3	decmcc 1.1 with tsam?	TOOK::CALLANDER	MCC = My Constant Companion	`Fri Jan 24 1992 14:39`	2
	you are using DECmcc 1.1 right? TS AM is not 1.2 compatible.
2160.4	some questions	TOOK::CASSIDY	Linda, LKG2-2/BB10, DTN 226-7270	`Fri Jan 24 1992 16:45`	9
	I didn't understand some of the details in the base note - Does the problem happen on only that one server? Does the problem only happen on DS200's? Does checking the server attributes hang only AFTER you get this alarm error? I assume the servers are okay (uptime for the display you included showed over 110 days. - Linda
2160.5	TSAM not currently in active FT	TOOK::MINTZ	Erik Mintz, DECmcc Development	`Mon Jan 27 1992 13:37`	8
	Sorry, it turns out this was not an appropriate note to enter as a QAR. There is currently no active TSAM field test. The early field test (on DECmcc V1.1) is no longer active, and field test of a V1.2 compatible TSAM has not yet started. Once field test is re-started, then the TSAM developers will have time to respond to support questions.
2160.6	More info	SNOC01::MISNETWORK	They call me LAT	`Mon Jan 27 1992 20:17`	8
	I am using DECmcc V1.1 with appropriate TSAM version. The problem happens on all the DECserver 200's. I have had no problem with the MUXserver 300's. The alarm exception on my MUXserver alarms come up only when I ^c out of my show server command ( on DECserver 200's ). Extremely strange! Cheers, Louis
2160.7	Is problem dead?	SNOC01::MISNETWORK	They call me LAT	`Mon Jan 27 1992 21:48`	12
	re .5 Does this mean that I am out of luck getting this problem looked at. The reason for my concern is that I have TSAM on a Digital owned system on a customer site, and we are trying to show them just what we can do for them as far as managing their network. Problems like this, and the fact that we can't immediately fix them don't look too good. I know that TSAM was never out of Field Test and work on TSAM 1.2 is stretching resources, but when a customer decides what they want to buy, they go for what they see works for them. Thanks for your help. Cheers, Louis
2160.8	Mystery solved	SNOC01::MISNETWORK	They call me LAT	`Mon Feb 03 1992 05:08`	18
	After getting some more time to look at this problem, I found that the problem is not specifically related to any bug in TSAM. The details are in note 2250. In brief, the problem was caused by some alarms polling PDPs registered as STATIONS. When enabled, the following errors would occur - TSM error is NO USEABLE SERVICE CIRCUITS TSAM error is NO USEABLE SERVICE CIRCUITS NCP error is CONSOLE CARRIER PROTOCOL NOT AVAILABLE - ALREADY IN USE Similar problem to using TSM and LTM on same system. Will have to change my PDP monitoring methods. Cheers, Louis
2160.9	see 2250	TOOK::CALLANDER	MCC = My Constant Companion	`Wed Feb 05 1992 14:18`	3
	also see 2250, I believe it relates to what you are seeing (than again, I don't know tsam so maybe not :->)