- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Checking out a problem in the lab using Virtual Co...
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
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
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
06-23-2010 01:04 PM
06-23-2010 01:04 PM
Checking out a problem in the lab using Virtual Connect Flex-10
Yan was looking for some help when looking at a VC Flex-10 issue.
**********************************************************************************
Our customer application environment was BL460CG6+VCFlex10+Vsphere4.1(topology as attached),but there were some problems during the implement.
- They use 2 VC flex-10 in C7000 with firmware 2.33 ,and smartlink and vlan tunneling was assigned. NIC driver version was bnx2x1.52 on Vsphere4.1; 2 VC module uplink to Cisco catalyst 3750G and Catalyst 4948 as the attachment.
Current issue is warning on switch, detail warning information as below:
May 27 14:28:55: %SW_MATM-4-MACFLAP_NOTIF: Host 0050.567e.cd76 in vlan 10 is flapping between port Po1 and port Po3
May 27 14:28:55: %SW_MATM-4-MACFLAP_NOTIF: Host 0050.5671.d3a0 in vlan 10 is flapping between port Po1 and port Po3
May 27 14:28:55: %C4K_EBM-4-HOSTFLAPPING: Host 00:50:56:7E:CD:76 in vlan 10 is flapping between port Po3 and port Po1
May 27 14:28:55: %C4K_EBM-4-HOSTFLAPPING: Host 00:50:56:71:D3:A0 in vlan 10 is flapping between port Po3 and port Po1
- Another issue: every physical NIC on 460G6 was split to 3 logical NIC, after perform smart link,the Vmware NIC can’t detect the uplink interrupt .so the using NIC model was Beacon Probing ,but the customer felt net speed slowly . It seemed DCC unavailable.
Your kind feedback is appreciated.
******************************************************************************************
Carlos jumped in:
*********************************************************************************
Yan,
In regards to your error:
May 27 14:28:55: %SW_MATM-4-MACFLAP_NOTIF: Host 0050.567e.cd76 in vlan 10 is flapping between port Po1 and port Po3
May 27 14:28:55: %SW_MATM-4-MACFLAP_NOTIF: Host 0050.5671.d3a0 in vlan 10 is flapping between port Po1 and port Po3
May 27 14:28:55: %C4K_EBM-4-HOSTFLAPPING: Host 00:50:56:7E:CD:76 in vlan 10 is flapping between port Po3 and port Po1
May 27 14:28:55: %C4K_EBM-4-HOSTFLAPPING: Host 00:50:56:71:D3:A0 in vlan 10 is flapping between port Po3 and port Po1
This is due to a teaming fail over. When the team fails to the secondary NIC the team MAC is learned on the second switch.Channel-group-3 and Channel-group-1. That is the reason for the flapping. Check the team status to see as to the reason why they are failing over.
************************************************************************
Any other comments or suggestions? Let us know if you have seen this problem and how you resolved it.