Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Ethernet\s+port\s+on\s+Remote\s+Routers\?\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Ethernet\s+port\s+on\s+Remote\s+Routers\?\s*$/: 2 ]

Total 2 documents matching your query.

1. Ethernet port on Remote Routers? (score: 1): Author: Drew Wall <drwall AT TEKSYSTEMS DOT COM>; Date: Fri, 5 Feb 1999 16:55:27 -0500; Has anyone run into this problem? Solaris 2.5.1 NV 5.1 Only the serial ports on the customer's remote routers (Cisco) are being discovered. The ethernet port on each router is identified, but labeled; /usr/local/webapp/mharc-adsm.org/html/nv-l/1999-02/msg00135.html (11,418 bytes)
2. Re: Ethernet port on Remote Routers? (score: 1): Author: James Shanks <James_Shanks AT TIVOLI DOT COM>; Date: Fri, 5 Feb 1999 17:14:38 -0500; I am not certain what question you are asking here. The default discovery behavior for NetView is, was, and always has been, to reach the next network and stop. The next network will be unmanaged. Yo; /usr/local/webapp/mharc-adsm.org/html/nv-l/1999-02/msg00136.html (12,321 bytes)

Current List: 1 - 2
Page: [1]