- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Virtual Connect NO_COMM problem
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
04-13-2014 05:47 AM
04-13-2014 05:47 AM
Virtual Connect NO_COMM problem
Hi,
we have a Degrade warning on all server profiles from yeasterday, when I checked the VC (enc1 bay1 VC FlexFabric 10/24) it shows "Overall status: No communication" and "OA communication status: Failed". the VC provide no comunication and all up-links are dead (Not linked), and in OA bay1 information I see: "Management IP Address: Unknown"
when I reset or turn it off and on again I see the following system logs:
------
2014-04-13T16:38:17+04:18 VCEFXTW21310070 vcmd: [ENET:enc1:iobay1:3004:Info] Enet Module power on
2014-04-13T16:38:44+04:18 VCEFXTW21310070 vcmd: [ENET:enc1:iobay1:3031:Major] Enet Module IP is 0.0.0.0
2014-04-13T16:38:59+04:18 VCEFXTW21310070 vcmd:last message repeated 2 times
2014-04-13T16:38:59+04:18 VCEFXTW21310070 vcmd: [ENET:enc1:iobay1:3023:Major] Enet Module state NO_COMM : Cannot communicate with component, Previous: Enet Module state UNKNOWN
2014-04-13T16:49:04+04:18 VCEFXTW21310070 vcmd: [ENET:enc1:iobay1:3031:Major] Enet Module IP is 0.0.0.0
------
it seems VC can not get the IP from OA using EBIPA, when I change the bay it get its IP and I can ping it again.
please help!