All MIBs › INKTOMI-TS-MIB › invalidConfig

invalidConfig

OID (symbolic): INKTOMI-TS-MIB::invalidConfig

OID (numeric): 1.3.6.1.4.1.1967.3.1.3.4.0.3

Node type: NOTIFICATION-TYPE

Description: Warning. Traffic server was started with an invalid configuration. mgralarm: MGMT-ALARM-PROXY-CONFIG-ERROR

Examples

Send this trap to an SNMP manager — replace <manager> with the IP or hostname of your monitoring server (SNMPv2c):

snmptrap -v2c -c public <manager> '' INKTOMI-TS-MIB::invalidConfig
snmptrap -v2c -c public <manager> '' 1.3.6.1.4.1.1967.3.1.3.4.0.3

Listen for incoming traps on the manager host (-f keeps it in the foreground, -Lo prints to stdout — useful for testing):

snmptrapd -f -Lo -c /dev/null authCommunity log public

Example snmptrapd log entry:

zoo11-linux.zoo [UDP: [192.168.30.111]:58762->[192.168.30.10]:162]:
  DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (58316682) 6 days, 17:59:26.82
  SNMPv2-MIB::snmpTrapOID.0 = OID: INKTOMI-TS-MIB::invalidConfig

Start monitoring Inktomi Traffic Server caching proxies with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the INKTOMI-TS-MIB::invalidConfig OID value, configure state conditions and alerts, and monitor any Inktomi Traffic Server caching proxies from a single console.

OID Breakdown

Upper-level ancestors (10 from the standard OID tree / other modules)

Numeric OID	Name	Module
1	iso	LANART-AGENT
1.3	org	AirPair-MIB
1.3.6	dod	AirPair-MIB
1.3.6.1	internet	AirPair-MIB
1.3.6.1.4	private	AirPair-MIB
1.3.6.1.4.1	enterprises	AirPair-MIB
1.3.6.1.4.1.1967	vendorInktomi	INKTOMI-GLOBAL-REG
1.3.6.1.4.1.1967.3	inktomiProducts	INKTOMI-GLOBAL-REG
1.3.6.1.4.1.1967.3.1	inktomiTSMIBs	INKTOMI-GLOBAL-REG
1.3.6.1.4.1.1967.3.1.3	inktomiTSEvents	INKTOMI-GLOBAL-REG

Numeric OID	Name	Module
1.3.6.1.4.1.1967.3.1.3.4	inktomiTSGeneralEvents	INKTOMI-TS-MIB
1.3.6.1.4.1.1967.3.1.3.4.0.3	invalidConfig	INKTOMI-TS-MIB

INKTOMI-TS-MIB :: invalidConfig

invalidConfig

Module

This MIB depends on