For blade and IBM blade server, the external ext port traffic is replicated to the internal int port. The implementation method is different.

How to copy traffic from the external port ext to the internal int port on the blade server to collect DNS traffic

(1) We have fixed the packet capture problem for nortel_32r1860 switch module 112.4.20.12dns of the IBM blade server.

After exploration and testing, it seems that the beidian switch module does not use the image command to achieve replication traffic (although there is a corresponding port-loading ing Monitor-port... command, but it does not take effect), but the traffic can be copied in the same VLAN. If you want to copy the ext3 traffic to int14, you just need to put ext3 and int14 under the same vlan11, you can skip tagging.

(2) for blade servers, the use of mirror commands dedicated to mirror is required to achieve traffic replication, but the same VLAN method cannot be used successfully.

This article is from the blog "the blog", and will not be reposted!

For  blade and IBM blade server, the external ext port traffic is replicated to the internal int port. The implementation method is different.