Accessing MIBs. At the end of this module you will be able to

Transcription

1 Module Accessing MIBs At the end of this module you will be able to describe Tuxedo Management Information Bases (MIBs) list and explain the six MIBs currently provided use the Tuxedo ud32 utility to create and update entities in the Tuxedo core MIB -1 Copyright -1

2 ƒ ƒ ƒ Road Map MIB Overview Managing Applications through MIBs Lab Workshop -2 Copyright -2

3 Section 1 MIB Overview At the end of this section you will be able to describe Tuxedo Management Information Bases (MIBs) list and explain the six MIBs currently provided indicate the fields in MIB request message buffers -3 Copyright -3

4 What is a MIB? ƒ A MIB (Management Information Base) is a collection of attributes and value pairs associated with a class or object ƒ "class" is used in a broad sense, as being an entity that has attributes ƒ MIBs are accessed and modified using the Tuxedo AdminAPI 0\0,% 0\&ODVV Attributes $WWULEXWH $WWULEXWH $WWULEXWH $WWULEXWH Values 9DOXH 9DOXH 9DOXH 9DOXH -4 Copyright -4

5 BEA Tuxedo MIBs ƒ A collection of MIBs provide access to system parameters ƒ Each system component has its own MIB ƒ Tuxedo provides six MIBs Available MIBs Provides Management of Tuxedo (TM) /WS (WS) ZRUNVWDWLRQRUUHPRWHFOLHQWV /Q (APPQ) Domain (DM) 4TXHXHV Events (EVENT) 'RPDLQJDWHZD\V ACLs (ACL) PDFKLQHVVHUYHUVQHWZRUNLQJDQGORDGEDODQFLQJ (YHQW%URNHUVXEV\VWHP VHFXULW\DFFHVVFRQWUROOLVW -5 More information can be obtained in the Tuxedo Reference documentation: MIB(5) Management Information Base The abbreviations in (..) on the slide refer to that MIB, for example the Tuxedo MIB is TM_MIB and the /WS MIB is WS_MIB. All the MIBs are documented in the Reference Section 5 of the Tuxedo documentation, for example TM_MIB(5) Management Information Base for the Tuxedo core system. Copyright -5

6 An Example Use of the AdminAPI %%/ 70,% %% Some Admin Clients: WPDGPLQ TPDGPLQ $GPLQ &OLHQW WX[FRQILJ WSFDOOÅ70,%ÅÃ,Q%XIëÃ2XW%XIë1DPH9DOXH SDLUV $70, )0/ÃGDWD -6 The Admin API We used the term Admin API previously. This is a generic term sometimes used to describe the interface into the Tuxedo Administration (TM_MIB) subsystem, which is really a request for a special service.tmib that is advertised by the Bulletin Board Liaison (BBL) process. The parameters supplied with the.tmib service request determine the nature of the request. The buffer type used in the.tmib request is an FML32 buffer and obviously the parameter fields in the request and response buffers are FML32 fields. tmconfig (1) An interactive Tuxedo Administration utility to dynamically update and retrieve information while the application is running. It makes changes directly to the TUXCONFIG and/or Bulletin Board; you need to save the changes to a text UBBCONFIG format if you want to re-use the changed parameters. Using the MIB API directly is a preferred method a Copyright -6

7 What is SNMP? ƒ SNMP (Simple Network Management Protocol) is a mechanism originally devised to manage simple networked devices ¾ Originally devices included mostly hardware devices like printers and routers ƒ SNMP has since been adapted to also manage systems and software applications ƒ SNMP defines three basic commands ¾ SET: sets an attribute to a value ¾ GET: retrieves the value of an attribute ¾ GETNEXT: same as GET but with cursors -7 Copyright -7

