This post is more than 5 years old
50 Posts
0
2273
April 22nd, 2009 09:00
ECC6.1 Brocade discovery and SMI-S agent issue
Hi,
Env:
DS-5000B/Brocade 5000
Fabric OS version v6.1.0h kernel 2.6.14.2
SMI agent 120.8.0. add the DS5000B as the proxy switch, but log in failed with error" Operation NOT support".
Do anyone have experience of SMI agent configure and discovery brocade switch in ECC6.1 for sharing? Thanks!
Ray,Chenxt
Env:
DS-5000B/Brocade 5000
Fabric OS version v6.1.0h kernel 2.6.14.2
SMI agent 120.8.0. add the DS5000B as the proxy switch, but log in failed with error" Operation NOT support".
Do anyone have experience of SMI agent configure and discovery brocade switch in ECC6.1 for sharing? Thanks!
Ray,Chenxt
No Events found!
ConorLawlor
2 Intern
•
233 Posts
0
May 24th, 2010 07:00
Hi,
If you are already at the latest Brocade SMI Agent for EOS version 2.7.
Try the following steps to resolve. if the issue remains open a SR with support with the below logs.
A) Confirm if the host which runs the CM has dual IP configured, The CM server may be selecting the server connection IP dynamically which SMI (EOS) Agent is not able to pick. Set the CM host IP address directly in the IP configuration tab instead of the default one (Automatic).
See page 18 & 20 of the EOS Install guide for steps. http://www.brocade.com/downloads/documents/support_plans/SMIAGENT/SMI-S_v2.7/smis2.7_InstallGuide.pdf
B) To get back to the options screen of the Brocade SMI Agent
Do the following
1. Stop the SMI Agent 2.7 server.
2. Delete the mcdataProductInterface properties file available @ < Install Folder >\SMI_Agent_for_EOS_products\agent\server\jserver\bin.
3. Start the SMI Agent 2.7 server by Start_server.bat (Windows)
4. Choose the appropriate connection mode again.
Follow page 12 to 18 of the EOS Install for steps. http://www.brocade.com/downloads/documents/support_plans/SMIAGENT/SMI-S_v2.7/smis2.7_InstallGuide.pdf
C) Confirm there is successful communications between the SMI Agent Provider Hosts and Connectrix Manager, To test this and test network communications, use 'ping -t -l ' to/from Each component: As Example :
Run a ping -t -l 4096 < > command from the SMI Agent Provider Host to Connectrix Manager
Check for dropped packets which would indicate a network issue.
Leave the command running for 1 minute, press Control C to end.
Check the Ping statistics for lost packets.
D) Confirm correct ports are opened If a firewall exists:
Proxy mode: SMI Agent - EFCM communication
If a firewall exists between the EFCM Server and SMI Agent in proxy mode operation, the following port numbers must be open:
• 80 - Web Server port number on the Server port
• 51511 - API-Server to Client communication port
• 51510 - API-Server to Client export port
• 55555 - API-Client to Server export port
• 51513 - ECCAPI port
• 8081 - Web proxy port
NOTE If EFCM Server is configured to run on different non-default ports, respective ports must be opened.
If a firewall exists between the SMI Agent and FCC agent, the following port numbers must be open:
• 5989 - https communication
• 5988 - http communication
E) If the issue remains setup debug mode the and try the connection again.
Configuring the debug log for M-EOS Provider
By default, the Debug Log tab is hidden in the application. You must press Ctrl+Shift+F9 to view the debug log tab on the SMI Agent for EOS Products Server Configuration window. The Log Debugging Data check box is disabled by default. Enable the Log Debugging Data check box to enable the Debug Levels table. Click the Debug Log tab to configure the debug log. After you enable the Log Debugging Data check box, it will reflect in the Server Configuration tool until you clear the checkbox. Assign a logging level of Debug to each category. For log location > Select file > Name the file debug.log
See page 25 & 26 of the EOS User guide of more information on turning on debug. http://www.brocade.com/services-support/drivers-downloads/smi-agent/application_matrix.page
Collect and attach the following logs to the SR on powerlink.
1. The newly created M-EOS Provider debug log
2. From the M-EOS host the logs in the following location:
agent\server\logs\audit
agent\server\jserver\mof
agent\server\logs
agent\server\jserver\logr
Regards
Conor Lawlor
seamuscoffey
472 Posts
0
April 22nd, 2009 11:00
I've worked quite a bit on supporting the SMI Agents in CC 6.1. However, I have not seen the 'operation not supported' error (the usual issue we encounter is the 'not connected' error). Your switch and firmware levels are good as per the latest Brocade SMI Agent 120.8.0 Release Notes.
The SMI Provider logs need to be looked at in order to determine the root cause. You'll probably need to open a SR re same.
Regards,
Séamus Coffey
EMC Global Services
Chenxt
50 Posts
0
April 23rd, 2009 11:00
seamuscoffey
472 Posts
0
April 23rd, 2009 12:00
Regards,
Séamus