- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- Aruba & ProVision-based
- >
- Aruba VSF and Next Generation UI: a cosmetic bug i...
-
- Forums
-
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
- HPE Blog, Austria, Germany & Switzerland
- Blog HPE, France
- HPE Blog, Italy
- HPE Blog, Japan
- HPE Blog, Middle East
- HPE Blog, Russia
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
-
Blogs
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Blog, Latin America
- HPE Blog, Middle East
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
-
Information
- Community
- Welcome
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Tips and Tricks
- Resources
- Announcements
- Email us
- Feedback
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Aruba Airheads Community
- Enterprise.nxt
- HPE Dev Community
- Cloud28+ Community
- Marketplace
-
Forums
-
Blogs
-
Information
-
English
- 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
- Email to a Friend
- 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 Up
No 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

Hewlett Packard Enterprise International
- Communities
- HPE Blogs and Forum
© Copyright 2021 Hewlett Packard Enterprise Development LP