| Hi Scott,
I have tried to provide answers to all your questions. Look for
paras enclosed between � and �.
1) The ip config file no longer includes the strip command to remove the domain
information from the host names. Is there a reason for this?
�
Did it ever work? :-) srtip.com option was never supported under
MCC. Original code for Autoconfig came from MSU. Name space planning
under MSU is done with a very different philosophy. The default
behavior of Autoconfiguration will be to display all internet
names where they are know, or internet address on the map.
Since these names are also used to register the node, massaging the
internet name fro registration was not a choice we had. Perhaps if
such functionality is needed strongly from usability point of view,
let us know and we will put it on the wish list.
�
2) I have two snmp components (chipcom hub, and ds300). When the ip routine
queries these entities it finds out that there are more than 16 interfaces
and reports a message saying that if#17 dropped. Can this interface
restriction be changed?
�
This is the limitation of the tool. To make any change will require
significant design efforts. We will put your request on the wish
list for the next version though.
�
3) This problem occurs in both the ip and DECNET routines. In both cases the user
is prompted for the directory spec for the files to be placed in. The routines
provide a default of sys$sysroot:[sysmgr]. The user is then asked if this is
OK. If you answer no and try to put in any directory spec (including
sys$sysroot:[sysmgr]), an error is returned saying don't use a logical name.
Looking at the command procedures, the following section is causing the
problem:
MCC_IP_AUTOCONFIG.COM and MCC_WAN4_AUTOCONFIG.COM
$ IF F$TRNLNM("''_MCC_AC_TOP_DIR'") .NES. "" .OR. -
F$LOCATE("<", _MCC_AC_TOP_DIR) .EQ. F$LENGTH(_MCC_AC_TOP_DIR) .OR. -
F$LOCATE("[", _MCC_AC_TOP_DIR) .EQ. F$LENGTH(_MCC_AC_TOP_DIR)
$ THEN
$ echo ""
$ echo " Error: Error parsing directory name. Please do not specify"
$ echo " the directory using a logical name."
$ GOTO GET_DIR
$ ENDIF
It looks like if the second .OR. was changed to a .AND. that it may work, but I
haven't actually tried it yet.
�
Thank you for pinpointing the problem. I will enter this QAR and
we will certainly fix it. Hey there are advantages to shipping the
source code too!! :-)
�
I like the looks of the changes made. Getting the map file to the right spot and
creating the deregistration file are both nice.
�
Thanks for your nice words. Yes we did make significant change in
the user interface. What we did not make clear is that a ? will
give you a lot of on line help for all the questions being asked.
As usual we appreciate all you comments.
- Anil Navkal
�
|
|
Anil,
Thanks for the responses.
First, I added the strip command to the ip config file and it works anyway,
even though there are no comments in the procedure to that effect. I end up
with a domain map which only shows the simple ip name. I don't know if that will
cause adverse affects but so far everything is going fine.
I ran across the ? help as I was looking at the third problem. Looks good.
Thanks,
Scott
|
| > 2) I have two snmp components (chipcom hub, and ds300). When the ip routine
> queries these entities it finds out that there are more than 16 interfaces
> and reports a message saying that if#17 dropped. Can this interface
> restriction be changed?
> �
> This is the limitation of the tool. To make any change will require
> significant design efforts. We will put your request on the wish
> list for the next version though.
> �
Just for your information: the DECNIS 600 theoretically supports up to 56
interfaces. In fact, as that configuration would prevent a LAN circuit, the
likely maximum is 48. When we support channelised T1 that number will
probably go up significantly (maybe 384). The SNMP interfaces list is
likely to grow as "virtual" interfaces become common. I suggest a redesign
with a limit of 1000 in mind.
Graham
|