[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

3455.0. "can't register fddi bridge or concentrator ?" by ZPOVC::SINSPS () Wed Jul 29 1992 07:27

Hi, I've encountered problem in registering FDDI bridge or concentrator. The
configuration of my customer is illustrated below :-

	    "A"							    "B"
	+---------+		+------------+  		+---------+
	|DECbridge|		|Concentrator|	      fddi	|DECbridge|
	|  610	  |		|    500     |------------------|   610	  |
	+---------+		+------------+			+---------+
	 |   |	 |		       |			 |   |	 |
    -----+   |	 		       | fddi controller
	     |			+------------+
	     | ethernet 	|     VAX    |
	     | interface	|     6620   |
	     |			+------------+
	     |			       | ethernet controller
	     |			       |
    +-----------------------------------------------------------------------+
		E T H E R N E T			C A B L E	

Of the 2 bridges above, I managed to register bridge "A" only. Whenever, I 
tried to register bridge "B" or the concentrator, I received 'CANNOT 
COMMUNICATE WITH TARGET'. DECmcc 1.1 and ELM 1.0 are running on the VAX6620
with VMS 5.5 installed. What could be the possible cause of the problem ? Could
it be that bridge "A" was registered successfully because MCC on VAX6620 knew
how to communicate through its ethernet controller only; however it could not 
communicate with the Concentrator or bridge "B" through its fddi controller?
Would upgrade to DECmcc 1.2 & ELM 1.2 help ? Please advise. Many thanks in 
advance.

Eng Huat.

T.R	Title	User	Personal Name	Date	Lines
3455.1		SLINK::CHILDS	Practice passive aggression.	`Wed Jul 29 1992 11:51`	5
	My guess is that MCC is only seeing the ethernet port on your machine. Could you please try this command: MCC> show mcc 0 bridge_am available ports
3455.2	Try via port.	QUIVER::HAROKOPUS		`Wed Jul 29 1992 14:02`	10
	The MCC EA routines do not officially support access to devices from the management station directly through an FDDI controller. However, doing a register bridge <name> addr=<bridge addr>, via port=<fddi port name> may work for you. Regards, Bob
3455.3	Good suggestions, will try them out.	ZPOVC::SINSPS		`Wed Jul 29 1992 22:15`	5
	Good suggestions from both of you. Will keep you posted of the outcome. Thanks, Eng Huat.
3455.4	problem solved with 1.2	ZPOVC::SINSPS		`Thu Aug 13 1992 07:28`	5
	Yesterday, I upgraded both the BMS and ELM to 1.2 and I was able to register the concentrator and both bridges. Thanks, Eng Huat.
3455.5	Need to use FDDI not Ethernet	ENUF::CAUDILL	Kelly - NaCM Tech Support - 264-3320	`Tue Nov 17 1992 16:23`	9
	First off, how do I change MCC to know that FXA0: is my LAN device rather than EXA0:? The machine - a VAX 7000/610 - has an ethernet controller but it isn't hooked up to anything. It's network connection is the FDDI. I used via port=fxa0: on the register command and was able to register the concentrator. But when I do a show, I get "management Protocol error" I'm running BMS V1.2.3 on VMS V5.5-2.
3455.6	Did you specify VIA PORT on the SHOW?	CHRISB::BRIENEN	Network Management Applications!	`Tue Nov 17 1992 16:43`	0
3455.7	How do I make it the default?	ENUF::CAUDILL	Kelly - NaCM Tech Support - 264-3320	`Tue Nov 17 1992 17:16`	7
	Now why didn't I think of that!?? So... How do I make it the default? How do I do it from the iconic map?
3455.8		VCSESU::WADE	Bill Wade, VAXc Systems & Support Eng	`Wed Nov 18 1992 08:52`	16
	re. .7 To make it the default - FCL - Use default qualifier via port fxa0: IMPM Operations > Operation qualifiers > via port But, unless it has changed for 1.2.3, there is limited functionality with the via port qualifier. A biggie is alarms can't be set to poll with the via port. Bill
3455.9	How can save the default?	ENUF::CAUDILL	Kelly - NaCM Tech Support - 264-3320	`Wed Nov 18 1992 09:40`	7
	I found the operation qualifier... pull down. Thanks for the info on the use default... command. Is there any way I can get this to happen automatically? No one on this system is ever going to use EXA0 because it isn't hooked up. So, at present, it seems like everyone who ever uses MCC is going to have to change this every time they start MCC - very annoying.
3455.10	for VMS, an init file	TOOK::KOHLS	Ruth Kohls	`Thu Nov 19 1992 09:48`	6
	-< How can save the default? >- For VMS, make a command file with the "use default" command in it and define a logical, MCC_INIT, to point to the command file. The "DECmcc Use" Manual describes this in the Customization section. Ruth K.
3455.11		VCSESU::WADE	Bill Wade, VAXc Systems & Support Eng	`Thu Nov 19 1992 14:06`	1
	Can not do for IMPM.