Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
 
HP ProCurve Networking

» My ProCurve Sign In

HP ProCurve Networking  >  Customer Care support  >  FAQs

FAQs


  »

HP Networking



The FAQs listed below are for these products:

  • J8712A ProCurve Switch zl Internal Powers Supply
  • J8713A ProCurve Switch zl 220V Internal Power Supply
  • J8714A ProCurve Switch zl Power Supply Shelf
  • J8715A ProCurve Switch 8212zl Base System
  • J9091A ProCurve Switch 8212zl Chassis
  • J9092A ProCurve Switch 8200zl Management Module
  • J9093A ProCurve Switch 8200zl Fabric Module
  • J9095A ProCurve Switch 8200zl System Support Module

»  View FAQs for a different group of products

Customer Care

»  Overview
»  Services
»  Support
   »  Software
   »  Warranty
   »  FAQs
   »  Knowledge Base
   »  Manuals
   »  Reference library
   »  Configuration examples
   »  Support forms
   »  Security notices

My ProCurve gives you instant access to software update notifications.
» Register or log in now

Commercial help me agent » Contact ProCurve
8206zl and 8212zl
» Q: What are the differences between the 8212zl chassis and the 8206zl chassis?
» Q: When ordering spares for 8206zl and 8212zl are there any parts that can be shared between chassis?

8212zl Chassis switch roll from J8715A to J8715B
» Q: Why is HP ProCurve Rolling J8715A/HP ProCurve 8212zl Switch?
» Q: Does the new J8715B/8212zl Base System product provide any product capability changes or improvements compared to old J8715A/8212zl Base System?
» Q: What impact will this roll have on legacy 8212zl customers (who previously purchased J8715A/HP ProCurve Switch 8212zl Base Systems)?
» Q: Is the 8212zl standard product warranty different for the new, J8715B-based offering?
» Q: Will there be any pricing changes with this roll?

General product details
» Q: What is the ProCurve 8212zl switch?
» Q: What comes with the 8212zl base system, part number J8715A?
» Q: Is the 8212zl chassis an active or passive chassis?
» Q: What is the throughput of the 8212zl?
» Q: How many addresses can the routing table hold?
» Q: What is the routing/switching capacity?
» Q: Is Premium Software licensing available for 8200zl like on 5400zl and 3500yl?
» Q: What is the pin out on the console cable for the 8212zl?
» Q: How long is the hardware warranty?
» Q: Why are the System Support Module (SSM) screws different than the screws that hold the other modules in?
» Q: What is the easiest way to install an 8212zl chassis into a rack?

Power/PoE
» Q: What are the power supply options for the zl chassis?
» Q: Can the 8212zl power supplies be hot swapped?
» Q: What parts are included when a power supply is purchased?
» Q: What do the power cord connectors look like?
» Q: What is the maximum number of PoE ports supported by the 8212zl switch?
» Q: Besides internal power supplies, can you connect external power for additional PoE power?
» Q: What are the two devices defined for PoE implementations?
» Q: On what pairs is PoE power distributed?
» Q: How does PSE (power sourcing equipment) know when a PD (powered device) needs PoE?
» Q: How does one enable pre-standard PoE support?
» Q: What is a jumper cable and how is it used?
» Q: Does ProCurve Networking by HP have jumper cables for its LAN Switch products?
» Q: Why are ProCurve jumper cables required for use with a PDU or UPS?
» Q: What do the jumper cable connectors look like?
» Q: What ProCurve products require a C14 to C15 or a C19 to C20 jumper cable to connect to a PDU or UPS?
» Q: What are the technical specifications for the C14 to C15 and C19 to C20 jumper cables?
» Q: How does a customer purchase the C14 to C15 or C19 to C20 jumper cables?
» Q: Is there a redundancy command that simplifies managing power redundancy on zl chassis?
» Q: What are the different power configurations for the 5406zl and 8206zl with the 3 power supplies?
» Q: What are the different power configurations for PoE only (not PoE+) with the 5406zl and 8206zl?
» Q: What are the different power configurations for PoE/PoE+ with the 5406zl and 8206zl?
» Q: What are the different power configurations for the 5412zl and 8212zl with the 3 power supplies?
» Q: What are the different power configurations for PoE only (not PoE+) with the 5412zl and 8212zl?
» Q: What are the different power configurations for PoE/PoE+ with the 5412zl and 8212zl?

Redundancy
» Q: How long does it take for the Standby management module to take control if the Active management module fails?
» Q: How do the management modules interact with each other?
» Q: Are the management modules hot swappable?
» Q: Can the 8212zl switch function without a management module in the system?
» Q: If my active management module fails and the Standby management module becomes active, will the 8212zl lose its configuration?
» Q: Can you disable the synchronizing of configurations between the active management module and the standby management module?
» Q: Can you manually force the standby management module to become the active module?
» Q: What are the events that cause management modules to switchover?
» Q: What events do not cause a management switchover to occur?
» Q: What commands are available to help understand current redundancy configuration?
» Q: What existing CLI commands are affected by Redundant Management?
» Q: Are the 8212zl Fabric modules redundant or resilient?

Accessories
» Q: What modules only work in the 8212zl and not in the 5400zl?
» Q: What types of interface modules are supported in ProCurve 8212zl Switches?
» Q: How can I get the best performance from a 4 port 10G module considering each module only gets 28.8G throughput to the switch fabric?
» Q: If I only have two 10G connections on one module how do I guarantee each port gets 10G?
» Q: Is the 8212zl fan tray field replaceable?
» Q: What are the part numbers for the field replaceable parts for the 8212zl?
» Q: Which mini-GBICs are supported on the ProCurve 8212zl Switch?
» Q: What types of 10-GbE transceivers are supported in the ProCurve 8212zl Switch?
» Q: What precautions should I follow when removing the J8177B gigabit-copper mini-GBIC from my switch?
» Q: Which ProCurve mini-GBICs and SFPs are supported in which ProCurve products?

Features/Protocols
» Q: Are Jumbo frames supported on the ProCurve 8212zl series switches?
» Q: Are Jumbo frames enabled per VLAN or per physical interface?
» Q: What type of spanning tree implementation do the ProCurve 8212zl switches support?
» Q: How would MSTP interact with switches that support only 802.1D STP or 802.1w RSTP?
» Q: What advantage does implementation of IEEE 802.1s MSTP offer over legacy STP or RSTP?
» Q: Will the ProCurve 8212zl support routing when Switch Meshing is enabled?
» Q: When configured for meshing, is the ProCurve 8212zl switch backwards-compatible with older model ProCurve switches that support meshing?
» Q: How does UDP Broadcast Forwarding work?
» Q: Can 802.1X, Web-based authentication, and MAC-based authentication all be used concurrently on a switch port?
» Q: Are there limits to the number of Access Control Entries (ACEs) supported within an Access Control List (ACL)?
» Q: Is there a limit to the number of ACLs supported by the 8212zl?
» Q: How does Source port filtering work?
» Q: What are the default DSCP codepoint values?
» Q: Does the 8212zl support sFlow?
» Q: How do I enable sFlow support on the ProCurve 8212zl switch using a network management application? Must I configure anything on the switch?
» Q: How do I take advantage of multiple configuration files?
» Q: What is the benefit of maintaining current software on my ProCurve Switch?
» Q: Why doesn't the VRRP backup router respond to pings when it is in the master role?
» Q: Why don't the 8212zl Switches support CDP?
» Q: Does the (link aggregation) trunking algorithm for the ProCurve 8212zl Series switches take into account IP addresses when allocating sa/da individual traffic flows to the individual links of a trunk?
» Q: Does the 8212zl support remote port mirroring?
» Q: Which USB Flash Drives have been tested with the ProCurve 8212zl switches and what were the findings?
» Q: Is it okay to use USB flash drives that have not been tested?
» Q: What should I do if the USB flash drive file system is not recognized by the ProCurve switch?
» Q: What are the USB flash drive support limitations?
» Q: Does the 8212zl support rate limiting?

Software
» Q: Can I load the same software version on my 8206zl that I run on my 8212zl?
» Q: What power CLI enhancements are available with software K.14.xx?
» Q: What new features are available when updating to K.14.xx software?

Interoperability
» Q: My Cisco 7910, 7912, 7940, 7960 IP phone does not power up when connected to zl PoE modules?

Security
» Q: Does the 8212zl support DHCP Snooping?
» Q: Does the 8212zl have CPU protection?
» Q: Does the 8212zl support Virus throttling?

Routing
» Q: What routing protocols are supported on the 8212zl?
» Q: How many static routes does the 8212zl support?
» Q: How many secondary IP addresses per interface?
» Q: How many IP interfaces does the 8200zl support?
» Q: How large is the ARP/Route table?

Troubleshooting
» Q: Right after I start up my switch, I observe high (99-100%) CPU utilization. Why does this happen?
» Q: How are broadcast storms created and what are some tips to avoid them?
» Q: What information should you have before calling your reseller or ProCurve Support?
» Q: What information might support request to help troubleshoot problem once customer has already called support?

Answers

8206zl and 8212zl

Q: What are the differences between the 8212zl chassis and the 8206zl chassis?

  • The 8206zl supports 6 interface modules the 8212zl supports 12.
  • The 8206zl will only run on K.14.34 or later software. The 8212zl will run on K12.31 or later software.
  • The 8206zl supports 2 internal power supplies the 8212zl supports 4.

» Return to top

Q: When ordering spares for 8206zl and 8212zl are there any parts that can be shared between chassis?
Yes, the following modules can be shared between chassis:

  • (J9092A) Management Module
  • (J9093A) Fabric Modules
  • (J9095A) System Support Module

» Return to top

8212zl Chassis switch roll from J8715A to J8715B

Q: Why is HP ProCurve Rolling J8715A/HP ProCurve 8212zl Switch?
HP ProCurve is a firm believer in offering our customers choices. As a result of this roll our Switch 8212zl customers will now be able to…

  • Deploy an J8715B/8212zl Base System with Layer 2 and basic Layer 3 features only or an 8212zl with Advanced Layer 3 features (with purchase of J9474A/8200zl Premium License)
  • Upgrade a deployed J8715B/8212zl Base System with Advanced Layer 3 features (with post-deployment purchase of J9474A/8200zl Premium License)

» Return to top

Q: Does the new J8715B/8212zl Base System product provide any product capability changes or improvements compared to old J8715A/8212zl Base System?
There are no product capability differences between a J8715A/8212zl Base System and a J8715B/8212zl Base System. The only offering difference is which feature set is pre-enabled in the system.

» Return to top

Q: What impact will this roll have on legacy 8212zl customers (who previously purchased J8715A/HP ProCurve Switch 8212zl Base Systems)?

  • Previously installed J8715A/8212zl Base Systems: No impact
    • Customers will continue to be provided software enhancements common to both legacy J8715A and new J8715B Base Systems
    • Legacy 8212zl Base Systems will continue to be supported by HP and Support Services for the foreseeable future
    • No change to legacy 8212zl Base Systems product standard warranty terms & conditions:
      • h/w warranty: lifetime, next business day advance replacement, for as long as you own the product
      • s/w warranty: lifetime, for as long as you own the product
      • phone/email support (h/w and all s/w functionality): local business hours, for as long as you own the product
      • bug fixes, feature enhancements (h/w and all s/w functionality): for as long as you own the product
  • Legacy 8212zl customers who wish to deploy new 8212zl systems would purchase J8715B/8212zl Base Systems going forward. If advanced Layer 3 features are required for those systems customer would also purchase J9474A/8200zl Premium License

» Return to top

