|
|
 |
|
| | |
|
Auto-negotiation
Cabling
Design options
Features
| »
| Q: What are the features of the HP ProCurve 10/100 Hub 12 (product number J3294A), 12m (product number J3288A) , 24 (product number J3295A), and 24m (product number J3289A)? |
|
| »
| Q: Do I need an external switch connected to the HP ProCurve 10/100 Hub 12, 12m, 24, or 24m so that my 10Mbps clients can talk to a 100Mbps server? |
|
| »
| Q: What is the MDI/MDI-X button used for on the HP ProCurve 10/100 Hubs? |
|
| »
| Q: Do the HP ProCurve 10/100 Hub 12, 12m, 24, and 24m support full-duplex? |
|
| »
| Q: Do the HP ProCurve 10/100 Hub 12, 12m, 24, and 24m support 802.1Q/802.1p? |
|
|
| |
| | |
|
|
|
| |
|
|
Q: What are the features of the HP ProCurve 10/100 Hub 12 (product number J3294A), 12m (product number J3288A), 24 (product number J3295A), and 24m (product number J3289A)?
The HP ProCurve 10/100 hubs are low-cost, multiport, dual-speed (10 and 100 Mbps) repeaters that can be used to build high-performance workgroup networks. These hubs are autosensing devices that provide the flexibility of adjusting to different network connection speed settings. The hub ports always operate at half-duplex. The features of these hubs includes:
- 12 or 24 Ethernet 10/100Base-TX ports with RJ-45 connectors.
- All ports can autosense the connector speed (10 or 100 Mbps) with the connected device.
- A built-in bridge connects 10 Mbps and 100 Mbps devices automatically
- Per-port LEDs showing link status and whether the port is operating at 100 Mbps or 10 Mbps.
- Activity and Collision LEDs showing general levels of network activity and collisions on the hub.
- Push-button MDI/MDI-X selection on Port 1 to allow a straight-through cable to be used for cascading to another hub or switch.
- Additional management features are included with the Hub 12m and Hub 24m such as per-port security, and hub control through a full-featured hub console, built-in web browser interface, and HP Toptools for Hubs & Switches (included at no additional cost).
- Rack or wall mountable with mounting hardware included.
» Return to top
Q: Do I need an external Switch connected to the HP ProCurve 10/100 Hub 12, 12m, 24, or 24m so that my 10Mbps clients can talk to a 100Mbps server?
No. You do not need to connect the HP ProCurve 10/100 Hubs to an external switch for ports at either speed to communicate with each other. There is an internal bridge which connects the 10Mbps and 100Mbps ports.
» Return to top
Q: Should I use category 5 networking cable on all the connections to the HP ProCurve 10/100 Hub 12, 12m, 24, and 24m?
You should use category 5 cable throughout your network. This will prevent many intermittent cable problems because category 5 is a better quality of cable. You may use category 3 cable on all connections made at 10Mbps. However, if in the future you upgrade those links to 100Mbps, you will need to upgrade that cabling to category 5.
» Return to top
|
| |
| | |
|
|
|
| | |
|
ftp ftp.HP | | Use your ftp software to ftp to HP's site |
Name:anonymous | | Log in as "anonymous" |
Password:john@mycompany.com | | Enter your email address as your password |
ftp>bin | | Enter "bin" to use the binary file transfer type |
ftp>cd/pub/networking/software |
| Go to the directory that has the networking files |
ftp> get filename | | Transfer the file you want to your computer |
ftp> quit | | Quit the ftp session |
|
| |
| | |
|
|
| | |
|
|
Extract the file by typing the filename (e.g., "j3288100.exe") to extract the file.
Read the readme file for directions on how to download the software to your device.
» Return to top
Q: What cables are used with the HP ProCurve 10/100 Hub 12, 12m, 24, and 24m?
All of the twisted-pair ports except port 1 are wired as MDI-X. Port 1 can be changed to either MDI or MDI-X using the MDI/MDI-X button.
For connections to the 10 Mbps ports, you can use Category 3, 4 or 5 unshielded twisted-pair cable, as supported by the IEEE 802.3 Type 10Base-T standard.
For connections to the 100 Mbps ports, use Category 5 only, as defined by the IEEE 802.3u Type 100Base-TX standard. Only twisted-pair cables with solid conductors are supported to the full 100 meters; do not use braided or drop cables.
Twisted-Pair Cable for Hub (MDI-X) to Computer (MDI) Network Connection
All twisted-pair wires must be twisted through the entire length of the cable. The wiring sequence must conform to AT&T 258A (not USOC). To connect PCs to other MDI network devices to these ports, use a "straight-through" cable as shown here:
|
| |
| | |
|
|
|
| | |
|
|
» Return to top
Q: What is the MDI/MDI-X button used for on the HP ProCurve 10/100 Hubs?
We first need some background information. In general, hub ports are MDI-X, transceivers and NICs are MDI. Switch ports are intended to seem like hub ports, so they are MDI-X.
The following devices are MDI devices:
- End node NICs
- HP 10Base-T external transceivers (e.g., 28685B HP EtherTwist Transceiver)
- HP 10Base-T internal transceiver modules (e.g., J2607A HP Twisted Pair Transceiver Module)
The following devices are MDI-X devices:
- HP 10Base-T hub ports (fixed RJ-45) (e.g., built-in RJ-45 ports on the J3200A HP Advancestack 10BT S Hub-12r)
- HP 100Base-TX hub ports (fixed RJ-45) (e.g., J4091A HP ProCurve 100Base-T Hub 8)
- HP switch ports (fixed RJ-45) (e.g., built-in RJ-45 ports on the J3102A HP Advancestack Switch 2000 Ethernet Module)
- HP 100Base-TX internal transceiver modules (e.g., J3192C HP Advancestack 100Base-TX UTP Transceiver Module)
Network communication over twisted-pair wires requires a "roll" of the signals from transmit at one end to receive at the other end. This is accomplished in one of two ways:
- Connect an MDI port at one end to an MDI-X port at the other end, using a straight-through cable
or
- Connect the same style port at both ends, using a crossover cable
So to answer the question, please note that the HP ProCurve 10/100 Hub 12, 12m, 24, and 24m provide a port that can be either MDI or MDI-X, configured by the pushbutton, letting you select the appropriate setting for your needs.
» Return to top
Q: How do I know if a client is connected at 10Mbps or 100Mbps?
The port number (Link) LED will be lit when the port is connected at 10Mbps, and the rectangular LED just below the Link LED will also be lit when the port is connected at 100Mbps.
» Return to top
Q: How many hubs can I cascade together when connecting at 10Mbps?
You can have up to four hubs cascaded when connecting 10Mbps nodes to the ports on the HP ProCurve 10/100 Hub.
» Return to top
Q: How many hubs can I cascade together when connecting at 100Mbps?
The HP ProCurve 10/100 Hub 12, 12m, 24, and 24m are class II hubs when attaching 100Mbps devices. Therefore you may have two 10/100 hubs cascaded together. You may have 100 meters of network cable between a hub and an end node. You may only have 5 meters of cable between the two 10/100 hubs.
» Return to top
Q: Do the HP ProCurve 10/100 Hub 12, 12m, 24, and 24m support full-duplex?
The hub ports can only operate in half-duplex mode. If the attached device is running in full-duplex mode, and cannot auto-negotiate to half duplex, it will cause a lot of late collisions on the network, degrading performance for all nodes.
» Return to top
Q: Do the HP ProCurve 10/100 Hub 12, 12m, 24, and 24m support 802.1Q/802.1p?
The HP ProCurve 10/100 Hubs allow 1522 byte size packets tagged with an 802.1Q tag but do not decode the VLAN ID. The hubs do not participate in VLAN tagging or VLAN priorities. The packets will be forwarded without any problems.
» Return to top
Q: Is 10/100Mbps auto-negotiation the same as Plug-n-Play?
No. The following configuration will cause severe network problems:
The hub, switch, or router will correctly sense (not auto-negotiate) the 10Mbps or 100Mbps speed. Since the end node was configured for a specific speed and duplex state, and therefore does not negotiate, the hub, switch, or router will choose the communication mode specified by the 802.3u standard, namely half-duplex.
With one device running at half-duplex and the device on the other end of the connection at full-duplex, the connection will work reasonably well at low levels of traffic. At high levels of traffic the full-duplex device (end node, in this case) will experience an abnormally high level of CRC or alignment errors. The end users usually describe this situation as, "Performance seems to be approximately 1Mbps!". Often, end nodes will drop connections to their servers.
In this same situation, the half-duplex device will experience an abnormally high level of late collisions.
The network administrator must take care to verify the configuration of each network device during installation. Also, check the operational mode of each network device. That is, check both how you configured it and also that it comes up as you expect, for example, at 10Mbps/half-duplex.
» Return to top
|
| |
| | |
|
|
