[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

1278.0. "Vitalink-cannont communicate" by TROOA::GILBERT () Tue Jul 23 1991 19:09

    I have just installed a loaner version of the Vitalink AM .  It even
    came with a USE manual!  Anyway, when I go to register the first
    Vitalink bridge I get the following:
    
    MCC> REGISTER TRANSLAN O021 ADDRESS=08-00-7C-00-48-31
    
    TRANSLAN JLL_NS:.O021
    AT 23-JUL-1991 16:00:39
    
    The requested operation cannot be completed
                MCC Unhandled Service Reply = Cannot communicate with
    target
    
    
    I did a SET WATCH FILE/CLASS=ALL to observe file activity and it is
    running MCC_TRANSLAN_AM prior to getting the message.  There is also a
    many-second delay before it gives the error message.
    
    The troubleshooting guide warns of making sure the bridge is there. 
    The console of the bridge is accessible via VAXcluster Console and I
    can do lots of commands on it.  However, I have no way that I know of
    to SET HOST or run something just to see if I can get at it from my MCC
    station.
    
    I have tried a command I saw in the notes file (MCC> SHOW BRIDGE
    ethernet-address ALL IDENT) but I got the same message.
    
    Is there a checklist I can go through to determine whether MCC can see
    the bridge and , if so, why it can't talk to it enough to do the
    REGISTER.  I am new to bridges and DECmcc (not to mention DNS) so all
    help will be valuable.
    
    Thanks in advance,
    
    Peter

T.R	Title	User	Personal Name	Date	Lines
1278.1	Check your LAN connection; Try a STATION command on it	MCDOUG::MCPHERSON	i'm only 5 foot one...	`Tue Jul 23 1991 19:41`	21
	The delay is becuase the AM code is trying over and over to get to the Translan, with some delay. There is a timeout value that basically says how long the AM should wait before giving up. CANNOT COMMUNICTATE WITH TARGET means that you couldn't make ethernet connect- ivity with the box from your DECmcc system. You're sure your DECmcc system is on the same LAN, right? If you want to eliminate whether or not it's the TRANSLAN AM, try REGISTERing the TRANSLAN as a STATION and see what happens. e.g. MCC> REGISTER STATION translan_station 008-00-7C-00-48-31 If that fails, check one more time to make sure that you have direct ethernet connectivity to the Translan (no routers between you...) and if you still have the same problem report back here with detailed information about the configuration - Translan types - Translan software version on each - Translan net configuration (esp with respect to the DECmcc system)
1278.2	REGISTER STATION worked	TROOA::GILBERT		`Wed Jul 24 1991 13:29`	14
	Thanks for the help. I have asked the customer to verify the direct access aspect to the point where I am becoming a bother. However, I did try the register station command and, after almost the same delay, it registered successfully. I attribute the delay this time to the slowness of DNS as well as having made a connection to the station. So, where do I go from here? Should I be trying to modify the timers within the TRANSLAN AM or do I have a bigger problem here? If the TRANSLAN timers are respectable, I must have a network problem. If not, can I increase the timers? Thanks again, Peter
1278.3	Still need some environmental/configuartion information	MCDOUG::MCPHERSON	i'm only 5 foot one...	`Wed Jul 24 1991 14:41`	31
	If you were able to register the TRanslan as a STATION, then your have local Ethernet connectivity to the Translan. If the Translan is busy then it will drop management requests on the floor. Once again: please report in here with some environmental information: Is the Translan busy? What type of Translan? What Software version is the Translan running? What how many serial lines on the Translan? what speed for each line? how busy is each line? Capture output from the following commands and post it here as well. MCC> SHOW STATION 08-00-7C-00-48-31 ALL ATTRIBUTES MCC> SHOW TRANSLAN 08-00-7C-00-48-31 ALL ATTRIBUTES If the Translan still doesn't respond, then exit MCC, and at DCL $ DEFINE MCC_TRANSLAN_AM_LOG 26 then start mcc again and do this: MCC> SHOW TRANSLAN 08-00-7C-00-48-31 ALL ATTRIBUTES Post the full resulting output here (or mail it to me) and we'll see if we can figure out what's going on
1278.4	Spanning Tree=False was the problem	TROOA::GILBERT		`Thu Aug 01 1991 18:01`	11
	After much confusion with some help from Doug MacPherson I found that the customer had set the Spanning Tree variable to False on Group 0, which contains the Ethernet port. Setting this variable also sets TX/RX Management messages to False, presumably telling the Vitalink bridge to ignore everything I was sending it. Some documented bridge settings would have helped. The Vitalink AM book says nothing about actual bridge parameter settings, only those on the VAX and DECmcc side. Peter