This object is used in conjunction with the sysConfChange object, to be read after setting a value for sysConfChange to obtain status of that operation. When this object returns notReady(99) snmp client must poll again, until it returns a valid response different from notReady(99). success(1): Last SET request of SysConfChange object was successful. Mgt station should continue process. noEditingRightsVlan(2): The VLAN configuration is busy, probable causes: VLAN is being edited somewhere else (editToken taken) VLAN is distributing configuration among the switches Mgt station should check the editToken state and advice the user to wait or force a release of the token, if taken. If not taken advice user to wait until configuration is no longer busy and try again. noEditingRightsLocalParm(3): A switch is having the local parameters modified. Mgt station should advice user to wait and try again. flashOperationFailed(4): A switch failed loading the configuration from Flash. Mgt station should advice user to check status of the switches and possibly try again later. flashOperationNothingToLoad(5): The contacted switch didn't have a configuration saved in Flash + Mgt station should advice the user that this switch never had a configuration saved, and the load from Flash has been aborted. This could occur if the contacted switch is new in the stack, and thus haven't had anything saved yet, or if the user simply never saved anything in Flash. Mgt station should advice user to save configuration in flash for entire stack always. tftpOperationFailed(6): The TFTP of files to the switches failed Mgt station should advice user to check status of the switches and possibly try again later. tftpOperationNoLock(7): The stack TFTP lock has not been set by Mgt station. Mgt station should advice user that someone may have tampered with the stack (reset, re-config) while the process was ongoing. (This could also be due to an error by the Mgt platform or switch) tftpOperationStackMemberMissingParmFile(8): One or more of the switches in the stack (other than the contacted switch) didn't receive a parameter block file yet. Mgt station should advice user to check status of the stack, if new switches were added since the configuration was backed-up, or during the process, this could be the problem. tftpOperationMissingParmFile(9): The contacted switch didn't receive a parameter block file yet. Mgt should advice user that a proper parameter block file wasn't received on the contacted switch. Data may have been corrupted. tftpOperationMissingNvpFile(10): The contacted switch didn't receive a network vlan policy file yet. Mgt should advice user that a proper nvp file wasn't received on the contacted switch. Data may have been corrupted. tftpOperationMgtTimeout(11): The contacted switch didn't receive a keep-alive signal from the Mgt station for 60 seconds. If Mgt is still there it should advice the user to check connection between Mgt station and switch. factoryDefaultOperationFailed(12): A switch failed loading the configuration from default parameters. Mgt station should advice user to check status of the switches and possibly try again later. stackMemberRejectsOperation(13): A switch (other than the contacted) couldn't initiate the desired operation. Mgt should advice the user to check the stack status. If switches were added or removed during the operation this may have caused the problem. intraStackCommunicationError(16): Communication between the stack members failed. Mgt should advice user to check cable connections and status of the switches, and possibly try operation again. internalError(17): This should never occur, and would indicate that a switch is in a fatal state of error. Mgt should advice the user to report the problem to support. notReady(99):