| 1 |
<pre>Network Working Group C. Kalbfleisch |
| 2 |
Request for Comments: 2039 OnRamp Technologies, Inc. |
| 3 |
Category: Informational November 1996 |
| 4 |
|
| 5 |
|
| 6 |
<span class="h1">Applicablity of Standards Track MIBs to Management of World Wide</span> |
| 7 |
<span class="h1">Web Servers</span> |
| 8 |
|
| 9 |
Status of this Memo |
| 10 |
|
| 11 |
This memo provides information for the Internet community. This memo |
| 12 |
does not specify an Internet standard of any kind. Distribution of |
| 13 |
this memo is unlimited. |
| 14 |
|
| 15 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Abstract</span> |
| 16 |
|
| 17 |
This document was produced at the request of the Network Management |
| 18 |
Area Director following the HTTP-MIB BOF at the 35th IETF meeting to |
| 19 |
report on the applicability of the existing standards track MIBs to |
| 20 |
management of WWW servers. |
| 21 |
|
| 22 |
Requirements for management of a World Wide Web (WWW) server are |
| 23 |
presented. The applicable existing standards track MIBs are then |
| 24 |
examined. Finally, an analysis of the additional groups of MIB |
| 25 |
attributes that are needed to meet the requirements is presented. |
| 26 |
|
| 27 |
Table of Contents |
| 28 |
|
| 29 |
<a href="#section-1">1</a>. Abstract.................................................<a href="#page-1">1</a> |
| 30 |
<a href="#section-2">2</a>. Overview.................................................<a href="#page-2">2</a> |
| 31 |
<a href="#section-3">3</a>. Requirements.............................................<a href="#page-3">3</a> |
| 32 |
<a href="#section-3.1">3.1</a> Operational Model Requirements...........................<a href="#page-3">3</a> |
| 33 |
<a href="#section-3.1.1">3.1.1</a>. Host specific and Application Monitoring.................<a href="#page-3">3</a> |
| 34 |
<a href="#section-3.1.2">3.1.2</a>. Dependencies among applications..........................<a href="#page-3">3</a> |
| 35 |
<a href="#section-3.1.3">3.1.3</a>. Error generation and reporting...........................<a href="#page-3">3</a> |
| 36 |
<a href="#section-3.1.4">3.1.4</a>. Capacity planning........................................<a href="#page-4">4</a> |
| 37 |
<a href="#section-3.1.5">3.1.5</a>. Log Digester.............................................<a href="#page-4">4</a> |
| 38 |
<a href="#section-3.2">3.2</a>. Service Model Requirements...............................<a href="#page-4">4</a> |
| 39 |
<a href="#section-3.2.1">3.2.1</a>. Retrieval services.......................................<a href="#page-4">4</a> |
| 40 |
<a href="#section-3.2.2">3.2.2</a>. Document information store -- managing documents.........<a href="#page-4">4</a> |
| 41 |
<a href="#section-3.2.3">3.2.3</a>. Server configuration.....................................<a href="#page-4">4</a> |
| 42 |
<a href="#section-3.2.4">3.2.4</a>. Server Control...........................................<a href="#page-4">4</a> |
| 43 |
<a href="#section-3.2.5">3.2.5</a>. Quality of Service.......................................<a href="#page-4">4</a> |
| 44 |
<a href="#section-4">4</a>. Relationship to existing IETF efforts....................<a href="#page-5">5</a> |
| 45 |
<a href="#section-4.1">4.1</a>. MIB-II [<a href="#ref-2" title=""Management Information Base for Network Management of TCP/IP-based internets: MIB- II"">2</a>]...............................................<a href="#page-5">5</a> |
| 46 |
<a href="#section-4.2">4.2</a>. Host Resources MIB [<a href="#ref-3" title=""Host Resources MIB"">3</a>]...................................<a href="#page-5">5</a> |
| 47 |
<a href="#section-4.3">4.3</a>. Network Services Monitoring MIB [<a href="#ref-4" title=""Network Services Monitoring MIB"">4</a>]......................<a href="#page-6">6</a> |
| 48 |
<a href="#section-4.4">4.4</a>. Application MIB [<a href="#ref-5" title=""Definition of Managed Objects for Applications"">5</a>]......................................<a href="#page-7">7</a> |
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Kalbfleisch Informational [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc2039">RFC 2039</a> WWW Track MIBs November 1996</span> |
| 55 |
|
| 56 |
|
| 57 |
<a href="#section-5">5</a>. Summary of Existing Standards Track MIBs.................<a href="#page-8">8</a> |
| 58 |
<a href="#section-6">6</a>. Definition of additional attributes......................<a href="#page-9">9</a> |
| 59 |
<a href="#section-7">7</a>. Usage Scenarios.........................................<a href="#page-11">11</a> |
| 60 |
<a href="#section-8">8</a>. Conclusion..............................................<a href="#page-11">11</a> |
| 61 |
<a href="#section-9">9</a>. References..............................................<a href="#page-13">13</a> |
| 62 |
<a href="#section-10">10</a>. Acknowledgments.........................................<a href="#page-13">13</a> |
| 63 |
<a href="#section-11">11</a>. Further Information.....................................<a href="#page-14">14</a> |
| 64 |
<a href="#section-12">12</a>. Security Considerations.................................<a href="#page-14">14</a> |
| 65 |
<a href="#section-13">13</a>. Authors' Address........................................<a href="#page-14">14</a> |
| 66 |
|
| 67 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Overview</span> |
| 68 |
|
| 69 |
The World Wide Web (WWW) is a network of information, accessible via |
| 70 |
a simple easy to use interface. The information is often presented |
| 71 |
in HyperText or multi-media. The information is provided by servers |
| 72 |
which are located all around the world. The usability of the web |
| 73 |
depends largely on the performance of these servers. WWW servers are |
| 74 |
typically monitored through log files. This becomes a difficult task |
| 75 |
when a single organization is responsible for a number of servers. |
| 76 |
Since many organizations currently use the Internet Standard SNMP to |
| 77 |
manage their network devices, it is desirable to treat these WWW |
| 78 |
servers as additional devices within this framework. This will allow |
| 79 |
a single Network Management Station (NMS) to automate the management |
| 80 |
of a number of WWW servers as well as the entire enterprise. Defining |
| 81 |
a standard for this purpose allows a single management application to |
| 82 |
manage a number of servers from a variety of vendors. Additionally, |
| 83 |
a formal definition of what has to be managed and how to manage it |
| 84 |
tends to lead to integrated and improved performance and fault |
| 85 |
management. |
| 86 |
|
| 87 |
Content providers are interested in the access statistics and |
| 88 |
configuration of their sites. The content provider may be the same or |
| 89 |
a different organization than the one that maintains the server as a |
| 90 |
whole. It may be possible to realize the new paradigm of "Customer |
| 91 |
Network Management" to provide this information to the content |
| 92 |
provider. This means that there exists a distinct organization |
| 93 |
different than the network operations center that is also interested |
| 94 |
in the management information from a device. Customer network |
| 95 |
management is desirable to allow each content provider on a server to |
| 96 |
access information about his own documents independent of the rest. |
| 97 |
|
| 98 |
Various organizations may be interested in SNMP manageable WWW |
| 99 |
clients and proxies as well. At this time, our focus is on WWW |
| 100 |
servers. A natural extension to this work could be a framework for |
| 101 |
managing WWW Clients and general information retrieval systems like |
| 102 |
WWW proxies, NNTP, GOPHER, FTP and WAIS. The focus of this document |
| 103 |
remains the management of WWW servers. |
| 104 |
|
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Kalbfleisch Informational [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc2039">RFC 2039</a> WWW Track MIBs November 1996</span> |
| 111 |
|
| 112 |
|
| 113 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Requirements</span> |
| 114 |
|
| 115 |
WWW servers can be viewed from several perspectives when assigning |
| 116 |
management responsibilities. For the sake of discussion, these |
| 117 |
perspectives are named the Operational Model and the Service Model. |
| 118 |
The Operational Model views WWW servers as computers with hardware, |
| 119 |
disk, OS and web server software. This model represents the actual |
| 120 |
resources that make up the machine so that it can be monitored from |
| 121 |
the perspective of resource utilization. The Service Model views the |
| 122 |
WWW server as a black box that simply handles the responses to |
| 123 |
requests from clients located on the web. |
| 124 |
|
| 125 |
The two models compliment each other while providing distinct |
| 126 |
information about the server. Members of the organization |
| 127 |
responsible for the WWW server, may be interested in one and/or both |
| 128 |
of the management models. For this reason, the management |
| 129 |
information should be scalable, for one or both models to be |
| 130 |
implemented independent of the other. |
| 131 |
|
| 132 |
With this in mind, the requirements for WWW server management can are |
| 133 |
summarized below by expanding upon those generated at the HTTP-MIB |
| 134 |
BOF. |
| 135 |
|
| 136 |
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a> Operational Model Requirements</span> |
| 137 |
|
| 138 |
<span class="h4"><a class="selflink" id="section-3.1.1" href="#section-3.1.1">3.1.1</a>. Host specific and Application Monitoring</span> |
| 139 |
|
| 140 |
This includes monitoring the utilization of CPU, disk and network |
| 141 |
capacity. |
| 142 |
|
| 143 |
<span class="h4"><a class="selflink" id="section-3.1.2" href="#section-3.1.2">3.1.2</a>. Dependencies among applications.</span> |
| 144 |
|
| 145 |
Some systems implement a number of services within a single piece of |
| 146 |
code. Others use multiple pieces of code to implement the same set of |
| 147 |
services. Because of this, dependencies develop among processes. |
| 148 |
These dependencies become critical when a particular process needs to |
| 149 |
be stopped, restarted or reconfigured. These dependencies need to be |
| 150 |
defined within the management information so that management |
| 151 |
applications can operate the systems correctly. |
| 152 |
|
| 153 |
<span class="h4"><a class="selflink" id="section-3.1.3" href="#section-3.1.3">3.1.3</a>. Error generation and reporting</span> |
| 154 |
|
| 155 |
The WWW server generally reports errors via logging facilities. The |
| 156 |
format of the log file is not well defined. It is required that a |
| 157 |
standard facility for error reporting be utilized. |
| 158 |
|
| 159 |
|
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Kalbfleisch Informational [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc2039">RFC 2039</a> WWW Track MIBs November 1996</span> |
| 167 |
|
| 168 |
|
| 169 |
<span class="h4"><a class="selflink" id="section-3.1.4" href="#section-3.1.4">3.1.4</a>. Capacity planning</span> |
| 170 |
|
| 171 |
It is required to obtain statistics which can be used for capacity |
| 172 |
planning purposes. This includes planning for increased network |
| 173 |
bandwidth, computing power, disk space, number of concurrent server |
| 174 |
threads, etc. |
| 175 |
|
| 176 |
<span class="h4"><a class="selflink" id="section-3.1.5" href="#section-3.1.5">3.1.5</a>. Log Digester</span> |
| 177 |
|
| 178 |
WWW servers generally report status information by data generated in |
| 179 |
Common Log Format [<a href="#ref-1" title=""Logging in the W3C httpd"">1</a>]. This information needs to be preserved as |
| 180 |
attributes in a MIB to facilitate remote monitoring providing a |
| 181 |
standard way to represent and retrieve the management information. |
| 182 |
|
| 183 |
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Service Model Requirements</span> |
| 184 |
|
| 185 |
<span class="h4"><a class="selflink" id="section-3.2.1" href="#section-3.2.1">3.2.1</a>. Retrieval services</span> |
| 186 |
|
| 187 |
Retrieval services are an abstract decoupling the information space |
| 188 |
from the underlying transport mechanism. The goal at this time is to |
| 189 |
focus on the requirements for management of WWW servers. There may be |
| 190 |
considerable overlap with other types of servers like (FTP, NNTP, |
| 191 |
GOPHER and WAIS). The term "retrieval services" is used here to |
| 192 |
retain this abstraction. It is required to get statistics about the |
| 193 |
usage and performance of the retrieval services. |
| 194 |
|
| 195 |
<span class="h4"><a class="selflink" id="section-3.2.2" href="#section-3.2.2">3.2.2</a>. Document information store -- managing documents.</span> |
| 196 |
|
| 197 |
Information from a WWW server can be static (a file) or dynamic (the |
| 198 |
output of some processing). Management of these two types of |
| 199 |
information sources range from maintaining access statistics and |
| 200 |
access permissions to verifying the operational status of all |
| 201 |
applications that provide the dynamic information. |
| 202 |
|
| 203 |
<span class="h4"><a class="selflink" id="section-3.2.3" href="#section-3.2.3">3.2.3</a>. Server configuration.</span> |
| 204 |
|
| 205 |
It is desirable to be able to centralize configuration management of |
| 206 |
the servers within an enterprise. |
| 207 |
|
| 208 |
<span class="h4"><a class="selflink" id="section-3.2.4" href="#section-3.2.4">3.2.4</a>. Server Control.</span> |
| 209 |
|
| 210 |
WWW servers generally need to be controlled in regards to starting |
| 211 |
and stopping them as well as rotating log files. |
| 212 |
|
| 213 |
<span class="h4"><a class="selflink" id="section-3.2.5" href="#section-3.2.5">3.2.5</a>. Quality of Service</span> |
| 214 |
|
| 215 |
Provide an indication of the quality of service the WWW server is |
| 216 |
providing. |
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Kalbfleisch Informational [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc2039">RFC 2039</a> WWW Track MIBs November 1996</span> |
| 223 |
|
| 224 |
|
| 225 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Relationship to existing IETF efforts</span> |
| 226 |
|
| 227 |
In general, a WWW server is made up of or depends upon the following |
| 228 |
components: |
| 229 |
|
| 230 |
-a general purpose workstation running some operating system |
| 231 |
-http server software to answers requests from the network |
| 232 |
-various support routines like CGI programs or external |
| 233 |
applications (like DBMS) used to access information |
| 234 |
-a document store on one or more storage devices |
| 235 |
|
| 236 |
The health and performance of each of the above components is of |
| 237 |
interest when managing a WWW server. |
| 238 |
|
| 239 |
There are a number of standards track MIB modules that are of |
| 240 |
interest to the above list of items. This list includes MIB-II [<a href="#ref-2" title=""Management Information Base for Network Management of TCP/IP-based internets: MIB- II"">2</a>], |
| 241 |
Host Resources MIB [<a href="#ref-3" title=""Host Resources MIB"">3</a>], Network Service Monitoring MIB [<a href="#ref-4" title=""Network Services Monitoring MIB"">4</a>] and |
| 242 |
Application MIB [<a href="#ref-5" title=""Definition of Managed Objects for Applications"">5</a>]. |
| 243 |
|
| 244 |
This creates an impressive list of attributes to be implemented. A |
| 245 |
definition of various levels of management of a WWW server is desired |
| 246 |
so that the implementor may scale his implementation in chunks which |
| 247 |
may include various components of each section. For instance, this |
| 248 |
may allow customer network management without requiring the other |
| 249 |
groups being implemented. |
| 250 |
|
| 251 |
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. MIB-II [<a href="#ref-2" title=""Management Information Base for Network Management of TCP/IP-based internets: MIB- II"">2</a>]</span> |
| 252 |
|
| 253 |
MIB-II defines the managed objects which should be contained within |
| 254 |
TCP/IP based devices. |
| 255 |
|
| 256 |
The WWW server should support the applicable portions of MIB-II. |
| 257 |
This set probably includes, as a minimum, the following groups: |
| 258 |
system, interfaces, udp, icmp, tcp and snmp. |
| 259 |
|
| 260 |
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. Host Resources MIB [<a href="#ref-3" title=""Host Resources MIB"">3</a>]</span> |
| 261 |
|
| 262 |
This MIB defines a uniform set of objects useful for the management |
| 263 |
of host computers independently of the operating system, network |
| 264 |
services, or any software application. |
| 265 |
|
| 266 |
The MIB is structured as six groups; each specified as either |
| 267 |
"mandatory" or "optional". If ANY "optional" group of the MIB is |
| 268 |
implemented, then ALL "mandatory" groups of the MIB must also be |
| 269 |
implemented. This may cause implementation problems for some |
| 270 |
developers since many of these attributes require intimate knowledge |
| 271 |
of the OS. |
| 272 |
|
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Kalbfleisch Informational [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc2039">RFC 2039</a> WWW Track MIBs November 1996</span> |
| 279 |
|
| 280 |
|
| 281 |
The groups defined by the MIB are: |
| 282 |
|
| 283 |
-System Group Mandatory |
| 284 |
-Storage Group Mandatory |
| 285 |
-Device Group Mandatory |
| 286 |
|
| 287 |
-device types |
| 288 |
-device table |
| 289 |
-processor table |
| 290 |
-network table |
| 291 |
-printer table |
| 292 |
-disk storage table |
| 293 |
-partition table |
| 294 |
-file-system table |
| 295 |
-file-system types |
| 296 |
-Running Software Group Optional |
| 297 |
-Running Software Performance Group Optional |
| 298 |
-Installed Software Group Optional |
| 299 |
|
| 300 |
The system group provides general status information about the host. |
| 301 |
The storage and device groups define the information about the |
| 302 |
configuration and status of the resources which compose the host. It |
| 303 |
defines the resources which make up a generic host system and how |
| 304 |
they relate to each other. Much of this information is useful for |
| 305 |
managing various aspects of a WWW server, like the file system and |
| 306 |
CPU utilization. This information is useful for meeting the |
| 307 |
operational requirements. Much of this information is however more |
| 308 |
detailed than many WWW server managers require for service level |
| 309 |
requirements. |
| 310 |
|
| 311 |
The remaining groups define software components which are installed |
| 312 |
and/or running on the host. Performance information is defined which |
| 313 |
extends that defined for each running process. Unfortunately, the |
| 314 |
mapping between running software and installed software is difficult |
| 315 |
since it is related by a foreign key (Product ID) which does not |
| 316 |
appear to be required to exist in either table [<a href="#ref-6" title=""Applicability of Host Resources MIB to Application Management"">6</a>]. There is no |
| 317 |
provision to represent a group of processes which together perform |
| 318 |
some task (IE an application made up of multiple processes). The |
| 319 |
Applications MIB WG plans to address these deficiencies. |
| 320 |
|
| 321 |
<span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a>. Network Services Monitoring MIB [<a href="#ref-4" title=""Network Services Monitoring MIB"">4</a>]</span> |
| 322 |
|
| 323 |
This MIB is one of three documents produced by the MADMAN (Message |
| 324 |
And Directory MANagement) Working group. It defines a set of general |
| 325 |
purpose attributes which would be appropriate for a range of |
| 326 |
applications that provide network services. This definition is from |
| 327 |
the perspective of the service without considering the implementation |
| 328 |
in terms of host computers or processes. Attributes provide |
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Kalbfleisch Informational [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc2039">RFC 2039</a> WWW Track MIBs November 1996</span> |
| 335 |
|
| 336 |
|
| 337 |
statistics and status on the in-bound and out-bound associations that |
| 338 |
are currently active, and which have been active. |
| 339 |
|
| 340 |
This MIB is intended to be the minimum set of attributes common |
| 341 |
across a number of Network Service Applications. Additional |
| 342 |
attributes are to be defined as necessary to manage specific network |
| 343 |
service applications. WWW servers clearly fall into the category of |
| 344 |
network service applications. All attributes in this MIB are |
| 345 |
relevant to WWW servers. |
| 346 |
|
| 347 |
The MIB consists of two tables: |
| 348 |
|
| 349 |
-applTable Mandatory |
| 350 |
-assocTable Optional |
| 351 |
|
| 352 |
The applTable describes applications that provide network services |
| 353 |
and keeps statistics of the current number of active associations and |
| 354 |
the total number of associations since application initialization. |
| 355 |
The assocTable contains more detailed information about active |
| 356 |
associations. |
| 357 |
|
| 358 |
The other two MIBs defined by MADMAN, MTA MIB [<a href="#ref-7" title=""Mail Monitoring MIB"">7</a>] and DSA MIB [<a href="#ref-8" title=""X.500 Directory Monitoring MIB"">8</a>], |
| 359 |
are not relevant to the management of WWW services. They do, |
| 360 |
however, demonstrate how to extend the Network Services Monitoring |
| 361 |
MIB for a specific set of applications. |
| 362 |
|
| 363 |
<span class="h3"><a class="selflink" id="section-4.4" href="#section-4.4">4.4</a>. Application MIB [<a href="#ref-5" title=""Definition of Managed Objects for Applications"">5</a>]</span> |
| 364 |
|
| 365 |
The Application MIB WG is defining two separate MIBs: the sysApplMib |
| 366 |
and the applMib. The first defines attributes that can be monitored |
| 367 |
without instrumenting the applications. The second will define |
| 368 |
additional attributes requiring application instrumentation. |
| 369 |
|
| 370 |
The sysApplMIB allows for the description of applications as a |
| 371 |
collection of executables, and files installed and executing on a |
| 372 |
host computer. The objects support configuration, fault and |
| 373 |
performance management of some of the basic attributes of application |
| 374 |
software. |
| 375 |
|
| 376 |
|
| 377 |
|
| 378 |
|
| 379 |
|
| 380 |
|
| 381 |
|
| 382 |
|
| 383 |
|
| 384 |
|
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">Kalbfleisch Informational [Page 7]</span></pre> |
| 389 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span> |
| 390 |
<span class="grey"><a href="./rfc2039">RFC 2039</a> WWW Track MIBs November 1996</span> |
| 391 |
|
| 392 |
|
| 393 |
The groups defined in the sysApplMIB are: |
| 394 |
|
| 395 |
-System Application Installed Group Mandatory |
| 396 |
-sysApplInstalledTable |
| 397 |
-sysApplCfgElmtTable |
| 398 |
|
| 399 |
-System Application Run Group Mandatory |
| 400 |
-sysApplRunTable |
| 401 |
-SysApplPastRunTable |
| 402 |
-sysApplElmtRunTable |
| 403 |
-sysApplElmtPastRunTable |
| 404 |
|
| 405 |
The sysApplInstalledTable captures what applications are installed on |
| 406 |
a particular host and the sysApplCfgElmtTable provides information |
| 407 |
regarding the executables and non executable files which collectively |
| 408 |
compose the application. The sysApplRunTable contains the application |
| 409 |
instances which are currently running and the sysApplPastRunTable |
| 410 |
contains a history about applications which have previously executed |
| 411 |
on the host. The sysApplElmtRunTable contains the process instances |
| 412 |
which are currently running and sysApplElmtPastRunTable contains a |
| 413 |
history about processes which have previously executed on the host. |
| 414 |
|
| 415 |
It should be noted that two implementations of the same set of |
| 416 |
network services may each define a different set of processes and |
| 417 |
files within this MIB. Ultimately enough management information is |
| 418 |
needed so that these different implementations can at least be |
| 419 |
managed similarly. |
| 420 |
|
| 421 |
WWW servers fall into the general category of application software. |
| 422 |
Therefore the attributes of this MIB are applicable if the process |
| 423 |
level detail is requested to meet the Operational Model requirements. |
| 424 |
|
| 425 |
The Application MIB WG is to resolve the problems described above |
| 426 |
with the relationship between the running and installed software of |
| 427 |
the Host Resources MIB. |
| 428 |
|
| 429 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Summary of Existing Standards Track MIBs</span> |
| 430 |
|
| 431 |
The existing MIBs are largely orthogonal as demonstrated by the |
| 432 |
diagram below. Host Resources relates network information to the |
| 433 |
interfaces defined in MIB-II. The system application MIB relates its |
| 434 |
running element table to the equivalent entry in the Host Resources |
| 435 |
running software table. |
| 436 |
|
| 437 |
It should be noted that the running software of the Host Resources |
| 438 |
includes ALL software running on the host, while the running element |
| 439 |
table of the system application MIB only includes "interesting" |
| 440 |
processes of monitored applications. |
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
<span class="grey">Kalbfleisch Informational [Page 8]</span></pre> |
| 445 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span> |
| 446 |
<span class="grey"><a href="./rfc2039">RFC 2039</a> WWW Track MIBs November 1996</span> |
| 447 |
|
| 448 |
|
| 449 |
In the diagram below, "Other Services", "Application Specific MIBs" |
| 450 |
and "Application MIB" represent work to be done or in progress. |
| 451 |
|
| 452 |
+---------------+ |
| 453 |
| Application | |
| 454 |
| Specific MIBs | |
| 455 |
+---------------+ |
| 456 |
| |
| 457 |
+--------+ +---+ +---+ +---------------+ |
| 458 |
|Other | |MTA| |DSA| | Application | |
| 459 |
|services| |MIB| |MIB| | MIB | |
| 460 |
+--------+ +---+ +---+ +---------------+ |
| 461 |
| | | | |
| 462 |
+--------------------+ +---------------+ +--------------+ +------+ |
| 463 |
| Network Services | | System | |Host Resources| |MIB-II| |
| 464 |
| Monitoring MIB | |Application MIB|--| MIB |--| | |
| 465 |
+--------------------+ +---------------+ +--------------+ +------+ |
| 466 |
|
| 467 |
The stack of MIBs above "Network Services Monitoring MIB" represent |
| 468 |
monitoring from the Service Model. The other stacks represent |
| 469 |
monitoring from the Operational Model. Neither of these stacks goes |
| 470 |
to the level of specific detail for any application. The author is of |
| 471 |
the opinion that HTTP or Web Server specific MIBs would exist at the |
| 472 |
top of each stack to represent the service and implementation view of |
| 473 |
the server respectively. There should be a relationship between |
| 474 |
these two perspectives defined so that the correlations between the |
| 475 |
two perspectives is possible. This relationship would be useful for |
| 476 |
general application and service monitoring in addition to just web |
| 477 |
servers. However, it is not of specific interest to either the |
| 478 |
MADMAN WG or the Application MIB WG. It is therefore suggested that |
| 479 |
such a relationship is defined in a general case outside of either of |
| 480 |
those groups that would be applicable for WWW servers as well as for |
| 481 |
other application to service mappings. |
| 482 |
|
| 483 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Definition of additional attributes</span> |
| 484 |
|
| 485 |
The existing MIB attributes meet the Operational Model Requirement |
| 486 |
for tracking information specific to a host. Specifically, MIB-II, |
| 487 |
Host Resources and the Applications MIB address these items. The |
| 488 |
Network Services MIB addresses a portion of the service model |
| 489 |
requirement for the decoupling of the information space from the |
| 490 |
transport mechanism. |
| 491 |
|
| 492 |
Several sets of additional attributes are needed to meet the |
| 493 |
remaining requirements. These additional attributes may be generally |
| 494 |
applicable to other network information retrieval services (like FTP, |
| 495 |
NNTP, GOPHER and WAIS) as well as client and proxy management. |
| 496 |
Management of these services is not the scope of this document. |
| 497 |
|
| 498 |
|
| 499 |
|
| 500 |
<span class="grey">Kalbfleisch Informational [Page 9]</span></pre> |
| 501 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span> |
| 502 |
<span class="grey"><a href="./rfc2039">RFC 2039</a> WWW Track MIBs November 1996</span> |
| 503 |
|
| 504 |
|
| 505 |
These additional attributes can be classified as: |
| 506 |
|
| 507 |
1) Definition of relationship between the Network Services Monitoring |
| 508 |
and Application MIBs. This allows the functional organization of |
| 509 |
the server to be known. It allows the management application to |
| 510 |
understand the effect of restarting specific processes on the |
| 511 |
services provided. This addresses the Operational Model |
| 512 |
requirement to model dependencies between applications. |
| 513 |
|
| 514 |
2) Additions to generic Network Services Monitoring MIB. A draft [<a href="#ref-9" title=""Definitions of Managed Objects for HTTP"">9</a>] |
| 515 |
has already been circulated due to the work of a mailing list and |
| 516 |
a sample implementation. These attributes list a summary at the |
| 517 |
service level of the configuration and the health of the server. |
| 518 |
From this, performance metrics can be observed. In addition, the |
| 519 |
health of the server in terms of data timeouts is known. These |
| 520 |
attributes address the requirement for Operational Model tracking |
| 521 |
of specific activity and the requirement for Service Model |
| 522 |
retrieval services. |
| 523 |
|
| 524 |
3) Document storage and access statistics are needed to address |
| 525 |
service model requirements. |
| 526 |
|
| 527 |
4) Additions to Application MIB are required to address server |
| 528 |
configuration requirements in the service model. |
| 529 |
|
| 530 |
5) Error and fault management attributes are required to address |
| 531 |
requirements for tracking specific activity of the web server. |
| 532 |
|
| 533 |
6) Configuration and Control are items that may be able to be defined |
| 534 |
in a general way within the applications MIB. If not, a specific |
| 535 |
definition would be required here. |
| 536 |
|
| 537 |
Of the items listed above, (1) is needed on a general basis. The |
| 538 |
others appear to the author as WWW server specific unless the scope |
| 539 |
of the work is opened to WWW clients and proxies as well as other |
| 540 |
services (like NNTP, FTP, GOPHER and WAIS). |
| 541 |
|
| 542 |
|
| 543 |
|
| 544 |
|
| 545 |
|
| 546 |
|
| 547 |
|
| 548 |
|
| 549 |
|
| 550 |
|
| 551 |
|
| 552 |
|
| 553 |
|
| 554 |
|
| 555 |
|
| 556 |
<span class="grey">Kalbfleisch Informational [Page 10]</span></pre> |
| 557 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span> |
| 558 |
<span class="grey"><a href="./rfc2039">RFC 2039</a> WWW Track MIBs November 1996</span> |
| 559 |
|
| 560 |
|
| 561 |
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Usage Scenarios</span> |
| 562 |
|
| 563 |
The example scenario will be a single host computer which implements |
| 564 |
WWW services using the "virtual domain" concept. In this model, a |
| 565 |
single host performs as the WWW server for one or more addresses. |
| 566 |
For the purpose of example, we will specify that there are three |
| 567 |
domains being serviced from this host whose WWW servers are: |
| 568 |
|
| 569 |
-www.a.com |
| 570 |
-www.b.com |
| 571 |
-www.c.com |
| 572 |
|
| 573 |
Some implementations may implement these services as one set of |
| 574 |
processes that handle requests for each of the addresses. Others may |
| 575 |
implement these services as a set of processes for each address. |
| 576 |
This means that the relationship defined between the Network Services |
| 577 |
Monitoring MIB and Application MIB components of the management |
| 578 |
information may vary between different implementations of the same |
| 579 |
configuration. |
| 580 |
|
| 581 |
MIB-II and Host Resources would provide the information about the |
| 582 |
host including the CPU, disk and network. The Host Resource running |
| 583 |
table provide information on the processes in the system. |
| 584 |
|
| 585 |
There would be an entry in the Network Services Monitoring applTable |
| 586 |
for each virtual domain. In addition, the assocTable shows which |
| 587 |
connections are currently active. An extension to the association |
| 588 |
table would be helpful to provide information as to what is being |
| 589 |
transmitted. |
| 590 |
|
| 591 |
The sysApplMib would have entries in its installed software tables |
| 592 |
for the web server software and each "interesting" component. This |
| 593 |
should include the server binary, CGI programs, configuration files |
| 594 |
and possibly the server log files. Depending on the implementation |
| 595 |
of the server, the processes for each domain may show up in the same |
| 596 |
or different running software tables. |
| 597 |
|
| 598 |
Additional information as described in the previous section would |
| 599 |
round out the management information that would be available for the |
| 600 |
WWW server. |
| 601 |
|
| 602 |
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Conclusion</span> |
| 603 |
|
| 604 |
A number of currently defined attributes are useful for management of |
| 605 |
a WWW server. Specifically, MIB-II and Host Resources should be |
| 606 |
considered for monitoring the health of the machine in terms of host |
| 607 |
and network configuration and capacity. The Network Services |
| 608 |
Monitoring MIB and the Application MIBs provide a general framework |
| 609 |
|
| 610 |
|
| 611 |
|
| 612 |
<span class="grey">Kalbfleisch Informational [Page 11]</span></pre> |
| 613 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span> |
| 614 |
<span class="grey"><a href="./rfc2039">RFC 2039</a> WWW Track MIBs November 1996</span> |
| 615 |
|
| 616 |
|
| 617 |
to represent the components of the WWW server from both a service and |
| 618 |
implementation perspective. The Network Services Monitoring MIB |
| 619 |
suggests that extensions are necessary to cover specific network |
| 620 |
application monitoring. A set of such attributes can be well defined |
| 621 |
to provide status information of the WWW server. The Application MIB |
| 622 |
suggests similar extensions. Some of these attributes may be generic |
| 623 |
to all applications, and thus be implemented within the scope of the |
| 624 |
applMib. It is the opinion of this author that there will still |
| 625 |
remain specific instrumentation for WWW servers that can not, and |
| 626 |
should not, be covered in the Network Services Monitoring and |
| 627 |
Application MIBs. |
| 628 |
|
| 629 |
Since the Network Services Monitoring MIB and the Applications MIB |
| 630 |
represent orthogonal efforts of management, it is desirable to define |
| 631 |
the relationship between the two in a standard way. This definition |
| 632 |
is probably more than a simple pointer from one table to another. |
| 633 |
Since it is outside the scope of either of those efforts, it is this |
| 634 |
author's opinion that that definition could and should be addressed |
| 635 |
within the scope of defining management of a specific application (IE |
| 636 |
WWW servers). This defintion although defined for a particular |
| 637 |
application, should be useful in a general way to describe the |
| 638 |
relationship between the Network Services Monitoring MIB and the |
| 639 |
Applications MIB. |
| 640 |
|
| 641 |
Additional attributes are needed in order to meet all of the |
| 642 |
requirements specified in this document. An IETF standard would |
| 643 |
prevent independent developments of this effort in many enterprise |
| 644 |
MIBs. It also allows management applications to control servers from |
| 645 |
multiple vendors. It is likely that as the work in this area |
| 646 |
progresses, the management information will be useful for other |
| 647 |
Network Information Retrieval services (like FTP, GOPHER, WAIS and |
| 648 |
NNTP) as well. |
| 649 |
|
| 650 |
Finally, the Operational Model and Service Model Requirements lead to |
| 651 |
two main uses of the management information. Design of the MIB |
| 652 |
including the usage of the existing MIBs should allow one or the |
| 653 |
other or both of these models to be implemented in a standard way. |
| 654 |
This may be desirable depending specifically on the audience of the |
| 655 |
data, the cost of instrumentation and the resources of the system. |
| 656 |
|
| 657 |
|
| 658 |
|
| 659 |
|
| 660 |
|
| 661 |
|
| 662 |
|
| 663 |
|
| 664 |
|
| 665 |
|
| 666 |
|
| 667 |
|
| 668 |
<span class="grey">Kalbfleisch Informational [Page 12]</span></pre> |
| 669 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span> |
| 670 |
<span class="grey"><a href="./rfc2039">RFC 2039</a> WWW Track MIBs November 1996</span> |
| 671 |
|
| 672 |
|
| 673 |
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. References</span> |
| 674 |
|
| 675 |
[<a id="ref-1">1</a>] Anonymous, "Logging in the W3C httpd", |
| 676 |
<a href="http://www.w3.org/hypertext/WWW/Daemon/User/Config/Logging.html">http://www.w3.org/hypertext/WWW/Daemon/User/Config/Logging.html</a>, |
| 677 |
W3C, July 1995. |
| 678 |
|
| 679 |
[<a id="ref-2">2</a>] McCloghrie, K., and M. Rose, Editors, "Management Information |
| 680 |
Base for Network Management of TCP/IP-based internets: MIB- |
| 681 |
II", STD 17, <a href="./rfc1213">RFC 1213</a>, Hughes LAN Systems, Performance |
| 682 |
Systems International, March 1991. |
| 683 |
|
| 684 |
[<a id="ref-3">3</a>] Grillo, P., and S. Waldbusser, "Host Resources MIB", <a href="./rfc1514">RFC 1514</a>, |
| 685 |
Network Innovations, Intel Corporation, Carnegie Mellon |
| 686 |
University, September 1993. |
| 687 |
|
| 688 |
[<a id="ref-4">4</a>] Kille, S., and N. Freed, "Network Services Monitoring MIB", |
| 689 |
<a href="./rfc1565">RFC 1565</a>, ISODE Consortium, Innosoft, January 1994. |
| 690 |
|
| 691 |
[<a id="ref-5">5</a>] Saperia, J., C. Krupczak, R. Sturm, and J. Weinstock, "Definition |
| 692 |
of Managed Objects for Applications", Work in Progress. |
| 693 |
|
| 694 |
[<a id="ref-6">6</a>] Krupczak, C. and S. Waldbusser, "Applicability of Host Resources |
| 695 |
MIB to Application Management", Empire Technologies, Inc., |
| 696 |
International Network Services, October 1995. |
| 697 |
|
| 698 |
[<a id="ref-7">7</a>] Kille, S., and N. Freed, "Mail Monitoring MIB", <a href="./rfc1566">RFC 1566</a>, ISODE |
| 699 |
Consortium, Innosoft, January 1994. |
| 700 |
|
| 701 |
[<a id="ref-8">8</a>] Mansfield, G., and S. Kille, "X.500 Directory Monitoring MIB", |
| 702 |
<a href="./rfc1567">RFC 1567</a>, AIC Systems Laboratory, ISODE Consortium, January 1994. |
| 703 |
|
| 704 |
[<a id="ref-9">9</a>] Hazewinkel, H., E. van Hengstum, A. Pras, "Definitions of Managed |
| 705 |
Objects for HTTP", Work in Progress. |
| 706 |
|
| 707 |
<span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. Acknowledgments</span> |
| 708 |
|
| 709 |
This document was produced at the request of the Network Management |
| 710 |
Area Director following the HTTP-MIB BOF at the 35th IETF meeting to |
| 711 |
report on the applicability of the existing standards track MIBs to |
| 712 |
management of WWW servers. |
| 713 |
|
| 714 |
|
| 715 |
|
| 716 |
|
| 717 |
|
| 718 |
|
| 719 |
|
| 720 |
|
| 721 |
|
| 722 |
|
| 723 |
|
| 724 |
<span class="grey">Kalbfleisch Informational [Page 13]</span></pre> |
| 725 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span> |
| 726 |
<span class="grey"><a href="./rfc2039">RFC 2039</a> WWW Track MIBs November 1996</span> |
| 727 |
|
| 728 |
|
| 729 |
The author gratefully acknowledges the comments of the following |
| 730 |
individuals: |
| 731 |
|
| 732 |
Ned Freed, [email protected] |
| 733 |
Innosoft, Inc. |
| 734 |
|
| 735 |
Harrie Hazewinkel, [email protected] |
| 736 |
University of Twente |
| 737 |
|
| 738 |
Cheryl Krupczak, [email protected] |
| 739 |
Empire Technologies, Inc. |
| 740 |
|
| 741 |
Rui Meneses, [email protected] |
| 742 |
Centre for Earth Observation |
| 743 |
|
| 744 |
Jon Saperia, [email protected] |
| 745 |
BGS Systems, Inc. |
| 746 |
|
| 747 |
Juergen Schoenwaelder, [email protected] |
| 748 |
University of Twente |
| 749 |
|
| 750 |
Chris Wellens, [email protected] |
| 751 |
InterWorking Labs, Inc. |
| 752 |
|
| 753 |
<span class="h2"><a class="selflink" id="section-11" href="#section-11">11</a>. Further Information</span> |
| 754 |
|
| 755 |
The current status of the HTTP-MIB standardization can be found on |
| 756 |
the World Wide Web at <URL:http://http-mib.onramp.net/>. An email |
| 757 |
list is in operation for discussion of this topic. To subscribe, |
| 758 |
send email to "[email protected]" with the message body of |
| 759 |
"subscribe HTTP-MIB". |
| 760 |
|
| 761 |
<span class="h2"><a class="selflink" id="section-12" href="#section-12">12</a>. Security Considerations</span> |
| 762 |
|
| 763 |
Security issues are not discussed in this memo. |
| 764 |
|
| 765 |
<span class="h2"><a class="selflink" id="section-13" href="#section-13">13</a>. Authors' Address</span> |
| 766 |
|
| 767 |
Carl W. Kalbfleisch |
| 768 |
OnRamp Technologies, Inc. |
| 769 |
Email: [email protected] |
| 770 |
1950 Stemmons Frwy |
| 771 |
2026 INFOMART |
| 772 |
Dallas, TX 75207, USA Tel: (214) 672-7246 |
| 773 |
[email protected] Fax: (214) 672-7275 |
| 774 |
|
| 775 |
|
| 776 |
|
| 777 |
|
| 778 |
|
| 779 |
|
| 780 |
Kalbfleisch Informational [Page 14] |
| 781 |
</pre> |