[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

4371.0. "T1.3 dna$towers change after register node4 entity" by GOYA::MERINO () Mon Jan 11 1993 15:38

I am running the Polycenter Framework for ULTRIX T1.3.

Could anybody explain me why after registering a node4 the dna$towers
attribute changes as shown below?

Before the mcc register:

dns> show obj .es.cica.dna.sevax2 dna$towers
                                SHOW
                              OBJECT  PIVE:.es.cica.dna.sevax2
                                  AT  11-JAN-1993:18:25:13
                    DNA$Towers (set) = :
                   Tower  1 Floor 1  = 01 13    (null)
                   Tower  1 Floor 2  = 02       00 13           ncacn_dnet_nsp
                   Tower  1 Floor 3  = 04       (null)
                   Tower  1 Floor 4  = 06       39 72 4f 10 01 00 01 00 01 00 01
 00 36 aa 00 04 00 03 d8 20

After the mcc register:

dns> show obj .es.cica.dna.sevax2 dna$towers
                                SHOW
                              OBJECT  PIVE:.es.cica.dna.sevax2
                                  AT  11-JAN-1993:18:26:56
                    DNA$Towers (set) = :
                   Tower  1 Floor 1  = 01 13    (null)
                   Tower  1 Floor 2  = 02       00 13           ncacn_dnet_nsp
                   Tower  1 Floor 3  = 04       (null)
                   Tower  1 Floor 4  = 06       39 72 4f 10 01 00 01 00 01 00 01
 00 36 aa 00 04 00 03 d8 20
                    DNA$Towers (set) = :
                   Tower  1 Floor 1  = 01 13    (null)
                   Tower  1 Floor 2  = 02       00 13           ncacn_dnet_nsp
                   Tower  1 Floor 3  = 04       (null)
                   Tower  1 Floor 4  = 06       39 72 4f 00 00 00 00 00 00 00 00
 01 00 00 00 30 73 4e 00 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0
0 00 00 57 0d 10 4d 43 43 5f c4 59 01 10 06 17 ff ff 05 28 01 00 a4 81 01 00 00
00 00 00 ff ff 3c 80 5e 00 00 00 b3 ad 51 2b 02 09 0d 00 11 f0 31 2b af d4 03 00
 11 f0 31 2b b8 d4 03 00 00 20 00 00 02 00 00 00 de eb bd 5e 00 00 00 00 a0 59 0
1 10 00 00 00 00 00 00 00 00 54 37 4c 00 00 00 00 00 01 00 00 00 09 80 26 03 00
00 00 00 34 8b 05 10 4c 6c 4e 00 00 00 00 00 54 37 4c 00 00 00 30 00 00 00 00 00
 00 00 00 00 00 00 00 00 a0 59 01 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0
0 00 00 00 00 00 01 00 00 00 f4 87 4d 00 00 00 00 00 02 00 00 00 2c 53 12 10 6c
7d 4a 00 00 00 00 00 00 00 00 00 00 00 00 00 04 00 00 00 00 00 00

T.RTitleUserPersonal
Name
DateLines
4371.1More info on Phase IV Address PrefixGOYA::MERINOTue Jan 12 1993 15:1615
    I tried the same operation in a different system with different Phase
    IV address prefix and the behaviour is normal.
    
    If the Phase IV address prefix is 49:: the dna$towers are updated
    correctly.
    
    If the Phase IV address prefix is 39:724:1001000100010001 the
    dna$towers are updated incorrectly.
    
    Is this a known problem?
    
    Is there any patch to solve it?
    
    Thanks for answers,
    Angel.
4371.2Sounds like QAR materialTOOK::MINTZErik MintzTue Jan 12 1993 15:475
This does not sound like a familiar problem.
I would suggest a QAR (see note 7).

-- Erik

4371.3What's your MCC_NODE_IDP?TRM::KWAKWed Jan 13 1993 14:257
    
    RE: .0 & .1
    
    What is your MCC_NODE_IDP defined to?
    Is it set to "39:724:" ?
    
    William
4371.4MCC_NODE_IDP=39:724:1001000100010001GOYA::MERINOThu Jan 14 1993 13:374
    The value of the environment variable MCC_NODE_IDP is
    39:724:1001000100010001
    
    Angel
4371.5The fix will be available in V1.3 SSBTRM::KWAKFri Jan 22 1993 11:495
    
    The problem has been fixed and the change will be included
    in the DECmcc V1.3 SSB kit.
    
    William