How to Gather MX7000 Chassis Logs

This video will demonstrate the how to gather chassis logs from your MX7000. Methods for versions both pre and post v2.0 are shown.

Hello everyone. My name is Cynthia, and I am a Domain Engineer specializing in modular systems and the MX7000 chassis.

In this video we are going to cover how to gather MX7000 chassis logs. This will require logging in with credentials that have chassis administrator privileges. In this video we will cover two methods on how to gather the logs.

If you are on Open Manage Enterprise Modular version 2.0 and above we can accomplish this from the ‘All devices’ page. If you are below this version then we will need to accomplish this via a different method, which we will also cover in this video. First we will look at the method of pulling chassis logs if you are on Open Manage Enterprise Modular version 2.0 or above.

We'll navigate to ‘Devices’, ‘All devices’. As you can see on this page there are multiple device types that you can review, as well as what chassis they are located in. You can pull logs from compute sleds as well as the chassis on this page. You cannot pull logs from switches or storage devices from this page.

For this demonstration I will select two chassis as well as one compute sled, and then select ‘Extract logs’. From here you can see the last extracted log and you can download it. You can also edit your selection to add more devices. You can see which devices are selected, as well as choose where you want your download to export to.

In this case we're going to select ‘Locally to device’ which will download to your local browser. Once you select the download option, here we have the option to ‘Mask sensitive logs’ which will mask any IP addresses or MAC addresses that are in the chassis logs.

Sensitive information that is captured as a part of the audit logs will not be masked however. We also have the option of adding additional logs to the compute sled logs we are collecting, for example if you are troubleshooting issues with drives or with your RAID controller then you might select the ‘Storage log’ option.

The ‘Debug logs’ option is typically selected if we are trying to troubleshoot a more complex issue as it gives us a lot of granular information about what's going on in the compute sled that we're gathering logs on.

Typically when creating a SupportAssist collection from the iDRAC or via this method from the chassis GUI we would prefer to have the debug logs option checked because it gives us more granular information. Similar to the chassis logs, the sled logs also have the option to filter for sensitive data.

We can monitor the job by selecting up here, and clicking on the job. You can also get to the job queue via monitor jobs up at the top, and we can see the jobs running against all of our target devices. For the purposes of this video I will speed up the recording, and as you can see at this point the chassis is packaging up the logs into a zip file to prepare for download.

The logs may be downloaded from this ‘Download extract log’ option or if you navigate back to ‘All devices’ and ‘Extract log’ you may download the logs from this screen as well. So if you navigate to chassis and drill into the lead chassis from ‘Troubleshoot’, ’Extract log’ you'll notice you can extract the log from here as well.

This was the case before OME-M 2.0 that you would need to extract the log from here. For monitor jobs we can see the job running just as we did before, and prior to 2.0 you did not have ‘Download extract log’ in the job queue, you would have to go back to ‘Troubleshoot’, ‘Extract log’ and then download the log from here.

If you want to gather logs from a different chassis, a member chassis, and from the lead chassis, you drilled into said chassis and tried to extract log the ‘Locally to device’ option is not available, unless you go into the GUI of that chassis directly via its IP or hostname. However you can extract the log to an NFS or CIFS share via this method. And that concludes this video.

Thank you for watching