Visara Master Console Center Administration Guide P/N 707130-001
Technical Support Contacting the Visara Intellicenter For US domestic customers, Visara provides technical support through its Intellicenter, 8:30 - 5:00 (ET) Monday through Friday at 888-542-7282. Calls outside these hours are handled by automatic pager, so expect a delay. You can also call through our switchboard at 919-882-0200. For support outside the US, please contact the company that has sold the product to you. Notices Copyright © 2007 by Visara International.
Contents Technical Support ..................................................................................... 2 Contacting the Visara Intellicenter ............................................................ 2 Notices...................................................................................................... 2 List of Figures ............................................................................................... 9 List of Tables .........................................................
Visara Master Console Center MCC Configuration Files............................................................................. 44 fonts.cfg: Font Configuration................................................................... 44 keymap.cfg: Keyboard Mappings............................................................ 45 osgroup.cfg: OS Groups ......................................................................... 45 security.cfg: User Security .........................................................
Contents Valid Keys............................................................................................. 101 Example................................................................................................ 101 MVS Configuration.................................................................................... 102 Valid Keys............................................................................................. 102 MVS Agent Section.......................................................
Visara Master Console Center Creating New Login Users .................................................................... 132 Adding an Existing Unix User as a MCC User ...................................... 134 Changing a Login User’s Password...................................................... 135 Deleting a Login User ........................................................................... 136 Configuring login Groups ......................................................................
Contents Icsmaster_YYYY-MM-DD: MCC Startup and Shutdown Error Log....... 180 messages.log: Filtered Message Log ................................................... 180 newmsg.log: New Messages Log ......................................................... 181 software.log: Software Messages Log .................................................. 182 system.log: Host System Messages Log .............................................. 183 unit.log: I/O Unit Messages Log..........................................
Visara Master Console Center To Display a Printer Console ................................................................ 216 Implementation Notes ........................................................................... 217 Ataman Telnet .......................................................................................... 218 Appendix A Valid Color Names.................................................................. 219 Index......................................................................
Contents List of Figures Figure 1 Exceed System Administration Settings for the MCC ................................. 36 Figure 2 Exceed System Transport Settings for the MCC......................................... 36 Figure 3 Exceed System Other Settings for the MCC ............................................... 37 Figure 4 PS/2 Keyboard............................................................................................. 38 Figure 5 3270 North American Keyboard ..................................
Visara Master Console Center List of Tables Table 1 X Terminal Monitor Settings.......................................................................... 27 Table 2 xp.cnf MCC Terminal Settings ...................................................................... 29 Table 3 Keybindings in both us3270.kbf and mf3270.kbf Files ................................. 35 Table 4 Keybindings in mf3270.kbf File .....................................................................
Chapter 1 Introduction This chapter discusses: The purpose of this guide. Users of this guide. Organization of this guide. Manual conventions used. Starting the MCC. Restarting the MCC. Shutting down the MCC.
Visara Master Console Center Purpose of This Guide This guide describes how to administer the Master Console Center (MCC). Users of This Guide This manual is primarily intended to be read by the administrator of the MCC. The following list details the skills and experience required by the administrator: Trained in MCC use and administration. Unix experience, preferably Linux. Basic network concepts and administration knowledge. X-windows familiarity.
Chapter 1 Introduction Organization of this Guide This guide is organized into the following chapters: Topic Page Chapter 1 Introduction discusses the purpose of this guide, users of this guide, manual conventions, starting, restarting, and shutting down the MCC. 11 Chapter 2 Administering the License Key describes how to install and maintain the license key that is required for the MCC to function correctly.
Visara Master Console Center 14 Chapter 14 Remote Access to the MCC discusses the gwcharcons facility which enables dial-in and telnet access to the consoles configured in the MCC. 199 Chapter 15 Troubleshootingdiscusses problems that may occur, and tools and techniques for recovering the system. 205 Chapter 16 Integrating Other Products with the MCC discusses integrating Ataman Telnet and BMC PATROL with the MCC. 215 Appendix A Valid Color Names discusses the colors and RGB values.
Chapter 1 Introduction The MCC Documentation Set In addition to this manual, you may need to refer to other manuals in the MCC documentation suite. These are: Software Installation Guide. Provides instructions for the initial installation and configuration of the MCC software. Getting Started. Contains an initial overview of the MCC, and its applications. Operations Guide. Contains procedures for day-to-day operation of the MCC, including selecting consoles, and managing alerts and messages.
Visara Master Console Center Manual Conventions The names of menus, menu options, and window controls are in bold type. Also, text that you type is a different font. For example: Type boot and press the Return key. Text that is placed within the <> symbol should be replaced (including <>) with the appropriate text. For example: ipaddr Substitute the MCC system’s IP address. hostname Substitute the MCC system’s host name.
Chapter 1 Introduction This stops all MCC programs, including the core MCC programs. Note: To only logout of the interactive user display, not the MCC system, choose the Logout option from the User menu. 3. When the MCC login window reappears, login as any user. This will also automatically start the MCC core programs. To “cycle” only the MCC user interface programs: Administration Guide 1. Logout of the system by selecting the Logout option on the user display. 2. Login again.
Visara Master Console Center Shutting Down the MCC Rebooting the MCC is rarely necessary. Changes to the MCC configuration require a MCC software restart only. Generally, the MCC is powered down only for hardware installation, hardware maintenance, or to physically relocate the MCC CPU. Before Shutting Down the MCC The administrator should follow the following procedure before shutting down the MCC: 1.
Chapter 1 Introduction Note: If you are going to turn the CPU back on again at this point, wait at least 60 seconds. This allows time for all of the internal devices to reset. 3. Power off all remaining equipment, for example, the system console, and switches. 4. Power off the power supply unit. Structure of the MCC Directories All of the subdirectories for the MCC are located in /usr/ics/. Some of the subdirectories include: Config, which contains the configuration files.
Chapter 2 Administering the License Key The MCC software requires installation of a license key file on your system before it can run. The file is customized for a specific site and machine, and cannot be used elsewhere. In certain cases (for example, evaluation copies), the license is only valid for a limited period, and the MCC software will cease to operate if the license is not renewed. The MCC can be shut down if the license has expired, but it will not be possible to restart it.
Visara Master Console Center MaxAllowedEBusConsoles specifies the maximum number of EBus card ports. MaxAllowedIConConsoles specifies the number of Visara Icon 5250 consoles that are allowed. MaxAllowedTelnetConsoles specifies the number of telnet consoles allowed. MaxAllowedCommandConsoles specifies the number of command consoles allowed. MaxAllowedTN3270Consoles specifies the number of 3270 sessions or consoles allowed. MaxAllowedTN5250Consoles specifies the number of TN5250 sessions aloowed.
Chapter 2 Administering the License Key If the License Key is Invalid or Expired If the MCC cannot start because of an invalid or expired license key, error messages appear in two locations, stderr, and the log/icsexec.log file. The startup script also displays a dialog window "MCC license is not valid" when the program cannot be started for one of these reasons. Contact Visara Technical Support immediately to resolve the problem.
Chapter 3 MCC Terminal Configuration This chapter discusses: Setting up the MCC Terminal. Customizing the MCC Terminal. Displaying hosts on the XDMCP. Disabling the pickup of other servers on the same network. Having an X terminal monitor which gateway to use. Having multiple xp.cnf configuration files. Specifying primary and secondary boots. Using X Terminal emulation software.
Visara Master Console Center Setting up an X Terminal To setup the X terminal: Caution: The X Terminal monitor weighs over 70 lbs. 2. Follow the manufacturer’s installation instructions included with unit for correctly cabling the unit. 3. Power on the monitor and the base unit. 4. While the blue boot screen is displayed, press the space bar to stop the X terminal from attempting to boot. If this is not successful, power off the X terminal and retry. The BOOT> prompt appears.
Chapter 3 MCC Terminal Configuration Token Ring X terms: No option available. X terminal Test Menu: bp /usr/tekxp/boot/selftest.500 10. Set the boot method: Normal: bm nfs 8192 Over shared (congested) or small fractional T1: bm nfs 1024 11. The default and recommended resolution is 1600 x 1280.
Visara Master Console Center 18. Click the Configuration Summaries option. A drop-down list appears. Select the X Environment option. Confirm the following settings: a. Retain X Settings: NO b. Host Connect Method: XDMCP Direct c. Enter your server name in the XDMCP Server text box: 19. Click the Return to Main Menu button. 20. Click the Network Tables and Utilities button. A drop-down list appears. Select the NFS Mount option. a. Enter :/usr in the File System Name text box.
Chapter 3 MCC Terminal Configuration Customizing the MCC Terminal It may be necessary to customize the MCC terminal settings for each installation site if for example: Multiple locations are involved in the configuration. The MCC servers are on subnets other than the MCC terminal’s. The config file for the customizations is /usr/tekxp/boot/config/xp.cnf. Each section in the file contains all of the instructions provided by Tektronix. Enable the following settings in xp.
Visara Master Console Center where is the MCC system’s IP address, and is the MCC system’s host name. The gateway.tbl should contain a list of all gateways (routers) at all sites in the organization. Each gateway definition contains the target network address and the IP address of the gateway to use for that network, in the following format: where is the network address of the remote network (for example, 200.100.50.
Chapter 3 MCC Terminal Configuration xdmcp_menu_entry PREFERRED where is the system’s host name, and PREFERRED (optional) causes the specified MCC system to always be at the top of the list.
Visara Master Console Center Specifying Primary and Secondary Boot Hosts The primary boot host is specified on the X terminal with the IH command. The primary host can also be specified in the xp.cnf file, but this is not recommended. If specifying an optional secondary boot host is possible, it must be specified in the xp.cnf file. boot_method_2 NFS 8192 boot_host_name_2 ‘’ boot_path_2 ‘/usr/tekxp/boot/os.
Chapter 3 MCC Terminal Configuration X Terminal Emulation Software The MCC software is designed to work with the Tektronix X terminal. However, there are various software packages, such as Hummingbird Exceed, NetManage, and Reflections/X available for desktop PCs that allow the user to emulate X terminal function. Visara cannot guarantee the functionality of any third party X terminal emulation software with the MCC.
Visara Master Console Center Microsoft Windows requires a keyboard driver for 122-key keyboards, which may be difficult to find. Windows does not ship with a 122-key driver, and may use the 83/84 XT keyboard driver as the default. Configuring a 3270 Keyboard After installing the 3270 keyboard, test the special keys such as PA1 and ErEOF. If they do not function correctly, check the following: Ensure the proper keyboard driver is installed in Microsoft Windows.
Chapter 3 MCC Terminal Configuration List of Significant Keybindings Scancode Keycap Exceed X Mapping 76 Clear Clear 5A PA1 F30 6D ErEOF F27 Table 3 Keybindings in both us3270.kbf and mf3270.
Visara Master Console Center 1. Disable the button in the top right corner of the Exceed window, to prevent users from closing a console window without logging out correctly. Launch xconfig from the Exceed program menu, choose Settings — System Administration. Set the options in the resulting window as follows: Figure 1 Exceed System Administration Settings for the MCC Note: 'X Client Native Window Manager Exit' is in the Disabled box. This is NOT the default setting. 2.
Chapter 3 MCC Terminal Configuration 3. In the win.ini file in the Windows installation directory (WinNT or Windows, not the Exceed directory), add the following if an Exceed section does not exist: [exceed] custom=1 If an Exceed section already exists, add 'custom=1' if necessary. 4. If the MCC is started through the Exceed xstart application, launch the Exceed XStart application from the Start Menu, then click the Other button in the upper right corner.
PS/2 Keyboard (101 Key IBM version, manufactured by Lexmark) Esc ~ ` ! 1 F1 F2 F3 F4 @ 2 # 3 $ 4 % 5 Q Tab W A Caps Lock S Z Shift E Ctrl R D X F5 ^ 6 T F C F6 & 7 Y G V F7 * 8 U H B F8 I J N ( 9 ) 0 O K F10 _ - + = { [ P : ; L < , M F9 > .
3270 North American Keyboard (122 Keys) Attn SysRq CrSel F13 F14 F15 F16 F17 F18 F19 F20 F21 F22 F23 F24 F1 F2 F3 F4 F5 F6 F7 F8 F9 F10 F11 F12 ~ ` Clear Pause Erinp ExSel ErEOF SetUp Record Print Copy Play Ident Test | 1 Q Tab Caps Lock Shift Reset @ 2 W A > < # 3 E S Z $ 4 % 5 R D X ¬ 6 T F C & 7 Y G V * 8 U H B I J N ( 9 ) 0 O K M _ ! ¢ P : ; L , } { ? / .
Chapter 4 MCC Configuration File Management This chapter discusses: Directory structure. Syntax of the configuration files. MCC Configuration Files. Most configuration files are processed only at the startup of the MCC. Caution: If changes are made to any of the configuration files, the MCC software must be cycled (stopped and restarted). Any active users should log out before recycling the MCC, or they may see unpredictable or inaccurate data.
Visara Master Console Center [cpu 9021] where Left bracket “[” begins the definition of the section header. CPU is a section header keyword. 9021 is the unique name (within all cpu sections) given to the section (spaces are allowed). Right bracket “]” ends the definition of the section header. Notes: The term “section name” refers to only the unique name in the section header. Section names are case-insensitive.
Chapter 4 MCC Configuration File Management Keys Keys are keywords or user-defined field names. They are on the left side of the equation. For example: os=Prod2 where OS is a keyword in a cpu section. Equals “=”ends the key and begins the value. Prod2 is the value of the key. Note: Keys are case-insensitive. Values Values are on the right side of the equation and, depending on the section, contain one or more value definitions.
Visara Master Console Center MCC Configuration Files Add or modify MCC configuration files from the Master window Administration menu Configuration option. Table 5 lists configuration files for the MCC: File Name Menu Option Page fonts.cfg Fonts 44 keymap.cfg Emulator:Keyboard Index 45 objmgr.cfg Object Manager 47 osgrp.cfg OS Groups 45 security.cfg Security 45 snmp.cfg SNMP Setup 45 status.cfg Status Colors 53 system.cfg System 46 charset.cfg None (character sets) 58 vt100.
Chapter 4 MCC Configuration File Management keymap.cfg: Keyboard Mappings The keymap configuration file contains data necessary for the various hardware and OS consoles defined in the system.cfg file. Its purpose is to define the keymap file for X terminal vendors, since manufacturers can implement different keycode values for each key on the keyboard.
Visara Master Console Center system.cfg: MCC System The system configuration file contains two major definitions: The layout of the System Summary window (the organization of the System Summary window icons). The host port definitions, including the physical connections to the host equipment (for example, mainframes, routers, and Unix servers). Note: Some commands listed in the Scripting Guide, such as ICON( ), are case-sensitive. An icon’s definition in system.cfg must match its usage in the command.
Chapter 4 MCC Configuration File Management [sw taskname] fieldname1=5 fieldname2=“CAT” fieldname3=UP The TaskName can be a maximum of 11 characters. objmgr.cfg: Object Manager The object manager configuration file contains information to define objects to the MCC Object Manager. This includes Task Manager (TaskMan) options, colors, color rules, object types, object fields, and pick lists. Options Section The options section of the objmgr.cfg file defines options to the object manager system.
Visara Master Console Center The last number is the status number to propagate to the OS level for the color combination. The number corresponds to a status number in status.cfg, and therefore must be between ‘1’ and ‘16’. Note: A name of “normal” must always exist. The MCC uses its definition as the default (or “normal”) display color. In the example below, the colors for the “normal” combination are white letters on a pale green background.
Chapter 4 MCC Configuration File Management current:up,desired:up current:up,desired:down = *:normal = *:normal, desired:warning [colorrules unixcolors] current:up,desired:up current:up,desired:down current:down,desired:up current:unknown,desired:up = = = = *:normal *:normal, desired:warning *:error, *:normal, current:warning List Section The list section defines a list of values (an enumerated list). A list in the definition of the list field type defines the valid entries for the list field.
Visara Master Console Center Fields Section The fields section defines a set of fields. A set of fields is used for each object type. The field “taskname” is automatically created by the system and contains the name of the task. This field cannot be changed. The left side of the equation is the field name. The field name may be up to 32 characters. The right side of the equation is a comma-separated list of attributes of the field definition in the format: “attribute:value”.
Chapter 4 MCC Configuration File Management Notes: A “desired” field must be defined for the Set Desired Status option to function correctly in the OS task list (TaskMan). The fields “tmmode” and “moveable” must be defined for the moving software between OS’s option to work in the OS task list (TaskMan). Refer to Moving Tasks between Operating Systems on page 52. Task Manager can track the program which last changed the “desired” field. This is useful for monitoring scripts in certain environments.
Visara Master Console Center Moving Tasks between Operating Systems TaskMan can move tasks from one OS to another. This feature is useful when a particular task may be handled by more than one OS, and the OS currently serving the task has failed in some way. Through careful setup and scripting, the task can be moved automatically to another OS using TaskMan. The relevant script(s) handle startup of the task on the new OS.
Chapter 4 MCC Configuration File Management For each moveable task, one OS should be marked with a moveable status of Primary; this is the OS where the task primarily resides. All other OSs should be marked with a moveable status of Zombie and a tmmode of Zombie; these are the OSs to which the task could be moved. status.cfg: Status Colors The color definition file links a color to a status number. Each MCC object and message has a status that affects the object’s color.
Visara Master Console Center Table 8 lists default status colors: Status Foreground Color Background Color 1 White Red 2 White VioletRed 3 Black HotPink 4 Black Orange 5 Black Yellow 6 Black Gold 7 Black White 8 Black LightSkyBlue 9 Black PaleGreen 10 Black Aquamarine 11 Black Cyan 12 Black Gray 13 Black LightSteelBlue 14 White SteelBlue 15 White Blue 16 White Brown Table 8 status.cfg file Default Color Options The Status.
Chapter 4 MCC Configuration File Management GCL Status Constants There are five status numbers represented as manifest constants in GCL, which should not be changed. They are listed in Table 9: Status Color Manifest Constant 1 Red STATUS_ERROR 4 Orange STATUS_WARNING 6 Gold STATUS_INPROCESS 9 PaleGreen STATUS_NORMAL 14 SteelBlue STATUS_DOWN Table 9 GCL Status Constants Colors If these colors are modified, take care to pick colors that are meaningful for the status.
Visara Master Console Center icsmaster.txt and masterwnd.txt: Configuring Shutdown ICSMASTER is the master MCC program that starts and stops all MCC daemon programs. Masterwnd is the program associated with the master GUI window that is used to view active users, log in/out, and administer the MCC. When the MCC is shut down, ICSMASTER checks that all MCC programs terminate normally. At a normal MCC shutdown, the file $ICSHOME/config/icsmaster.
Chapter 4 MCC Configuration File Management User Defined Message File Each message in a Log Display window can be linked by a keyword to a User Defined Message (UDM). UDMs are defined in the UDM file, and each consists of a keyword and up to 250 message lines. To open the User Defined Messages file for viewing or modification, use the Master Window's Administration— Configuration-User Messages menu option.
Visara Master Console Center charset.cfg Character Set File The charset.cfg configuration file contains data necessary for emulation of a keyset and display set in sessions with the host systems attached to the EBUS. The associated host systems are defined in the system.cfg file. Direct editing of these data files is not possible, but it is possible to verify their contents. The values for keyset and dispset correspond to files of the same name as the value in /usr/ics/ebus.
Chapter 4 MCC Configuration File Management Softkey Files Softkeys can be defined to allow the user to send keys that are not obvious or present on the MCC keyboard. Examples include the “Start” and “Stop” keys on mainframe consoles, or the “Break” key on RS232/VT100 consoles. Refer to Chapter 3 Selecting Consoles in the Operations Guide for information on selecting and sending softkeys. Default softkey files are provided for most console types, as listed in Table 11.
Visara Master Console Center Softkeys Mnemonics List Table 12 Key Mnemonics Supported by MCC Software lists all keys that are supported by the MCC software and the keyboard emulations that support each key. Not all the keys listed are included in the default files provided; refer to Adding a New Key on page 67 to enable a key that is listed, but not included in the default files. Note: When "3270" is shown in the table, the key is supported in all emulations of the 327x protocol family.
Chapter 4 MCC Configuration File Management Key Mnemonic (for Action key) Description Emulations/Systems supporting this key ClearDsp HP7009x ClearLine HP7009x CloseBrace } All CloseBracket ] 3151, VT100, and VT220 Cmd Comma 3080, AS/400 , All CommReq 3270 converged Copy 3270 converged, 4381 CrSel Cursor Select 3270 DeleteChar HP7009x DeleteLine HP7009x DeleteWrap HP7009x DelWord Delete Word 3270 converged Delete Delete All Diag 3270 converged DMsgBkwd 3080 DMsgFrwd
Visara Master Console Center Key Mnemonic (for Action key) Description Emulations/Systems supporting this key Exclaim ! All F1 through F12 Same as PF1 through PF12 All F13 through F24 Same as PF13 through PF24 3270, AS/400, VT100, VT220 Find FldMark Field mark 62 3270 AS/400 Forward 3080, 3090, 3270 converged, 3151 HardReset HP7009x Hex AS/400 Home 3080, 3090, 3270, 4381, and AS/400 HomeDown HP7009x HomeUp HP7009x Ident 3080, 3090, 3270, 4381 Index 3090, 3151 InitTerm HP700
Chapter 4 MCC Configuration File Management Key Mnemonic (for Action key) Description Emulations/Systems supporting this key Notes numeric keypad 1 KP_2 VT100 and VT220 numeric keypad 2 VT100 and VT220 KP_3 VT100 and VT220 numeric keypad 3 VT100 and VT220 KP_4 VT100 and VT220 numeric keypad 4 VT100 and VT220 KP_5 VT100 and VT220 numeric keypad 5 VT100 and VT220 KP_6 VT100 and VT220 numeric keypad 6 VT100 and VT220 KP_7 VT100 and VT220 numeric keypad 7 VT100 and VT220 KP_8 VT100 and V
Visara Master Console Center Key Mnemonic (for Action key) Description Emulations/Systems supporting this key LastCmd Last command 3090 and 3151 Left Move cursor left All LeftDbl Move cursor left two positions 3080, 3090, 3270, 4381, AS/400 LineDisc 4381 Menu HP7009x ModeSel 4381 Msg 3080 Newline AS/400 Next Screen VT220 NextSess Move to next session AS/400 NotSign ¬ 3080, 3090, 3270, 4381 OpenBrace { All OpenBracket [ VT100, VT220, 3151, AS/400, HP7009x PA1 Program Atte
Chapter 4 MCC Configuration File Management Key Mnemonic (for Action key) Description Emulations/Systems supporting this key Reset 3080, 3090, 3270, 4381, AS/400, 3151 Restart 3080, 3090, 3151, HP7009x Return All Right 3090, 3151 RightArrow Move cursor right All RightDbl Move cursor right two positions 3080, 3090, 3270, 4381, AS/400 ScrollDown HP7009x ScrollUp HP7009x Select HP7009x, VT220 Session1 Switch to session 1 AS/400 Session2 Switch to session 2 AS/400 Session3 Switch
Visara Master Console Center Key Mnemonic (for Action key) Description Emulations/Systems supporting this key Notes Perle box Stop 3080, 3090, 4381, 3151, HP7009x SvPCE 3090 SwapCons Swap Console 3090, 3151 SysReq System Request 3270, AS/400 System HP7009x Tab All Test 3080, 3090, 3270, 4381, AS/400 TOD Time of day 3080, 3090, 3151 Toggle Toggle status indicators AS/400 User HP7009x UpArrow Move cursor up All ViewLog View log file 3090, 3151 Table 12 Key Mnemonics Supporte
Chapter 4 MCC Configuration File Management action=KP_Enter However, because the action= is unchanged, KP_Enter is still sent to the host. Adding a New Key To add one of the keys listed in Table 12 Key Mnemonics Supported by MCC Software to the available softkeys, edit the relevant .bank file to include the required key mnemonic and the label for the key. For example, to add a caret (circumflex) key to the VT100 keypad softkeys, make the following entry in the keypad.
Visara Master Console Center top=function left=arrows right=form bottom=form 68 © Visara International 2007
Chapter 4 MCC Configuration File Management Example of function.bank Softkey File An example of the VT100 function.bank file is shown below: [sizes] width=60 height=40 # Row 0 -- F1-F12.
Visara Master Console Center [key] label=F10 action=F10 [key] label=F11 action=F11 [key] label=F12 action=F12 # Row 2 - F13-F24 [key] location=0,1 label=F13 action=F13 [key] label=F14 action=F14 [key] label=F15 action=F15 [key] label=F16 action=F16 [key] label=F17 action=F17 [key] label=F18 action=F18 [key] label=F19 action=F19 70 © Visara International 2007
Chapter 4 MCC Configuration File Management [key] label=F20 action=F20 [key] label=F21 action=F21 [key] label=F22 action=F22 [key] label=F23 action=F23 [key] label=F24 action=F24 Administration Guide 71
Visara Master Console Center Example of arrows.bank Softkey File An example of the VT100 arrows.bank file is shown below: [sizes] width=60 height=40 # NOTE: Strings in this file were converted to actions so the # softkeys would work correctly in both keypad and non-keypad # modes.
Chapter 4 MCC Configuration File Management Example of keypad.bank Softkey File An example of the VT100 keypad.
Visara Master Console Center [key] location=3,1 label=/ action=KP_Divide [key] location=0,2 label=7 action=KP_7 [key] location=1,2 label=8 action=KP_8 [key] location=2,2 label=9 action=KP_9 [key] location=3,2 label=+ action=KP_Add [key] location=0,3 label=4 action=KP_4 [key] location=1,3 label=5 action=KP_5 [key] location=2,3 label=6 action=KP_6 [key] location=3,3 label=action=KP_Subtract 74 © Visara International 2007
Chapter 4 MCC Configuration File Management [key] location=0,4 label=1 action=KP_1 [key] location=1,4 label=2 action=KP_2 [key] location=2,4 label=3 action=KP_3 # This should be double-height [key] location=3,4 size=1,2 label=Enter action=KP_Enter [key] location=0,5 size=2,1 label=0 action=KP_0 [key] location=2,5 label=. action=KP_Decimal The Reset – Reset Telnet Connection section provides a reset button that may be used in the unlikely event that a telnet server hangs.
Chapter 5 MCC system.cfg Configuration File This chapter defines the layout of the MCC system configuration file, which includes the following sections: Room section Group section CPU section OS section Console section Printer section Unit section MVS Agent This file must be customized for each MCC installation. Caution: If changes are made to any of the configuration files, the MCC software must be cycled (stopped and restarted).
Visara Master Console Center Section Name Length Table 13 lists the sections of the system configuration file, and the maximum length (number of characters) permitted in the section name.
Chapter 5 MCC system.cfg Configuration File Valid Key Requirements Each section includes a list of keys that may be required in the system.cfg section. Some keys that are listed are optional. The Required? column defines whether this key must be included in this section or if the key is optional: Yes Section must include this key. No This key is optional. The Qty column defines the minimum number of keys to include in this section: 1 Section must have at least one key.
Visara Master Console Center Room Section The room section defines the top level of the System Summary window. The room section name determines the name of the room icon. The room name must be eight characters or less. The CPU icons and the group icons are displayed left to right in the order in which they are defined in the file. CPUs defined within groups should not also be defined in the Room section. See CPU Section on page 82 for more details.
Chapter 5 MCC system.cfg Configuration File Group Section The group section defines a group of CPUs and other groups. This allows creation of subgroups, creating a hierarchy. The group section name determines the name of the group icon. The group name must be eight characters or less. Note: CPUs defined within groups should not also be defined in the room section. See CPU Section on page 82 for more details.
Visara Master Console Center CPU Section The CPU section defines a CPU, its console, and its operating systems. The CPU section name determines the name of the CPU icon. The CPU name must be unique and eight characters or less. If a CPU name appears in a group, it cannot be used in the room. For example, having the CPU HP9000 in both a group and a room is invalid. The system.cfg file can contain a maximum of 600 CPU sections.
Chapter 5 MCC system.
Visara Master Console Center OS Section The OS section of the MCC system.cfg file defines an OS, its type, its consoles, and software lists. The OS section name determines the name of the OS icon. VM and server systems such as Unix machines do not require a printer defined, as neither has the concept of a printer console as does MVS. However, a printer must be defined if the MCC system is using the “Q” series of commands in scripts (refer to the QREAD command in the Scripting Guide for more details).
Chapter 5 MCC system.cfg Configuration File hostname No 0 or 1 Network host name for the system. Typically, this will be the same as the OS name, but the true network host name may differ due to character limitations. If you use the MCC/BMC PATROL integration product, the host name must refer to the name of the host as reported by BMC PATROL agents. The MCC OS name refers to the name of an OS inside the MCC. mvsagent No 0 or 1 Associates an MVSAGENT configuration with the OS.
Visara Master Console Center Example [os PROD] type=mvs console=PROD OS printer=PROD PRN swlist=config/swlist/prod [os AIX325-320H] type=unix console=320H-RS232 printer=320H-RS232 swlist=config/swlist/AIX325-320H [os AIX325-M43] type=unix console=M43-RS232 swlist=config/swlist/AIX325-M43 [os op2] type=unix hostname=op2 console=Test Console swlist=config/swlist/test0 [os SHORT] type=unix hostname=really_long_hostname console=Test Console swlist=config/swlist/test0 [OS OP1] type=unix hostname=op1 console=Te
Chapter 5 MCC system.cfg Configuration File [os QuuxOS] type=mvs console=Quux OS printer=Quux PRN mvsagent=QuuxAgent Console Category Section It is possible to assign console categories to each console on the Console Selection window. Each console can have no categories or several categories assigned to it. Category names listed in the console category section are case-sensitive, and display in exactly the format typed in the Console Selection window.
Visara Master Console Center Console Section The console section defines an OS console connection. The console section name determines the name of the console emulator icon. Console names can be a maximum of 30 characters. Consoles types may be: Telnet TN3270 TN5250 ICON Command Notes: When adding consoles or changing console names, be sure to update the security group profiles.
Chapter 5 MCC system.cfg Configuration File Common Console Section Keys Table 18 lists the keys common to all console definitions: Key Required? Quantity Description interface Yes 1 The type of interface. Valid entries are ICON, Command, Telnet. lock_timeout No 0 or 1 The number of seconds to wait before unlocking the terminal and discarding user typed text. If set to 0, the terminal will never automatically unlock. If not specified, the default is 30 seconds.
Visara Master Console Center ICON Section The ICON section of the system.cfg file defines an ICON interface unit, its type, and IP address. The ICON section name determines the name of the ICON console icon button. The ICON header name must be 11 characters or less. The name after the ICON tag must be unique. Key Required? Quantity Description type Yes 1 The type of ICON Interface Unit.
Chapter 5 MCC system.cfg Configuration File ICON Console Type Table 37 outlines the valid key requirements for the ICON console type, in addition to those keys listed in Common Console Section Keys, Table 18 Console Section, Common Keys, Page 89: Key Required? Quantity Description iotype Yes 1 Matches an ICON name tag in the ICON section.You may always just use XT in this field. Host Yes 1 Host name that the iCON has been configured to use.
Visara Master Console Center Telnet Console Type The telnet section defines a telnet console session. The telnet section name determines the name of the console emulator icon. Valid Keys Table 21 lists the valid key requirements, in addition to those keys listed in Common Console Section Keys on page 89: Key Required? Quantity Description iotype Yes 1 The interface type—VT100, VT220, as400perle, or hp700/92, 3270, 3278, 3278-2, 3278-3, 3278-4, 3278-5.
Chapter 5 MCC system.cfg Configuration File Telnet service Key Values If not specified, the service key defaults to 23, the default telnet port. Other ports that allow telnet connections can be specified using this key. Example [console DEC-UNIX-Telnet] interface=telnet iotype=VT100 host=localhost days_history=1 audit=yes [console PS340-telnet] interface=telnet iotype=VT100 host=206.144.7.
Visara Master Console Center iotype=VT100 PingThreshold=20 PingResponse=30 Note: Use interface=telnet-standardclient in place of interface=telnet to select the DEC telnet client. Both interface= specifications may be included in the same system.cfg file if connecting to different console types. Refer to Chapter 3 Selecting Consoles in the Operations Guide for information on using HP700 consoles.
Chapter 5 MCC system.cfg Configuration File Printer Section The printer section defines a printer console connection. The printer section name determines the name of the printer emulator icon. Printer consoles can be defined for ICON, and telnet sessions. The printer session must have the same parameters (for example, stty_flags, newline specification, and operating mode) as the related glass console session, or error messages will be generated. .
Visara Master Console Center Command Console The Command Console section defines a command console that runs a defined command or Unix shell script when selected. For example, the Command Console can be used to: Provide Windows NT console consolidation using the VNC product (see http://www.uk.research.att.com/vnc) and Netscape Navigator. The VNC executable must be configured on the NT workstation or server.
Chapter 5 MCC system.cfg Configuration File Examples The following example provides console consolidation of a Windows NT server through Netscape Navigator installed on the MCC. The VNC executable must be installed on the NT server. [console NTServer] interface=command command=netscape http://NTServer:5800 categories=Command The following example displays the index of the MCC manuals in a Netscape Navigator browser on the MCC workstation.
Visara Master Console Center Use exec to have ksh execute the command without forking. This can be included in the script or in the comand as shown in the preceding example. For additional examples, refer to examples/commandconsoles/reuse-netscape and examples/commandconsoles/launch-x-vnc. Include the command in a script that forwards signals to the child process. Refer to examples/commandconsoles/map-signals for an example script. Using Exec In most cases, exec can be specified in the command.
Chapter 5 MCC system.cfg Configuration File VNC (Virtual Network Computing) is a product that allows a computer system environment to be viewed and manipulated from another system across a highspeed data network. Integrated with the MCC, the VNC product allows a MCC operator to monitor and control the graphical interface of distributed Windows NT systems from a single console, namely the MCC terminal. The VNC software: Accepts connections from the MCC.
Visara Master Console Center Security VNC is configured with a password during installation. This password must be supplied at connection time by any MCC user wishing to access the Windows NT server from the VNC viewer or a Web browser. This stand-alone password is not associated with an NT user domain account. Installing the VNC Software To provide access for monitoring and controlling a Windows NT server from the MCC: 1. Obtain the VNC software. Refer to http://www.uk.research.att.com/vnc. 2.
Chapter 5 MCC system.cfg Configuration File Unit Section The unit section defines a unit device for a CPU. The unit section name determines the name of the unit icon. Names must be eight characters in length or less. Valid Keys Table 23 lists the valid key requirements: Key Required? Quantity Description number Yes 1 The unique unit number (logical unit number). Specified in hex. address Yes 1 Specified in hex. type Yes 1 Specified in hex. channel Yes 1 Specified in hex.
Visara Master Console Center MVS Configuration The MVSConfig section defines the MCC environmental values for connection to MCCSTARS. Valid Keys Table 24 lists the valid key requirements of the MVSConfig section: Key Required? Quantity Description workstationid Yes 1 The workstation’s identification to the MVS Agent. retrytime Yes 1 How often to retry failed connections to the agents. Specified in seconds.
Chapter 5 MCC system.cfg Configuration File MVS Agent Section Table 25 lists the valid key requirements for each MVSAgent section: Key Required? Quantity Description userid Yes 1 The userid that identifies the MCC to the MVS Agent. password Yes 1 The password to authenticate the MCC to the MVS Agent. version Yes 1 The version of the protocol between the MVS Agent and the MCC. Set to ‘2’ for the old version of WatchMVS.
Visara Master Console Center Example: [MVSConfig] retrytime=10 [MVSAgent QuuxAgent] userid=WATCHECS password=0x0123456789ABCDEF version=3 release=1 retrytime=50 ipaddress=192.168.0.22 ipport=2769 [MVSAgent AlphaAgent] userid=WATCHECS password=0x0123456789ABCDEF version=3 release=1 retrytime=50 ipaddress=192.168.0.
Chapter 6 Defining and Changing OS Groups This chapter describes how to assign operating systems to logical groups, and how to modify existing groups. Introduction An OS Group is a logical group of operating systems. There are no predefined rules for groups, and it is not necessary that all member operating systems are of the same type or in the same physical location. They may be grouped together according to purpose, physical location, operating system type, or even physical CPU height.
Visara Master Console Center Editing OS Groups To edit OS Groups, select the Administration menu Configuration:OS Group option. The System Configuration Editor window appears. Figure 10 System Configuration Editor window (OS Groups) The System Configuration Editor window displays OS groups configured on the MCC system. The Members list box contains operating systems that are members of the currently selected OS group. The Available list box displays those Operating Systems defined in the system.
Chapter 6 Defining and Changing OS Groups Creating a new OS group 1. Click the New button. 2. The Modify OS Group window appears. Figure 11 Modify OS Group window 3. Enter the name in the OS Group Name text box. 4. Click the OK button. Adding an operating system to the selected group 1. Select an operating system from the Available list box. 2. Click the Add button. The operating system is added to the Members list box. Removing an operating system from the selected group 1.
Visara Master Console Center Deleting an OS group 1. Select an OS group from the OS Groups list box. 2. Click the Delete button. Note: Do not change the name of or delete an OS group if the group is in use. Modify all relevant Event Rules before deleting or renaming the OS Group. To save changes, from the System Configuration Editor window click the Save button. The changes are committed to the osgroup.cfg file. Changes become effective within Event Manager the next time the MCC system starts.
Chapter 7 Setting Up SNMP This chapter describes how to configure the MCC to utilize the optional SNMP (Simple Network Management Protocol) capability of the MCC, including: Configuring an SNMP Agent. Configuring SNMP Agent Groups. Using SNMP from Scripts. MIBs available on the MCC.
Visara Master Console Center Overview The MCC optionally allows communication with any networked host using the Simple Network Management Protocol (SNMP). The MCC is capable of sending and receiving SNMP traps, and getting and setting MIB values. To utilize SNMP capabilities within the MCC, definitions must first be configured using the SNMP Editor. The editor is available from the Master window Administration menu—Configuration:SNMP Setup option.
Chapter 7 Setting Up SNMP Definitions An SNMP agent is a managed host that can communicate using the SNMP protocol. SNMP Agent Group. Within the MCC, the concept of SNMP agent groups is simply a logical grouping of SNMP agents. Agent groups are useful within Event Manager for limiting an SNMP trap event rule to some, but not all, of the configured agents. Configuring an SNMP Agent To configure a new SNMP agent or modify an existing agent: Figure 11 SNMP Agent window 1.
Visara Master Console Center Community. The community used when accessing MIB values. The default is “public”. To identify the required SNMP community, refer to the documentation for the agent with which the MCC will communicate. Trap Port. Normally, set to the default port number of 162. However, it is possible that some agents may communicate on a different port number. MIB Port. Normally set to the default MIB port number of 161. 3. Click the OK button. Saving changes to the agent Click the OK button.
Chapter 7 Setting Up SNMP Configuring SNMP Agent Groups From the SNMP Editor window, it is possible to add agents, add agent groups, modify existing agents, and delete agents. Click the Agent Groups tab on the SNMP Editor window to bring the Agent Groups tab to the front. Figure 12 SNMP Editor, Agent Groups tab The Agent Group list box contains all the defined agent groups. When you select an agent group, the Current Agents list box displays the configured agents that are members of the group.
Visara Master Console Center Creating a new agent group 1. Click the New button. The Agent List window appears. Figure 13 Agent List window 2. Type the name of the new agent group. 3. Click the OK button. The new agent group is added to the Agent Groups list box. Modifying an agent group 1. Click the Modify button. The Agent List window appears (see Figure 15). 2. Type the new name of the agent group. 3. Click the OK button. The name change can be viewed in the Agent Groups list box.
Chapter 7 Setting Up SNMP Using SNMP from Scripts The SNMP commands available in the GCL scripting language are: Command Explanation SNMP_TRAPSEND Sends a trap to an agent. SNMP_GET Gets a MIB value from an agent. SNMP_GETNEXT Gets the next MIB value from an agent (see the Scripting Guide for a complete description). SNMP_SET Sets a MIB value on an agent. SNMP_GETTABLE Gets all values from an MIB table.
Visara Master Console Center MIB File MIB Is Located In FDDI SMT 6.2 Bridge DECnet Phase IV SIP Frame Relay Character RS-232 Parallel Printer Party IP Forwarding Table Repeater X.25 LAPB X.25 Packet Layer RIP Ethernet like DS1/E1 DS3/E3 Identification Multiprotocol Interconnect over X.25 PPP LCP PPP SEC PPP IP NCP PPP Bridge NCP Bridge FDDI 7.3 SMT Token Ring RMON Host Resource MAU SNMP Repeater Source Routing DECnet Phase IV Ethernet Like Ethernet Like AppleTalk RMON TCP/IPX Rfc1285.mib Rfc1286.
Chapter 7 Setting Up SNMP Adding a MIB 1. Open a Unix shell window. 2. In that window, change directory by entering cd /usr/ics/mib 3. Concatenate together the ANS.1 file along with all the MIBs you want to be able to access. The ASN.1 file contains the MIB-II definition as well as some other definitions that must be present. For example: cat ASN.1 rfc1514.mib rfc1757.mib > customMib.tmp 4. Enter run /usr/ics/bin/makemib –out customMib.db customMib.tmp 5.
Chapter 8 Administering Users This chapter discusses: Administering security for groups including changing permissions. Displaying and modifying MCC users. Adding or deleting users from groups. Displaying and modifying login users; adding or deleting users.
Visara Master Console Center Introduction Administering MCC users includes adding, removing, and maintaining MCC users and their privileges. Proper administration requires a thorough understanding of the group-level security used in the MCC. The MCC uses group-level security. Unlike in operating systems, users have no individual access rights. All rights are assigned to groups. Users belong to one or more groups. There are three levels of security for MCC “items” such as consoles and OSs: None.
Chapter 8 Administering Users What is the difference between MCC Users and Login Users? “Users” are normally individuals who access the system. However, within the MCC programs, it is important to understand the difference between “MCC Users” and “Login Users”. “Login Users” correspond to login accounts on the MCC host (that is, Unix accounts). At a “Login:” prompt, the user enters the Login User’s login name and password. This level of security is managed by the MCC host operating system, i.e.
Visara Master Console Center Administering Security Changes to the MCC security configuration are made from the Security Editor window. From the MCC master window, select the Administration menu— Configuration: Security option. The Security Editor window appears. Figure 14 Security Editor window, Security Groups tab From the Security Editor window, it is possible to modify, add, and delete: Security groups. MCC users. Login users.
Chapter 8 Administering Users Group Security Adding Security Groups To add a security group: 1. From the Security Editor window Groups tab, click the New Group button. The Add/Update Security group window appears. 2. Enter a name in the Name: text box. 3. Click the OK button. The Add/Update Security group window asks if you are sure if you want to create a new security group. 4. Click the Create Group button. The new group appears in the Security Groups List.
Visara Master Console Center Viewing Security Group Permissions To view the security group permissions, from the Master window, select the Administration menu Configuration—Security option. The Security Editor window appears. The Groups tab should be in front by default. The Group Privileges and Users in Group toggle buttons near the bottom of the Security Editor window modify the display. Figure 15 Security Editor window, Groups tab To view security group permissions: 1.
Chapter 8 Administering Users Setting Security for Consoles By default, members of a security group do not have access to a console. The group permissions must be changed to VIEW (read-only access) or UPDATE (read/write access) to allow access to the console. Changes only take effect when a user logs out and back in again. Console for CPU:OS combination: If a console is defined in both CPU and OS sections of the system.cfg file (see Chapter 5 MCC system.
Visara Master Console Center Viewing Security Group Members To view users in a security group: 1. From the Security Editor window Groups tab, select a security group from the Security Groups list box. 2. Select the Users in Group toggle button to display users assigned to the selected security group. Users in the selected security group appear in the text box to the right of the Security Groups list box. Figure 16 Security Editor window, Group Members This is a view-only window.
Chapter 8 Administering Users Viewing and Changing MCC Users From the Master window, select the Administration menu Configuration:Security option. Click the MCC Users tab to display users and current groups. Figure 17 Security Editor window, MCC Users tab From the Security Editor window, MCC Users tab it is possible to: Add a MCC user to a security group. Remove a MCC user from a security group. Create a new MCC user.
Visara Master Console Center Creating a new MCC User When adding a new user, both a MCC user and a Unix login user must be defined for the user account. To add a new MCC User: 1. From the Security Editor window MCC Users tab, click the New User button. The Add MCC User window appears. Figure 18 Add New MCC User window 2. Enter the new user’s name in the Login Name: text box.
Chapter 8 Administering Users Adding a MCC User to a Security Group To add a user to a security group: 1. From the Security Editor window MCC Users tab, select a group from the Available Groups list box. 2. Click the Add button. - The group name then appears in the Current Groups list. - A shortcut to clicking the Add button is to double-click the group name in the Available Groups list box. Deleting a MCC User To delete a MCC User: 1.
Visara Master Console Center Viewing and Changing Login Users Users are created, modified, and deleted from the Security Editor window Login Users tab. From the Master Console Center master window, select the Administration menu Configuration: Security option. The Security Editor window displays. Click the Login Users tab to display a list of login users. Note: All users in Unix group “ics” are displayed.
Chapter 8 Administering Users Modifying Login Users Caution: When working with login users, changes are being made to the OS user system accounts immediately. These changes cannot be reversed. The Security Editor does not directly modify the list of Login Users. Thus, selecting a user in the list has no effect on the program operation for New User or Delete User. However, it does have an effect when changing another user’s password.
Visara Master Console Center Creating New Login Users To create a new login user: 1. From the Security Editor window Login Users tab, click the New User button. The Create Login User informational window appears. This window display the message “Creating a new user in a separate window…” 2. The Create Login User text-entry window appears, running an interactive session “sudo adduser”. 3. Answer the questions in the text-entry window.
Chapter 8 Administering Users Question or Message Action Logname: (new user’s name) This summary allows you to confirm the entries. Enter y or n. Fullname: (new user’s full name) Primary group: ics If n, you will start over with the previous answers as defaults. Other groups: (group list) If y, the new user is created. Home directory: (new user’s home dir) Is this correct? [y] User (user’s name) has been created.
Visara Master Console Center Adding an Existing Unix User as a MCC User Instead of creating a new login user for each MCC user (see Creating New Login Users on page 132), it is possible to add existing users who already have valid accounts in the OS as MCC users. 1. Log in as root. 2. Open the /etc/group file in vi or other editor. Add the name of the existing user to the ics group by putting “,username” at the end of the line starting with ics, for example, “,JohnD”. Save and close the file.
Chapter 8 Administering Users Changing a Login User’s Password To change a user’s password: 1. From the Security Editor window Login Users tab, select the user in the User list box. 2. Click the Change Password button. 3. The Create Login User text-entry window appears, running an interactive session “sudo passwd ”. 4. Answer the questions in the text-entry window. The questions may vary slightly, depending on the version of program.
Visara Master Console Center Deleting a Login User To delete a user 1. From the Security Editor window Login Users tab, click the Delete User button. 2. The Delete Login User text-entry window appears, running an interactive session “sudo removeuser”. 3. Answer the questions in the text-entry window. The questions may vary slightly, depending on the version of program.
Chapter 8 Administering Users 4. Click the OK button on the Delete User window. Configuring login Groups The sudo group MCCADMIN contains all users who are members of the login group called “icsadmin”. Login groups are configured in /etc/group. The MCC host’s /etc/group file should have a line similar to the following: icsadmin:*:129:ics This line defines a login group called “icsadmin”. It has a group ID of 129. In this example, the only user in the group is “ics”.
Chapter 9 Managing and Editing Events with Event Manager This chapter discusses how to modify event handling rules including: Console message event rules. SNMP trap event rules. Time event rules.
Visara Master Console Center Overview The MCC Event Manager watches for user-configurable events to occur, performing a list of actions based upon the specific event. Event Manager is configured through the Event Editor, allowing the user to specify event rules and the actions to perform when a particular rule is triggered. Event Manager supports three types of event rules: Console Messages. SNMP Traps. Time Events.
Chapter 9 Managing and Editing Events with Event Manager How Event Manager Works When the MCC is started, the Event Manager: Begins scanning the printer queues for console messages. Asks SNMP Trap Manager to forward all traps to Event Manager. Begins checking scheduled rules against the current time and date. When a new console message appears, Event Manager sequentially scans through the Console Message Rules looking for a match. The first match causes that rule’s actions to be performed.
Visara Master Console Center Editing Events From the MCC Master Window, select the Administration menu— Configuration:Event Editor option. The Event Editor window appears. Note: Access to this option requires that the user have “Configuration: Event Manager” security. Figure 20 Event Editor, Console Messages tab The Event Editor window displays events and the actions associated with those events. An event may have more than one action assigned to it.
Chapter 9 Managing and Editing Events with Event Manager Modifying Event Manager Rules The following buttons are located on the Event Editor window: New Rule. Create a new event rule. New Action. Add a new action to the currently-selected event rule. Modify. Modify the currently-selected event rule or action. Move Up / Move Down. Move the currently-selected event rule or action up or down in the list. Delete. Delete the currently selected event rules or actions.
Visara Master Console Center Comment. This text area is for user notes. It can explain what the rule is trying to do, and may be especially useful if the search criteria are obscure or confusing. This is set from the Event Rule window. Actions. The list of actions to perform when the rule is triggered. Refer to the sections describing the specific rule types later in this chapter for detailed information.
Chapter 9 Managing and Editing Events with Event Manager Additional Action Fields In addition to the common action fields, the action selected from the Action drop-down list box on the Modify Rule Action window determines what additional fields appear on the Modify (action name) Rule Action window. When the Log Filtered Message option is selected from the Action drop-down list box, the following options appear: OS Name. The name of the OS that should be associated with the message.
Visara Master Console Center When the KeyInput option is selected from the Action drop-down list box, the following options appear: 146 Console Type. Choose a console to which to key the input. Sort By. How the Console Name drop-down list box is sorted. Console Name. Selects a console. Key String. Used to build a parameter.
Chapter 9 Managing and Editing Events with Event Manager Console Message Event Rules Console message event rules are edited from the Console Message Rule window. From the Console Message Rule window, it is possible to add, modify, or delete console message rules. The Move Up and Move Down buttons allow rule order manipulation. The OK and Cancel buttons are used for saving and abandoning changes, respectively. Changes do not become permanent until Save is pressed in the main window.
Visara Master Console Center In addition to the common rule fields (see Common Rules Fields on page 143), Console Message event rules have the following additional fields: Message Source. Console Messages come from OS and printer consoles. Valid sources are a specific OS, OS Groups, or any OS. Type. Selects whether the rule should match messages from a physical printer of the OS, the MVS Agent of the OS, or both. The default is to match on messages from the physical printer for the OS.
Chapter 9 Managing and Editing Events with Event Manager Regular Expressions The search string used for processing console messages is a regular expression. Refer to the Scripting Guide for a discussion of regular expressions. Modifying Console Message Rule Actions To modify console message rule actions: 1. From the Event Editor window Console Messages tab, select an event. 2. Click the Modify button. The Modify Console Message Rule Action window appears.
Visara Master Console Center Building Console Message Parameters When the Exec Script action option on the Modify Console Message Rule Action window is selected, a parameter may have to be set, depending on the script used. To build time rule parameters: 1. From the Event Editor window Console Message tab, select an action. 2. Click the Modify button, or double-click an action. The Modify Console Message Rule Action window appears. 3. Click the Parameters build (…) button.
Chapter 9 Managing and Editing Events with Event Manager The Build Parameters window allows parameter substitution based upon the associated event rule type. For console messages, this window also allows modification of the “Split Words By” field. The available substitutions for Console Message actions are listed in Table 31: Substitution Description &M& The entire console message &MS& The message source (OS Name) &W1& The first word of the input message as separated by the “Split Words By” field.
Visara Master Console Center SNMP Trap Event Rules SNMP Trap event rules are modified or created from the Trap Event Editor window. From this window, it is possible to: Modify SNMP trap events. Modify SNMP trap event actions. Modifying SNMP Trap Event Rules To modify SNMP trap event rules: 1. From the Event Manager window SNMP Traps tab, select an event rule. 2. Click the Modify button. The SNMP Trap Rule window appears. Figure 25 SNMP Trap Rule window 3.
Chapter 9 Managing and Editing Events with Event Manager - Agent Name. As part of SNMP configuration, the agents with which the host communicates are specified. Groups of SNMP Agents can also be created. This field allows specification of an SNMP Agent or an SNMP Agent Group to associate with the rule. If neither an agent nor group is specified, the rule applies to all agents. - Generic Number. Select a generic SNMP trap number from the drop-down list.
Visara Master Console Center To delete an SNMP trap rule action: 1. From the SNMP Trap window, select an action. 2. Click Delete, and then click OK on the confirmation box. Creating or Modifying SNMP Trap Rule Actions When the New or Modify button is selected on the SNMP Trap Rule window, the New/Modify SNMP Trap Rule Action window appears.
Chapter 9 Managing and Editing Events with Event Manager Selecting a Script for the Trap Rule to Execute When the Script Name (…) button is selected in the New/Modify SNMP Trap Rule Action window, the Select Script window appears. Figure 27 Select Script window To select a script for the trap rule to execute: 1. Select a script from the Script list box. 2. Click the OK button.
Visara Master Console Center Building SNMP Trap Action Rule Parameters When the Parameters (…) button is selected in the New/Modify SNMP Trap Rule Action window, the Build Parameters window appears. Figure 28 Build Parameters window Enter the necessary parameters, including substitution symbols if appropriate, then click OK.
Chapter 9 Managing and Editing Events with Event Manager Substitution Explanation &THN& Trap Host Name. Only used if the MCC System can resolve the hostname. If the IP address is not in the MCC /etc/hosts file, and the MCC is unable to determine the hostname through DNS, this value is null (empty). &TGN& Trap generic number.
Visara Master Console Center Time Event Rules Time event rules are modified or created from the Time Event rule window. From this window, it is possible to: Modify time events. Modify time event actions. Time Event Specification Requirements To specify time events properly, follow these rules: The start time and end time, if entered, must be in a valid format according to a 24 hour clock. Midnight is entered as “00:00”, not “24:00”.
Chapter 9 Managing and Editing Events with Event Manager Examples To run an event every Monday, Wednesday, and Friday during February, enter an appropriate start time and enter “02/01/2007” for the start date and “02/28/2007” for the end date (assuming the U.S. locale). Make sure only Monday, Wednesday, and Friday are selected, and all other days are cleared. It is not necessary to specify that the event will be run every n days. To run an event every 45 minutes from 8:00 A.M. until 5:00 P.M.
Visara Master Console Center Modifying Time Event Rules Modify or create a time event rule from the Time Event Rule window. To modify time event rules: 1. From the Event Manager window Time Events tab, select an event rule. 2. Click the Modify button. The Time Event Rule window appears. Figure 29 Time Event Rule window In addition to the common rule fields (see Common Rule Fields on page 143), the Time Event Rule window displays the following information: Start Time.
Chapter 9 Managing and Editing Events with Event Manager End Date. The last date on which an event is run. It is entered in the same format as the start date. This field is optional. Run on days. The day of the week is checked if an event runs on that day, or is not checked if the event does not run that day. At least one day of the week must be checked. Repeat every. Specify how often an event runs.
Visara Master Console Center Creating or Modifying Time Event Rule Actions When the New or Modify button is selected on the Time Event Rule window, the New/Modify Time Rule Action window appears,see Figure 30. Figure 30 New/Modify Time Rule Action window Note: See Common Actions Fields on page 144 and Additional Action Fields on page 145 for information about the Action and Status field selections. 162 3. Click the Script Name (…) button to select a script for this time rule to run.
Chapter 9 Managing and Editing Events with Event Manager Selecting a Script for the Time Rule to Execute When the Script Name (…) button is selected in the New/Modify Time Rule Action window, the Select Script window appears. Figure 31 Build Parameters window 1. Select a script from the Script list box. 2. Administration Guide Click the OK button.
Visara Master Console Center Building Time Rule Action Parameters When the Parameters (…) button is selected in the New/Modify Time Rule Action window, the Build Parameters window appears. Enter the necessary parameters, then click OK. Figure 32 Time Rule Action Build Parameters window No parameter substitutions are currently available for time events but you can build your own parameters. There are no substitutions symbols available for timed events.
Chapter 10 Maintaining Log Files This chapter describes: The various log files that are created by the MCC. How to view each log. How to interpret the log entries.
Visara Master Console Center Overview All messages are saved in log files, which fall into two categories: Output messages from the host systems. MCC messages, which are usually generated from scripts. All log files are in standard ASCII format, and reside in the /usr/ics/log directory. All logs can be accessed through the MCC GUI interface. All logs can be directly accessed through the Unix operating system.
Chapter 10 Maintaining Log Files Channel.log, cpu.log, software.log and unit.log each have a maximum length of 500 messages. icsexec.log, icsmaster.log, messages.log, newmsg.log, and system.log each have a maximum length of 10,000 messages. When the active log file reaches the maximum length, the following actions occur: 1. The active log file is closed and renamed to the backup filename. 2. The system runs the Reserved Script #logswap.scr, passing parameters to it which describe the backup file.
Visara Master Console Center Log File Descriptions alert.log: Alert Log All actions performed with alerts are logged to alert.log. The format of the lines in the Alert Log files is: date time user action AlertNum options For example: 2007-01-14 14:31 arl 2007-01-14 14:32 arl 2007-01-14 14:33 arl New 131 New 4 Test message Mod 131 state Closed Del 131 These three lines indicate that user arl did the following at the specified times: Created a new alert, numbered 131.
Chapter 10 Maintaining Log Files audit.log: Audit Log The audit log records commands issued manually from the MCC console, and from MCC scripts. Outputs from all consoles for which auditing is enabled are combined in the same Audit Log. To activate this option, edit the system.cfg file and add a line to the console definition of each console to be audited containing audit=yes The audit log can be viewed only through the Unix command line. The format of audit.
Visara Master Console Center Alt Clear Alt CrSel Alt_A to _Z Alt_Backslash Alt_Backspace Alt_CentSign Alt_Comma Alt_DownArrow Alt_Enter Alt_EraseEOF Alt_Insert Alt_LeftBrace Alt_LessThan Alt_Period Alt_PF13 Alt_PF16 Alt_PF19 Alt_Return Alt_Semicolon Alt_ShiftLock Alt_SingleQuote Alt_Slash Alt_Space Alt_Tab Alt_UpArrow AltCursor AltGrave AsgnCons Attn Backslash Backspace BackTab Bkwd Break BrokenPipe Cancel CentSign ChangeDisplay Clear Cmd CommReq Control_A to _Z Co
Chapter 10 Maintaining Log Files channel.log: Channel Log The channel log contains channel messages. The channel log cannot be deactivated and is populated by scripts. To direct a message into the channel log, use the LOG script command: LOG(LOG_CHAN, $Msg) The channel log can be viewed only through the Unix command line. When channel colors are manually changed with the Icon command of the MCC, a message can be entered which is recorded to this log. The format of channel.
Visara Master Console Center Console History Log The MCC maintains Console History Logs that contain recent event messages for selected consoles. The console history logger program starts each time the MCC is started or restarted. At startup, it begins reading the MCC message queue for messages directed to consoles that have history logging configured. Each such message is copied to the history log file for the particular console.
Chapter 10 Maintaining Log Files Note: Take care when using the scroll bar to navigate through the log, as the cursor remains where it was last placed. If the cursor is on the last line, when a message is received while viewing the middle of the log, the display jumps immediately to the bottom of the log to show the new data.
Visara Master Console Center Sample Console History Log Configuration The following sample configuration shows the entries required to define an OS with an telnet console and a printer, then enable console history logging for the printer only. Refer to Chapter 5 MCC system.cfg Configuration File for more details of where to make these entries.
Chapter 10 Maintaining Log Files Troubleshooting Problems with Console History Logging The console history log is not displayed if no console history is being maintained for the associated printer. If console history is unavailable, check the following: Run the configuration checker (see CFGCHK Program on page 210). The checker displays warnings if Days History is specified inconsistently or incorrectly, or if the printer is not referenced. Check the historylogger.
Visara Master Console Center event.log: Event Log Event Manager logs its activities into the event.log file. All lines in event.log begin with a date and time stamp. At startup, Event Manager issues a “--gwEventMgrD Startup ---” message (with more dashes than shown here).
Chapter 10 Maintaining Log Files Note: Events are logged in the order of initiation. However, it is possible that the first action associated with a rule may appear in the log after the entry for the second action associated with that rule. This indicates that the first action did not fully begin before the second action.
Visara Master Console Center Here are some sample Event Log entries: 2006-12-20 2006-12-20 2006-12-20 2006-12-20 2006-12-20 2006-12-20 2006-12-20 2006-12-20 2006-12-20 15:16:16 15:16:16 15:16:16 15:17:00 15:17:00 15:17:00 15:17:01 15:17:00 15:17:01 2 2 1 3 3 4 4 3 4 ACTIVE ACTIVE ACTIVE ACTIVE ACTIVE ACTIVE ACTIVE ACTIVE ACTIVE Console Msg Event 5 - AIX - alpha1 Ignore Action Ignore Action Console Msg Event 2 - AIX - $ echo alpha3 System Cmnd Execute Action - mv /tmp/arl1 /tmp/arl2 Console Msg Event 2
Chapter 10 Maintaining Log Files icsexec.log: MCC Execution Log The MCC execution log contains all the messages automatically generated by the MCC programs, both error messages and normal informational messages. When the MCC automatically executes a script based on a condition, the details are recorded here.
Visara Master Console Center Icsmaster_YYYY-MM-DD: MCC Startup and Shutdown Error Log Whenever the MCC system is shut down or started up, error messages are recorded in this log file. The MCC reroutes stderr messages from all programs to icsmaster_YYYY-MM-DD, adding color/status and date/time to the beginning of some messages. This file cannot be the target of a LOG command. It can only be viewed through the OS command line. messages.
Chapter 10 Maintaining Log Files newmsg.log: New Messages Log When Event Manager is processing console messages and a console message does not match any rule in the list of event rules, the message is written to the New Messages Log, newmsg.log. This log can identify new messages to handle with automation scripts. Where possible, this log should be empty—no new messages should be logged here. Check this file every one or two weeks, and note any new messages the MCC has received.
Visara Master Console Center software.log: Software Messages Log The Software Messages Log contains only those messages that have been explicitly logged with this syntax: LOG(LOG_SW, $Msg) This log may be populated by scripts. When OS colors are manually changed with the Icon command of the MCC, a message can be entered which is recorded to this log.
Chapter 10 Maintaining Log Files system.log: Host System Messages Log The Host System Log contains the raw, unprocessed text of all printer messages received by the MCC from host systems. It can be viewed from the Unix command line, or by selecting the Other—System Messages Log menu option. The format is: 2OS Text ContFlag The first character in the line will always be a 2. This is followed by the OS Name and the message text. Appended to the end of the line is the continuation flag -- a 0 or 1.
Chapter 11 Backing Up and Restoring MCC Software This chapter discusses how to back up and restore MCC files and scripts.
Visara Master Console Center Overview It is important to backup the MCC, particularly custom scripts, to safeguard against unexpected problems. To ease the task of creating backups, MCC scripts are provided for automatically copying the files to tape. Full MCC System Scripts Only Backup fullbackup MCCbackup scriptbackup Restore See Full Restore on page 187. MCCrestore scriptrestore Table 35 Backup and Restoration Scripts Backing Up Files To backup files: 1.
Chapter 11 Backing Up and Restoring MCC Software Restoring Scripts Caution: Do NOT try to run scriptrestore except on a tape generated by scriptbackup. Also, do NOT attempt to do a MCCrestore except on a tape generated by MCCbackup. Data loss or corruption may result. Full Restore This procedure assumes the MCC has a fully installed operating system with correctly partitioned files. 1. Login as root. 2.
Visara Master Console Center Restoring Other Files 188 1. Insert the appropriate tape into the MCC tape drive. 2. Execute the appropriate script: - To restore ALL MCC files, including binaries, configuration, and script files, select /usr/ics/bin/MCCrestore. This restores the files to the CURRENT directory. VISARA recommends restoring files to /tmp or /usr/tmp, and then copying the relevant files to the proper subdirectory under /usr/ics.
Chapter 12 Setting MCC System Date and Time This chapter describes how to adjust the MCC’s date and time when necessary. A procedure is also given for selecting the correct time zone.
Visara Master Console Center Setting Date and Time Occasionally, it may be necessary to reset the MCC system date and/or time. Unix handles both daylight savings time and leap years by automatically changing the time or date, so normally no manual time adjustments are required. Note: Changing the year requires additional steps. If the year needs to be changed, consult the Unix man pages on the date command. To change the date or time: 1.
Chapter 12 Setting MCC System Date and Time Changing the Time Zone To change the time zone information, perform the following steps: 1. On the MCC system console, log in with user id “root”. 2. Change to the /etc/zoneinfo directory: cd /etc/zoneinfo 3. Use the following command to list and browse through all time zone files: ls | more 4. Pick the appropriate time zone and write down the file name. For example, in the US subdirectory, Mountain is the file name of the timezone for the US Mountain area.
Chapter 13 Printing from the MCC This chapter describes how to configure a printer for use with the MCC. It does NOT describe how to use printer consoles through the MCC.
Visara Master Console Center Overview The ability to print files directly from the MCC may prove useful in some situations. Configuring the printer (NOT to be confused with printer consoles) is relatively straightforward. The MCC can print to an LP/LPD capable printer, or to a printer host which has been configured to accept print requests from other machines. Configuring Printing To configure the MCC for TCP/IP network printing: 1. Define the print host in /etc/hosts or DNS. 2.
Chapter 13 Printing from the MCC lg06 lg08plus lg12 lg12plus lg31 lgl04plus lgl08plus lj250 ln03 ln03ja ln03r ln03s ln05 ln05ja ln05r ln06 ln06r ln07 ln07r ln08 ln08r ln09 ln10ja ln14 ln17 ln17_a4 ln17ps ln17ps_a4 ln82r nec290 ps_level1 ps_level2 remote xf unknown generic_ansi generic_ansi_a4 generic_text generic_text_a4 or press RETURN for [unknown] : remote Enter printer synonym: hp5 Enter printer synonym: laser5 Enter printer synonym: Set spooler directory 'sd' [/usr/spool/lpd] ? Set print
Visara Master Console Center Enter symbol name: q Printer #0 ---------Symbol type value ------ ---- ----lf STR /usr/adm/lperr lp STR mx INT 0 rm STR laserjet5 rp STR text sd STR /usr/spool/lpd sh BOOL on Are these the final values for printer 0 ? [y] Adding comments to printcap file for new printer, type '?' for help. Do you want to add comments to the printcap file [n] ? : Set up activity is complete for this printer.
Chapter 13 Printing from the MCC If everything is configured correctly and the file still does not print, contact Visara Technical Support.
Chapter 14 Remote Access to the MCC This chapter describes how to connect to the MCC from a remote character-based terminal for troubleshooting or support purposes.
Visara Master Console Center Overview While an X Terminal or emulation is the recommended method of using the MCC, it is possible that such a terminal will not always be available. In this situation, gwcharcons allows text-only remote console access from any VT100 terminal. This facility is particularly suited to offsite troubleshooting and support. Note: Security privileges for the Login User account and MCC User account also apply to all remote access sessions.
Chapter 14 Remote Access to the MCC gwcharcons: Remote Console Access gwcharcons is a non-GUI (character only) console that allows dial-in and telnet access to the consoles configured in the MCC—the same consoles accessible from the MCC GUI. Starting gwcharcons 1. Dial into or connect by telnet to the MCC. 2. Log in with a valid MCC Login User account. 3. When logging into the MCC by telnet or modem a limited menu of choices is offered.
Visara Master Console Center If a non-numeric character is entered at the gwcharcons console selection prompt, the screen may go blank. Enter a valid numeric character to continue. If a user’s console session becomes slow or unresponsive to the MCC’s console manager program (for example, because of excess message traffic), the MCC will disconnect from the specific user’s console session, and log an error message. This prevents negative effects on other users.
Chapter 14 Remote Access to the MCC Ctrl-F: Enter Softkeys/function keys The softkeys window lists the available function keys and softkeys. The use of softkeys allows entry of keystrokes which would normally not be possible with the keyboard currently being used. Help appears along the bottom. Enter the number of a particular entry and press . Ctrl-F has no effect from the main screen. Ctrl-K: Enter control key To send a control key, type Ctrl-K.
Chapter 15 Troubleshooting This chapter provides basic guidance and steps to take in situations where the MCC system is not operating correctly.
Visara Master Console Center General Information If any errors occur while working with the MCC, contact VISARA Technical Support. To help VISARA diagnose and correct problems, write down exact error messages, and any actions you were performing at the time of the error. The OS prompt for the root account is “#”.
Chapter 15 Troubleshooting MCC stopped/suddenly shut down Login as “root” on the system console and follow these steps: 1. Create a backup as described in Backing Up Files on page 186. 2. Restart the MCC. Console does not function properly If a problem affects a single console, and other consoles are functioning correctly: Check the status of the console in the Console Selection window and/or the GWCC (gwcharcons). Check the relevant log files. Refer to Chapter 10 Maintaining Log Files for details.
Visara Master Console Center ICSMASTER ICSMASTER is a troubleshooting aid that: Identifies all VISARA programs that are running on the MCC server. Closes the running programs. Optionally, logs off all active users. The options listed here are used with the ICSMASTER program. These options should be used with bin/icsmaster. 208 Option Description -a Display the current system alerts. -A Display just the count of current system alerts.
Chapter 15 Troubleshooting Option Description -t Check if system is already running, retuning 11 if not, otherwise 0. -T Display the length of time the system has been running. -u Display the current system users. -U Display just the count of current system users. -v This option allows you to verify the name and version of the VISARA programs. -V Display details of the name and version -x Using this option identifies running processes and resources, then exits. It does not start ICSMASTER.
Visara Master Console Center CFGCHK Program The cfgchk configuration checker program checks the MCC configuration files for errors, and writes error messages to stdout or the Execution Log. It may be run either by choosing the Check Configuration option from the Administration menu, or from the command line to troubleshoot configuration problems. To run cfgchk from the menu, select the Administration menu— Configuration:Check Configuration option.
Chapter 15 Troubleshooting Scanning Text Files for ASCII Control Characters The MCC screen editor does not display ASCII control characters in text files such as configuration (.cfg) files and scripts if the user inadvertently types them. As these characters may cause errors, the configuration files and scripts should be scanned after each editing sessions to identify them.
Visara Master Console Center /usr/ics/config/snmp.cfg, OK /usr/ics/config/status.cfg, OK /usr/ics/config/system.cfg, 31, 108 ****** /usr/ics/config/MCCsessioncleanup.txt, OK When no control characters are found, “OK” is appended to the end of the output line. When control characters are found, the line is appended with the location of the characters and the string “******”. In the example, control characters were detected in objmgr.cfg on line 187, and in system.cfg on line 31 and 108.
Chapter 15 Troubleshooting Note: Compiled scripts (.scx files) are ignored.
Chapter 16 Integrating Other Products with the MCC This chapter provides an overview of how to integrate some third-party products for use with the MCC.
Visara Master Console Center Launching a Display of Console Selection window To invoke the Console Selection window, the program or user must pass the following arguments to the wrapper script: MCC [-d display] gwconsole where “display” is the name of the display on which the console “console_name” will appear. If the display is not specified, the current value of the DISPLAY environment variable is used by default.
Chapter 16 Integrating Other Products with the MCC Implementation Notes General The launching program or user must be added with the proper security permissions as: - A Unix login user. - A MCC user. - A member of the appropriate security group(s) as required. Refer to Chapter 8 Administering Users for details. Access permissions may also be required on the host system to run the window. The display can be set before the script is called, in which case it may be omitted from the command.
Visara Master Console Center Ataman Telnet This product may be used in place of the telnet client supplied with Windows NT. Refer to the Ataman TCP Remote Logon Services User’s Manual which is installed on the PC when the Ataman TCP Remote Logon Services program is installed. The file name of this document is “userman.doc”.
Appendix A Valid Color Names Color Name RGB Numbers Color Name RGB Numbers alice blue AliceBlue antique white AntiqueWhite AntiqueWhite1 AntiqueWhite2 AntiqueWhite3 AntiqueWhite4 aquamarine aquamarine1 aquamarine2 aquamarine3 aquamarine4 azure azure1 azure2 azure3 azure4 beige bisque bisque1 bisque2 bisque3 bisque4 black blanched almond BlanchedAlmond blue blue violet blue1 blue2 blue3 blue4 BlueViolet brown brown1 brown2 brown3 brown4 burlywood burlywood1 burlywood2 240 248 255 240 248 255 250 235 21
Visara Master Console Center Color Name RGB Numbers Color Name RGB Numbers dark sea green dark slate blue dark slate gray dark slate grey dark turquoise dark violet DarkGoldenrod DarkGoldenrod1 DarkGoldenrod2 DarkGoldenrod3 DarkGoldenrod4 DarkGreen DarkKhaki DarkOliveGreen DarkOliveGreen1 DarkOliveGreen2 DarkOliveGreen3 DarkOliveGreen4 DarkOrange DarkOrange1 DarkOrange2 DarkOrange3 DarkOrange4 DarkOrchid DarkOrchid1 DarkOrchid2 DarkOrchid3 DarkOrchid4 DarkSalmon DarkSeaGreen DarkSeaGreen1 DarkSeaGreen2
Appendix A Valid Color Names Color Name RGB Numbers Color Name RGB Numbers gray13 gray14 gray15 gray16 gray17 gray18 gray19 gray2 gray20 gray21 gray22 gray23 gray24 gray25 gray26 gray27 gray28 gray29 gray3 gray30 gray31 gray32 gray33 gray34 gray35 gray36 gray37 gray38 gray39 gray4 gray40 gray41 gray42 gray43 gray44 gray45 gray46 gray47 gray48 gray49 gray5 gray50 gray51 gray52 gray53 gray54 gray55 gray56 33 33 33 36 36 36 38 38 38 41 41 41 43 43 43 46 46 46 48 48 48 555 51 51 51 54 54 54 56 56 56 59 59
Visara Master Console Center Color Name RGB Numbers Color Name RGB Numbers green yellow green1 green2 green3 green4 GreenYellow grey grey0 grey1 grey10 grey100 grey11 grey12 grey13 grey14 grey15 grey16 grey17 grey18 grey19 grey2 grey20 grey21 grey22 grey23 grey24 grey25 grey26 grey27 grey28 grey29 grey3 grey30 grey31 grey32 grey33 grey34 grey35 grey36 grey37 grey38 grey39 grey4 grey40 grey41 grey42 grey43 grey44 173 255 47 0 255 0 0 238 0 0 205 0 0 139 0 173 255 47 192 192 192 000 333 26 26 26 255 255
Appendix A Valid Color Names Color Name RGB Numbers Color Name RGB Numbers grey89 grey9 grey90 grey91 grey92 grey93 grey94 grey95 grey96 grey97 grey98 grey99 honeydew honeydew1 honeydew2 honeydew3 honeydew4 hot pink HotPink HotPink1 HotPink2 HotPink3 HotPink4 indian red IndianRed IndianRed1 IndianRed2 IndianRed3 IndianRed4 ivory ivory1 ivory2 ivory3 ivory4 khaki khaki1 khaki2 khaki3 khaki4 lavender lavender blush LavenderBlush LavenderBlush1 LavenderBlush2 LavenderBlush3 LavenderBlush4 lawn green LawnG
Visara Master Console Center Color Name RGB Numbers Color Name RGB Numbers LightSalmon2 LightSalmon3 LightSalmon4 LightSeaGreen LightSkyBlue LightSkyBlue1 LightSkyBlue2 LightSkyBlue3 LightSkyBlue4 LightSlateBlue LightSlateGray LightSlateGrey LightSteelBlue LightSteelBlue1 LightSteelBlue2 LightSteelBlue3 LightSteelBlue4 LightYellow LightYellow1 LightYellow2 LightYellow3 LightYellow4 lime green LimeGreen linen magenta magenta1 magenta2 magenta3 magenta4 maroon maroon1 maroon2 maroon3 maroon4 medium aquam
Appendix A Valid Color Names Color Name RGB Numbers Color Name RGB Numbers orange2 orange3 orange4 OrangeRed OrangeRed1 OrangeRed2 OrangeRed3 OrangeRed4 orchid orchid1 orchid2 orchid3 orchid4 pale goldenrod pale green pale turquoise pale violet red PaleGoldenrod PaleGreen PaleGreen1 PaleGreen2 PaleGreen3 PaleGreen4 PaleTurquoise PaleTurquoise1 PaleTurquoise2 PaleTurquoise3 PaleTurquoise4 PaleVioletRed PaleVioletRed1 PaleVioletRed2 PaleVioletRed3 PaleVioletRed4 papaya whip PapayaWhip peach puff PeachPuf
Visara Master Console Center Color Name RGB Numbers Color Name RGB Numbers sienna sienna1 sienna2 sienna3 sienna4 sky blue SkyBlue SkyBlue1 SkyBlue2 SkyBlue3 SkyBlue4 slate blue slate gray slate grey SlateBlue SlateBlue1 SlateBlue2 SlateBlue3 SlateBlue4 SlateGray SlateGray1 SlateGray2 SlateGray3 SlateGray4 SlateGrey snow snow1 snow2 snow3 snow4 spring green SpringGreen SpringGreen1 SpringGreen2 SpringGreen3 SpringGreen4 steel blue SteelBlue SteelBlue1 SteelBlue2 SteelBlue3 SteelBlue4 tan tan1 tan2 tan3
Index 3 3270 North American keyboard emulation ...........39 A Add New MCC User window................................128 adding SNMP trap rule actions ...........................153 Alert Log ...............................................................168 alert.log file ...........................................................168 ASCII control characters scanning text files for .................................................209 Ataman Telnet integrating ............................................
Visara Master Console Center editing.........................................................................142 Events Editor window description ..................................................................142 Exceed emulation software ....................................33 F Filtered Message Log ...........................................180 font configuration ...................................................44 fonts.cfg file.............................................................
Index backing up ..................................................................186 restoring .....................................................................187 MCC Startup and Shutdown Error Log ..............180 MCC system configuration.....................................46 MCC system configuration file...............................77 command console section.............................................96 CPU section..................................................................
Visara Master Console Center levels of ......................................................................120 removing MCC user from security group...................129 saving changes in security editor................................137 Security Editor window Login Users tab description ..................................................................130 Security Editor window MCC Users tab description ..................................................................
Index event rules ..................................................................152 troubleshooting general........................................................................204 specific problems........................................................204 U UDM file..................................................................57 unit device defining for CPU ........................................................101 unit.log file ............................................................
707130-001
