[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

3325.0. "No Notification for NODE4 * in V1.2!" by FOUR62::LICAUSE (Al Licause (338-5661)) Tue Jul 07 1992 17:37

I noticed this problem late in the T1.2.7 release and see that it appears to
still be with us in the released version.

Any notification events defined for entity NODE4 * are ignored......we must
use specific node4 entries for each node needed.  

I didn't notice anything specific about this in the release notes, but in
any case if it is reproduceable, this could mean some very large notification
files.

Interested to know if anyone else sees the same problem.

Al
T.RTitleUserPersonal
Name		DateLines
3325.1node4 circuit okCTHQ4::WOODCOCKTue Jul 07 1992 17:558
Hi Al,

The node4 circuit entity seems ok. I use NODE4 * CIRCUIT * with both of the
last kits.

regards,
brad...
3325.2Still doesn't work on the VAX4000/500 V5.5 VMSFOUR62::LICAUSEAl Licause (338-5661)Wed Jul 08 1992 11:0822
Ok.....I give up on this one....well almost!

Developers please....might this be a timing problem?

It appears to work on a VAXstation 4000/60, but not on the 4000/500.
Both systems are running V5.5 VMS.

I've tried changing the case, I've tried changing the MCC node to a routing
node, I've tried enable and disabling and deleting rules until I'm blue in
the face.

I've checked targeting.....NONE!  for any domain.

I've checked filtering.....none specified and I've even disabled all filtering
specifically.

The wild card does work for COLLECTOR entities, but not NODE4!!!!!

Any suggestion, ideas or thoughts would be appreciated.  Has anyone run this
and gotten it to work with the same configuration mentioned above?

Al
3325.3A REAL BUG!...BEWARE OF PARTIALLY REGISTERED NODE4 ENTITES!!!FOUR62::LICAUSEAl Licause (338-5661)Thu Jul 09 1992 11:2020
Many thanks to the patience of Stella Ko...

This is a real bug in V1.2 SSB.

Since our setting is an isolated demo center, not linked to the Easynet,
I needed to demonstrate the limited capability for managing or at least
monitoring an SNA gatewy.

I created a NODE4 entity called SNAGWY which, of course did not exist, and
as a result, was known by MCC as a partially registered entity.  I also 
created a COLLECTOR with this node and used same to pass SNANCP strings.

We found that it was the partially registered NODE4 entity that was causing
the NODE4 * type notification events to be ignored.

Once this entity was removed, the NODE4 * events were now caught and displayed.

I will replace NODE4 SNAGWY with REFERENCE SNAGWY.

Al
3325.4Should have been fixedBIKINI::KRAUSEEuropean NewProductEngineer for MCCFri Jul 10 1992 04:4310
>This is a real bug in V1.2 SSB.
>
>We found that it was the partially registered NODE4 entity that was causing
>the NODE4 * type notification events to be ignored.
>

    Which "SSB Kit" do you have? I thought Jill Callander fixed this one
    already. Jill?

    *Robert
3325.5I don't think its the same bugTOOK::MINTZErik Mintz, dtn 226-5033Fri Jul 10 1992 08:146
The bug that was fixed at the last minute was an access violation that
occured in notification if the first entity in a domain was partially
registered.  That does not sound like the same case as described here.

-- Erik
3325.6FOUR62::LICAUSEAl Licause (338-5661)Fri Jul 10 1992 14:285
This is the kit annouced in note 3.167, dated July 2,1992.

Stella Ko is now able to reproduce the problem and will submit a QAR on same.

Al