Q: Is the 8212zl standard product warranty different for the new, J8715B-based offering?

  • J8715B/8212zl, no 8200zl Premium License installed (standard s/w features): NO CHANGE compared to J8715A/8212zl
  • J8715B/8212zl, 8200zl Premium License installed (advanced s/w features): Changes apply to advanced s/w features as noted below
  J8715B/8212zl Base System (standard s/w features) 8200zl Premium License (advanced s/w features)
h/w warranty Lifetime, next business day advance replacement, for as long as you own the product n/a
s/w warranty Lifetime, for as long as you own the product
Phone/email support h/w + standard s/w features: local business hours, for as long as you own the product Advanced s/w features: local business hours, 1 year

Customer purchase support contracts to provide phone/email support beyond the 1st year
Bug fixes for as long as you own the product
Feature enhancements h/w + standard s/w features: for as long as you own the product Advanced s/w features: 1 year

Customer purchase support contracts to provide enhancement subscription services beyond the 1st year

» Return to top

Q: Will there be any pricing changes with this roll?

  • Customers deploying 8212zl systems that require Advanced Layer 3 features can expect to pay a slightly higher price for the combined J8715B/HP ProCurve Switch 8212zl, J9474A/HP ProCurve 8200zl Premium License, and Software Support Services (which must be purchased to provide phone/email support and software updates/upgrades for the advanced software functionality provided with the 8200zl Premium License beyond the initial 1 year warranty period for that product).
  • Customers requiring Layer 2 and/or Base Layer 3 features only can expect to pay a lower price for the new J8715B/8212zl Base System (compared to the legacy J8715A/8212zl Base System product).

» Return to top

General product details

Q: What is the ProCurve 8212zl switch?
The ProCurve Switch 8212zl is a high-performance, highly available, chassis switch platform that enables unified core-to-edge adaptive network solutions and delivers to market the industry’s first core switch with a lifetime warranty. With a full range of connectivity options, comprehensive networking features, advanced security tools, and unified core-to-edge infrastructure and management tools, the Switch 8212zl reduces complexity and provides lower cost of ownership. The ProCurve Switch 8212zl is ideal for customers seeking to cost-effectively meet the stringent availability requirements of today’s converged network environments without sacrificing performance or flexibility.

» Return to top

Q: What comes with the 8212zl base system, part number J8715A?
The 8212zl (J8715A) comes with the following parts:

  • (1) J9091A Chassis
  • (1) J9092A Management Module
  • (2) J9093A Fabric Modules
  • (1) J9094A Fan Tray
No power supplies come with the J8715A Chassis bundle.

» Return to top

Q: Is the 8212zl chassis an active or passive chassis?
The ProCurve switch 8212zl is a passive chassis.

» Return to top

Q: What is the throughput of the 8212zl?
The 8212zl throughput is up to 428 million pps.

» Return to top

Q: How many addresses can the routing table hold?
The routing table can hold up to 10,000 entries.

» Return to top

Q: What is the routing/switching capacity?
The routing/switching capacity on the 8212zl is 692 Gbps total (28.8Gb/slot).

» Return to top

Q: Is Premium Software licensing available for 8200zl like on 5400zl and 3500yl?
Yes, Customers can purchase the J9474A Premium license that enables OSPF, VRRP, PIM-DM and PIM-SM capabilities.

» Return to top

Q: What is the pin out on the console cable for the 8212zl?

RJ45 to DB9 Cable Pin Numbers

RJ45 (signal reference from MM)

DB9 (signal reference from PC)

RTS

1

8

CTS

TX_Debug

2

6

DSR

TXD

3

2

RXD

GND

4

5

GND

DCD

5

1

DCD

RXD

6

3

TXD

RX_Debug

7

4

DTR

CTS

8

7

RTS

 

 

9

RI


» Return to top

Q: How long is the hardware warranty?
The warranty lasts for as long as you own the product, with next business-day advance replacement (where available) for confirmed hardware failures.

» Return to top

Q: Why are the System Support Module (SSM) screws different than the screws that hold the other modules in?
Since the SSM is a required module for the operation of the 8212zl chassis, it is not a hot swappable module. Although no damage will occur to the chassis if the SSM is removed during operation, if removed it will power down the system (similar to pulling a sole management module with no standby MM in place). To prevent the accidental removal of the module, the SSM is mounted to the chassis with Tamper-Resistant Screws (TRS). TRS also contribute to the low failure rate probability for the SSM – static discharge through user handling, or misalignment of pins upon reinsertion, just to name a few contributors to module failure. Refer to the illustration below.

Torx screws set up

» Return to top

Q: What is the easiest way to install an 8212zl chassis into a rack?

  1. Use a #1 Phillips (cross-head) screwdriver and attach the mounting brackets to the switch with the included 8-mm M4 screws. For the Switch 8212zl, each bracket is attached with four screws as shown in the following illustration.
    8mm M4 Screws
  2. Partially install a screw into the top hole of a pair of holes that are 0.5 inches apart in each rack/cabinet upright as shown in the illustration below. Ensure that the screws are at the same level in each upright.
    Partially install a screw into the top hole of a pair of holes that are 0.5 inches apart in each rack
  3. Place the switch in the rack and lower it so that the notches in the bottom of the bracket slide onto the screws, then tighten these screws.
    Place the switch in the rack and lower it so that the notches in the bottom of the bracket slide onto the screws, then tighten these screws.
  4. Install the other screw into the upper hole in each bracket. Tighten these screws.
    Install and tighten the other 12 to 24 screws

» Return to top

Power/PoE

Q: What are the power supply options for the zl chassis?
There are two power supplies available for the 8200zl and 5400zl family of switches. Read below for more information:

ProCurve Switch zl 875W Power Supply (J8712A) ProCurve Switch zl 875W Power Supply (J8712A)

Electrical characteristics
Voltage: 100-127 VAC/200-240 VAC
Maximum current: 12 A/5.7 A
Frequency range: 50/60 Hz
Power: 875 W
Notes
J8712A supplies 600 W chassis power and 273 W PoE power.
Two J8712A supplies are required to power the J8715A chassis.
See the Ordering Guide for more details on power supply selection for PoE power.

ProCurve Switch zl 1500W Power Supply (J8713A) ProCurve Switch zl 1500W Power Supply (J8713A)

Physical characteristics
Dimensions: 6.05 x 7.45 x 5.1 in.
(15.37 x 18.92 x 12.95 cm)
Weight: 7.5 lb (3.4 kg)

Electrical characteristics
Maximum current: 10A
Frequency range: 50/60 Hz
Power: 1500 W

Notes
220 V only. Installation of the J8713A reduces the chassis altitude specification to 10,000 ft (3677 m).
J8713A supplies 600 W chassis power and 900 W PoE power.
See the Ordering Guide for more details on power supply selection for PoE power.
Units shipped to North America include a NEMA L6-20P twist lock power cord. Non-locking NEMA 6-20P optionally available – see the Ordering Guide for more details.

POE1.3Supply End - NEMA L6-20P
Equipment End - IEC-C19
20A/250V

ProCurve Switch zl 1500W PoE + zl Power Supply (J9306A) ProCurve Switch zl 1500W PoE + zl Power Supply (J9306A)
Standard PoE+ power supply for zl series switches. Supplies 300W for PoE+ power at 110-127 volts, 900W for PoE+ power at 200-240 volts, and 600 W for switch power.

Physical characteristics
Dimensions: 6.05(d) x 7.45(w) x 5.1(h) in.
(15.37 x 18.92 x 12.95 cm)
Weight: 7.5 lb (3.2 kg)

Electrical characteristics
Voltage: 100-127 VAC/200-240 VAC
Maximum current: 13 / 10 A
Maximum power rating: 1500 W
Frequency range: 50/60 Hz

Notes
  • Maximum power rating and maximum heat dissipation are the worst-case theoretical maximum numbers provided for planning the infrastructure with fully loaded PoE (if equipped), 100% traffic, all ports plugged in, and all modules populated.
  • Each J9306A supplies 600 W chassis power, 300 W of PoE/PoE+ power at 110-127 volts, and 900 W of PoE/PoE+ power at 200-240 volts.

» Return to top

Q: Can the 8212zl power supplies be hot swapped?
The power supply in the chassis generates both system power and PoE power. There are multiple power slots to allow for additional PoE power and/or redundancy. As long as the minimum number of power supplies for system power is installed at any given time, power supplies can be removed and replaced while the switch is operating. Caution should be used when doing this, however, because disconnecting power supplies interrupts PoE operation.

» Return to top

Q: What parts are included when a power supply is purchased? The Switch zl Internal Power Supply has the following components shipped with it:

  • ProCurve Switch zl Internal Power Supply Installation Guide (5991-8553)
  • Customer Support/Warranty booklet
  • Power cord, one of the following:

J8712A Power Supply

J8713A Power Supply

Region

Cable

Region

Cable

Australia/New Zealand

8120-5335

Australia/New Zealand

8121-0871

China

8121-1034

China

1021-0924

Continental Europe

8120-5336

Continental Europe

8120-6899

Denmark

8120-5340

Denmark

8120-6897

Japan

8120-5342

Japan

8120-6903

Switzerland

8120-5339

Switzerland

8120-6897

United Kingdom/
Hong Kong/Singapore

8120-5334

United Kingdom/
Hong Kong/Singapore

8120-6898

United States/
Canada/Mexico

8121-0973

United States/
Canada/Mexico

8120-6903*

South Africa

8120-5341

South Africa

8121-0915

Taiwan

8121-0941

Taiwan

8120-6903

* A non-locking power cord is also available. Order part number 8120-6893. To order, go to http://www.hp.com/buy/parts.

J9306A Power Supply
Region Cable Region Cable
Australia/New Zealand 8121-0857 Israel 8121-1009
China 8121-1034 Thailand 8121-0671
Continental Europe 8120-5336 Taiwan
(110V operation)
8121-0967
Denmark 8120-5340 Taiwan
(NEMA L6-20, 220V)
8121-0941
Japan
(NEMA L6-20, 200V)
8121-0941 U.S./Canada/Mexico
(NEMA 5-15, 120V)
8121-0973
Switzerland 8120-5339 U.S./Canada/Mexico
(NEMA L6-20, 240V)
8121-0941
United Kingdom/Hong Kong/Singapore 8120-5334 South Africa/India 8120-5341

Note: The 8121-0973 120V ships with all J9306A power supplies in the U.S. Customers requiring the 8121-0941 can purchase through the HP part store.

» Return to top

Q: What do the power cord connectors look like?
The following table displays the connectors for the regional power cords.

 
Country

Part Number

Length

Connector Type

Connector

Connector Type

Connector

Australia/
New Zealand

8120-5335

2.5 m

AS 3112-3 AS 3112-3

C15

C15

8121-0871

4.5 m

AS 3112-3 AS 3112-3

C19

C19

China

8120-8385

2.5 m

GB 1002 GB 1002

C15 90-deg

C15 90-deg

8121-0916

2.5 m

SEV 1011 SEV 1011

C19

C19

8121-1034

2.5 m

GB 1002 GB 1002

C15

C15

Continental Europe

8120-5336

2.5 m

CEE 7-VII CEE 7-VII

C15

C15

8120-6899

4.5 m

CEE 7-VII CEE 7-VII

C19

C19

8120-6352

2.5 m

CEE 7-VII CEE 7-VII

C19

C19

Denmark

8120-5340

2.5 m

DK 2-5A DK 2-5A

C15

C15

8120-6897

4.5 m

IEC 309 IEC 309

C19

C19

Isreal

8121-1009

2.5 m

SI 32 90-DEG SI 32 90-DEG

