Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Netview\s+5\.1\.1\s+Discovery\s+problem\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Netview\s+5\.1\.1\s+Discovery\s+problem\s*$/: 4 ]

Total 4 documents matching your query.

1. Netview 5.1.1 Discovery problem (score: 1): Author: Raymond Tuggle <rtuggle AT BCBS-GA DOT COM>; Date: Sat, 25 Dec 1999 20:31:27 -0500; I have been running Netview 5.0 and the discovery worked fine. I just upgraded to release 5.1.1. I decided to clear the maps and start all over with discovering the network. I have run into a problem; /usr/local/webapp/mharc-adsm.org/html/nv-l/1999-12/msg00468.html (12,248 bytes)
2. Netview 5.1.1 Discovery problem (score: 1): Author: Leslie Clark <lclark AT US.IBM DOT COM>; Date: Mon, 27 Dec 1999 12:32:16 -0500; Raymond, this sort of thing could be caused by oddities in name resolution. At each maintenance level of Netview, it has come to rely more and more on name resolution when drawing the network. Does a; /usr/local/webapp/mharc-adsm.org/html/nv-l/1999-12/msg00470.html (14,785 bytes)
3. Netview 5.1.1 Discovery problem (score: 1): Author: Raymond Tuggle <rtuggle AT BCBS-GA DOT COM>; Date: Tue, 28 Dec 1999 23:44:37 -0500; Thanks for the info on how to set up AIX to look in the host file prior to looking into at the DNS. I have wanted to figure out how to do this, so I could set up each router with a better name assoic; /usr/local/webapp/mharc-adsm.org/html/nv-l/1999-12/msg00486.html (16,861 bytes)
4. Re: Netview 5.1.1 Discovery problem (score: 1): Author: Leslie Clark <lclark AT US.IBM DOT COM>; Date: Wed, 29 Dec 1999 09:38:32 -0500; Raymond, the business with Netview splitting interfaces across devices is almost certainly caused by the name resolution. I don't like it, but that's how it is behaving right now. If you delete one o; /usr/local/webapp/mharc-adsm.org/html/nv-l/1999-12/msg00488.html (17,738 bytes)

Current List: 1 - 4
Page: [1]