| RE .1
Thanks Eric.
RE:.0
> 1. I use the DECmcc machine as an X-Window client and I open the
> mcc_iconic_map on another machine ( X-Window server ). While doing so
> the option in the pop-up menu which should activate the autoconfig
> doesn't work and give an error "CAN'T OPEN DISPLAY".
> Any reason ? Is it a known bug ?
Yes the bug is a know bug and has been taken care of in T1.2.4
You too can do the following:
1. Copy the file /usr/lib/X11/app-defaults/mcc_resource.dat into login dir.
2. Remove the string "-d 0:0" from the following lines:
mcc_pml.applications: DECmcc Command Line (FCL),DECmcc IP Autoconfiguration,DECmcc DECnet Phase IV Autoconfiguration
mcc_pml.applications.DECmcc Command Line (FCL).vms_command: CREATE/TERM/WAIT/WINDOW_ATTRIBUTES=(TITLE =\"DECmcc Command Line\",ICON_NAME=\"DECmcc FCL\") MANA/ENTER
mcc_pml.applications.DECmcc IP Autoconfiguration.vms_command: CREATE/TERM/WAIT/WINDOW_ATTRIBUTES=(TITLE =\"DECmcc IP Autoconfiguration\",ICON_NAME=\"DECmcc AC IP\") @mcc_common:mcc_ip_autoconfig.com
mcc_pml.applications.DECmcc DECnet Phase IV Autoconfiguration.vms_command: CREATE/TERM/WAIT/WINDOW_ATTRIBUTES=(TITLE =\"DECmcc Phase IV Autoconfiguration \",ICON_NAME=\"DECmcc AC DNA4\") @mcc_common:mcc_wan4_autoconfig.com
mcc_pml.applications.DECmcc Command Line (FCL).ultrix_command: /usr/bin/dxterm -e mcc_fcl
mcc_pml.applications.DECmcc IP Autoconfiguration.ultrix_command: /usr/bin/dxterm -e /usr/mcc/mcc_system/mcc_ip_autoconfig.sh
mcc_pml.applications.DECmcc DECnet Phase IV Autoconfiguration.ultrix_command: /usr/bin/dxterm -e /usr/mcc/mcc_system/mcc_wan4_autoconfig.sh
We had hard coded the dxterm to be opened on the sever side. The above change will
always open the terminal on the client side.
> 2. I activated the IP Autoconfiguration and the nodes drawn on the
> domain map has no connection between them. There was not any connection
> when I wrote the "pplink address1 address2" command on the
> configuration file. Any ideas what's wrong ?
In order to see connectivity you will have to either copy all the newly created
map files (i.e. ./dna4/<domain_name>/*.mcc_map ) to your login dir
or set the environmental variable MCC_MAPS to the directory in which the
maps are. Once you do an of the above you should be able to see the
connectivity. If you are still having any problem, let us know.
There is another nasty bug in DNA4 autoconfig in T1.2.3 kit.
Can you wait for T1.2.4? It has all of the known bugs fixed :-)
You can run IP autoconfig without any problems though!
Anil Navkal
|
| Hello,
Thanks for your answers.
.2
I was looking in the resource file for the "-d 0:0" string as you
wrote, but I didn't find such a string.
Concerning the connection between nodes in the map drawn by the
IP autoconfig. I don't know if that is what you ment cause you wrote
about the DNA4 autoconfig and not the IP. Anyhow I tried the MCC_MAPS
variable and didn't help.
If you have any other thing that may help it will sure be nice. I need
this features as soon as possible. BTW, when is T1.2.4 intended to be
announced ?
Thanks again,
Ido
|
| Sorry I took so long to get back to you. I am also confused as to
why you don't see the string
-d 0:0
in your /usr/lib/X11/app-defaults/mcc_resource.dat file.
Can you post a copy of this file here so I too can see
how a dxterm is created?
Re.
Concerning the connection between nodes in the map
drawn by the IP autoconfig. I don't know if that
is what you ment cause you wrote about the DNA4
autoconfig and not the IP. Anyhow I tried the
MCC_MAPS variable and didn't help.
You are right I did say DNA4 when I should have said IP
autoconfig. The map files you need to copy are in your
<~/IP/<domain_name>/*.mcc_map > directory if you started
the IP utility from IMPM. If you started it from the
command line then the map files are in the following dir
<dire-spec-of-wherever-you-were-when-you-invoked-autoconfig>
/IP/<domain_name>/*.mcc_maps
Can you see any map files? Can you post the "ls -l" of this dir
here?
RE:
BTW, when is T1.2.4 intended to be announced ?
Ans> Very very soon! We have corrected a number of problems
in the new kit.Please let us know if you still can not
use the Autoconfig Utility.
BTW: VMS kits are out. Can you try the autoconfig utility
while waiting for the Ultrix kit to come out?
Regards,
Anil Navkal
Project Leader DECmcc Autoconfig
<<< NOTED::DISK$NOTES4:[NOTES$LIBRARY_4OF5]MCC.NOTE;1 >>>
-< DECmcc Network Management Product Family >-
================================================================================
Note 1900.3 Autoconfig_ip questions ? 3 of 3
IDOWS::IDO "Ido Ganor, SWS Israel, TAV02::IDO, @ISO" 21 lines 10-DEC-1991 14:19
-< No success ... >-
--------------------------------------------------------------------------------
Hello,
Thanks for your answers.
.2
I was looking in the resource file for the "-d 0:0" string as you
wrote, but I didn't find such a string.
If you have any other thing that may help it will sure be nice. I need
this features as soon as possible. BTW, when is T1.2.4 intended to be
announced ?
Thanks again,
Ido
<<< Note 1900.2 by TOOK::NAVKAL >>>
-< If you can not wait till T1.2.4 .... >-
RE .1
Thanks Eric.
RE:.0
> 1. I use the DECmcc machine as an X-Window client and I open the
> mcc_iconic_map on another machine ( X-Window server ). While doing so
> the option in the pop-up menu which should activate the autoconfig
> doesn't work and give an error "CAN'T OPEN DISPLAY".
> Any reason ? Is it a known bug ?
Yes the bug is a know bug and has been taken care of in T1.2.4
You too can do the following:
1. Copy the file /usr/lib/X11/app-defaults/mcc_resource.dat into login dir.
2. Remove the string "-d 0:0" from the following lines:
mcc_pml.applications: DECmcc Command Line (FCL),DECmcc IP Autoconfiguration,DECmcc DECnet Phase IV Autoconfiguration
mcc_pml.applications.DECmcc Command Line (FCL).vms_command: CREATE/TERM/WAIT/WINDOW_ATTRIBUTES=(TITLE =\"DECmcc Command Line\",ICON_NAME=\"DECmcc FCL\") MANA/ENTER
mcc_pml.applications.DECmcc IP Autoconfiguration.vms_command: CREATE/TERM/WAIT/WINDOW_ATTRIBUTES=(TITLE =\"DECmcc IP Autoconfiguration\",ICON_NAME=\"DECmcc AC IP\") @mcc_common:mcc_ip_autoconfig.com
mcc_pml.applications.DECmcc DECnet Phase IV Autoconfiguration.vms_command: CREATE/TERM/WAIT/WINDOW_ATTRIBUTES=(TITLE =\"DECmcc Phase IV Autoconfiguration \",ICON_NAME=\"DECmcc AC DNA4\") @mcc_common:mcc_wan4_autoconfig.com
mcc_pml.applications.DECmcc Command Line (FCL).ultrix_command: /usr/bin/dxterm -e mcc_fcl
mcc_pml.applications.DECmcc IP Autoconfiguration.ultrix_command: /usr/bin/dxterm -e /usr/mcc/mcc_system/mcc_ip_autoconfig.sh
mcc_pml.applications.DECmcc DECnet Phase IV Autoconfiguration.ultrix_command: /usr/bin/dxterm -e /usr/mcc/mcc_system/mcc_wan4_autoconfig.sh
We had hard coded the dxterm to be opened on the sever side. The above change will
always open the terminal on the client side.
> 2. I activated the IP Autoconfiguration and the nodes drawn on the
> domain map has no connection between them. There was not any connection
> when I wrote the "pplink address1 address2" command on the
> configuration file. Any ideas what's wrong ?
In order to see connectivity you will have to either copy all the newly created
map files (i.e. ./dna4/<domain_name>/*.mcc_map ) to your login dir
or set the environmental variable MCC_MAPS to the directory in which the
maps are. Once you do an of the above you should be able to see the
connectivity. If you are still having any problem, let us know.
There is another nasty bug in DNA4 autoconfig in T1.2.3 kit.
Can you wait for T1.2.4? It has all of the known bugs fixed :-)
You can run IP autoconfig without any problems though!
Anil Navkal
|