cisco_trunks
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| cisco_trunks [2017/11/16 08:48] – walkeradmin | cisco_trunks [2023/03/09 22:35] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 39: | Line 39: | ||
| ---- | ---- | ||
| - | ==== Overview ==== | ||
| - | \\ | ||
| - | First of all, I would like to outline what I am trying to achieve. Look at the diagram below. | ||
| - | \\ | ||
| - | \\ | ||
| - | {{: | ||
| - | \\ | ||
| - | \\ | ||
| - | There are two sets of receivers (so consider two sets of multicast) coming from different head-ends. To keep the traffic separate, lets consider that the ports connected to the receivers on the left are all in VLAN A, and the receivers on the right are in VLAN B, as show below. | ||
| - | \\ | ||
| - | \\ | ||
| - | {{: | ||
| - | \\ | ||
| - | \\ | ||
| - | VLAN C is on another switch where our destination equipment is located. The link between the two Cisco switches is our Trunk. | ||
| - | \\ | ||
| - | \\ | ||
| - | {{: | ||
| - | \\ | ||
| - | \\ | ||
| - | The reason we are using a Trunk is that a single port (interface) can only carry traffic from a single VLAN, because an interface can only exist in one VLAN. So if you have multiple VLANs that you wish to carry from one switch to another, you need to use a Trunk. A Trunk can carry the traffic from mulitple VLANs. | ||
| - | \\ | ||
| - | \\ | ||
| - | ---- | ||
| ==== Example ==== | ==== Example ==== | ||
| \\ | \\ | ||
cisco_trunks.1510822117.txt.gz · Last modified: 2023/03/09 22:35 (external edit)