2008年12月31日 星期三

[藍森林-自由軟件] - [討論]為什麼要使用802.1Q TUNNELNG

[藍森林-自由軟件] - [討論]為什麼要使用802.1Q TUNNELNG

也就是為什麼要使用Q IN Q? (802.1q to 802.1q)

用TRUNK不就行了?

這個 我感覺就是 運營商 利用他的l2 網絡 為很多不同的用戶提供遠程的trunk中繼


Understanding 802.1Q Tunneling
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 of 4096 of the 802.1Q specification.

Using the 802.1Q tunneling 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 infrastructure even when they appear to be on the same VLAN. The 802.1Q tunneling expands VLAN space by using a VLAN-in-VLAN hierarchy and tagging the tagged packets. A port configured to support 802.1Q tunneling is called a tunnel port. When you configure tunneling, you assign a tunnel port to a VLAN that is dedicated to tunneling. Each customer requires a separate VLAN, but that VLAN supports all of the customer's VLANs.

Customer traffic tagged in the normal way with appropriate VLAN IDs come from an 802.1Q trunk port on the customer device and into a tunnel port on the service-provider edge switch. The link between the customer device and the edge switch is an asymmetric link because one end is configured as an 802.1Q trunk port and the other end is configured as a tunnel port. You assign the tunnel port interface to an access VLAN ID unique to each customer

用TRUNK就可以實現,為什麼還要用TUNNELING?

2種實現各有什麼優缺點??

為什麼 啊呀為什麼?



上面已經說的很清楚了。 功能說明了他的用途。


你遠端的 2個 站點間 想 中繼vlan。那麼 用 裸光纖也可以。 用 isp 提供的 q in q 服務也可以。但是,相信 後者費用 要低的多。

上面的E文是描述由於VLAN-ID只能有4096個,但是SP分配給客戶的VLAN-ID不只4096個那麼少,因此為了要解決VLAN-ID不夠用和重疊問題,可以使用802.1Q TUNNEL技術,因為TUNNEL接口可以有N多個。

謝謝2位.
有點眉目了.
Q IN Q 解決VLAN OVERLAP,和數量限制.
但是 Q IN Q 不能處理IP,不能轉發VLAN間數據.
這又是缺點.而TRUNK沒有這個問題.

所以, 大家繼續看還有什麼異同?

要處理IP重疊問題可以用MPLS VPN解決

QinQ中傳播的是公網數據(IP)還是私網數據??? 待續......

沒有留言:

張貼留言