C15

C15

8121-1010

2.5 m

SI 32 90-DEG SI 32 90-DEG

C19

C19

Japan

8120-5342

2.5 m

JIS C8303 JIS C8303

C15

C15

8120-6903

4.5 m

NEMA L6-20P NEMA L6-20P

C19

C19

8121-0942

2.5 m

JIS C8303 JIS C8303

C19

C19

South Africa / India

8120-5341

2.5 m

SABS 164 SABS 164

C15

C15

8121-0915

2.5 m

SABS 164 SABS 164

C19

C19

Switzerland

8120-5339

2.5 m

SEV 1011 SEV 1011

C15

C15

8120-6897

4.5 m

IEC 309 C19

C19

C19

8121-0916

2.5 m

SEV 1011 SEV 1011

C19

C19

Taiwan

8121-0967

2.5 m

CNS 690 CNS 690

C15

C15

8121-0941

2.5 m

NEMA L6-20P NEMA L6-20P

C15

C15

8120-6903

4.5 m

NEMA L6-20P NEMA L6-20P

C19

C19

8121-0968

4.5 m

CNS 690 CNS 690

C19

C19

Thailand

8121-0671

2.5 m

NEMA 5-15P NEMA 5-15P

C15

C15

8121-0675

4.5 m

NEMA 10-20 NEMA 10-20

C19

C19

8121-0922

2.5 m

NEMA 5-15P NEMA 5-15P

C19

C19

U. K. / Hong Kong / Singapore

8120-5334

2.5 m

BS 1363/A BS 1363/A

C15

C15

8120-6898

4.5 m

BS 1363/A BS 1363/A

C19

C19

8121-0907

2.5 m

BS 1363/A BS 1363/A

C19

C19

U.S. / Canada / Mexico

8121-0973

2.5 m

NEMA 5-15P NEMA 5-15P

C15

C15

8121-0941

2.5 m

NEMA L6-20P NEMA L6-20P

C15

C15

8120-6903

4.5 m

NEMA L6-20P NEMA L6-20P

C19

C19

8120-6893

4.5 m

NEMA 6-20P NEMA 6-20P

C19

C19

8120-6361

2.5 m

NEMA 5-20P NEMA 5-20P

C19

C19

» Return to top

Q: What is the maximum number of PoE ports supported by the 8212zl switch?

Power Supply Configuration Total PoE Power (Watts) Number of PoE ports at 15.4 W consumption Number of PoE ports at 8 W consumption
No Redundancy With N+N Redundancy No Redundancy With N+N Redundancy

Two 875W
(J8712A)

546 W
(2 X 273)

35

17

68

34

Four 875W
(J8712A)

1092 W
(4 X 273)

70

35

136

68

Two 1500W
(J8713A)

1800 W
(2 X 900)

116

58

225

112

Four 1500W
(J8713A)

3600 W
(4 X 900)

233

116

288

225

» Return to top

Q: Besides internal power supplies, can you connect external power for additional PoE power?
The ProCurve Switch zl Power Supply Shelf (J8714A) provides a 3U high enclosure to hold up to two extra zl switch power supplies (the same type used in the 8212zl/5400zl switches) to provide additional PoE power to zl switches beyond the PoE power available through the switch's internal power supplies alone. These extra supplies also can be used to provide PoE power redundancy beyond what is possible with switch internal supplies. Large Switch zl VoIP installations are ideal environments for the ProCurve Switch zl Power Supply Shelf.

Power Supply Types

System Power

PoE Power

Graphic

External Switch zl Power Shelf J8714A

0
(only provides PoE power)

Up to 1800W

Install 1 or 2 of J8712A or J8713A

Install 1 or 2 of J8712A or J8713A

» Return to top

Q: What are the two devices defined for PoE implementations?
The first type, called the powered device or PD, receives power from the second type, called the power sourcing equipment or PSE. Powered devices include any Ethernet device capable of receiving power through a data port such as IP telephones, IP cameras, PDAs and tablet PCs. Power sourcing equipment, such as ProCurve switches with PoE support, must meet IEEE 802.3af specifications for voltage (47 to 57 volts DC) and wattage (up to 15.4 watts), with further limitations on devices that receive power. The ProCurve 8212zl is PoE-enabled to support both IEEE 802.3af compliant devices, as well as some pre-802.3af standard devices.

» Return to top

Q: On what pairs is PoE power distributed? The 802.3af standard provides two options for providing power over CAT 5 Ethernet cable. They are:

  1. Unused pairs: This option takes advantage of the fact that 10Base-T and 100Base-TX signals use only two of the four twisted pairs in the cable. In this option, the pins on pairs 1/2 and 3/6 are used for data, and the pins on pairs 4/5 and 7/8 are used for power. The 4/5 pair is twisted together to form the positive supply, and the 7/8 pair is twisted together to form the negative supply.
  2. Data pairs: This option provides power over pairs that also provide data, and is necessary because 1000Base-T signals use all four pairs. In this option, either the 1/2 pair or the 3/6 pair can form the positive supply.

The 8212zl uses the Data pairs for all RJ45 ports on the J8702A (24-port Gig module) & J8705A (20+4-port Gig + mGBIC module).

» Return to top

Q: How does PSE (power sourcing equipment) know when a PD (powered device) needs PoE?
In most networks, PSE will be connected to some devices that support PoE and some that do not. Consequently, in order to prevent damage to non-PoE devices, the 802.3af specification includes a negotiation mechanism between PSEs and the stations connected to them. Under the specification, PSEs apply a slight voltage on the power-delivery pairs. If there is a valid PD on the cable, it will present a resistance and a capacitance. Typically, this discovery process requires approximately 500 milliseconds. The PSE will apply the full wattage if it discovers a PD, but the flow is current-limited to prevent damage to cable and equipment under fault conditions.

After discovery, a PD must draw a minimum current for the power flow to remain active. If, for example, the PD is unplugged; the PSE will discontinue power supply over the cable. The discovery process will be repeated when the PD is returned to service.

» Return to top

Q: How does one enable pre-standard PoE support?
The ProCurve Switch 8212zl Switch supports some pre-802.3af devices. This feature is enabled by default. It can be disabled using the no power pre-std-detect command.

» Return to top

Q: What is a jumper cable and how is it used?
A jumper cable (also known as a jumper cord), provides a power interconnect between a LAN Switch and a power distribution device, such as a Power Distribution Unit (PDU) or an Uninterruptible Power Supply (UPS).

» Return to top

Q: Does ProCurve Networking by HP have jumper cables for its LAN Switch products?
Yes, ProCurve Networking by HP does have jumper cables available for its LAN Switch products through the worldwide HP Parts Store at www.hp.com/buy/parts.

» Return to top

Q: Why are ProCurve jumper cables required for use with a PDU or UPS?
The ProCurve Networking by HP jumper cables are designed to HP specifications to minimize defects in materials and workmanship. The jumper cables were developed specifically to meet the extended temperature specifications, 0°C to 55°C (32°F to 131°F) of ProCurve switches while complying with international laws.

Using jumper cables which do not meet ProCurve’s specifications could result in overheating of the jumper cables. Use the proper jumper cables listed for your ProCurve switches. Use of any other jumper cable is not supported by ProCurve.

» Return to top

Q: What do the jumper cable connectors look like?
The following table displays the connectors for C14 to C15 jumper cables and C19 to C20 jumper cables.

Product Description Connector Type Connector Type
C14 to C15
Jumper Cable

C14
C14

C15
C15

C19 to C20
Jumper Cable

C19
C19

C20
C20

 

The C15 or C19 connector inserts into the power inlet on the switch power supply, while the C14 or C20 connector inserts into the receptacle on a power distribution device, PDU or UPS.

» Return to top

Q: What ProCurve products require a C14 to C15 or a C19 to C20 jumper cable to connect to a PDU or UPS?
The table below displays, by country, the jumper cable part number for a specific ProCurve product. The jumper cable required by a ProCurve 8200zl or 5400zl switch and a ProCurve Power Supply Shelf, depends on the wattage of the power supply in the ProCurve product (875 W (J8712) or 1500 W (J8713)). Jumper cables are available in two lengths, 1 meter and 2.5 meters.

Country

Length
(meters)

ProCurve
Switch
3500yl/6200yl 2

ProCurve
Switch 8200zl/5400zl
and
Power Supply Shelf

ProCurve 620
Red/Ext Power
Supply 1

875 W Supply 2

1500 W Supply 1

Australia/
New Zealand

1 m
2.5 m

8121-1093
8121-1094

8121-1089
8121-1090

China

1 m
2.5 m

8121-1093
8121-1094

8121-1089
8121-1090

Continental
Europe

1 m
2.5 m

8121-1093
8121-1094

8121-1089
8121-1090

Denmark

1 m
2.5 m

8121-1093
8121-1094

8121-1089
8121-1090

Israel

1 m
2.5 m

8121-1093
8121-1094

8121-1089
8121-1090

Japan

1 m
2.5 m

8121-1092   
8121-1091   

8121-1089
8121-1090

South Africa/
India

1 m
2.5 m

8121-1093
8121-1094

8121-1089
8121-1090

Switzerland

1 m
2.5 m

8121-1093
8121-1094

8121-1089
8121-1090

Taiwan

1 m
2.5 m

8121-1092   
8121-1091   

8121-1089
8121-1090

Thailand

1 m
2.5 m

8121-1093
8121-1094

8121-1089
8121-1090

U.K.

1 m
2.5 m

8121-1093
8121-1094

8121-1089
8121-1090

Hong Kong/
Singapore

1 m
2.5 m

8121-1093
8121-1094

8121-1089
8121-1090

U.S./Canada/
Mexico

1 m
2.5 m

8121-1092   
8121-1091   

8121-1089
8121-1090

1 – C19 to C20 cable: The C19 connector connects into the power inlet on the switch’s power supply, while the C20 connector connects into the receptacle on a power distribution unit.
2 – C14 to C15 cable: The C15 connector connects into the power inlet on the switch’s power supply, while the C14 connector connects into the receptacle on a power distribution unit.

» Return to top

Q: What are the technical specifications for the C14 to C15 and C19 to C20 jumper cables?
The table below contains the technical specifications for the C14 to C15 and C19 to C20 jumper cables.

Part Number Jumper Cable Description Length Volts Amps
8121-1089 Straight C19 connector to straight C20 connector 1.0 m
(39.3 in)
100 – 240 Volts 20 A
(16 A2)
8121-1090 Straight C19 connector to straight C20 connector 2.5 m
(98.4 in)
100 – 240 Volts 20 A1
(16 A2)
8121-1092 Straight C14 connector to straight C15 connector 1.0 m
(39.3 in)
100 – 240 Volts 15 A
8121-1091 Straight C14 connector to straight C15 connector 2.5 m
(98.4 in)
100 – 240 Volts 15 A
8121-1093 Straight C14 connector to straight C15 connector 1.0 m
(39.3 in)
200 - 240 Volts 10 A
8121-1094 Straight C14 connector to straight C15 connector 2.5 m
(98.4 in)
200 - 240 Volts 10 A

1 – Rating of 20 A at 240 V in U.S. and Canada
2 – Rating of 16 A at 240 V in Japan, Taiwan, Australia/New Zealand, China, Continental Europe, Denmark, Israel, South Africa/India, Switzerland, Thailand, U.K., and Hong Kong/Singapore

» Return to top

Q: How does a customer purchase the C14 to C15 or C19 to C20 jumper cables?
The C14 to C15 jumper cables or C19 to C20 jumper cables are orderable through the HP Parts Store at www.hp.com/buy/parts.

