Conference azur::mcc

2560.0. "disabling an access module is not easy" by COL01::LUNT () Fri Mar 13 1992 14:12

Hello,


	I am trying to test out the Lan Autotoplogy part of the ELM package. I
ran into problems when the program tried to create the map file. I was then
reading through the manual and read that the listener cannot run concurrently 
with the Ethernet am. So, I figured, perhaps this is my problem, I will
"disenroll" the Ethernet AM. No easy task, there is no "disenroll" directive.
So I edited my startup file to not install the shareable image:

sys$share:mcc_enet_am.exe

and the mcc_enroll_dir file to not inlude the command:

enroll mcc_enet_am mcc_enet_am

I then rebooted my system because I also had to change some system
parameters, ran the Lan autotopolgy program again, same error. So I
decided to make sure the Ethernet am was truly disabled:

test mcc 0 ethernet_am

and recieved test successfull.

Am I missing something here? Firstly why in the enroll file is it called
mcc_enet_am and in mcc itself ethernet_am? Secondly, how exactly does
one disable an enrolled am or fm?

Julie Ann

I don't believe you have to "disenroll" anything.
Having a module enrolled does not imply that it is running.

What you have to avoid is competition for the Ethernet device.
So long as you are not running any commands that call the station AM
(eg export polling for station), you should not have a conflict.

-- Erik

    Hi,
    
    	Thanks for the reply,
    
    		I have submitted a qar for the problem, because
    I don't believe that the contention for the Ethernet is the 
    problem I am seeing.
    
    Julie Ann