Unsolved

This post is more than 5 years old

1 Rookie

 • 

6 Posts

2686

April 29th, 2019 04:00

iDRAC Group Manager issues

We have several PowerEdge R7425 servers with iDRAC 3.21.24.22 and I am trying to set up a iDRAC Group for an easier overview of the status of the systems without having to log in to each one individually.

The issue is although I can set up the group using one of them I cannot add any further members to the group, I get either one of the following errors (depending on if I try adding a node from the group manager or if I log in to a node and add it to the group that way)

GMGR0016 SERVICETAG is unable to join the iDRAC local group GROUPNAME either because the Group passcode is incorrect, group already has the max allowed iDRACs, iDRAC already part of another group, group name does not exist, or issues in network connection.

GMGR0047 The group job is either stopped by a user action or failed at the member level.Do the following and rerun the job: 1) Check the group job rollup status to see if the job is stopped by the user. If yes, rerun the job if required. 2) If not, review the job execution details in the Lifecycle Log details of the member iDRAC. By using the iDRAC graphical user interface (GUI), on the home page, click Maintenance > Lifecycle Log. By using command line interface (CLI), enter the RACADM command "racadm lclog view".

I have triple checked the passcode is correct, even changed to 12345678 just to rule that out.  Is it a licensing issue?

4 Operator

 • 

2.9K Posts

April 29th, 2019 07:00

I would flash the iDRAC to 3.30.30.30. I checked the user guide and Group Manager will support up to 100 servers. It is a feature of the iDRAC Enterprise license, too. You'll want to confirm that your systems are showing up with iDRAC Enterprises for group membership. I'll link to the user guide also. Page 185 goes into detail on the group manager.

https://topics-cdn.dell.com/pdf/idrac9-lifecycle-controller-v3303030_users-guide_en-us.pdf

1 Rookie

 • 

6 Posts

April 30th, 2019 04:00

Thanks, updating the firmware to 3.30.30.30 on them all seems to have solved it :)

Top