User's Manual
Table Of Contents
- 1. INTRODUCTION
- 2. INSTALLATION
- 3. SWITCH MANAGEMENT
- 4. WEB CONFIGURATION
- 4.1 Main Web page
- 4.2 System
- 4.2.1 Management
- 4.2.1.1 System Information
- 4.2.1.2 IP Configuration
- 4.2.1.3 IP Status
- 4.2.1.4 Users Configuration
- 4.2.1.5 Privilege Levels
- 4.2.1.6 NTP Configuration
- 4.2.1.6.1 System Time Correction Manually
- 4.2.1.7 Time Configuration
- 4.2.1.8 UPnP
- 4.2.1.9 DHCP Relay
- 4.2.1.10 DHCP Relay Statistics
- 4.2.1.11 CPU Load
- 4.2.1.12 System Log
- 4.2.1.13 Detailed Log
- 4.2.1.14 Remote Syslog
- 4.2.1.15 SMTP Configuration
- 4.2.1.16 Fault Alarm
- 4.2.1.17 Digital Input/Output
- 4.2.2 Simple Network Management Protocol
- 4.2.3 RMON
- 4.2.4 DHCP server
- 4.2.5 Industrial Protocol
- 4.2.6 Remote Management
- 4.2.1 Management
- 4.3 Switching
- 4.3.1 Port Management
- 4.3.2 Link Aggregation
- 4.3.3 VLAN
- 4.3.3.1 VLAN Overview
- 4.3.3.2 IEEE 802.1Q VLAN
- 4.3.3.3 VLAN Port Configuration
- 4.3.3.4 VLAN Membership Status
- 4.3.3.5 VLAN Port Status
- 4.3.3.6 Private VLAN
- 4.3.3.7 Port Isolation
- 4.3.3.8 VLAN setting example:
- 4.3.3.9 MAC-based VLAN
- 4.3.3.10 IP Subnet-based VLAN Membership Configuration
- 4.3.3.11 Protocol-based VLAN
- 4.3.3.12 Protocol-based VLAN Membership
- 4.3.4 Spanning Tree Protocol
- 4.3.5 Multicast
- 4.3.6 MLD Snooping
- 4.3.7 MVR (Multicast VLAN Registration)
- 4.3.8 LLDP
- 4.3.9 MAC Address Table
- 4.3.10 Loop Protection
- 4.3.11 UDLD
- 4.3.12 GVRP
- 4.3.13 PTP
- 4.3.14 Link OAM
- 4.4 Quality of Service
- 4.5 Security
- 4.6 Power over Ethernet
- 4.7 Ring
- 4.8 ONVIF
- 4.9 Maintenance
- 5. SWITCH OPERATION
- 6. TROUBLESHOOTING
- APPENDIX A: Networking Connection
- APPENDIX B : GLOSSARY
User’s Manual of IGS-5225 series
332
Authentication Initiation and Message Exchange
The switch or the client can initiate authentication. If you enable authentication on a port by using the dot1x
port-control auto interface configuration command, the switch must initiate authentication when it
determines that the port link state transitions from down to up. It then sends an EAP-request/identity frame to
the client to request its identity (typically, the switch sends an initial identity/request frame followed by one or
more requests for authentication information). Upon receipt of the frame, the client responds with an
EAP-response/identity frame.
However, if during bootup, the client does not receive an EAP-request/identity frame from the switch, the
client can initiate authentication by sending an EAPOL-start frame, which prompts the switch to request the
client's identity
I
f 802.1X is not enabled or supported on the network access device, any EAPOL frames from the
client are dropped. If the client does not receive an EAP-
request/identity frame after three attempts
to start authentication, the
client transmits frames as if the port is in the authorized state. A port in
the authorized state effectively means that the client has been successfully authenticated.
When the client supplies its identity, the switch begins its role as the intermediary, passing EAP frames between the client and
the authentication server until authentication succeeds or fails. If the authentication succeeds, the switch port becomes
authorized.
The specific exchange of EAP frames depends on the authentication method being used. “Figure 4-5-2” shows a message
exchange initiated by the client using the One-Time-Password (OTP) authentication method with a RADIUS server.
Figure 4-5-2-2: EAP Message Exchange
Ports in Authorized and Unauthorized States
The switch port state determines whether or not the client is granted access to the network. The port starts in
the unauthorized state. While in this state, the port disallows all ingress and egress traffic except for 802.1X