n The VLAN tag of the Ethernet data
n The VLAN tag added by Ethernet processing board when the Ethernet data has no VLAN
The Ethernet switch interconnected with NE1 (convergence node) should be able to identify the above two kinds of VLANs. Otherwise, the networking in this example will fail.
Community Users 1 and 2 are in city 1 and city 2 respectively. The two users need to communicate with each other
User 3 and User 4 are users in cyber cafes in city 1 and city 2 respectively. The two users need to communicate with each other as well.
Services of the communities and those of cyber cafes are isolated completely. The peak hour of communities is at night and that of cyber cafes is in the day, so they can share a 10 Mbit/s bandwidth. The Ethernet switch equipment of them can provide 100 Mbit/s Ethernet electrical interfaces but does not support VLAN.
The bandwidth sharing requirement in this application can be realized by the OptiX OSN 3500. Figure 4-3 shows the networking diagram.
Figure 4-3 EPL service application (shared VCTRUNK)
|
Implementation |
Port route + VLAN route
In city 1, the service of User 1 is accessed through MAC1 and the service of User 3 is accessed through MAC2 of NE1, added with different VLANs (VLAN ID: 100 and VLAN ID: 200). After converging by the Ethernet board, all services are sent to city 2 over one VCTRUNK. In city 2, the Ethernet processing board of NE2 processes the service (with VLAN ID: 100 and VLAN ID: 200) from city 1, and sends it to User 2 and User 4 respectively based on the VLAN ID number. |
||
|
Hardware configuration |
Configure one EFS4 board in NE1 to access Ethernet services from User 1 and User 3. Configure one EFS4 board in NE2 to access Ethernet services from User 2 and User 4. For slots of the EFS4 board, refer to “Appendix A Network Configuration Requirements”. |
||
|
Service route |
NE1 |
NE2 |
|
|
User 1 ïð User 2 |
MAC1 + VLAN ID: 100 ïð VCTRUNK1 + VLAN ID: 100 |
VCTRUNK1 + VLAN ID: 100 ïð MAC1 + VLAN ID: 100 |
|
|
User 3 ïð User 4 |
MAC2 + VLAN ID: 200 ïð VCTRUNK1 + VLAN ID: 200 |
VCTRUNK1 + VLAN ID: 200 ïð MAC2 + VLAN ID: 200 |
|
|
Bind VCTRUNK1 to five VC-12s |
|||
|
Protection |
The service can be protected by the SDH equipment. |
||
& Note:
You can apply the same principles to implementation of GE services except that the GE service requires EGS2 board and binding VCTRUNK to one or more VC-3s.
The MSTP equipment can realize the convergence of EPL services and bandwidth sharing on the line. The VLAN label makes it possible that more than one EPL service shares a MAC port or VCTRUNK, thus saving the port and bandwidth resources.
This application is applicable to users have different peak hours so that they can preempt the bandwidth freely.
Ingress and Egress are two operations to label switch path (LSP). Ingress indicates adding MPLS label. Egress indicates stripping MPLS label. The typical application of the EVPL service is to perform ingress when services enter the network and egress when services leave the network. This application isolates different services in the network through MPLS label.
EVPL adopts the MPLS technology, whose transmission efficiency is lower than EPL and the configuration is more complicated.
Company A has two branches (1 and 2) located in city 1 and city 2 respectively, the M&S department in branch 1 needs to communicate with that in branch 2, so does the technical support department. The communication between the M&S departments shares the 10 Mbit/s bandwidth with that between the technical support departments. However, the two services are completely isolated. The VLAN ID accessed by the two departments is both 100. Ethernet switch in Company A can provide the 100 Mbit/s Ethernet electrical interface.
Уважаемый посетитель!
Чтобы распечатать файл, скачайте его (в формате Word).
Ссылка на скачивание - внизу страницы.
