Check here to start a new keyword search. It is assumed that you have entered the correct host name or IP address, user name, and password in Spectrum Control. Verify the stopped status of the megha service: Below are examples of the underlying exceptions that are logged in Spectrum Control, typically in dmSvcTrace. Log on to the Analytics probe server through an SSH client like putty using the following credentials:. Can you telnet to the Network Advisor server and port and show that the port is listening? Click Next , and then click OK.
|Date Added:||23 August 2012|
|File Size:||20.10 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
The data collection of the following switch port metrics are disabled by default. Download a sample file by clicking the Export option.
Connect failed When failing to connect, you might also see the following error in dmSvcTrace. Start the megha service using the command:.
Select the Select switches for data collection using csv file import option. Edit the CSV file details offline based on your requirements. In the CSV file, you can add only those switches that you want to monitor or type No for each switch that you do not want to monitor.
The error messages presented in Spectrum Control depend on the specific action, but in all cases they give an indication that a connection could not be established or that no agent is available. If you’ve checked the items above and still can’t connect, you might be hitting one of a couple known defects with the Network Advisor SMI Agent.
To view the status click the Details option. Below are some examples of those errors.
Adding Brocade FC Switch (BNA) probe
Note After a probe is added, it might take some time before the registered resources appear in the Infrastructure Analytics Advisor server GUI. From the Analytics probe server home page, click Add Probe. Initial setup after adding a probe.
You can also add the switches using the Import CSV option, which allows you to add a large number of switches with a flexibility of adding only those switches that you want to monitor. This is a bnw of items to check to help you do some basic troubleshooting to identify and resolve the most common errors that occur. Brocaed the Choose switches for data collection window, select the switches that you want to monitor.
The user must have Area of Responsibility as All Fabrics and at least one role: BTADSE The data can’t be collected by the probe because the data collector or the storage resource that is being probed isn’t available. You can specify any available port number. Open a web browser, and then enter the following URL in the address bar to log on to Infrastructure Analytics Advisor server:. Can you connect between the Spectrum Control server and Brocade Network Advisor server with other applications?
Refer to Viewing the host CSV file import status for more information. Collecting optional metrics for Brocade Network Advisor probe. Note When a new switch is added to Brocade Network Advisor, the probe begins collecting data automatically. Fixed in Network Advisor.
Watson Product Search Search.
IBM Resolving communication issues with Brocade Network Advisor – United States
Start collecting information about your system resources by adding probes to the Analytics probe server. Verify the stopped status of the megha service: Log on to the Analytics probe server through an SSH client like putty using the following credentials:. Contact and feedback Need support?
Brocad Switch or Add Fabric Test Connection for a previously added switch or fabric Run Fabric Probe Performance monitoring data collection The error messages presented in Spectrum Control depend on the specific action, but in all cases they give an indication that a connection could not be established or that no agent is available. Make sure these are correctly specified between the applications.
Brocade Network Advisor Note: Ensure that the CSV file is in a specific format.