Updating SNA Resources Dynamically
It is not necessary to delete an SNA resource before redefining it. A resource must be inactive, however, when you redefine it.
If a redefinition is rejected for a reason other than that the
resource is active, a STATE_CHECK return code is returned as well
as a specific secondary return code, as listed in the NOF specification.
Most rejections are due to inconsistencies in the configuration, such
as one of the following:
- Attempting to define an LS with the adjacent CP name set to the local CP name.
- Attempting to define two link stations on a non-switched port with the same destination address.
Such rejections occur regardless of whether you are defining a resource for the first time or redefining it.
Keep in mind the following when redefining resources:
- You cannot change the ls_role of a port that has link stations defined on it. The link stations must be deleted before the port role can be changed (because an LS may default to the port ls_role).
- You cannot change the type of a named DLC. The DLC definition must be deleted before the same name can be reused for a DLC of a different type.