Connectrix: B-Series: Alias Operation Fails on "AliasName" Due to Internal Error' When Using aliremove

Unable to remove members from alias.

An incorrectly typed Port World Wide Name (PWWN) can result in an error response when using aliremove on multiple members. Further, aliremove commands with correct PWWN get the same response.

An alias can consist of multiple PWWN members. Having an incorrect member in the list when trying to remove multiple members from an alias, causes the error response:

Alias operation failed on "AliasName" due to internal error

After that, attempting to use aliremove on any of the PWWNs used correctly in the first aliremove attempt continues to see the same error message.

Below is an example where the alias FRAPPY is created with four members. Three members are attempted to be removed but the member in bold (1:41:2e:c0:01:c9:98:3c) is an incorrect PWWN. 

After that even a valid PWWN (51:40:2e:c0:01:c9:a3:6a) cannot be removed successfully. This is persistent until you do a cfgsave and cfgenable or you can log out and back in.

alicreate FRAPPY, "51:41:2e:c0:01:c9:a3:6a; 51:41:2e:c0:01:c9:a3:69; 51:41:2e:c0:01:c9:a3:68; 51:41:2e:c0:01:c9:98:3c"
cfgsave
cfgenable

aliremove FRAPPY, "51:41:2e:c0:01:c9:a3:6a; 51:41:2e:c0:01:c9:a3:68;1:41:2e:c0:01:c9:98:3c"
Alias operation failed on "FRAPPY" due to internal error

aliremove FRAPPY, "51:41:2e:c0:01:c9:a3:6a"
Alias operation failed on "FRAPPY" due to internal error

This FOS defect was found during development and fixed. No defect number as it was found and fixed internally.

Workaround:
The issue is cleared by doing cfgsave and cfgenable or by logging out and back into the switch. Keep in mind that all zoning transactions done while logged into the switch are lost when logging out unless the changes are saved first.

Fix:
Upgrade FOS to a 9.x version.