Alcatel-Lucent OS9-GNI-U24 ユーザーズマニュアル
Alcatel-Lucent
Page 87
OmniSwitch 9000
S
S
S
i
i
i
m
m
m
p
p
p
l
l
l
i
i
i
f
f
f
i
i
i
e
e
e
d
d
d
M
M
M
a
a
a
n
n
n
a
a
a
g
g
g
e
e
e
a
a
a
b
b
b
i
i
i
l
l
l
i
i
i
t
t
t
y
y
y
ecognizing a great demand in the marketplace and customers expectation for a level of synergism in the network management, Alcatel.Lucent has developed a
comprehensive, unified, and simplified network and switch management solutions for its full array of networking products including the AOS OmniSwitch
product family. The OS9000 switch and network management industry proven features offers the network administrators ease-of-use and ease of management.
The following is only a highlight of the advanced network and switch management features supported by the OmniSwitch 9000 Series:
comprehensive, unified, and simplified network and switch management solutions for its full array of networking products including the AOS OmniSwitch
product family. The OS9000 switch and network management industry proven features offers the network administrators ease-of-use and ease of management.
The following is only a highlight of the advanced network and switch management features supported by the OmniSwitch 9000 Series:
Diagnosing Switch problems:
o
Port Mirroring
o
RMON: Supports RFC 2819 RMON group (1-Statistics, 2-History, 3-Alarm, and 9-Events)
o
Switch Health
o
Monitoring Memory Tools
o
Switch Logging
Authentication or AAA Servers
Policy Servers
Dual image and dual configuration file storage provides backup
4.2.18
Intuitive Alcatel.Lucent CLI for familiar interface and reduced training costs
Easy to use point and click web based element manager with built-in help for easy configuration of new technology features
Remote telnet management or secure shell
Port based, port mirroring for troubleshooting, supports four sessions with four source to one destination configuration.
Human readable ASCII based config files for offline editing and bulk configuration
IGMPv1/v2/v3 snooping to optimize multicast traffic
BootP/DHCP client allows auto-config of switch IP information to simplify deployment
Auto-negotiating 10/100/1000 ports automatically configure port speed and duplex setting
Auto MDI/MDIX automatically configures transmit and receive signals to support straight thru and crossover cabling
DHCP relay to forward client requests to a DHCP server
4.1.5
SNMPv1/v2/v3
Integration with SNMP manager OmniVista for network wide management
System event log
Network Time Protocol (NTP) for network wide time synchronization
Alcatel.Lucent Interswitch Protocols (AIP)
4.1.6
o
AMAP: Alcatel.Lucent Mapping Adjacency Protocol (AMAP) for building topology maps within OmniVista
o
GMAP
Alcatel.Lucent Interswitch Protocols (AIP)
Alcatel.Lucent Interswitch Protocols (AIP) is used to discover adjacent switches and retain mobile port
information across switches. The following protocols are supported:
• Alcatel.Lucent Mapping Adjacency Protocol (AMAP), which is used to discover the topology of
OmniSwitches and OmniSwitch/Routers (Omni S/R).
• Group Mobility Advertisement Protocol (GMAP), which is used to retain learned mobile port and
protocol information.
These protocols are independent of each other and perform separate functions.
information across switches. The following protocols are supported:
• Alcatel.Lucent Mapping Adjacency Protocol (AMAP), which is used to discover the topology of
OmniSwitches and OmniSwitch/Routers (Omni S/R).
• Group Mobility Advertisement Protocol (GMAP), which is used to retain learned mobile port and
protocol information.
These protocols are independent of each other and perform separate functions.
Interswitch Protocol (AMAP)
Alcatel.Lucent Interswitch Protocols (AIP) is used to discover adjacent switches and retain mobile port
information across switches. By default, AMAP is not enabled.
The Alcatel.Lucent Mapping Adjacency Protocol (AMAP) is used to discover the network topology of
OmniSwitch, switches in a particular installation. Using this protocol, each switch determines which
OmniSwitch; Omni S/R and/or OmniAccess switches are adjacent to it by sending and responding to
Hello update packets. For the purposes of AMAP, adjacent switches are those that:
• Have a Spanning Tree path between them
• Do not have any switch between them on the Spanning Tree path that has AMAP enabled
information across switches. By default, AMAP is not enabled.
The Alcatel.Lucent Mapping Adjacency Protocol (AMAP) is used to discover the network topology of
OmniSwitch, switches in a particular installation. Using this protocol, each switch determines which
OmniSwitch; Omni S/R and/or OmniAccess switches are adjacent to it by sending and responding to
Hello update packets. For the purposes of AMAP, adjacent switches are those that:
• Have a Spanning Tree path between them
• Do not have any switch between them on the Spanning Tree path that has AMAP enabled
Authentication Servers or AAA servers
(authentication, authorization, and accounting)
Authentication servers are sometimes referred to as AAA servers (authentication, authorization, and
accounting). These servers are used for storing information about users who want to manage the switch
(Authenticated Switch Access) and users who need access to a particular VLAN(s) (Authenticated
VLANs).
RADIUS or LDAP servers may be used for Authenticated Switch Access and/or Authenticated
VLANs. Another type of server, SecurID’s ACE/Server, may be used for authenticated switch access
only; the ACE/Server is an authentication-only server (no authorization or accounting). Only RADIUS
servers are supported for 802.1X Port-Based Network Access Control.
Authentication Servers Specifications:
RADIUS RFCs Supported:
accounting). These servers are used for storing information about users who want to manage the switch
(Authenticated Switch Access) and users who need access to a particular VLAN(s) (Authenticated
VLANs).
RADIUS or LDAP servers may be used for Authenticated Switch Access and/or Authenticated
VLANs. Another type of server, SecurID’s ACE/Server, may be used for authenticated switch access
only; the ACE/Server is an authentication-only server (no authorization or accounting). Only RADIUS
servers are supported for 802.1X Port-Based Network Access Control.
Authentication Servers Specifications:
RADIUS RFCs Supported:
RFC 2865–Remote Authentication Dial In User Service (RADIUS)
RFC 2866–RADIUS Accounting
RFC 2867–RADIUS Accounting Modifications for Tunnel Protocol Support
RFC 2868–RADIUS Attributes for Tunnel Protocol Support
RFC 2809–Implementation of L2TP Compulsory Tunneling via RADIUS
RFC 2869–RADIUS Extensions
RFC 2548–Microsoft Vendor-specific RADIUS Attributes
RFC 2882–Network Access Servers Requirements: Extended RADIUS Practices
LDAP RFCs Supported:
RFC 1789–Connectionless Lightweight X.5000 Directory Access Protocol
RFC 2247–Using Domains in LDAP/X.500 Distinguished Names