Teldat Router Configuration and Monitoring Doc. DM704-IRev. 10.97 February, 2014 - ii - I NDEX Chapter 1 Teldat Router Console .................................................................................... 1 1.Introduction ........................................................................................................................ 2 2.Local and remote terminal .................................................................................................. 3 3.User interface ..................................................................................................................... 4 3.1.Teldat Router connection ........................................................................................ 4 3.2.Executing a command ............................................................................................. 7 3.3.User Interface Processes ......................................................................................... 7 3.4.Accessing the processes .......................................................................................... 9 3.5.Returning to the Console Manager.......................................................................... 9 3.6.Obtaining help ......................................................................................................... 10 4.GESTCON process commands .......................................................................................... 11 4.1.MONITOR .............................................................................................................. 11 4.2.CONFIG .................................................................................................................. 11 4.3.RUNNING-CONFIG .............................................................................................. 12 4.4.FLUSH .................................................................................................................... 12 4.5.INTERCEPT ........................................................................................................... 12 4.6.LOAD ..................................................................................................................... 12 4.7.LOGOUT ................................................................................................................ 14 4.8.PROCESS ............................................................................................................... 14 4.9.STATUS ................................................................................................................. 15 4.10.RESTART ............................................................................................................... 15 4.11.TELNET ................................................................................................................. 15 4.12.VRF-TELNET ........................................................................................................ 17 Chapter 2 Teldat Router Configuration .......................................................................... 18 1.Introduction ........................................................................................................................ 19 2.Configuration Process ........................................................................................................ 23 3.Configuration procedure user interface .............................................................................. 24 4.Configuration commands ................................................................................................... 30 4.1.ADD ........................................................................................................................ 30 4.2.AUTOINSTALL ..................................................................................................... 31 4.3.BACKUP-FILES .................................................................................................... 32 4.4.BANNER ................................................................................................................ 33 4.5.CONFIG-MEDIA ................................................................................................... 35 4.6.CONFIRM-CFG ..................................................................................................... 37 4.7.CONFIRM-CFG-NEEDED .................................................................................... 37 4.8.COPY ...................................................................................................................... 40 4.9.DESCRIPTION ....................................................................................................... 40 4.10.DISABLE ................................................................................................................ 40 4.11.DUMP-COMMAND-ERRORS .............................................................................. 41 4.12.ENABLE ................................................................................................................. 41 4.13.EVENT ................................................................................................................... 42 4.14.FEATURE............................................................................................................... 42 4.15.FILE ........................................................................................................................ 53 4.16.FIRMWARE-CHECKING ..................................................................................... 58 4.17.FORMAT ................................................................................................................ 59 4.18.GLOBAL-PROFILES ............................................................................................. 59 4.19.LICENCE-CHANGE .............................................................................................. 60 4.20.LIST ........................................................................................................................ 61 4.21.LOG-COMMAND-ERROR ................................................................................... 63 4.22.MANAGEMENT .................................................................................................... 63 4.23.NETWORK............................................................................................................. 64 4.24.NO ........................................................................................................................... 64 4.25.NODE ..................................................................................................................... 68 - iii - 4.26.PRIVILEGE ............................................................................................................ 69 4.27.PROTOCOL ........................................................................................................... 73 4.28.QUICK CONFIGURATION .................................................................................. 74 4.29.SAVE ...................................................................................................................... 74 4.30.SET ......................................................................................................................... 75 4.31.TELEPHONY ......................................................................................................... 86 4.32.TIME ....................................................................................................................... 87 4.33.UCI.......................................................................................................................... 93 4.34.UNSET-DEMO-LICENSE ..................................................................................... 93 4.35.USER ...................................................................................................................... 94 4.36.END ........................................................................................................................ 97 Chapter 3 Teldat Router Monitoring .............................................................................. 99 1.Introduction ........................................................................................................................ 100 2.Monitoring procedure commands ...................................................................................... 101 2.1.? (HELP) ................................................................................................................. 102 2.2.BUFFER ................................................................................................................. 102 2.3.CLEAR ................................................................................................................... 104 2.4.CONFIGURATION ................................................................................................ 104 2.5.DEVICE .................................................................................................................. 107 2.6.ERROR ................................................................................................................... 108 2.7.EVENT ................................................................................................................... 108 2.8.FEATURE............................................................................................................... 109 2.9.LAST-CONFIG-CHANGES .................................................................................. 116 2.10.MALLOC-MONITOR ............................................................................................ 116 2.11.MANAGEMENT .................................................................................................... 117 2.12.MEMORY............................................................................................................... 117 2.13.NETWORK............................................................................................................. 118 2.14.NODE commands ................................................................................................... 118 2.15.PROTOCOL ........................................................................................................... 119 2.16.QUEUE ................................................................................................................... 120 2.17.QUICK .................................................................................................................... 121 2.18.STATISTICS .......................................................................................................... 121 2.19.SYSTEM ................................................................................................................. 122 2.20.TFTP ....................................................................................................................... 136 2.21.TELEPHONY ......................................................................................................... 136 2.22.UCI.......................................................................................................................... 136 2.23.WEB-PROBE ......................................................................................................... 137 2.24.LOG ........................................................................................................................ 137 Chapter 4 Event Logging System ELS ............................................................................ 138 1.Introduction ........................................................................................................................ 139 2.Event Logging System ....................................................................................................... 140 3.Event Logging System user interface ................................................................................. 147 4.Event Logging System Commands .................................................................................... 152 4.1.Configuration Process Commands .......................................................................... 152 4.2.Monitoring process commands ............................................................................... 172 5.Supported personalized parameters .................................................................................... 183 Chapt er1 Tel datRout erConsol e TELDAT ROUTER - The Console I - 2 Doc.DM704-I Rev.10.97 1.I nt r oduc t i on All TeldatRouterdevices employ the same user interface for every model.They only differ on the protocol software loaded in each device. The information contained in this chapter is divided in the following sections: Local and remote terminal. User interface. User interface description. GESTCON process commands. TELDAT ROUTER - The Console I - 3 Doc.DM704-I Rev.10.97 2.Loc aland r emot e t er mi nalThe TeldatRouterallows user access for configuration and monitoring functions through a local or remote terminal. Loc alTer mi nalA local terminal is directly connected to the TeldatRouterthrough an RS-232 serial cable. For further information see the Device Installation Manual. Remot e Ter mi nalThe remote connections provide the same functionality as the local ones, except that a local terminal must be used for the initial configuration. The remote terminals are connected to the TeldatRouterthrough TELNET once the IP protocol has been enabled.See TCP-IPConfigurationManual (Dm702-I) for further information on how to enable the IP protocol. By means of local or remote terminal it is possible to access the Teldat Router and carry out the distinct processes.Theseprocessesarerelatedtodeviceconfigurationwithstatusmonitoringandrelated statistics.Messages can also be received on any events produced.These processes are named as follows: P 1 (GESTCON):This is the console management process (GESTCON).This is the starting point on booting a console session and that accesses other processes. P 2 (VISEVEN):Thisprocessallowseventsproducedinthesystemtobedisplayed,from establishedconnectionstoerrorsinthesystem(VISEVEN).Theseevents shouldbepre-configuredeitherinprocess4(CONFIG)orinprocess3 (MONITOR)throughtheEventLoggingSystem.SeeChapter4Event Logging System ELS for further information. P 3 (MONITOR):This permits you to MONITOR the state of the system as well as the statistics gathered by the device. P 4 (CONFIG):This process permits you to edit all the configuration parameters.From this processyoucangenerateacompleteconfigurationforthedevicewithout altering the operation procedure.In order to activate this configuration, you need to save it in the file system and restart the device. P 5 (RUNNING-CONFIG):Thisistheprocessthroughwhichchangesinthedevices active configuration are affected.The configuration changes executed from this process take immediate effect, however if it is not saved in the file system, it will be lost on rebooting the device. These processes are accessed from the console by striking the keys P 2, P 3 P 4 or P 5. TELDAT ROUTER - The Console I - 4 Doc.DM704-I Rev.10.97 3.Useri nt er f ac e The following steps are the same for all Teldat Router, regardless the software installed. Teldat Router connection. Executing a command. User interface processes. Accessing the process. Return to the Console Manager. Obtaining help. 3.1.Tel datRout erc onnec t i on You can establish console sessions with the device both locally through serial port RS-232 and also remotely through a TELNET session.The following paragraphs explain both methods of accessing the device. Loc alConnec t i on During device booting, information will be displayed to the user on the configuration of the device hardware and software and the system startup progress.Once this booting stage has completed, the user is asked to initiate a session by pressing any key. A user and password control the access to the router local connection.By default no user is registered.In this case it will not be requested when you access the device and the first thing to appear is the welcome text and the console management prompt as shown below. Tel dat ( c) 2001- 2002 Rout er model XXXXXCPUMPC860S/ N: YYYY/ YYYYY 1LAN, 2WANLi ne, 2I SDNLi ne CI Tsof t war ever si on: ZZZZZ * where XXXXX is the specific router model. Inordertoregisterauser,pleaseseetheusercommandinChapter2TeldatRouter Configuration.Incaseswherethereareenabledusers,theintroductionofauserandthe corresponding password will be requested.If the authentication is accepted, then the welcome text will be shown. User : RootPasswor d: **** Tel dat ( c) 2001- 2002 Rout er model XXXXXCPUMPC860S/ N: YYYY/ YYYYY 1LAN, 2WANLi ne, 2I SDNLi ne CI Tsof t war ever si on: ZZZZZ * TELDAT ROUTER - The Console I - 5 Doc.DM704-I Rev.10.97 where XXXXX is the specific router model, YYYY/YYYY the unit serial number and ZZZZ the CIT code release currently running. If the password is not valid, the following text will appear: User : RootPasswor d: ****** Accessdeni ed If the password is incorrectly introduced, you will not be able to access the console.If you exhaust the maximum number of erroneous attempts, the application will block for one minute. If you have been authenticated in the system and an inactive period of time has also been configured (see the set command in Chapter 2 Teldat Router Configuration"), a monitoring process will begin.If the configured inactive time period times out without the user touching any of the keys, the local connection will close.In this case the user must reenter the password again when he wishes to use the console. Depending on the user you have authenticated with, you have permission when accessing the different processes and executing some restricted commands. The user access level is specified with a value between 0 and 15 and a mode, default or strict. Five different predetermined access levels have been defined in the default mode: NONE [0]:System access is not permitted. EVENTS [1]: Access is permitted to the Console Management (P1), to the Events Viewing (P2) but you cannot execute the Ping, Telnet, Restart or Load commands. MONITOR [5]:Access is permitted to the Console Management (P1), to the Events Viewing (P2) and the Monitoring process (P3).You are also permitted to execute the Ping and Telnet commands but not the Restart or Load commands. CONFIG [10]:Access is permitted for all the process and all the standard commands. ROOT [15]:In addition to being able to access all the processes and the standard commands, you canalsoaccesstheusermanagementowncommands.Thesewillbeexplained further on in this manual. You must save the configuration (see the save command in Chapter 2) if you wish to maintain the users registered on restarting the device as contrariwise you lose the said user configuration. Theusercommandmanagestheusersandpermitsthefollowingactions:add,delete,enableand disable users, list and change the user access level: user namepassword password: Configures a user password, creating it if it does not exist. no user name: Deletes a user from the user list.You can eliminate as many users as you wish except if there is only one Root user and there are other registered users.In this case, you can only delete the rest of the users as if not you cannot manage the remaining users.If you eliminate all the users except the last Root, then you can delete the latter.The system then will not request user and password in order to access the device, as there are no more users registered in the system. user nameactive: TELDAT ROUTER - The Console I - 6 Doc.DM704-I Rev.10.97 Permits you to enable users.Simply indicate the user name you wish to enable. user name no active: Permits you to disable users.You cannot disable Root users. list user: Displays a list of registered users, their access level and if they are enabled or not. Permits you to change the access level of any registered user with the exception of users with Root access level. For further information on the user command, please see the explanation given in Chapter 2. The user management is compatible with the password defined through the set password command.Therefore if you update a device that has this password enabled, this will continue to permit access using this password while not registering any user. The user management has priority over the device password; therefore when there are registered and enabled users (these are enabled by default when they are registered) the old password will no longer be valid. Remot e c onnec t i on To connect to TeldatRouterinitializing a TELNET session in the host (the host being the system connected to the remote terminal), you need the IP address of the device you wish to connect to. Example: t el net 128. 185. 132. 43 TheTeldat Router acts as a TELNET server. The remote terminal acts as aTELNET client. Once a TELNET session is established with the Teldat Router, if necessary, a user and password will be requested in order to access the system.Once correctly authenticated in the system, the following welcome text will appear. User : RootPasswor d: **** Tel dat ( c) 2001- 2002 Rout er model XXXXXCPUMPC860S/ N: YYYY/ YYYYY 1LAN, 2WANLi ne, 2I SDNLi ne CI Tsof t war ever si on: ZZZZZ * where XXXXX is the specific router model, YYYY/YYYY the unit serial number and ZZZZ the CIT code release currently running. The access control to the Teldat Router is similar to the local mode access.If there are users defined and these are enabled (these enable by default when created), the introduction of a user and their corresponding password is requested in order to connect to the system.When the authentication is correct,thewelcometextandpromptappearandyouhaveaccesstotheauthenticateduser permissions as indicated in the connection via local. If the password is not valid, the following text will be displayed: TELDAT ROUTER - The Console I - 7 Doc.DM704-I Rev.10.97 User : RootPasswor d: ****** Accessdeni ed If the password is not entered within approximately 20 seconds or the password provided is incorrect, at the third attempt the device will disconnect the TELNET session. 3.2.Ex ec ut i ng a c ommand To enter a command, simply enter the necessary letters that differentiate one command from another within the menu you are working in. Example: Within the menu containing the following commands: user upload down Ifyoukeyinau,anerrorwillbeproduced indicatingthatyouhave introduced anambiguous command (both user and upload begin with a u).If you introduce a d, do, dow or down, this command will be executed.In the same way if you introduce us, use or user, this command will execute and similarly up, upl, uplo, uploa or upload will execute the upload command.Any other entry will produce an error, as no command will coincide with the characters entered. To delete the last character(s) from the command line use the backspace () key. 3.3.UserI nt er f ac e Pr oc esses Theuserinterfaceismadeupofvariousprocesseswhichcanbeaccessedthroughtheconsole sessions. The processes normally handled are: GESTCON, MONITOR, CONFIG, RUNNING-CONFIG and VISEVEN.The following diagram describes the structure of the processes in the Teldat Router. As shown in the figure, each process has a different prompt.You can find out which process you are in by checking the prompt. The following list shows the prompts for the different processes: ProcessPrompt GESTCON* MONITOR+ CONFIGConfig>RUNNING-CONFIGConfig$ TELDAT ROUTER - The Console I - 8 Doc.DM704-I Rev.10.97 GESTCON*RUNNING-CONFIGConfig$CONFIGConfig>MONITOR+VISEVENprocess 5process 4process 3process 2 TheTeldatRouteroffersthepossibilityofpersonalizingthedevice,includingatextbeforethe prompt. This text can contain a maximum of 8 characters and takes the name assigned to the device.To introduce the text, please see the configuration command set hostname. Each of these processes is described below: GESTCON Pr oc ess This is the Console Manager; its task is to simplify access to the rest of the processes on the console. MONI TOR Pr oc ess Allows the user to monitor the status and statistics of the router hardware and software.Provides access to the protocol and interface menus which in turn, allow the user to monitor the configured protocols and other parameters. CONFI G Pr oc ess Enables configuration of various parameters such as net addresses and events.Provides access to the configuration of protocols thus permitting protocol parameter configuration.You can carry out the whole of the device configuration from this process; however it will not activate until you have saved it and rebooted the device.This process is used to edit the device boot up configuration. TELDAT ROUTER - The Console I - 9 Doc.DM704-I Rev.10.97 RUNNI NG-CONFI G Pr oc ess Provides access to configure the interfaces, protocols, etc.All parameters configured through this process take immediate effect, however if not saved, they will be lost when the device is restarted.This process serves to dynamically modify the devices active configuration. VI SEVEN Pr oc ess Receives messages from the Events Logging System and displays them at the terminal in accordance with the user selection criterion. 3.4.Ac c essi ng t he pr oc esses Prompt * will appear once the session has initiated. Prompt * is the Console Manager prompt. From thisprompt it ispossible toaccess thedistinctprocess.Promptsare thesymbols thatidentifyeach process: To access a process, the following steps must be executed: 1.Look for the number that identifies the process. This information can be obtained by entering the status command at the * prompt. 2.Enter process pid, where pid is the process number we wish to access. For example, to configure Teldat Router, enter *pr ocess4 User Conf i gur at i on Conf i g>Themostcommonprocesseshowevercanbeaccessedthroughspecificcommands.Theseare displayed in the following table. CommandProcess monitorProcess 2: monitoring configProcess 4: startup configuration editor running-configProcess 5: active configuration 3.5.Ret ur ni ng t o t he Consol e ManagerTo return to the Console Manager (prompt *) from a process, e.g. CONFIG (prompt Config>) or MONITOR (prompt +), enterCtrl+p (the escapecharacter).ALWAYSRETURNTOTHE CONSOLEMANAGERBEFOREENTERINGANOTHERPROCESS. For example if you are in MONITOR and wish to enter CONFIG, enter Ctrl + p and return to prompt * before doing so. To end a TELNET session initiated from the Teldat Router toward another device, you can use the Ctrl +s escape character.This escape character forces the TELNET session, started by the Teldat Router, to close. The Ctrl. + p escape character is used to return to the console Manager, while the Ctrl. + s escape character is used to end a TELNET session. Example: *conf i g User Conf i gur at i on Conf i g> Press (Ctrl +p) * TELDAT ROUTER - The Console I - 10 Doc.DM704-I Rev.10.97 *moni t orConsol eOper at or+ Press (Ctrl +p) * Other protocol configuration/monitoring menus can be accessed from the configuration or monitoring processes. Returning to the corresponding process is achieved through the EXIT command and to the Console Manager via the escape character (Ctrl + p by default). 3.6.Obt ai ni ng hel p In all processes there is a command ? (HELP).This gives information on the commands that can be used with the prompt, not only in the Console Manager (*), but also in the configuration (Config> and Config$) and monitoring (+) processes. Youcanalsoenteran?afteranycommandtoobtainalistofoptionspermittedinthesaid command. You can also terminate a command or an option with an ? to get a list of commands or options which match that written.The tabulation key can also be used to automatically complete a command or option which is already completely determined. Example: Conf i g>pr ot ocol ? ar pAccessARPpr ot ocol conf i gur at i on asr t AccessASRTpr ot ocol conf i gur at i on bgpAccessBGPpr ot ocol conf i gur at i on depAccessDEPpr ot ocol conf i gur at i on dhcpAccessDHCPpr ot ocol conf i gur at i on dl sAccessDLSpr ot ocol conf i gur at i on h323AccessH323pr ot ocol conf i gur at i on i pAccessI Ppr ot ocol conf i gur at i on l 2t pAccessL2TPpr ot ocol conf i gur at i on noeAccessNOEpr ot ocol conf i gur at i on ospf AccessOSPFpr ot ocol conf i gur at i on r i pAccessRI Ppr ot ocol conf i gur at i on si pAccessSI Ppr ot ocol conf i gur at i on snmpAccessSNMPpr ot ocol conf i gur at i on Conf i g>pr ot ocol a? ar pAccessARPpr ot ocol conf i gur at i on asr t AccessASRTpr ot ocol conf i gur at i on Conf i g>pr ot ocol a TELDAT ROUTER - The Console I - 11 Doc.DM704-I Rev.10.97 4.GESTCON pr oc ess c ommands The GESTCON process (P1) allows you to configure and monitor all the device operation parameters. During the GESTCON process, the Teldat Router processes and transfers data traffic. When the device is switched on and enters the GESTCON process the copyright, information on the device, together with an asterisk * appear at the connected local terminal. This asterisk * is the prompt for GESTCON process which is the main user interface permitting access to all other processes. Most changes made in the TeldatRouteroperation parameters in the GESTCON process have an immediate effect i.e. it is unnecessary to restart the device. From the GESTCON process it is possible to access a set of commands that permit you to check the status oftheprocesses,monitorthedeviceinterfaceandpackettransferenceefficiency,aswellasthe configuration of various parameters. GESTCON pr oc ess c ommands t abl e CommandsFunction MONITORAccesses the monitoring process. CONFIGAccesses the startup configuration editing process.RUNNING-CONFIGAccesses the active configuration editing process. FLUSHClears all the messages stored up to that moment in the events buffer. INTERCEPTPermits you to change the procedures escape character. LOADReloads the application from the flash memory LOGOUTEnds the Telnet connection established with the device. PROCESSPermits access to a different device procedure and to enable its commands. RESTARTAllows you to restart the device rereading the configuration. STATUSDisplays the names and identifiers of each process. RESTARTAllows you to restart the device. TELNET EstablishesaTelnetconnectionastheremotedeviceclientwhoseremote address is specified. VRF-TELNET Establishes a Telnet connection as client for the remote device whose address is specified in the indicated VRF. 4.1.MONI TOR Accesses the monitoring process. Syntax: *moni t orExample: *moni t orConsol eOper at or+4.2.CONFI G Accesses the startup configuration editing process. TELDAT ROUTER - The Console I - 12 Doc.DM704-I Rev.10.97 Syntax: *conf i g Example: *conf i g Conf i g>4.3.RUNNI NG-CONFI G Accesses the active configuration editing process. Syntax: *r unni ng- conf i g Example: *r unni ng- conf i g Conf i g$ 4.4.FLUSH Deletes all the current events messages from the VISEVEN procedure output buffer. Syntax: *f l ush Example: *f l ush * 4.5.I NTERCEPT Allows you to change the processes escape character. In the below example the default character given is changed, (Ctrl+u) in place of (Ctrl+p). Syntax: *i nt er ceptExample: *i nt er ceptPr esst henew escapekeyandt henEnt er : Press (Ctrl+u) and Pr esst henew escapekeyagai nandt henent er : Press (Ctrl+u) and Escapekeyupdat ed * The escape key should not be a character that can be displayed. 4.6.LOAD Allows you to load the program from flash memory. TELDAT ROUTER - The Console I - 13 Doc.DM704-I Rev.10.97 Syntax: *l oad ACTI VATE DEACTI VATE I MMEDI ATE RACTI VATE RDEACTI VATE specifies the load type you want to execute. a) LOAD ACTI VATE Theactivateoptionallowstheusertoprogramaspecifictimetoreloadtheroutingapplication program.The time is configured in a 24-hour format. Syntax: *l oadact i vat e Example: *l oadact i vat e17: 21 Ar eyousur et or el oadt hesyst emat t heconf i gur edt i me( Yes/ No) ?y * b) LOAD DEACTI VATE The deactivate option allows you to cancel a pre-configured loading which has not as yet been carried out.If no loading has been programmed, then an error message will appear. Syntax: *l oaddeact i vat e Example: *l oaddeact i vat e Rel oadi st i medat 20: 00 Ar eyousur et ocancel t het i medr el oad( Yes/ No) ?y Ti medr el oadwascancel l ed * c ) LOAD I MMEDI ATE The immediate option reloads the application immediately. Syntax: *l oadi mmedi at e Example: *l oadi mmedi at e Ar eyousur et or el oadt hedevi ce( Yes/ No) ?y * d) LOAD RACTI VATE Permits the user to program a specific time where the routing application program restarts.The time is configured in a 24-hour format. Syntax: *l oadr act i vat e TELDAT ROUTER - The Console I - 14 Doc.DM704-I Rev.10.97 Example: *l oadr act i vat e17: 26 Ar eyousur et or est ar t t hesyst emat t heconf i gur edt i me( Yes/ No) ?y * e) LOAD RDEACTI VATE Permits you to deactivate the programmed restart process.If there is no restart programmed, an error message will appear. Syntax: *l oadr deact i vat e Example: *l oadr deact i vat e Rel oadi st i medat 17: 00 Ar eyousur et ocancel t het i medr est ar t ( Yes/ No) ?y Ti medr est ar t wascancel l ed * 4.7.LOGOUT Ends the Telnet connection established with the device without using a Telnet client command. Syntax: *l ogoutExample: *l ogoutDoyouwi sht oendt el net connect i on( Yes/ No) ? 4.8.PROCESS This permits access to another device process e.g. MONITOR, VISEVEN, or CONFIG. Once a new process has been accessed, it is possible to send specific commands or receive the process output. To obtain the process identifier enter the status command. Once connected to another process, such as MONITOR,VISEVEN,orCONFIG,usetheescapecharacter(Ctrl+p)inordertoreturntothe Console Manager (GESTCON). Syntax: *pr ocess this is the process identifier number whose console we wish to access. Example: *pr ocess4 User Conf i gur at i on Conf i g> When in one of the protocol menus such as Conf IP> or IP>, use the exit command in order to return to the menu of the process you are currently in. TELDAT ROUTER - The Console I - 15 Doc.DM704-I Rev.10.97 4.9.STATUS Permits you to know each process identifier (pid), as well as the name. Syntax: *st at us Example: *st at us Syst emPr ocesses:PI DNAME 1Mai nconsol e 2Event vi ewer3Moni t or consol e 4Conf i gconsol e 5Runni ngconf i gconsol e 6Tel net cl i ent* 4.10.RESTART Restarts Teldat Router without reloading the software. This has the following effects: Software counters are set to zero. Connected networks are tested. Routing tables are cleared. All packets are discarded until the restart has completed. Current software is executed. If this command is used during a remote terminal connection, the TELNET session will be lost since all the device procedures will be restarted. Syntax: *r est ar tExample: *r est ar tAr eyousur et or est ar t t hesyst em( Yes/ No) ?y Done Rest ar t i ng. Pl easewai t . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .APPDATADUMP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Runni ngappl i cat i on Fl ashconf i gur at i onr ead Par si ngt ext modeconf i gur at i on. . .Conf i gur at i onpar sed I ni t i al i zi ng Pr essanykeyt oget st ar t ed 4.11.TELNET Establishes a Telnet connection as the remote device client with a specified address.This address can be a domain name in cases where the DNS client has been configured. TELDAT ROUTER - The Console I - 16 Doc.DM704-I Rev.10.97 Syntax: *t el net [ sour ce | por t | ]vr f

You can specify the VRF through the vrf option when you want to start the telnet session.In cases where this option is not used, the main VRF is used. Incaseswherenoparametersareentered(telnetoption),youareaskedforallthetelnet parameters taking the main VRF as the VRF. The parameters you can specify in Telnet are: specifies the IP address or the device domain name which you wish to access via telnet. source specifies the source IP address to use for Telnet port specifies the destination port to use for Telnet Examples: Telnet to the device with address 172.123.23.67: *t el net 176. 123. 23. 67 Tr yi ngt oconnect . . .( Pr essCont r ol St ocomebackt ol ocal r out er )Connect i onest abl i shed Telnet to device 172.24.78.92 using source address 80.1.1.1 and port 6623. FTP*t el netTel net dest i nat i on[ ] ?172. 24. 78. 92 Tel net sour ce[ 172. 24. 78. 94] ?80. 1. 1. 1 Tel net por t [ 23] ?6623 Tr yi ngt oconnect . . .( Pr essCont r ol St ocomebackt ol ocal r out er )Connect i onest abl i shed Telnet to device 172.24.78.92 using source address 80.1.1.1and port 6623, specifying the parameters with options. FTP*t el net 172. 24. 78. 92sour ce80. 1. 1. 1por t 6623 Tr yi ngt oconnect . . .( Pr essCont r ol St ocomebackt ol ocal r out er )Connect i onest abl i shed Telnet to device with domain name router1.midominio.es: FTP*t el net r out er 1. mi domi ni o. es Tr yi ngt oconnect . . .( Pr essCont r ol St ocomebackt ol ocal r out er )Connect i onest abl i shed Telnet to device 172.24.78.92 using the router_aux VRF. FTP*t el net vr f r out er _aux172. 24. 78. 92 Tr yi ngt oconnect . . .( Pr essCont r ol St ocomebackt ol ocal r out er )Connect i onest abl i shed TELDAT ROUTER - The Console I - 17 Doc.DM704-I Rev.10.97 4.12.VRF-TELNET Establishes a Telnet connection in the indicated VRF as client for the remote device whose address is specified.This address can be a domain name in cases where the DNS client is configured. Syntax: *t el net [ sour ce | por t | ]

specifies the VRF name where you wish to initiate the telnet session. In cases where no additional parameters are entered (vrf-telnet option), you are asked for all the telnet parameters. Parameters that can be specified in Teldat are as follows: specifies the IP address or domain name for the device you wish to access via telnet. source specifies the source IP address to use for Telnet. port specifies the destination port to use for Telnet. Examples: Telnet to device with address 172.123.23.67 in the VRF client: *vr f - t el net cl i ent 176. 123. 23. 67 Tr yi ngt oconnect . . .( Pr essCont r ol St ocomebackt ol ocal r out er )Connect i onest abl i shed Telnet to device with address 172.24.78.92 in the VRF client using source address 80.1.1.1 and port 6623. FTP*vr f - t el netvr f t ag[ ] ?cl i entTel net dest i nat i on[ ] ?172. 24. 78. 92 Tel net sour ce[ 172. 24. 78. 94] ?80. 1. 1. 1 Tel net por t [ 23] ?6623 Tr yi ngt oconnect . . .( Pr essCont r ol St ocomebackt ol ocal r out er )Connect i onest abl i shed Telnettodevice172.24.78.92intheclientVRFusingsourceaddress80.1.1.1andport6623 specifying the parameters with options. FTP*vr f - t el net cl i ent 172. 24. 78. 92sour ce80. 1. 1. 1por t 6623 Tr yi ngt oconnect . . .( Pr essCont r ol St ocomebackt ol ocal r out er )Connect i onest abl i shed Telnet to device with domain name router1.midominio.es in the VRF client: FTP*vr f - t el net cl i ent r out er 1. mi domi ni o. es Tr yi ngt oconnect . . .( Pr essCont r ol St ocomebackt ol ocal r out er )Connect i onest abl i shed Chapt er2 Tel datRout erConf i gur at i on TELDAT ROUTER - Configuration II - 19 Doc.DM704-I Rev.10.97 1.I nt r oduc t i on From the functional point of view there are two virtual devices integrated in Teldat Router: 1.A router that performs the internetworking functions. 2.A packet switch coming from the router as well as from the X.25 and ISDN ports when they carry X.25 ROUTER NODEX.25 As the figure shows, each virtual device manages its own set of interfaces. Therefore it is necessary to accurately identify the different interfaces and to know whether an interface belongs to the router or the node. The interfaces in the Teldat Router configuration are identified through a name. The name for the physical interfaces is made up of a text string followed by two numbers separated by aslash.Thistextindicatesthetypeofinterface(serialline,ISDN,etc).Thefirstofthesetwo numbers indicates its location in the device (0 for the motherboard, 1 for the first extension pci, 2 for the second etc.) and the second number indicates the event number for the said type of interface for the same location (serial line 0, 1, 2, etc.). For interfaces added by the user, the name consists of a text string which indicates the type of interface and an identifier number which must be unique for each interface of the same type.An exception to this rule is the subinterfaces as their name is made up with the base interface number, over which these are configured, following by a period (.) and an identifier number.This identifier number again must be unique for each of the subinterfaces pertaining to the same base interface. The table of interface identifiers is obtained through the listdevices command in the configuration process. The output of this command in a specific device is shown below: Conf i g>l i st devi ces I nt er f aceConnect or Typeof i nt er f ace et her net 0/ 0LAN1Qui ccEt her netser i al 0/ 0SERI AL0/ WAN1ATCOMat m0/ 0DSL1ATMbr i 0/ 0BRI / I SDN1I SDNBasi cRat eI ntx25- node- - - Rout er - >Node Conf i g>The first column indicates the interface name (Interface), the second column indicates the physical connector which the interface (Connector) corresponds to, and the third column specifies the type of interface programmed. You must enter the name when selecting an interface (although you dont necessarily have to enter all the characters).For physical interfaces, simply enter the beginning of the text thus ensuring this does not coincide with any other interface text, following by the position if there is more than one interface of the same type.You do not always need to introduce the position (X/X); this is only necessary in cases where various interfaces of the same type are present (e.g. various serial interfaces). TELDAT ROUTER - Configuration II - 20 Doc.DM704-I Rev.10.97 Examples: Conf i g>l i st devi ces I nt er f aceConTypeof i nt er f aceCSRCSR2i ntet her net 0/ 0LAN1Fast Et her net i nt er f acef a200e0027 ser i al 0/ 0WAN1X25f a200a00f a203c005e ser i al 0/ 1WAN2X25f a200a20f a203d005d ser i al 0/ 2WAN3X25f a200a60f a203f 005b br i 0/ 0I SDN1I SDNBasi cRat eI nt f a200a40f a203e005c x25- node- - - Rout er - >Node00 Conf i g>Exampleofthevalidcommandstoaccessthefirstserialinterfaceofthemotherboard(WAN1) according to the devices listed in the above box. Conf i g>net wor kser i al 0/ 0 Conf i g>net wor kser 0/ 0 Conf i g>net wor kser 0 Conf i g>net wor ks0 Example of erroneous commands: Conf i g>net wor kser i alConf i g>net wor kserConf i g>net wor kser 0/ 4 Conf i g>net wor ks7 This network serial command is incorrect as there are various interfaces in the device with serial text; consequently you need to specify the interface location. Example of valid commands to access the bri interface: Conf i g>net wor kbr i 0/ 0 Conf i g>net wor kb0/ 0 Conf i g>net wor kbr i 0 Conf i g>net wor kb As, in this case, there is only one bri, you do not need to indicate the position within the equipment, simply introduce its text string.This does not necessarily need to be complete.The only characters necessary are those distinguishing this from other interfaces.As in this case there arent any other interfaces beginning with the letter b, this letter will suffice. Anotherimportantaspectisthatthereareinterfaceswhichdonothaveaphysical connector associated. This is the case of the x25-node interface in the example. This is due to the fact it is this interface that permits the virtual machines to join and consequently does not have an external connector associated. With this information you can redo the previous figure for this case: ROUTERX.25 ser i al 0/ 1 X25- node et her net 0/ 1 NODE NR br i 0/ 0 et her net 0/ 0 ser i al 0/ 0 Suppose now that you change the protocol in one of the WAN lines through the command setdata-link and we then consult the interface table. In the following example the X25 protocol is assigned to the physical line 1: TELDAT ROUTER - Configuration II - 21 Doc.DM704-I Rev.10.97 Conf i g>set dat a- l i nkx25ser i al 0/ 0 Conf i g>l i st devi ces I nt er f aceConnect or Typeof i nt er f ace et her net 0/ 0FE0/ LAN1Fast Et her net i nt er f ace et her net 0/ 1FE1/ LAN2Fast Et her net i nt er f ace ser i al 0/ 0SERI AL0/ WAN1X25 ser i al 0/ 1SERI AL1/ WAN2X25 br i 0/ 0BRI / I SDN1I SDNBasi cRat eI ntx25- node- - - Rout er - >Node Conf i g>As you can see, there is now an additional interface managed by the router and one less managed by the node. In this new example the diagram of the device is now as follows: ROUTERX.25 ser i al 0/ 0X25- node et her net 0/ 1 NODE NR br i 0/ 0 et her net 0/ 0 ser i al 0/ 1 In the following example, a generic Frame Relay interface is added over an ISDN basic access: Conf i g>adddevi cef r 1 Conf i g>The interface identifier is a number between 1 and 9999.This permits you to distinguish the created interface from other interfaces of the same type i.e. other frame-relay dial interfaces. Conf i g>l i st devi ces I nt er f aceConnect or Typeof i nt er f ace et her net 0/ 0FE0/ LAN1Fast Et her net i nt er f ace et her net 0/ 1FE1/ LAN2Fast Et her net i nt er f ace ser i al 0/ 0SERI AL0/ WAN1X25 ser i al 0/ 1SERI AL1/ WAN2X25 br i 0/ 0BRI / I SDN1I SDNBasi cRat eI ntx25- node- - - Rout er - >Node f r 1- - - Gener i cFR Conf i g>For those dial interfaces added by the user, you dont have to introduce the whole name in order to refer to the interface.Simply introduce the necessary characters in order to distinguish this from the other interfaces.The identifier however is mandatory. Example of valid commands to access the fr dial interface created according to the devices listed in the previous box: Conf i g>net wor kf r 1 Conf i g>net wor kf 1 In this new example, the diagram of the device is as follows: TELDAT ROUTER - Configuration II - 22 Doc.DM704-I Rev.10.97 ROUTERX.25 ser i al 0/ 1 X25- node et her net 0/ 1 NODE NR f r 1 et her net 0/ 0 br i 0/ 0 ser i al 0/ 0 IncaseswherewehaveATMinterfaces,subinterfacesassociatedtothesaidinterfacescanbe configured.E.g. in a configuration with an xDSL card in SLOT 3: Conf i g>l i st devi ces I nt er f aceConnect or Typeof i nt er f ace et her net 0/ 0GE0/ FE0/ LAN1Gi gabi t Et her net i nt er f ace et her net 0/ 1GE1/ FE1/ LAN2Gi gabi t Et her net i nt er f ace x25- node- - - Rout er - >Node at m3/ 0SLOT3Gener i cATMConf i g> Add a subinterface associated to the said interface: Conf i g>adddevi ceat m- subi nt er f aceat m3/ 02 Conf i g>l i st devi ces I nt er f aceConnect or Typeof i nt er f ace et her net 0/ 0GE0/ FE0/ LAN1Gi gabi t Et her net i nt er f ace et her net 0/ 1GE1/ FE1/ LAN2Gi gabi t Et her net i nt er f ace x25- node- - - Rout er - >Node at m3/ 0SLOT3Gener i cATMat m3/ 0. 2- - - ATM subi nt er f ace Conf i g> In order to access the said interface, you need to enter the base interface name followed by a period and the subinterface ID.This ID must be unique for all subinterfaces associated to the same base interface so they can be differentiated from each other.The ID must be entered in order to access the subinterface even if only one subinterface exists.When indicating the base interface name, follow the same rules as for the physical interfaces. Example of the valid commands to access an atm subinterface created according to the devices listed in the previous box: Conf i g>net wor kat m3/ 0. 2 Conf i g>net wor kat m3. 2 Conf i g>net wor kat m. 2 Conf i g>net wor ka. 2 As there is only one ATM base interface, you do not need to indicate the location. TELDAT ROUTER - Configuration II - 23 Doc.DM704-I Rev.10.97 2.Conf i gur at i on Pr oc ess The Configuration Process (config or running-config) permits you to configure router parameters such as: Interfaces. Protocols. The Configuration process CONFIG allows you to display and change the router startup configuration and store it in flash memory or in a smartcard.In order to store the changes made in this procedure, execute the save command. The router must be restarted so the configuration changes can take effect.To restart the router we can do the following: Execute the restart command at the * prompt in the Console Manager or Switch the router off then on. The RUNNING-CONFIG configuration process permits you to display and dynamically change the routeractiveconfigurationandstoreiteitherintheflashmemoryorinasmartcard.Sothatthe changes made in this process are stored, you need to execute the save command.Changes made in the RUNNING-CONFIG process take immediate effect. Note: All the active configuration can be displayed in the RUNNING-CONFIG process however you cannot modify all of it.Therefore, not all of the CONFIG process commands are available in the RUNNING-CONFIG process such as the no config command. The Configuration procedures CONFIG and RUNNING-CONFIG are framed into the router structure as shown in the following figure:GESTCON*RUNNING-CONFIGConfig$CONFIGConfig>MONITOR+VISEVENprocess 5process 4process 3process 2 TELDAT ROUTER - Configuration II - 24 Doc.DM704-I Rev.10.97 3.Conf i gur at i on pr oc edur e useri nt er f ac e Conf i gur at i on pr oc edur e ent er /ex i tTo enter the configuration procedure CONFIG from prompt * in the Console Manager GESTCON, enter the config command. ToentertheconfigurationprocedureRUNNIG-CONFIGfromprompt*intheConsoleManager GESTCON, enter the running-config command. Example: *conf i g Conf i g>To exit the configuration procedure and return to Console Manager GESTCON prompt *, press the escape character (Ctrl-p by default). Si mul t aneousl y ac c essi ng t he c onf i gur at i on menus When various users simultaneously access a device (via telnet or console), the Teldat router, with the aim of avoiding contradictions due to parallel configuration processes, will block simultaneous access to certain configuration menus. In cases where a conflict of this type is produced, the device will not permit the user to access the configuration environment and provide information on the circumstances provoking the situation. Example: At l as+syst emt el net I DUSERI PADDRESS: PORTCONNECTI ONTI MEI NACTI VI TYTI ME - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2teldat192. 168. 1. 2: 108/ 03/ 0512: 29: 260mi n* 1root172. 24. 51. 128: 13108/ 03/ 0512: 28: 5929mi n At l as+ User Console root At l as*conf i g At l asConf i g>pr ot ocol i p - - I nt er net pr ot ocol user conf i gur at i on- -At l asI Pconf i g>User Console teldat At l as*conf i g At l asConf i g>pr ot ocol i p CLI Er r or : Command locked by another user CLI Er r or : Commander r orAt l asConf i g> In this case, the teldat user tries to access the IP protocol configuration environment and the device prevents this as the root user is currently accessing the said menu. ShowCommand Theshowcommandcanbeexecutedfromanyconfigurationprocessmenu.Thispermitsthree options: TELDAT ROUTER - Configuration II - 25 Doc.DM704-I Rev.10.97 Conf i g>show ? al l - conf i g conf i g menu Conf i g> The showall-config command displays the net configuration of all the device menus and submenus that the user can access.I.e. displays all the commands that must be introduced through the console in order to configure the device as it is when executing the show all-config command. Example: Conf i g>show al l - conf i g ; Showi ngSyst emConf i gur at i onf or access- l evel 15. . .; ATLAS50Rout er 948Ver si on10. 7. 0 l og- command- er r or s noconf i gur at i on ;net wor ket her net 0/ 0 ; - - Et her net I nt er f aceUser Conf i gur at i on- -i paddr ess172. 24. 78. 116255. 255. 0. 0 ;;;;;exi t;;;;net wor ket her net 0/ 1 ; - - Et her net I nt er f aceUser Conf i gur at i on- -noi paddr ess ;exi t;;;;;net wor kx25- node ; - - X25- nodei nt er f aceconf i gur at i on- -noi paddr ess ;exi t;pr ot ocol i p ; - - I nt er net pr ot ocol user conf i gur at i on- -cl assl ess ;t vr p ; - - TVRPConf i gur at i on- -enabl e ;gr oup1i p172. 24. 78. 128 gr oup1l ocal - i p172. 24. 78. 116 ;exi t;exi t;;dump- command- er r or s end ; - - - end- - -Conf i g> TELDAT ROUTER - Configuration II - 26 Doc.DM704-I Rev.10.97 Thiscommandshowsthewholeofthenetconfigurationofthedevicethattheusercanaccess independently of the menu and submenu where the user is located.Therefore, for example, from the IP menu: I Pconf i g>show al l - conf i g ; Showi ngSyst emConf i gur at i onf or access- l evel 15. . .; ATLAS50Rout er 948Ver si on10. 7. 0 l og- command- er r or s noconf i gur at i on ;net wor ket her net 0/ 0 ; - - Et her net I nt er f aceUser Conf i gur at i on- -i paddr ess172. 24. 78. 116255. 255. 0. 0 ;;;;;exi t;;;;net wor ket her net 0/ 1 ; - - Et her net I nt er f aceUser Conf i gur at i on- -noi paddr ess ;exi t;;;;;net wor kx25- node ; - - X25- nodei nt er f aceconf i gur at i on- -noi paddr ess ;exi t;pr ot ocol i p ; - - I nt er net pr ot ocol user conf i gur at i on- -cl assl ess ;t vr p ; - - TVRPConf i gur at i on- -enabl e ;gr oup1i p172. 24. 78. 128 gr oup1l ocal - i p172. 24. 78. 116 ;exi t;exi t;;dump- command- er r or s end ; - - - end- - -I Pconf i g> The show config command displays the net configuration of all the menus and submenus that the user can access and that can be accessed from the menu where the user is located when he executes this command. TELDAT ROUTER - Configuration II - 27 Doc.DM704-I Rev.10.97 Example: Conf i g>show conf i g ; Showi ngSyst emConf i gur at i onf or access- l evel 15. . .; ATLAS50Rout er 948Ver si on10. 7. 0 l og- command- er r or s noconf i gur at i on ;net wor ket her net 0/ 0 ; - - Et her net I nt er f aceUser Conf i gur at i on- -i paddr ess172. 24. 78. 116255. 255. 0. 0 ;;;;;exi t;;;;net wor ket her net 0/ 1 ; - - Et her net I nt er f aceUser Conf i gur at i on- -noi paddr ess ;exi t;;;;;net wor kx25- node ; - - X25- nodei nt er f aceconf i gur at i on- -noi paddr ess ;exi t;pr ot ocol i p ; - - I nt er net pr ot ocol user conf i gur at i on- -cl assl ess ;t vr p ; - - TVRPConf i gur at i on- -enabl e ;gr oup1i p172. 24. 78. 128 gr oup1l ocal - i p172. 24. 78. 116 ;exi t;exi t;;dump- command- er r or s end ; - - - end- - -Conf i g> the show all-config.However if you execute the show config command from the IP menu, only the IP and the TVRP configurations are shown: TELDAT ROUTER - Configuration II - 28 Doc.DM704-I Rev.10.97 I Pconf i g>show conf i g ; Showi ngMenuandSubmenusConf i gur at i onf or access- l evel 15. . .; ATLAS50Rout er 948Ver si on10. 7. 0 cl assl ess ;t vr p ; - - TVRPConf i gur at i on- -enabl e ;gr oup1i p172. 24. 78. 128 gr oup1l ocal - i p172. 24. 78. 116 ;exi t;I Pconf i g> The show menu command displays the configuration of the menu where the command is executed but does not display the submenu configuration. Examples: Conf i g>show menu ; Showi ngMenuConf i gur at i onf or access- l evel 15. . . l og- command- er r or s noconf i gur at i on dump- command- er r or s end Conf i g> I Pconf i g>show menu ; Showi ngMenuConf i gur at i onf or access- l evel 15. . . cl assl ess ;I Pconf i g> TVRPconf i g>show menu ; Showi ngMenuConf i gur at i onf or access- l evel 15. . . enabl e ;gr oup1i p172. 24. 78. 128 gr oup1l ocal - i p172. 24. 78. 116 ;TVRPconf i g> The configuration generated by the show command can be copied to a text file and edited to the users requirements.Subsequentlythiscanbeinstalledinanunconfigureddevicesothatthisisnow configured. If, during the period where the router is displaying the configuration, you wish to abort the process simply enter the escape character (default is Ctrl + p). Opt i ons Li stWhenconfiguringadeviceyouarefrequentlyaskedtoselectanoptiontoconfiguredetermined entities for the router such as Frame Relay PVCs (Dm 703-I) or TVRP groups (Dm 725-I). TELDAT ROUTER - Configuration II - 29 Doc.DM704-I Rev.10.97 Whenselectinganoption,youdonotneedtoenterallthetextforthis,simplyintroducingthe necessary characters in order to distinguish this option from the rest will suffice. Examples: ser i al 0/ 0FRconf i g>pvc16? backupConf i gur esever al backuppar amet er s BcOut goi ngCommi t t edBur st Si ze BeOut goi ngExcessBur st Si ze CI ROut goi ngCommi t t edI nf or mat i onRat e compr essi onEnabl e/ di sabl ecompr essi onf or t hi sci r cui tdef aul t Cr eat et hevi r t ual ci r cui tencapsul at i onEncapsul at i ont ype encr ypt Enabl e/ di sabl eencr ypt i on f r agment at i on- si zeFor cedf r agment at i onsi ze i nver se- ar pI nver seARPconf i gur at i onf or t hi sdl cinameSet t hevi r t ual ci r cui t name no r out eSet st at i cr out ef or PVCswi t chi ng ser i al 0/ 0FRconf i g>pvc16ci r 32000 ser i al 0/ 0FRconf i g> Inthisparticularcase,youcouldhavesimplyenteredciasnootheroptionbeginswiththis.Howeverenteringjustcwouldbeinvalidasthereisanotheroptionthatbeginswithc (compression) consequently this would have produced an error. TELDAT ROUTER - Configuration II - 30 Doc.DM704-I Rev.10.97 4.Conf i gur at i on c ommands This section describes the configuration commands (CONFIG and RUNNING CONFIG process). Each commandincludesadescription,syntaxandoneexample.Thefollowingtablesummarizesthe configuration commands. CommandFunction ADDAllows you to create a virtual interface. AUTOINSTALLSets the autoinstall parameters. BACKUP-FILESMakes a backup copy of the system files. BANNERPermits you to configure banners in the device. CONFIG-MEDIAPermits you to specify the active storage unit: flash or SmartCard or both. CONFIRM-CFG-NEEDEDEnables the need to confirm the saved configuration. CONFIRM-CFGConfirms the current configuration. COPYAllows you to copy the Running Config configuration to Config. DESCRIPTIONConfiguration description. DISABLEDisables a specific feature in the router. DUMP-COMMAND-ERRORS Displays errors in the commands line. ENABLEEnables a specific feature in the router. EVENTEnters the events monitoring configuration procedure. FEATUREDefinestheadditionalfeaturesoftherouternotassociatedwithany predetermined interface. FILEPermits you to carry out operations with files (list and copy). FIRMWARE-CHECKINGEnables checking when firmware files are required. FORMATFormats a storage unit in the device. GLOBAL-PROFILESAccesses the profiles configuration menu, ATM, PPP etc. LICENCE-CHANGEChanges the current license. LISTShows the system parameters and hardware configuration. LOG-COMMAND-ERRORSBegins to save errors in the commands line. MANAGEMENTEnters the master router configuration environment. NETWORKEnters the configuration menu of a specific interface. NOInvalidates a command action or sets the default values. NODEEnters the X.25/ISDN, XOT or 270 Node configuration. PRIVILEGEPermits you to specify personalized execution permissions. PROTOCOLEnters the configuration of a specific protocol. SAVEAllows you to save the configuration in the active storage unit. SETConfigures system parameters, buffers, device name, etc. TELEPHONYSets the Voice over IP parameters. TIMEPermits you to view and change the system data and time. UCIPermits you to configure the Teldat Router encryption unit. USERPermits you to configure users. ENDEnd of configuration. 4.1.ADD AllowsyoutocreateavirtualinterfacetobeusedbyanISDNbasicaccessBchannel,ATM subinterfaces, PPP interfaces etc. TELDAT ROUTER - Configuration II - 31 Doc.DM704-I Rev.10.97 Syntax: Conf i g>add devi ceCr eat eavi r t ual devi ce specifies the selected option. The only option available for this command is: a) ADD DEVI CE Syntax: Conf i g>adddevi ce [ opt i ons] this is the virtual interface you want to create.To find out what types of interfaces are available, enter add device ?. Conf i g>adddevi ce? 270Cr eat eavi r t ual 270i nt er f ace at m- subi nt er f aceCr eat eavi r t ual ATM Subi nt er f acei nt er f ace bvi Cr eat eavi r t ual Br i dgei nt er f ace di al - r out i ngCr eat eavi r t ual Di al - Rout ei nt er f ace et h- subi nt er f aceCr eat eavi r t ual Et her net Subi nt er f acei nt er f ace f r Cr eat eavi r t ual Fr ame- Rel ayi nt er f ace hdl cCr eat eavi r t ual HDLCi nt er f ace l 2t pCr eat eavi r t ual L2TPi nt er f ace l oopbackCr eat eavi r t ual Loopbacki nt er f ace pcmci aCr eat eavi r t ual PCMCI Ai nt er f ace pppCr eat eavi r t ual PPPi nt er f ace t ni pCr eat eavi r t ual TNI Pi nt er f ace voi p- dummyCr eat eavi r t ual VoI Pi nt er f acewi t hnohar dwar e voi p- i sdnCr eat eavi r t ual VoI Pi nt er f aceover I SDN x25Cr eat eavi r t ual X25i nt er f ace xot Cr eat eavi r t ual XOTi nt er f ace [options] The options available depend on the type of virtual interface you wish to create.These are described in the manual specifically related to the said interface. Example: Conf i g>adddevi cepcmci a? modemPCCARDModemt ype umt sPCCARDUMTSt ype Conf i g>adddevi cepcmci amodem? Sl ot numberConf i g>adddevi cepcmci amodem1? I nt er f aceI d Conf i g>adddevi cepcmci amodem10?

