- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- HP 6125G blade switch redundancy issue on c3000
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
12-04-2015 04:04 AM
12-04-2015 04:04 AM
HP 6125G blade switch redundancy issue on c3000
Hi everybody,
i'm facing some switch redundancy issue on c3000 chassis with 2 bl460 gen9 servers.
chassis components are:
- 2 hp 6125G blade switch
- 2 hp b-serie 8/12 san switches
- 2 bl 460c gen9 with mezz slot 1 and 2 populated.
i know that by default, in c3000 chassis, all FlexLOM are directly mapped to interconnect bay 1 (for full and half servers), and to allow redundancy, mezz cards should be populated to map in interconnect bay2.
in my case, with this type of switch, servers have mezz cards in both slots for interconnect bays 2.3.4.
redundancy is good for the san with FC switches, but for the ethernet switches 6125G in bay 1 and 2 there is no redundancy, 1 cable is connected to each switch in port 1 and go to the same external cisco switch, for test i ping one of the servers which sucessfully reply, but if i unplug the cable out of the first switch i loose the pings and in the mine time connectivity to both servers, which confirm that redundancy is not automatic in this case. (here is attached some screenshots of the switches).
i think theses switches are managable, do i need to directly connect in each switch and activate something for redundancy??
thanks!!!