- Community Home
- >
- Storage
- >
- Data Protection and Retention
- >
- StoreOnce Backup Storage
- >
- Re: Storeonce encountered error D2DManager proces...
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
07-23-2018 12:57 AM
07-23-2018 12:57 AM
Storeonce encountered error D2DManager process state has changed: OK to Critical (NASMan)
Hello everyone,
We've encountered this issue couple of months, does anybodyhelp me to figure this out.
Thank you
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-24-2018 11:39 PM
07-24-2018 11:39 PM
Re: Storeonce encountered error D2DManager process state has changed: OK to Critical (NASMan)
This alert triggers due to serviceset and also if software on the Storeonce is outdated.
Please log a case with hpe technical team if storeonce is running on outdated software.
So plan for downtime for storeonce before restarting the serviceset ssid1.
run the below command
Access the CLI from an SSH terminal using an SSH client application (Putty session)
Login with :Admin and password :admin
#Hardware disable failover
# serviceset show status (Run to verify failover has stopped)
#Serviceset stop
#serviceset start
#serviceset show status (check status for the serviceset)
If issue still persists, Please log a case with our technical team for elevation and logs analysis to check the cause.
Regards,
Ashoka S