| 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 |
Notes 3456 and 3584 seems reported this problem, but I am not sure if
the context is the same.
I am running an autotopology on a site having several DECNIS. At the moment
all the network is still running Phase IV and the DECNIS have Phase IV
compatible addresses. The image crash reported below occurs when polling
the DECNIS which obviously do not understand NICE but only CMIP.
My questions :
a) Is the Phase IV autotopology limited to only nodes speaking NICE ?
b) If Yes, then do we have any means to learn a topology or limits the
search in order to avoid talking to CMIP machine ?
c) Even if we have some limitation in term of doing our autotopology today
when will it be possible :
- To avoid image crash when quering DECNIS ? (the way I perceive
the image crash. May be there are other reasons I am not aware of)
- To provide a work around in order to let customer build their
wan topology whatever management protocol they using (CMIP/NICE).
d) Do we have the same problem when doing autotopology for LAN (spanning
tree) if the autoconfigure program for LAN is not speaking CMIP to query
spanning tree characteristics on a DECnis being configured with a child
NODE5 entity BRIDGE. I need some infos to clarify these functions in
such heterogeneous protocol management environment (for the autotopology
functions).
Michel
===========================================================================
Include of the image crash
--------------------------
Please choose one of the following configurations:
[1] All DECnet Phase IV nodes
[2] All DECnet Phase IV nodes in selected area(s)
[3] All DECnet Phase IV nodes in a LAN
[4] All level 1 and level 2 DECnet Phase IV routers
[5] ALL level 1 and level 2 DECnet Phase IV routers in selected
area(s)
[6] ALL level 1 and level 2 DECnet Phase IV routers on the LAN
[7] All level 2 DECnet Phase IV routers
[8] All level 2 DECnet Phase IV routers in selected area(s)
[9] All level 2 DECnet Phase IV routers in the LAN
o Enter option [2]: 5
Please choose a search method:
[1] Search by adjacency
[2] Search by address
o Enter option [1]: 1
Please specify starting nodes for the search.
Enter one node at a time.
o Starting node [1.600]:
Press RETURN to end the list.
o Additional starting node(s) [1.600]:
Please specify areas to include in the search.
Enter one area at a time.
o Area to include [1]:
Press RETURN to end the list.
o Additional area to include [1]:
Please specify areas to exclude from the search.
Enter one area at a time.
o Area to exclude:
DECnet Phase IV Autoconfiguration starting data collection ...
This may take a while...
Results from 1.600, 1 circuits, 1 adjacencies, Q size 1...
Time out while expecting data from node 1.502
Time out while expecting data from node 1.502
Node 1.502 did not respond
Results from 1.502, 0 circuits, 0 adjacencies, Q size 0...
Kill process error
DECnet Phase IV Autoconfiguration data collection completed.
DECnet Phase IV Autoconfiguration starting data formatting ...
DECnet Phase IV Autoconfiguration data formatting completed.
DECnet Phase IV Autoconfiguration generating DECmc Registration
and Map files.
%SYSTEM-F-FLTDIV_F, arithmetic fault, floating divide by zero at PC=000022EF, P
L=03C00004
%TRACE-F-TRACEBACK, symbolic stack dump follows
module name routine name line rel PC abs PC
MCC_AC_MAP main 7034 000020AF 000022EF
Error: An error has occurred.
Warning: DECnet Phase IV Autoconfiguration data files
may be corrupt.
DECnet Phase IV Autoconfiguration exiting under error conditions.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 4062.1 | DECnis wasn't considered | TOOK::MATTHEWS | Thu Nov 12 1992 13:25 | 13 | |
DNA4 auto-topology is exactly that. It was designed to use DNA4's
Nice protocol and supports the classical DNA4 networks. DECnis is
fairly new and I am pretty sure that the auto-topology work was
unaware of DECnis and the various stages of migration from DNA4
to DNA5.
Auto-topology has no mechanism that I know of to filter out specific
node addresses so that they are not attempted. You also need to be
aware that both DNA4 and DNA5 AMs depend upon devices correctly
implementing the protocol version negotiation and NOT ALL devices
have correctly implemented it.
wally
| |||||
| 4062.2 | Some answeres | TOOK::NAVKAL | Thu Nov 12 1992 14:23 | 142 | |
Hi Michel,
Let me see if I can answer your questions with equal precision!
a) Is the Phase IV autotopology limited to only nodes speaking NICE ?
> Yes.
b) If Yes, then do we have any means to learn a topology or limits the
search in order to avoid talking to CMIP machine ?
> In general the code was not "designed to crash :-)" if it came across
> m/cs talking CMIP. The utility consists of 3 images. They are as follows:
>
> MCC_AC_WAN4_COLLECTOR.EXE ! This one collects the data
> MCC_AC_WAN4_MAPPER.EXE ! This one will process the data to define connectivity
> MCC_AC_MAP.EXE ! This one will produce the map, generate the
> ! script that registers entities found etc.
> The crash you see is in the last image. This is due to the fact that
> we missed certain error handling paths when nodes return an invalid
> string for the node names as a response to a nice message. I have not
> spend time to find out why we are getting invalid string to begin with.
> In any case the point I wanted to make was that the discovery part does not
> barf when a CMIP node is encountered. And yes I do understand that
> from usere's point of view, this explanation is not acceptable.
>
> I hope that we get a chance to fix this problem problem before
next version goes out the door.
c) Even if we have some limitation in term of doing our autotopology today
when will it be possible :
- To avoid image crash when querying DECNIS ? (the way I perceive
the image crash. May be there are other reasons I am not aware of)
> See my answer above.
- To provide a work around in order to let customer build their
wan topology whatever management protocol they using (CMIP/NICE).
> As Wally has said in .1 there are no plans what so ever to support
> CMIP in near term.
d) Do we have the same problem when doing autotopology for LAN (spanning
tree) if the autoconfigure program for LAN is not speaking CMIP to query
spanning tree characteristics on a DECnis being configured with a child
NODE5 entity BRIDGE. I need some infos to clarify these functions in
such heterogeneous protocol management environment (for the autotopology
functions).
> Folks from LAN BU will be able to answer this question.
Michel
===========================================================================
Include of the image crash
--------------------------
Please choose one of the following configurations:
[1] All DECnet Phase IV nodes
[2] All DECnet Phase IV nodes in selected area(s)
[3] All DECnet Phase IV nodes in a LAN
[4] All level 1 and level 2 DECnet Phase IV routers
[5] ALL level 1 and level 2 DECnet Phase IV routers in selected
area(s)
[6] ALL level 1 and level 2 DECnet Phase IV routers on the LAN
[7] All level 2 DECnet Phase IV routers
[8] All level 2 DECnet Phase IV routers in selected area(s)
[9] All level 2 DECnet Phase IV routers in the LAN
o Enter option [2]: 5
Please choose a search method:
[1] Search by adjacency
[2] Search by address
o Enter option [1]: 1
Please specify starting nodes for the search.
Enter one node at a time.
o Starting node [1.600]:
Press RETURN to end the list.
o Additional starting node(s) [1.600]:
Please specify areas to include in the search.
Enter one area at a time.
o Area to include [1]:
Press RETURN to end the list.
o Additional area to include [1]:
Please specify areas to exclude from the search.
Enter one area at a time.
o Area to exclude:
DECnet Phase IV Autoconfiguration starting data collection ...
This may take a while...
Results from 1.600, 1 circuits, 1 adjacencies, Q size 1...
Time out while expecting data from node 1.502
Time out while expecting data from node 1.502
Node 1.502 did not respond
Results from 1.502, 0 circuits, 0 adjacencies, Q size 0...
Kill process error
DECnet Phase IV Autoconfiguration data collection completed.
DECnet Phase IV Autoconfiguration starting data formatting ...
DECnet Phase IV Autoconfiguration data formatting completed.
DECnet Phase IV Autoconfiguration generating DECmc Registration
and Map files.
%SYSTEM-F-FLTDIV_F, arithmetic fault, floating divide by zero at PC=000022EF, P
L=03C00004
%TRACE-F-TRACEBACK, symbolic stack dump follows
module name routine name line rel PC abs PC
MCC_AC_MAP main 7034 000020AF 000022EF
Error: An error has occurred.
Warning: DECnet Phase IV Autoconfiguration data files
may be corrupt.
DECnet Phase IV Autoconfiguration exiting under error conditions.
| |||||
| 4062.3 | WANrouters as well | MARVIN::COBB | Graham R. Cobb (DECNIS development), REO2-G/G9, 830-3917 | Tue Nov 17 1992 09:37 | 10 |
Note that this Phase IV autotopology problem is not restricted to DECNIS. It also applies to all the WANrouter products (90/100/150/250/500). (I know that Wally and the autotopology team are well aware of that but some readers may not be). BRIDGE autotopology has a similar sort of problem -- it uses RBMS which the DECNIS products don't implement. However, in that case, the solution will probably eventually be to use SNMP. Graham | |||||