HP ProCurve Networking

» Kontakt

ProCurve Networking by HP - Anwendungshinweise



Contents

» 1. Introduction
» 2. Architecture
» 3. Configuration
» 3.1 Check PoE compatibility on ProCurve Switch 3500yl
» 3.2 Check PoE compatibility on ProCurve Switch 2610
» 4. Configuring QoS support
» 4.1 Configure QoS on the phone
» 4.2 Configure QoS on the switches
» 5. LLDP-MED support
» 5.1 Configure LLDP-MED support on the Aastra phone
» 5.2 Configure LLDP-MED on the switch
» 6. Configuring 802.1X support
» 6.1 Configure 802.1X login credentials on the phone
» 6.2 Configure 802.1 X on the switch
» 6.3 Configure multiple 802.1X sessions
» 7. Firmware versions
» 8. Reference documents

Downloads

» Interoperability between Aastra 5xi Series IP Phones and ProCurve Switches (PDF)

1. Introduction

This document describes how ProCurve switches and Aastra IP phones interoperate to build a secure and easy-tomanage network. Both the switch and the phone rely on standard protocols:

  • 802.3af, standard for Power-over-Ethernet (PoE) enables the switch to allocate up to 15.4W of power per port.
  • Quality-of-Service (QoS) mechanisms enable the network to give voice flow—which is sensitive to delay, jitter and packet loss—priority over the data traffic, to guarantee that the communications will continue in case of congestion.
  • LLDP-MED is a discovery protocol that enables switches to get some layer 2 information about a phone (such as its model, firmware, location, etc.) and automatically allocate certain network parameters (VLAN and QoS) to the phone.
  • 802.1X is the most recommended authentication method for access control on the network. It is recognized as a standard, and is implemented by most IP telephony constructors. Multiple 802.1X authentication enables authentication both of a phone plugged into a switch and of a user plugged into the dual port of the phone, while assigning them different profiles (VLAN, QoS, bandwidth).

» Return to top

2. Architecture

The platform contains:

  • One or more servers with the following services: Active Directory, DHCP, DNS, Certificate Authority, IAS.
  • Latest versions of ProCurve Manager Plus (PCM+) and Identity-Driven Manager (IDM).
  • Aastra 5xi Series phone (53i, 55i or 57i).
  • A ProVision Switch 3500yl or 2610-PWR with the latest firmware version. A similar configuration can also be used with a ProCurve 5400zl series switch or a 8212zl series switch. The configuration commands are identical for these products and the 3500yl.
  • A client laptop that can be plugged into the phone dual port for multiple authentication tests or used as a network analyzer (e.g., Wireshark)
Figure 1. Setup for ProCurve-Mitel interoperability
Figure 1. Setup for ProCurve-Aastra interoperability

» Return to top

3. Configuration

This section explains how to configure an Aastra phone and the ProCurve switch.

3.1 Check PoE compatibility on ProCurve Switch 3500yl

ProVision switches support standard PoE (802.3af), and so do Aastra phones. When the phone is plugged into a port on the ProCurve Switch 3500yl, the phone boots up.

To view the power consumption of the phone, issue the following command on the switch:To view the power consumption of the phone, issue the following command on the switch
Where X is the port into which the phone is plugged.

» Return to top

3.2 Check PoE compatibility on ProCurve Switch 2610

On a 2610 switch, the command to view power consumption is:To view the power consumption of the phone, issue the following command on the switch
Where X is the port into which the phone is plugged.

For example:
To view the power consumption of the phone, issue the following command on the switch
For an Aastra 53i SIP phone this consumption is around 2160 mW.

» Return to top

4. Configuring QoS support

This section explains how to configure Quality of Service parameters.

4.1 Configure QoS on the phone
Quality of Service parameters can be configured on the phone using the phone’s web interface.

To configure QoS on the Aastra phone:
  1. To access Aastra phone web interface, use a web browser and go to the phone’s URL:
    http://<phone-ip-address>
  2. By default the login credentials are:
    • Username: admin
    • Password: 22222
  3. From the Network Settings menu, you can set DSCP values for the different voice and signalization protocols, including SIP, RTP, and RTCP:
    To view the power consumption of the phone, issue the following command on the switch

