- Community Home
- >
- Networking
- >
- Software Defined Networking
- >
- teaming failure
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-02-2015 12:32 AM
01-02-2015 12:32 AM
teaming failure
Hi
I am unable to form a team with 3 controllers:
this is the setup
3 x hosts runining ubuntu 12.04.3LTS server ( kernal 3.8.0-29-generic) in virtualbox:
192.168.58.5
192.168.58.6
192.168.58.7
1 x admin machine
192.168.58.8
ping to all hosts successful
HP SDN controller version 2.0.0.4253
installed successfully on all 3 hosts
using the browser from an admin machine, I am able to log onto all controllers
I then use curl to setup the team
curl -sk --header X-Auth-Token:$token --request POST --url
https://192.168.58.7:8443/sdn/v2.0/team --data- binary
'{"team":{"name":"Test_Team","ip":"192.168.58.2","systems":
[{"name":"SDN","ip":"192.168.58.7","priority":10},
{"name":"BCKUP1","ip":"192.168.58.5","priority":20},
{"name":"BCKUP2","ip":"192.168.58.6","priority":30}]}}'
I then ge the following reply: unable to form a quorum
checking the support logs from 192.168.58.7
I see the following:
getting build version from 192.168.58.5
getting build version from 192.168.58.6
retrying connection due to persistanceException
ipAddress:192.168.58.5,BuildVersion 2.0.0.4253
retrying connection due to persistanceException
ipAddress:192.168.58.6,BuildVersion 2.0.0.4253
buildversion of this sytem:2.0.0.4253
validateBuildVersion::resultData: TeamActionstatus
[IP:192.168.58.5,Resoponse:2.0.0.4253,errorMsg:Success]
validateBuildVersion::resultData: TeamActionstatus
[IP:192.168.58.6,Resoponse:2.0.0.4253,errorMsg:Success]
All systems have the same build version 2.0.0.4253
posting team configuration to: 192.168.58.5
posting team configuration to: 192.168.58.6
exeception: Team config propagation faile to 192.168.58.5,java.lang.RuntimeException:java.net.SocketTimeoutexception:Read
timed out
exeception: Team config propagation faile to
192.168.58.6,java.lang.RuntimeException:java.net.SocketTimeoutexception:Read
timed out
RSTAPI propagation failed to some/all systems
unable to form a quorum
if i run curl again i then get the following from the support logs from 192.168.58.7
duplicateDataException :Team config propagation failed to
192.168.58.5,com.hp.api,DuplicateDataException: Teaming already configured on
this system
duplicateDataException :Team config propagation failed to
192.168.58.5,com.hp.api,DuplicateDataException: Teaming already configured on
this system
unable to form a quorum
however when I try verify this I get "team not configured on this system"
any help would be appreciated
thank you
Barry
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-06-2015 08:15 AM
01-06-2015 08:15 AM
Re: teaming failure
Hello,
Unless there is a specific reason for using version 2.0.0 we strongly suggest you to use version 2.4.5 of the VAN SDN Controller.
I would start from scratch (as I think you're using VMs) following the Admin Guide of the same version.
I did not notice any error in the procedure you followed but I think using latest version is the best way to test and configure TEAMING.
If facing same or similar issue please post the logs and also check java version running on your servers.
Regards,
Antonio
SDN Team