Reference record for OID 1.3.6.1.4.1.52642.1.1.10.2.3.1.1.1

Parent
1.3.6.1.4.1.52642.1.1.10.2.3.1.1 (fsPingTable)
Node code
1
Node name
fsPingEntry
Numeric OID
1.3.6.1.4.1.52642.1.1.10.2.3.1.1.1
URN notation
urn:oid:1.3.6.1.4.1.52642.1.1.10.2.3.1.1.1
ASN.1 notation

{1 3 6 1 4 1 52642 1 1 10 2 3 1 1 1}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) fs(52642) products(1) switch(1) switchMib(10) fsMgmt(2) fsPingMIB(3) fsPingMIBObjects(1) fsPingTable(1) fsPingEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) fs(52642) products(1) system(1) switchMib(10) fsMgmt(2) fsPingMIB(3) fsPingMIBObjects(1) fsPingTable(1) fsPingEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) fs(52642) switch(1) switch(1) switchMib(10) fsMgmt(2) fsPingMIB(3) fsPingMIBObjects(1) fsPingTable(1) fsPingEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) fs(52642) switch(1) system(1) switchMib(10) fsMgmt(2) fsPingMIB(3) fsPingMIBObjects(1) fsPingTable(1) fsPingEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) fs(52642) nmsProducts(1) switch(1) switchMib(10) fsMgmt(2) fsPingMIB(3) fsPingMIBObjects(1) fsPingTable(1) fsPingEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) fs(52642) nmsProducts(1) system(1) switchMib(10) fsMgmt(2) fsPingMIB(3) fsPingMIBObjects(1) fsPingTable(1) fsPingEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) fs(52642) fsProducts(1) switch(1) switchMib(10) fsMgmt(2) fsPingMIB(3) fsPingMIBObjects(1) fsPingTable(1) fsPingEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) fs(52642) fsProducts(1) system(1) switchMib(10) fsMgmt(2) fsPingMIB(3) fsPingMIBObjects(1) fsPingTable(1) fsPingEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) fs(52642) system(1) switch(1) switchMib(10) fsMgmt(2) fsPingMIB(3) fsPingMIBObjects(1) fsPingTable(1) fsPingEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) fs(52642) system(1) system(1) switchMib(10) fsMgmt(2) fsPingMIB(3) fsPingMIBObjects(1) fsPingTable(1) fsPingEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) fs(52642) fsProductId(1) switch(1) switchMib(10) fsMgmt(2) fsPingMIB(3) fsPingMIBObjects(1) fsPingTable(1) fsPingEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) fs(52642) fsProductId(1) system(1) switchMib(10) fsMgmt(2) fsPingMIB(3) fsPingMIBObjects(1) fsPingTable(1) fsPingEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nms(52642) products(1) switch(1) switchMib(10) fsMgmt(2) fsPingMIB(3) fsPingMIBObjects(1) fsPingTable(1) fsPingEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nms(52642) products(1) system(1) switchMib(10) fsMgmt(2) fsPingMIB(3) fsPingMIBObjects(1) fsPingTable(1) fsPingEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nms(52642) switch(1) switch(1) switchMib(10) fsMgmt(2) fsPingMIB(3) fsPingMIBObjects(1) fsPingTable(1) fsPingEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nms(52642) switch(1) system(1) switchMib(10) fsMgmt(2) fsPingMIB(3) fsPingMIBObjects(1) fsPingTable(1) fsPingEntry(1)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/52642/1/1/10/2/3/1/1/1
  • /ISO/Identified-Organization/6/1/4/1/52642/1/1/10/2/3/1/1/1
  • /ISO/3/6/1/4/1/52642/1/1/10/2/3/1/1/1
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/fs/products/switch/switchMib/fsMgmt/fsPingMIB/fsPingMIBObjects/fsPingTable/fsPingEntry
  • /iso/identified-organization/dod/internet/private/enterprise/fs/products/system/switchMib/fsMgmt/fsPingMIB/fsPingMIBObjects/fsPingTable/fsPingEntry
  • /iso/identified-organization/dod/internet/private/enterprise/fs/products/D7000/switchMib/fsMgmt/fsPingMIB/fsPingMIBObjects/fsPingTable/fsPingEntry
  • /iso/identified-organization/dod/internet/private/enterprise/fs/products/RTL8382M/switchMib/fsMgmt/fsPingMIB/fsPingMIBObjects/fsPingTable/fsPingEntry
  • /iso/identified-organization/dod/internet/private/enterprise/fs/switch/switch/switchMib/fsMgmt/fsPingMIB/fsPingMIBObjects/fsPingTable/fsPingEntry
  • /iso/identified-organization/dod/internet/private/enterprise/fs/switch/system/switchMib/fsMgmt/fsPingMIB/fsPingMIBObjects/fsPingTable/fsPingEntry
  • /iso/identified-organization/dod/internet/private/enterprise/fs/switch/D7000/switchMib/fsMgmt/fsPingMIB/fsPingMIBObjects/fsPingTable/fsPingEntry
  • /iso/identified-organization/dod/internet/private/enterprise/fs/switch/RTL8382M/switchMib/fsMgmt/fsPingMIB/fsPingMIBObjects/fsPingTable/fsPingEntry
  • /iso/identified-organization/dod/internet/private/enterprise/fs/nmsProducts/switch/switchMib/fsMgmt/fsPingMIB/fsPingMIBObjects/fsPingTable/fsPingEntry
  • /iso/identified-organization/dod/internet/private/enterprise/fs/nmsProducts/system/switchMib/fsMgmt/fsPingMIB/fsPingMIBObjects/fsPingTable/fsPingEntry
  • /iso/identified-organization/dod/internet/private/enterprise/fs/nmsProducts/D7000/switchMib/fsMgmt/fsPingMIB/fsPingMIBObjects/fsPingTable/fsPingEntry
  • /iso/identified-organization/dod/internet/private/enterprise/fs/nmsProducts/RTL8382M/switchMib/fsMgmt/fsPingMIB/fsPingMIBObjects/fsPingTable/fsPingEntry
  • /iso/identified-organization/dod/internet/private/enterprise/fs/fsProducts/switch/switchMib/fsMgmt/fsPingMIB/fsPingMIBObjects/fsPingTable/fsPingEntry
  • /iso/identified-organization/dod/internet/private/enterprise/fs/fsProducts/system/switchMib/fsMgmt/fsPingMIB/fsPingMIBObjects/fsPingTable/fsPingEntry
  • /iso/identified-organization/dod/internet/private/enterprise/fs/fsProducts/D7000/switchMib/fsMgmt/fsPingMIB/fsPingMIBObjects/fsPingTable/fsPingEntry
  • /iso/identified-organization/dod/internet/private/enterprise/fs/fsProducts/RTL8382M/switchMib/fsMgmt/fsPingMIB/fsPingMIBObjects/fsPingTable/fsPingEntry
  • Additional combinations skipped.

