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.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.8.1 Two Separate 802.1Q VLANs
- 4.3.3.8.2 VLAN Trunking between two 802.1Q aware switches
- 4.3.3.8.3 Port Isolate
- 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 Ring
- 4.7 Maintenance
- 4.8 Power over Ethernet
- 4.9 ONVIF
- 4.10 Routing
- 4.10.1 IP Configuration
- 4.10.2 IP Status
- 4.10.3 Routing Information Base
- 4.10.4 OSPF
- 4.10.4.1 Global Configuration
- 4.10.4.2 Network Area
- 4.10.4.3 Passive Interface
- 4.10.4.4 Stub Area
- 4.10.4.5 Area Authentication
- 4.10.4.6 Area Range
- 4.10.4.7 Interface Configuration
- 4.10.4.8 Virtual Link
- 4.10.4.9 Global Status
- 4.10.4.10 Area Status
- 4.10.4.11 Neighbor Status
- 4.10.4.12 Interface Status
- 4.10.4.13 Configuration Example of OSPFv4
- 5. SWITCH OPERATION
- 6. TROUBLESHOOTING
- APPENDIX A: Networking Connection
- APPENDIX B : GLOSSARY
User’s Manual of IGS-6325 series
165
ports. If the packet doesn't have an 802.1Q VLAN tag, the port will not alter the packet. Thus,
all packets received by and forwarded by an untagging port will have no 802.1Q VLAN
information. (Remember that the PVID is only used internally within the Switch). Untagging is
used to send packets from an 802.1Q-compliant network device to a non-compliant network
device.
Frame Income
Frame Leave
Income Frame is tagged Income Frame is untagged
Leave port is tagged Frame remains tagged Tag is inserted
Leave port is untagged Tag is removed Frame remain untagged
Table 4-3-3-1: Ingress / Egress Port with VLAN VID Tag / Untag Table
■ IEEE 802.1Q Tunneling (Q-in-Q)
IEEE 802.1Q Tunneling (Q-in-Q) is designed for service providers carrying traffic for multiple customers across their networks.
Q-in-Q tunneling is used to maintain customer-specific VLAN and Layer 2 protocol configurations even when different
customers use the same internal VLAN IDs. This is accomplished by inserting Service Provider VLAN (SPVLAN) tags into the
customer’s frames when they enter the service provider’s network, and then stripping the tags when the frames leave the
network.
A service provider’s customers may have specific requirements for their internal VLAN IDs and number of VLANs supported.
VLAN ranges required by different customers in the same service-provider network might easily overlap, and traffic passing
through the infrastructure might be mixed. Assigning a unique range of VLAN IDs to each customer would restrict customer
configurations, require intensive processing of VLAN mapping tables, and could easily exceed the maximum VLAN limit of
4096.
The Industrial Managed Switch supports multiple VLAN tags and can therefore be used in MAN applications as a provider
bridge, aggregating traffic from numerous independent customer LANs into the MAN (Metro Access Network) space. One of