QUESTION:
The customer is trying to configure ethernet using 10BaseT & Ethernet
V2. The following is the customer's configuration:
HARDWARE:
RS/6000 -> ETHERNET ADAPTER -> AUI -> 10BASET TRANSCEIVER -> RJ45 -> HUB
(IEEE 802.3)
SOFTWARE:
AIX 3.2 / NETWARE / TCPIP (EN0 INTERFACE)
QUESTIONS:
1. What RS/6000 models support 10BaseT?
2. The customer needs to use Ethernet_2 frame type (V2). Is en0 the
correct interface?
3. If the 10BaseT Transceiver has IEEE 802.3 on it, can it be used
with the Standard Ethernet Interface (en0)?
4. The system can ping itself, but it can not communicate with other
systems on the network. Do you have any suggestions?
---------- ---------- ---------- --------- ---------- ----------
A: I will answer your questions in the order that they were asked.
1) All RISC System/6000 models support 10baseT ethernet with the proper
hardware. Depending on the type of ethernet adapter that comes with the
RISC System/6000 (see list below), you may need a 10baseT transceiver.
High-Performance Ethernet Adapter (FC 2980)
- 10base5 standard
- 10base2 standard
- 10baseT use 10baset transceiver FC 4224, #02G7429
Integrated Ethernet 250
- 10base5 standard
- 10base2 use 10base2 transceiver FC 4223
- 10baseT standard use converter that ships with system, #51G8479
Integrated Ethernet M20, M20A, 220, 230
- 10base5 standard
- 10base2 use 10base2 transceiver FC 4223, #02G7435
- 10baseT use 10baseT transceiver FC 4224, #02G7429
Integrated Ethernet 340, 350, 360, 370, 55L
- 10base5 standard with FC 4221 (specify code #9000)
- 10base2 standard with FC 4221 (specify code #9000)
- 10baseT use FC 4222, card that replaces 4221 (specify code #9001)
- DO NOT use FC4221 with a 10baseT transceiver
2) Yes, en0 is the correct interface for standard V2 ethernet.
3) The 10baseT transceiver can be used with standard ethernet (en0) or
802.3 (et0).
4) Usually, this type of problem is caused by either name resolution or
routing. Try the following suggestions:
Use the command 'netstat -r' to look at the routing tables. Ensure that
the system has a route to the other machines on the network.
Are you pinging by hostname or IP address? If you can ping by IP
address but not by hostname, then the problem is name resolution.
Ensure that the interface is configured for the proper frame type,
either ethernet V2 or 802.3 (use the command 'netstat -i' to list
interfaces).
If none of the above suggestions help, please respond back with more
information and I will be glad to assist you further.
---------- ---------- ---------- --------- ---------- ----------
This item was created from library item Q654412 CQBKD
Additional search words:
COMMUNICATIO CONFIG CONFIGURATIO CONFIGURATOR CONFIGURE CQBKD
ETHERNET HOWTO IX MAR94 OZNEW RISCSYSTEM RISCTCP SOFTWARE TCPIP V2
10BASET
WWQA: ITEM: RTA000039805 ITEM: RTA000039805
Dated: 04/1996 Category: RISCTCP
This HTML file was generated 99/06/24~12:43:15
Comments or suggestions?
Contact us