home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!know!cass.ma02.bull.com!think.com!sdd.hp.com!zaphod.mps.ohio-state.edu!darwin.sura.net!haven.umd.edu!decuac!pa.dec.com!e2big.mko.dec.com!nntpd.lkg.dec.com!narfvx.enet.dec.com!francini
- From: francini@narfvx.enet.dec.com (John Francini)
- Newsgroups: comp.os.vms
- Subject: Re: SYSTEM-F-NOLINKS, maximum network logical links exceeded
- Message-ID: <1992Nov22.174003.1130@nntpd.lkg.dec.com>
- Date: 22 Nov 92 17:35:06 GMT
- References: <22NOV92.01314219@moleng.ucsc.edu>
- Sender: usenet@nntpd.lkg.dec.com (USENET News System)
- Organization: Digital Equipment Corporation, Littleton, MA
- Lines: 26
-
-
- In article <22NOV92.01314219@moleng.ucsc.edu>, wipke@moleng.ucsc.edu writes...
- >NCP shows max links = 32, but SHOW NET shows zero links to the node
- >that gives this error upon SET HOST <anyothernode>. Is max links
- >for the network or for the node? Is there some other parameter tha
- >that causes this?
- >
- >wipke@secs.ucsc.edu
-
- The error is coming from the remote system, not the local one, if I
- understand your scenario correctly. In other words:
-
- You're logged onto NODEA::. You SET HOST to NODEB::. You get the
- SYSTEM-F-NOLINKS. NODEB::'s using the maximum number of links.
-
- NODEB's NCP max links parameter needs to be increased.
-
- HOWEVER, if NODEB:: is really a VAXcluster alias, then you need to look at
- the "Alias maximum links" parameter on EACH system in the cluster, as this
- value is separately managed. When every system in the cluster has used up
- all of its cluster alias links, then the NOLINKS error will be generated.
-
- John Francini
- PATHWORKS for VMS
- Digital Equipment Corporation
- francini@narfvx.enet.dec.com
-