» Return to top

Q: Is there a redundancy command that simplifies managing power redundancy on zl chassis?
Yes,when PoE redundancy is enabled, PoE redundancy occurs automatically. The switch keeps track of power use and won’t supply PoE power to additional PoE devices trying to connect if that results in the switch not having enough power in reserve for redundancy if one of the power supplies should fail.

Syntax: [no] power-over-ethernet redundancy [n+1 | full]

Allows you to set the amount of power held in reserve for redundancy.

The no option means that all available power can be allocated to PDs.

Default: No PoE redundancy enforced.

n+1: One of the power supplies is held in reserve for redundancy. If a single power supply fails, no powered devices are shut down.If power supplies with different ratings are used, the highest-rated power supply is held in reserve to ensure full redundancy.

full: Half of the available power supply is held in reserve for redundancy. If power supplies with different ratings are used, the highest-rated power supply is held in reserve to ensure full redundancy.

See the power configuration FAQs for more information about PoE redundancy and power supplies.

» Return to top

Q: What are the different power configurations for the 5406zl and 8206zl with the 3 power supplies?

  Number of Power Supplies Redundancy Model
J8712A
(110 or 220 V)
J8713A
(220 V only)
J9306A N + 1
or full
Redundant System Power
@110-
127 V
@200-
240 V
System
Power
(12V)
1 0 1 0   None
2 0 2 0 Full Up to 600 W system power
0 1 0 1   None
0 2 0 2 Full Up to 600 W system power

» Return to top

Q: What are the different power configurations for PoE only (not PoE+) with the 5406zl and 8206zl?

Switch Model 5406zl/8206zl Number of Power Supplies Redundancy Model Non-redundant
Power Available
J8712A
(110 or 220 V)
J8713A
(220 V only)
N + 1 or full Redundant
PoE Power
Non-Redundant
PoE Power
PoE Power (50v)
Internal
1 0 - None 273 W
2 0 Full Up to 273 W 546 W
0 1 - None 546 W
0 2 Full Up to 900 W 1800 W
With External
Power supplies
added
3 0 N + 1 Up to 546 W 819 W
4 0 Full Up to 546 W 1092 W
0 3 N + 1 Up to 1800 W 2700 W
0 4 Full Up to 1800 W 3600 W
Mixed PoE Power
(Not Recommended)
1 1 N + 1 Up to 273 W 1173 W

» Return to top

Q: What are the different power configurations for PoE/PoE+ with the 5406zl and 8206zl?

Switch Model
5406zl/8206zl
Number of Power Supplies
J9306A
Redundancy Model Non-redundant
Power
Available
@110-
127 V
@200-
240 V
N + 1
or full
Redundant
PoE/PoE+
Power
Non-Redundant
PoE Power
PoE Power (50v)
Internal
1 0 - None 300 W
2 0 Full Up to 300 W 600 W
0 1 - None 900 W
0 2 Full Up to 900 W 1800 W
With External
Power supplies
added
3 0 N + 1 Up to 600 W 900 W
4 0 Full Up to 600 W 1200 W
0 3 N + 1 Up to 1800 W 2700 W
0 4 Full Up to 1800 W 3600 W

» Return to top

Q: What are the different power configurations for the 5412zl and 8212zl with the 3 power supplies?

  Number of Power Supplies Redundancy Model
J8712A
(110 or 220 V)
J8713A
(220 V only)
J9306A N + 1
or full
Redundant
System Power
@110-
127 V
@200-
240 V
System
Power
(12V)
2 2 2 2 - None
3 3 3 3 N + 1 Up to 1200 W system power
4 4 4 4 Full Up to 1200 W system power

» Return to top

Q: What are the different power configurations for PoE only (not PoE+) with the 5412zl and 8212zl?

Switch Model
5406zl/8206zl
Number of Power Supplies Redundancy Model Non-redundant
Power
Available
J8712A
(110 or 220 V)
J8713A
(220 V only)
N + 1 or full Redundant
PoE Power
Non-Redundant
PoE Power
PoE Power (50v)
Internal
2 0 - None 546 W
3 0 N + 1 Up to 546 W 819 W
4 0 Full Up to 546 W 1092 W
0 2 - None 1800 W
0 3 N + 1 Up to 1800 W 3600 W
0 4 Full Up to 1800 W 3600 W
With External
Power supplies
added
5 0 N + 1 Up to 1092 W 1365 W
6 0 Full Up to 819 W 1638 W
0 5 N + 1 Up to 3600 W 4500 W
0 6 Full Up to 2700 W 5400 W
Mixed PoE Power
(Not recommended)
2 1 N + 1 Up to 273 W 1446 W
1 2 N + 1 Up to 900 W 2073 W
2 2 N + 1 Up to 1173 W 2346 W

» Return to top

Q: What are the different power configurations for PoE/PoE+ with the 5412zl and 8212zl?

Switch Model
5406zl/8206zl
Number of Power Supplies
J9306A
Redundancy Model Non-redundant
Power
Available
@110-
127 V
@200-
240 V
N + 1 or full Redundant PoE/PoE+
Power
Non-Redundant
PoE/PoE+
Power
PoE Power (50v) Internal 2 0 - None 600 W
3 0 N + 1 Up to 300 W 900 W
4 0 Full Up to 600 W 1200 W
0 2 - None 1800 W
0 3 N + 1 Up to 900 W 2700 W
0 4 Full Up to 1800 W 3600 W
With External
Power supplies
added
5 0 N + 1 Up to 1200 W 1500 W
6 0 Full Up to 900 W 1800 W
0 5 N + 1 Up to 1800 W 4500 W
0 6 Full Up to 1800 W 5400 W

» Return to top

Redundancy

Q: How long does it take for the Standby management module to take control if the Active management module fails.
At initial release of the 8212zl Switch, the switch will begin forwarding traffic anywhere from 40 seconds to 2 minutes, depending on the complexity of the configuration file and network reconvergence times.

» Return to top

Q: How do the management modules interact with each other?
When the switch boots up, the management modules run selftest and then decides which is the active module and which is the standby module.  The module that becomes active finishes booting and then brings up the interface modules and ports. The standby module boots to a certain point, synchronizes basic files such as the config and security files, and only finishes booting if the active management module fails or the administrator choose to change which module is the active module. 

The two management modules communicate by sending heartbeats back and forth. The active management module continuously synchronizes the stored configuration and security files with the standby module. If the active management module fails, the standby management module becomes the active module and finishes the boot process by reading the stored config file, resetting the interface modules, and bringing up the ports. 

The running configuration file, not yet saved with the “write memory” command, is not synchronized between management modules.  The management module that becomes the “active” module will be the one that is booted going forward.

» Return to top

Q: Are the management modules hot swappable?
The management modules are designed to be hot-swappable, and can be removed from the chassis without damage. The synchronization of files (configuration, code images, state and default condition directives) may indeed be occurring, so to minimize the possibility of corruption between MMs, when manually removing the module, use the “MM Shutdown” button. The “MM Shutdown” is a recessed button used to gracefully shutdown the management module, completing any synchronization of files and state information to the second management module. When the “Down” LED is lit, the management module can be removed.

» Return to top

Q: Can the 8212zl switch function without a management module in the system?
The ProCurve Switch 8212zl Series requires at least a single management module that oversees (or “supervises”) the operation of the interface modules and fabric modules. If both management cards are removed the system will shutdown. The management module is responsible for network control processing (e.g., OSPF updates or ARP requests), while each interface module in conjunction with the fabric modules handles the traffic switching in ASIC hardware.

» Return to top

Q: If my active management module fails and the Standby management module becomes active, will the 8212zl lose its configuration?
No, by default, the active management module is always synchronizing Flash Images (both Primary and Secondary images), stored configuration files, and start-up directives. Running configuration files are NOT synchronized and are lost upon a management module switchover event.

» Return to top

Q: Can you disable the synchronizing of configurations between the active management module and the standby management module?
Yes, the command to disable the management cards from synchronizing is “no redundancy management-module”.  After executing the command you are prompted with this message: “The other management module may reboot and it will no longer be used for system redundancy except in the case of a hardware failure of the active management module. Do you want to continue [y/n]?”. Selecting “y” disables redundant management.

» Return to top

Q: Can you manually force the standby management module to become the active module?
Yes, the command is “redundancy switchover”.

» Return to top

Q: What are the events that cause management modules to switchover?
There are a number of events that can cause the active management module to switchover to the standby management module when redundancy is enabled:

  • The standby management module has not received a heartbeat for some time from the active management module
  • The redundancy switchover command is executed
  • The active management module is hotswapped out
  • The MM Reset button on the active management module is pressed
  • The MM Shutdown button on the active management module is pressed
  • The boot or boot active command is executed
  • The reload command is executed
  • There is a hardware failure on the active management module
  • The active management module crashes

In all of these cases the standby management module takes control and performs the actual switchover. The reason for the switchover is entered in log messages on the newly active management module and to any configured Syslog servers.

» Return to top

Q: What events do not cause a management switchover to occur?
Below are the events for which a switchover is not triggered:

  • When a boot system command is executed
  • When the Reset button on the System Support module is pressed
  • When redundancy is disabled, unless there is a hardware failure and the system is rebooted.

» Return to top

Q: What commands are available to help understand current redundancy configuration?
The commands that display current redundancy configuration are:

  • show redundancy
  • show flash
  • show version

Examples of each below:

Below is the output of show redundancy:
Output of show redundancy

Below is an example of show flash:
Output of show flash

Below is an example of show version:
Output of show version

Below is an example of show flash with redundancy turned off:
Output of show flash with redundancy turned off

» Return to top

Q: What existing CLI commands are affected by Redundant Management?

Command

Action

boot<cr>

Reboots active management module from the flash image that is specified for the default boot.  This can be changed with the “boot set-default flash” command.

boot active

Boots the active management module.  The switch starts to boot from the default flash image.  You can select which image to boot from during the boot process.  He switch will switchover to the standby module.  If a second management module is not present in the switch, the system is rebooted.

b oot standby

Boots the standby management module.  The switch does not switchover if the standby module is not present, this message displays “The other management module is not present”

b oot system
[flash < primary| secondary>]

Boots both the active and standby management modules.  You can specify the flash image to boot from.

b oot set-default [flash < primary| secondary>]

Sets the default flash for the next boot to primary or secondary. You will see this message:
“This command changes the location of the default boot. This command will change the default flash image to boot from <flash chosen>. Hereafter, ‘reload’ and ‘boot’ commands will boot from <flash chosen>. Do you want to continue [y/n]?”

r eload<cr>

Boots (warm reboot) the active management module.  Switchover to the standby management module occurs if redundancy is enabled. If redundancy is disabled or there is no standby management module, the reload command boots the system.
Note: If the running config file is different from the stored config file, you will be prompted to save the config file. The reload at/after versions of this command do not display a prompt to save configuration file changes; the changes are lost on the scheduled reload.

a uto-tftp

If a new image is downloaded using auto-tftp, the active management module downloads the new software version to both the active and standby modules. Rebooting after the auto-tftp completes reboots the entire system.

banner

The banner will not been seen on the standby module, only the active module.

chassislocate

If the management module performs a switchover, the LED does not remain lit.

clear

The clear crypto command causes public keys to be deleted from both modules when the second module is in standby mode.

console

Console settings, such as mode, flow-control, and baud-rate, are the same on both management modules. There cannot be individual settings for each management module.

copy

Files are automatically sync’d from the active management module to the standby management module.  When no parameter is specified with the copy crash-data or copy
crash-log command, files from all modules (management and interface) are concatenated.
Note: If redundancy is disabled or the standby module failed selftest, the copy command affects only the active management module.

