- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- p2000 manage ip is 0.0.0.0, cannot change via part...
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
05-16-2012 08:02 PM - edited 05-16-2012 08:03 PM
05-16-2012 08:02 PM - edited 05-16-2012 08:03 PM
p2000 manage ip is 0.0.0.0, cannot change via partner controller or CLI
A p2000 fc controller manage ip is 0.0.0.0 with unknown reason. Via CLI it shows below:
0.0.0.0
(none) login:
When I try to login with manage/!manage, it shows uncorrect username or password!
Other method I try:
with a good controller at A position,fail one at B positon
via controller A SMU, controller B network cannot be change(fields cannot modify).
via controller A CLI, controller B network cannot be change(report errors).
via controller A SMU, controller B firmware shows no bunlde version
update firmware, controller B cannot update.
I guess somebody power off storage when controller updating led to this issus.
Any Idea?
Thanks!