- Community Home
- >
- Storage
- >
- HPE Nimble Storage
- >
- Array Setup and Networking
- >
- Cisco UCS connection to Core or FEX
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
07-26-2016 05:41 AM
07-26-2016 05:41 AM
Hello,
We are having an issue with two CS500 arrays. Both are currently connected to a Cisco UCS via the Core. Controller A is fine and up, however Controller B is not able to see the matching port on Controller A. This means that health checks fail, and no failover is possible. Investigations turned up that the ARP/MAC is failing to show up on the Core MAC table. When we hook to the FEX, same result (as expected). Our connections have been validated where A/1 is plugged into the same network as B1 and on it's own VLAN, and the same for A2/B2. Trunking is not an issue. We duplicated this issue with another CS500 we have that is being installed. Nimble support verified that ARP requests are failing between the controllers. Does anyone have any experience with Nexus and Nimble that could shed some light? Also, we have seen that the controllers can plug into the Fabric Interconnects, however our current routing prevents this.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-27-2016 01:36 PM
07-27-2016 01:36 PM
SolutionMike,
It looks like Nimble Support is working with you and one of your colleagues in regards to this issue. From what we saw there was a steady stream of network CRC errors being received on the standby controller ports. The standby controller was rebooted and the health check errors are no longer present. I believe Cisco is still looking into possible bugs. I would suggest letting Nimble Support know if the problem manifests again.