crypto

Authentication files for ssh or the https server are copied to the standby management module. The clear crypto command deletes the public keys from both modules when the second module is in standby mode.

e rase flash

Erases the software version on the active and standby modules. If redundancy has been disabled, or the standby module has not passed selftest, the flash is not erased on the standby module.

e rase config

Erases the config file on the active and standby modules. If redundancy has been disabled, or the standby module has not passed selftest, the config file is not erased on the standby module.

e rase startup-config

Affects both modules if the second module is in standby mode. If redundancy has been disabled, or the standby module has not passed selftest, the startup-config file is not erased on the standby module.

fastboot

When fastboot is enabled, this information is saved to the standby management module when the config files are sync’d. The fastboot value is used during the next boot on both modules.

front-panel-security
factory-reset
password-clear
password-recovery

This command and its options only affects the active management module. See “Front-Panel Button Functions” on page 2-24 in the Access Security Guide for more information about resetting the switch.

kill

Does not affect the console on the standby module.

log

Log messages from a formerly active management module are available on the current active management module after a switchover.

p assword (set or clear)

Affects only the active management module until a switchover occurs, at which time it affects the new active module. The new password information is sent to the standby module and takes effect when a switchover occurs.

startup-default

Affects both modules. The config file is immediately sent to the standby module and also becomes the default on that module when the next boot occurs.

update

Only affects the active module. The standby may become the active module when the updated active module is booted.

write

A write memory updates the config file in flash on the active module. The file is then sync’d to the standby module.

» Return to top

Q: Are the 8212zl Fabric modules redundant or resilient?
The 8212zl fabric modules are resilient. There are two fabric modules in chassis. If a fabric module fails, the remaining fabric module will continue forwarding traffic, resulting in a 50 percent reduction in throughput.

» Return to top

Accessories

Q: What modules only work in the 8200zl and not in the 5400zl?
The modules that only work in the 8200zl series and not the 5400zl are the management, fabric, and system support modules. These modules are specific to the 8200zl series products. The 5400zl has the same components integrated into the chassis. Below is more information on each module:

ProCurve Switch 8212zl Management Module (J9092A)
ProCurve Switch 8200zl Management Module (J9092A)

Module for use with Switch 8200zl chassis. With RJ-45 serial console port for out-of-band management access.

ProCurve Switch 8212zl Fabric Module (J9093A)
ProCurve Switch 8200zl Fabric Module (J9093A)

Switch 8200zl Fabric Module. Ordered by customers for onsite sparing only (base configuration J8715A and J9475A includes required fabric modules).

ProCurve Switch 8212zl System Support Module (J9095A)
ProCurve Switch 8200zl System Support Module (J9095A)

Switch 8200zl System Support Module. Ordered by customers for onsite sparing only (8212zl base system J8715A comes with required module).

» Return to top

Q: What types of interface modules are supported in ProCurve 8212zl Switches?
All zl modules work in the 8212zl and the 5400zl switches. Below is more information on each module:

HP ProCurve Switch zl 24 port Gig-T PoE Module (J8702A)
HP ProCurve Switch zl 24 port Gig-T PoE Module (J8702A)1

Ports
24 RJ-45 auto-sensing 10/100/1000 ports (IEEE 802.3 Type 10Base-T, IEEE 802.3u Type 100Base-TX, IEEE 802.3ab Type 1000Base-T)

Media Type: Auto-MDIX
Duplex: 10Base-T/100Base-TX: half or full; 1000Base-T: full only

Cabling
Type: 1000Base-T: Category 5 (5E or better recommended), 100 Ω differential 4-pair unshielded twisted pair (UTP) or shielded twisted pair (STP) balanced, complying with IEEE 802.3ab 1000Base-T

HP ProCurve Switch zl 20 port Gig-T + 4 port mGBIC Module (J8705A)
HP ProCurve Switch zl 20 port Gig-T + 4 port mGBIC Module (J8705A)1

Ports
4 open mini-GBIC (SFP) slots -
20 RJ-45 auto-sensing 10/100/1000 ports (IEEE 802.3 Type 10Base-T, IEEE 802.3u Type 100Base-TX, IEEE 802.3ab Type 1000Base-T)

Media Type: Auto-MDIX
Duplex: 10Base-T/100Base-TX: half or full; 1000Base-T: full only

Notes:
When using mini-GBICs with this product, mini-GBICs with revision "B" or later (product number ends with the letter "B" or later, e.g., J4858B, J4859C) are required.

When installed in a zl chassis, the J8705A module limits the operating temperature range of the chassis to 32°F to 104°F (0°C to 40°C).

HP ProCurve Switch zl 24 port mini-GBIC Module (J8706A)
HP ProCurve Switch zl 24 port mini-GBIC Module (J8706A)2

Ports
24 open mini-GBIC (SFP) slots

Notes
When using mini-GBICs with this product, mini-GBICs with revision "B" or later (product number ends with the letter "B" or later, e.g., J4858B, J4859C) are required.

When installed in a zl chassis, the J8706A module limits the operating temperature range of the chassis to 32°F to 104°F (0°C to 40°C).

HP ProCurve Switch zl 4 port 10-GbE X2 Module (J8707A)
HP ProCurve Switch zl 4 port 10-GbE X2 Module (J8707A)1

Ports
4 open 10-GbE X2 transceiver slots

Notes
When installed in a zl chassis, the J8707A module limits the operating temperature range of the chassis to 32°F to 104°F (0°C to 40°C).

HP ProCurve Switch zl 4 port 10-GbE CX4 Module (J8708A)
HP ProCurve Switch zl 4 port 10-GbE CX4 Module (J8708A)2

Ports
4 CX4 10-GbE ports (IEEE 802.3ak Type 10Gbase-CX4)

Duplex: full only

Cabling
Maximum distance:15 m using CX4 cable
300 m using optical media converters and multimode fiber cable

Notes
Use CX4 10-GbE cable (0.5 m-15 m) or HP ProCurve 10-GbE CX4 Media Converter (J8439A).
No CX4 cables are included with this module.

HP ProCurve 24-Port 10/100/1000 PoE+ zl Module (J9307A)
HP ProCurve 24-Port 10/100/1000 PoE+ zl Module (J9307A)3

Ports
24 RJ-45 auto-sensing 10/100/1000 ports (IEEE 802.3 Type 10Base-T, IEEE 802.3u Type 100Base-TX, IEEE 802.3ab Type 1000Base-T)

Media Type: Auto-MDIX
Duplex: 10Base-T/100Base-TX: half or full; 1000Base-T: full only

Cabling
Type: 1000Base-T: Category 5 (5E or better recommended), 100 Ω differential 4-pair unshielded twisted pair (UTP) or shielded twisted pair (STP) balanced, complying with IEEE 802.3ab 1000Base-T.

HP ProCurve 20-Port 10/100/1000 PoE+ / 4-Port mini-GBIC zl Module (J9308A)
HP ProCurve 20-Port 10/100/1000 PoE+ / 4-Port mini-GBIC zl Module (J9308A)3

Ports
24 RJ-45 auto-sensing 10/100/1000 ports (IEEE 802.3 Type 10Base-T, IEEE 802.3u Type 100Base-TX, IEEE 802.3ab Type 1000Base-T)

Media Type: Auto-MDIX
Duplex: 10Base-T/100Base-TX: half or full; 1000Base-T: full only

Cabling
Type: 1000Base-T: Category 5 (5E or better recommended), 100 Ω differential 4-pair unshielded twisted pair (UTP) or shielded twisted pair (STP) balanced, complying with IEEE 802.3ab 1000Base-T.

HP ProCurve 24-Port 10/100 PoE+ zl Module (J9478A)
HP ProCurve 24-Port 10/100 PoE+ zl Module (J9478A)3

Ports
24 RJ-45 auto-sensing 10/100 ports (IEEE 802.3 Type 10Base-T, IEEE 802.3u Type 100Base-TX)

Media Type: Auto-MDIX
Duplex: half or full

Cabling
Type: 100Base-TX: Category 5 (or better), 100 Ω differential unshielded twisted pair (UTP) or shielded twisted pair (STP), complying with IEEE 802.3u 100Base-TX

HP ProCurve 4-Port 10-GbE SFP+ zl Module (J9309A)
HP ProCurve 4-Port 10-GbE SFP+ zl Module (J9309A)3

Ports
4 open 10-GbE SFP+ transceiver slots

Notes
When installed in a zl chassis, the J9309A module limits the operating temperature range of the chassis to 32F to 113F (0C to 45C).

HP ProCurve Wireless Edge Services zl Module (J9051A)
HP ProCurve Wireless Edge Services zl Module (J9051A)4

Working in conjunction with ProCurve radio ports, the ProCurve Wireless Edge Services zl Module provides centralized wireless LAN management of advanced wireless services, enabling a highly secure, multi-service network on ProCurve zl switches.

HP ProCurve Redundant Wireless Services zl Module (J9052A)
HP ProCurve Redundant Wireless Services zl Module (J9052A)4

The ProCurve Redundant Wireless Services zl Module automatically adopts ProCurve radio ports if the primary Wireless Edge Services zl Module is unavailable or fails.

HP ProCurve MSM765zl Mobility Controller (J9370A)
HP ProCurve MSM765zl Mobility Controller (J9370A)

HP ProCurve MSM765zl Mobility Controller delivers a high-performance networking solution. Built on the HP ProCurve One Services zl Module platform, it provides centralized wireless LAN configuration and management of advanced wireless services.

» Return to top

Q: How can I get the best performance from a 4 port 10G module considering each module only gets 28.8G throughput to the switch fabric?
When more than two ports of a 10-GbE module are in a linked state, ports 1 and 4 are statically mapped to share one 14.4 Gbps channel, while ports 2 and 3 are statically mapped to share the other 14.4 Gbps channel.  If only one port in a given channel is in a linked state, then that port operates at wirespeed and the other port uses no bandwidth.  If both ports in a given channel are in a linked state, then the 14.4 Gbps of bandwidth is balanced fairly between the two ports.  For example, in an application where three ports on the module are needed and it is important to ensure that port 1 always has a full 10 Gbps available.  Refer to diagram below:

hey

» Return to top

Q: If I only have two 10G connections on one module how do I guarantee each port gets 10G?
When any two 10-GbE ports on a given module are in a linked state, each port automatically operates on its own channel, which guarantees 10 Gbps of bandwidth for each port. The two ports are dynamically mapped to an available high-speed channel and support full 10 Gbps wirespeed operation.

» Return to top

Q: Is the 8212zl fan tray field replaceable?
Yes, the Fan tray is field replaceable. Once a fan tray is removed, if a replacement does not get inserted within three minutes the chassis will power down. The part number for the fan tray is J9094A.

» Return to top

Q: What are the part numbers for the field replaceable parts for the 8212zl?

Part Number

Components

J9091A
J9091-69001

8212zl Chassis (with Fan Tray)
Warranty replacement for 8212zl Chassis (with Fan Tray)

J9092A
J9092-69001

8212zl Management Module
Warranty replacement 8212zl Management Module without CF card

J9093A
J9093-69001

8212zl Fabric Module
Warranty replacement 8212zl Fabric Module

J9094A
J9094-69001
J9095A
J9095-69001

8212zl Fan Tray
Warranty replacement 8212zl Fan Tray
8212zl System Support Module
Warranty replacement 8212zl System Support Module

5070-2983

Two-post Rack Mounting Kit for Switch 8212zl

5070-3051

Programmed CompactFlash Kit for 8212zl Management Module

5188-6699

