[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

5555.0. "Insuff. recource error after upgrade" by ZUR01::SCHNEIDERR () Wed Sep 01 1993 11:28

Hello,

A customer made an upgrade from EMS 2.2 to EMS 2.3. He installed EMS on a cluster.
He run the installation from a satelite VAX 4000-60. He has two licenses for EMS.
One on this satelite and an other one on an other satelite (3100-76).

After the upgrade we get the following errormessages, only on the 4000-60.

Each time we do an open domain, the default notificationrequest for this domain
is created and enabled. After the enable we get.

>Request from another PM not processed
>% MCC-E-EVT_POOL_INSRES, insufficient recources to create/access event pool
>
>Unexpected condition returned to Notification FM
>MCC Routine Error
>% MCC-E-EVT_POOL_INSRES, insufficient recources to create/access event pool




If we create a notification request mainly, the following happens:


   
    - Create Notify Request mit  Domain: DEMPR30
                                 Entity List: SNMP *
                                 Events: ANY EVENTS

       1) Unexpected condition returned to Notification FM
          MCC Routine Error
          %MCC-E-EVT_POOL_INSRES, insufficcient resources to create/access
                                  event pool

       2) Unexpected condition returned to Notification FM
          Exception encountered
          The Event Sink has stopped    


    - Create Notify Request mit Domain: DEMPR34
                                        Entity List: NODE4 *
                                        Events: ANY EVENTS


    -> 6 times this message:

         Unexpected condition returned to Notification FM
         Exception Encountered
         Internal Error in DECnet Phase IV AM


    - Again the same request

    -> No error message



Regards Roland
T.RTitleUserPersonal
Name
DateLines
5555.1Check global pages and run MCC_AUDITANTIK::WESTERBERGStefan Westerberg DS StockholmThu Sep 02 1993 07:380
5555.2will check GBLpagesZUR01::SCHNEIDERRMon Sep 06 1993 03:525
Stefan,

We run already the AUDITOR, but we didn't check the GBLpages. We will do it.

Thanks for the moment  Roland
5555.3GBLpages was the faultZUR01::SCHNEIDERRMon Sep 06 1993 04:388
Stefan,

We checked now the GBLpages and you got it !!!!

Thanks for the tip, now all is up and runing well.


Roland