n the topology database, updating the inventory database (if any), and so on. Once configuration or rollback has been carried out, the attribute passed is checked for the presence of the managed object name. If present, then that managed object will be updated with the current configuration details. If the attribute has no managed object name, then the managed object name of the device will be taken and updated to synchronise the topology database. User-implemented updates can be plugged in to the database by implementing a particular interface. 11 Configuration Management 11.2.9 Debugging CMS is equipped with debugging facilities, which give details such as the username, the task executed and the time of operation. Debugging levels can be defined such that if "1" is given, then only the CMS-related debug will be switched on. If the input is "2", then more detailed debugging information will be switched on. 11.2.10 Trivial File Transfer Protocol - TFTP TFTP is a forerunner protocol of File Transfer Protocol (FTP). The TFTP protocol is used to transfer information in both directions between a client and its server. TFTP is intended to be used when bootstrapping diskless systems are used. Devices with- out memory, such as routers and switches, also use TFTP in order to obtain boot- strap information from their servers. TFTP protocol uses UDP for transferring files between server and the client, and by default uses port "69" to transfer data. When TFTP is used, the file that is being transferred is split into packets, each containing 512 bytes of data. The completion of the transfer is intimated to the receiver by sending a packet that has 0-511 bytes. The mode is one of the ASCII strings netascii or octet, in any combination of upper- case or lowercase, terminated by a byte of 0. The denotation "netascii" means that the data are lines of ASCII text with each line terminated by the two-character sequence of a carriage return followed by a linefeed, called CR/LF. Both ends must convert data from this format to the fo