| Hi,
I have the same problem of .0, the PSL of the accvio is the same,
and it happens doing the IP autoconfig.
It is a Vaxstation 4000-60 104Mb memory with mcc 1.2-7 .
Any news about this problem or workaround are greatly appreciated.
Ciao,
Andrea Lasagna, NOC Italy
|
|
Hello Andrea,
What is the scope of the network search you were attempting when
you encountered the accvio? Were you looking for routers only,
or for hosts too?
Could you please post here the .cf file you were using when
you saw the accvio?
Thanks,
Ulla Figwer
P.S. The following is a summary of the answer to QAR #2875,
mentioned in .1:
We neither support nor advise anyone to open the entire DEC
network (including all end nodes) for autodiscovery.
The tool is just not intended for this. There are limits
on the scope of search possible with IP Autoconfiguration.
If only routers are needed, do not specify -p and -h options.
-h option will try to contact all end nodes and the -p option
will aggressively persue this, thereby flooding the network.
These options may be used if the scope of the search is not
too large.
There is not justification for the accvio, however all testing
with reasonable search parameters has never uncovered an accvio.
It is not possible for us to test discovery of hosts and routers
in the whole DEC network. The scope is too large. If you
run into problems, try reducing the scope of the search and
perhaps running IP Autoconfiguration several times to cover
the entire network, one piece at a time.
|
| > What is the scope of the network search you were attempting when
> you encountered the accvio? Were you looking for routers only,
> or for hosts too?
Well, just an IP autoconfiguration of the customer network. It's a WAN
with about 100 end nodes and at least 10 Cisco routers.
I was looking for hosts too.
> Could you please post here the .cf file you were using when
> you saw the accvio?
yes attached there is the .cf
I encountered the accvio when the command procedure queries a
Cisco with the address of the subnet between the two LAN.
I'll try to draw the situation for explain it better:
lan a -----> __________________________________________ 151.96.16.0
| 151.96.16.201
-----------
| cisco a |
-----------
| 151.96.4.2
|
|
| 151.96.4.1
-----------
| cisco b |
-----------
| 151.96.72.1
lan b -----> ------------------------------------------ 151.96.72.0
the mcc node is in lan A, with ucx i loop succesful cisco A with 151.96.16.201
but not with 151.96.4.2 the error is :
%UCX-I-LOOPINACT, 151.96.4.2 does not respond
-SYSTEM-F-UNREACHABLE, remote node is not currently reachable
the same is when i loop 151.96.4.1 for cisco B, but it's ok if i loop
151.96.72.1 . So lan B is reachable and i can see its nodes but the
autoconfig when query the router with 151.96.4.1 goes in accvio.
I assume that it goes in accvio because of a problem on the setting of the
Cisco ports, i tried other Cisco's without problems, but i think that the
procedure should skip the router unreachable.
thanks in advance
Ciao,
Andrea Lasagna.
the .cf:
# ============================================================================
#
# DECmcc IP Autoconfiguration configuration file.
#
# This configuration file is used to specify DECmcc IP Autoconfiguration
# data collection parameters.
#
# ============================================================================
# ----------------------------------------------------------------------------
# The following 'gwy' commands give the starting point(s) for the
# configuration search. You should not need to change them, but you may wish
# to add distant routers if you have isolated "islands" of connectivity.
#
# Format:
#
# gwy <name-or-address>
gwy 151.96.16.118
gwy 151.96.16.164
gwy 151.96.16.202
gwy 151.96.16.201
gwy 151.96.16.131
gwy 151.96.16.116
gwy 151.96.16.69
gwy 151.96.16.74
gwy 151.96.16.117
gwy 151.96.16.164
gwy 151.96.16.152
# ----------------------------------------------------------------------------
# The following 'permit' commands define the limits of the search.
# The predefined one(s) limit the search to the IP networks that this
# host is connected to. You may need to add additional 'permit'
# commands if there are other networks that you need to probe.
# In addition, you may include 'deny' commands that will explicitly
# exclude groups of hosts. The arguments to both of these commands
# are an IP address, which is compared against addresses encountered
# in the search, and a bitmask, which determines which bits of the
# comparison are significant. The first matching address/mask pair
# encountered determines whether the search is continued from that
# point. If there is no match, the default is 'deny'.
#
# Format:
#
# permit <address> <mask>
# deny <address> <mask>
permit 151.96.0.0 255.255.0.0
permit 151.96.16.0 255.255.255.0
permit 151.96.72.0 255.255.255.0
permit 151.96.78.0 255.255.255.0
permit 151.96.84.0 255.255.255.0
permit 151.96.90.0 255.255.255.0
permit 151.96.24.0 255.255.255.0
permit 151.96.4.0 255.255.255.0
permit 151.96.2.0 255.255.255.0
permit 151.96.66.0 255.255.255.0
permit 151.96.34.0 255.255.255.0
permit 151.96.18.0 255.255.255.0
permit 151.96.26.0 255.255.255.0
permit 151.96.36.0 255.255.255.0
permit 151.96.28.0 255.255.255.0
permit 151.96.20.0 255.255.255.0
permit 151.96.22.0 255.255.255.0
# ----------------------------------------------------------------------------
# The following 'permit' command allows the search to investigate IP
# networks built using Digital's "Portal" IP-over-DECnet router.
# If you have Portals, leave this command in. If not, the command
# will not interfere with anything, so it may be left in.
#permit 132.157.0.0 255.255.0.0
# ----------------------------------------------------------------------------
# If you need to learn about hosts (in addition to routers), uncomment the
# "options -h" line, below.
#
# You also need to either:
#
# 1) give "host-permit" and "host-deny" commands, or
# 2) remove the "host-deny 0.0.0.0 0.0.0.0" line, below.
#
# These work just like the "permit" and "deny" commands, above. When
# querying a host, the "host-*" access list is checked first. If it
# does not have a match, then the router access list is checked. So, by
# default, the -h option will cause all hosts in the network to be queried.
# This is a lot of data, and is rarely what you want. Therefore, you will
# probably want to give "host-permit" commands for a few subnets, and
# "host-deny 0.0.0.0 0.0.0.0" to not find any other hosts.
#
# Format:
#
# host-permit <address> <mask>
# host-deny <address> <mask>
options -h
host-permit 151.96.72.0 255.255.255.0
host-permit 151.96.16.0 255.255.255.0
host-permit 151.96.66.0 255.255.255.0
host-permit 151.96.34.0 255.255.255.0
host-permit 151.96.18.0 255.255.255.0
host-permit 151.96.26.0 255.255.255.0
host-permit 151.96.36.0 255.255.255.0
host-permit 151.96.28.0 255.255.255.0
host-permit 151.96.20.0 255.255.255.0
host-permit 151.96.22.0 255.255.255.0
host-deny 0.0.0.0 0.0.0.0
# ----------------------------------------------------------------------------
# If you want to be really aggresive about finding hosts, you can use the -p
# option to force a "ping" (ICMP echo) of all of the possible hosts on a
# subnet. This should cause almost all hosts to be found, although
# DECmcc IP Autoconfiguration will take somewhat longer to complete.
# options -p
# ----------------------------------------------------------------------------
# By default, hosts that are discovered are placed in subdomains associated
# with the network they are connected to if there are 3 or more hosts on a
# network. Up to 40 hosts will be placed in each such domain. These
# parameters can be modified with the host-domainsize command.
#
# Format:
#
# host-domainsize <min> <max>
# ----------------------------------------------------------------------------
# The following 'community' commands define the SNMP "community name"
# that is used to grant permission to make queries of an SNMP agent.
# It is rather like a password. "public" is a common default that allows
# read-only access. If routers in your network use different community
# names, you must add them here. This command is similar to the 'permit'
# command above; the community string (first argument) is used if the
# address (second argument) and mask (third argument) match the host's
# address.
#
# If more than one address/mask pair in the list matches, each matching
# community name will be tried, from the beginning of the list. You should
# use the following order to minimize the amount of time spent waiting for
# requests with "bad" community names to time out:
#
# community names with specific (255.255.255.255) masks
# (e.g. for one router)
#
# common community names with general masks (0.0.0.0)
# (e.g. for "public")
#
# uncommon community names with general masks (0.0.0.0)
#
# If no community commands are given then the community name "public" will
# be used.
#
# Format:
#
# community <name> <address> <mask>
community public 0.0.0.0 0.0.0.0
# ----------------------------------------------------------------------------
# If you have point-to-point links that are not appearing properly in the
# map, you can manually configure point-to-point links here. The "pplink"
# command takes as its arguments the IP addresses (not hostnames) of the
# endpoints of a point-to-point link. It does not hurt to configure these,
# as the information will be ignored if enough information is available from
# SNMP.
#
# The exceptions list generated by DECmcc IP Autoconfiguration shows which
# endpoints of point-to-point links could not be resolved. Use it as a
# guide to see which links need to be manually configured.
#
# Format:
#
# pplink <address1> <address2>
# ----------------------------------------------------------------------------
# You can specify additional command-line options here.
#
# Useful ones are:
#
# -H Lay out backbone nets horizontally (default)
#
# -V Lay out backbone nets vertically rather than
# horizontally
#
# -S num Node spacing; the default is 6.0 nodes across
# the main map
#
# -r count seconds
#
# Specify the number of retransmission attempts and the
# retransmission timeout. If these numbrs are too low,
# some nodes may be missed. If they are too high,
# DECmcc IP Autoconfiguration will take a long time to
# finish. The defaults are 2 retries, with 10 second
# timeouts. It is reasonable to increase the
# timeout to 60 seconds. (e.g. -r 2 60)
#
# Format:
#
# options <option>...
options -H -r 2 60
|