RJ45-to-DB9 Console cable for 8212zl

5070-8562

Four-post 19 inch rack

» Return to top

Q: Which mini-GBICs are supported on the ProCurve 8212zl Switch?
For the most current information on ProCurve mini-GBICs for your switch, refer to the datasheet:

  1. Go to: http://www.hp.com/rnd/library/index.htm
  2. Scroll to ProCurve Switch 8212zl datasheet then click to select.
  3. Scroll to the information on mini-GBICs.

This product requires ProCurve revision "B" or later mini-GBICs (product number ends with the letter "B", for example J4858B, J4859B). These switches do not support revision "A" mini-GBICs. Non-ProCurve mini-GBICs are not supported. Use of genuine products ensures that your network maintains optimal performance and reliability. Should you require additional ProCurve mini-GBICs, please contact a ProCurve sales representative or an authorized reseller.

ProCurve Gigabit-SX-LC Mini-GBIC (J4858B)

ProCurve Gigabit-SX-LC Mini-GBIC (J4858B)

Transceiver type

Fiber type

Core diameter (microns)

Modal
bandwidth
(MHz*km)

Supported range
(meters)

Gigabit-SX

Multimode

62.5

160

2 to 220 (note 1)

Gigabit-SX

Multimode

62.5

200

2 to 275 (note 2)

Gigabit-SX

Multimode

50

400

2 to 500

Gigabit-SX

Multimode

50

500

2 to 550 (note 3)

ProCurve Gigabit-LX-LC Mini-GBIC (J4859B)

ProCurve Gigabit-LX-LC Mini-GBIC (J4859B)

Transceiver type

Fiber type

Core diameter (microns)

Modal
bandwidth
(MHz*km)

Supported range
(meters)

Gigabit-LX

Multimode

62.5

500

2 to 550 (note 4)

Gigabit-LX

Multimode

50

400

2 to 550 (note 4)

Gigabit-LX

Multimode

50

500

2 to 550 (note 4)

Gigabit-LX

Singlemode

9

N/A

2 to 10,000 (note 5)

ProCurve Gigabit-LH-LC Mini-GBIC (J4860B)

ProCurve Gigabit-LH-LC Mini-GBIC (J4860B)

Transceiver type

Fiber type

Core diameter (microns)

Modal
bandwidth
(MHz*km)

Supported range
(meters)

Gigabit-LH

Singlemode

9

N/A

10 to 70,000 (note 6)

ProCurve Gigabit 1000Base-T Mini-GBIC (J8177B)

ProCurve Gigabit 1000Base-T Mini-GBIC (J8177B)

Transceiver type

Cable type

Duplex

Speeds

Supported range (meters)

Gigabit-1000Base T

5E or better Recommended

Full only

1000Base-T only

1 to 100

ProCurve 100-FX SFP-LC Transceiver (J9054B)

ProCurve 100-FX SFP-LC Transceiver (J9054B)

Transceiver type

Fiber type

Core diameter (microns)

Modal
bandwidth
(MHz*km)

Supported range
(meters)

100BASE-FX

Multimode

62.5 or 50

N/A

up to 2,000

Notes:

  1. The TIA 568 building wiring standard specifies 160/500 MHz*km multimode fiber.
  2. The international ISO/IEC 11801 building wiring standard specifies 200/500 MHz*km multimode fiber.
  3. The ANSI Fibre Channel specification specifies 500/500 MHz*km 50 micron multimode fiber, and 500/500 MHz*km fiber has been proposed for addition to ISO/IEC 11801.
  4. When using the LX mini-GBIC in 50 µm or 62.5 µm multimode fiber (MMF) operation, a mode-conditioning patch cord may be required at each end of the link.
  5. ProCurve supports up to 10,000 meters, which is the IEEE 1000BASE-LX10 standard. (The IEEE 1000BASE-LX standard supports up to 5000 meters.)
  6. The transmission distances are dependent on the particular fiber loss and coupling loss involved, among other factors, and can be estimated from the optical loss budget. For distances less than 20km, a 10dB attenuator must be used. For distances between 20km and 40km, a 5dB attenuator must be used. Attenuators can be purchased from most cable vendors.

» Return to top

Q: What types of 10-GbE transceivers are supported in the ProCurve 8212zl Switch?
For the most current information on ProCurve transceivers for your switch, refer to the datasheet:

Scroll to ProCurve Switch 8212zl datasheet then click to select Scroll to the information on transceivers.

ProCurve 10-GbE X2-SC SR Optic (J8436A)

ProCurve 10-GbE X2-SC SR Optic (J8436A)

Transceiver type

Fiber type

Core diameter (microns)

Modal bandwidth (MHz*km)

Supported range (meters)

10GBase-SR

multimode

62.5

160

2 to 26

10GBase-SR

multimode

62.5

200

2 to 33

10GBase-SR

multimode

50

400

2 to 66

10GBase-SR

multimode

50

500

2 to 82

10GBase-SR

multimode

50

2000

2 to 300

ProCurve 10-GbE X2-SC LR Optic (J8437A)

ProCurve 10-GbE X2-SC LR Optic (J8437A)

Transceiver type

Fiber type

Core diameter (microns)

Modal bandwidth (MHz*km)

Supported range (meters)

10GBase-LR

single mode

9

N/A

2 to 10,000

ProCurve 10-GbE X2-SC ER Optic (J8438A)

ProCurve 10-GbE X2-SC ER Optic (J8438A)


Transceiver type

Fiber type

Core diameter (microns)

Modal bandwidth (MHz*km)

Supported range (meters)

10GBase-ER

single mode

9

N/A

2 to 30,000*

* Maximum distance 40 km using engineered link.

ProCurve 10-GbE CX4 Media Converter (J8439A)


Transceiver type

Fiber type

Core diameter (microns)

Modal bandwidth (MHz*km)

Supported range (meters)

CX4 Optical Media Converter

multimode

62.5

150

1 to 50

CX4 Optical Media Converter

multimode

50

500

1 to 100

CX4 Optical Media Converter

multimode

50

2000

1 to 300

ProCurve Switch 10-GbE X2-CX4 Transceiver (J8440B)

ProCurve Switch 10-GbE X2-CX4 Transceiver (J8440B)


Transceiver type

CX4 cable vendors

Supported range (meters)

CX4

Gore Electronics
Molex
Amphenol

1 to15

» Return to top

Q: What precautions should I follow when removing the J8177B gigabit-copper mini-GBIC from my switch?
To remove the J8177B from a mini-GBIC slot on the switch, follow this procedure:

  1. Remove the attached cable from the mini-GBIC.
  2. Without forcing the latch, swivel the latch 90 degrees to the unlocked position.

CAUTION: Do not force the latch! If the latch does not easily swivel 90 degrees, move the latch back to the locked position, re-seat the mini-GBIC by pressing it into the switch, then repeat step 2.

» Return to top

Q: Which ProCurve mini-GBICs and SFPs are supported in which ProCurve products?
The ProCurve Networking Mini-GBIC Support Matrix specifies which mini-GBICs and SFPs are supported on which ProCurve products. General rules are:

  • Only genuine ProCurve mini-GBICs and SFPs are supported on ProCurve products.
  • The J8177B 1000Base-T mini-GBIC is not supported in "dual personality" ports (which already include a gigabit copper LAN port).

Newer ProCurve products require revision "B" or later mini-GBICs and SFPs (product number ends with the letter "B" or later, for example J4858B, J4859B).

» Return to top

Features/Protocols

Q: Are Jumbo frames supported on the ProCurve 8212zl series switches?
Yes. Ports operating at 1 Gbps or 10 Gbps speeds accept forward packets of up to 9220 bytes (including four bytes for a VLAN tag) when configured for jumbo traffic. Note that on ports operating at 10 Mbps or 100 Mbps, the Maximum Transmission Unit (MTU) is fixed at 1522 bytes. The switch drops any inbound packets larger than the MTU allowed on a port.

» Return to top

Q: Are Jumbo frames enabled per VLAN or per physical interface?
Inbound jumbo packets are enabled on a per-VLAN basis. That is, on a VLAN configured for jumbo traffic, all ports belonging to that VLAN and operating at 1 Gbs or 10 Gbps allow inbound jumbo packets of up to 9220 bytes.

» Return to top

Q: What type of spanning tree implementation do the ProCurve 8212zl switches support?
IEEE 802.1s Multiple Spanning Tree Protocol is supported.

» Return to top

Q: How would MSTP interact with switches that support only 802.1D STP or 802.1w RSTP?
MSTP is backward-compatible with the RSTP-enabled and STP-enabled switches in your network. Use the following command to optimize this interoperability.

ProCurveSwitch8200zl (config)# spanning-tree force-version < stp-compatible | rstp-operation | mstp-operation>

An excerpt from the parameter descriptions follows.

For more detail, please see the Advanced Traffic Management Guide for the ProCurve 8212zl Switch.

stp-compatible: The switch applies 802.1D STP operation on all ports.
rstp-operation: The switch applies 802.1w operation on all ports except those ports where it detects a system using 802.1D Spanning Tree.

» Return to top

Q: What advantage does implementation of IEEE 802.1s MSTP offer over legacy STP or RSTP?
The 802.1D and 802.1w spanning tree protocols operate without regard to a network's VLAN configuration, and maintain one common spanning tree throughout a bridged network. Thus, these protocols map one loop-free, logical topology on a given physical topology. This causes redundant links to be blocked; they are then available on a standby basis. With MSTP, each spanning tree instance can include one or more VLANs and applies a separate, per-instance forwarding topology. Thus, when a port belongs to multiple VLANs, it may be dynamically blocked in one spanning tree instance, but forwarding in another instance. This achieves load-balancing across the network while still providing fault tolerance through rapid, automatic reconfiguration if there is a failure in a network's physical topology.

» Return to top

Q: Will the ProCurve 8212zl support routing when Switch Meshing is enabled?
No. If meshing is configured on the switch, the routing features (IP routing, RIP, and OSPF) must be disabled. The switch's meshing and routing features cannot be enabled at the same time.

» Return to top

Q: When configured for meshing, is the ProCurve 8212zl switch backwards-compatible with older model ProCurve switches that support meshing?
The ProCurve 8212zl switch is compatible with the meshing feature on the 5400zl, 3500yl, 6200yl, 5300xl and 3400cl Series switches. There is no backward-compatibility mode for interoperation with a ProCurve Switch 4000M mesh.

» Return to top

Q: How does UDP Broadcast Forwarding work?
Some applications rely on client requests sent as limited IP broadcasts addressed to a UDP application port. If a server for the application receives such a broadcast, the server can reply to the client. Since typical router behavior, by default, does not allow broadcast forwarding, a client's UDP broadcast requests cannot reach a target server on a different subnet unless the router is configured to forward client UDP broadcasts to that server.

A switch with routing enabled includes optional per-VLAN UDP broadcast forwarding that allows up to 256 server and/or subnet entries on the switch (16 entries per-VLAN). If an entry for a particular UDP port number is configured on a VLAN and an inbound UDP broadcast packet with that port number is received on the VLAN, then the switch routes the packet to the appropriate subnet. Each entry can designate either a single device or a single subnet.

For configuration details, please see the Multicast and Routing Guide for these switches.

» Return to top

Q: Can 802.1X, Web-based authentication, and MAC-based authentication all be used concurrently on a switch port?
Yes. Details about configuring these features may be viewed in the ProCurve 8212zl Access Security Guide.

» Return to top