» Return to top

4.2 Configure QoS on the switches
The recommended method is to have a dedicated VLAN for voice and configure the QoS parameters for the VLAN. The L2 and DSCP policy advertised are based on the actual QoS configuration for the voice VLAN. By default these values are:

  • L2 priority 6
  • DSCP 46, which corresponds to the Expedited Forwarding (EF) class

To modify the 802.1p or DSCP values:To modify the 802.1p or DSCP values

For more information on QoS settings on ProCurve switches, please refer to the following documents:


» Return to top

5. LLDP-MED support

This section explains how to configure LLDP-MED support.

5.1 Configure LLDP-MED support on the Aastra phone
Aastra phones 53i, 55i and 57i will officially support LLDP-MED in Autumn 2008. Tests have been run on a beta version.

LLDP is enabled by default on the phones. It can be enabled or disabled from the Advanced Settings | Network Settings menu of the phone web interface. The LLDP packet interval can also be modified:To modify the 802.1p or DSCP values

» Return to top

5.2 Configure LLDP-MED on the switch
To configure LLDP-MED on the switch:
     1. Defining a VLAN as voice VLAN enables LLDP-MED: 1. Defining a VLAN as voice VLAN enables LLDP-MED

     2. Then configure LLDP-MED. LLDP-MED must be configured on the switch to support MED TLVs, in particular network policy and capabilities: 2. Then configure LLDP-MED. LLDP-MED must be configured on the switch to support MED TLVs, in particular network policy and capabilities

     3. To obtain information about the phone, issue the command:
To obtain information about the phone, issue the command Where X is the port into which the phone is plugged.

The following shows an example of an output:
To obtain information about the phone, issue the command

On the phone, the LLDP-MED-assigned voice VLAN and priority settings appear:To obtain information about the phone, issue the command

To view the phone power consumption, issue the command:To obtain information about the phone, issue the command
Where X is the port into which the phone is plugged. For example:

To obtain information about the phone, issue the command


» Return to top

6. Configuring 802.1X support

This section explains how to configure 802.1X support.

6.1 Configure 802.1X login credentials on the phone
To configure the phone:

  1. In the phone’s Web interface, got to Advanced Settings | 802.1X support to 802.1X.
  2. Select the EAP type. For the EAP type you have the choice between EAP-MD5 (login/password) or EAP/TLS (with certificates):To obtain information about the phone, issue the command
  3. Reset the phone. When it reboots you see a display indicating 802.1X authentication:To obtain information about the phone, issue the command

» Return to top

6.2 Configure 802.1 X on the switch
To configure 802.1X on the switch:

1. Enable 802.1X on the phone ports:
To obtain information about the phone, issue the command

2. Enter the RADIUS information in the switch configuration:To obtain information about the phone, issue the command

» Return to top

6.3 Configure multiple 802.1X sessions
To configure multiple 802.1X sessions:

  1. Modify the switch configuration for the port connected to the phone. Configure it so the voice VLAN is tagged and the data VLAN untagged.
  2. Set the client-limit parameter on the switch to 3 to enable both the PC and the phone to authenticate. For example:

To obtain information about the phone, issue the command


The data VLAN can also be dynamically assigned using Identity Driven Manager.

The phone and PC authentication appear in IDM: To obtain information about the phone, issue the command

» Return to top

7. Firmware versions

Firmware versions of the switches used for this application note are as follows: Firmware versions of the switches used for this application note are as follows:
  • K.13.09 for the ProCurve ProVision switches (5406zl, 3500yl, 8212zl)
  • R.11.07 for the ProCurve Switch 2610-PWR

Aastra phones have been tested using a beta version of firmware. The version is Release 2.3 Beta 1, as follows:

  • FC-001086-00-xx for model 53 i
  • FC-001087-00-xx for model 55 i
  • FC-001088-00-xx for model 57 i

» Return to top

8. Reference documents

For further information about how to configure ProCurve switches to support convergence, please refer to the following links:

» Return to top