APM MIB Update

Steve Waldbusser

San Diego IETF

12/11/00

New APM MIB structure

All applications and application verbs identified by appLocalIndex

AppLocalIndex is 2 things:– Integer32 Textual Convention

• Used for agent-assigned index values to identify applications• Any object with this type has values assigned by the agent out of the same

space• Therefore, no 2 values of any objects with type AppLocalIndex may conflict

– Index to apmAppDirectoryTable• All values of all objects with type AppLocalIndex have an entry in this table• apmAppDirectoryTable provides configuration information for each application,

most notably the bucket boundaries• Used to be protocolDirectoryExtensions table

Where are protocols assigned?

Protocol Directory Table– Registered applications (e.g. Pop3, SAP/R3)– Registered application verbs (e.g. Pop3 RETR, SAP/R3 AR)– Either standards-based or commercial apps

• Unlikely to find custom in-house apps here

– Populated by the vendor with “limited extensibility” for population by the customer/NMS

apmHttpFilterTable– Web-hosted applications identified by a common URL prefix and/or server address

(e.g. /finance/expenses.cgi, /hr/vacationrequest.cgi)– Populated by customer/NMS

apmUserDefinedTable– Custom in-house applications (e.g. “Set Credit Limit”, “FindLowestFare”)– Populated by “implementation-specific” means

• apmUserDefinedTable is read-only• Practically speaking, this is populated by customer

Example of Registration Tables

Protocol ProtocolDirLocalIndex

SMTP 25

HTTP 80

Protocol Directory Table

Example of Registration Tables

Protocol ProtocolDirLocalIndex

SMTP 25

HTTP 80

Protocol Directory Table

apmHttpFilterTable

FilterIndex FilterAppLocalIndex URL

1 101 /index.html

2 102 /finance/expense.cgi

3 103 /hr/vacationrequest.cgi

Example of Registration Tables

Protocol ProtocolDirLocalIndex

SMTP 25

HTTP 80

Protocol Directory Table

apmHttpFilterTable

FilterIndex FilterAppLocalIndex URL

1 101 /index.html

2 102 /finance/expense.cgi

3 103 /hr/vacationrequest.cgi

Read/Write: Chosen randomly by manager when creating row

ReadOnly: Assigned by agent from appLocalIndex number space when row is created

Example of Registration Tables

Protocol ProtocolDirLocalIndex

SMTP 25

HTTP 80

Protocol Directory Table

apmHttpFilterTable

FilterIndex FilterAppLocalIndex URL

1 101 /index.html

2 102 /finance/expense.cgi

3 103 /hr/vacationrequest.cgi

apmUserDefinedTableAppLocalIndex Application

104 “Schedule Delivery”

105 “Set Credit Limit”

106 “Find Lowest Fare”

apmAppDirectoryTable

AppLocalIndex ResponsivenessType

Config Boundary1 Boundary2 Boundary3

25 Transaction (1) On 1 2 …80 Transaction (1) On 1 2 …80 Throughput(2) On 20 Kbps 100 Kbps …101 Transaction (1) On 2 5 …102 Transaction (1) On 5 15 …103 Transaction (1) On 5 15 …104 Transaction (1) On 5 15 …105 Transaction (1) On 5 15 …106 Transaction (1) On 5 15 …

Indexing Changes

protocolDirID was the index for a number of “data” tables

It has been replaced everywhere by appLocalIndex– Allows data tables to record metrics for applications defined in

apmHttpFilterTable and apmUserDefinedTable– It’s also greatly shortens the index of these tables

apmReportTable Example

Assume application aggregation for simplicity– Fewer Rows– Zeros for ServerAddress and ClientID

ApmReportControlIndex

ApmReportIndex

ApmReportAppLocalIndex

ApmReportServerAddr

ApmReportClientID

ApmReportRspType

ApmReportTransCount

…

1 1 25 0 0 1 345 …

1 1 80 0 0 1 657 …1 1 80 0 0 2 657 …1 1 101 0 0 1 24 …1 1 102 0 0 1 53 …1 1 103 0 0 1 24 …1 1 104 0 0 1 53 …1 1 105 0 0 1 63 …1 1 106 0 0 1 46 …1 2 25 0 0 1 524 …… … … … … … … …

Throughput-Oriented: These are request-response transactions that have larger and widely varying amounts of data to transfer. The responsiveness metric for throughput-oriented applications is the data rate. However, for consistency with the other metrics, where lower values are better, this metric is expressed as seconds per terabit. For example, 2 Kilobits per second is equal to 500 million sec/Terabit and 1 Gigabit per second is equal to 1000 sec/Terabit. Software that displays these metrics to humans is urged to convert them to a more familiar form when displaying them,for example kilobits per second or megabits per second.