Do the same steps within the ProSphere UI as above to ensure your Access Credentials username/password are correct to log into the Brocade SMI-S agent and the Discovery job is pointed to the correct IP of the Brocade SMI-S agent host.
If you see errors after the discovery job completes and the setup is correct open a chat or SR with support
ProSphere does support discovering Brocade switches with the standalone 120.11 SMI agent as long as the switch firmware is below 6.4.x so if the firmware is 7.0 of higher see the below details about CMCNE
Brocade stopped developing the Standalone SMI agent (this supports up to 6.4.x firmware) the latest version of this agent comes as an Integrated Agent as part of Connectrix Manager Converged Network (CMCNE) and supports for later firmware’s will be added to this agent.
https://support.emc.com/products/23304_CMCNE please note the full version of CMCNE requires a license. But CMCNE can be installed and setup to run without a license for the Integrated SMI Agent. When asked to Choose the appropriate edition to install Select the SMI Agent only option this way no license is required.
The ProSphere support matrix shows which versions of CMCNE is supported. Currently CMCNE/BNA 11.1.x and CMCNE/BNA 11.2.1
Note before installing CMCNE on the same host as the Standalone SMI agent 120.11 ensure to uninstall this agent before installing the Integrated SMI Agent.
I can see from the screenshots you confirmed when you log into testsmiprovider and run the DV command it successfully list the arrays
Have you two separate issues with discovering the array and one with Brocade switches?
You will need separate access credentials and Discovery jobs for discovering the Brocade switches and the Arrays.
Review the help menu within the UI for more details on the above along with the documents on the ProSphere product page https://support.emc.com/products/5690
If you need more help open a chat session or SR with support for each of your separate issues
Any way lets look at the arrays first:
What step does the discovery fail at for ProSphere?
Do you see the array in question appearing in the Discovery > Object List > Arrays UI? if so select the status under the Discovery Status column
Which process did it fail at Discovery or Topology or Capacity? Selected the failed process under Process log What error message do you see under Detailed Message?
Confirm you can reach the ECOMConfig UI and log in with the access credentials you are using in ProSphere to do the discovery.
Go to the following URI from a host on the same subnet of the ProSphere App:
Login with the SMI Provider access credentials when prompted
I am assuming you are still using the default in ProSphere as below for the SMI-S agent
Username: admin Password: #1Password
If the ECOMConfig page does not load check for any firewalls blocking the port 5988 between the ProSphere App and SMI-S agent host
From the UI Discovery > Access Credentials select the Access Credentials you have created to contact to the EMC SMI-S agent to edit Confirm the SMI-S Attributes are correct.
Port default of 5988,
Interop Namespace set to interop,
Username is the username used for the EMC SMI-S
Password is the password used for the EMC SMI-S agent
From the UI Discovery > Discovery Jobs select the Discovery Job created for the array discovery to edit. Ensure the filter detection method has Arrays selected and the IP address to be scanned is the IP of the EMC SMI-S agent host.
Ensure the correct Access Credentials for the EMC SMI-S is added to Selected Access Credentials
The result no element was detected would point at the ECOM service not running please restart the emcom service on the EMC SMI-S host before re-running the array Discovery job
From the UI Discovery > Discovery Jobs after you run the Array discovery job under the column RUN date select the date. Within the Job Execution Results screen select the job so to see blue in the back round of the line to show its highlighted what reason does it give for failing within the Log for Object Name?
If the EMC SMI-S and Brocade SMI-S are on the same host ensure that they are not both setup to use 5988 as this will cause a conflict. Change one of them to use another port and update the Access Credential within the ProSphere UI to reflex the changes.
ConorLawlor
233 Posts
0
February 27th, 2013 04:00
Hi Miguel,
For the Brocade Switches:
Do the same steps within the ProSphere UI as above to ensure your Access Credentials username/password are correct to log into the Brocade SMI-S agent and the Discovery job is pointed to the correct IP of the Brocade SMI-S agent host.
If you see errors after the discovery job completes and the setup is correct open a chat or SR with support
ProSphere does support discovering Brocade switches with the standalone 120.11 SMI agent as long as the switch firmware is below 6.4.x so if the firmware is 7.0 of higher see the below details about CMCNE
http://www.brocade.com/downloads/documents/support_plans/SMIAGENT/120.11.0/smiagent120.11.0_releasenotes_v1.0.pdf
Brocade stopped developing the Standalone SMI agent (this supports up to 6.4.x firmware) the latest version of this agent comes as an Integrated Agent as part of Connectrix Manager Converged Network (CMCNE) and supports for later firmware’s will be added to this agent.
https://support.emc.com/products/23304_CMCNE please note the full version of CMCNE requires a license. But CMCNE can be installed and setup to run without a license for the Integrated SMI Agent. When asked to Choose the appropriate edition to install Select the SMI Agent only option this way no license is required.
The ProSphere support matrix shows which versions of CMCNE is supported. Currently CMCNE/BNA 11.1.x and CMCNE/BNA 11.2.1
Note before installing CMCNE on the same host as the Standalone SMI agent 120.11 ensure to uninstall this agent before installing the Integrated SMI Agent.
Regards
Conor
ConorLawlor
233 Posts
1
February 27th, 2013 04:00
Hi,
I can see from the screenshots you confirmed when you log into testsmiprovider and run the DV command it successfully list the arrays
Have you two separate issues with discovering the array and one with Brocade switches?
You will need separate access credentials and Discovery jobs for discovering the Brocade switches and the Arrays.
Review the help menu within the UI for more details on the above along with the documents on the ProSphere product page https://support.emc.com/products/5690
If you need more help open a chat session or SR with support for each of your separate issues
Any way lets look at the arrays first:
What step does the discovery fail at for ProSphere?
Do you see the array in question appearing in the Discovery > Object List > Arrays UI? if so select the status under the Discovery Status column
Which process did it fail at Discovery or Topology or Capacity? Selected the failed process under Process log What error message do you see under Detailed Message?
Confirm you can reach the ECOMConfig UI and log in with the access credentials you are using in ProSphere to do the discovery.
Go to the following URI from a host on the same subnet of the ProSphere App:
http://< SMI-S IP>>:5988/ECOMConfig
Login with the SMI Provider access credentials when prompted
I am assuming you are still using the default in ProSphere as below for the SMI-S agent
Username: admin
Password: #1Password
If the ECOMConfig page does not load check for any firewalls blocking the port 5988 between the ProSphere App and SMI-S agent host
From the UI Discovery > Access Credentials select the Access Credentials you have created to contact to the EMC SMI-S agent to edit Confirm the SMI-S Attributes are correct.
Port default of 5988,
Interop Namespace set to interop,
Username is the username used for the EMC SMI-S
Password is the password used for the EMC SMI-S agent
From the UI Discovery > Discovery Jobs select the Discovery Job created for the array discovery to edit.
Ensure the filter detection method has Arrays selected and the IP address to be scanned is the IP of the EMC SMI-S agent host.
Ensure the correct Access Credentials for the EMC SMI-S is added to Selected Access Credentials
The result no element was detected would point at the ECOM service not running please restart the emcom service on the EMC SMI-S host before re-running the array Discovery job
From the UI Discovery > Discovery Jobs after you run the Array discovery job under the column RUN date select the date. Within the Job Execution Results screen select the job so to see blue in the back round of the line to show its highlighted what reason does it give for failing within the Log for Object Name?
If the EMC SMI-S and Brocade SMI-S are on the same host ensure that they are not both setup to use 5988 as this will cause a conflict. Change one of them to use another port and update the Access Credential within the ProSphere UI to reflex the changes.
Regards
Conor
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
February 27th, 2013 09:00
Tks Connor, let me review this solution and back whit my comment asap. Thank a lot