�

NETGEAR VoIP Avaya QE 20

Avaya Quick Edition and NETGEAR Design Guide

Table of Contents

1.0 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

2.0 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

2.� Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

3.0 VoIP Network Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

3.� Reliability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

3.2 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

3.3 Scalability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

3.4 QoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

3.5 VLANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

3.6 PoE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

4.0 Deployment Scenario and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 4

4.� Deployment Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

4.2 Network Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

4.3 Configure the FVS338 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

4.4 Configuring DHCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

4.5 Configuring the Smart Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

4.6 Configure the Switch for Quality of Service (QoS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

4.7 Mapping CoS to Queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . �3

4.8 Configuring VPN Site-to-Site Tunnel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . �6

5.0 Management and Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

About NETGEAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

List of FiguresFigure �: Avaya/NETGEAR Solution for 20-user Main Office Network and One Teleworker Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

List of TablesTable �: Equipment for the Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

2

1.0 IntroductionOn May 2�, 2007, NETGEAR®, a worldwide provider of technologically advanced network-ing products, and AVAYA, a leading global provider of business communications applications, systems and services, announced that they were teaming to bring advanced business-class Internet telephony to small businesses. As a global leader of networking products for the small business sector, NETGEAR combines its networking technology and experience with Avaya’s market-lead-ing IP telephony technology to deliver an advanced, easy-to-deploy, easy-to-manage solution for companies of 20 users or less.

Avaya’s Quick Edition (QE) delivers business class communication features like voice mail, auto-attendant, and rich call management features such as Call Forward, Conferencing, Park, Page and Retrieve that are ideally suited for helping small businesses create a professional business image. Quick Edition can connect multiple remote branches, enabling central management so that even small offices can equip home workers with the same features they have when they are in the office.

The Avaya and NETGEAR bundle consists of Avaya Quick Edition phones, an Avaya PSTN (Public Switched Telephone Network) Gateway, NETGEAR Power over Ethernet (PoE) switches, and a NETGEAR virtual private network (VPN) firewall.

This solution is designed for quick and easy deployment. Table � displays the equipment used in this solution with a description and a recommendation for deployment.

Table 1: Equipment for the Solution

Type Models Key Features

PSTN Gateway

Avaya Quick Edition (QE)G�0/G�� Gateway

Manages calls between QE phones and calls to/from the telephone network

IP Phones Avaya 46�0 and 462� QE IP Phones Integral 2-port switch allows computer to plug directly into phone, allowing phone and com-puter to share an Ethernet port

Firewall FVS338, NETGEAR ProSafe VPN Firewall. With 8 FE ports and supports up to 50 simultaneous IPSec VPN tunnels

• Protects business network from intrusions, spam and virus

• Ensures privacy between business locations

NETGEAR ProSafe SmartPoE Switches

NETGEAR ProSafe Smart PoE switches: • ProSafe Unmanaged switches

– ProSafe FS�08P 8 Port FE switch with PoE

– ProSafe FS��6P �6 Port FE switch with PoE

• ProSafe Smart switches– FS726TP 24 Port FE switch with PoE

and 2 GE uplink ports.– FS728TP 24 Port FE switch with PoE

and 4 GE uplink ports

All switches:• Powers phones through the Ethernet cable

(Standards 802.3of compliant)Smart-managed:• Supports Quality of Service (QoS) for pri-

oritizing voice traffic

Note: For a detailed view of product features and functionality, please visit the NETGEAR and Avaya sites:

www.NETGEAR.com

www.Avaya.com

3

2.0 ScopeThis document has been created to assist value added resellers and network/system administrators who support small businesses of �00 end users or less in the design and consideration of a Voice over IP (VoIP) network using NETGEAR and Avaya equipment. An introduction to network design considerations and specifics pertaining to VoIP and VoIP network preparation will also be discussed. Finally, we will review a case study that gives NETGEAR equipment configuration samples. This document is not intended to show configuration of Avaya equipment. For more detail on Avaya equipment and product configurations, please refer to www.Avaya.com.

2.1 PrerequisitesIn this document, we will be discussing the configuration and deployment of NETGEAR equipment with a focus on Quality of Service (QoS), Protocol over Ethernet (PoE), Virtual Local Area Networks (VLANs) and management. This document is not a training document for VoIP or any other technologies discussed, and assumes that the reader has a basic understanding of networking concepts and networking terminology.

3.0 VoIP Network Design The key components of a VoIP design are the same as those for a data network design—reliability, security and scalability. Both also need to be configured to suit the needs of the business applica-tions being run on them. In the case of VoIP, technologies such as PoE and QoS play a major role in ensuring an easy deployment and smooth traffic transmission.

3.1 ReliabilityReliability should be a key deciding factor when selecting equipment for a network. Both NET-GEAR and Avaya products are designed for high reliability. NETGEAR ProSafe VPN firewall and PoE switches combined with Avaya one-X Quick Edition delivers a distributed system with no single point of failure. Each telephone is backed up by two other phones so that, in the unlikely event that a phone fails, one of the backups will forward the call to voicemail or to another exten-sion or phone number set up by the user.

Since all Avaya phones receive power from the NETGEAR switch, ensuring power availability for the NETGEAR Smart Switch with a UPS Universal Power Supply in the wiring closet will ensure that phones stay on in the event that power to the wiring closet fails.

3.2 SecurityFor all businesses, security is a major consideration. The NETGEAR/Avaya solution has security on the network as well as its voice products. NETGEAR products are 802.�x port security ready and have a wide range of security features that can be implemented, such as secured login, MAC-based authentication and Access Control Lists (ACLs). In addition, the Avaya Quick Edition products have advanced security features such as Secure Socket Login.

NETGEAR ProSafe VPN firewall also adds security by protecting against viruses, hackers and other elements that attempt to disrupt business continuity. The ProSafe FVS338 adds another layer of insurance that voice communications are secure.

4

3.3 ScalabilityWhen designing a network, it is always important to keep it simple and design with growth in mind. The NETGEAR/Avaya solution has been designed for flexibility and scalability. Adding more phones for end users to expand the voice network can be accomplished by simply adding more equipment, such as a NETGEAR ProSafe PoE switch. The scalability of the technology makes the system easy to expand. NETGEAR and Avaya equipment provide many product options that will fit the demands of a growing business today, and will scale easily and cost affectively with future growth.

3.4 QoSQuality of Service (QoS) is a key component of any network, especially a VoIP network. It is highly recommended to configure QoS for any size network. For VoIP, configuring QoS is a safe-guard that insures smoother and cleaner traffic flow, which in turn provides higher sound quality for VoIP. Both NETGEAR and Avaya support QoS features. These features will be discussed further in the deployment section of this document.

3.5 VLANsVirtual LANs are a great tool for securing and managing network traffic. For a VoIP deployment, VLANs can create independent logical networks within a physical network that separate voice traf-fic from data traffic. This mitigates the risk that a broadcast storm or denial of service (DOS) attack on the data network will affect the quality of voice networks. In addition, separating voice and data traffic into separate domains will reduce competition for network bandwidth and thus reduce latency (queue/wait time) for transmission services.

3.6 PoEPower over Ethernet (PoE) is a key technology for VoIP and should be considered for every VoIP network. PoE allows devices like IP phones, wireless access points and IP cameras to be powered through Ethernet cables (UTP 5) from the Ethernet switches, eliminating the need for separate power distribution for these network devices. PoE allows for an easy and quick VoIP deployment. It also cuts down on the price of power supplies for phones and allows for centralized power to be managed via a single power source—in this case the switch. A switch that is on an external power supply for power backup, such as UPS or RPS as defined below, ensures that end devices and IP phones are also backed up. This is an important aspect of a VoIP network, as it adds another level of security for network reliability and uptime.

These features will be discussed further in the deployment section of this document.

For more information on PoE, please visit www.netgear.com.

4.0 Deployment Scenario and ConfigurationThe necessary configuration for the solution on the network side is very simple, and the network can be set up with working IP Phones by following just a few easy configuration steps. The important thing is to have the VPN router configured to work with the WAN interface and to turn on the DHCP (Dynamic Host Configuration Protocol) server. These are the only requirements needed for this network to function. The rest are fine-tuning and management functions such as turning on QoS or expanding the network to a remote site such as a branch office or a teleworker. To give an example of this, below is a sample network deployment.

5

In this section, we will use a case scenario to show the step-by-step configuration of an actual VoIP Avaya/NETGEAR deployment. The purpose of this exercise is to build a NETGEAR VoIP network that is designed around Avaya QE 20 equipment, walking through the configuration of the VoIP network and giving specific configuration examples.

The equipment chosen for this network is from the recommended network equipment list for the Avaya QE 20 solution previously shown in Table �. The main site consists of two NETGEAR ProSafe products, the FVS338 and the FS728TP. Choosing the right equipment is based on the business’s current and future needs. Selecting the right switch is dependent on the number of ports and functionality of the switch. All recommended products allow for optimal VoIP functionality and performance.

Note: The term teleworker site is used instead of branch office in this document as a result of the size of the network and not the functionality of the NETGEAR and Avaya equipment, which are fully capable of deploying in a branch office.

Figure 1: Avaya/NETGEAR Solution for 20-user Main Office Network and One Teleworker Site

4.1 Deployment ConfigurationsAs shown in Figure �, the main office network consists of a NETGEAR ProSafe FVS338 Firewall and the FS728TP. The Avaya QE phones require a flat network, or one subnet to communicate with each other. Also, with a network of this size, having one subnet in the main office keeps the network simple and easy to manage. For this case scenario deployment, the following IP address ranges are used.

• Main Office: �0.�0.�0.0 subnet mask: 255.255.255.0

• Teleworker Site: �92.�68.�.0 subnet mask: 255.255.255.0

These address ranges are arbitrary and any IP address ranges will do for this network. The IP addresses can either be left alone as the default �92.�68.x.x or specified to fit the current or planned company network policy.

6

4.2 Network ConfigurationsNow that the hard part of creating a network—choosing the equipment, drawing out a logical diagram, and choosing the IP addressing scheme—is done, configuring the equipment is very straightforward. Here are the 3 simple steps to follow:

�. First configure the FVS338.

a. Log into the FVS338.

b. Configure the Internet connection based on your service provider (DSL, CABLE, T�, etc.).

c. Assign the FVS338 and IP Address.

2. Configure the switch.

a. Configure QoS on the switch.

b. View PoE options and statistics.

3. Finally, configure the FVS338 VPN tunnel for teleworker site.

Configuration steps are explained in both a quick installation and a detailed installation format below. The quick installation procedure lists configuration steps and gives advanced users a quick guide to follow. Detailed installation steps are provided for those who would like a more granular explanation of the fields to be configured.

4.3 Configure the FVS338 Step one is to configure the FVS338. The FVS 338 will provide DHCP and VPN service to the network.

Quick Installation Procedures:

�. Basic router configuration—set up the router to the WAN port.

2. Change IP address of router from �92.�68.�.� to �0.�0.�0.�.

3. Configuring the DHCP server: Configure the IP address range. For this network, the main of-fice network is �0.�0.�0.0 with a subnet mask of 255.255.255.0. This will be the IP address range of all the products on the network.

Detailed Installation Procedures:

�. Connecting the firewall physically to your network: Connect the cables, turn on your router and wait for the Test LED to go out. Make sure your Ethernet and LAN LEDs are lit. (See the FVS338 ProSafe VPN Firewall 50 Installation Guide on your Resource CD.)

2. Logging into the firewall: After logging in, you are ready to set up and configure your firewall, change your password and enable remote management.

3. Configuring the Internet connections to your ISPs: During this phase, you will connect to your ISPs and can also program the WAN traffic meters if desired.

Log into the FVS338 by entering the default IP address in your supported network browser: Inter-net Explorer 5.0 or higher, Netscape Navigator 4.7 or higher.

Enter http://192.168.1.1 as the URL

• admin for User Name

• password for Password

7

Note: For the procedure on connecting to the FVS338, please view the installation guide on the NETGEAR support site: ftp://downloads.netgear.com/files/FVS338_IG_24AUG06.pdf

4.4 Configuring DHCP�. Select Network Configuration from the main menu and LAN Setup from the submenu. The

LAN Setup screen will display.

2. Enter the IP Address of your router (factory default: �92.�68.�.�). For this case scenario network we will use �0.�0.�0.0. (Always make sure that the LAN Port IP address and DMZ port IP address are in different subnets.)

3. Enter the IP Subnet Mask. The router should be the first IP address, in this case �0.�0.�0.�, of a network. The subnet mask specifies the network number portion of an IP address. Your router will automatically calculate the subnet mask based on the IP address that you assign. Unless you are implementing subnetting, use 255.255.255.0 as the subnet mask (computed by the router).

8

4. Check the Enable DHCP Server radio button. By default, the router will function as a DHCP server, providing TCP/IP configuration for all computers connected to the router’s LAN.

a. Enter the Domain Name of the router (this is optional and not necessary for our case scenario network).

b. Enter the Starting IP Address. This address specifies the first of the contiguous ad-dresses in the IP address pool. Any new DHCP client joining the LAN will be assigned an IP address between this address and the Ending IP Address. The IP address �92.�68.�.2 is the default start address.

For this case scenario, enter the Starting IP Address as 10.10.10.50

Note: It is also important to reserve a list of IP addresses for network equipment, such as additional switches or servers. For this network, IP addresses �0.�0.�0.� to �0.�0.�0.�0 are reserved for this purpose.

c. Enter the Ending IP Address. This address specifies the last of the contiguous ad-dresses in the IP address pool. Any new DHCP client joining the LAN will be assigned an IP address between the Starting IP address and this IP address. The IP address �92.�68.�.�00is the default ending address.

For this case scenario, an Ending IP Address of 10.10.10.150 is entered.

d. Enter a WINS Server IP address. This box can specify the Windows NetBios Server IP if one is present in your network. This field is optional.

e. Enter a Lease Time. This specifies the duration for which IP addresses will be leased to clients.

f. Check the Enable DNS Proxy radio box. This is optional—the default is enabled. If enabled, the VPN firewall will provide a LAN IP Address for DNS address name resolution.

g. Click Apply to save your settings.

h. Click Reset to discard any changes and revert to the previous configuration.

4.5 Configuring the Smart SwitchThis PoE capable Smart Switch, the FS728TP, provides power and data using built-in IEEE 802.3af PoE on all 24 ports. In addition, the FS728TP offers an intuitive Web-based management tool for quick and easy deployment and configuration making it ideal for deploying VoIP.

Quick Installation Procedures:

�. Access the switch through the Web interface. There are a few ways to do this. The recom-mended way is to use the installation CD-ROM which installs the Smartwizard Discovery Utility. Or if you prefer, you can just find the IP address in the FVS338 DHCP client table.

2. Configure QoS (recommended).

a. Enable Class of Service (CoS) on the switch

b. Modify the CoS setting on the Ethernet ports with VoIP IP phones to the value of 6

c. Set the priority to Strict Priority

d. Map the CoS value to the priority Queue of 4

3. PoE configuration (optional).

9

a. View port-based PoE information

b. View PoE switch-wide information. Set PoE threshold if and enable traps for management purposes.

Detailed Installation Procedures:

For further detail on setting up the smart switch, please refer to the installation guide: ftp://downloads.netgear.com/files/FS728TP_QIG_05DEC06.pdf

To connect the switch, follow the procedures below:

4. Once you have logged into the switch, it will bring you to the FS728TP default page.

4.6 Configure the Switch for Quality of Service (QoS)QoS is a feature that adds insurance to network functionality and is highly recommended. The Avaya QE phones can function without QoS. Adding Quality of Service is a precautionary step in case of high bandwidth utilization. It is best to configure QoS for this deployment at the port level. Without QoS, network bandwidth is shared across all traffic equally. This leaves room for more aggressive and chatty applications such as MP3 downloads or video streaming to dominate available bandwidth, negatively impacting time-sensitive traffic such as VoIP. In this case scenario, we will turn on QoS on the Ethernet port that the Avaya IP phone is connected to. This way, any traffic coming from that port will be protected from other network traffic.

�0

Enable CoS on the switch by selecting Enable:

�. Click Switch > QoS > General > CoS to open CoS Page.

2. The CoS Page contains the following:

• CoS Mode—Determines whether QoS is enabled on the device. For this setup, enable CoS Mode.

• Possible values are: Enable (enables QoS on the interface) and Disable (disables QoS on the interface).

3. Leave the Trust Mode as default on CoS. For this setup, select Trust Mode to CoS.

Trust Mode defines which packet fields to use for classifying packets entering the device. When no rules are defined, the traffic containing the predefined packet CoS field is mapped according to the relevant Trust Modes table. Traffic not containing a predefined packet field is mapped to “best effort.” The possible Trust Mode field values are:

• CoS—Classifies traffic based on the CoS (VPT) tag value.

• DSCP—Classifies traffic based on the Differentiated Services Code Point tag value.

• None—Indicates that Trust is not enabled on the device.

4. Click . Quality of Service is enabled on the device.

��

5. Now select the ports you want to configure. From the Set Default User Priority drop down menu, select priority 6, then change the priority level on this page. NOTE: It’s important to configure this option only for ports with Avaya IP Phones. This ensures that VoIP traffic realizes a higher priority than data traffic.

6. Interface—Displays the interface for which the global QoS parameters are defined.

• Port—Selects the port for which the global QoS parameters are defined.

• LAG—Selects the LAG for which the global QoS parameters are defined.

7. Default CoS—Determines the default CoS value for incoming packets for which a VLAN tag is not defined. As mentioned previously, select priority of 6 for all Avaya IP phones.

8. Click . Quality of Service is enabled on the device.

�2

To enable Queue settings:

�. Click Switch > QoS > General > Queue to open the Queue Page.

2. The Queue Page contains the following fields:

• Strict Priority—Specifies whether traffic scheduling is based strictly on the queue priority.

• WRR—Assigns WRR weights to queues to prevent a specific application from consuming all of a port’s forwarding capability. The queue weights are preconfigured and are set to 0, 2, 4 and 7.

3. Select Strict Priority or WRR Fields. For this setup, select Strict Priority.

4. Click . The queue settings are set and the device is updated.

�3

4.7 Mapping CoS to QueuesNow comes the mapping of the CoS value to the Queue. Since we gave the ports CoS a value of 6, that is the only Queue we need to manipulate. Change the CoS value of 6 to map to Queue 3. The default is 4, however it is important to lower to 3 so that there is room for growth, meaning in the future it will be possible to give a higher priority to other ports.

�. The CoS to Queue Page contains fields for mapping CoS values to traffic queues.

2. To map CoS values to queues, click Switch > QoS > Mapping > CoS to Queue.

3. The CoS to Queue Page opens and shows the following fields:

• Class of Service—Specifies the CoS priority tag values, where zero is the lowest and 7 is the highest.

• Queue—Defines the traffic forwarding queue to which the CoS priority is mapped. Four traffic priority queues are supported. The lowest priority is � and the highest is 4.

• Restore Defaults—Restores the device factory defaults for mapping CoS values to a forwarding queue.

4. Define the queue number in the Queue field next to the required CoS value.

5. Click . The CoS value is mapped to a queue and the device is updated.

�4

4.7.1 PoE option on FS728TP

Power over Ethernet (PoE) provides power to devices over existing LAN cabling without updating or modifying the network infrastructure. This removes the limitation of placing network devices like the following close to power sources.

• IP Phones

• Wireless Access Points

• IP Gateways

• Audio and video remote monitoring

Powered Devices are devices that receive power from the source device power supplies. IP phones are examples of powered devices connected to the source device via Ethernet. The PoE Configuration Page contains system PoE information for enabling PoE on the device, monitoring the current power usage and enabling PoE traps.

This section shows where to view the power statistics for the switch. A preview of the overall switch PoE budget as well as per port statistics. It is recommended to view this information as a precaution. For more information, please view the NETGEAR PoE white paper on NETGEAR.com.

To enable PoE on the device:

�. Click System > PoE Configuration. The PoE Configuration Page opens:

The PoE Configuration Page contains the following fields:

• Power Status—Indicates the online power source status. The possible field values are:

On—Indicates that the power supply unit is functioning.

Off—Indicates that the power supply unit is not functioning.

Faulty—Indicates that the power supply unit is functioning, but an error has occurred (for example, a power overload or a short circuit).

�5

• Nominal Power—Indicates the actual amount of power the device can supply. The field value is displayed in Watts.

• Consumed Power—Indicates the amount of the power used by the device. The field value is displayed in Watts.

• System Usage Threshold—Indicates the percentage of power consumed before an alarm is generated. The field value is �-99 percent. The default is 95 percent.

• Traps—Indicate if PoE device traps are enabled. The possible field values are:

Checked—Enables PoE traps on the device.

Unchecked—Disables PoE traps on the device. This is the default value.

• Interface—Indicates the specific interface for which PoE parameters are defined. PoE parameters are assigned to the powered device that is connected to the selected interface.

• Admin Mode—Indicates the device PoE mode. The possible field values are:

Enable—Enables the Device Discovery protocol and provides power to the device using the PoE module. The Device Discovery Protocol enables the device to discover Powered Devices attached to the device interfaces and to learn their classification. This is the default setting.

Disable—Disables the Device Discovery protocol and stops the power supply to the device using the PoE module.

• Priority Level—Determines the port priority if the power supply is low. The field default is low. For example, if the power supply is running at 99% usage, and port � is prioritized as high, but port 3 is prioritized as low, port � is prioritized to receive power and port 3 may be denied power. The possible field values are:

Low—Defines the PoE priority level as low. This is the default level.

Medium—Defines the PoE priority level as Medium.

High—Defines the PoE priority level as high. This is the highest PoE priority level.

• Class—Indicates the amount of power assigned to the powered device connected to the selected interface. The powered device classifies devices, and the devices use the classifica-tion information. The field values are:

Class 0—Indicates that the maximum power level at the input of the Powered Device is �5.4 watts.

Class 1—Indicates that the maximum power level at the input of the Powered Device is 4.0 watts.

Class 2—Indicates that the maximum power level at the input of the Powered Device is 7.0 watts.

Class 3—Indicates that the maximum power level at the input of the Powered Device is �5.4 watts.

Class 4—Treated as Class 0.

• Output Voltage—Displays the output voltage in watts.

• Output Current (ma)—Displays the output current in milliamps.

• Power Limit (Watt)—Indicates the power limits in watts.

• Status—Indicates if the port is enabled to work on PoE. The possible field values are:

On—Indicates the device is delivering power to the interface.

Off—Indicates the device is not delivering power to the interface.

Test Fail—Indicates the powered device test has failed. For example, a port could not be enabled and cannot be used to deliver power to the powered device.

Testing—Indicates the powered device is being tested. For example, a powered device is tested to confirm it is receiving power from the power supply.

�6

Searching—Indicates that the device is currently searching for a powered device. Searching is the default PoE operational status.

Fault—Indicates that the device has detected a fault on the powered device. For example, the powered device memory could not be read.

2. Define the fields.

3. Click . The PoE interface is defined and the device is updated.

To view PoE statistics:

�. Click PoE Configuration. The PoE Configuration Page opens:

2. Click the interface. The Modify PoE Configuration Page opens:

The Modify PoE Configuration Page contains the following fields:

• Interface—Indicates the specific interface for which PoE parameters are defined. PoE param-eters are assigned to the powered device that is connected to the selected interface.

• Admin Mode—Indicates the device PoE mode. The possible field values are:

Enable—Enables the Device Discovery protocol and provides power to the device using the PoE module. The Device Discovery Protocol enables the device to discover Powered Devices attached to the device interfaces and to learn their classification. This is the default setting.

Disable—Disables the Device Discovery protocol and stops the power supply to the device us-ing the PoE module.

4.8 Configuring VPN Site-to-Site Tunnel This section walks through how to configure a VPN site-to-site connection. The Avaya Quick Edition 20 solution allows for a remote worker/ branch office deployment. This section will walk through the NETGEAR side of configurations to enable this feature. NETGEAR has simplified this process by putting in place a VPN wizard to walk you through the process.

�7

Before beginning this process, the remote site must have an existing network. You can follow the ‘Configure the FVS338’ procedures in section 4.3 of this document to accomplish this task.

Quick Installation Procedures:

�. To expedite the process, obtain the WAN IP addresses for both routers, choose a secured pre-shared key for both sides (must be within 8 to 49 characters long), and finally know the remote site LAN IP network address and subnet mask. The wan IP address can be viewed in the FVS338 firewall settings under Management in the Router Status field as shown in the screen shot.

2. Start the VPN Wizard and create a Gateway connection. When the Wizard is complete, check the VPN connection status.

3. View the VPN Policy for connection status.

Detailed Installation Procedures:

�. First log into the FVS338 and configure the remote FVS338. For the branch/teleworker site you can use default IP address and DHCP information for simplified deployment.

2. To configure the VPN tunnel, select VPN from the main menu and VPN Wizard from the submenu. The VPN Wizard screen will display.

3. Select Gateway as your VPN tunnel connection. The wizard needs to know if you are planning to connect to a remote gateway or you are setting up the connection for a remote client/PC, in order to establish a secure connection to this device.

4. Select a Connection Name. Enter an appropriate name for the connection. This na is not supplied to the remote VPN endpoint. It is used to help you manage the VPN settings.

�8

5. Enter a Pre-shared Key. The key must be entered both here and on the remote VPN Gate-way or the remote VPN Client. This key length should be minimum 8 characters and should not exceed 49 characters. This method does not require using a CA (Certificate Authority).

6. Enter the Remote WAN IP Address or Internet Name of the gateway to which you want to connect. The remote WAN IP address of the gateway must be a public address or the Internet name of the gateway. The Internet Name is the Fully Qualified Domain Name (FQDN) as set up in a Dynamic DNS service. Both local and remote ends should be defined as either IP addresses or Internet Names (FQDN). A combination of IP address and Internet Name is not permissible.

7. Enter your Local WAN IP Address or Internet Name. The Local WAN IP Address is the address used in the IKE (internet key exchange) negotiation phase and might automatically display the WAN IP address assigned by your ISP. You can modify the address to use your own fully qualified domain name or FQDN (this is required if the WAN Mode you selected is auto-rollover).

8. Enter the Remote LAN IP Address and Subnet Mask of the remote gateway. The information entered here must match the Local LAN IP and Subnet Mask of the remote gateway—otherwise the secure tunnel will fail to connect. The IP address range used on the remote LAN must be different from the IP address range used on the local LAN.

9. Click Apply to save your settings. The VPN Policies table will display showing your VPN policy. You can click the IKE Policies tab to view the corresponding IKE Policy.

�9

4500 Great America ParkwaySanta Clara, CA 95054 USA1-888-NETGEAR (638-4327)E-mail: info@NETGEAR.comwww.NETGEAR.com

© 2007 NETGEAR, Inc. NETGEAR, the NETGEAR logo, Connect with Innovation, Everybody’s connecting, the Gear Guy logo, IntelliFi, ProSafe, RangeMax and Smart Wizard are trademarks or registered trademarks of NETGEAR, Inc. in the United States and/or other countries. Microsoft, Windows, and the Windows logo are trademarks or registered trademarks of Microsoft Corporation in the United States and/or other countries. Other brand and product names are trademarks or registered trademarks of their respective holders. Information is subject to change without notice. All rights reserved.

5.0 Management and SupportAll NETGEAR products are simple and straightforward to manage and troubleshoot, with easy-to-use Web-based interfaces for management, and status LED’s for quick glance assessment.

NETGEAR and Avaya support and contact information is located on the companies web pages.

Avaya Quick Edition 20 products and help links:

• Main page: http://www.avaya.com

• Quick Edition Product page: http://www.avaya.com/gcm/master-usa/en-us/products/offers/one_x_quick_edition.htm

• Avaya Support page: http://support.avaya.com

NETGEAR Product ProSafe support:

• NETGEAR offers Lifetime support on all ProSafe products. More information can be found on http://www.NETGEAR.com

• Main page: http://www.NETGEAR.com

• Product support: http://kbserver.netgear.com/main.asp

About NETGEARNETGEAR has been a worldwide provider of technologically advanced, branded networking products since �996. Our mission is to be the preferred customer-driven provider of innovative networking solutions for small businesses and homes.