- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Challenge in port mirroring configuration on Cisco...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-06-2015 12:45 PM
05-06-2015 12:45 PM
Challenge in port mirroring configuration on Cisco switch connected to VC
Ramu had a customer question:
************
Hi Champs
Need your help,.
We are working on a large customer requirement where production network traffic needs to be mirrored to another chassis through Cisco external switch. Customer is not interested in doing port mirroring on VC level as he needs to send data to VM in separate Chassis.
***********
Reply from Vincent:
***********
You already have the proper solution: put the analyzer on a rack server, not on a blade connected to VC modules.
VC will never forward Ethernet unicast frames to a blade server when it knows the destination MAC address in the frame resides elsewhere than the blade server in question. All you could get captured on the blade server is broadcast frames and unicast frames where the destination MAC is unknown to VC, or is the blade server itself.
You just CANNOT put a network analyzer on a blade server connected to VC to capture traffic coming from the outside, there is no configuration that can make it work.
*************
Comments?