Q: Are there limits to the number of Access Control Entries (ACEs) supported within an Access Control List (ACL)?
The total number of supported ACEs in all the ACLs depends on the combined resource usage by ACL, QoS, IDM, Virus-Throttling, ICMP, and Management VLAN features. For more on this topic, refer to the appendix titled “Monitoring Resources” in the 8200zl Management and Configuration Guide.

» Return to top

Q: Is there a limit to the number of ACLs supported by the 8212zl?
You can configure up to 2048 ACL assignments to VLANs, as follows:

  • Named (Extended or Standard) ACLs: Up to 2048 (minus any numeric ACL assignments)
  • Numeric Standard ACLs: Up to 99; numeric range: 1 - 99
  • Numeric Extended ACLs: Up to 100; numeric range: 100 - 199
  • Total ACEs in all ACLs: Depends on the combined resource usage by ACL, QoS, IDM, Virus-Throttling, ICMP, and Management VLAN features

» Return to top

Q: How does Source port filtering work?
When you create a source-port filter, the switch automatically sets the filter to forward traffic from the designated source to all destinations for which you do not specifically configure a "drop" action. Thus, it is not necessary to configure a source-port filter for traffic you want the switch to forward unless the filter was previously configured to drop the desired traffic. Details about configuration of the filter command can be reviewed in the Access Security Guide for the 8212zl product.

» Return to top

Q: What are the default DSCP codepoint values?
The DSCP Policy Table associates an 802.1p priority with a specific ToS byte codepoint in an IPv4 packet. This enables you to set a traffic management policy that operates independently of 802.1Q VLAN-tagging. In the default state, most of the 64 codepoints do not assign an 802.1p priority, as indicated by "No-override" value in the table below.

No-override values

You can use the [show] qos dscp-map command to list the current DSCP Policy table, change the codepoint priority assignments, and assign optional names to the codepoints.

» Return to top

Q: Does the 8212zl support sFlow?
Yes, the 8212zl support sFlow.  sFlow is a technology for monitoring traffic in data networks containing switches and routers.  In particular, it defines the sampling mechanisms implemented in an sFlow Agent for monitoring traffic, the sFlow MIB for controlling the sFlow Agent, and the format of sample data used by the sFlow Agent when forwarding data to a central data collector.

The 8212zl Switches support up to three instances of sFlow, which you can configure either using SNMP (like ProCurve Manager would do), or from the CLI.

» Return to top

Q: How do I enable sFlow support on the ProCurve 8212zl switch using a network management application? Must I configure anything on the switch?
If you are using ProCurve Manager Plus (PCM+) for traffic monitoring on your switches, no further CLI configuration is necessary. sFlow monitoring requires the use of a management software application such as ProCurve Manager Plus 2.0 which receives, collects, and displays the traffic data. The process of configuring the management application for data collection involves sending snmp set commands that trigger the switch to send the sFlow data. Please see the configuration examples for further information on the snmp set commands used.

To allow the management station to configure the sFlow parameters, the software will need to be configured with valid read and write SNMP community names or valid SNMPv3 configuration information that matches what is configured on the switch.

The show sflow command set may be used to view various aspects of the sFlow configuration and status.

» Return to top

Q: How do I take advantage of multiple configuration files?
The switch allows up to three startup-config files with options for selecting which startup-config file to use for:

  • A fixed reboot policy using a specific startup-config file for a specific boot path (primary or secondary flash)
  • Overriding the current reboot policy on a per-instance basis

multiple configuration files

While you can still use remote storage for startup-config files, you can now maintain multiple startup-config files on the switch and choose which version to use for a reboot policy or an individual reboot.

This choice of which configuration file to use for the startup-config at reboot provides the following new options:

  • The switch can reboot with different configuration options without having to exchange one configuration file for another from a remote storage location.
  • Transitions from one software release to another can be performed while maintaining a separate configuration for the different software release versions.
  • By setting a reboot policy using a known good configuration and then overriding the policy on a per-instance basis, you can test a new configuration with the provision that if an unattended reboot occurs, the switch will come up with the known, good configuration instead of repeating a reboot with a misconfiguration.

» Return to top

Q: What is the benefit of maintaining current software on my ProCurve Switch?
One of the benefits of owning a ProCurve product is free software updates. Maintaining current software can proactively add to the reliability of your product. In addition to addressing occasional issues in new software versions, ProCurve Networking also adds features and enhancements to software which provide investment protection by extending the value and functional life of products. A proactive notification service is available on the MyProCurve portal. This service generates an e-mail alert when the product line you select has a new version of software posted to the ProCurve web site.

» Return to top

Q: Why doesn't the VRRP backup router respond to pings when it is in the master role?
This behavior is by design, and is required by section 6.4.3 of the VRRP RFC 3768. The backup router will forward traffic as appropriate for its gateway role, but will not respond to ping. The failed ping response is often an important mechanism for reporting the failover which has occurred on the network segment.

» Return to top

Q: Why don't the 8212zl Switches support CDP?
ProCurve Networking Business recommends IEEE standards-based features for device discovery. To this end, the IEEE 802.1ab standard Link Layer Discovery Protocol (LLDP) is supported. It provides for device discovery for network management platforms and switch neighbor discovery.

» Return to top

Q: Does the (link aggregation) trunking algorithm for the ProCurve 8212zl Series switches take into account IP addresses when allocating sa/da individual traffic flows to the individual links of a trunk?
Yes, ProCurve uses IP addressing in the hashing decisions that determine which link a packet traverses after it is routed on the 8200.

» Return to top

Q: Does the 8212zl support remote port mirroring?
Yes, the 8200 supports remote port mirroring.  With ProCurve’s traffic mirroring on the 8200, 5400, 3500 and 6200, you no longer need to monitor a port on every switch. Instead, you can send mirrored data from multiple remote switches to one local switch. The security appliance attached to this local switch can then monitor all the mirrored data, reducing the number of security appliances you need on your network.

» Return to top

Q: Which USB Flash Drives have been tested with the ProCurve 8212zl switches and what were the findings?

USB Flash Drive Tested

Result/Notes

Belkin 128MB F5U025-128MB

Works without issue

BUSlink BDP-128-U2

Works without issue

FujiFilm 25910364

Works without issue

HP PH6557A 256 MB

Works without issue

HP RK534AA 1 GB

Works without issue

HP RK535AA 2 GB

Works without issue

Kingston DataTraveler 256 MB

Works without issue

Lexar JumpDrive 512 MB

Works without issue

Memorex TravelDrive 256MB

Works without issue

PNY Attache 128MB P-FD128U20-RF

Works without issue

ProCurve branded JMTek 128MB

Works without issue

SanDisk Cruzer Titanium 512

Works without issue

SanDisk Cruzer Mini 512

Works without issue

Sandisk Cruzer Mini 256

Works without issue

Sandisk Cruzer Micro 256

Works without issue

Verbatim 128MB 95023

Works without issue

Viking InterWorks 256MB 910VI256USB-P00

Works without issue

SimpleTech Bonzai Xpress 128

Works without issue

SimpleTech Bonzai Xpress 256

Works without issue

Sony MicroVault 512

Works without issue; if unformatted, format on PC; do not use security software

USB Flash Drive Tested

Problem on ProCurve switch

Sonnet Piccolo 512

Switch file system doesn't see drive; Reformat did not work

Sony MicroVault 256

Will not work. Needs USM Finger Print Software driver.

» Return to top

Q: Is it okay to use USB flash drives that have not been tested?
Yes. Most USB flash drive devices (under 32 GB ) using a FAT file system should work.

» Return to top

Q: What should I do if the USB flash drive file system is not recognized by the ProCurve switch?
Check the format on a PC.  If the device is unformatted, formatting it may enable it to work.  Use only a FAT file system.  ProCurve switches do not support the NTFS file system.

» Return to top

Q: What are the USB flash drive support limitations?
The USB port supports connection to a single USB mass storage device.  USB hubs to add more ports are not supported.

For devices with multiple partitions, only the first partition is supported.  Devices with secure partitions are not supported.

» Return to top

Q: Does the 8212zl support rate limiting?
Yes, the 8212zl supports rate limiting.  Traffic rate-limiting applies to both inbound and outbound traffic; you can specify bandwidth usage in terms of bits per second (bps).

» Return to top

Software

Q: Can I load the same software version on my 8206zl that I run on my 8212zl?
Yes, If the software you choose to run on both chassis is K.14.34 or later. The 8206zl supports software version K.14.34 or later. The 8206zl will not support any software prior to K.14.34.

» Return to top

Q: What power CLI enhancements are available with software K.14.xx?
With software version K.14.xx or later more informative power information is displayed when executing the following commands. Changes are shown in red.

8206zl# show power-over-ethernet
Status and Counters - System Power Status
Pre-standard Detect : On
System Power Status : No redundancy
PoE Power Status : No redundancy
Chassis power-over-ethernet:
Total Available Power : 300 W
Total Failover Power : 0 W
Total Redundancy Power : 0 W
Total used Power : 0 W +/- 6W
Total Remaining Power : 300 W
Internal Power
1 300W/POE+ /Connected.
2 0W /Connected - Faulted.
External Power
EPS1 /Not Connected.
EPS2 /Not Connected.
8206zl# show power-over-ethernet brief
Status and Counters - Port Power Status
System Power Status : No redundancy
PoE Power Status : No redundancy
Available : 300 W
Used : 0 W
Remaining : 300 W
Module A Power
Available : 100 W
Used : 0 W
Remaining : 100 W
  PoE    | Power   Power     Alloc Alloc  Actual Configured  Detection   Power
  Port   | Enable  Priority  By    Power  Power  Type        Status      Class
  ------ + ------- --------- ----- ------ ------ ----------- ----------- ------
  A1     | Yes     low       usage 17 W   4.0 W              Delivering    0
  A2     | Yes     low       usage 17 W   0.0 W              Searching     0
  A3     | Yes     low       usage 17 W   7.0 W              Delivering    0
  A4     | Yes     low       usage 17 W   0.0 W              Searching     0
  A5     | Yes     low       usage 17 W   8.4 W              Delivering    0
  A6     | Yes     low       usage 17 W   0.0 W              Searching     0
  A7     | Yes     low       usage 17 W   0.0 W              Searching     0
  A8     | Yes     low       usage 17 W   0.0 W              Searching     0
  A9     | Yes     low       usage 17 W   0.0 W              Searching     0

The remaining installed module information will follow in the same format as above

» Return to top

Q: What new features are available when updating to K.14.xx software?

Software Manual/ Enhancements Description
Management and Configuration Guide
Advanced Classifier-Based Mirroring: More flexible and powerful port- and VLAN-based mirroring, including a finer granularity for selecting the inbound IP traffic that you want to mirror. See also “Classifier-Based Software Configuration” in the Advanced Traffic Management Guide.
Global Mirroring Updates: Deprecation and automatic conversion of ACL-based mirroring to classifier- based mirroring configuration in release K.14.xx. Support for no-tag-added option in direction-based mirroring on port interfaces, which allows you to exclude the VLAN tag added to packets sent as mirrored copies of selected traffic to a mirroring destination.
Distributed Trunking: Allows a server to connect to multiple switches with a single logical trunk enabling load-balancing and redundancy.
Debug, Syslog, and Show Command Updates: New enhancements include:
  • Enhanced diagnostics and debug information on features such as IP routing, LLDP, OSPF, SSH, VRRP and Wireless Services.
  • The logging facility command enables you to specify the destination subsystem used in a configured Syslog server.
  • Pattern matching option with the show command provides the ability to do searches for specific text. Selected portions of the output are displayed, depending on the parameters chosen.
