[Help] - 2 VM solaris pingable Post: 302538630

5 More Discussions You Might Find Interesting

1. IP Networking

Serious un-pingable stumper of a problem...

I have been busting my head over a network issue at work recently. I believe the problem to be in the L2 domain, but "the powers that be" believe that it looks more like a server port related problem. And the biggest problem of all is that EVERYBODY in the Engineering Department uses this...

2. Shell Programming and Scripting

need to check whether a sever is pingable or not inside the script

Hi, need to write a script which will check number of ip address are able to ping or not ..

3. Solaris

Unable to login using ssh,telnet onto my solaris machine with solaris 10 installed

Hi, I am unable to login into my terminal hosting Solaris 10 and get the below error message "Server refused to allocate pty ld.so.1: sh: fatal: libc.so.1: open failed: No such file or directory " Is there anyways i can get into my machine and what kind of changes are required to be...

4. UNIX for Dummies Questions & Answers

host not booting, but is pingable

hi there. im having a problem with a host at the moment, i can ping the host and responds with host is alive. i cannot telnet, rsh or anything else to it... it tells me connection refused. when i run a ckport on it i get answers from : *** successful - smtp *** successful - sunrpc ...

5. Shell Programming and Scripting

validating(pingable or not) remote ip address in shell script

i need to verify whether the ip adress given as input to the shell script is pingable or not... that is whether the ip is alive and responding.. ping $ip_adress the above wont work in script because the execution is continuous... so the shell script keeps will dwell in this pinging process......

LEARN ABOUT NETBSD

de

DE(4)							   BSD Kernel Interfaces Manual 						     DE(4)

NAME

     de -- DECchip 21040, 21140, 21141, 21142, and 21143 PCI Ethernet interface driver

SYNOPSIS

     de* at pci? dev ? function ?

     Configuration of PHYs may also be necessary.  See mii(4).

DESCRIPTION

     The de driver supports Ethernet and Fast Ethernet interfaces based on the Digital Equipment Corporation DECchip 21040, 21140, 21141, 21142,
     and 21143 model controllers for PCI bus.

     21040   10BASE-T and AUI/BNC
     21140   10BASE-T and 100BASE-TX
     21141   10BASE-T and 100BASE-TX
     21142   10BASE-T and 100BASE-TX
     21143   10BASE-T and 100BASE-TX

     Supported Network Interface Cards (NIC) include, but are not limited to:

     Accton EN1207i
     Cogent EM100
     Asante AsanteFAST
     DEC DE435
     DEC DE450
     DEC DE500
     SMC 9332
     Znyx NetBlaster ZX340 series (345, 348, 346)

     Generally, if the NIC is for PCI bus, and the major controller chip has the DIGITAL logo on it, with one of the model numbers above, the de
     driver should recognize and control it.  Beware, however, that many NIC manufacturers change the Ethernet controller chip without changing
     the product model number, and a physical inspection of the NIC, or a probe of the NIC with a PCI diagnostic tool is the only way to tell if a
     real DEC TULIP controller is present.

     Multi-port interfaces are typically configured as a PCI-PCI bridge with multiple de instances on the PCI bus on the other side of the bridge.

     DEC sold its semiconductor division to Intel.  In addition, there are many "knock-offs" of the DEC TULIP Ethernet controller chips; NICs
     based on these chips are handled by the tlp(4) driver.

     This de driver should not be confused with the NetBSD VAX de driver for the DEC DEUNA/DELUA Ethernet controller for UniBus.

SEE ALSO

     ifmedia(4), intro(4), mii(4), pci(4), tlp(4), ifconfig(8)

     http://www.adaptec.com/, http://www.asante.com/, http://www.smc.com/, http://www.znyx.com/

HISTORY

     The de driver first appeared in NetBSD 1.1

AUTHORS

     Matt Thomas <matt@3am-software.com>.

BSD
								 February 11, 2000							       BSD