| Oracle® Communications EAGLE Database Administration - System Management User's Guide Release 46.6 E93319 Revision 1 |
|
 Previous |
 Next |
| Oracle® Communications EAGLE Database Administration - System Management User's Guide Release 46.6 E93319 Revision 1 |
|
|
Previous |
Next |
This procedure is used to change the characteristics of a terminal, except for the SEAS terminal and a measurements terminal for an EAGLE containing a maximum of 700 signaling links, using the chg-trm command.
To configure a measurements terminal for an EAGLE containing a maximum of 700 signaling links, go to the Configuring the Measurements Terminal for an EAGLE Containing 700 Signaling Links procedure.
To configure a SEAS terminal, refer to the Configuring SEAS Terminals procedure.
The communication attributes can be changed on any terminal except on the terminal you are logged on to. The message output group assignments can be changed on any terminal, including the terminal you are logged on to. The chg-trm command uses these parameters.
:trm – terminal numbers (1 - 40, terminals 1-16 are serial terminals, terminals 17-40 are telnet terminals).
:baud – Serial port baud rate (2400, 4800, 9600, or 19200, 38400, 57600, 115200). Values 38400, 57600, and 115200 are only valid when the OAMHC is used.
:sb – The number of stop bits used in communications with the device (1 or 2).
:prty – Parity used by the device (odd, even, none).
:type – The type of device being connected (See the "Terminal Types" section).
:fc – The type of flow control used between the EAGLE and the output devices. (sw - software, hw - hardware, both - hardware and software, none).
Note:
Hardware flow control (fc=hw) and both hardware and software flow control (fc=both) are not supported for the terminal if the EAGLE contains E5-TDMs. Part of the terminal output may be lost if hardware flow control or both hardware and software flow control are specified for the terminal when the EAGLE contains E5-TDMs.:tmout – The maximum amount of time, in minutes, that a login session on the specified port can remain idle (that is, no user input) on the port before being automatically logged off. (0 - 99, see the "Security Parameters" section).
:mxinv – The login failure threshold – The number of login attempt failures or attempts to unlock a terminal that can occur on the terminal before the terminal is disabled. (0 - 9, see the "Security Parameters" section).
:dural – The length of time that the terminal is disabled after the login failure threshold has been exceeded. (See the "Security Parameters" section).
:all – Specifies whether or not all unsolicited messages are displayed on the specified terminal (yes or no).
:traf – Specifies whether or not traffic related unsolicited messages are displayed on the specified terminal (yes or no).
:link – Specifies whether or not link maintenance related unsolicited messages are displayed on the specified terminal (yes or no).
:sa – Specifies whether or not security administration related unsolicited messages are displayed on the specified terminal (yes or no).
:db – Specifies whether or not database related unsolicited messages are displayed on the specified terminal (yes or no).
:sys – Specifies whether or not system maintenance related unsolicited messages are displayed on the specified terminal (yes or no).
:pu – Specifies whether or not program update related unsolicited messages are displayed on the specified terminal (yes or no).
:uimrd – Specifies whether or not UIM redirect related unsolicited messages are displayed on the specified terminal (yes or no).
:appserv – Specifies whether or not application server related unsolicited messages are displayed on the specified terminal. (yes or no).
:appss – Specifies whether or not application subsystem related unsolicited messages are displayed on the specified terminal (yes or no).
:card – Specifies whether or not card related unsolicited messages are displayed on the specified terminal (yes or no).
:clk – Specifies whether or not clock related unsolicited messages are displayed on the specified terminal (yes or no).
:dbg – Specifies whether or not debug related unsolicited messages are displayed on the specified terminal (yes or no).
:gtt – Specifies whether or not global title translation related unsolicited messages are displayed on the specified terminal (yes or no).
:gws – Specifies whether or not gateway screening related unsolicited messages are displayed on the specified terminal (yes or no).
:meas – Specifies whether or not measurements maintenance related unsolicited messages are displayed on the specified terminal (yes or no).
:mon – Specifies whether or not unsolicited messages related to the Sentinel monitoring functions are displayed on the specified terminal (yes or no).
:mps – Specifies whether or not MPS related unsolicited messages are displayed on the specified terminal (yes or no).
:seas – Specifies whether or not SEAS maintenance related unsolicited messages are displayed on the specified terminal (yes or no).
:slan – Specifies whether or not SLAN maintenance related unsolicited messages are displayed on the specified terminal (yes or no).
:logintmr – the login timer. This parameter specifies the maximum time for logging on to the telnet terminal after selecting the terminal. This timer makes sure the user logs in with in the configured time and terminal does not remain idle. The value for this timer can be from 3 seconds to 600 seconds. An additional value none indicates that the user has an indefinite amount of time to login on the telnet terminal. The system default value for this parameter is none. This parameter can be specified only for telnet terminals (type=telnet).
:logouttmr – the logout timer. This parameter specifies the maximum time the telnet session remains open after the user manually or automatically logs out. The value for this timer can be from 0 to 1200 seconds. An additional value none indicates that the telnet session is never closed when the user logs out. The system default value for this parameter is none. This parameter can be specified only for telnet terminals (type=telnet).
:pngtimeint – the ping timer interval. This parameter specifies the amount of time that must pass before the IPSM initiates a new ping cycle. The value for this timer can be from 100 to 1200000 milliseconds. An additional value none indicates that pinging does not occur. The system default value for this parameter is none. This parameter can be specified only for telnet terminals (type=telnet) and EMSALM terminals (type=emsalm).
:pngfailcnt – This parameter specifies the number of consecutive ping fails that must occur before the telnet connection is dropped. The value for this timer can be from 1 to 10. The system default value for this parameter is 1. This parameter can be specified only for telnet terminals (type=telnet) and EMSALM terminals (type=emsalm).
The messages assigned to the output message groups defined by the traf, db, link, sa, sys, pu, uimrd, appserv, appss, card, clk, dbg, gtt, gws, meas, mon, mps, seas, and slan parameters are listed in Unsolicited Alarm and Information Messages Reference .
Certain UIMs (unsolicited information messages) can be assigned to the UIM Redirect output group or remain in their original output message group. The uimrd parameter of the chg-trm command and the on=uimrd and off=uimrd parameters of the chg-stpopts command determine which output groups these UIMs are assigned to and how the EAGLE handles them.
The on=uimrd parameter of the chg-stpopts command tells the EAGLE to put these UIMs in the unsolicited UIM Redirect output message group. If the off=uimrd parameter is specified with the chg-stpopts command, the messages remain in their original output message group. The on=uimrd parameter value of the chg-stpopts command is shown in the UIMRD row of the rtrv-stpopts output as the value yes. The off=uimrd parameter value of the chg-stpopts command is shown in the UIMRD row of the rtrv-stpopts output as the value no. The uimrd=yes parameter of the chg-trm command allows the specified terminals to receive unsolicited UIM redirect output messages.
Table 4-2 shows the combination of the values of both uimrd values and how the EAGLE handles the messages. The unsolicited output group message assignments are listed in Unsolicited Alarm and Information Messages Reference.
Table 4-2 UIMRD Parameter Combinations
| UIMRD value of the terminal | UIMRD STP option value | Action |
|---|---|---|
| No |
No (See Note 1) |
The UIMs remain in their original output message group and are output to terminals receiving messages from the original output message group. |
| No |
Yes (See Note 2) |
The UIMs are in the UIM Redirect output group but are not output to any terminal. |
| Yes |
No (See Note 1) |
The UIMs remain in their original output message group and are output to terminals receiving messages from the original output message group. Even though the No UIM redirect messages are output to any terminal. |
| Yes |
Yes (See Note 2) |
The UIMs are in the UIM Redirect output group and are output to terminals receiving unsolicited UIM redirect messages. |
| Notes:
|
||
If the type=vt320 or type=sccs parameters are specified, the value of the prty parameter cannot be none. The value of the prty parameter must be either odd or even.
The EAGLE requires at least two terminals assigned to the Security Administration command class. The terminal type of a terminal assigned to the Security Administration command class cannot be changed to these terminal types, printer (:type=printer) or none (:type=none) if the change would leave the EAGLE with only one terminal assigned to the Security Administration command class. The command class assignments of the terminal are shown with the rtrv-secu-trm command. If the terminal type is being changed to either printer or none, go to the Changing Terminal Command Class Assignments procedure and make sure that the command class assignment for the terminal being changed does not have the Security Administration command class assigned to it, or change the command class assignment of another terminal to include the Security Administration command class.
If the all=yes parameter and the traf, db, link, sa, sys, pu, uimrd, appserv, appss, card, clk, dbg, gtt, gws, meas, mon, mps, seas, or slan parameters are specified, for example, chg-trm:trm=1:all=yes:pu=no; all the message output groups are set to yes with the exception of the message output groups specified in the chg-trm command which are set to no. In this example, the value of all the message output groups is yes (all=yes) with the exception of the program update message output group which has the value no (pu=no).
If the all=no parameter is specified for a SEAS terminal (type=seas), all the output group values are changed to NO except for the SEAS output group. The SEAS output group value remains set to YES and this message is displayed.
SEAS Output Group is SET for SEAS terminal <terminal number>
The total value of the terminals’ baud rate cannot be greater than 172,032. If the total baud rate of the terminals exceeds 172,032, change the baud rates of the terminals so that the total baud rate is not greater than 172,032.
Only four terminals should be configured to receive unsolicited system maintenance messages (:sys=yes).
If the communication attributes (baud, sb, prty, and fc) or the terminal type (type) for the terminal are being changed, the terminal must be placed out of service with the rmv-trm command before the changes can be made.
If only the output message group or security (tmout, mxinv, dural) parameters are being changed, the terminal can remain in service when the chg-trm command is executed.
Terminal Types
There are nine terminal types that can be used on the EAGLE.
The VT320 type is the standard terminal used for entering commands, displaying command responses, displaying periodic system status information at screen specific locations, and scrolling unsolicited messages.
The PRINTER type is used with printers for recording UAMs, UIMs and echoed command responses.
The KSR type mimics older style teleprinters (that is, printers with a keyboard).
The SCCS type is used for some network monitoring and surveillance applications. SCCS terminals are the same as KSR terminals, except a pre-defined “start-of-message” character is added to indicate the beginning of a new command response or unsolicited message.
The NONE type is typically used to indicate unused terminals.
The MGMT terminal type, or management terminal, provides a machine to machine messaging interface between the EAGLE and the customer’s network to provide network surveillance.
The TELNET terminal type provides up to 24 IP based connections to the EAGLE’s user interface using a telnet client, in addition to the 16 RS-232 terminals. The telnet terminals are numbered from 17 to 40. The telnet terminals are configured automatically when the IP User Interface (Telnet) feature is enabled and activated, and when the IPSMs are configured in the database. The EAGLE can have 3 IPSMs, with each IPSM supporting eight telnet terminals. The baud, prty, sb, and fc parameters cannot be specified with the chg-trm command for a telnet terminal, but all other terminal parameters can be specified and changed for a telnet terminal. For terminals 17 to 40, the values for the type parameter can be only telnet, none, or emsalm.
Note:
If thechg-trm command is executed from a telnet terminal (terminals 17 to 40), only the output group parameters (all, traf, link, sa, db, sys, pu, uimrd, appserv, appss, card, clk, dbg, gtt, gws, meas, mon, mps, seas, slan) and the terminal type can be changed.The EMSALM terminal type provides an alarm monitoring capability that displays only UAMs and system alive messages generated by the EAGLE. UIMs and autonomous reports are not displayed on the EMSALM terminals, even if the output group settings for these terminals would allow these messages to be displayed on these terminals.
Caution:
EMSALM terminals can accept login requests and commands; however, these operations may interfere with the alarm monitoring functions of the EMSALM terminals and should be performed on another terminal.The EMSALM terminal type can be assigned to any terminal, serial (terminals 1 to 16) or telnet (terminals 17 to 40). When the terminal type is changed to emsalm, all the output message group settings for that terminal are set to yes, even if any of the output message groups were set to no before the terminal type change. These output message group settings can be changed, if desired. The communications attributes (baud, prty, sb, fc) and security parameter values (tmout, mxinv, dural) are not changed.
Caution:
It is recommended that all the output message group settings for an EMSALM terminal are set toyes. Changing any of the output message group settings to no could prevent alarm messages controlled by the output message group from being displayed on the EMSALM terminal.Caution:
If a terminal dedicated to measurements collection is configured (see the Configuring the Measurements Terminal for an EAGLE Containing 700 Signaling Links procedure), it is recommended that this terminal is not changed to an EMSALM terminal.When the terminal type is changed from emsalm to another terminal type, the output message group settings, communications attributes, and security parameter values are not changed.
When assigning the EMSALM terminal type to a serial terminal, the communication attribute (baud, prty, sb, fc), security (tmout, mxinv, dural), and output group (traf, db, link, sa, sys, uimrd, appserv, appss, card, clk, dbg, gtt, gws, meas, mon, mps, seas, slan) parameters values can be changed.
When assigning the EMSALM terminal type to a telnet terminal, only the security (tmout, mxinv, dural), and output group (traf, db, link, sa, sys, pu, uimrd, appserv, appss, card, clk, dbg, gtt, gws, meas, mon, mps, seas, slan) parameters values can be changed.
The SEAS terminal type is used to provide a path between the EAGLE and the CCS MR to support the SEAS over IP feature. The SEAS terminal type is not used in this procedure. To configure a terminal as a SEAS terminal, refer to the Configuring SEAS Terminals procedure.
Security Parameters
The monitoring of a terminal’s idle time (tmout) and the automatic logout function only applies to terminal types VT320 (type=vt320), KSR, (type=ksr), SCCS (type=sccs), and MGMT (type=mgmt). The tmout parameter can be specified with other terminal types, but it will have no effect. The system default value for the tmout parameter is 30 minutes. The tmout=0 parameter value allows the terminal to remain idle indefinitely without being automatically logged off.
To impose a temporary lockout of a terminal after a particular number of login attempt failures or a particular number of attempts to unlock a terminal have occurred, the mxinv and dural values for that terminal must be greater than 0.
The mxinv=0 parameter value prevents any temporary lockout of the terminal regardless of the number of successive failed login or unlock attempts that were made at the terminal. No messages are issued regarding the temporary lockout. This action applies even if the dural parameter value is greater than 0.
The dural=0 parameter prevents the terminal from being temporarily locked out. If the mxinv parameter value is greater than 0 and the dural parameter value is 0, the EAGLE issues messages concerning login failure threshold, but the terminal will not be locked out.
The value of the dural parameter can be expressed in seconds (0 - 59), minutes and seconds (0 - 5959), or hours, minutes, and seconds (0 - 995959). The value 999999 for the dural parameter disables the terminal, when the login failure threshold has been exceeded, for an indefinite period of time. A terminal that is disabled for an indefinite period of time is identified by the entry INDEF in the DURAL field of the rtrv-trm command output. A terminal disabled indefinitely can only be restored to service by inhibiting the terminal with the rmv-trm command, then placing it into service with the rst-trm command.
When the EAGLE is delivered to the user, the mxinv and dural parameters will be set to these values:
:mxinv = 5
:dural = 0100 (1 minute, 0 seconds)
The RTRV-TRM Output
The output of the rtrv-trm command is displayed in two parts. The first part displays the communication and security attributes of the terminal. The communication attributes of the terminal, BAUD, PRTY (parity), SB (stop bits), and DBTS (data bits), are displayed in the COMM field of the rtrv-trm output and are displayed in this format: BAUD–DBTS–PRTY–SB. The type of flow control used by the terminal is shown in the FC field. The security attributes of the terminal are shown in the TMOUT, MXINV, and DURAL fields. The second part of the rtrv-trm command output displays the types of unsolicited messages the terminal may receive. An example of the rtrv-trm command output is shown in this example.
rlghncxa03w 06-10-01 16:02:08 GMT EAGLE5 36.0.0
TRM TYPE COMM FC TMOUT MXINV DURAL
3 VT320 9600-7-E-1 SW 30 5 99:59:59
TRM TRAF LINK SA SYS PU DB UIMRD
3 NO YES NO YES NO YES YES
APP APP
TRM SERV SS CARD CLK DBG GTT GWS MEAS MON MPS SEAS SLAN
3 YES YES YES YES YES YES YES YES YES YES NO NO
In this example, terminal 3 is running at 9600 baud with 7 data bits, even parity, and 1 stop bit.
COMM and FC fields are not displayed in the rtrv-trm output. The following items are displayed for these terminals in addition to the security attributes and the types of unsolicited messages the terminal may receive. An example rtrv-trm output example follows the list. SECURE field. If the Eagle OA&M IP Security Enhancements feature is on, the terminal is secure. The entry yes is shown in the SECURE field. If the Eagle OA&M IP Security Enhancements feature is off, the terminal is not secure. The entry no is shown in the SECURE field. Controlled Feature Activation Procedures contains the procedures to enable and turn on, or turn off the Eagle OA&M IP Security Enhancements feature. LOGINTMR), logout timer (LOGOUTTMR), ping time out timer (PNGTIMEINT), and the ping fail count (PNGFAILCNT) values.
rlghncxa03w 06-10-01 16:02:08 GMT EAGLE5 39.0.0
TRM TYPE LOC TMOUT MXINV DURAL SECURE
30 TELNET 1204 60 0 00:00:00 no
TRM LOGINTMR LOGOUTTMR PNGTIMEINT PNGFAILCNT
(sec) (sec) (msec)
30 none none none 1
TRM TRAF LINK SA SYS PU DB UIMRD
30 YES YES YES YES YES YES YES
APP APP
TRM SERV SS CARD CLK DBG GTT GWS MEAS MON MPS SEAS SLAN
30 YES YES YES YES YES YES YES YES YES YES NO NO
Using Telnet Terminals in Place of Serial Terminals
If the Eagle OA&M IP Security feature is disabled and turned off , serial terminals must be connected to the EAGLE and provisioned in the database because Security Administration commands cannot be executed from a telnet terminal.
If the Eagle OA&M IP Security feature is enabled and on, Security Administration commands, in addition to all other commands, can be executed from a telnet terminal only if the Eagle OA&M IP Security feature is enabled and on. The ability to execute commands from a particular terminal is dependent on the terminal command class assignments for that terminal. Even with the ability to execute most EAGLE commands from a telnet terminal, it is recommended that at least two serial terminals remain connected to the EAGLE. The act-echo, lock, and unlock commands cannot be executed from a telnet terminal. These terminals should be configured with at least Security Administration command class privileges.
By having serial terminals connected to the EAGLE, the user would still have access to the EAGLE in the event of a telnet terminal connection failure.
Upgrades of the EAGLE from a telnet terminal are not supported. When the EAGLE is upgraded, the MASPs are upgraded first, followed by the various cards in the EAGLE. The cards are upgraded by taking the cards out of service, then placing the cards back into service. When the IPSMs are taken out of service, the telnet sessions running on the IPSMs are disabled. This can result in losing the telnet terminal connection to the EAGLE. The Expanded Terminal Output Groups feature can create a situation where UIMs required for the upgrade would not be displayed on the same telnet terminal that initiated the upgrade. The upgrade would be difficult to complete if the UIMs generated during the upgrade are not displayed on the same telnet terminal that initiated the upgrade.
The EAGLE upgrade procedure recommends that some method to capture command input and output during the upgrade process is used. The telnet terminals do not support capturing the input and output, nor can the EAGLE’s act-echo command be used on a telnet terminal. Because of this limitation, the upgrade procedure should not be executed from a telnet terminal.
For any EAGLE release, whether the Eagle OA&M IP Security feature is enabled or not, if applicable, Kermit file transfers, required for the Security Log feature, are not supported from telnet terminals. The Kermit file transfers can be performed only from a serial terminal.
Figure 4-10 Changing Terminal Characteristics
Sheet 1 of 6
Sheet 2 of 6
Sheet 3 of 6
Sheet 4 of 6
Sheet 5 of 6
Sheet 6 of 6