Descriptions

fsPingEntry — FS.COM official Documentation Hub native MIB packages, FS.COM MIB copies (LibreNMS/Observium Community)

Entry contains ping parameters and results. A management station wishing to create an entry should first generate a pseudo-random serial number to be used as the index to a ping entry. The station should then create the associated entry. We must set all specifies valid values for the non-defaulted configuration objects, certainly, it should also modify the default values for the other configuration objects if the defaults are not appropriate. Once the appropriate instance of all the configuration objects have been created or set,the row status should be set to active to initiate the request. Once the ping sequence has been activated, it cannot be stopped -- it will run until the configured number of packets have been sent. Once the sequence completes, the management station should retrieve the values of the status objects of interest, and should then delete the entry. In order to prevent old entries from clogging the table, entries will be aged out, but an entry will never be deleted within 5 minutes of completing.

Source records

fsPingEntry

Status in source: current.

Names: fsPingEntry

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "fsPingEntry",
    "OBJECT-TYPE",
    "SYNTAX",
    "FSPingEntry",
    "MAX-ACCESS",
    "not-accessible",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"Entry contains ping parameters and results. A management station wishing to create an entry should first generate a pseudo-random serial number to be used as the index to a ping entry. The station should then create the associated entry. We must set all specifies valid values for the non-defaulted configuration objects, certainly, it should also modify the default values for the other configuration objects if the defaults are not appropriate. Once the appropriate instance of all the configuration objects have been created or set,the row status should be set to active to initiate the request. Once the ping sequence has been activated, it cannot be stopped -- it will run until the configured number of packets have been sent. Once the sequence completes, the management station should retrieve the values of the status objects of interest, and should then delete the entry. In order to prevent old entries from clogging the table, entries will be aged out, but an entry will never be deleted within 5 minutes of completing.\"",
    "INDEX",
    "{",
    "fsPingIndex",
    "}",
    "::=",
    "{",
    "fsPingTable",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "row",
      "FSPingEntry"
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "Entry contains ping parameters and results. A management station wishing to create an entry should first generate a pseudo-random serial number to be used as the index to a ping entry. The station should then create the associated entry. We must set all specifies valid values for the non-defaulted configuration objects, certainly, it should also modify the default values for the other configuration objects if the defaults are not appropriate. Once the appropriate instance of all the configuration objects have been created or set,the row status should be set to active to initiate the request. Once the ping sequence has been activated, it cannot be stopped -- it will run until the configured number of packets have been sent. Once the sequence completes, the management station should retrieve the values of the status objects of interest, and should then delete the entry. In order to prevent old entries from clogging the table, entries will be aged out, but an entry will never be deleted within 5 minutes of completing."
    ],
    null,
    null,
    [
      "INDEX",
      [
        [
          0,
          "fsPingIndex"
        ]
      ]
    ],
    null
  ]
}
  • FS.COM MIB copies (LibreNMS/Observium Community) · Publisher's source file: Source package: observium-community-latest.tar.gz

    Vendor MIB copy from the Observium Community archive. FS.COM support.

    Module: FS-PING-MIB

    Published definition
    fsPingEntry OBJECT-TYPE
            SYNTAX FSPingEntry
            MAX-ACCESS not-accessible
            STATUS current
            DESCRIPTION
                    "Entry contains ping parameters and results.
                    
                    A management station wishing to create an entry should
                    first generate a pseudo-random serial number to be used
                    as the index to a ping entry.  The station should
                    then create the associated entry.
                    
                    We must set all specifies valid values for the 
                    non-defaulted configuration objects, certainly, it should
                    also modify  the default values for the other configuration 
                    objects if the defaults are not appropriate.
                                           
                    Once the appropriate instance of all the configuration
                    objects have been created or set,the row status should be set
                    to active to initiate the request.  
    
                    Once the ping sequence has been activated, it cannot be
                    stopped -- it will run until the configured number of
                    packets have been sent.
    
                    Once the sequence completes, the management station should
                    retrieve the values of the status objects of interest, and
                    should then delete the entry.  In order to prevent old
                    entries from clogging the table, entries will be aged out,
                    but an entry will never be deleted within 5 minutes of
                    completing." 
            INDEX { fsPingIndex }
            ::= { fsPingTable 1 }
    Module imports
    {'FS-TC': ['IfIndex'], 'FS-SMI': ['fsMgmt'], 'SNMPv2-TC': ['TruthValue', 'RowStatus'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'IpAddress', 'Unsigned32', 'Integer32'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP']}

    Related source files and packages:


    Source location: FS-PING-MIB::fsPingEntry.
    Source version and references

    Downloaded: 2026-10-23T19:25:17.851939+00:00.

  • FS.COM official Documentation Hub native MIB packages · Publisher's source file: Source package: 2024012909344598z6fl.zip

    Module: FS-PING-MIB

    Published definition
    fsPingEntry OBJECT-TYPE
            SYNTAX FSPingEntry
            MAX-ACCESS not-accessible
            STATUS current
            DESCRIPTION
                    "Entry contains ping parameters and results.
                    
                    A management station wishing to create an entry should
                    first generate a pseudo-random serial number to be used
                    as the index to a ping entry.  The station should
                    then create the associated entry.
                    
                    We must set all specifies valid values for the 
                    non-defaulted configuration objects, certainly, it should
                    also modify  the default values for the other configuration 
                    objects if the defaults are not appropriate.
                                           
                    Once the appropriate instance of all the configuration
                    objects have been created or set,the row status should be set
                    to active to initiate the request.  
    
                    Once the ping sequence has been activated, it cannot be
                    stopped -- it will run until the configured number of
                    packets have been sent.
    
                    Once the sequence completes, the management station should
                    retrieve the values of the status objects of interest, and
                    should then delete the entry.  In order to prevent old
                    entries from clogging the table, entries will be aged out,
                    but an entry will never be deleted within 5 minutes of
                    completing." 
            INDEX { fsPingIndex }
            ::= { fsPingTable 1 }
    Module imports
    {'FS-TC': ['IfIndex'], 'FS-SMI': ['fsMgmt'], 'SNMPv2-TC': ['TruthValue', 'RowStatus'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'IpAddress', 'Unsigned32', 'Integer32'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP']}

    Related source files and packages:

    • S3910-24TS and S3910-48TS Switches SNMP MIB Files (V1.0)S3910-24TS and S3910-48TS Switches SNMP MIB Files (V1.0); Models: S3910-24TS, S3910-48TS; Catalog updated: 2024-05-28 19:39:45; File: mall/doc/2024012909344598z6fl.zip; Publisher Last-Modified: Mon, 29 Jan 2024 01:34:50 GMT; 1.5 MiB
    • S5810 Series Switches SNMP MIB Files (V1.0)S5810 Series Switches SNMP MIB Files (V1.0); Models: S5810-28FS, S5810-28TS, S5810-48FS, S5810-48TS, S5810-48TS-P; Catalog updated: 2024-05-28 19:39:45; File: mall/doc/20240129093459svlvsn.zip; Publisher Last-Modified: Mon, 29 Jan 2024 01:35:04 GMT; 1.5 MiB

    Source location: FS-PING-MIB::fsPingEntry.
    Source version and references

    Same file in 20240129093459svlvsn.zip.

    Downloaded: 2026-10-24T13:35:05.114056+00:00.

  • FS.COM official Documentation Hub native MIB packages · Publisher's source file: Source package: s5810-series-switches-snmp-mib-files.zip

    Module: FS-PING-MIB

    Published definition
    fsPingEntry OBJECT-TYPE
            SYNTAX FSPingEntry
            MAX-ACCESS not-accessible
            STATUS current
            DESCRIPTION
                    "Entry contains ping parameters and results.
                    
                    A management station wishing to create an entry should
                    first generate a pseudo-random serial number to be used
                    as the index to a ping entry.  The station should
                    then create the associated entry.
                    
                    We must set all specifies valid values for the 
                    non-defaulted configuration objects, certainly, it should
                    also modify  the default values for the other configuration 
                    objects if the defaults are not appropriate.
                                           
                    Once the appropriate instance of all the configuration
                    objects have been created or set,the row status should be set
                    to active to initiate the request.  
    
                    Once the ping sequence has been activated, it cannot be
                    stopped -- it will run until the configured number of
                    packets have been sent.
    
                    Once the sequence completes, the management station should
                    retrieve the values of the status objects of interest, and
                    should then delete the entry.  In order to prevent old
                    entries from clogging the table, entries will be aged out,
                    but an entry will never be deleted within 5 minutes of
                    completing." 
            INDEX { fsPingIndex }
            ::= { fsPingTable 1 }
    Module imports
    {'FS-TC': ['IfIndex'], 'FS-SMI': ['fsMgmt'], 'SNMPv2-TC': ['TruthValue', 'RowStatus'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'IpAddress', 'Unsigned32', 'Integer32'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP']}

    Related source files and packages:

    • NC8200 and NC8400 Series Switches SNMP MIB FilesNC8200 and NC8400 Series Switches SNMP MIB Files; Models: NC8200-16Q, NC8200-24BC, NC8200-4TD, NC8200-8C, NC8400-16CD, NC8400-32C, NC8400-4TH; Catalog updated: 2024-05-28 19:26:13; File: mall/file/user_manual/nc8200-and-nc8400-series-swithes-snmp-mib-files.zip; Publisher Last-Modified: Fri, 05 Aug 2022 14:34:12 GMT; 1.5 MiB
    • S5810 Series Switches SNMP MIB FilesS5810 Series Switches SNMP MIB Files; Models: S5810-28FS, S5810-48FS, S5810-48TS-P; Catalog updated: 2024-05-28 19:26:26; File: mall/file/datasheet/s5810-series-switches-snmp-mib-files.zip; Publisher Last-Modified: Fri, 05 Aug 2022 04:20:38 GMT; 2.3 MiB
    • N5860 and N8560 Series Switches SNMP MIB FilesN5860 and N8560 Series Switches SNMP MIB Files; Models: N5860-48SC, N8560-32C, N8560-48BC, N8560-64C; Catalog updated: 2024-09-12 14:10:35; File: mall/file/user_manual/n5860-and-n8560-series-swithes-snmp-mib-files.zip; Publisher Last-Modified: Fri, 05 Aug 2022 14:33:20 GMT; 1.5 MiB

    Source location: FS-PING-MIB::fsPingEntry.
    Source version and references

    Same file in nc8200-and-nc8400-series-swithes-snmp-mib-files.zip.

    Same file in n5860-and-n8560-series-swithes-snmp-mib-files.zip.

    Downloaded: 2026-10-24T13:35:06.534038+00:00.

  • FS.COM official Documentation Hub native MIB packages · Publisher's source file: Source package: s3410-series-swithes-snmp-mib-files.zip

    Module: FS-PING-MIB

    Published definition
    fsPingEntry OBJECT-TYPE
            SYNTAX FSPingEntry
            MAX-ACCESS not-accessible
            STATUS current
            DESCRIPTION
                    "Entry contains ping parameters and results.
                    
                    A management station wishing to create an entry should
                    first generate a pseudo-random serial number to be used
                    as the index to a ping entry.  The station should
                    then create the associated entry.
                    
                    We must set all specifies valid values for the 
                    non-defaulted configuration objects, certainly, it should
                    also modify  the default values for the other configuration 
                    objects if the defaults are not appropriate.
                                           
                    Once the appropriate instance of all the configuration
                    objects have been created or set,the row status should be set
                    to active to initiate the request.  
    
                    Once the ping sequence has been activated, it cannot be
                    stopped -- it will run until the configured number of
                    packets have been sent.
    
                    Once the sequence completes, the management station should
                    retrieve the values of the status objects of interest, and
                    should then delete the entry.  In order to prevent old
                    entries from clogging the table, entries will be aged out,
                    but an entry will never be deleted within 5 minutes of
                    completing." 
            INDEX { fsPingIndex }
            ::= { fsPingTable 1 }
    Module imports
    {'FS-TC': ['IfIndex'], 'FS-SMI': ['fsMgmt'], 'SNMPv2-TC': ['TruthValue', 'RowStatus'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'IpAddress', 'Unsigned32', 'Integer32'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP']}

    Related source files and packages:

    • S3100-16TF Switch SNMP MIB FilesS3100-16TF Switch SNMP MIB Files; Models: S3100-16TF; Catalog updated: 2026-10-08 14:09:01; File: mall/resource/s3100-16tf-switch-snmp-mib-files.zip; Publisher Last-Modified: Thu, 08 Oct 2026 06:09:01 GMT; 2.4 MiB
    • S3910 Series Swithes SNMP MIB FilesS3910 Series Swithes SNMP MIB Files; Models: S3910-24TS, S3910-48TS; Catalog updated: 2024-05-28 19:26:04; File: mall/file/user_manual/s3910-series-swithes-snmp-mib-files.zip; Publisher Last-Modified: Fri, 05 Aug 2022 14:37:14 GMT; 2.4 MiB
    • S5860 Series Swithes SNMP MIB FilesS5860 Series Swithes SNMP MIB Files; Models: S5860-20SQ, S5860-24XB-U, S5860-48SC; Catalog updated: 2026-02-22 10:42:59; File: mall/file/user_manual/s5860-series-swithes-snmp-mib-files.zip; Publisher Last-Modified: Fri, 05 Aug 2022 14:40:34 GMT; 2.4 MiB
    Show all 4 related files and packages
    • S3410 Series Swithes SNMP MIB FilesS3410 Series Swithes SNMP MIB Files; Models: S3410-24TS-P; Catalog updated: 2024-05-28 19:26:04; File: mall/file/user_manual/s3410-series-swithes-snmp-mib-files.zip; Publisher Last-Modified: Fri, 05 Aug 2022 14:36:20 GMT; 2.4 MiB

    Source location: FS-PING-MIB::fsPingEntry.
    Source version and references

    Same file in s3100-16tf-switch-snmp-mib-files.zip.

    Same file in s5860-series-swithes-snmp-mib-files.zip.

    Same file in s3910-series-swithes-snmp-mib-files.zip.

    Downloaded: 2026-10-24T13:35:09.286003+00:00.

Current Registration Authority (inferred from ancestor 1.3.6.1.4.1.52642)

FS.COM INC

Direct children (14)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.52642.1.1.10.2.3.1.1.1.1 fsPingIndex00
1.3.6.1.4.1.52642.1.1.10.2.3.1.1.1.2 fsPingAddress00
1.3.6.1.4.1.52642.1.1.10.2.3.1.1.1.3 fsPingDataLength00
1.3.6.1.4.1.52642.1.1.10.2.3.1.1.1.4 fsPingTimes00
1.3.6.1.4.1.52642.1.1.10.2.3.1.1.1.5 fsPingTimeOuts00
1.3.6.1.4.1.52642.1.1.10.2.3.1.1.1.6 fsPingReturns00
1.3.6.1.4.1.52642.1.1.10.2.3.1.1.1.7 fsPingMaxTime00
1.3.6.1.4.1.52642.1.1.10.2.3.1.1.1.8 fsPingAvTime00
1.3.6.1.4.1.52642.1.1.10.2.3.1.1.1.9 fsPingMinTime00
1.3.6.1.4.1.52642.1.1.10.2.3.1.1.1.10 fsPingCompleted00
1.3.6.1.4.1.52642.1.1.10.2.3.1.1.1.11 fsPingEntryStauts00
1.3.6.1.4.1.52642.1.1.10.2.3.1.1.1.12 fsPingSourceIp00
1.3.6.1.4.1.52642.1.1.10.2.3.1.1.1.13 fsPingSourceInterfaceIndex00
1.3.6.1.4.1.52642.1.1.10.2.3.1.1.1.14 fsPingTypeOfService00