EMPIRE-SVCRSP :: svcRspTableArgs

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsEMPIRE-SVCRSPsvcRspTableArgs

svcRspTableArgs

Module: EMPIRE-SVCRSP

OID (symbolic): EMPIRE-SVCRSP::svcRspTableArgs

OID (numeric): 1.3.6.1.4.1.546.16.6.10.1.4

Node type: OBJECT-TYPE

Type: DisplayString

Access: read-write

Description: Service-specific arguments used for measuring purposes. Limit of 256 characters. Example service arguments are: dns: dns-server hostname http: URL [proxy-server] [username:user password:pass] ftp: ftp-server username passwd pop3: pop3-server username passwd nntp: nntp-server smtp: smtp-server ping: system-name packetsize tcpconnect: system-name port custom: script-name https: URL [proxy-server] [username:user password:pass]

What is svcRspTableArgs?

This read-write DisplayString (up to 256 characters) holds the service-specific arguments for a test, whose expected format depends on svcRspTableSvc — for example "system-name packetsize" for ping, or a URL with optional proxy and credentials for http/https. An admin fills this in to tell the test what to check, such as which server, URL, or account to use. For an ftp test, setting svcRspTableArgs to "ftp.example.com user1 pass1" tells the agent which server and credentials to use for the FTP response-time check.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.546.16.6.10.1.4
snmpwalk -v2c -c public <target> EMPIRE-SVCRSP::svcRspTableArgs

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.546.16.6.10.1.4.1
snmpget -v2c -c public <target> EMPIRE-SVCRSP::svcRspTableArgs.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.546.16.6.10.1.4.1 s <value>

Start monitoring Server running Empire/CA SystemEDGE monitoring agent (service response/availability tests) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the EMPIRE-SVCRSP::svcRspTableArgs OID value, configure state conditions and alerts, and monitor any Server running Empire/CA SystemEDGE monitoring agent (service response/availability tests) from a single console.

OID Breakdown

Upper-level ancestors (8 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.546empireCAHYPERV-AIM-MIB
1.3.6.1.4.1.546.16applicationsCAHYPERV-AIM-MIB
Numeric OIDNameModule
1.3.6.1.4.1.546.16.6svcRspEMPIRE-SVCRSP
1.3.6.1.4.1.546.16.6.10svcRspTableEMPIRE-SVCRSP
1.3.6.1.4.1.546.16.6.10.1svcRspTableEntryEMPIRE-SVCRSP
1.3.6.1.4.1.546.16.6.10.1.4svcRspTableArgsEMPIRE-SVCRSP