Avaya P130 사용자 설명서
Chapter 1 Overview
2
Avaya P130 User’s Guide
Avaya P130 Management includes:
•
•
CLI (same CLI as the other Cajun Campus products).
— Connection via RS-232, Telnet, Modem and PPP.
— Telnet Passwords and Embedded Radius Client.
— Connection via RS-232, Telnet, Modem and PPP.
— Telnet Passwords and Embedded Radius Client.
•
P130 Web-based Management
•
MultiService Network Manager supports the P130 management.
•
Upload/Download
— Configuration file (in CLI format)
— Software Image file (single Bank) – download only
— Embedded Web file (download only)
— Log file (upload only).
— Configuration file (in CLI format)
— Software Image file (single Bank) – download only
— Embedded Web file (download only)
— Log file (upload only).
P130 Features
The standard P130 features of the switch are described below.
Auto-Negotiation
Every 10/100 port on the P130 supports Auto-Negotiation which automatically
detects and supports the duplex 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 P130 to Ethernet or Fast Ethernet
equipment at full or half duplex without configuration.
detects and supports the duplex 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 P130 to Ethernet or Fast Ethernet
equipment at full or half duplex without configuration.
Link Aggregation Group (LAG)
LAG provides increased bandwidth and redundancy for critical high-bandwidth
applications such as inter-switch links and connections to servers. You can
aggregate the bandwidth of up to eight 10/100Base-Tx or two 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 divided among all the LAG links (see also the LAG documentation
module).
LAGs can be created in the switch in order to increase bandwidth and resiliency in
switch-to-switch and server-to-switch connections. P133T supports up to 3 LAGs,
P133G2, P133GT2 and P133F2 support up to 4 LAGs, P134G2 supports up to 6
LAGs.
Each LAG is considered a single switch interface. Packets are not forwarded
between its ports, and non-unicast packets are transmitted only through one port -
the "Flood"(or "Base") port. In addition, packet order is maintained within each
session.
applications such as inter-switch links and connections to servers. You can
aggregate the bandwidth of up to eight 10/100Base-Tx or two 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 divided among all the LAG links (see also the LAG documentation
module).
LAGs can be created in the switch in order to increase bandwidth and resiliency in
switch-to-switch and server-to-switch connections. P133T supports up to 3 LAGs,
P133G2, P133GT2 and P133F2 support up to 4 LAGs, P134G2 supports up to 6
LAGs.
Each LAG is considered a single switch interface. Packets are not forwarded
between its ports, and non-unicast packets are transmitted only through one port -
the "Flood"(or "Base") port. In addition, packet order is maintained within each
session.