US6691300B1 - Method and apparatus for analyzing the progress of a software upgrade on a telecommunications switch - Google Patents
Method and apparatus for analyzing the progress of a software upgrade on a telecommunications switch Download PDFInfo
- Publication number
- US6691300B1 US6691300B1 US09/430,983 US43098399A US6691300B1 US 6691300 B1 US6691300 B1 US 6691300B1 US 43098399 A US43098399 A US 43098399A US 6691300 B1 US6691300 B1 US 6691300B1
- Authority
- US
- United States
- Prior art keywords
- stage
- messages
- user interface
- message
- software upgrade
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Lifetime
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/1305—Software aspects
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/13109—Initializing, personal profile
Definitions
- the present invention is related to, and shares some disclosure with, U.S. patent application Ser. No. 09/431,741, entitled “Method and Apparatus for Determining Whether the Advance State of A Telecommunications Switch is Adequate for a Software Upgrade,” invented by Barshefsky et al., now U.S. Pat. No. 6,393,101; and U.S. patent application Ser. No. 09/430,903, entitled “Method and Apparatus for Determining Whether the Immediate State of a Telecommunications Switch Is Adequate for a Software Upgrade,” invented by Lilley et al., U.S. Pat. No. 6,396,904; both of which are filed concurrently with the present application.
- the present invention relates generally to telephone switching systems, and in particular, to a method and apparatus for analyzing the progress of software upgrades or retrofits on telephone switching systems.
- Modern telephone switching systems are large-scale, highly complex systems incorporating one or more switching elements cooperatively controlled and supervised by one or more computing means.
- One commercial exemplar of a modern telephone switching system is the 5ESS ELECTRONIC SWITCHING SYSTEM, from Lucent Technologies Inc., 600 Mountain Avenue, Murray Hill, N.J. 07974.
- the 5ESS electronic switch is a distributed switching system. Both the switching system capabilities and the control, supervision and administration capabilities are distributed.
- Each of the computing facilities associated with these distributed capabilities includes appropriate computer programs or software to achieve the desired operation of the switching elements and other components of the switching system.
- a report data stream is produced by the 5ESS switching system containing text messages regarding the current state and recent operations of the switching system.
- the report data stream includes messages that (1) describe the state of the switch hardware; (2) report automatic actions taken by the switch; (3) report operations entered by a switch operator; (4) report results of routine or scheduled diagnostics; and (5) indicate non-routine events, abnormal conditions, errors or alarms.
- the report data stream is typically supplied to a “read-only” printer or “ROP” via a serial port. Hence, the report data stream is often referred to as the “ROP” or “ROP” report.
- the report data stream is voluminous, sometimes generating 4 to 5 megabytes of data for storage per day. Therefore, the ROP is often stored on a computer to permit searching and review for problem solving.
- a telecommunications switch owner often desires to have all ROP output from its switches collected in a single location for review.
- the ROP or its equivalent, is typically reviewed manually or with the assistance of a computer to detect problems during a retrofit of a switch.
- this method of monitoring a retrofit is prone to miss errors and can be inefficient.
- this method requires substantial subject matter expertise from a person manually reviewing the ROP.
- a method for analyzing and displaying the progress of a software upgrade on a switch.
- First a report stream containing a plurality of messages associated with the state of the switch is received.
- the plurality of messages are searched for a select set of messages that are associated with the software upgrade.
- the select set of messages includes at least a first message associated with an entry into a stage of the software upgrade.
- the select set of messages includes a second message associated with an exit from the stage of the software upgrade.
- an entry message and an exit message for each stage of the software upgrade are included within the select set of messages.
- the user interface is updated to reflect the exit from that stage of the software upgrade.
- the user interface includes predetermined areas that are visually perceptible and associated with each stage of the software upgrade.
- the designated visually perceptible areas of the user interface are colored predetermined colors to reflect entry and exit from the stages of the software upgrade.
- messages associated with an entry into a stage of the retrofit are timed. That is, a timer is used to determine the actual elapsed time from entry message. The actual elapsed time is compared to an expected time associated with the stage. In this manner, an actual elapsed time from an entry into a stage is compared against an expected time for exit out of the stage. When the actual elapsed time exceeds the expected time associated with the stage, the user interface is updated accordingly to alert a user of a potential problem.
- predetermined error messages are detected in the report stream.
- these predetermined error messages reflect the occurrence of an event on the switch that should not occur during the software upgrade.
- the user interface is updated accordingly to alert a user to an error.
- an apparatus or system for monitoring the process of a software upgrade on a telecommunications switch.
- the apparatus includes a report receiver, a processor, and a user interface.
- the report receiver receives a stream of messages from the telecommunications switch to thereby produce a received stream of messages.
- the received stream of messages includes messages reflecting the state of the telecommunications switch.
- the processor is operably coupled to the report receiver and stores the received stream of messages and searches the received stream of messages for select messages. In particular, the processor searches for select messages indicating an entry into a stage of the software upgrade or messages reflecting an exit from a stage of the software upgrade.
- a user interface coupled to the processor reflects the entry and exit from the stages of the software upgrade.
- the user interface includes designated areas associated with each stage of the software upgrade and those designated areas are populated with predetermined text streams and colors reflecting entry and exit from the associated stages.
- the user interface includes an audible alarm for alerting a user to certain events associated with the software upgrade, for example, alarms.
- the processor includes a timer that times an actual elapsed time from the receipt of an entry message, reflecting entry into a stage of the software upgrade.
- the actual elapsed time is compared against an expected time and the user interface is updated if the actual elapsed time exceeds the expected time.
- predetermined error messages are detected and the user interface reflects the detection of the error messages.
- FIG. 1 is a block diagram of a system for monitoring and analyzing the progress of a software upgrade on a telecommunications switch in accordance with the present invention.
- FIG. 2 is a flow chart illustrating a method for monitoring and analyzing the progress of a software upgrade on a telecommunications switch in accordance with the present invention.
- FIG. 3 is a diagram illustrating a visual portion of a user interface for monitoring and analyzing the progress of a software upgrade on a telecommunications switch in accordance with the present invention.
- FIG. 4 is a diagram illustrating an additional visual portion of a user interface for monitoring and analyzing the progress of a software upgrade on a telecommunications switch in accordance with the present invention.
- FIG. 1 is a block diagram illustrating a system 100 for monitoring and analyzing the progress of a software upgrade on a telecommunications switch in accordance with the present invention.
- System 100 includes regional servers 102 , clients 104 , national server 106 and network 108 .
- Network 108 couples national server 106 and regional servers 102 together for data communications in a manner well known to those of skill in the art.
- Clients 104 are shown in FIG. 1 coupled to a regional server 102 or national server 106 directly by network connections 109 . Alternatively, clients 104 are directly coupled to network 108 .
- National server 106 , regional servers 102 and clients 104 are general-purpose computers programmed in a manner to implement the present invention, as described further below.
- Telecommunications switches 110 are coupled to system 100 to provide system 100 with information relating to the state of the telecommunications switches 110 . More specifically, each telecommunications switch 110 produces a report stream 114 .
- Report stream 114 is a serial stream of text messages reflecting the state of the telecommunications switch 110 , including error messages, alarms, and other state information.
- Regional servers 102 include a plurality of modems 112 that are coupled to modems 113 on switches 110 . Modems 112 and modems 113 are coupled together selectively over the public switched telephone network to facilitate transmission and reception of report stream 114 .
- the report stream 114 or ROP 114 is also transmitted to a ROP printer 116 or to a ROP spooler 118 .
- ROP spooler 118 typically is a computer that receives ROP 114 and stores ROP 114 for future processing.
- regional servers 102 are coupled to switches 110 to receive ROP 114 prior to a software upgrade. Most preferably, regional servers 102 are coupled to switches 110 six to eight hours prior to the beginning of the software upgrade. Regional servers 102 are preferably geographically disbursed in a region near the associated switches 110 .
- Network 108 provides a means for regional servers 102 to communicate with each other and a national server 106 .
- National server 106 is a centralized national server that is coupled to all regional servers 102 . This hierarchical arrangement permits regional servers 102 to monitor switches within its associated region and then for the national server 106 to monitor all regions via connections to the regional servers 102 .
- National server 106 and regional servers 102 are preferably implemented as a single or multiple general-purpose computers.
- servers 102 , 106 are PENTIUM-class computers running WINDOWS NT with SERVICE PACK 5 from Microsoft Corporation.
- Clients 104 are also general-purpose computers with monitors and keyboards provided for engineers and technicians to interface with system 100 .
- clients 104 are PENTIUM-class computers running WINDOWS 95, WINDOWS 98 or WINDOWS NT with SERVICE PACK 5, all from Microsoft Corporation.
- FIG. 2 is a flow chart illustrating a method for monitoring and analyzing a software upgrade on a telecommunications switch in accordance with the present invention.
- FIG. 2 is descried below with reference to the system shown in FIG. 1 .
- the report stream from the switch being monitored is received ( 200 ).
- modem 112 of regional server 102 receives a stream of text messages reflecting the state of the telecommunications switch 110 .
- the report stream contains text with certain indicia used by regional server 102 to delineate the boundaries for a message.
- Server 102 searches the report stream for certain messages.
- a database on server 102 or another computer on network 108 stores definitions of certain messages that are relevant to the software upgrade. Certain streams of text found in the report stream indicate the receipt of a message.
- the database is a SYBASE database available from Sybase, Inc., 6475 Christie Avenue, Emeryville, Calif. 94608-1050.
- the messages of interest relate to messages that must occur or should not occur during the software upgrade or retrofit.
- the software upgrade is delineated into certain distinct stages.
- the stages of the software upgrade typically include Begin, Enter, Tape, MOP, Pump SM, Pump CMP, TSMOLD, Proceed, OFLBOOT, SWITCH FORWARD, TSMNEW, TSMRMV, STOP OFLBOOT, BOOTHOOK, CORCS, RECENT CHANGE, COMMIT, and END.
- Begin merely indicates the beginning of the software retrofit. Enter signifies the beginning of the tape loading stage.
- Tape stage tapes are counted as they are read onto offline partitions of a file system.
- the offline partitions are mounted.
- the new generic (software) is loaded into the offline side of the switching module.
- the new generic is loaded into the offline side of the communications processor module.
- the TSMOLD stage a list of out of service trunks is created and saved.
- the Proceed stage the offline side of the administrative module is “pumped” or loaded.
- the OFLBOOT stage indicates the start of the boot of the administrative module.
- the SWITCH FORWARD stage the switch changes from a side running the old generic to a side running the new generic.
- the TSMNEW stage determines mismatches against the out-of-service list from TSMOLD stage and a previous out-of-service list.
- the TSMRMV stage makes the out-of-service list of trunks match the list created at the TSMOLD stage.
- the STOP OFLBOOT stage stops offline boot and restores information on a side of the administrative module.
- the BOOTHOOK stage updates recent change information on the side running the new generic.
- customer originated recent changes are updated.
- RECENT CHANGE stage recent changes are reapplied.
- the COMMIT stage restores the switching modules so that both sides are on the new generic and hard drives on the administrative module are restored with the new generic.
- the END stage indicates the end of the retrofit. Of course, the stages of the retrofit are redefined periodically.
- a message is associated with the entry into each stage and the exit from each stage of the retrofit.
- a failure message is associated with a stage.
- Table 1 below lists exemplary entry, exit, and failure messages for the stages of a software upgrade in the preferred embodiment.
- the “Stage” column indicates the relevant stage of the retrofit.
- the “State” column indicates entry, exit (completion), or failure of the associated stage. For example, “Begin” (row 1 ) indicates entry into the Begin stage; “Begin Complete” (row 2 ) indicates exit from the Begin stage; and “OFLBOOT failed” (row 19 ) indicates that the OFLBOOT stage failed.
- the “Image” column indicates an action to be taken in the user interface in response to receipt of the message.
- “ 1 ” indicates that a designated area in the user interface associated with the stage should be colored yellow; “ 2 ” indicates that the designated area should be colored green; and “ 3 ” indicates that the designated area should be colored red.
- the “Recognition” column lists the message that relates to the state of the associated stage. For example, “REPT RETRO BEGIN RESUME WHEN SESSION HAS STARTED” (row 1 ) is transmitted in the ROP stream and detected in accordance with the present invention to indicate entry into the Begin stage of the retrofit.
- the “ProgressID” column includes a number that determines whether the associated stage is displayed in certain views of the user interface. More specifically, a number other than “ 0 ” indicates that the stage is displayed in the consolidated status view of the user interface; and “ 2 ” indicates that the stage is displayed differently, for example, in a predetermined color, in the user interface.
- Server 102 determines whether a message received in the report stream relates to an entry into a retrofit stage ( 204 ). If the message does relate to an entry into a retrofit stage then a timer is set with the expected stage time ( 206 ), in particular, an expected time is predefined for each stage of the retrofit. This advantageously allows monitoring to determine whether a switch has remained in a stage of the retrofit for too long. This may indicate a problem requiring correction.
- the message associated with entry into the retrofit stage is stored, including a time and date stamp from the report stream that is associated with the message.
- the message reflecting entry into a retrofit stage is stored for use by the user interface as discussed further below.
- the search for predetermined messages continues.
- an exit message associated with an exit from that stage of the retrofit is received.
- the stage timer that was set for and upon the entry into that stage is reset ( 210 ). Under normal conditions where a stage completes prior to an expected stage time, resetting the stage timer is not detected by a user.
- stage timer expires prior to a reset ( 212 )
- a user is warned.
- the user is warned by updating the user interface in a predetermined manner, as discussed below.
- a reset of the stage timer ( 210 ) ends the time audit for a particular stage ( 216 ).
- Table 2 has three columns entitled “Recognition 1 ,” “Recognition 2 ,” and “Recognition 3 .” Each of these columns may contain a text stream.
- the actual ROP message being identified is the Boolean combination of Recognition 1 & Recognition 2 (if populated) & Recognition 3 (if populated) on the same line in the ROP stream. For example, referring to row 1 , a combination of “ALW” and “RC” on the same line in the ROP stream is a message of interest to the retrofit process.
- the “Type” column stores a number that is associated with certain actions that are taken in response to receipt of the identified message.
- the actions that may occur in response to the messages include, visually updating a user interface, audibly updating a user interface, storing the ROP message in one or more files, and inserting additional text into a file or user interface.
- the “Text 1 ” column includes text that is displayed in the user interface or stored in a file in response to receipt of the associated message.
- messages are detected.
- messages referred to as processor recovery messages or PRMs are received from the administrative module. These messages are a string of 16 hexadecimal numbers. Certain of the messages are detected and the system responds by visually updating a user interface, audibly updating a user interface, storing the ROP message in one or more files, or inserting additional text into a file or user interface. Actions taken in response to PRMs convert the cryptic hexadecimal code into a message or sound that is readily perceived by a person. In some cases, multiple lines of a ROP message are parsed to determine a message stored and displayed in a user interface.
- the method described above is preferably implemented with software running on servers 102 , 106 and clients 104 .
- the core monitoring application is preferably a multi-threaded NT service written in C++. This core monitoring application manages the connections to the switches 110 , collects and stores data from the switches 110 , and performs the analysis. For example, In order to connect to a switch, the server spawns a thread for that switch. All monitoring activities for that switch take place within the thread. Internal communications between applications is preferably accomplished using TCP/IP sockets. Data used to control the application, e.g., the predetermined messages, and data stored from the application, e.g., the identified messages, are stored in a database. A C++ library that encapsulates the database primitives provides application access to the database.
- the user interface is preferably a Microsoft Visual C++ application.
- FIG. 3 is a diagram illustrating a visual portion of a user interface for displaying the progress of a software upgrade on a telecommunications switch in accordance with the present invention.
- the user interface is implemented on a client 104 .
- Client 104 preferably has software that accesses the database on a server 102 , 106 and reflects changes made in the database in a visually aesthetic manner.
- the user interface is displayed on a computer monitor.
- Display 300 is a consolidated status display. Display 300 collectively shows in one screen the progress of multiple switches or offices undergoing a software upgrade.
- Display 300 includes a tool bar area 302 , with short cuts or buttons for selecting certain commands, including commands to connect to and disconnect from a regional server 102 or national server 106 .
- a region area 304 displays a label associated with the particular region being monitored, in this example, the “Southern” region.
- the display 300 is characterized by a set of columns and rows.
- Column 306 labeled “HC” relates to a “health check” conducted prior to the retrofit progress. The “health check” is performed prior to the retrofit to determine whether to proceed with the retrofit. This determination is described in co-pending patent applications referred to above in the cross-reference to related applications.
- Column 308 includes the name of the office or switch. In other words, column 308 lists the particular switch that is scheduled for a retrofit, generally by geographical designation. Columns 312 , 314 , 316 , 318 , 320 and 324 list certain stages of the retrofit and other pertinent fields relating to the retrofit. Column 312 relates to the COMMIT stage and column 314 relates to the END stage. Other stages are preferably displayed by scrolling horizontally in display 300 . Column 316 gives the status of the retrofit.
- the status column is populated with “Pending,” “Succeed,” “Failure” or “Abort.” Pending indicates the office will retrofit within five to seven days; Succeed indicates the retrofit was successful; Failure indicates the retrofit was not successfully completed; and Abort indicates the office retrofitted, but returned to the old generic.
- Column 318 relates to the down time associated with the retrofit; column 320 lists the time of the most recent note entered, if any; and column 324 lists the number of OFL boot attempts.
- Each row of display 300 relates to the switch or office listed in column 308 .
- the area defined by the intersection of a column relating to a stage of the retrofit and a row related to a particular office being retrofit is used to display information associated with that particular stage of the retrofit.
- area 350 which is the intersection of column 312 and row 332 , relates to the commit stage of the retrofit for the Shreveport, Louisiana office listed in column 308 , row 332 .
- a date and time associated with the entry into the commit stage is listed in area 350 and a date and time associated with the exit out of the commit stage is shown below the entry data in area 350 .
- Area 350 is colored a predetermined color to indicate certain status relating to the associated stage of the retrofit at the associated office.
- a background color of green is used to reflect no errors found in the associated stage of the retrofit.
- a flashing yellow background that is alternating between yellow and another color, or the lack thereof, is used to indicate that a stage has exceeded a predetermined expected stage time.
- a non-flashing yellow background color indicates the stage is in progress and has not exceeded an expected time.
- a red color is used to indicate that an error occurred during the associated stage at the associated office.
- a blue color is used to indicate the OFLBOOT stage. Other colors are optionally used.
- the area of the user interface containing the name of the office preferably reflects general status about the office. In particular, this area preferably flashes red to indicate a major or critical alarm at an office. Selecting any stage box, for example, by double clicking on the stage box, causes the user interface to display a status display for the selected office.
- a stage box is defined by the intersection of a column relating to a retrofit stage and a row relating to a particular office or switch. The status display is discussed below with respect to FIG. 4 . Selecting a row in the notes column 320 causes the user interface to display a window containing a note if one exist.
- FIG. 4 shows a status display 400 relating to the progress of a retrofit for a single switch or office.
- Status display 400 provides additional details associated with a certain office in designated areas or panes.
- display 400 includes a ROP output pane 402 , a MSG file output pane 404 , an FRM file output pane 406 , a stage pane 408 , a switch pump pane 410 and an alarm pane 412 .
- Display 400 also includes a toolbar 420 , which displays icons for certain commands, and a status bar 440 , which includes additional status.
- ROP output pane 402 displays the text stream from the ROP as it is received and stored in a log file.
- the text in the pane scrolls as additional text is received, but is paused by selecting a pause command in toolbar 420 .
- the MSG file output pane 404 displays messages written to a .msg file.
- the .msg file contains alarm messages received in the ROP for the switch during monitoring. Alarms are indications of events on the switch that may require corrective action. Alarms fall into three categories reflecting their level of severity—minor, major, or critical.
- the FRM output pane 406 displays output written to a form file for the office.
- the form file is written in response to the receipt of predetermined messages.
- the form file contains, for example, the entry and exit messages for each stage, failing processor recovery messages (PRMs), errors and other predetermined messages.
- PRMs failing processor recovery messages
- the form file is useful to diagnose problems.
- the alarm pane 412 displays the most recent alarm message.
- Alarm pane 412 is preferably colored green for minor alarms, yellow for major alarms and red for critical alarms.
- the acknowledge button 422 is used to acknowledge the occurrence of the current alarm.
- the ACK all button is used to acknowledge all pending alarms.
- the buttons 422 , 424 are made inactive when no alarms are pending. Alarms also cause an audible sound, with the sound varying with the severity of the alarm.
- the switch pump pane 410 indicates when each switching module is “pumped” or completed.
- the word “pumped” appears next to the switching module number when the associated switching module is pumped. If there are errors in the pump process, the errors are indicated, rather than the word “pumped.”
- the stage pane 408 shows the progress of the office through the stages of the retrofit.
- An area or stage square 430 is provided for each stage with the name of the stage designated below the square 430 .
- the stage square 430 is colored a predetermined color to reflect the status of the stage of the retrofit. Preferably, green indicates that the stage is complete; yellow indicates the stage is in progress; red indicates the stage failed; and blue indicates offline boot is running or OFLBOOT is in progress.
- Display 400 includes a status bar 440 that includes additional status information.
- section 442 contains a voice phone number associated with the office;
- section 444 contains a foreign exchange number associated with the switch;
- section 446 indicates which retrofit tape is being loaded;
- section 448 indicates whether notes have been entered for the office.
- the present invention includes a system for regional and national monitoring of retrofits on telecommunication switches.
- Retrofit monitoring advantageously allows for early problem detection and correction to efficiently utilize resources during a retrofit.
- Centralized retrofit monitoring advantageously allows for ready and remote diagnoses of problems due to expertise gained from previous retrofit monitoring. Though described above with respect to telecommunications switching systems, the retrofit monitoring process may equally apply to software upgrades on other processor-based systems.
Abstract
Description
TABLE 1 | |||||
Stage | State | Image | Recognition | ProgressID | |
Begin | Begin | 1 | REPT RETRO BEGIN RESUME | 1 | |
WHEN SESSION HAS STARTED | |||||
Begin | Begin Complete | 2 | UPD GEN BEGIN COMPLETED | 1 | |
SUCCESSFULLY | |||||
Enter | Enter | 1 | MOUNT TEXT TAPE FOR MHD 0/1 | 1 | |
ON | |||||
Enter | Enter Complete | 2 | REPT ENTER HOOK COMPLETED | 1 | |
SUCCESSFULLY | |||||
Tape | Tape | 1 | UPD GEN ENTER MOUNT TAPE | 0 | |
AND CONTINUE | |||||
Tape | Tape Loaded | 2 | /updtmp/site/toolxfer/info.out | 0 | |
MOP | MOP | 1 | ISMOP REPORT | 0 | |
MOP | MOP Complete | 2 | REPT PROC SCHED PROCEED | 0 | |
PAUSED | |||||
Pump SM | Pump SM | 1 | ST:OPUMP,SM | 0 | |
Pump SM | Pump SM Complete | 2 | REPT PROC SCHED PROCEED | 0 | |
PAUSED | |||||
Pump CMP | Pump CMP | 1 | ST:OPUMP, CMP = 0,MATE | 0 | |
Pump CMP | Pump CMP Complete | 2 | ST OPUMP CMP = 1-0 COMPLETED | 0 | |
TSMOLD | TSMOLD | 1 | REPT RETRO PROCEED CONTINUE | 0 | |
TSMOLD | TSMOLD Complete | 2 | UPD GEN TSM COMPLETED | 0 | |
Proceed | Proceed | 1 | REPT RETRO PROCEED EAI SETUP | 1 | |
Proceed | Proceed Complete | 2 | REPT PROC SCHED SWITCHFWD | 1 | |
PAUSED AT STAGE BOUNDARY | |||||
OFLBOOT | OFLBOOT | 1 | AM OFFLINE BOOT STARTED | 2 | |
OFLBOOT | OFLBOOT Complete | 2 | EXC OFLBOOT COMPLETED | 2 | |
OFLBOOT | OFLBOOT failed | 3 | OFFLINE BOOT FAILED | 2 | |
OFLBOOT | OFLBOOT failed | 3 | OFLBOOT TERMINATED | 2 | |
OFLBOOT | OFLBOOT failed | 3 | ERROR CODE f031 | 2 | |
SWITCH | SWITCHFWD | 1 | SWITCHING SMS | 1 | |
FORWARD | |||||
SWITCH | SWITCHFWD | 2 | SWITCH ONLINE SIDE | 1 | |
FORWARD | Complete | COMPLETED | |||
SWITCH | SWITCHFWD | 3 | ERROR SWITCHING SMS | 1 | |
FORWARD | |||||
TSMNEW | TSMNEW | 1 | REPT ALWCHKS STARTING | 0 | |
ALWCHKS FOR SM | |||||
TSMNEW | TSMNEW Complete | 2 | UPD GEN TSM CADN SUMMARY | 0 | |
TSMRMV | TSMRMV | 1 | TSMRMV | 0 | |
TSMRMV | TSMRMV Complete | 2 | UPD GEN TSM COMPLETED | 0 | |
STOP | STOP OFLBOOT | 1 | STOP OFLBOOT STARTED | 0 | |
OFLBOOT | |||||
STOP | STOP OFLBOOT | 2 | STOP OFLBOOT COMPLETED | 0 | |
OFLBOOT | Comp. | ||||
BOOTHOOK | BOOTHOOK | 1 | offrcr.out | 1 | |
| BOOTHOOK | 2 | BOOT HOOK COMPLETED | 1 | |
Complete | |||||
CORCS | CORCS | 1 | CNVT CORCLOG LOAD STARTED | 0 | |
| CORCS Complete | 2 | |
0 | |
LOAD:CONCURRENT CONTROL | |||||
PROCESS COMPL | |||||
RECENT | RECENT CHANGE | 1 | RCNEW ODDEVOL STARTED | 1 | |
CHANGE | |||||
RECENT | RECENT CHANGE | 1 | RC REAPPLICATION | 1 | |
CHANGE | CONCURRENT PROCESS | ||||
STARTED | |||||
RECENT | |
2 | RCNEW ODDEVOL COMPLETED | 1 | |
CHANGE | Comp. | ||||
COMMIT | COMMIT | 1 | RETRO COMMIT CONTINUING | 1 | |
COMMIT | COMMIT Complete | 2 | UPD GEN COMMIT COMPLETED | 1 | |
COMMIT | COMMIT Complete | 2 | REPT CMT HOOK COMPLETED | 1 | |
SUCCESSFULLY | |||||
END | END | 1 | UPD GEN END APP EXECUTING | 1 | |
| END Complete | 2 | UPD GEN END COMPLETED | 1 | |
TABLE 2 | ||||
Recognition1 | Recognition2 | Recognition3 | Type | Text1 |
ALW: | RC | 0 | ||
AUD: | 0 | |||
BKUP: | ODD | 0 | ||
CCS TRUNK | 0 | |||
SIGNALING IN | ||||
SERVICE | ||||
CLR: | AMA | MAPS | 0 | |
CLR: | FILESYS | 0 | ||
CLR: | TRN | 0 | ||
CMTHOOK | COMPLETE | 0 | ||
CNVT: | AMA | CONFIG | 0 | |
CNVT: | RCLOG | 0 | ||
CORCS HAVE | 0 | |||
BEEN LOG | ||||
DFC | ERROR | 0 | ||
ENDHOOK | COMPLETE | 0 | ||
ERROR | CAN | 0 | ||
ERROR | INV | 0 | ||
EXC OFLBOOT | 0 | |||
STARTED | ||||
EXC: | ENVIR | UPROC | 0 | |
EXC: | ODDRCVY | 0 | ||
EXC: | POPCO | 0 | ||
GLCCS | IS SET TO | 0 | ||
INH: | CORC | 0 | ||
INH: | RC | 0 | ||
INIT: | AM | 0 | ||
MHD | AUTONOMOUS | 0 | ||
MNT OFL PTNS | 0 | |||
OFFLINE PUMP | ||||
MODECD | COMPLETE | 0 | ||
OFFLINE PERIPH | DISK | 0 | ||
OFFLINE PERIPH | ERROR | 0 | ||
OFFLINE PERIPH | HASH | 0 | ||
OFFLINE PERIPH | INCON | 0 | ||
OFFLINE PERIPH | PATH | 0 | ||
OFFLINE PERIPH | PROB | 0 | ||
OFFLINE PERIPH | UNAV | 0 | ||
OFFLINE PERIPH | VERIFY | 0 | ||
OFFLINE PUMP | DISK | 0 | ||
OFFLINE PUMP | ERROR | 0 | ||
OFFLINE PUMP | FAIL | 0 | ||
OFFLINE PUMP | HASH | 0 | ||
OFFLINE PUMP | INCON | 0 | ||
OFFLINE PUMP | PATH | 0 | ||
OFFLINE PUMP | PROB | 0 | ||
OFFLINE PUMP | UNAV | 0 | ||
OFFLINE PUMP | VERIFY | 0 | ||
OP:GEN | RESET | 0 | ||
ORD:CPI | 0 | |||
REPT | BOOT HOOK | 0 | ||
COMPLETED | ||||
REPT | CACHE-ERR | 0 | ||
REPT | DFC | CODE | 0 | |
REPT | ISOLATE | 0 | ||
REPT | MHD 0 UNEQUIPPED | 0 | ||
REPT | PRCD HOOK | 0 | ||
COMPLETED | ||||
REPT | PROCEED PAUSED AT | 0 | ||
STAGE BOUNDARY | ||||
REPT | RETRO PROCEED | 0 | ||
PERFORM | ||||
REPT DKDRV | 0 | |||
REPT RETRO | 0 | |||
BEGIN | ||||
ST:OPUMP | 0 | |||
STOP OFLBOOT | 0 | |||
COMPLETED | ||||
STOP: | EXC | ANY | 0 | |
STOP: | EXC | USER | 0 | |
STOP:OFLBOOT,R | 0 | |||
ST | ||||
STOP:OLFBOOT,R | 0 | |||
ST | ||||
STP: | RCRLS | 0 | ||
STP:OPUMP | 0 | |||
SUPPORTED | 0 | |||
RCVS LOGGED: | ||||
TCAP SIGNALING | 0 | |||
IN SERVICE | ||||
TRANSITION SPEC | 0 | |||
UPD GEN | AM OFFLINE BOOT | 0 | ||
SUCCESSFUL | ||||
UPD GEN | END APP EXECUTING | 0 | ||
UPD GEN | ENTER | BLOCKS | 0 | |
WRITTEN | ||||
UPD GEN | OFFLINE | 0 | ||
UPD GEN | SELECTED FOR | 0 | ||
UPD GEN | SWITCHFWD | COMPLETED | 0 | |
UPD GEN | SWITCHFWD | STARTED | 0 | |
UPD GEN | TSM | COMPLETE | 0 | |
UPD GEN | TSM IN PROGRESS | 0 | ||
UPD:BKOUT | 0 | |||
UPD:BOLO | 0 | |||
UPD:EXALL | APPLY | 0 | ||
UPD:EXALL | OFC | 0 | ||
UPD:EXALL | SOAK | 0 | ||
UPD:GEN | APPLPROC | “MOP” | 0 | |
UPD:GEN | APPLPROC | APPLY | 0 | |
UPD:GEN | APPLPROC | HOOK | 0 | |
UPD:GEN | APPLPROC | MODECD | 0 | |
UPD:GEN | APPLPROC | STOPMOP | 0 | |
UPD:GEN | APPLPROC | TOOLS | 0 | |
UPD:GEN | APPLPROC | TSMNEW | 0 | |
UPD:GEN | APPLPROC | TSMOLD | 0 | |
UPD:GEN | APPLPROC | TSMRMV | 0 | |
UPD:GEN | APPLPROC | WRTAMA | 0 | |
UPD:GEN | BACKOUT | 0 | ||
UPD:GEN | CONTINUE | 0 | ||
UPD:GEN | SMBKOUT | 0 | ||
UPD:GEN | STOPOLB | 0 | ||
UPD:GEN | SWITCH | 0 | ||
UPD:UPNAME | 0 | |||
WRT:AMADATA | 0 | |||
UPD:GEN | BEGIN | 1 | ||
MOUNT | FOR MHD | AND RESUME | 2 | |
UPD GEN | ENTER | MOUNT TAPE | 2 | |
AND CONTINUE | ||||
STOP: | GEN | 3 | ||
UPD:GEN | RESTORE | 3 | ||
UPD:GEN | ENTER | 4 | ||
UPD:GEN | MHDSTAT | 4 | ||
EXT-BOARD-ADDR | 5 | |||
CNVT | CORCLOG | STOPPED | 6 | |
MOVELOG | 6 | |||
REPT | POPCO | 6 | ||
SUPR ERROR | 6 | |||
CODE | ||||
CNVT: | CORC | 7 | START CORCs | |
EXC: | RCRLS | EVOL | 7 | START RECENT CHANGE |
EXC: | RCRLS | OSPS | 7 | START RECENT CHANGE |
RCNEW ODDEVOL | 7 | RECENT CHANGE COMPLETE | ||
COMPLETED | ||||
RCNEW ODDEVOL | 7 | RECENT CHANGE COMPLETE | ||
STOP | ||||
START OF CU | RECOVERY | 7 | BOOT START of | |
CU RECOVERY | ||||
RCNEW ODDEVOL | 8 | RECENT CHANGE COMPLETE | ||
ABORT | ||||
DATE = | 9 | *****BASE # | ||
PROCESSOR: | CP | 9 | ***** AM ODD | |
PROCESSOR: | IM | 10 | ||
UPD:GEN | APPLPROC | LOOKODD | 11 | |
REPT | CORR-BIT-ERR | 12 | ||
REPT | MEM-SYSTEM | 12 | ||
REPT | PARITY-ERROR | 12 | ||
REPT | HASHSUM FAILURE | 13 | ||
CNVT | CORCLOG | LOAD SM = | 14 | |
CORCS | IN ERROR | 15 | ||
BOOTHOOK | COMPLETE | 16 | BOOTHOOK COMPLETE | |
CONCURRENT | 16 | CORCs COMPLETE | ||
CONTROL PROCESS | ||||
COMPLETED | ||||
ENTRHOOK | COMPLETE | 16 | ENTRHOOK COMPLETED | |
INSTALLTOOLS | COMPLETE | 16 | INSTALLTOOLS COMPLETE | |
MODIFY | COMPLETE | 16 | MODIFY COMPLETE | |
PRCDHOOK | COMPLETE | 16 | PRCDHOOK COMPLETE | |
UPD GEN | COMMIT | COMPLETED | 16 | COMMIT STAGE COMPLETE |
UPD GEN | ENTER | COMPLETED | 16 | TAPE LOAD COMPLETE |
UPD GEN | PROCEED | COMPLETED | 16 | PROCEED STAGE COMPLETE |
UPD:GEN | COMMIT | 16 | START COMMIT STAGE | |
UPD:GEN | END | 16 | END STAGE | |
UPD:GEN | PROCEED | 16 | START PROCEED STAGE | |
BACKOUT-RC | 18 | Fix RC BACKOUT before | ||
RC reapp starts (RC/DB) | ||||
STOPPED WITH | 19 | |||
ERROR CODE | ||||
REPT RETROFIT | 21 | |||
TOTAL SYSTEM | ||||
DOWNTIME | ||||
DOWNTIME | 22 | |||
Claims (24)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/430,983 US6691300B1 (en) | 1999-11-01 | 1999-11-01 | Method and apparatus for analyzing the progress of a software upgrade on a telecommunications switch |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/430,983 US6691300B1 (en) | 1999-11-01 | 1999-11-01 | Method and apparatus for analyzing the progress of a software upgrade on a telecommunications switch |
Publications (1)
Publication Number | Publication Date |
---|---|
US6691300B1 true US6691300B1 (en) | 2004-02-10 |
Family
ID=30771272
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/430,983 Expired - Lifetime US6691300B1 (en) | 1999-11-01 | 1999-11-01 | Method and apparatus for analyzing the progress of a software upgrade on a telecommunications switch |
Country Status (1)
Country | Link |
---|---|
US (1) | US6691300B1 (en) |
Cited By (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050193385A1 (en) * | 2004-02-27 | 2005-09-01 | De Heer Arie J. | Method and apparatus for upgrading software in network bridges |
US7062545B1 (en) * | 2000-10-10 | 2006-06-13 | At&T Corp. | System and method for managing dial platform configuration |
US20140157253A1 (en) * | 2011-03-31 | 2014-06-05 | Alcatel-Lucent India Limited | Retrofitting a processor cluster |
US20150193230A1 (en) * | 2014-01-09 | 2015-07-09 | Bank Of America Corporation | Entity wide software tracking and maintenance reporting tool |
US20160142258A1 (en) * | 2014-11-19 | 2016-05-19 | Candi Controls, Inc. | Methods and systems for verifying installation of a device |
US10855761B1 (en) | 2018-12-31 | 2020-12-01 | Facebook, Inc. | Techniques for in-place directive execution |
US10979500B1 (en) * | 2018-12-31 | 2021-04-13 | Facebook, Inc. | Techniques for directive-based messaging synchronization |
US11025576B1 (en) | 2018-12-31 | 2021-06-01 | Facebook, Inc. | Techniques for backend-specific cursor tracking |
US11055314B1 (en) | 2018-12-31 | 2021-07-06 | Facebook, Inc. | Techniques for a database-driven messaging user interface |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5710899A (en) * | 1991-12-06 | 1998-01-20 | Lucent Technologies Inc. | Interactive selectors for selecting subsets of a set of values |
US6078647A (en) * | 1997-11-21 | 2000-06-20 | Hewlett Packard Company | Method and apparatus for detecting a data service provider in a public switched telephone network |
-
1999
- 1999-11-01 US US09/430,983 patent/US6691300B1/en not_active Expired - Lifetime
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5710899A (en) * | 1991-12-06 | 1998-01-20 | Lucent Technologies Inc. | Interactive selectors for selecting subsets of a set of values |
US6078647A (en) * | 1997-11-21 | 2000-06-20 | Hewlett Packard Company | Method and apparatus for detecting a data service provider in a public switched telephone network |
Non-Patent Citations (4)
Title |
---|
Atkins et al., "Using version control data to evaluate the impact of software tools", ACM, pp. 324-333, May 1999. * |
Eick et al., "Graphical analysis of computer log files", ACM, pp. 50-56, Dec. 1994.* * |
La Porta et al., "Direct signaling: a new access signaling architecture", IEEE, pp. 489-501, Aug. 1997.* * |
McWhirter, "VGrep: a graphical tool for the exploration of textural documents", ACM, pp. 324-325, May 1995.* * |
Cited By (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7062545B1 (en) * | 2000-10-10 | 2006-06-13 | At&T Corp. | System and method for managing dial platform configuration |
US20050193385A1 (en) * | 2004-02-27 | 2005-09-01 | De Heer Arie J. | Method and apparatus for upgrading software in network bridges |
US7392520B2 (en) * | 2004-02-27 | 2008-06-24 | Lucent Technologies Inc. | Method and apparatus for upgrading software in network bridges |
US20140157253A1 (en) * | 2011-03-31 | 2014-06-05 | Alcatel-Lucent India Limited | Retrofitting a processor cluster |
US20160274897A1 (en) * | 2014-01-09 | 2016-09-22 | Bank Of America Corporation | Entity wide software tracking and maintenance reporting tool |
US9417868B2 (en) * | 2014-01-09 | 2016-08-16 | Bank Of America Corporation | Entity wide software tracking and maintenance reporting tool |
US20160274908A1 (en) * | 2014-01-09 | 2016-09-22 | Bank Of America Corporation | Entity wide software tracking and maintenance reporting tool |
US20150193230A1 (en) * | 2014-01-09 | 2015-07-09 | Bank Of America Corporation | Entity wide software tracking and maintenance reporting tool |
US9740477B2 (en) * | 2014-01-09 | 2017-08-22 | Bank Of America Corporation | Entity wide software tracking and maintenance reporting tool |
US9898276B2 (en) * | 2014-01-09 | 2018-02-20 | Bank Of America Corporation | Entity wide software tracking and maintenance reporting tool |
US20160142258A1 (en) * | 2014-11-19 | 2016-05-19 | Candi Controls, Inc. | Methods and systems for verifying installation of a device |
US9923769B2 (en) * | 2014-11-19 | 2018-03-20 | Candi Controls, Inc. | Methods and systems for verifying installation of a device |
US10855761B1 (en) | 2018-12-31 | 2020-12-01 | Facebook, Inc. | Techniques for in-place directive execution |
US10979500B1 (en) * | 2018-12-31 | 2021-04-13 | Facebook, Inc. | Techniques for directive-based messaging synchronization |
US11025576B1 (en) | 2018-12-31 | 2021-06-01 | Facebook, Inc. | Techniques for backend-specific cursor tracking |
US11055314B1 (en) | 2018-12-31 | 2021-07-06 | Facebook, Inc. | Techniques for a database-driven messaging user interface |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8799722B2 (en) | Business to business network management event detection and response system and method | |
US9900226B2 (en) | System for managing a remote data processing system | |
US5748098A (en) | Event correlation | |
US5287505A (en) | On-line problem management of remote data processing systems, using local problem determination procedures and a centralized database | |
EP1146689B1 (en) | Tree hierarchy and description for generated logs | |
US8176137B2 (en) | Remotely managing a data processing system via a communications network | |
US6141777A (en) | System and method for reporting telecommunication service conditions | |
EP0602295B1 (en) | Method for configuring and operating a telecommunication apparatus | |
US6115743A (en) | Interface system for integrated monitoring and management of network devices in a telecommunication network | |
US20090158189A1 (en) | Predictive monitoring dashboard | |
KR20060051738A (en) | System and method for managing data concerning service dispatch | |
US6691300B1 (en) | Method and apparatus for analyzing the progress of a software upgrade on a telecommunications switch | |
CA2254141A1 (en) | Method and apparatus for integrated network management and systems management in communications networks | |
JP2003104644A (en) | Restoration support system for broken down elevator and monitor center | |
CN101197621A (en) | Method and system for remote diagnosing and locating failure of network management system | |
US6396904B1 (en) | Method and apparatus for determining whether the immediate state of a telecommunications switch is adequate for a software upgrade | |
US6393101B1 (en) | Method and apparatus for determining whether the advance state of a telecommunications switch is adequate for a software upgrade | |
JP2006023910A (en) | Server fault recovery method and server fault recovery system | |
KR20050058772A (en) | System and method for providing internet failure management using wire and wireless network | |
JP3449425B2 (en) | Computer network monitoring support system | |
US7848244B1 (en) | SONET network outage impact measurement | |
US20030012211A1 (en) | Query and analysis method for MSTPs in a mobile telecommunication network | |
EP0471638B1 (en) | Problem prevention on a computer system in a service network of computer systems | |
JPH08181693A (en) | Countermeasure and management device against network fault | |
KR100443914B1 (en) | system and method for providing fault information |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: LUCENT TECHNOLOGIES INC., NEW JERSEY Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:ALEXANDER, EDDIE GAYLE;BROUGHTON, JOHN CRAVENS;CHAMBERLIN, ROBERT EARL, JR.;AND OTHERS;REEL/FRAME:010369/0451;SIGNING DATES FROM 19991027 TO 19991028 |
|
FEPP | Fee payment procedure |
Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
FPAY | Fee payment |
Year of fee payment: 4 |
|
FPAY | Fee payment |
Year of fee payment: 8 |
|
FPAY | Fee payment |
Year of fee payment: 12 |
|
AS | Assignment |
Owner name: OMEGA CREDIT OPPORTUNITIES MASTER FUND, LP, NEW YORK Free format text: SECURITY INTEREST;ASSIGNOR:WSOU INVESTMENTS, LLC;REEL/FRAME:043966/0574 Effective date: 20170822 Owner name: OMEGA CREDIT OPPORTUNITIES MASTER FUND, LP, NEW YO Free format text: SECURITY INTEREST;ASSIGNOR:WSOU INVESTMENTS, LLC;REEL/FRAME:043966/0574 Effective date: 20170822 |
|
AS | Assignment |
Owner name: WSOU INVESTMENTS, LLC, CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:ALCATEL LUCENT;REEL/FRAME:044000/0053 Effective date: 20170722 |
|
AS | Assignment |
Owner name: BP FUNDING TRUST, SERIES SPL-VI, NEW YORK Free format text: SECURITY INTEREST;ASSIGNOR:WSOU INVESTMENTS, LLC;REEL/FRAME:049235/0068 Effective date: 20190516 |
|
AS | Assignment |
Owner name: WSOU INVESTMENTS, LLC, CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:OCO OPPORTUNITIES MASTER FUND, L.P. (F/K/A OMEGA CREDIT OPPORTUNITIES MASTER FUND LP;REEL/FRAME:049246/0405 Effective date: 20190516 |
|
AS | Assignment |
Owner name: WSOU INVESTMENTS, LLC, CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:TERRIER SSC, LLC;REEL/FRAME:056526/0093 Effective date: 20210528 |