The Avaya P330 family of stackable Ethernet workgroup switches includes a range
of modules with 10/100/1000 Mbps ports, Layer 3 capability and ATM Expansion
sub-module. The base product is the Avaya P333T switch which has 24x10/100
Mbps ports and an Expansion sub-module slot. The optional expansion submodules provide additional Ethernet, Fast Ethernet, and Gigabit Ethernet
connectivity.
The Avaya P330R family allows you to add multilayer switching to your existing
Avaya P330 stacks. The base product for the Avaya P330R family is the Avaya
P333R switch, which combines Avaya P333T capabilities with Layer 3 capabilities.
An Avaya P330 stack can contain up to 10 switches and up to 3 backup power
supply units. The stacked switches are connected using the Avaya X330STK
stacking sub-modules which plug into a slot in the back of the Avaya P330. They are
connected using the X330SC or X330LC cable (if the stack is split between 2 racks).
The Avaya X330RC cable connects the top and bottom switches in the stack and
provides redundancy and hot-swapability in the same way that modules can be
swapped in a modular switching chassis.
The Avaya P330 is fully compliant with IEEE standards for VLAN Tagging, Gigabit
Ethernet, Spanning Tree and Flow Control. This full standards-compliance,
combined with auto-negotiation for 10/100/1000 Mbps and half/full duplex
facilitates the expansion of your network to match your company's growing needs.
The P330R is fully compliant with IETF standards ARP, ICMP, DHCP/BOOOTP,
RIP v.1, RIP v.2, OSPF, IP Forwarding, and VRRP.
Avaya P333R User’s Guide1
Chapter 1Overview
Avaya P330 Family Features
•You can connect up to 10 Avaya P330 switches in a stack. Moreover, this stack
can be either in one rack or split over several racks using the X330LC Long
Cable, according to your requirements.
•Avaya X330STK - this stacking sub-module is used to connect Avaya P330
switches in a stack, via the Octaplane.
•Avaya P330 BUPS - this back-up power supply module supports up to four
Avaya P330 switches.
•One RJ-45/RS-232 front panel console connector for both terminal and modem
(future release) sessions.
•Two fan units in every switch, with operation sensors.
•One virtual IP address for managing the whole stack, the P330 stack is managed
as a single entity.
•Hot swapping of one switch at a time - by activation of the redundant cable:
— Does not disrupt the operation of other Avaya P330 switches.
— Does not change stack configuration.
— Does not require network downtime.
•Connection via Telnet to the IP of the stack Master or directly to the Router IP,
or from the front panel ports of any switch with:
— multiple levels of password protection.
— login and inactivity timeouts.
2Avaya P333R User’s Guide
Layer 2 Features
Auto-Negotiation
Every 10/100 port on the Avaya P330 supports Auto-Negotiation which
automatically detects and supports the operating mode and speed of a connected
device. Auto-negotiation is also supported on the Gigabit Ethernet ports for flow
control mode only.
This means that you can simply connect the Avaya P330 to Ethernet or Fast Ethernet
equipment at full or half duplex without configuration.
Congestion Control
Congestion control is a key element of maintaining network efficiency as it prevents
resource overload.
The Avaya P330 supports congestion control on all Ethernet ports, using the
following:
•Back Pressure in half duplex mode.
•IEEE 802.3x Flow Control in full duplex mode.
VLANs
The Avaya P330 VLANs are fully IEEE 802.1Q compliant and can handle up to 1k
tagged VLANs.
Chapter 1Overview
Multiple VLANs per Port
The Avaya P330 provides the ability to set multiple (1K) VLANs per port. The three
available Port Multi-VLAN binding modes are:
•Bound to All - the port is programmed to support the entire 3K VLANs range.
Traffic from any VLAN is forwarded through a port defined as Bound to All.
•Bound to Configured - the port supports all the VLANs configured in the
switch/stack. These may be either Port VLAN IDs (PVID) or VLANs that were
manually added to the switch.
•Statically Bound - the port supports VLANs manually configured on it.
Leaky VLAN
Leaky VLAN provides the ability to send unicast traffic between two ports on
different VLANs. Leaky VLAN will function only on modules (and sub-modules)
with C/S 2.0 and higher.
Avaya P333R User’s Guide3
Chapter 1Overview
Port Classification
With the Avaya P330, you can classify any port as regular or valuable. Setting a port
to valuable means that a link fault trap can be sent even when the port is disabled.
This feature is particularly useful for the software redundancy application, where
you need to be informed about a link failure on the dormant port.
Network TIME Acquiring Protocols
The P330 supports the SNTP Protocol over UDP port 123. You can choose between
SNTP or TIME protocol over UDP port 37.
MAC Security
You can define a port as secure, to prevent it from learning new mac addresses. If an
unknown MAC or station tries to access a secure port, the intruder request is sent to
the management station.
Link Aggregation Group (LAG)
LAG provides increased bandwidth and redundancy for critical high-bandwidth
applications such as inter-stack links and connections to servers. You can aggregate
the bandwidth of up to eight 10/100Base-Tx ports, two 100Base-FX or 1000Base-X
ports.
Load sharing ensures that if one of the port connections fails, the other connections
will assume the load seamlessly. Load balancing guarantees that the traffic load at
any level will be evenly divided among all the LAG links.
IP Multicast Filtering
IP Multicast allows you to send a single copy of an IP packet to multiple
destinations, and can be used for various applications including video streaming
and video conferencing.
On LANs, IP Multicast packets are transmitted in MAC Multicast frames.
Traditional LAN switches flood these Multicast packets to all stations in the VLAN.
Multicast filtering functions may be added to the Layer 2 switches to avoid sending
Multicast packets where they are not required. Layer 2 switches capable of
Multicast filtering send the Multicast packets only to ports that connect members of
that Multicast group. In order for this feature to operate correctly, you need in your
network a router issuing IGMP queries.
Note: IP Multicast filtering will function only based on the port's VLAN ID and not
based on any VLAN bound to the port.
4Avaya P333R User’s Guide
Radius Security
The Remote Authentication Dial-In User Service (RADIUS) is an IETF standard
(RFC 2138) client/server security protocol. Security and login information is stored
in a central location known as the RADIUS server. RADIUS clients such as the
Avaya P330, communicate with the RADIUS server to authenticate users.
All transactions between the RADIUS client and server are authenticated through
the use of a “shared secret” which is not sent over the network. The shared secret is
an authentication password configured on both the RADIUS client and its RADIUS
servers. The shared secret is stored as clear text in the client’s file on the RADIUS
server, and in the non-volatile memory of the Avaya P330. In addition, user
passwords are sent between the client and server are encrypted for increased
security.
Port Redundancy
Redundancy can be implemented between any two ports in the same stack at the
link level. You can also assign redundancy between any two LAGs in the stack or
between a LAG and a port. One port or LAG is defined as the primary port, and the
other as the secondary port. In case the primary port link fails, the secondary port
takes over.
Chapter 1Overview
Intermodule Redundancy
Intermodule redundancy includes all Port Redundancy functionality, and
additionally maintains port integrity even when the primary port link fails as the
result of a failure of the module. If the module on which the active port in an
Intermodule Port Redundancy pair is located is powered down or removed from
the stack, the secondary port in the Intermodule Port Redundancy pair takes over.
Only one pair per stack can be set for Intermodule Port Redundancy.
Stack Redundancy
In the unlikely event that an Avaya P330 switch or Octaplane link should fail, stack
integrity is maintained if the redundant cable is connected to the stack. The broken
link is bypassed and data transmission continues uninterrupted. The single
management IP address for the stack is also preserved for uninterrupted
management and monitoring.
Hot-Swappable
You can remove or replace any unit within the stack without disrupting operation
or performing stack-level reconfiguration. You can therefore adapt the P330 to your
requirements on the fly and with a down-time which is second to none.
When you remove an expansion module from the stack, all configuration
definitions on expansion modules are lost.
Avaya P333R User’s Guide5
Chapter 1Overview
If you wish to save configuration definitions, perform the following procedure:
1Power down the switch.
2Remove the expansion module.
3Insert the new module.
4Power up the switch.
Backup Power Supply
Each Avaya P330 module comes with a Backup Power Supply (BUPS) connector. If
the internal power supply fails, the Avaya P330 BUPS (available separately)
automatically supplies power to the switch for uninterrupted operation.
Fans
The Avaya P330 module fans have integrated sensors which provide advance
warnings of fan failure via management.
Network Management Agent (NMA) Redundancy
Since each Avaya P330 module has an integral SNMP agent, any module in a stack
can serve as the stack NMA while other NMAs act as redundant agents in “hot”
standby. If the “live” NMA fails then a backup is activated instantaneously.
Software Download
Avaya P330 includes a safe software download procedure in which backup code is
always present.
You should perform a reset after downloading software to the Module.
6Avaya P333R User’s Guide
Layer 3 Features
Modes of Operation
The P333R has three modes of operation (in each mode, Layer 2 is always active):
•Layer 2-only mode
•EZ2route mode and Layer 2
•Router mode and Layer 2.
Forwarding
The P333R forwards IP packets between IP networks. When it receives an IP packet
through one of its interfaces, it forwards the packet through one of its interfaces.
P333R supports multinetting, enabling it to forward packets between IP subnets on
the same VLAN as well as between different VLANs. Forwarding is performed
through standard means in both Router mode and EZ2route mode.
EZ2route Mode
Avaya’s EZ2route technology employs the power and simplicity of the
Avaya P333R hardware to perform true Layer 3 switching functions without the
administrative overhead associated with regular routers.
In EZ2route mode, Layer 3 switching is based on automatic learning. This
eliminates the need to configure the switch as a routing entity and eliminates the
complications associated with the configuration of regular routers.
In EZ2route mode, the P333R does not perform any active routing operations, such
as running routing protocols or performing resource-intensive route calculations.
This makes the P333R transparent to other routing entities on the network.
With EZ2route mode, you can increase Level 3 bandwidth simply by adding
additional P333R modules to the stack. A P333R in EZ2route mode can be used to
boost the performance of one or more routers outside the stack, and of other P333R
modules in the same stack operating in Router mode. Multiple P333R modules in
EZ2route mode can be stacked together to increase the Layer 3 forwarding capacity
of the stack.
In EZ2route mode, the P333R learns the network dynamically, and therefore
eliminates the need for configuration. However, there are some special instances,
where minimal configuration is needed.
Chapter 1Overview
Avaya P333R User’s Guide7
Chapter 1Overview
Redundancy
Routing protocols naturally provide some level of redundancy. However, IP
stations that are manually configured with a single ‘default gateway’ IP address do
not naturally recover when their default gateway fails. These stations do not
automatically try to use other routers or Layer-3-switches connected to the same
subnet.
The P333R supports two router redundancy protocols, VRRP and SRRP, to solve
this problem.
Virtual Router Redundancy Protocol (VRRP)
VRRP is an IETF protocol designed to support redundancy of routers on the LAN,
as well as load balancing of traffic. VRRP is transparent to host stations, making it
an ideal choice when redundancy, load balancing and ease of configuration are all
required.
The concept underlying VRRP is that a router can backup other routers, in addition
to performing its primary routing functions. This redundancy is achieved by
introducing the concept of a virtual router. A virtual router is a routing entity
associated with multiple physical routers. The routing functions of the virtual router
are performed by one of the physical routers with which it is associated. This router
is known as the master router.
For each virtual router, VRRP selects a master router. If the selected master router
fails, another router is selected as master router.
In VRRP, two or more physical routers can be associated with a virtual router, thus
achieving the extreme reliability inherent in the P333R SAFER architecture.
In a VRRP environment, host stations interact with the virtual router. They are not
aware that this router is a virtual router, and they are not affected when a new
router takes over the role of master router. This makes VRRP fully interoperable
with every host station.
VRRP can be activated on an interface using a single command while allowing for
the necessary fine-tuning of the many VRRP parameters. For a detailed description
of VRRP, refer to VRRP standards and published literature.
Simple Router Redundancy Protocol (SRRP)
Avaya P333R IP SRRP redundancy capabilities provide automatic backup Layer 3
switching for IP stations. P333R units can be configured to back each other up so
that if one fails the other will take over its forwarding functions. The backup P333R
is not idle. As long as both P333R units are functional, traffic is shared between
them. The P333R modules can be in the same Avaya P330 stack or in different,
connected, Avaya P330 stacks. The P333R can back up another P333R unit or any
other router.
8Avaya P333R User’s Guide
A P333R unit configured to back up another unit monitors the other’s status by
polling it at configured intervals, and automatically detects when the other fails and
when it becomes functional again. When detecting a failure, the backup P333R
sends a gratuitous ARP message that causes all stations to send their IP traffic to the
backup P333R MAC address instead of the failed unit MAC address. As long as it is
an active backup resulting from the failure of the main unit, the backup P333R
answers ARP requests for the main unit, providing its own MAC address.
OSPF Load Balancing
The P333R supports load balancing in Layer 3 by using OSPF Equal Cost Multipath
(ECM) and static routes multipath. OSPF and static multipath balances Layer 3 load
forwarding by splitting traffic into several possible equal-cost paths, thus freeing
additional bandwidth for traffic.
Policy – Quality of Service (QoS)
The P333R supports QoS by using multiple priority levels and IEEE 802.1p priority
tagging to ensure that data and voice receive the necessary levels of service.
The Avaya P333R can enforce policy on routed packets (per packet), according to
four criteria:
•The IEEE 802.1p priority tag in the incoming packet.
•The Diff-Serv byte (TOS field) in the IP header of the incoming packet.
•Matching the packet’s source or destination IP address to the configured
priority policy.
•Whether the packet source or destination TCP/UDP port number falls within a
pre-defined range.
Since the P333R is a multilayer switch, it can enforce centralized network policies
using Avaya’s RealNet Rules central policy management application.
Chapter 1Overview
Policy – Access Control
The P333R supports Access Control policy. The P333R uses policy lists containing
both Access Control rules and QoS rules. The policy lists are ordered by rule
indexing. Access Control rules define how the P333R should handle routed packets.
There are three possible ways to handle such packets:
•Forward the packet (Permit operation)
•Discard the packet (Deny operation)
•Discard the packet and notify the management station (Deny and Notify)
The Avaya P333R can enforce Access Control policy on each routed packet,
according to the following criteria:
•Matching the packet's source or destination IP address to the configured Access
Control policy.
Avaya P333R User’s Guide9
Chapter 1Overview
•Determine if the packet source or destination TCP/UDP port number falls
within a pre-defined range.
•Using the ACK bit of the TCP header.
The Avaya P333R access control rules are set-up using the Command Line Interface
and Avaya's RealNet Rules central policy management application.
DHCP/BOOTP Relay
The P333R supports the DHCP/BOOTP Relay Agent function. This is an application
that accepts DHCP/BOOTP requests that are broadcast on one VLAN and sends
them to a DHCP/BOOTP server that connects to another VLAN or a server that
may be located across one or more routers that would otherwise not get the
broadcast request. The relay agent handles the DHCP/BOOTP replies as well,
transmitting them to the client directly or as broadcast, according to a flag in the
reply message. Note that the same DHCP/BOOTP relay agent serves both the
BOOTP and DHCP protocols.
When there is more than one IP interface on a VLAN, the P333R chooses one of the
IP addresses on this VLAN when relaying the DHCP/BOOTP request. The DHCP/
BOOTP server then uses this address to decide from which subnet the address
should be allocated.
When the DHCP/BOOTP server is configured to allocate addresses only from a
single subnet among the different subnets defined on the VLAN, you may need to
configure the P333R with the relay address on that subnet so that the DHCP/
BOOTP server can accept the request.
DHCP/BOOTP Relay in P333R is configurable per VLAN and allows for two
DHCP/BOOTP servers to be specified. In this case, it duplicates each request, and
sends it to both servers. This provides redundancy and prevents the failure of a
single server from blocking hosts from loading.
DHCP/BOOTP Relay in P333R can be enabled or disabled.
RIP
P333R supports the widely used RIP routing protocol (both RIPv1 and RIPv2). The
RIPv1 protocol imposes some limitations on the network design with regard to
subnetting. When operating RIPv1, you must not configure variable length subnet
masks (VLMS). Each IP network must have a single mask, implying that all subnets
in a given IP network are of the same size. Also, when operating RIPv1, you must
not configure supernets, which are networks with a mask smaller than the natural
net mask of the address class, such as 192.1.0.0 with mask 255.255.0.0 (smaller than
the natural class C mask which is 255.255.255.0). For detailed descriptions of RIP
refer to the standards and published literature.
RIPv2 is a new version of the RIP routing protocol, not yet widely used but with
some advantages over RIPv1. RIPv2 solves some of the problems associated with
10Avaya P333R User’s Guide
Loading...
+ 240 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.