Troubleshooting switches and chassis

Find solutions to common problems that you might encounter when you add and monitor switches and chassis.

Problems and questions	Answers
I am not able to add a chassis to IBM Storage Insights	Before you add the chassis, verify the following check points: Ensure that the chassis meets the hardware and software requirements. Check that the user account has the essential properties. If you are adding Cisco chassis, check that NX-API is enabled. If you are adding Brocade switches, check that the user has chassis role and Logical Fabrics list 1-128. Ensure that the protocol and port number are matching with your requirement. Brocade chassis can enable either HTTPS or HTTP, but not both. Enabling HTTPS disables HTTP automatically. Cisco configures HTTPS when the NX-API feature is enabled. You can also enable HTTP. If you attempt to add a chassis that is shown in the IBM Storage Insights with Not Monitored condition, the add chassis action fails. Instead use the Configure Data Collection action on the chassis page to configure data collection for Not Monitored chassis. For more instructions, see Configuring Brocade switches for monitoring for adding Brocade switches and Planning for Cisco switches and fabrics for adding Cisco switches.
I am able to see my chassis in the IBM Storage Insights, but in Not Monitored condition. How can I get my chassis in monitored condition?	If your chassis is showing in Not Monitored condition, you cannot add the same chassis to IBM Storage Insights again. You cannot start the data collection on that chassis. Instead use the Configure Data Collection action on the chassis page to configure data collection for Not Monitored chassis. If the issue is not resolved, verify the following check points: Ensure that the chassis meets the hardware and software requirements. Check that the user account has the essential properties. If you are adding Cisco chassis, check that NX-API is enabled. If you are adding Brocade switches, check that the user has chassis role and Logical Fabrics list 1-128. Ensure that the protocol and port number are matching with your requirement. Brocade chassis can enable either HTTPS or HTTP, but not both. Enabling HTTPS disables HTTP automatically. Cisco configures HTTPS when the NX-API feature is enabled. You can also enable HTTP. If a chassis is discovered through an added chassis, but has different user credentials, port or protocol settings than the connected chassis, use Configure Data Collection action on the chassis page and enter the correct port, protocol, and user credentials. Make sure the changes to the NX-API configuration of Cisco switch is saved by using copy command before the switch is rebooted. If the Cisco chassis is configured to run NX-API with HTTPS on port 443, it creates a conflict with the web server that runs on the same port. So, do not use the port 443. Use another unused port number.

Problems and questions

Answers

I am not able to add a chassis to IBM Storage Insights

Before you add the chassis, verify the following check points:

Ensure that the chassis meets the hardware and software requirements.
Check that the user account has the essential properties.
If you are adding Cisco chassis, check that NX-API is enabled.
If you are adding Brocade switches, check that the user has chassis role and Logical Fabrics list 1-128.
Ensure that the protocol and port number are matching with your requirement.
- Brocade chassis can enable either HTTPS or HTTP, but not both. Enabling HTTPS disables HTTP automatically.
- Cisco configures HTTPS when the NX-API feature is enabled. You can also enable HTTP.
If you attempt to add a chassis that is shown in the IBM Storage Insights with Not Monitored condition, the add chassis action fails. Instead use the Configure Data Collection action on the chassis page to configure data collection for Not Monitored chassis.

For more instructions, see Configuring Brocade switches for monitoring for adding Brocade switches and Planning for Cisco switches and fabrics for adding Cisco switches.

I am able to see my chassis in the IBM Storage Insights, but in Not Monitored condition. How can I get my chassis in monitored condition?

If your chassis is showing in Not Monitored condition, you cannot add the same chassis to IBM Storage Insights again. You cannot start the data collection on that chassis. Instead use the Configure Data Collection action on the chassis page to configure data collection for Not Monitored chassis.

If the issue is not resolved, verify the following check points:

Ensure that the chassis meets the hardware and software requirements.
Check that the user account has the essential properties.
If you are adding Cisco chassis, check that NX-API is enabled.
If you are adding Brocade switches, check that the user has chassis role and Logical Fabrics list 1-128.
Ensure that the protocol and port number are matching with your requirement.
- Brocade chassis can enable either HTTPS or HTTP, but not both. Enabling HTTPS disables HTTP automatically.
- Cisco configures HTTPS when the NX-API feature is enabled. You can also enable HTTP.
If a chassis is discovered through an added chassis, but has different user credentials, port or protocol settings than the connected chassis, use Configure Data Collection action on the chassis page and enter the correct port, protocol, and user credentials.
Make sure the changes to the NX-API configuration of Cisco switch is saved by using copy command before the switch is rebooted.
If the Cisco chassis is configured to run NX-API with HTTPS on port 443, it creates a conflict with the web server that runs on the same port. So, do not use the port 443. Use another unused port number.