Action
1. Authenticate using the curl command:
curl --noproxy [IP_ADDRESS] -X POST --fail -ksSfL --url "https://[IP_ADDRESS]:8443/sdn/v2.0/auth" --header
"Content-Type: application/json" --data-binary
'{"login":{"user":"sdn","password":"skyline","domain":"sdn"}}'
For example:
curl --noproxy 1192.0.123.5 -X POST --fail -ksSfL --url "https://192.0.123.5:8443/sdn/v2.0/auth" --header
"Content-Type: application/json" --data-binary
'{"login":{"user":"sdn","password":"skyline","domain":"sdn"}}'
The curl command in this example generated the following response:
{"record":{"token":"2ee24d3a87c345e98deaeaed4bf770ef","expiration":1416343000000,
"expirationDate":"2014-11-18 12-36-40 -0800","userId":"06338e545b9a4f04b145a5ad7c541254",
"userName":"sdn","domainId":"1685f85a515e4983b4ea64fff9917ecc","domainName":"sdn"}}
2. Check systems status using the curl command:
curl --noproxy [IP_ADDRESS] --header "X-Auth-Token:[AUTHENTICATION_TOKEN]" --fail -ksS -L -f --request
GET --url "https://[IP_ADDRESS]:8443/sdn/v2.0/systems"
For example:
curl --noproxy 192.0.123.5 --header "X-Auth-Token:2ee24d3a87c345e98deaeaed4bf770ef" --fail -ksS -L -f
--request GET --url "https://192.0.123.5:8443/sdn/v2.0/systems"
The curl command in this example generated the following response:
{"systems":[{"uid":"0046a56e-a65e-4960-9d9e-f1820a285e53","version":"2.5.2.0496",
"ip":"192.0.123.5","role":"member","core_data_version":16,
"core_data_version_timestamp":"2014-11-18T19:30:37.587Z","status":"suspended","self":true},
{"uid":"1ac1c1e7-1a6e-4401-ad3e-206028d57db8","version":"2.5.2.0496","ip":"192.0.127.34",
"role":"member","core_data_version":16,"core_data_version_timestamp":"2014-11-18T19:30:38.480Z",
"status":"unreachable"},{"uid":"2533a1df-cced-44f9-b9be-f6e3851da261","version":"2.5.2.0496",
"ip":"192.0.125.176","role":"member","core_data_version":16,
"core_data_version_timestamp":"2014-11-18T19:30:38.933Z","status":"unreachable"}]}
3. Check alerts.
• To get all alerts, use the following curl command:
curl --noproxy [IP_ADDRESS] --header "X-Auth-Token:[AUTHENTICATION_TOKEN]" --fail -ksS -L -f --request
GET --url "https://[IP_ADDRESS]:8443/sdn/v2.0/alerts"
• To get alerts from a time interval, use the following curl command:
curl --noproxy [IP_ADDRESS] --header "X-Auth-Token:[AUTHENTICATION_TOKEN]" --fail -ksS -L -f --request
GET --url
"https://[IP_ADDRESS]:8443/sdn/v2.0/alerts?start=XXXX-XX-XXTXX:XX:XX.XXXZ&end=XXXX-XX-XXTXX:XX:XX.XXXZ"
For example:
curl --noproxy 192.0.123.5 --header "X-Auth-Token:2ee24d3a87c345e98deaeaed4bf770ef" --fail -ksS -L
-f --request GET --url
"https://192.0.123.5:8443/sdn/v2.0/alerts?start=2014-11-18T19:30:15.000Z&end=2014-11-18T19:30:17.000Z"
The curl command in this example generated the following response:
{"alerts":[{"uid":"9ddf298e-a747-409c-b021-2610d6bf3e85",
"system_uid":"0046a56e-a65e-4960-9d9e-f1820a285e53","topic":"HealthMonitor",
"org":"HealthMonitor","ts":"2014-11-18T19:30:16.641Z","sev":"CRITICAL","state":true,
"desc":"Health Monitor com.hp.sdn.adm.system.impl.QuorumRegistar changed state to CRITICAL > reason:
No quorum"},
{"uid":"0e8deb7d-edcf-4000-a01d-db9bbabcc337","system_uid":"1ac1c1e7-1a6e-4401-ad3e-206028d57db8",
"topic":"HealthMonitor","org":"HealthMonitor","ts":"2014-11-18T19:30:16.905Z",
"sev":"CRITICAL","state":true,"desc":"Health Monitor
com.hp.sdn.adm.system.impl.QuorumRegistar changed state to CRITICAL > reason: No quorum"}]}
Unable to create team
Symptom
A group of SDN controllers fail to create a team.
Cause
The DNS server configured on each controller is unreachable.
164 Troubleshooting
To Next Page
Loading...