Conf i g>adddevi cepcmci amodem10 Conf i g> For further information, please see the manual associated to the virtual interface you wish to create. 4.2.AUTOI NSTALL EstablishesthedeviceparametersforautoinstallationthroughFrameRelayfromaTELDAGES network manager. Syntax: Conf i g>aut oi nst al l [ val ue]i dent i f i er Conf i gur ei dent i f i er t ype management - host Conf i gur emanagement host this is the autoinstallation parameter identifier to configure. TELDAT ROUTER - Configuration II - 32 Doc.DM704-I Rev.10.97 [value] value to assign to the above specified parameter. There are two types of configurable parameters: a) AUTOI NSTALL I DENTI FI ER Specifies the typeofdeviceidentifiersoit is correctlyinterpretedfromthe TELDAGESnetwork manager. Syntax: Conf i g>aut oi nst al l i dent i f i er this is the type of device identifier.Currently only serial is available which uses the device serial number to identify it for the network manager. Example: Conf i g>aut oi nst al l i dent i f i er ser i alConf i g>b) AUTOI NSTALL MANAGEMENT-HOST Identifies the management station where the remote autoconfiguration is executed. Syntax: Conf i g>aut oi nst al l management - host management station identifier.This identifier can be an IP address or a Fully Qualified Domain Name/Hostname. Example: Conf i g>aut oi nst al l management - host www. gest i on. t el dat . es Conf i g>4.3.BACKUP-FI LES This creates a recovery point by making a copy of the system files from the primary partition to the backuppartition.Consequently,shouldthefilingsystembecomecorrupt,thedevicewill automatically restore the files from the recovery point and is able continue operating. The configuration monitoring command shows information relative to the recovery process, indicating if it has started up normally (from the first partition) or if its restored from the recovery point (from the backup partition). The configuration command [no] firmware-checking determines if the restoration for the filing system is enabled in cases where a necessary firmware file is corrupt. This command only works in devices with partitioned flash memory. Syntax: Conf i g>backup- f i l es Example 1: Conf i g>backup- f i l es Backupi npr ogr ess. . .Backupsuccessf ul .Conf i g>In this example, a recovery point has been successfully created. Example 2: Conf i g>backup- f i l es TELDAT ROUTER - Configuration II - 33 Doc.DM704-I Rev.10.97 CLI Er r or : Backupdevi cenot avai l abl e.CLI Er r or : Commander r orConf i g>In this example, the device does not have a partitioned flash and therefore the command has returned an error message without creating any recovery point. 4.4.BANNER Permits you to configure banner in the device. Syntax: Conf i g>banner l ogi nSet l ogi nbanner specifies the type of banner to configure. a) Bannerl ogi n Permits you to configure an access banner in the device which is always displayed when a user tries to access the device through console, telnet or ftp. Toentervariouslinesoftextinthebanner,executethebannerlogincommand,orderlyand consecutively, followed by each line of text (between inverted commas should there be spaces). The size of an access banner is limited to 15 lines of text each containing 80 characters. Syntax: Conf i g>banner l ogi nExample: Conf i g>banner l ogi n "################################################################################"Conf i g>banner l ogi n"# Est eequi poespr opi edaddeTel dat , S. A. ysuusoest r est r i ngi doasus#" Conf i g>banner l ogi n"# empl eados. Por f avor , abor t eest aconexi nsi ust ednoes empl eadode#" Conf i g>banner l ogi n"# Tel dat , S. A. ot i eneunaaut or i zaci nl egal par aacceder alequi po. #" Conf i g>banner l ogi n "################################################################################" Conf i g>show conf i g ; Showi ngSyst emConf i gur at i onf or access- l evel 15. . .; ATLAS50Rout er 948Ver si on10. 7. 0 l og- command- er r or s noconf i gur at i on banner l ogi n "################################################################################" banner l ogi n"# Est eequi poespr opi edaddeTel dat , S. A. ysuusoest r est r i ngi doa sus#" banner l ogi n"# empl eados. Por f avor , abor t eest aconexi nsi ust ednoesempl eado de#" banner l ogi n"# Tel dat , S. A. ot i eneunaaut or i zaci nl egal par aacceder al equi po.#" banner l ogi n "################################################################################" ;user GPEREZhash- passwor d9DDE06D391B87902FD9FCC8AACC9641B ;user TELDAThash- passwor dA44AD55CE197114B241EE3DDEBB04660 ;; TELDAT ROUTER - Configuration II - 34 Doc.DM704-I Rev.10.97 ;net wor ket her net 0/ 0 ; - - Et her net I nt er f aceUser Conf i gur at i on- -noi paddr ess ;exi t;;;net wor ket her net 0/ 1 ; - - Et her net I nt er f aceUser Conf i gur at i on- -noi paddr ess ;exi t;;;;net wor kx25- node ; - - X25- nodei nt er f aceconf i gur at i on- -noi paddr ess ;exi t;;;dump- command- er r or s end ; - - - end- - -Conf i g>saveyes Bui l di ngconf i gur at i onast ext . . . OK Wr i t i ngconf i gur at i on. . . OKonFl ash Conf i g> *r est ar tAr eyousur et or est ar t t hesyst em( Yes/ No) ?y Done Rest ar t i ng. Pl easewai t . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .APPDATADUMP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Bi os- st ackused: 0x1498 Bi os- st ackf r ee: 0x2B68 Aux- st ackused: 0x0 Aux- st ackf r ee: 0x2000 Runni ngappl i cat i on Fl ashconf i gur at i onr ead Par si ngt ext modeconf i gur at i on. . .Conf i gur at i onpar sed I ni t i al i zi ng Pr essanykeyt oget st ar t ed ################################################################################# Est eequi poespr opi edaddeTel dat , S. A. ysuusoest r est r i ngi doasus## empl eados. Por f avor , abor t eest aconexi nsi ust ednoesempl eadode## Tel dat , S. A. ot i eneunaaut or i zaci nl egal par aacceder al equi po. ################################################################################# User : By default, the device does not have an access banner configured. b) BannerEx ecConfigures a welcome banner that is displayed when a user accesses the device through the console, Telnet, SSH or FTP. TELDAT ROUTER - Configuration II - 35 Doc.DM704-I Rev.10.97 If the banner contains more than one line then each line must be independently configured through the bannerexeccommand,enteringeachlineintheorderyouwantthemdisplayed.Iftheline text contains spaces, these must be entered between quotation marks. The banner is limited to a maximum of 15 lines of text and 80 characters per line. Syntax: Conf i g>banner execExample: Conf i g>banner exec"##############################################################" Conf i g>banner exec"" Conf i g>banner exec". . . . . . . . . . . . : : : : : : : : : : : WELCOME: : : : : : : : : : : . . . . . . . . . . . . " Conf i g>banner exec"" Conf i g>banner exec"##############################################################" Conf i g>saveyes Bui l di ngconf i gur at i onast ext . . . OK Wr i t i ngconf i gur at i on. . . OKonFl ashasCONFI G Conf i g>*r est ar tAr eyousur et or est ar t t hesyst em( Yes/ No) ?y Rest ar t i ng. Pl easewai t . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .APPDATA DUMP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . .Bi os- st ackused: 0x14E8 Bi os- st ackf r ee: 0x2B18 Aux- st ackused: 0x0 Aux- st ackf r ee: 0x2000 Runni ngappl i cat i on WARNI NG: Runni ngwi t hsuper l i cence. Fl ashconf i gur at i onr ead Par si ngt ext modeconf i gur at i on. . .Conf i gur at i onpar sed I ni t i al i zi ng Pr essanykeyt oget st ar t ed Tel dat ( c) 2001- 2012 Rout er model Super **CPUMPC8260S/ N: 472/ 04709 2LAN, 2WANLi nes, 1I SDNLi ne CI Tsof t war ever si on: 10. 09. 04Oct 25201218: 43: 58 ############################################################## . . . . . . . . . . . . : : : : : : : : : : : WELCOME: : : : : : : : : : : . . . . . . . . . . . . ############################################################## * 4.5.CONFI G-MEDI A This permits you to select the active storage device in which the configurations are saved on applying the configuration command save.This is also the default media in the file list command. You might find two storage medias in the devices: flash memory and SmartCard cards.All devices have the flash memory as the basic storage unit.The availability of SmartCard cards depends on the TELDAT ROUTER - Configuration II - 36 Doc.DM704-I Rev.10.97 type of device.In order to find out if your device supports SmartCard, please see the installation manual. By default, the device has the value smartcard-flash configured in those devices that support the SmartCard and the flash option in those that dont.You can check which unit is active through the file list configuration command. Syntax: Conf i g>conf i g- medi a f l ashConf i gur at i onsar est or edonl yi nFl ash smar t car dConf i gur at i onsar est or edonl yi nSmar t Car d smar t car d- f l ashConf i gur at i onsar est or edi nSmar t Car dandFl ash specifies the name of the storage unit to be used. For further information on the use of the storage units, please see the file list and file copy commands described in this manual as well as the installation manual for your device.For further information on how to select a file as the active configuration, please see the setfile command described in this manual. ThebehaviordescribedbelowaltersslightlyifthemicroswitcheissettoON.Forfurther information please see the installation manual for your device. a) CONFI G-MEDI A FLASH Specifies the flash memory as the only active storage unit when reading or writing configurations. On booting the device the configuration is read from Flash.If the active configuration file is not found, the device will boot with the default configuration.On saving the configuration through the save command, this will be saved in the Flash memory with the name of the active file. Example: Conf i g>conf i g- medi af l ash b) CONFI G-MEDI A SMARTCARD Specifies the SmartCard as the only active storage unit when reading or writing configurations. On booting the device the configuration is read from the Smart Card.If the card is not present or the active configuration file is not found, the device will boot with the default configuration.On saving the configuration through the save command, this will be saved in the SmartCard with the name of the active file. Example: Conf i g>conf i g- medi asmar t car d c ) CONFI G-MEDI A SMARTCARD-FLASH Specifies both the SmartCard as well as the flash memory as active storage devices when reading or writing configurations.The SmartCard is considered as having priority over the flash memory. Initially on booting, the configuration is read from theSmartCard.If the card is not present or the active configuration file cannot be found, the operation is repeated in the Flash memory.If the file is not found in the Flash memory then the device will boot with the default configuration.After reading the Smart Card configuration file the device checks to see that this is written in the Flash memory.If the configuration is not present then the device enters it so that both medias are synchronized. On saving the configuration through the save command, the configuration is saved in both the Smart CardandtheFlashwith the name of the active file.The console indicates the devices where the configuration has been stored and through a warning text will show the devices where recording has not been possible. TELDAT ROUTER - Configuration II - 37 Doc.DM704-I Rev.10.97 Example: Conf i g>conf i g- medi asmar t car d- f l ash 4.6.CONFI RM-CFG Confirms the current configuration.You need to have saved a configuration with the configuration confirmation function activated.Please see confirm-cfg-needed. Syntax: Conf i g>conf i r m- cf g This action can also be executed via SNMP.Please see section 4.7 4.7.CONFI RM-CFG-NEEDED Enablestheneedtoconfirmthesavedconfiguration.Ifyouhaveexecutedthiscommand,the configuration is saved in TEMP.CFG in order to be checked.If, after restarting, the configuration is not confirmed with the confirm-cfg command within the configured time, the device will restart with the previous configuration.If the configuration is confirmed it, is saved with the corresponding name i.e. the use of TEMP.CFG is transparent to the user.Should the new configuration make the device restart before the programmed test time is reached, if after ten restarts without the configuration being confirmed, the previous configuration will be restored.If you execute the no confirm-cfg command, thedevicewillrestartwiththepreviousconfiguration.Thenoconfirm-cfg-neededcommand disables the need to confirm the newly saved configurations. Syntax: Conf i g>conf i r m- cf g- needed def aul t Enabl est heneedof conf i gur at i onconf i r mat i on t i meout Set sat i meout t owai t f or conf i r mat i on specifies the selected action. a) CONFI RM-CFG-NEEDED DEFAULT Enables the need to confirm the saved configurations with a test time of 10 minutes. Syntax: Conf i g>conf i r m- cf g- neededdef aul tExample: Conf i g>conf i r m- cf g- neededdef aul tConf i g>b) CONFI RM-CFG-NEEDED TI MEOUT Configures the new configuration test time which the device will wait before restarting the previous configuration if confirmation is not carried out.The minimum is one minute and the maximum is 5 weeks. Syntax: Conf i g>conf i r m- cf g- neededt i meout specifies the test time in any of the following formats: Xw, Xd, Xh, Xm, Xs, HH:MM, HH:MM:SS. TELDAT ROUTER - Configuration II - 38 Doc.DM704-I Rev.10.97 Example: Conf i g>conf i r m- cf g- neededt i meout 30s Conf i g>There is the possibility of executing the confirmed save configuration feature through SNMP.To do this, three new SNMP variables have been created with their corresponding OIDs: telAdminStatusConfirmConfig(OID:1.3.6.1.4.1.2007.1.2.14).Thisvariableservesto confirm/not confirm the current configuration. Inawriteoperation,settingthisvariableto1confirmsthecurrentconfigurationand setting it to 0 rejects the current test configuration so the device restarts with the previous configuration. In a read operation, a 0 value (confirmed) indicated that the current configuration has been confirmed.A 1 value (test_cnfg_inactive) indicates that the current configuration has not been confirmed as yet (consequently this is a test configuration) and neither is it active.Its the previous configuration which is still active.A 2 value (test_cnfg_active) indicates that the current configuration has not been confirmed as yet (and consequently this is a test configuration),butwearedealingwithanactiveconfiguration.Avalueof3 (configuration_recovered)indicatesthatthepreviousconfigurationhasbeenrecovered and is confirmed and active.A value of 4 (undefined) only occurs in cases where the confirmed saved configuration is disabled as in this case the use of this SMNP variable makes no sense. There are three scenarios where recuperation of the old configuration can be produced (andthereforethetelAdminStatusConfirmConfigvariabletakesthe configuration_recovered value 3): a)Aftertheconfirmationwaittimerhastimedoutwithoutconfirmingthetest configuration. b)After 10 consecutive device restarts (produced before the confirmation wait timer has timed out).The intention to restore the old configuration in this scenario is in order to protect us should the new configuration make the device restart before reaching the programmed test time. c)After rejecting the current test configuration through the noconfirm-cnfg command (or through SNMP by entering a 0 in the telAdminStatusConfirm Config variable). telAdminStatusConfirmEnabled (OID: 1.3.6.1.4.1.2007.1.2.15). This variable serves to enable/disable the confirmed save. Inawriteoperation,settingthisvariableto1enablestheneedtoconfirmthesaved configuration.Setting this variable to 0 disables the need to configure the new saved configurations. In a read operation, a 0 value (disable) indicates that the confirmed save configuration functionalityisdisabled. Andavalueof1(enable)indicatesthat theconfirmedsave configuration functionality is enabled. telAdminStatusTimeoutConfirm (OID: 1.3.6.1.4.1.2007.1.2.16). This variable serves to configure the value (in seconds) that the confirmed save configuration functionality timer takes.I.e. this is the time the device waits before restarting the old configuration if this is not confirmed. The values permitted for this variable are within the range of 60 (1 minute) and 3024000 (5 weeks).Default is 600 (10 minutes). TELDAT ROUTER - Configuration II - 39 Doc.DM704-I Rev.10.97 Inawriteoperation,valuesbetween60and3024000configurethetimertothesaid introduced value. In a read operation, values between 60 and 3024000 returns the seconds value to that the timer is configured with. Therefore, a logical operating sequence for the confirmed save configuration via SNMP is: Initiallytheconfirmedsaveconfigurationisdisabled.TheSNMPvariableshavethe following values: otelAdminStatusConfirmConfig =4 (undefined) otelAdminStatusConfirmEnabled =0 (disable) otelAdminStatusTimeoutConfirm =600 Enabletheconfirmedsaveconfiguration(settingthetelAdminStatusConfirmEnabled SNMP variable value to 1). The SNMP variables take the following values: otelAdminStatusConfirmConfig =0 (confirmed) otelAdminStatusConfirmEnabled =1 (enable) otelAdminStatusTimeoutConfirm =600 Set the confirmation wait timer value to the value you want (1 minute for example).To do this, set the telAdminStatusTimeoutConfirm SNMP variable value to 60.The SNMP variables take the following values: otelAdminStatusConfirmConfig =0 (confirmed) otelAdminStatusConfirmEnabled =1 (enable) otelAdminStatusTimeoutConfirm =60 Make the changes in the device configuration that you consider opportune and save them (setting the telAdminStatusSaveConfig SNMP variable value to 1).The SNMP variables take the following values: otelAdminStatusConfirmConfig =1 (test_cnfg_inactive) otelAdminStatusConfirmEnabled =1 (enable) otelAdminStatusTimeoutConfirm =60 Restart the device.The SNMP variables take the following values: otelAdminStatusConfirmConfig =2 (test_cnfg_active) otelAdminStatusConfirmEnabled =1 (enable) otelAdminStatusTimeoutConfirm =60 Confirm the tests configuration (which are active) before the 60 second timer times out (settingthetelAdminStatusConfirmConfigSNMPvariablevalueto1).TheSNMP variables take the following values:otelAdminStatusConfirmConfig =0 (confirmed) otelAdminStatusConfirmEnabled =1 (enable) otelAdminStatusTimeoutConfirm =60 Continuingwiththeexample,wecouldcarryoutsomenewchangesinthedevice configuration and save them (setting the telAdminStatusSaveConfig SNMP variable to 1).The SNMP variables take the following values: otelAdminStatusConfirmConfig =1 (test_cnfg_inactive) otelAdminStatusConfirmEnabled =1 (enable) otelAdminStatusTimeoutConfirm =60 Restart the device.We can see that the test configuration is active.The SNMP variables take the following values: otelAdminStatusConfirmConfig =2 (test_cnfg_active) TELDAT ROUTER - Configuration II - 40 Doc.DM704-I Rev.10.97 otelAdminStatusConfirmEnabled =1 (enable) otelAdminStatusTimeoutConfirm =60 Nowweneedtoleavethetimertotimeout(1minute)withoutconfirmingthetest configuration.Orwecouldrestorethepreviousconfigurationbysettingthe telAdminStatusConfirmEnabledSNMPvariablevalueto0.Inbothcases,thedevice restarts with the old configuration as the active configuration and the SNMP variables displays the following values: otelAdminStatusConfirmConfig =3 (configuration_recovered) otelAdminStatusConfirmEnabled =1 (enable) otelAdminStatusTimeoutConfirm =60 4.8.COPY ThiscommandallowsyoutocopytheRunningConfig(P5)configurationtoConfig(P4).Confirmation will be requested in cases where the Config (P4) configuration has been modified. Syntax: Conf i g>copyr unni ng- conf i gconf i g Example: Conf i g>copyr unni ng- conf i gconf i g War ni ng: St at i c- conf i ghasbeenchanged.CopyRunni ng- Conf i gt oConf i g( Yes/ No) ?y Copyi ngconf i gur at i on. . . OK Conf i g>4.9.DESCRI PTI ON Permitsyoutointroducedescriptivetextsregardingthedeviceconfiguration.Thisdescriptionis displayed on screen on executing the list configuration configuration command. Syntax: Conf i g>descr i pt i on the configuration description text.If this text contains spaces, this must be written between quotation marks (e.g. description description containing spaces). Example: Conf i g>descr i pt i onMadr i d_Br anch_Out comi ng_Rout er4.10.DI SABLE Disables a specific personalized parameter. This command is used to deactivate the behavior activated through the enable patch command. In order to use this, you need to know the name of the activated parameters.To do this use the list patch command in the configuration console. Syntax: Conf i g>di sabl epat ch name of the parameter to deactivate.If you introduce default as the parameter name, ALL the active parameters will be deactivated. TELDAT ROUTER - Configuration II - 41 Doc.DM704-I Rev.10.97 Example: Conf i g>di sabl epat char pi _snd_l clConf i g>4.11.DUMP-COMMAND-ERRORS Displays, on screen, a list of the first five erroneous commands introduced in the configuration console fromthepointwherethelog-command-errorscommandwasexecuted.Thiscommandis particularly useful for detecting errors that have been produced when loading a complete configuration file in a device. Syntax: Conf i g>dump- command- er r or s Example: Conf i g>dump- command- er r or s War ni ng: possi bl eer r or si nt heconf i gur at i on, at l east t hesef ound:l i ne2- > astl i ne4- > devet h1 l i ne5- > devser 134 l i ne6- > conf 0 l i ne7- > l i st i nt er f et h1 ( l i nescount i ngsi ncel ast l og- command- er r oscommand)Toomanyer r or s, somecannot bepr i nt ed( pr i nt ed5of 8)Conf i g>4.12.ENABLE Thisenablesaspecificpersonalizedparameter.Thiscommandallowsyouundercertain circumstances to modify the routers behavior.It deals with the management of personalized versions.You need the names of the available parameters1 and their possible admitted values in order to use it.Introducing the name and desired value for the parameter will activate it. Syntax: Conf i g>enabl epat ch [ val ue] name of the parameter to activate. [value] value of the said parameter. Example: Conf i g>enabl epat char pi _snd_l cl 1 Conf i g>In order to check the active parameters in your device at any point, use the list patch command.To disable an active personalized parameter, use the disable patch command followed by the parameter name. 1 The personalized parameters relative to each Teldat device functionality can be found correctly documented in the manuals associated to these said functionalities. TELDAT ROUTER - Configuration II - 42 Doc.DM704-I Rev.10.97 4.13.EVENT ThisallowsyoutorecordthoseeventsyouwishtobestoredbytheEventLoggingSysteminthe configuration.Enter exit to return to the Config> prompt. Syntax: Conf i g>eventExample: Conf i g>event - - ELSConf i g- -ELSConf i g>In order to see the commands that can be executed from this prompt, please see Chapter4Event Logging System ELS. 4.14.FEATURE Thisdefinestheadditionalfeaturesoftherouterwhicharenotassociatedtoapre-determined interface. Syntax: Conf i g>f eat ur e [ par amet er s]aaaAAAconf i gur at i onenvi r onmentaccess- l i st sAccessgener i caccessl i st sconf i gur at i on envi r onmentact Al sacust omt r apconf i gur at i onenvi r omentaf sAdvancedst at ef ul f i r ewal l andr out i ng aut oset - cf gAut oset - Conf i gconf i gur at i onenvi r onmentbandwi dt h- r eser vat i onBandwi dt h- Reser vat i onconf i gur at i onenvi r onmentcl ass- mapCl assMapconf i gur at i onenvi r onmentcont r ol - accessCont r ol - accessconf i gur at i onenvi r onmentdnsDNSconf i gur at i onenvi r onmentdns- updat er DNSUpdat er conf i gur at i onenvi r onmentecho- r esponder Echopr ot ocol conf i gur at i onenvi r onmenter r - di sabl eEr r or di sabl econf i gur at i on f r ame- r el ay- swi t chFr ameRel aySwi t chconf i gur at i onenvi r onmentgps- appl i cat i onsGPSappl i cat i onsconf i gur at i onenvi r onmentht t pAccesst her out er ht t ppr ot ocol conf i gur at i on i p- di scover yTI DPconf i gur at i onenvi r onmenti st udI PSECTunnel Ser ver Di scover yconf i gur at i onenvi r onmentkey- chai nKeychai nmanagementl dapLDAPconf i gur at i onenvi r onmentmac- f i l t er i ngMac- f i l t er i ngconf i gur at i onenvi r onmentmanagement Management conf i gur at i onenvi r onmentnet f l ow Net f l ow cl i ent conf i gur at i on nsl aNet wor kSer vi ceLevel Advi sor conf i gur at i on nsmNet wor kSer vi ceMoni t or conf i gur at i onenvi r onmentnt pNTPconf i gur at i onenvi r onmentpol i cy- mapPol i cyMapconf i gur at i onenvi r onmentpr ef i x- l i st sAccessgener i cpr ef i xl i st sconf i gur at i on envi r onmentr adi usRADI USpr ot ocol conf i gur at i onenvi r onmentr monRemot eNet wor kMoni t or i ngconf i gur at i onenvi r onmentr out e- mapRout e- mapconf i gur at i onenvi r onmentscada- f or war der SCADAFor war der conf i gur at i onenvi r onmentsni f f er Sni f f er conf i gur at i onenvi r onmentspi SPI , mobi l eI PPr esenceSer vi ce, conf i gur at i onenvi r onmentsshSecur eShel l conf i gur at i onenvi r onmentst unSt unf aci l i t yconf i gur at i onenvi r onment TELDAT ROUTER - Configuration II - 43 Doc.DM704-I Rev.10.97 sysl ogSysl ogconf i gur at i onenvi r onmentt f t pTFTPconf i gur at i onenvi r omentt msTMSconf i gur at i onenvi r onmentvl anI EEE802. 1Qswi t chconf i gur at i onenvi r onmentvl i Vi r t ual Li nuxI nt er f aceconf i gur at i on vr f VRFconf i gur at i onenvi r onmentwr r - backup- wanWRRconf i gur at i onenvi r onmentwr s- backup- wanWRSconf i gur at i onenvi r onment name of the feature to configure. [parameters] parameters required for the specified option. a) FEATURE AAA Accesses the AAA feature configuration menu. Syntax: Conf i g>f eat ur eaaa Example: Conf i g>f eat ur eaaa - - AAAuser conf i gur at i on- -AAAconf i g>For further information on the AAA feature configuration, please see manual Dm800-I AAA Feature. b) FEATURE ACCESS-LI STS Accesses the configuration environment for the generic access lists. Syntax: Conf i g>f eat ur eaccess- l i st s Example: Conf i g>f eat ur eaccess- l i st s - - AccessLi st suser conf i gur at i on- -AccessLi st sconf i g>Forfurtherinformationonconfiguringgenericaccesslists,pleaseseemanualDm752-IAccess Control. c ) FEATURE ACT Accesses the ACT feature configuration menu. Syntax: Conf i g>f eat ur eactExample: Conf i g>f eat ur eact - - Al saCust omTr apconf i gur at i on- -ACTconf i g>For further information on configuring the ACT feature, please see manual Dm818-I ACT Feature. d) FEATURE AFS Accesses the afs configuration environment. Syntax: Conf i g>f eat ur eaf s TELDAT ROUTER - Configuration II - 44 Doc.DM704-I Rev.10.97 Example: Conf i g>f eat ur eaf s AFSconf i g> For further information on afs configuration, please see manual Dm786-I AFS. e) FEATURE AUTOSET-CFG Accesses the autoset-cfg configuration environment for those devices that support this. Syntax: Conf i g>f eat ur eaut oset - cf g Example: Conf i g>f eat ur eaut oset - cf g - - Aut oset cf gConf i gur at i on- -Aut oset - cf gConf i g>? Forfurtherinformationonautoset-cfgconfiguration,pleaseseemanualDm797-IDynamic Configuration Control. f ) FEATURE BANDWI DTH-RESERVATI ON This permits access to the Bandwidth-Reservation configuration environment (BRS). Syntax: Conf i g>f eat ur ebandwi dt h- r eser vat i on Example: Conf i g>f eat ur ebandwi dt h- r eser vat i on - - Bandwi dt hReser vat i onuser conf i gur at i on- -BRSConf i g>For further information on configuring bandwidth reservation, please see manual Dm715-I Bandwidth Reservation System. g) FEATURE CLASS-MAP Accesses the class-map configuration environment. Syntax: Conf i g>f eat ur ecl ass- map Example: Conf