Services on the QFX Series - Juniper.net
Services on the QFX Series - Juniper.net
Services on the QFX Series - Juniper.net
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
<str<strong>on</strong>g>Services</str<strong>on</strong>g> <strong>on</strong> <strong>the</strong> <strong>QFX</strong> <strong>Series</strong><br />
If a packet for pvlan100 enters <strong>on</strong> <strong>the</strong> promiscuous trunk port and exits <strong>on</strong> <strong>the</strong> isolated<br />
access port, <strong>the</strong> original packet is untagged <strong>on</strong> egress because it is exiting <strong>on</strong> an access<br />
port. However, <strong>the</strong> mirror copy retains <strong>the</strong> tag for pvlan100 when it is sent to <strong>the</strong> analyzer.<br />
Here is ano<strong>the</strong>r example: If a packet for comm300 ingresses <strong>on</strong> <strong>the</strong> community port and<br />
egresses <strong>on</strong> <strong>the</strong> promiscuous trunk port, <strong>the</strong> original packet carries <strong>the</strong> tag for pvlan100<br />
<strong>on</strong> egress, as expected. However, <strong>the</strong> mirrored copy retains <strong>the</strong> tag for comm300 when<br />
it is sent to <strong>the</strong> analyzer.<br />
Soluti<strong>on</strong><br />
This is expected behavior.<br />
Related<br />
Documentati<strong>on</strong><br />
• Understanding Port Mirroring <strong>on</strong> page 3<br />
• Example: C<strong>on</strong>figuring Port Mirroring for Local Analysis <strong>on</strong> page 13<br />
• Example: C<strong>on</strong>figuring Port Mirroring for Remote Analysis <strong>on</strong> page 17<br />
80<br />
Copyright © 2013, <strong>Juniper</strong> Networks, Inc.
Change language