Due to the VLAN flooding all the NOD-B equipments are not getting their proper VLANs, causes the NOD-Bs are down. Kindly see the below example for the better understanding.
The MUB & IUB of NOD-B is down & also the external clock & SOIP is shown the down alarm.
Kindly follow the process of creating ERPS to avoid the VLAN flooding:
1. Define the East/West port for perticular NEs.
2. Choose a RPL port.
3. Configure the ERPS & also transparent all the VLANs with all the NEs except RPL NE.
4. Configure the ERPS in RPL NE with RPL port & control VLAN
5. Transparent the VLAN IDs with RPL NE.
This above process will resolve the VLAN flooding, cause here we are not defining ERPS to all the NEs except RPL NE. If we define the RPL port then that pertucular port will block for the main path, so VLAN flooding will not happening in any case.
The following snap is about the bypassing all the VLANs throughout the ring, this is an instance of one node:
In this node we are bypassing all the VLANs from 4IFU2 to 3IFU2.
This window is all about configuring the ERPS in a perticular NODE.
Only RPL node should be configure with RPL OWNER RING NODE FLAG & RPL Port.
This should be configure before transparent all the VLANs throughout the ring, otherwise this will be the wrong configuration.
During creating the ERPS protection in a hybrid ring we have to make transparent all the VLANs through out the ring. Wrong service implementation may cause the VLAN flooding.
Ethernet regularly uses “Broadcast” packets, which flood a LAN to all devices:
1. Unknown MAC addresses get broadcast to the LAN
2. Various protocols broadcast to obtain information
3. This results in a basic workload for each receiver independent of whether the information is addressed to them or not
For the above reasons, VLAN system comes into the picture, now we need to be careful about this VLAN flooding.
Because it will occupy the bandwith & become a mess in a network.