as discussed above , device mimics are displayed images that can indicate the status of one or more corresponding physical or logical devices . by using a device mimic , a user is presented with a graphical representation of a device that can be used to display device status in an intuitive format . in accordance with the present invention , display updates are depicted in the mimic upon detection of a change in device status or at periodic , e . g ., pre - selected , intervals . by selecting the interval between device updates to be small , a change in device status is illustrated soon after it occurs . display updates are accomplished in accordance with the present invention by changing those portions of the mimic display that correspond to a device having a status that changed since the last update . the other portions of the display are usually left unaltered . the present invention takes advantage of the fact that status sub - images that relate to device characteristics that have not changed their status since the last update , as well as fixed sub - images , need not be updated . one embodiment of the present invention involves monitoring the status of one or more physically remote devices from a management system including , e . g ., a computer and a display device . in the exemplary embodiment , the management system is coupled to a monitoring system via the internet and / or an intranet . in the exemplary embodiment , the monitored device is a network device , e . g ., router . though this exemplary embodiment is used to display information relating to a network device , it is envisioned that the device mimic described herein may be applied to display the status of any type of monitored device whether it be a logical or physical device . [ 0032 ] fig1 illustrates system 100 implemented in accordance with the present invention . as illustrated , system 100 comprises management system 102 , monitoring system 118 , network device 104 , e . g ., a router , computer 111 , digital camera 112 , for creating graphical data , and an information database , e . g ., management information database ( mid ) 106 . management system 102 , computer 111 , digital camera 112 and monitoring system 118 are coupled to network device 104 via network connections 108 a , 108 b , 108 c , and 108 d , respectively . network device 104 and network connections 108 a - 108 d may comprise part of an intranet or the internet . mid 106 , which couples to monitoring system 118 , includes device - status information , such as port - status information about network device 104 . monitoring system 118 , network device 104 , and management system 102 each include input / output ( i / o ) ports used for interfacing with network connections 108 a - 108 d . management system 102 includes computer 130 for performing various operations in response to routines , data , and information stored within computer 130 that relate to system management functions . management system 102 also includes display device 134 and printer 110 . various functions of computer 130 relate to the generation and updating of device mimic 140 which is displayed as part of web browser screen 139 . computer 130 displays web browser screen 139 and mimic 140 on display device 134 . monitoring system 118 is responsible for monitoring the status of network device 104 and the status of various other devices included in system 100 , e . g ., computer 111 and digital camera 112 . a particular implementation may include monitoring system 118 as part of network device 104 . network device 104 maintains and uses the information contained in mid 106 to provide status - update information and initial - device mimic description files to management system 102 . for purposes of explanation , network device 104 , which may be , e . g ., a router , bridge , switch , repeater , hub , or any other similar type of device that transmits digital information or data between locations based on routing information , will be used as an exemplary monitored device . display device 134 , which forms part of management system 102 , may be of any type including , but not limited to , a cathode ray tube display or a light emitting diode (“ led ”) display . the internal structure of the computer 130 is illustrated in fig2 . fig1 depicts mimic 140 being displayed on display 134 . mimic 140 may be the same as , or similar to , the mimics shown in fig3 and 4 . the manner in which mimic 140 is generated and refreshed by computer 130 in accordance with the present invention will be discussed below in detail with respect to fig5 and 6 . [ 0038 ] fig2 depicts an exemplary embodiment of those components associated with computer 130 for displaying a mimic 140 , e . g ., of the type depicted in fig3 and 4 , on the display 134 . computer 130 may comprise a personal computer ( pc ), a workstation , a server , a mainframe computer , or any other type of computer . system memory 202 , included within computer 130 , comprises read only memory ( rom ) 204 and random access memory ( ram ) 206 . ram 206 includes basic input / output system ( bios ) 208 , which contains basic routines to transfer information between the elements within computer 130 , such as during start - up . ram 206 also includes an html document that includes visible frame 207 a and hidden frame 207 b . rom 204 may include operating system 209 a , applications 209 b , data 209 c , other program modules 209 d , and web browser 209 e . computer 130 further includes drive portion 220 , comprising hard disk drive interface 222 , hard disk drive 224 , magnetic disk drive interface 226 , magnetic disk drive 228 , optical disk drive interface 230 , and optical disk drive 232 . magnetic disk drive 228 writes to or reads from a ( e . g ., removable ) magnetic disk ( not shown ). optical disk drive 232 reads from or writes to a removable optical disk ( not shown ) such as a compact disk or a digital video disk ( dvd ). hard disk drive 224 , magnetic disk drive 228 , and optical disk drive 232 are coupled to system bus 280 by hard disk drive interface 222 , magnetic disk drive interface 226 , and optical drive interface 230 , respectively . the drives and their associated storage media may provide non - volatile storage of machine readable instructions , data structures , program modules , and other information that may be utilized by computer 130 . some contents , such as operating system 209 a , which may be stored in hard disk drive 224 , may be written into rom 204 during initial startup of computer 130 . some contents of hard disk drive 224 , i . e ., applications , may be written into corresponding locations in rom 204 or ram 206 as a result of user input of computer 130 . thus , hard disk drive 224 ( and its associated hard disk ) may comprise the following copies : operating system 235 a , application programs 235 b , data 235 c , program modules 235 d , and web browser 235 e . copies in the hard disk drive correspond to locations in rom 204 . since the access space of the hard disk drive 224 is considerably larger than that of rom 204 , only some of the data and programs contained in hard disk drive 224 may be stored in rom 204 at any given time . though fig2 depicts a hard disk drive , a removable magnetic disk drive , and an optical disk drive , those skilled in the art will appreciate that other types of storage media may be used . these other types of storage media include , but are not limited to magnetic cassettes , flash memory cards , digital video disks , bernouli cartridges , other types of ram , and other types of rom . in addition , a number of program modules may be stored on the hard disk , magnetic disk , optical disk , rom , or ram , such as an operating system , one or more application program , display driver , printer driver , and program data , for example . a user may enter commands and information into personal computer 130 through input devices , such as keyboard 270 , or a mouse , a joystick , or a microphone ( not shown ). output devices , such as display 134 , display data output from computer 130 . display device 134 connects to computer 130 via display interface 248 and system bus 280 . computer 130 may operate in a networked environment , defined by logical connections between one or more remote computers , such as the management system 102 or an additional computer depicted in fig2 as remote computer 250 . the connections depicted in fig2 are intended to comprise local area network ( lan ), wide area network wan , intranet , internet , and / or isdn configurations . remote computer 250 may be a pc , a server , a router , a network pc , or other common network node , or any other known computer . remote computer 250 may include many or all of the elements described above relative to computer 130 . when used in a lan , computer 250 may be connected to the lan through network interface adapter 252 . computer 130 may be connected to the remote computer 250 via modem 254 when used in a wan , such as the internet . modem 240 , which may be internal or external to computer 130 , may connect to system bus 280 via a serial port interface ( not shown ). in a networked environment , some of the program modules depicted relative to computer 130 may be stored in a remote memory storage device . the network connections shown are exemplary and other means of establishing a communications link between the computers may be used . computer 130 comprises computer processor 260 that controls operation of computer 130 through data communications via processor i / o 261 to and from the associated elements over system bus 280 . operations of processors are well known , and will not be further detailed herein . in a preferred embodiment , a mimic is described to web browser 209 e as an html document that includes a javascript routine as described below in detail . in order to facilitate the implementation of mimics to a range of devices , a device mimic is typically composed of a plurality of separate sub - images . for instance , one embodiment of mimic 140 is illustrated in fig3 and 4 , as it appears on display 134 . a mimic is usually formed from many different sub - images . the different sub - images may be classified as either fixed ( invariant ) or status ( variant ). each status sub - image may indicate the status of a particular device status , say the statuses of port connections in the present example . a mimic usually comprises a variety of different status sub - images and fixed sub - images . since a device status may vary during normal device operation , a mimic displaying corresponding status sub - images should be altered as quickly as practicable . for example , a status sub - image may illustrate one particular ethernet port status . if there are twenty - four ethernet ports in a specific device , correspondingly , there might be twenty - four ethernet status sub - images . the same sub - image may be reused to generate each of the 24 status sub - images . other status sub - images may include console port sub - images , data transfer rate of a port , etc . fixed , or invariant , sub - images do not need to be updated , since they represent a characteristic of the device that does not change over time with normal device operation . fixed sub - images may be used to make the graphical representation of a mimic to a user . examples of fixed sub - images may include sub - image panels simulating device panels on a monitored device , advertising logos , and number sub - images corresponding to specific status sub - images . in fig3 and 4 , examples of fixed sub - images include the permanent labels : “ port status information ” and “ ethernet port status .” each of these fixed sub - images appears unchanged in mimic 140 regardless of updates . panel 310 in mimic 140 defines a large pixel area that remains constant regardless of status changes in monitored network device 104 . in addition , numerals “ 1 ” to “ 24 ”, which identify the associated ethernet port status sub - images , also do not change during the updating of mimic 140 , and thus are fixed sub - images . in addition , panel 310 in mimic 140 includes user activated poll - rate sub - image 311 . by clicking on poll - rate sub - image 311 a user can input a particular polling rate and , therefore , change the rate at which the ethernet port statuses are polled and sub - images 302 are refreshed . thus , a large portion of mimic 140 is formed from fixed sub - images . as such , a considerable amount of processing and refreshing time may be saved in accordance with the present invention by refreshing only portions of mimic 140 that represent the status sub - images corresponding to device characteristics that have a changed status since the last update , as opposed to regenerating the entire contents of mimic 140 . to render the refreshing of mimic 140 during status updates as quick and responsive as possible , it is desirable to limit the number of , and area of , status sub - images as much as practical . limiting the refreshing to only those status sub - images corresponding to device states that have changed since the last update is also desirable . status sub - images in fig3 and 4 include twenty - four bi - functional ethernet port status sub - images 302 . each ethernet port sub - image 302 includes two status sub - image portions : a sign sub - image portion 306 and a color ( striped ) sub - image portion 308 . the sign sub - image portion 306 and the color sub - image portion 308 function in the same manner for each ethernet port sub - image 302 . color sub - image portion 308 takes on one of two color values represented herein by the presence or absence of striping . color sub - image portions 308 indicate whether the associated ethernet port is enabled or not . in fig3 and 4 , a dark color , e . g ., striped , in sub - image portion 308 indicates that the associated ethernet port is not enabled , while a light color , e . g ., non - striped , in sub - image portion 308 indicates that the associated ethernet port is enabled . in fig3 for example , the dark - colored ( striped ) sub - image portion 308 numbered “ 13 ” corresponds to a device port that is not enabled . in fig4 the color sub - image numbered “ 13 ” corresponds to a device port that is enabled . in fig3 - 4 , sign sub - image portions 306 represent device state information , which indicates whether or not a link is connected to the corresponding port . a positive sign (+) in the sign sub - image portion 306 indicates that a link is connected to the corresponding device port ; a negative sign (−) in the sign sub - image portion 306 indicates that no link is connected to the corresponding device port . in fig3 for example , the sign sub - image for ethernet port 12 is a “−” indicating that no link is connected to the corresponding device port . in fig4 the sign sub - image for ethernet port 12 is a “+” indicating that a link is connected to the corresponding device port . a console port sub - image ( not shown ) may similarly indicate whether a corresponding device console port is active or not . accordingly , through the use of one of two color values ( striping ) and the use of either the “+” or “−” symbol , mimic 140 indicates the state of each port . the sign sub - image portion 306 and the color sub - image portion 308 , as depicted in fig3 - 4 , are illustrative and are not intended to be limiting in scope . for instance , sub - images appearing to be a link plugged into a port could indicate a link state , e . g ., whether or not the link is connected to a port in the corresponding monitored device . a check - mark sub - image could indicate an active port in the corresponding monitored device . in addition , a port may be represented by two distinct sub - images , e . g ., a first sub - image may indicate a link connected to the port and a second light may indicate that the port is active . the first sub - image might be on when the corresponding device port is active and off when the corresponding device port is inactive . the second sub - image might be on when a link is connected to the corresponding device port and off when no link is connected to the corresponding device port . any readily comprehensible mimic sub - image convention is within the scope of the present invention . mimic 140 , as illustrated in fig3 - 4 , provides status information relating to the monitored network device 104 . web browser screen 139 includes additional images and information that may be used to control the device . port setup portion 320 displays port status control sub - image 326 , which a user can activate to control network device 104 . a user can manually enable or disable a particular ethernet port in network device 104 by , e . g ., clicking on a corresponding button at the bottom of port setup portion 320 . in response , web browser 209 e transmits a request to network device 104 , which computer 111 executes , causing command data corresponding to the action suggested by the activated button in port setup portion 320 to be transmitted from monitoring system 118 to the monitored network device 104 via network connection 108 d . when command data are received by the monitored network device 104 , a processor portion of network device 104 processes the command data and responds by changing the state of the monitored network device 104 . a change in status of network device 104 is reflected by a change in a corresponding mimic sub - image 302 during the next update of sub - images 302 . other device states of the monitored network device 104 may also be interactively controlled via management system 102 . in the known prior art discussed above , a full mimic description is used to generate each new mimic , which entirely replaces a previously displayed mimic . as discussed above , the periodic generation of entire mimics to replace similar mimics usually places considerable processing demands on a monitoring system . in addition , transmitting an entire mimic description each time a mimic is to be updated can place considerable demands on such network resources as bandwidth . in accordance with the present invention , mimic updates are accomplished by generating , transmitting , and using sets of html files that contain device state information , e . g ., represented as a set of encoded values , as opposed to transmitting a description of an entire mimic . such mimic update files may be hidden files , i . e ., files the contents of which are not rendered directly visible to a user of the management system . the present invention also contemplates that mimic sub - images automatically update as a device status changes or at set periodic intervals without the need for intervention by a user of the management system . in accordance with the present invention , an html description of an entire mimic , including all of the status sub - images and all of the fixed sub - images , need only be generated at startup . thus , the fixed sub - images and the status sub - images ( which may subsequently be changed ) are generated to form the complete mimic image at startup . detected changes in the status , e . g ., state , of a monitored device , for example , if an active port becomes inactive or if a new link is connected to a port , are transmitted from a monitor to a management system using a relatively simple encoding scheme . the encoded state information is included in an html file that is transmitted to a management system . the html file containing the device state information will usually be substantially smaller than the html documents needed to describe a typical mimic , e . g ., less than one - twentieth or one - hundredth the size of a full mimic description . use of this mimic update approach can greatly reduce the amount of network traffic associated with mimic updates . the method of the present invention also reduces the computational burden on a typical monitoring system . the state information files , e . g ., hidden html files ( sometimes called hidden frames ), representing status updates are received by a web browser . the hidden html files containing device state information normally include javascript commands that initiate a mimic update operation . the mimic update operation may be implemented using a separate update routine included as part of the full device mimic description file used to create an original mimic . an update routine compares each new status , e . g ., state , value included in the received update state information with an existing status value associated or used to generate the existing mimic . if any new status value differs from a corresponding existing status value , the computer replaces the sub - image present in a mimic by a sub - image that accurately reflects the present state of the monitored devices or device . if no change in the state of the device is detected , the mimic is left unaltered . it is further noted that in a preferred embodiment , a management system and a monitoring device may be physically remote from each other . in addition , a monitored device may be physically remote from a monitoring system . some of the various functions of the present technique may be summarized as follows : a . tagging sub - images of a device mimic as either status sub - images , which can change , or fixed sub - images , which do not change . normally , status sub - images may be used to illustrate device state information . b . generating status update files including device state information . this function does not require generating a full html description of a mimic , and instead relies upon a simple encoding ( discussed below ) of device state or device - status information into a set of device state information which are included in a status update file . c . processing of an encoded status or state information by a management system to detect changes in device states . d . executing a javascript routine to allow sub - image replacement techniques to update portions of a mimic without having to regenerate an entire mimic . fig5 - 7 depict mimic monitoring process 500 in accordance with the present invention . in fig5 web browser 209 e ( see fig2 ) performs a portion of process 500 ( shown in the left side ), while remote - monitoring system 118 ( see fig1 ) performs the steps located in the right side . in general , when a web browser , e . g ., web browser 209 e , accesses an executable file , commonly known as a server script , from a web server , e . g ., monitoring system 118 , the web server executes the file program and returns its output to the web browser . upon executing a file program , the web server usually formats the output as an html document , commonly known as a script document . process 500 begins with browse step 501 , wherein a user of management system 102 initially activates web browser 209 e ( see fig2 ) to “ browse ” into network device 104 ( see fig1 ) for remote - monitoring purposes via the internet . in response , monitoring system 118 , which functions as a web server , fetches frame - set document 502 from mid 106 and , via return step 505 , transmits frame - set document 502 , typically an html document , to web browser 209 e . frame - set document 502 includes frame - format data 503 and frame - files data 504 . frame - format data 503 includes frame instructions that describe how web browser 209 e should divide screen 139 ( see fig3 - 4 ) into several rectangular regions , commonly known as frames . frame - files data 504 specifies the names and locations of executable frame files 524 located at monitoring system 118 that are capable of outputting html documents to be loaded into particular frames . thus , while frame - set document 502 controls the number and size of the frames of mimic 140 , it also informs web browser 209 e where to obtain the contents of each of these frames . in particular , frame - set document 502 divides web browser screen 139 into visible frame 207 a , and an invisible or hidden frame 207 b ( see fig3 ). while the contents of hidden frame 207 b are not visible in web browser screen 139 ( see fig3 and 4 ), the head of hidden frame 207 b can contain data . in addition , frame - set document 502 may define other conventional frames , such as a second visible frame that holds port setup portion 320 ( see fig3 - 4 ). details related to the processing and displaying of port setup portion 320 and other conventional frames are well known and , therefore , are not described further . thus , upon receiving frame - set document 502 , web browser 209 e performs frame - setup step 506 . in frame - setup step 506 , web browser 209 e initializes frames 207 a and 207 b , and allocates a specific graphic area in web browser screen 139 to be associated with visible frame 207 a . as described above , web browser 209 e will allocate no graphic area for hidden frame 207 b because there is nothing to display . in access step 507 , web browser 209 e essentially requests that monitoring system 118 execute frame files 504 and return specific frame - files data as , for example , a set of html documents . one such html document outputted by an execution of frame - files 504 is mimic document 509 , which is loaded into visible frame 207 a . specifically , when executing frame files 504 , a server script located in monitoring system 118 generates mimic document 509 , which includes mimic description data 510 in the form of an html description of network device 104 . mimic document 509 also includes the following javascript functions : poll - device function 511 , poll - rate function 512 , update function 513 and initialize function 514 . finally , the execution of frame - files 504 also produces null document 515 . monitoring system 118 returns mimic document 509 and null document 515 in return step 516 . null document 515 , an html document with a null body , contains files to be loaded into the head of hidden frame 207 b . it is noted that the use of null document 515 and , therefore , hidden frame 207 b is necessary to avoid potential sequencing errors . as will become apparent below , precise sequencing will ensure that mimic updates are not requested until after a mimic has been fully retrieved . after receiving mimic document 509 and null document 515 , web browser 209 e next renders these documents to produce device mimic 140 , via render step 517 . at this time , web browser 209 e displays an image of device mimic 140 that is similar to the image depicted in fig3 . however , at this point , monitoring system 118 has not yet informed web browser 209 e what the specific statuses are of the ethernet ports of network device 104 . thus , status sub - image 302 will not yet contain color sub - image portions 308 and sign sub - image portions 306 . instead , status sub - image 302 could contain a set of twenty - four gray boxes . after rendering documents 509 and 515 in render step 517 , web browser 209 e performs periodic updates of the status - sub - images 302 in update step 518 . [ 0073 ] fig6 and 7 show the details of render step 517 and update step 518 . in fig6 web browser 209 e performs the steps contained in the left side , while monitoring system 118 performs the steps located in the right side . the first step is to render null document 515 , which is trivial . since frame 207 b is invisible , there will be no place to display data from null document 515 . as such , null document 515 will have nothing to display and , therefore , will have no body . on the other hand , the head of null document 515 will contain a null value that web browser 209 e loads into the head of hidden frame 207 b , via load step 601 . next , web browser 209 e renders mimic document 509 . the body of mimic document 509 contains references to a number of images that web browser 209 e automatically requests from monitoring system 118 as a result of rendering mimic document 509 . these images relate to the many fixed and changeable sub - images appearing in panel 310 of device mimic 140 ( see fig3 and 4 ). thus , the process of rendering mimic document 509 includes the act of requesting these images from monitoring system 118 , via request step 602 . in response , monitoring system 118 performs execute step 603 , which involves executing the requested image files to produce a set of image documents that monitoring system 118 returns to web browser 209 e . web browser 209 e loads these documents into the body of mimic document 509 . using the received image documents , web browser 209 e displays device mimic 140 , in display step 604 . after web browser 209 e displays device mimic 140 , a script engine in web browser 209 e executes initialize function 514 via execute step 605 . this causes poll device function 511 to periodically execute via periodic - trigger step 606 . in the present example , an updating or polling period might be , for example , a thirty - second period , meaning that management system 102 would be polled to update the status of status sub - images 302 in mimic 140 every thirty seconds . in response to the execution of poll - device function 511 , via execute step 607 , web browser 209 e begins the process of retrieving the status of network device 104 from monitoring system 118 . initially , web browser 209 e loads into the head of hidden frame 207 b the name of a predetermined executable file located in mid 106 that , when executed , will retrieve and return the current status of network device 104 . in the present example , the value “ ex ” represents the name of that predetermined executable file located in mid 106 . thus , in load step 608 , web browser 209 e loads the value “ ex ” in the head of hidden frame 207 b causing the null value to change to the value “ ex .” web browser 209 e , responding to load step 608 , than performs request step 609 , which involves sending a message to monitoring system 118 to retrieve and execute file “ ex .” upon receiving the request , monitoring system 118 performs execute step 610 , which involves executing file “ ex ,” thereby obtaining the most - recent status of network device 104 . for instance , in execute step 610 , a javascript program that is part of file “ ex ” obtains the appropriate statuses of the twenty - four ports of network device 104 . that javascript program could do this by several means , including accessing a status look - up table stored in mid 106 . in this regard , monitoring system 118 could automatically maintain the status look - up table up - to - date by , for example , reading the current status of the twenty - four ports of network device 104 every second or so . the javascript program simply encodes each set of twenty - four port statuses into a status string of twenty - four characters , with each character representing the state of a corresponding port . each character string would then be loaded into a look - up table in mid 106 . a typical encoding process will now be described using the port - status examples depicted by sub - images 302 in fig3 and 4 . there are four possible states for each of the twenty - four sub - images numbered 1 - 24 . the four states may be encoded as : state 0 = port disabled / no link ; state 1 = port disabled / link present ; state 2 = port enabled / no link ; and state 3 = port enabled / link present . as discussed above , a dark colored ( stripped ) image corresponds to a disabled port and a light colored image corresponds to an enabled port . a positive sign (+) corresponds to a link present and a negative sign (−) corresponds to no link . thus , state 0 corresponds to a dark colored ( stripped ) image with a negative sign (−), such as shown in sub - image 2 in fig3 . state 1 corresponds to a dark colored ( stripped ) image with a positive sign (+), such as shown in sub - image 5 in fig3 . state 2 corresponds to a light colored image with a negative sign (−), such as shown in sub - image 3 in fig3 . finally , state 3 corresponds to a light colored image with a positive sign (+), such as shown in sub - image 1 in fig3 . using the above convention and the status example shown in fig3 the encoded states of the twenty - four ethernet ports would correspond to the following character string : “ 302312103030010301321021 .” on the other hand , the following character string : “ 303312103031210301321021 ,” would represent the state situation represented in fig4 . each of the twenty - four characters assumes one of only four different values , namely , 0 , 1 , 2 or 3 . from comparison of the two character strings , it can be seen that only the corresponding third , twelfth and thirteenth characters differ . as explained above , monitoring system 118 would periodically read the state of each port in network device 104 and encode those states into a character string similar to those just described with respect to fig3 - 4 . in addition , monitoring system 118 loads the character strings into a look - up table in mid 106 . in execute step 610 , a javascript program located in file “ ex ” would retrieve the most recently encoded character string from mid 106 and return the output data to web browser 209 e as part of update html document 630 , in send step 611 . the update document 630 would also contain a function call to update function 513 , which was previously loaded into the head of visible frame 207 a in render step 517 . web browser 209 e loads , in load step 612 , update document 630 into the head of hidden frame 207 b . web browser 209 e then renders update document 630 , via render step 613 . since update document 630 has no body , there will be nothing for web browser 209 e to display . thus , in render step 613 , web browser 209 e need only execute the script located in the head of update document 630 , which invokes a function call to update function 513 . when update function 513 executes , in execute step 614 , it accepts as a parameter the character string , which was part of update document 630 , as being a new device status . using that new device status as a parameter , in update step 615 , web browser 209 e updates the twenty - four statuses in status sub - images 302 . after the update is complete , the process returns to periodic - trigger step 606 where the update cycle repeats . [ 0083 ] fig7 illustrates the details of a process of updating the states of status sub - images 302 in update step 615 . in compare step 701 , web browser 209 e compares the old status to the new status . if , in decision step 702 , web browser 209 e finds that the old status equals the new status , signifying that there has been no change in the states of the ethernet ports since the last update , the process exits the “ y ” path of step 702 and returns to periodic trigger step 606 . if , however , web browser 209 e finds that the old status does not equal the new status , the process exits the “ n ” path of step 702 and makes a character - by - character comparison to find where the differences occur . that process begins in step 703 by initializing an index “ i ” to the value one ( 1 ), and a constant “ n ” to the value twenty - four ( 24 ). the index “ i ,” which varies from one to twenty - four , points to the twenty - four different sub - images 302 . the constant “ n ” represents the total number of sub - images 302 . in compare step 704 , web browser 209 e compares the corresponding characters numbered “ i ” in those character strings representing the new status and the old status . for example , since “ i ” will initially have a value one ( 1 ), the first characters in the new and old status strings are compared . for purposes of illustration , assume that the twenty - four states depicted in fig3 represent an old status , and that those depicted in fig4 represent a corresponding new status as follows : thus , when “ i ” equals one ( 1 ), web browser 209 e will find , in decision step 705 , that the first characters are both “ 3 ” and , therefore , are equal to each other . thus , the process exits the “ y ” path of step 705 to decision step 706 . in decision step 706 , the index “ i ” is compared to the constant “ n .” in the present example , “ i ” equals one and “ n ” equals 24 . since at this point “ i ” does not equal “ n ,” the process exits the “ n ” path of step 706 to increment step 707 , where “ i ” is set equal to “ i + 1 .” with “ i ” now equal to two ( 2 ), the corresponding second characters are compared , in compare step 704 . since the second characters both equal “ 0 ,” the process advances to increment step 707 via the “ y ” path of step 705 and the “ n ” path of step 706 . index “ i ” is now incremented to three ( 3 ) in step 707 , causing comparison of the corresponding third characters , in compare step 704 . since the corresponding third characters are unequal ( the old equals two and the new equals three ), the process will exit the “ n ” path of decision step 705 . next , the web browser 209 e proceeds to a process of replacing the image of the third status sub - image , i . e ., the sub - image numbered 3 in fig3 - 4 , to reflect the new state of the corresponding ethernet port . specifically , web browser 209 e replaces the negative sign (−) in the third status - sub - image 302 with a positive sign (+) ( see fig3 - 4 ). to effect this change , web browser 209 e first changes the source ( src ) attribute for status sub - image “ i ,” where “ i ” equals three ( 3 ). specifically , assume that the src attribute has the following format : & lt ; ip address & gt ; is the internet protocol address of monitoring system 118 ; & lt ; directory path & gt ; is a path to the image &# 39 ; s directory in mid 106 ; & lt ; name & gt ; is an arbitrary symbolic or descriptive name of a particular image ; gif is a file extension that identifies a particular commercial bit map image format . since , in the present case , only the state of the image has changed , only the numeric code corresponding to the state in src attribute needs to be changed . with respect to the corresponding third characters , the old state is represented by the character “ 2 ” and the new state is represented by the character “ 3 .” consequently , the corresponding src attributes are as follows : web browser 209 e now retrieves the appropriate image data for updating the corresponding third sub - image 302 in mimic 140 . using the new src attribute ( shown above ) in retrieve step 711 , web browser 209 e first looks in a cache memory to see if the corresponding image data had recently been downloaded from the network so that the image data can be redisplayed quickly in update step 712 . if the appropriate image data is not located in cache memory , web browser 209 e accesses the appropriate image data from monitoring system 118 . in either case , web browser 209 e uses the new src attribute to obtain the image data corresponding to the new state . in the present example , web browser 209 e , in update step 712 , displays the new image ( a light color with a positive sign ) for the third status sub - image 302 to reflect the new state of the corresponding ethernet port . the process then proceeds to decision step 706 , where index “ i ” is compared to constant “ n .” the process continues as described above , changing only those status sub - images 302 that have a new state . in the present example , in addition to changing the third status sub - image , status sub - images 12 and 13 will be the only other sub - images that need to be changed . finally , when web browser 209 e finds “ i ” to be equal to 24 in decision step 706 , the process exits the “ y ” path , thereby returning to periodic trigger step 606 . while the process of updating a displayed mimic has generally been described as being performed in response to an update request generated by management system 102 , it is to be understood that such updates may be initiated by monitoring system 118 . indeed , those update requests that monitoring system 118 initiates may take place only when an actual change in state of an ethernet port occurs . for example , after the initial generation and display of device mimic 140 , management system 102 may generate a hidden frame of the type discussed above and transmit it each time the monitoring system detects that a change in the state of the monitored device has occurred . management system 102 would update the displayed mimic 140 in the manner discussed above when responding to the reception of a hidden frame that included a set of device state information and an appropriate javascript program . in addition , it is to be understood that device mimic 140 can be output to a printer in addition to , or instead of , being displayed on display device 134 . obviously many other modifications and variations of the present invention are possible in the light of the above teachings . it is therefore to be understood , that within the scope of the appended claims , the invention may be practiced otherwise than as specifically described .