Conference azur::mcc

1020.0. "DNS problem after FDDI AM(mako) installation" by ZPOVC::RAMARAJ () Thu May 16 1991 09:42

I've a system with BMS V1.1, TSAM FT, TRANSLAN FT, FDA and SNMP V1.0.  They
all running fine.

This same system is the DNS server.
VMS 5.4-1
Licenses include DECMCC-EMS, DECMCC-BMS.

I installed the MAKO products, that contains the CONC AM and the Enhanced 
Bridge AM.  Installation went through fine without any problem.

When I go into MCC and try to look at any entity(node4, snmp, terminal server, 
Translan, bridge (LANBRIDGE100, LANBRIDGE150 and LANBRIDGE200) or register any 
new entity, it works fine, just like before.

The moment I try to register a DC500 or DC500, it does not work.  It times out
after sometime, saying "Unable to communicate with the DNS server" or "Timeout
in communicating with DNS server".
After this any command I try to do with the global entity bridge fails, with
the same error.  Even if I try to look at the LANbridge that was ok before.

Other AM are ok.

If I try to shutdown DNS, with DNS$stop, it also gets stuck, with a timeout
error, unable to communicate with DNS server.
I had to stop/id=xxx, the 3 DNS processes, and do a DNS$STOP.

Then when I restart, with DNS$startup, everything is fine with the bridge; I
can look at the LANbridge 150 as before.

I try registering the DC500 or DB500 again, its back to the same problem 
again.

Anyone can give a clue as to what is happening or how to trace the problem.

Raj
SWS Singapore

    
    Re: .0
    
    Please read topic # 571.* for some info on "Unable to communicate ..."
    
    There are many topics in NOTED::DNS and NOTED::DNS_PROGRAMMER notes 
    conference on "Unable to commun ..." and "DNS$_Nocommunication".