- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- HPE Aruba Networking & ProVision-based
- >
- Aruba VSF and Next Generation UI: a cosmetic bug i...
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
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
06-25-2018 07:00 AM - edited 06-26-2018 11:03 PM
06-25-2018 07:00 AM - edited 06-26-2018 11:03 PM
Aruba VSF and Next Generation UI: a cosmetic bug involving MMs.
Scenario: Aruba VSF deployed with two Aruba 5406R zl2 (both with identical modules composition) on latest available software KB.16.05.0007 (May 2018).
On the screenshot below note the how the Management Modules are represented through green LED (MM2 is marked Active even if it is not inserted at all, MM1 is inserted but UI reports its Slots as empty):
Note instead what correctly CLI reports about MM (MM1, on both VSF members):
HPE5406Rzl2_VSF_Backend# show modules
Status and Counters - Module Information
Chassis: 5406Rzl2 J9850A Serial Number: xxxxxxxxxx
Allow V2 Modules: No
Core Mod
Slot Module Description Serial Number Status Dump Ver
----- -------------------------------------- -------------- -------- ----- ---
1/MM1 HP J9827A Management Module 5400Rzl2 xxxxxxxxxx Active YES
1/A HP J9987A 24p 10/100/1000BASE-T v3 ... xxxxxxxxxx Up
1/B HP J9987A 24p 10/100/1000BASE-T v3 ... xxxxxxxxxx Up
1/C HP J9993A 8p 1G/10GbE SFP+ v3 zl2 Mod xxxxxxxxxx Up
2/MM1 HP J9827A Management Module 5400Rzl2 xxxxxxxxxx Active YES
2/A HP J9987A 24p 10/100/1000BASE-T v3 ... xxxxxxxxxx Up
2/B HP J9987A 24p 10/100/1000BASE-T v3 ... xxxxxxxxxx Up
2/C HP J9993A 8p 1G/10GbE SFP+ v3 zl2 Mod xxxxxxxxxx UpNo MM2 at all. It's clear.
New Generation UI is providing wrong status with regards to Management Modules (Active/Empty) status on both VSF Members.
I'm not an HPE Employee