1SGE_ST(8) Grid Engine Administrative Commands SGE_ST(8)
2
6 util/sgeST/sge_st - Grid Engine Service Tags Support control command
7
9 sge_st enable | disable | register | unregister | check | enabled |
10 supported | help
11
13 sge_st controls the Grid Engine support for Service Tags. A Service
14 Tag support improve the monitoring of usages of the Grid Engine.
15
17 enable Enables the Service Tags support for Grid Engine. If the Ser‐
18 vice Tags packages are installed on the host, the presence of
19 the product instance service tag is checked in every start of
20 the qmaster daemon.
21 disable
24 Disables the Service Tags support for Grid Engine.
25 register
28 Create the product instance service tag.
29 unregister
32 Remove the product instance service tag.
33 check Checks the status of the product instance service tag. If not
36 registered, the option returns "unregistered". If registered,
37 the option returns "registered:<product_instance_urn>"
38 enabled
41 Check the status of the service tags support. If the service
42 tags are enabled by Grid Engine administrator, the option
43 returns "true", otherwise "false".
44 supported
47 Checks if the Service Tags are supported on this host. This
48 option validates the presence of the Service Tags packages on
49 the host and checks if they are correctly installed. If Service
50 Tags are supported on this host, the option return a word
51 "true", otherwise "false".
52
55 Service Tags enables automatic discovery of systems, software and ser‐
56 vices. A service tag uniquely identifies each tagged asset, and allows
57 the asset information to be shared over a local network in a standard
58 XML format.
59 The Grid Engine can create a service tag for one cluster installation.
61 A service tag entry is stored in the Service Tag registry. Each ser‐
62 vice tag has an unique instance identifier which is generated when the
63 record is added to the registry. This identifier is used as the key
64 when accessing the record.
65 The discoverer and listener services installed together with Service
67 Tags on a host. They provide a way to discover a service tags via the
68 network. The discoverer is a UDP-based application which exists to pro‐
69 vide information about the listener. The listener is a TCP-based
70 application which provides a way to gather service tag and associated
71 environmental information.
72 The discoverer service is used by operating system upgrade or register
74 tools to send the service tags data to SUN. There is no other way, how
75 to propagate the collected data to SUN than through the registration
76 tool. The data to be send can be inspected and accepted. The Service
77 Tags Data is going to be analyzed.
78
80 GE_ROOT Specifies the location of the Grid Engine standard con‐
81 figuration files.
82 GE_CELL If set, specifies the default Grid Engine cell. To
84 address a Grid Engine cell
85
87 sge_st The command must be called with Grid Engine admin rights or root
88 permissions.
89
91 sge_st creates a st.enabled file in GE_CELL\common directory. If avail‐
92 able, the file contains the product related urn key. This key will be
93 used for upgrading purposes.
94 <ge_root>/<cell>/common/st.enabled
95 Grid Engine Service Tags Support enabling indicator
96
98 ge_qmaster(8).
99
101 See ge_intro(1) for a full statement of rights and permissions.
102GE 6.2u5 $Date: 2007/10/30 16:54:07 $ SGE_ST(8)