- Community Home
- >
- Services
- >
- Insight Remote Support
- >
- How to troubleshoot: The RIBCL subscription to "DL...
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
Discussions
Forums
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
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-04-2019 02:09 AM
тАО07-04-2019 02:09 AM
How to troubleshoot: The RIBCL subscription to "DL580-1" has failed
Hi HPE employees,
I use IRS->Discovery->
Select Type: Server
Select Sub-Type: ProLiant Gen 10
Select and Configure Protocol: iLO Remote Insight Board Command Language Protocol(RIBCL)
and input the correct Credential to "start discovery" but I always got the errors like below:
What happened? I am sure I can use this iLO IP Address and Credential to connect to the ilo web site.
----
Protocol: iLO Remote Insight Board Command Language Protocol (RIBCL)
Service: SUBSCRIPTION
Type: SUBSCRIPTION
Status: FAILURE
Description: The RIBCL subscription to DL580-1 has failed.
Detailed: 1. Check that the connectivity check has passed. Without connectivity, subscriptions will not succeed. 2. Check that the credentials are still valid.
Created: 7/4/2019 3:17:43 PM
Last Updated: 7/4/2019 3:17:43 PM
----
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-08-2019 06:26 PM - last edited on тАО07-08-2019 10:07 PM by Parvez_Admin
тАО07-08-2019 06:26 PM - last edited on тАО07-08-2019 10:07 PM by Parvez_Admin
Re: How to troubleshoot: The RIBCL subscription to "DL580-1" has failed
Hi Dennis,
The DL 580 Gen10 device could also be register through iLO4 GUI:
1) Login to iLO4 GUI > Remote Support> Under "Registration Tab" provide IRS server IP, and port 7906, then click on register.
Please let me know if you get any error message.
Regards,
Vijay Pandey
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-09-2019 05:24 AM
тАО07-09-2019 05:24 AM
Re: How to troubleshoot: The RIBCL subscription to "DL580-1" has failed
Vijay points out that you can register via the iLO User Interface, which is true - however, for the entire system to function properly, you must give Insight RS the RIBCL credentials for the iLO to allow proper operations.
The error message you posted is given when one of 2 things happen:
* Credentials no longer authenticate (password has changed, or was not entered properly into Insight RS)
* Network is not reachable (device is down, or subnet is configured in a way to make it not reachable)
Please make sure you have the correct credentials in the Insight RS tool, and attempt to re-discover the device.
Please let us know if the problem persists - but if it does, a call to HPE support may be in order.
I work for HPE
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
