Table of Contents
Advertisement
Pushing flows, groups, or meters via a northbound REST API to any controller in the team is
supported even if that controller is not the master of the given device. In that case, the controller
will delegate the request to the controller who is the master of the switch and the master controller
will handle the request. If the switch returns an error from the given request (for example, the
meters table is full), the switch responds to the owning controller with a proper Openflow error.
But when that error is sent back to the requesting controller, it is not parsed properly and results
in an error.
Action
If you are pushing a meter or group mod to a connected switch from a controller, that controller
must be the master in order to handle the errors correctly.
Getting UnsafeConfigurationException, HTTP code: 403
Symptom
Getting UnsafeConfigurationException, HTTP code: 403. Applies to application, license,
and configuration changes.
Cause
One member of a team is not active. All team members in a teamed environment must be active
before you can make configuration, licensing, or application changes, or changes to regions.
Otherwise, the configuration is not guaranteed to be synchronized with all the members of the
team.
Action
Indicates that the operation cannot be completed.
Getting ApplicationDisableException, HTTP code: 500
Symptom
Getting ApplicationDisableException, HTTP code: 500.
Cause
Occurs when an application status is STAGED or UPGRADE_STAGED, or that something has gone
wrong as specified in error message.
Action
Indicates that an application cannot be disabled.
Getting ApplicationEnableException, HTTP code: 500
Symptom
Getting ApplicationEnableException, HTTP code: 500.
Cause
Occurs when an application status is not DISABLED, or that something has gone wrong as
specified in the error message.
Action
Indicates that an application cannot be enabled.
160 Troubleshooting
Hide quick links:
Advertisement
Table of Contents
Troubleshooting
