Conference azur::mcc

3900.0. "Extra information was returned for NODE4" by USTICA::ODOARDI () Wed Oct 14 1992 13:33

	Hello,

	I'm thinking to upgrade my MCC version 1.1 to 1.2 (SSB or EMS).

	In this time I've installed (on different station) both the release.

	My last problem is this:

	when I want to see node4 characteristic (the real entity is DEMSA)
	with MCC 1.2 (using Iconic Map) I obtain an "Extra Information 
	Message".

	If I do the same command with 1.1 all is O.K.

	What is the problem?

	Thanks,

					Barbara




	DECmcc 1.1:
	===========

	Parameters obtained with Iconi Map:

	Babble Timer	6000
	Cost		11
	Counter Timer	14400
	Hello Timer	15
	Line		MLN-GVA
	Maximum Transmits 128
	Protocol	DDCMP Point
	Transmit Timer	--NOT RETURNED --



	ASKY_Bra> mccl
	DECmcc (V1.1.0)


	MCC> show node4 mlngva circ mln-gva all char

	Node4 46.34 Circuit mln-gva
	AT 14-OCT-1992 13:39:47 Characteristics
	
	Examination of Attributes shows:
	                          Counter Timer = 14400 Seconds
        	                           Cost = 11
                	            Hello Timer = 15 Seconds
                        	           Line = MLN-GVA
                 	              Protocol = DDCMP Point
         	                  Babble Timer = 6000 Milliseconds
                	      Maximum Transmits = 128 Messages


*********************************************************************
	DECmcc 1.2:
	===========

	Parameters obtained with Iconi Map:

	Counter Timer	14400
	Cost		11
	Hello Timer	15
	Line		MLN-GVA
	Protocol	DDCMP Point
	administrativeState --NOT RETURNED --

	AND:

	Management Window Message: Extra information was returned for 
	     		Node4 MLNGVA Circuit MLN-GVA : code 97

	Management Window Message: Extra information was returned for 
	     		Node4 MLNGVA Circuit MLN-GVA : code 100




	Gundam > manage/enter
	DECmcc (V1.2.0)

	MCC> show node4 mlngva circ mln-gva all char

	Node4 46.34 Circuit mln-gva
	AT 14-OCT-1992 12:55:57 Characteristics

	Examination of Attributes shows:
	                          Counter Timer = 14400 Seconds
        	                           Cost = 11
                	            Hello Timer = 15 Seconds
                        	           Line = MLN-GVA
                    	               Protocol = DDCMP Point
                        	   Babble Timer = 6000 Milliseconds
                     	      Maximum Transmits = 128 Messages





    

Hi Barbara,

I think that what you are seeing is differences in the management specification
for node4 circuit between v1.1 and v1.2.

The Extra Information message is displayed when attributes are returned in
outp which do not belong to the variant for this circuit. Indeed codes 97 and 
100 are for attributes babble timer and maximum transmits which are in outp
(can be seen in FCL display - FCL simply decodes outp without taking variants
into account).

Additionally, because of the way the variant information was defined, the
administrativeState was expected in outp (but not returned) in V1.2.  Similarly,
in V1.1, Transmit Timer was not returned.

The attribute used for variant selector is Protocol.

Hope this helps a little.

Verna

	Hello Verna,

	and thank you for your answer (I've just suspected a similar reply...).

	My question is this:

	Can I receive a correct information from Iconic Map???




						Barbara

		

> 	Management Window Message: Extra information was returned for 
> 	     		Node4 MLNGVA Circuit MLN-GVA : code 97
> 
> 	Management Window Message: Extra information was returned for 
> 	     		Node4 MLNGVA Circuit MLN-GVA : code 100

I understand why variants are needed and used.  But more often than not they
are  wrong!  MCC  in general, and the iconic PM in particular, have improved
the  handling  of  the  (not at all uncommon case) where the data dictionary
doesn't agree with the real world but it needs to get better still.

In this  case, for example, there is no excuse at all for not displaying the
name  and value of the extra attributes in the pop-up messages.  There is no
excuse for just saying "code 97".  All the information was in the dictionary
and FCL managed just fine!

Oh, and  by  the  way, the variants clearly need to be fixed for V1.3 -- can
someone enter a QAR for this, please, so that it doesn't get forgotten.

Graham

It is already very late in the V1.3 development cycle.

If you feel this is important, I would suggest stating your case 
yourself; see note 7 for instructions on filing QARs.

-- Erik

    I went in and fixed the phaseIV MSLs for Circuit and Line variant
    info.  The fix will be in V1.3 (including fieldtest).