Table B.3Pinout of the Required Connection for Console Communica-
tions205
Table 4.1Navigation, Cursor Movement and Shortcuts ..................222
P332G-ML User’s Guidexv
List of Tables
xviP332G-ML User’s Guide
Chapter 1
Overview
The P332G-ML is a powerful Multilayer Gigabit Ethernet stackable switch . It
enhances the P330 line to support high density multilayer Gigabit Ethernet
solutions.
The Avaya P332G-ML has 12 GBIC (SFP) f iber-opti c ports a nd provides Layer 2 a nd
optional Layer 3 Gigabit Ethernet switching. The high port density and stackability
make it ideal for distribution and mid-sized backbo ne applications where
performance and reliability are more important than ever. Like other members of
the Avaya P330 family, the P332G-ML is available in AC and DC versions.
The low cost and scalability of the Avaya P332G-ML allow you to deploy Gigabit
Ethernet throughout your network. For the first time, all your users can benefit from
the latest development in Ethernet technology.
The Avaya P332G-ML adds affordable multilayer high-density Gigabit Ethernet
capabilities to the Avaya P330 stackable switching system.
Multilayer switching with QoS, Policy Management and multiple levels of security
and redundancy make the Avaya P332G-ML an ideal part of a converged network.
The Avaya P332G-ML is part of the P330 line. A P330 stack can contain up to 10
switches. The stacked switches are connected using stacking sub-modules which
plug into a slot in the back of the P330. They are connected using the X330SC cable
or the X330LC or X330L-SC cable (if the stack is split between 2 racks). The X330RC
and X330L-RC cable (if the stack is split between 2 racks) connects the top and
bottom switches in the stack and provid es redu ndancy.
The P332G-ML is ready for voice and data applications, and supports IEEE
standards for VLAN Tagging, Gigabit Ethernet, Spanning Tree and Flow Control.
The P332G-ML module is fully IEEE 802.1Q compliant and can handle up to 253
tagged VLANs from a range of 1 to 3071.
Multiple VLANs per Port
The P332G-ML provides the ability to s et multiple VL ANs per port. The three
available Port Multi-VLAN binding mo d es 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.
Link/Port Redundancy
Redundancy can be implemented between any two ports in the same stack at the
link level. You can also assign redund ancy between any two LAGs in the st ack 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
Network Management Agent (NMA) Redundancy
Since each P332G-ML 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 activa ted instantaneously.
Intermodule Redundancy
Intermodule redundancy inclu des 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.
P332G-ML User’s Guide3
Chapter 1Overview
Stack Redundancy
In the unlikely event that a P330 switch or Octaplane link should fail, stack integrity
is maintained if the redundant cable is connected to th e stack. The broken link is
bypassed and data transmission contin ues uninterrupted. The single management
IP address for the stack is also preserved for uninterrupted management and
monitoring.
Spanning Tree
P332G-ML supports the IEEE 802.1D Standard Spanning Tree Protocol. This
protocol detects and eliminates logical loops in the network and auto matically
places some ports on stand by to form a network with the most efficien t path ways.
Hot-Swappable
You can remove or replace any unit within the stack with out 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.
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.
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. RA DIUS clients such as the
P332G-ML, communicate with the RADIUS server to authenticate users.
All transactions between the RADIUS client and server are auth enticated 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 cli e nt 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 P332G-ML. In addition, user
passwords are sent between the client and server are encrypted for increased
security.
4P332G-ML User’s Guide
Port Classification
With the P332G-ML, 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 link/intermodule redundancy application,
where you need to be informed about a link failure on the dormant port.
Network TIME Acquiring Protocols
The P332G-ML supports the SNTP Protocol over UDP port 123. You can choose
between SNTP or TIME protocol over UDP port 37.
Link Aggregation Group (LAG)
LAG provides increased bandwidth and redundancy for critical high-bandwidth
applications such as int er-stack links and connections to servers. With the P332G ML you can aggregate the bandwidth of groups of up to four 1000Base-X ports in a
LAG, or pairs of adjacent 1000Base-X ports within a group, for a maximum of 6
LAGs per switch.
IP Multicast Filtering
IP Multicast allows you to send a sin gle copy of an IP packet to multiple
destinations, and can be used fo r vario us applications including video streamin g
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.
Chapter 1Overview
Note: IP Multicast filtering will function only based on the port's VLAN ID and not
based on any VLAN bound to the port.
P332G-ML User’s Guide5
Chapter 1Overview
Congestion Control
Congestion control is a key element of maintaining network efficiency as it prevents
resourc e overl oad.
The P332G-ML supports congestion con trol on all Ethe rnet ports , usi ng IEEE 802 .3x
Flow Control in full duplex mode.
Backup Power Supply
Each P332G-ML module comes with a Backup Power Supply (BUPS) connector. If
the internal power supply fails, the P330-ML BUPS (available separately)
automatically supplies power to the swit ch f or uninterrupted operation.
Note: The BUPS used with P332G-ML units is different from the BUPS used with
other P330 products
Fans
The P332G-ML module fans have integrated sensors which provide advance
warnings of fan failure via management.
Software Download
P332G-ML includes a safe software download procedure in which backup code is
always present.
You should perform a reset after downloading software to the Module.
6P332G-ML User’s Guide
Layer 3 Features
Modes of Operation
The P332G-ML has two modes of operation (in each mode, Layer 2 is always active):
•Layer 2-only mode
•Router mode and Layer 2.
Note: This section is only applicable if you either purchased a preconfigured
P332G-ML or purchased a Routing License Key Certificate and activated the License
Key.
Forwarding
The P332G-ML 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. P332G-ML 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 Router mode.
Redundancy
Routing protocols naturall y provide some level of redundancy. However, IP
stations that are manually con figured with a single ‘default gatewa y’ IP address do
not naturally recover when their default gatewa y fails. These stations do not
automatically try to use other routers or Layer-3-switches connected to the same
subnet.
The P332G-ML supports two router redundancy protocols, VRRP and SRRP, to
solve this problem.
Chapter 1Overview
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 stati ons, making it
an ideal choice when redundancy, lo ad 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.
P332G-ML User’s Guide7
Chapter 1Overview
In VRRP, two or more physical routers can be associated with a virtual router, thus
achieving the extreme reliability inherent in the 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)
P332G-ML IP SRRP redundancy capabilities provide automatic backup Layer 3
switching for IP stations. P332G-ML units can be configured to back each other up
so that if one fails the other will take over its forwarding functions. The backup
P332G-ML is not idle. As long as both P332G-ML units are functional, traf f ic is
shared between them. The P332G-ML modules can be in the same P330 stack or in
different, connected, P330 stacks. The P332G-ML can back up another P332G-ML
unit or any other router.
A P332G-ML 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 de tecting a failure, the backup P332G-ML
sends a gratuitou s ARP mes sage th at caus es all stations to send their IP traffic to the
backup P332G-ML 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 P332GML answers ARP requests for the main unit, providing its own MAC address.
Policy – Quality of Service (QoS)
The P332G-ML 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 P332G-ML 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.
The P332G-ML can enforce centralized network po licies using the CajunRules
central policy management application.
8P332G-ML User’s Guide
Policy – Access Control
The P332G-ML supports Access Control policy. The P332G-ML 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 P332G-ML 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 P332G-ML 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.
•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 P332G-ML access control rules are set-up using the Command Line Interface
and the CajunRules central policy management application.
DHCP/BOOTP Relay
The P332G-ML 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 P332G-ML 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 P332G-ML with the relay address on that subnet so that the DHCP/
BOOTP server can accept the request.
DHCP/BOOTP Relay in P332G-ML 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 P332G-ML can be enabled or disabled.
Chapter 1Overview
P332G-ML User’s Guide9
Chapter 1Overview
RIP
P332G-ML supports the widely us ed RI P routing protocol (both RIPv1 and RIPv2).
The RIPv1 protocol imposes some limita tions 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 operati ng R I Pv1, 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 rou ting protocol, not yet widely used but with
some advantages over RIPv1. RIPv2 solves some of the problems associated with
RIPv1. The most important change in RIPv2 is the addition of a subnet mask field
which allows RIPv2 to support variab le length subnets. RIPv2 also in cludes an
authentication mechanism similar to the one used in OSPF.
Configuration of the RIP version, 1 or 2, is per IP interface (default is version 1).
Configuration should be homogenous on all routers on each subnet, i.e. there
should not be both RIPv1 and RIPv2 routers on the same subnet. However, different
IP interfaces of the P332G-ML can be configured with di ffere nt RIP ver sions (as long
as all routers on the subnet are configured to the same version).
RIPv2 and RIPv1 are considered the same protocol with regard to redistribution to/
from OSPF and static route preferences.
OSPF
P332G-ML supports the OSPF routing protocol. P332G-ML can be configured as an
OSPF Autonomous System Boundary Router (ASBR) by configuration of route
redistribution. P332G-ML can be installed in the OSPF backbone area (area 0.0.0.0)
or in any OSPF area that is part of a multiple areas network. However, P332G-ML
cannot be configured to be an OSPF area border router itself.
The P332G-ML supports the equal-cos t multipath (ECMP) feature which allows
load balancing by splitting traf fic between several equivalent paths.
While OSPF can be activated with default values for each in terface using a single
command, many of the OSPF parameters are configurable.
For a detailed description of OSPF, refer to the O SPF standards and published
literature.
10P332G-ML User’s Guide
Static Routes
Chapter 1Overview
Static routes can be configured to the P332G-ML. They are never timed-out, or lost
over reboot, and can only be removed by manual configuration. Deletion (by
configuration) of the IP interface deletes the static routes using this interface as well.
A static route becomes inactive if the interface over which it is defined is disabled.
When the interface is enabled, the static route becomes active again.
Static routes can only be configured for remote destina tions, i.e. destinations that
are reachable via another router as a next hop. The next hop router must belong to
one of the directly attached networks for which P332G-ML has an IP interface.
“Local” static routes, such as those that have no next hop , are not allowe d.
Two kinds of static routes can be configured, High Preference static routes which are
preferred to routes learned from any routing protocol and Low Preference static
routes which are used temporarily until the route is learned from a routing protocol.
By default, a static route has Low Preference.
Static routes can be advertised by routing protocols (i.e. RIP, OSPF) as described
under Route redistribution.
Static routes also support load-balanci ng similar to OSPF. A static rou te can be
configured with multiple next hops so that traf f ic is split between these next hops.
This can be used for example to load-balance traffic between several firewalls which
serve as the default gateway.
Route Redistribution
Route redistribution is the interaction of multiple routing protocols. OSPF and RIP
can be operated concurrently in P332G-ML. In this case, P332G-ML can be
configured to redistribute routes learned fro m one protocol into the d omain of the
other routing protocol. Similarly, static routes may be redistributed to RIP and to
OSPF. Route redistribution should not be configured carelessly, as it involves metric
changes and might cause routing loops in the presence of other routes with
incompatible schemes for route redistribution and route preferences.
The P332G-ML scheme for metric translation in route redistribution is as follows:
•Static to RIP metric configurable (default 1)
•OSPF internal metric N to RIP metric 1
•OSPF external type 1 metric N to RIP metric 1
•OSPF external type 2 metric N to RIP metric N+1
•Static to OSPF external type 2, metric configurable (default 1)
•RIP metric N to OSPF external type 2, metric N
•Direct to OSPF external type 2, metric 1.
P332G-ML User’s Guide11
Chapter 1Overview
By default, the P332G-ML does not redistribute routes between OSPF and RIP.
Redistribution from one protocol to the other can be configured. Static routes are, by
default, redistributed to RIP and OSPF. P332G-ML allows the user to globally
disable redistribution of static routes to RIP, and separately to globally disable
redistribution of static routes to OSPF. In addition, P332G-ML lets the user
configure, on a per static route basis, whether the route is to be redistributed to RIP
and OSPF, and what metric (in the range of 1-15). The default state is to enable the
route to be redistributed at metric 1. When static routes are redistributed to OSPF,
they are always redistributed as external type 2.
Route Preferences
The routing table may contain routes from different sources. Routes to a certain
destination may be learned ind e pendently from RIP and from OS PF, and at the
same time, a static route can also be configured to the same destination. While
metrics are used to choose between routes of the same protocol, protocol
preferences are used to choose between routes of different protocols.
The preferences only apply to routes for the same destination IP address and mask.
They do not override the longest-match choice. For example, a high-preference
static default route will not be preferred over a RIP route to the subnet of the
destination.
P332G-ML protocol preferences are listed below from the most to the least
preferred:
The P332G-ML can be configured to relay netbios UDP broadcast packets. This
feature is used for applications such as WINS that use broadcast but may need to
communicate with stations on o ther subnets or VLANs.
Configuration is performed on a per-interface basis. Whe n a ne tbios broadcast
packet arrives from an interface on which netbios rebroadcast is enabled, the packet
is distributed to all other interfaces configured to rebroadcast netbios.
If the netbios packet is a net-directed broadcast (e.g., 149.49.255.255), the packet is
relayed to all other interfaces on the list, and the IP destination of the packet is
replaced by the appropriate interface broadcast address.
If the netbios broadcast packet is a limited broadcast (e.g., 255.255.255.255), it is
relayed to all VLANs on which there are netbios-enabled interfaces. In that case, the
12P332G-ML User’s Guide
Loading...
+ 212 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.