[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

3839.0. "BRIDGE rule exception, INV_HANDLE error" by CSOADM::ROTH (I'm getting closer to my home...) Wed Sep 30 1992 23:22

DECmcc V1.2
VMS V5.5
local namespace

Some LANbridge rules run for about an hour and then all conk out with the
following exception:


**** Exception occurred in rule 
Domain LOCAL_NS:.oveng Rule OVENG_BRIDGE_LINEDOWN
at  30-SEP-1992 01:27:50.66  ****

    Rule name:     Domain LOCAL_NS:.oveng Rule OVENG_BRIDGE_LINEDOWN
    Domain:        Domain LOCAL_NS:.oveng
  Occurred at:     30-SEP-1992 01:27:50.66
     Category:     BRIDGE_LINEDOWN
  Description:     Bridge Line is not = FORWARDING. This means that one side
                   of the LANbridge is down... bridge is faulty or there is a
                   bad Ethernet problem.
     Severity:     Indeterminate
 
   Expression:     (BRIDGE * LINE * PORT MODULE STATE <> FORWARDING, AT EVERY
                   00:10)

    Exception:     %MCC-E-INV_HANDLE, software error: invalid handle parameter
                   The rule has been disabled
 

Here's what the message manual says about this:

INV_HANDLE, software error: invalid handle

Source: Information Manager, AHS routines, all modules, FCL PM

Explanation: DECmcc was asked to process a handle, but it was in an
             invalid state or had an invalid context.

User Action: Developers: check your code. End users: please contact
             your Digital representative.


Any guesses?

Thanks-

Lee Roth
T.RTitleUserPersonal
Name		DateLines
3839.1Oh no - not the Invalid Handle !MOLAR::ROBERTSKeith Roberts - Network Management ApplicationsThu Oct 01 1992 09:0613
  Roth,

  The Invalid Handle error pops up from time to time.  Because it is
  so intermittent it has been very difficult to find and fix.  A few sections
  of code have been fixed - and we thought it was gone - guess not 8(

  We suspect that certain error conditions are not properly cancelling a
  Handle before it is deleted.  The delete operation then returns the Invalid
  Handle error which bubbles up.

  I have entered a QAR in the MUSEUM QAR database: mcc013_int # 11

  /keith
3839.2CSOADM::ROTHI&#039;m getting closer to my home...Thu Oct 01 1992 15:456
Any suggestions on how to avoid it? Use different rule format?  Avoid
wildcards? Switch from pop to lemonaide at lunch?

Thanks-

Lee
3839.3any special conditions when the error occursMOLAR::ROBERTSKeith Roberts - Network Management ApplicationsThu Oct 01 1992 16:1017
RE: .2

> Any suggestions on how to avoid it? Use different rule format?  Avoid
> wildcards? Switch from pop to lemonaide at lunch?

  I'm sorry that my reply didn't help solve the problem.  Because this is
  a really odd thing to reproduce 'in the lab' - it makes it all that much
  harder to track down and repair.

  If you can record any special conditions that may be occuring when the
  rule when you get this error, it may help us reproduce it.

  It is possible that the global wildcard is the cause - that is relatively
  new code.  You could try running rules without it and see if the error
  goes away.

  /keith
3839.4maybe this is why..CSOADM::ROTHI&#039;m getting closer to my home...Fri Oct 02 1992 09:4724
Could this have led to the problem?


                TOP
                /|\
               / | \
              /  |  \
             A   B   C

Wildcard rules placed in domain A, B, C

Domain A contained a DOMAIN icon pointing to domain B
Domain B contained a DOMAIN icon pointing to domain C
Domain B contained a DOMAIN icon pointing to domain A
Domain C contained a DOMAIN icon pointing to domain B

All of these extra icons were DYNAMIC rather than static.

(someone else put these in so they could move laterally from domain to domain.
Of course, this made notifications interesting...)

I have removed these 'extras' and will see how the bridge rules fares.

Lee
3839.5good bet.\TOOK::MCPHERSONpre-retinal integrationFri Oct 02 1992 10:149
>Domain A contained a DOMAIN icon pointing to domain B
>Domain B contained a DOMAIN icon pointing to domain C
>Domain B contained a DOMAIN icon pointing to domain A
>Domain C contained a DOMAIN icon pointing to domain B
>
>All of these extra icons were DYNAMIC rather than static.

It's a good bet that dynamic domains with that sort of 'cross-containment'
caused your problem.
3839.6Still a bad boy...CSOADM::ROTHI&#039;m getting closer to my home...Thu Oct 08 1992 17:3610
Well, I cleared up the 'cross-containment' stuff and it still happens.

BTW, I am running a batch job that keeps the rules always enabled, if that
matters.

I will enter this into the QAR system.

Thanks-

Lee
3839.7See #3398.6TRM::KWAKWed Nov 11 1992 11:117
    
    Please see reply .6 of topic #3398
    
    #3398 described the same problem. The problem seems to be in
    the Bridge AM.
    
    William