See the Troubleshooting appendix for details.
ACE Hit Counts: ACE matches (hits) for permit and deny entries can be tracked using the show statistics < aclv4 | aclv6 > command. See the Troubleshooting appendix for details.
Ping/Traceroute Updates: The Ping, Ping6, Traceroute and Traceroute6 commands now include a source < ip-addr | vid > option. See the Troubleshooting appendix for details.
Advanced Traffic Management Guide
Classifier-Based Configuration:

Classifier-based service policies are designed to work with existing globally-configured, switch-wide and port-wide configurations by allowing you to zoom in on a subset of port or VLAN traffic. Using multiple match criteria, you can finely select and define the classes of traffic that you want to manage. Policy actions determine how you can handle the selected traffic.

See also “Advanced Classifier-Based Mirroring” in the Management and Configuration Guide and “Advanced Classifier-Based QoS” in the Advanced Traffic Management Guide.

Advanced Classifier-Based QoS: More flexible and powerful QoS classification and enforcement, including:
  • A finer granularity for classifying inbound IPv4 and IPv6 traffic
  • Additional actions for managing selected traffic, such as rate-limiting and IP precedence marking
See also Classifier-Based Software Configuration.
Global QoS enhancements: Support for IPv6 addresses, IPv6 prefixes, and IPv4 subnet masks in global QoS configuration and "show" commands has been added. See also DSCP Mapping Updates.
DSCP Mapping Updates: Support for additional DSCP codepoint values in global and classifier-based QoS commands that remark packets and remap DSCP-802.1p priority assignments.
Management VLAN: The Management VLAN feature applies to both IPv4 and IPv6 traffic.
Routing and Multicast Guide
ECMP Routing for Static Routes: Supports optional load-sharing across redundant links by allowing OSPF to add two, three, or four equal-cost next-hop routes for traffic to different subnets.
OSPF Display Commands: Enhanced show ip ospf statistics, clear ip ospf statistics, and show ip ospf spf-log commands. See also updates to the debug ip ospf command in the Troubleshooting appendix in the Management and Configuration Guide.
Access and Security Guide
Management Interface Wizard: Allows easy configuration of secure management interfaces at initial setup using either the CLI or Web browser interface.
RADIUS COS Updates: 802.1p (CoS) Priority for traffic inbound to the switch has changed from per-port to per-user.
RADIUS Rate-Limiting Updates: Includes:
  • traffic inbound (ingress) to the switch has changed from per-port to per-user
  • traffic per-port outbound (Egress) from the switch has been added
RADIUS ACLs: Enhanced support for dynamic (RADIUS-assigned) ACLs capable of filtering both IPv4 and IPv6 traffic from authenticated clients.
IP SSH for IPv4 and IPv6: SSH is now automatically supported for both IPv4 and IPv6 when SSH is enabled. The ip-version < 4 | 6 | 4or6 > command has been removed.
Ipv6 Configuration Guide
IPv6 ACLs: Support has been added for static IPv6 ACLs per-VLAN and per-port.
[no] telnet6-server [DEPRECATED]: The [no] telnet6-server command has been replaced by the [no] telnet-server command, which formerly was used only for IPv4 Telnet. The telnet-server command now enables or disables both IPv4 and IPv6 Telnet.
clear ipv6 neighbors No longer lists removed addresses. Neighbor entries for active routers are not removed, but their layer-2 information is cleared.

» Return to top

Interoperability

Q: My Cisco 7910, 7912, 7940, 7960 IP phone does not power up when connected to zl PoE modules?
The 7910, 7912, 7940, and 7960 do not work when connected to zl PoE modules because they are not seen as valid devices. They do not present a valid power class. These models are no longer supported by Cisco. Refer to link below.

» Return to top

Security

Q: Does the 8212zl support DHCP Snooping?
Yes, the 8212zl supports DHCP snooping. DHCP snooping acts like a firewall between untrusted hosts and DHCP servers. It also gives you a way to differentiate between untrusted interfaces connected to the end-user and trusted interfaces connected to the DHCP server or another switch.

» Return to top

Q: Does the 8212zl have CPU protection?
Yes, the 8212zl provides advanced threat protection against malicious network traffic trying to shut down the switch. Software features such as DHCP Snooping, Dynamic ARP Protection, and the Instrumentation Monitor provide additional protection from attacks launched from both inside and outside your network. See the Access Security Guide for details.

» Return to top

Q: Does the 8212zl support Virus throttling?
Yes, the 8212zldetects traffic patterns typical of WORM-type viruses and either throttles or entirely prevents the ability of the virus to spread across the routed VLANs or bridged interfaces, without requiring external appliances. For more information, refer to the chapter on Virus Throttling in the Access Security Guide.

» Return to top

Routing

Q: What routing protocols are supported on the 8212zl?
The 8212zl supports RIP V1, RIP V2, OSPF; includes ECMP and NSSA support. See 8212zl Data Sheet for complete list of supported protocols.

» Return to top

Q: How many static routes does the 8212zl support?
The 8212zl support 256 static routes.

» Return to top

Q: How many secondary IP addresses per interface?
The 8212zl allows up to 32 IP addresses on an individual VLAN interface.

» Return to top

Q: How many IP interfaces does the 8200zl support?
The 8212zl will allow up to 2048 IPv4 addresses for the system.

The K.12 system software can support up to 128 of these interfaces participating in an OSPF routing domain.

» Return to top

Q: How large is the ARP/Route table?
The 8212zl system route table can hold up to 10,000 IPv4 routes. The protocol stack treats ARP cache entries as host routes, so they come out of the same resource pool.

» Return to top

Q: Right after I start up my switch, I observe high (99-100%) CPU utilization. Why does this happen?
When the switch boots, one of the initialization tasks is creation of encryption keys. Having the keys created in advance means that later, when a feature such as SSL or SSH that uses the keys is configured or used, there is minimal delay in the availability. This task takes a few seconds before it ramps up, depending on the switch model, the configuration being loaded, and the software revision. Even though the task consumes up to 100% of the CPU, it runs at a very low priority. Therefore, if another task requiring CPU cycles is started, this low priority task will back off. If this initialization/key generation task runs uninterrupted by higher priority tasks, it takes about 10 minutes to complete. If the CPU is busy with other tasks, the completion time will be extended.

To verify that the elevated CPU being seen is in fact what has been described here and not something else that requires troubleshooting, please use the commands documented below.

  1. task-monitor cpu (this command was introduced in K.13.04)
  2. show uptime
  3. show cpu
The output will look like the following.
Switch# task-monitor cpu 
Switch# show uptime 
0000:00:01:42.36
Switch# show cpu

99 percent busy, from 27 sec ago
1 sec ave: 100 percent busy
5 sec ave: 100 percent busy
1 min ave: 66 percent busy

Task usage for last 5 sec
% CPU | Description
-------+--------------------------
0.3 | Sessions & I/O
99.7 | System Services 
Note that the switch key generation that runs at initialization is a 
"System Services" task. Approximately 10 minutes later, the output will 
look more like this: 
Switch# show uptime
0000:00:10:41.42 
Switch# show cpu

14 percent busy, from 300 sec ago
1 sec ave: 1 percent busy
5 sec ave: 1 percent busy
1 min ave: 1 percent busy

Task usage for last 2 sec
% CPU | Description
-------+--------------------------
98.8 | Idle
1.2 | System Services 
Note that task-monitor is intended as a diagnostic tool, 
and when not in use, it should be disabled as follows. 

Switch# no task-monitor

» Return to top

Q: How are broadcast storms created and what are some tips to avoid them?
The most common cause of a broadcast storm is a redundant switched topology where a loop exists in the Ethernet wiring topology. It’s important to make sure that your network topology contains no data path loops. Between any two end nodes, there should be only one active cabling path at any time. Data path loops will cause broadcast storms that will severely impact your network performance.

For your switch, if you wish to build redundant paths between important nodes in your network to provide some fault tolerance, you should enable Spanning Tree Protocol support on the switch. This ensures only one of the redundant paths is active at any time, thus avoiding data path loops. Spanning Tree can be enabled through the switch console, the web browser interface, or ProCurve Manager. For more information refer to the Advance Traffic Management Guide.

» Return to top

Q: What information should you have before calling your reseller or ProCurve Support?
ProCurve support will ask for the following information when customers call support:

  1. Product number
  2. Serial number
  3. Customer Name
  4. Company
  5. Phone number
  6. Address
  7. Detailed description of problem

» Return to top

Q: What information might support request to help troubleshoot problem once customer has already called support?
ProCurve Support might request customer to fill out Support form, to make the support process most efficient, and aid in troubleshooting problem quicker. Support forms are located at http://www.procurve.com/customercare/support/forms/index.htm. Find your product and complete information in form. Only complete support form at the request of support agent. Some problems/failures do not require customers to complete form. The form below is for the 8200zl.

NOTE: This form is used to collect required data at the request of an HP ProCurve Support Engineer for an open support call. Do NOT use it to open a new call. If you need to open a new call please visit our web site at http://www.procurve.com and select "Contact ProCurve".

     ProCurve Switch Support Form - Required Data


If you are using an unmanaged product or you cannot access the CLI
(command-line interface) of a managed product please provide the
following information:

	Product Number: ___________________
	(This can be found in the blue box on the front of your switch.
	It will be in the format Jxxxxx).

	Part Number: ______________________
	(This can be found in the blue box on the front of your switch
	and will be in the format JxxxxX)

	Serial Number: 	___________________
	(This can be found on the rear of the switch on a white label)

Precise problem statement: __________________________________________

_____________________________________________________________________

_____________________________________________________________________

_____________________________________________________________________

What symptoms lead you to believe that the switch is not operating 
correctly? __________________________________________________________

_____________________________________________________________________

_____________________________________________________________________

Total number of switches affected? __________________________________

Did the problem begin at installation? ______________________________

How long has the switch been in operation? __________________________

What changes were made to the switch configuration prior to the 
problem episode? ____________________________________________________

_____________________________________________________________________

What changes were made to the network topology/conditions prior to
the problem episode? ________________________________________________

_____________________________________________________________________

How often does the problem occur? ___________________________________

What is the current workaround, if any? _____________________________

_____________________________________________________________________

What troubleshooting steps have you performed to isolate the problem
to this switch? _____________________________________________________

_____________________________________________________________________

_____________________________________________________________________

_____________________________________________________________________

If you have network management (e.g. ProCurve Manager) that can 
monitor the device, what is the network management product and what 
pertinent information does it report?  ______________________________

_____________________________________________________________________

_____________________________________________________________________

What if any Genuine ProCurve accessories are you using
(mini-GBICs, transceivers, RPS/EPS)? ________________________________

_____________________________________________________________________

_____________________________________________________________________

*********************************************************************
Please attach the following information:

1. Network topology map: 
   a) All IP addresses and subnet masks of devices that are relevant 
      to the problem.
   b) Port mapping of connected network devices.
   c) Port mapping of connected clients/servers relevant to the 
   problem.

Please attach the following for managed products with CLI:
2. TECHNICAL SUPPORT DATA:
   This output will help HP gather valuable information about your
   switch.
   The data should be captured while the problem is occurring.

   i) From a console connection or TELNET session, use the following 
      CLI command:

	show tech all [*ENTER*]

      and capture/log the output; or

   ii) You will need a TFTP server.  Use the following CLI command:

       copy command 'show tech all' tftp 
	    [*ENTER*]

3. CRASH LOG:  You will need a TFTP server to get this binary file.
	Use the following CLI command:  

       copy crash-log tftp  [*ENTER*]

» Return to top

Printable version
Privacy statement Using this site means you accept its terms
© 2010 Hewlett-Packard Development Company, L.P.