- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE 3PAR StoreServ Storage
- >
- SSMC 2.3 - Issues
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
02-16-2016 11:34 AM
02-16-2016 11:34 AM
SSMC 2.3 - Issues
Sorry if thius is in the wrong place, but I would like to share some recent troubles I have had with this versin of SSMC.
I performed an upgrade from SSMC 2.2 to 2.3 on two seperate systems and both of them crash when you try to access the Virtual Volumes seciotn. Only way around it at present is to create a VVSet, access that in SSMC then click on the volumes.. Also, these are to two different arrays so not linked in any way at a hardware or infrastructuree level (two seperate companies)
The second really natty issue is when you set the System Reporter report retention days. It has to be > 0, but it cant be 10, 20, 30, 40, 50...100, 101 - see a pattern there! Not great if you want a 30 day rolling retention.
Not yet had a chance to rasie support calls for these yet. One I can live with, the second is unexcusable.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-12-2016 04:17 PM
04-12-2016 04:17 PM
Re: SSMC 2.3 - Issues
The first issue is addressed in SSMC 2.3.1.
The second issue will be addressed in the next SSMC release. A workaround for the short term is to set the retention value at either 29 or 31 and adjust it when the next release is available.