As handy and useful as Mitel's OPSMAN is, if you're a regular OPSMAN user there is likely to come the day when you need to say "whoa" when something starts going terribly wrong and OPSMAN ignores your attempts to stop the job from its GUI interface.
If you've ever needed to STOP!! OPSMAN when it's in the middle of some automated task, such as an automated software upgrade that you see is failing miserably, the only way I've found to immediately kill the job and get OPSMAN to abort it (and stop retrying) is to unplug the Ethernet cable, either from the OPSMAN server or from the system (PBX) that OPSMAN is communicating with. Obviously if you're performing some remote task you'll need access either to the router or Etherswitch so you can shut down the port.
OPSMAN runs scripts and bases its actions on what it sees coming back from the PBX. Therefore, going into the maintenance terminal and entering the command "data terminate" in the middle of an OPSMAN-automated data save/restore/convert job will only cause OPSMAN to try to restart it... over and over. However, by interrupting OPSMAN's ability to communicate with the PBX, he realizes that something's terribly wrong and will (almost immediately) abort the task.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.