8 FML32 Buffer ƒ An FML32 buffer is a data structure used to set and retrieve MIB information ƒ FML32 buffer fields allow SNMP-style SET, GET, and GETNEXT commands Field Type GET GETNEXT TA_OPERATION VWULQJ 5 5 TA_CLASS VWULQJ 5 5 Other Fields dependent on the CLASS )0/ILHOGVWRVHWDWWULEXWH7B*5283WRYDOXH,1$&7,9( TA_OPERATION SET TA_CLASS T_GROUP TA_STATE INACT SET Copyright -8

9 Tuxedo & Enterprise Management ƒ All the major Enterprise Management products support Tuxedo administration Browser MIB API Command-Line Utilities Administration Console EventBroker MIB EVENTS SNMP TLOG Bulletin Board ULOG Enterprise Management Console -9 Standard SNMP management consoles can access Tuxedo MIBs through BEA SNMP Agent 2.1 (formerly called BEA Manager) or through a 3 rd party vendor supplied SNMP agent that accesses the Tuxedo MIB directly. Copyright -9

10 Review ƒ In this section we talked about ¾ MIBs in general ¾ the six MIB types provided in Tuxedo ¾ an overview of the use of the AdminAPI ¾ how Enterprise Management Consoles can interface with Tuxedo administration -10 Copyright -10

11 ƒ ƒ ƒ Road Map MIB Overview Managing Applications through MIBs Lab Workshop -11 Copyright -11

12 Section 2 Managing Applications through MIBs At the end of this section you will understand what the core Tuxedo MIB provides identify the major classes in the core MIB (TM_MIB) be able to use the Tuxedo ud32 utility to access and modify objects in the TM_MIB -12 Copyright -12

13 TMIBs ƒ TMIBs extend MIBs by containing more than one class ƒ Classes defined in TMIB define class properties accessible by an attribute name ƒ We will cover only a few of the classes here 70,% 7B*5283&ODVV Attributes TA_SRVGRP TA_GRPNO TA_LMID «7B6(59(5&ODVV Attributes TA_SRVGRP TA_SRVID TA_STATE «... Values APP_GRP 1 SITE1 «Values APP_GRP 117 ACTIVE «-13 Some commonly-used TMIB Classes T_BRIDGE T_CLIENT T_CONN T_DEVICE T_DOMAIN T_GROUP T_MACHINE T_NETGROUP T_SERVER T_SERVICE configures network connections between machines run-time attributes of active clients run-time attributes of active conversations configuration and run-time attributes of devices global application attributes attributes of a particular server group attributes pertaining to a particular machine attributes of network groups configuration and run-time attributes of servers configuration attributes of services Copyright -13

14 Class Entries and Attributes ƒ There may be several entries of the same class ƒ Some attributes are set at configuration time ƒ Some attributes are set at runtime 70,% *52837B*5283 Attributes TA_SRVGRP TA_GRPNO TA_LMID «TA_SRVGRP TA_GRPNO TA_LMID «... Values APP_GRP 1 SITE1 «*52837B*5283 Attributes Values SYS_GRP 2 SITE1 «-14 The TMIB can contain none, one, or more entries of a class. For example, there could be multiple Server Groups defined in the T_GROUP class. Each entry in the class is uniquely identifiable by a set of attributes. For the T_GROUP class, this would be the Group Number. Copyright -14

15 The ud32 Utility ƒ ud32 enables administrators to execute MIB commands without programming ƒ ud32 reads its input from the terminal or a file, creates an FML32 buffer and sends it to the BBL %%/ WSFDOOÅ70,%ÅÃ%XII,QëÃ%XII2XWëXG 7X[HGR 0,% :6 0,% $&/ 0,% 4 0,% 'RPDLQ 0,% (YHQW 0,%,QSXWÃ)LOH -15 The ud32 program is a general Tuxedo client utility that is used to generate generic client requests to servers that expect FML or FML32 request buffers. It can be used as a simple Tuxedo Administration client program to perform either scripted or ad-hoc MIB commands. This can save an Administrator from having to create client programs to perform specific tasks. Copyright -15

16 ud32 as an Administration Client ƒ The ud32 tool needs the following environment variables to be set Platform Variable Value 81,; :LQGRZV ),(/'7%/6 8V\VIOWSDGPHYWBPLE )/'7%/',5 78;',5XGDWDREM ),(/'7%/6 8V\VIOWSDGPHYWBPLE )/'7%/',5 78;',5?XGDWDREM ƒ ud32 is a general purpose utility; to use it to set TMIB fields, it must be run with tpsysadm privileges ud32 -C tpsysadm ud32 must be run with special client privileges to create or update TMIB entries. The -C option is used to run ud32 with the special client name tpsysadm. Copyright -16

17 Using ud32 - Example Executing ud32 from the command line: (some of the output is not shown) -17 Content of getsvr.dat input file to ud32 SRVCNM<tab>.TMIB TA_OPERATION <tab>get TA_CLASS <tab>t_server TA_SERVERNAME <tab>simpserv <cr> Copyright -17

18 T_MACHINE Class Definition ƒ Required and some optional attributes of T_MACHINE Attribute Values Description Required TA_PMID V\VWHPÃQDPHÃRIÃWKHÃWKHÃPDFKLQH 5 TA_LMID TA_TUXCONFIG TA_TUXDIR TA_APPDIR TA_STATE VWULQJ>@ VWULQJ>@ VWULQJ>@ ORJLFDOÃPDFKLQHÃLGHQWLILHU 5 DEVROXWHÃSDWKÃWRÃWX[FRQILJÃILOH 5 DEVROXWHÃSDWKÃRIÃ7X[HGRÃKRPHÃGLUHFWRU\ 5 VWULQJ>@ DEVROXWHÃSDWKÃWRÃORFDWLRQÃRIÃDSSOLFDWLRQÃILOHV 5 GET :"ACT INA MIG CLE RES SUS PAR DEA" SET :"NEW INV ACT INA DEA" -18 Copyright -18

19 Example of Adding a Machine UBBCONFIG *RESOURCES... MODEL MP OPTIONS LAN... *MACHINES MACHINE1... MACHINE2 *GROUPS... addmachine3.txt :HFDQDGGDQHZ0DFKLQHDV)ROORZV SRVCNM TA_OPERATION TA_CLASS TA_PMID TA_LMID TA_TUXDIR TA_APPDIR TA_TUXCONFIG TA_STATE FU! RQHÃWDE.TMIB SET T_MACHINE GUMBY SITE3 C:/tuxedo C:/myapps C:/myapps/tuxconfig INA RQHÃEODQNÃOLQH :HXSGDWH70,%ZLWKXGDVIROORZV c:\> ud32 < addmachine3.txt -19 The slide shows an example of adding a new machine, GUMBY, to the current configuration. Copyright -19

20 T_GROUP Class Definition ƒ These are some attributes of T_GROUP: Attribute TA_SRVGRP TA_GRPNO TA_LMID TA_STATE Values LMID1[,LMID2] Description ORJLFDOQDPHRIWKHVHUYHUJURXS 5 JURXSQXPEHU 5 SULPDU\DQGVHFRQGDU\PDFKLQHV 5 GET:"ACT INA MIG" SET:"NEW INV ACT RAC INA MIG" Required -20 T_GROUP Class Attributes TA_SRVGRP : string[1...30] : Logical name of the server group. The group name must be unique within all group names in the T_GROUP class and TA_LMID values in the T_MACHINE class. Server group names cannot contain an asterisk (*), comma, or colon. TA_GRPNO : 1 <= num < 30,000 : Group number associated with this server group. TA_LMID : LMID1[,LMID2] : Primary machine logical machine identifier for this server group (LMID1) and optional secondary logical machine identifier (LMID2). The secondary LMID indicates the machine to which the server group can be migrated (if the MIGRATE option is specified in the T_DOMAIN :TA_OPTIONS attribute). TA_STATE : GET: {ACTive INActive MIGrating}. A GET operation will retrieve configuration and run-time information for the selected T_GROUP object(s). SET: {NEW INValid ACTive ReACtivate INActive MIGrating}. Copyright -20

21 Example of Adding a Group UBBCONFIG +HUHZHGHFODUHDJURXS *MACHINES Machine1 LMID master... *GROUPS Group1 GRPNO 1 LMID master... addnewgroup.txt :HFDQDGGDQHZ*URXSDV)ROORZV SRVCNM.TMIB TA_OPERATION SET TA_CLASS T_GROUP TA_SRVGRP Group2 TA_GRPNO 2 TA_LMID master TA_STATE NEW :HXSGDWH70,%ZLWKXGDVIROORZV c:\> ud32 < addnewgroup.txt -21 The slide shows an example of adding a new Group, Group2, to the machine( LMID) master. Copyright -21

22 T_SERVER Class Definition ƒ Some of the attributes of T_SERVER: Attribute TA_SRVGRP TA_SRVID TA_SERVERNAME TA_MIN, TA_MAX TA_STATE Values Description Required VHUYHUÃJURXS 5 VHUYHUÃ,' 5 VHUYHUÃQDPH 5 PLQLPXPÃDQGÃPD[LPXPÃQXPEHUÃRIÃFRSLHVÃRIÃVHUYHU GET :"ACT INA MIG CLE RES SUS PAR DEA" SET :"NEW INV ACT INA DEA" -22 T_SERVER Class Attributes TA_SRVGRP : string[1...30] : Logical name of the server group. Server group names cannot contain an asterisk (*), comma, or colon. TA_SRVID : 1 <= num < 30,001 : Unique (within the server group) server identification number. TA_SERVERNAME : string[1...78] : Name of the server executable file. The server identified by TA_SERVERNAME will run on the machine(s) identified by the T_GROUP :TA_LMID attribute for this server s server group. If a relative pathname is given, then the search for the executable file is done first in TA_APPDIR, then in TA_TUXDIR/bin, then in /bin and /usr/bin, and then in <path>, where <path> is the value of the first PATH = line appearing in the machine environment file, if one exists. TA_STATE : SET: {NEW INValid ACTive INActive DEAd} GET: {ACTive INActive MIGrating CLEaning REStarting SUSpended PARtitioned DEAd} TA_MIN : 1 <= num < 1,001 : Minimum number of occurrences of the server to be booted by. TA_MAX : 1 <= num < 1,001 : Maximum number of occurrences of the server to be booted. Initially, tmboot (3c) boots T_SERVER :TA_MIN objects of the server, and additional objects may be started individually (by starting a particular server id) or through automatic spawning (conversational servers only). Run-time modifications to this attribute will affect all running servers in the set of identically configured servers (see TA_BASESRVID above) as well as the configuration definition of the server. Copyright -22

23 Example of Adding a Server Process UBBCONFIG... *GROUPS... Group2 GRPNO 2 LMID master... *SERVERS... MyServer1... MyServer addnewserver.txt :HFDQDGGDQHZ6HUYHUDV)ROORZV SRVCNM.TMIB TA_OPERATION SET TA_CLASS T_SERVER TA_SERVERNAME MyServer3 TA_SRVGRP Group2 TA_SRVID 70 TA_MIN 3 TA_STATE NEW :HXSGDWH70,%ZLWKXGDVIROORZV c:\> ud32 < addnewserver.txt -23 The slide shows an example of adding 3 new Server instances of MyServer3 to Server Group Group2, on the machine( LMID) master. Copyright -23

24 Review ƒ In this section we talked about ¾ the TMIB (TM_MIB) classes ¾ using the ud32 utility program to access and modifying information in some of the main TMIB classes -24 Copyright -24

25 Review ƒ In this module we talked about ¾ what a MIB is ¾ the six MIB types provided by Tuxedo ¾ the TMIB (TM_MIB) classes and their main attributes ¾ use of the ud32 utility to create and update TMIB class entities -25 Copyright -25

26 Lab Workshop Please refer to the Lab Exercises guide and do lab. The suggested time for this lab is 45 minutes. The Instructor will determine when it is appropriate to stop. -26 Copyright -26