OID reference

vosUserTrapCommFileName

1.3.6.1.4.1.10002.1.1.1.1.9

Description

Full path name of the current user trap destination file being used by the agent. If the file snmpd.user_trap exists when the agent starts up, user traps are routed using this file. If this file is not found when the agent starts up, the file snmpd.trap_comm will be used to specify user trap destinations. Set-requests…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.10002.1.1.1.1 (memory, os400, vos)
Node code
9
Node name
vosUserTrapCommFileName
Numeric OID
1.3.6.1.4.1.10002.1.1.1.1.9
URN notation
urn:oid:1.3.6.1.4.1.10002.1.1.1.1.9
Type
OBJECT-TYPE
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 10002 1 1 1 1 9}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) frogfoot(10002) servers(1) system(1) resources(1) memory(1) vosUserTrapCommFileName(9)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) frogfoot(10002) servers(1) system(1) resources(1) os400(1) vosUserTrapCommFileName(9)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) frogfoot(10002) servers(1) system(1) resources(1) vos(1) vosUserTrapCommFileName(9)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) frogfoot(10002) servers(1) system(1) resources(1) memory(1) vosUserTrapCommFileName(9)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) frogfoot(10002) servers(1) system(1) resources(1) os400(1) vosUserTrapCommFileName(9)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) frogfoot(10002) servers(1) system(1) resources(1) vos(1) vosUserTrapCommFileName(9)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) frogfoot(10002) servers(1) system(1) resources(1) memory(1) vosUserTrapCommFileName(9)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) frogfoot(10002) servers(1) system(1) resources(1) os400(1) vosUserTrapCommFileName(9)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) frogfoot(10002) servers(1) system(1) resources(1) vos(1) vosUserTrapCommFileName(9)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) frogfoot(10002) servers(1) system(1) resources(1) memory(1) vosUserTrapCommFileName(9)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) frogfoot(10002) servers(1) system(1) resources(1) os400(1) vosUserTrapCommFileName(9)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) frogfoot(10002) servers(1) system(1) resources(1) vos(1) vosUserTrapCommFileName(9)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) frogfoot(10002) servers(1) system(1) resources(1) memory(1) vosUserTrapCommFileName(9)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) frogfoot(10002) servers(1) system(1) resources(1) os400(1) vosUserTrapCommFileName(9)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) frogfoot(10002) servers(1) system(1) resources(1) vos(1) vosUserTrapCommFileName(9)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) frogfoot(10002) servers(1) system(1) resources(1) memory(1) vosUserTrapCommFileName(9)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/10002/1/1/1/1/9
  • /ISO/Identified-Organization/6/1/4/1/10002/1/1/1/1/9
  • /ISO/3/6/1/4/1/10002/1/1/1/1/9
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/10002/servers/system/resources/memory/vosUserTrapCommFileName
  • /iso/identified-organization/dod/internet/private/enterprise/10002/servers/system/resources/os400/vosUserTrapCommFileName
  • /iso/identified-organization/dod/internet/private/enterprise/10002/servers/system/resources/vos/vosUserTrapCommFileName
  • /iso/identified-organization/dod/internet/private/enterprise/frogfoot/servers/system/resources/memory/vosUserTrapCommFileName
  • /iso/identified-organization/dod/internet/private/enterprise/frogfoot/servers/system/resources/os400/vosUserTrapCommFileName
  • /iso/identified-organization/dod/internet/private/enterprise/frogfoot/servers/system/resources/vos/vosUserTrapCommFileName
  • /iso/identified-organization/dod/internet/private/enterprises/10002/servers/system/resources/memory/vosUserTrapCommFileName
  • /iso/identified-organization/dod/internet/private/enterprises/10002/servers/system/resources/os400/vosUserTrapCommFileName
  • /iso/identified-organization/dod/internet/private/enterprises/10002/servers/system/resources/vos/vosUserTrapCommFileName
  • /iso/identified-organization/dod/internet/private/enterprises/frogfoot/servers/system/resources/memory/vosUserTrapCommFileName
  • /iso/identified-organization/dod/internet/private/enterprises/frogfoot/servers/system/resources/os400/vosUserTrapCommFileName
  • /iso/identified-organization/dod/internet/private/enterprises/frogfoot/servers/system/resources/vos/vosUserTrapCommFileName
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/10002/servers/system/resources/memory/vosUserTrapCommFileName
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/10002/servers/system/resources/os400/vosUserTrapCommFileName
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/10002/servers/system/resources/vos/vosUserTrapCommFileName
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/frogfoot/servers/system/resources/memory/vosUserTrapCommFileName
  • Additional combinations skipped.

Meaning

Descriptions

1 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

Full path name of the current user trap destination file being
used by the agent. If the file snmpd.user_trap exists when
the agent starts up, user traps are routed using this file. If
this file is not found when the agent starts up, the file
snmpd.trap_comm will be used to specify user trap destinations.
Set-requests on this file name cause the agent to reinitialize
its user trap destinations using the data in the new file name.
Sources for this description

MIBdepot

Parsed from vossysmgr.mib.txt · comtek · COMTEK-MIB

Historical records

Additional source information

Information from MIBdepot 
vosUserTrapCommFileName OBJECT-TYPE
     SYNTAX  DisplayString (SIZE (0..256))
     ACCESS  read-write
     STATUS  mandatory
     DESCRIPTION
         "Full path name of the current user trap destination file being 
         used by the agent.  If the file snmpd.user_trap exists when 
         the agent starts up, user traps are routed using this file.  If 
         this file is not found when the agent starts up, the file 
         snmpd.trap_comm will be used to specify user trap destinations.  
         Set-requests on this file name cause the agent to reinitialize 
         its user trap destinations using the data in the new file name."
     ::= { vos 9 }

Siblings (8)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.10002.1.1.1.1.1 memTotal, os400SysName, vosNumModules00 Number of modules.
1.3.6.1.4.1.10002.1.1.1.1.2 memFree, os400SysModel, vosTable17 A simplified version of what is read from
s$get_module_usage().
1.3.6.1.4.1.10002.1.1.1.1.3 memBuffer, os400NumQHistoryEntries, vosNumRedLights00 Number of entries in the red light table.
1.3.6.1.4.1.10002.1.1.1.1.4 memCache, os400QHistoryTable, vosRedLightTable14 A table of messages from the >system>hardware_log.*.
1.3.6.1.4.1.10002.1.1.1.1.5 os400UtcOffset, vosConfigFileName00 Full path name of current configuration file used by agent.
The agent always uses the file snmpd.config as its configuration
file…
1.3.6.1.4.1.10002.1.1.1.1.6 vosInputQueueMessage00 Most recent remote console message sent by NMS to agent.
This MIB item is the method in which remote console
commands are entered…
1.3.6.1.4.1.10002.1.1.1.1.7 vosInputQueueName00 Input Queue name where the agent is to write remote
console messages for processing by NM*Console. This
name is specified in the…
1.3.6.1.4.1.10002.1.1.1.1.8 vosTrapCommFileName00 Full path name of the current trap destination file being used
by the agent. The agent always starts up using the file
snmpd.trap…