![Ruby Tech VS-2400S User Manual Download Page 56](http://html1.mh-extra.com/html/ruby-tech/vs-2400s/vs-2400s_user-manual_1498664056.webp)
VS-2400S 24 Ports VDSL2 Managed IP DSLAM with POTS splitter USER
’S MANUAL Ver.A3
55
show gvrp statistics <LIST>
Show GVRP statistics by port.
Parameters
:
<LIST> specifies the port list to be set
[
no
]
gvrp debug
[<
sys
|
err
|
pdu
|
db
|
gen
|
garp
|
gvrp
|
vlan
>]
Enable/disable GVRP debugging output.
4.0.3.1.3 QinQ VLAN Setting
Business customers of service providers often have specific requirements for VLAN IDs and the number of VLANs to be
supported. The VLAN ranges required by different customers in the same service-provider network might overlap, and traffic of
customers through the infrastructure might be mixed. Assigning a unique range of VLAN IDs to each customer would restrict
customer configurations and could easily exceed the VLAN limit (4096) of the IEEE 802.1Q specification. Using the QinQ
feature, service providers can use a single VLAN to support customers who have multiple VLANs. Customer VLAN IDs are
preserved, and traffic from different customers is segregated within the service-provider network, even when they appear to be in
the same VLAN. Using QinQ expands VLAN space by using a VLAN-in-VLAN hierarchy and retagging the tagged packets.
Virtual private networks (VPNs) provide enterprise-scale connectivity on a shared infrastructure, often Ethernet-based, with the
same security, prioritization, reliability, and manageability requirements of private networks. QinQ is a feature designed for
service providers who carry traffic of multiple customers across their networks and are required to maintain the VLAN and Layer
2 protocol configurations of each customer without impacting the traffic of other customers.
The following figure is an example of QinQ VLAN application.