[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| 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 |
5473.0. "ip autoconfiguration and accvio at starting point" by MUNICH::SCHWEMMER () Thu Aug 12 1993 12:16
Problem with IP Autoconfiguration in PNM 400 V1.3 under VMS V5.5-2.
IP Autoconfiguration ends in an ACCVIO during the phase
"querying host <ip-gateway>".
The IP-Gateway in this case is a CISCO-Box (AGS+ V8.3)
(It's possible to get information about this box over ICONIC MAP-Inter-
face. We can access all requested entitie's attributes, and also the
address translation tables.
The routing table is big, but we can access it.)
Customer's Polycenter-machine has the address:
140.181.97.33/NW-mask: 255.255.240.0
The IP-Gateway has the address:
140.181.96.1 /NW-mask: 255.255.240.0
In MCC_AUTOCONFIG_PREFIX.DAT he has specified the default values.
Domain name is .domain.gsi .
In the configuration-file he has specified:
gwy 140.181.96.1 (= cisco)
...
permit 140.181.96.0 255.255.240.0
permit 140.181.128.0 255.255.240.0
...
permit 132.157.0.0 255.255.0.0
...
host-deny 0.0.0.0. 0.0.0.0
...
host-domainsize 1 200
...
community public 0.0.0.0 0.0.0.0
community GSI-SNMP 140.181.96.1 255.255.255.255
...
options -r 2 30
*******************************************************************************
When he starts IP Autoconfiguration on his node, he gets the output:
Starting IP Autoconfiguration data collection ...
This may take a while...
Querying host 140.181.96.1 (cisco3)
%SYSTEM-F-ACCVIO, access violation, reason mask=04, virtual address=7Fe4b694, PC
=00099931, PSL=03C00000
%TRACE-F-TRACEBACK, symbolic stack dump follows
module name routine name line rel PC abs PC
00099931 00099931
0006BC47 0006BC47
NETWORKS net_new 4921 0000010D 00008FF5
NETWORKS net_make 4678 000000D5 00008969
SNMPMAP CleanUpAddrs 6344 00000428 000022F0
SNMPMAP add_if 6069 000002A1 00001D65
SNMPQUEUE query_done 4245 00000475 0000DD7D
SNMPQUEUE snmp_readone 3940 0000049B 0000D6B7
SNMPMAP dispatcher 5423 000001D7 0000127B
SNMPMAP main 5162 00000350 00000C24
Error: An error has occurred.
Warning: IP Autoconfiguration data files
may be corrupt.
IP Autoconfiguration exiting under error conditions.
*******************************************************************************
We were able to produce the same error on our inhouse-network. (Same reason
mask, same PC and PSL, same module and routine names were shown,
but different virtual address).
In our case we used an ULTRIX-machine as IP-gateway.
But, there's a little difference. We can ping our ip-gateway, but when we try
to take a look into this entity, e.g. into the Address-Translation-Table
(from Iconic Map Interface) we get an error window:
VMS Routine Error %NONAME-W-NOMSG, Message number 00000000
MCC Routine Error %MCC-E-ILVEOC, end of current constructor has been reached
(There's no special community name specified).
*******************************************************************************
Uuups, now I have 2 problems.
Could somebody please give me a hint how I can troubleshoot these 2 problems?
Thanks in advance.
With kind regards,
Mathilde Schwemmer,
Digital Service Center Munich
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 5473.1 | we can reproduce it | MUNICH::SCHWEMMER | | Fri Aug 13 1993 11:10 | 11 |
| I have some news.
We now were able to reproduce the same error with one of our inhouse-
machines (ULTRIX-IP-Gateway).
IP Autoconfiguration results in the mentioned ACCVIO, but we can access
all entity attributes over Iconic map.
Has somebody heard of this problem or can somebody give a hint?
Mathilde.
|