OID reference

vtssLldpConfigMedGlobalFastRepeatCount

1.3.6.1.4.1.52642.9.34.1.2.3.4.1

Description

Number of times to repeat LLDP frame transmission at fast start Rapid startup and Emergency Call Service Location Identification Discovery of endpoints is a critically important aspect of VoIP systems in general. In addition, it is best to advertise only those pieces of information which are specifically relevant to p…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.52642.9.34.1.2.3.4 (vtssLldpConfigMedGlobal)
Node code
1
Node name
vtssLldpConfigMedGlobalFastRepeatCount
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.52642.9.34.1.2.3.4.1
URN notation
urn:oid:1.3.6.1.4.1.52642.9.34.1.2.3.4.1
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 52642 9 34 1 2 3 4 1}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) fs(52642) nmsMgmt(9) vtssLldpMib(34) vtssLldpMibObjects(1) vtssLldpConfig(2) vtssLldpConfigMed(3) vtssLldpConfigMedGlobal(4) vtssLldpConfigMedGlobalFastRepeatCount(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) fs(52642) vtssSwitchMgmt(9) vtssLldpMib(34) vtssLldpMibObjects(1) vtssLldpConfig(2) vtssLldpConfigMed(3) vtssLldpConfigMedGlobal(4) vtssLldpConfigMedGlobalFastRepeatCount(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) fs(52642) fsSurveillanceMIB(9) vtssLldpMib(34) vtssLldpMibObjects(1) vtssLldpConfig(2) vtssLldpConfigMed(3) vtssLldpConfigMedGlobal(4) vtssLldpConfigMedGlobalFastRepeatCount(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nms(52642) nmsMgmt(9) vtssLldpMib(34) vtssLldpMibObjects(1) vtssLldpConfig(2) vtssLldpConfigMed(3) vtssLldpConfigMedGlobal(4) vtssLldpConfigMedGlobalFastRepeatCount(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nms(52642) vtssSwitchMgmt(9) vtssLldpMib(34) vtssLldpMibObjects(1) vtssLldpConfig(2) vtssLldpConfigMed(3) vtssLldpConfigMedGlobal(4) vtssLldpConfigMedGlobalFastRepeatCount(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nms(52642) fsSurveillanceMIB(9) vtssLldpMib(34) vtssLldpMibObjects(1) vtssLldpConfig(2) vtssLldpConfigMed(3) vtssLldpConfigMedGlobal(4) vtssLldpConfigMedGlobalFastRepeatCount(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) fiberstore(52642) nmsMgmt(9) vtssLldpMib(34) vtssLldpMibObjects(1) vtssLldpConfig(2) vtssLldpConfigMed(3) vtssLldpConfigMedGlobal(4) vtssLldpConfigMedGlobalFastRepeatCount(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) fiberstore(52642) vtssSwitchMgmt(9) vtssLldpMib(34) vtssLldpMibObjects(1) vtssLldpConfig(2) vtssLldpConfigMed(3) vtssLldpConfigMedGlobal(4) vtssLldpConfigMedGlobalFastRepeatCount(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) fiberstore(52642) fsSurveillanceMIB(9) vtssLldpMib(34) vtssLldpMibObjects(1) vtssLldpConfig(2) vtssLldpConfigMed(3) vtssLldpConfigMedGlobal(4) vtssLldpConfigMedGlobalFastRepeatCount(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) vtss(52642) nmsMgmt(9) vtssLldpMib(34) vtssLldpMibObjects(1) vtssLldpConfig(2) vtssLldpConfigMed(3) vtssLldpConfigMedGlobal(4) vtssLldpConfigMedGlobalFastRepeatCount(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) vtss(52642) vtssSwitchMgmt(9) vtssLldpMib(34) vtssLldpMibObjects(1) vtssLldpConfig(2) vtssLldpConfigMed(3) vtssLldpConfigMedGlobal(4) vtssLldpConfigMedGlobalFastRepeatCount(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) vtss(52642) fsSurveillanceMIB(9) vtssLldpMib(34) vtssLldpMibObjects(1) vtssLldpConfig(2) vtssLldpConfigMed(3) vtssLldpConfigMedGlobal(4) vtssLldpConfigMedGlobalFastRepeatCount(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) userNet(52642) nmsMgmt(9) vtssLldpMib(34) vtssLldpMibObjects(1) vtssLldpConfig(2) vtssLldpConfigMed(3) vtssLldpConfigMedGlobal(4) vtssLldpConfigMedGlobalFastRepeatCount(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) userNet(52642) vtssSwitchMgmt(9) vtssLldpMib(34) vtssLldpMibObjects(1) vtssLldpConfig(2) vtssLldpConfigMed(3) vtssLldpConfigMedGlobal(4) vtssLldpConfigMedGlobalFastRepeatCount(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) userNet(52642) fsSurveillanceMIB(9) vtssLldpMib(34) vtssLldpMibObjects(1) vtssLldpConfig(2) vtssLldpConfigMed(3) vtssLldpConfigMedGlobal(4) vtssLldpConfigMedGlobalFastRepeatCount(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) fs(52642) nmsMgmt(9) vtssLldpMib(34) vtssLldpMibObjects(1) vtssLldpConfig(2) vtssLldpConfigMed(3) vtssLldpConfigMedGlobal(4) vtssLldpConfigMedGlobalFastRepeatCount(1)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/52642/9/34/1/2/3/4/1
  • /ISO/Identified-Organization/6/1/4/1/52642/9/34/1/2/3/4/1
  • /ISO/3/6/1/4/1/52642/9/34/1/2/3/4/1
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/fs/nmsMgmt/vtssLldpMib/vtssLldpMibObjects/vtssLldpConfig/vtssLldpConfigMed/vtssLldpConfigMedGlobal/vtssLldpConfigMedGlobalFastRepeatCount
  • /iso/identified-organization/dod/internet/private/enterprise/fs/vtssSwitchMgmt/vtssLldpMib/vtssLldpMibObjects/vtssLldpConfig/vtssLldpConfigMed/vtssLldpConfigMedGlobal/vtssLldpConfigMedGlobalFastRepeatCount
  • /iso/identified-organization/dod/internet/private/enterprise/fs/fsSurveillanceMIB/vtssLldpMib/vtssLldpMibObjects/vtssLldpConfig/vtssLldpConfigMed/vtssLldpConfigMedGlobal/vtssLldpConfigMedGlobalFastRepeatCount
  • /iso/identified-organization/dod/internet/private/enterprise/nms/nmsMgmt/vtssLldpMib/vtssLldpMibObjects/vtssLldpConfig/vtssLldpConfigMed/vtssLldpConfigMedGlobal/vtssLldpConfigMedGlobalFastRepeatCount
  • /iso/identified-organization/dod/internet/private/enterprise/nms/vtssSwitchMgmt/vtssLldpMib/vtssLldpMibObjects/vtssLldpConfig/vtssLldpConfigMed/vtssLldpConfigMedGlobal/vtssLldpConfigMedGlobalFastRepeatCount
  • /iso/identified-organization/dod/internet/private/enterprise/nms/fsSurveillanceMIB/vtssLldpMib/vtssLldpMibObjects/vtssLldpConfig/vtssLldpConfigMed/vtssLldpConfigMedGlobal/vtssLldpConfigMedGlobalFastRepeatCount
  • /iso/identified-organization/dod/internet/private/enterprise/fiberstore/nmsMgmt/vtssLldpMib/vtssLldpMibObjects/vtssLldpConfig/vtssLldpConfigMed/vtssLldpConfigMedGlobal/vtssLldpConfigMedGlobalFastRepeatCount
  • /iso/identified-organization/dod/internet/private/enterprise/fiberstore/vtssSwitchMgmt/vtssLldpMib/vtssLldpMibObjects/vtssLldpConfig/vtssLldpConfigMed/vtssLldpConfigMedGlobal/vtssLldpConfigMedGlobalFastRepeatCount
  • /iso/identified-organization/dod/internet/private/enterprise/fiberstore/fsSurveillanceMIB/vtssLldpMib/vtssLldpMibObjects/vtssLldpConfig/vtssLldpConfigMed/vtssLldpConfigMedGlobal/vtssLldpConfigMedGlobalFastRepeatCount
  • /iso/identified-organization/dod/internet/private/enterprise/FS/nmsMgmt/vtssLldpMib/vtssLldpMibObjects/vtssLldpConfig/vtssLldpConfigMed/vtssLldpConfigMedGlobal/vtssLldpConfigMedGlobalFastRepeatCount
  • /iso/identified-organization/dod/internet/private/enterprise/FS/vtssSwitchMgmt/vtssLldpMib/vtssLldpMibObjects/vtssLldpConfig/vtssLldpConfigMed/vtssLldpConfigMedGlobal/vtssLldpConfigMedGlobalFastRepeatCount
  • /iso/identified-organization/dod/internet/private/enterprise/FS/fsSurveillanceMIB/vtssLldpMib/vtssLldpMibObjects/vtssLldpConfig/vtssLldpConfigMed/vtssLldpConfigMedGlobal/vtssLldpConfigMedGlobalFastRepeatCount
  • /iso/identified-organization/dod/internet/private/enterprise/vtss/nmsMgmt/vtssLldpMib/vtssLldpMibObjects/vtssLldpConfig/vtssLldpConfigMed/vtssLldpConfigMedGlobal/vtssLldpConfigMedGlobalFastRepeatCount
  • /iso/identified-organization/dod/internet/private/enterprise/vtss/vtssSwitchMgmt/vtssLldpMib/vtssLldpMibObjects/vtssLldpConfig/vtssLldpConfigMed/vtssLldpConfigMedGlobal/vtssLldpConfigMedGlobalFastRepeatCount
  • /iso/identified-organization/dod/internet/private/enterprise/vtss/fsSurveillanceMIB/vtssLldpMib/vtssLldpMibObjects/vtssLldpConfig/vtssLldpConfigMed/vtssLldpConfigMedGlobal/vtssLldpConfigMedGlobalFastRepeatCount
  • /iso/identified-organization/dod/internet/private/enterprise/S3200/nmsMgmt/vtssLldpMib/vtssLldpMibObjects/vtssLldpConfig/vtssLldpConfigMed/vtssLldpConfigMedGlobal/vtssLldpConfigMedGlobalFastRepeatCount
  • Additional combinations skipped.

SNMP properties

Value type
VTSSUnsigned8
Maximum access defined by MIB
read-write
Status in MIB
current
Allowed ranges
1–10

Using this OID with SNMP

At least one MIB declaration places this object in a scalar group. A scalar instance uses the suffix .0.

snmpget [connection options] DEVICE .1.3.6.1.4.1.52642.9.34.1.2.3.4.1.0

Replace the placeholders with your connection and authentication options. Available permissions and device support can differ from the MIB.

Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.

Product context

Documented MIB packages

The FS.COM catalogue lists MIB packages containing this definition for these models:

IES3110-8TFP-R.

A definition in a model's MIB package does not establish that the device implements it or permits access.

The displayed source records contain one distinct definition. Compare its source records.

vtssLldpConfigMedGlobalFastRepeatCount OBJECT-TYPE
    SYNTAX      VTSSUnsigned8 (1..10)
    MAX-ACCESS  read-write
    STATUS      current
    DESCRIPTION
        "Number of times to repeat LLDP frame transmission at fast start
         
         Rapid startup and Emergency Call Service Location Identification
         Discovery of endpoints is a critically important aspect of VoIP systems
         in general. In addition, it is best to advertise only those pieces of
         information which are specifically relevant to particular endpoint
         types (for example only advertise the voice network policy to permitted
         voice-capable devices), both in order to conserve the limited LLDPU
         space and to reduce security and system integrity issues that can come
         with inappropriate knowledge of the network policy.
         
         With this in mind LLDP-MED defines an LLDP-MED Fast Start interaction
         between the protocol and the application layers on top of the protocol,
         in order to achieve these related properties. Initially, a Network
         Connectivity Device will only transmit LLDP TLVs in an LLDPDU. Only
         after an LLDP-MED Endpoint Device is detected, will an LLDP-MED capable
         Network Connectivity Device start to advertise LLDP-MED TLVs in
         outgoing LLDPDUs on the associated port. The LLDP-MED application will
         temporarily speed up the transmission of the LLDPDU to start within a
         second, when a new LLDP-MED neighbor has been detected in order share
         LLDP-MED information as fast as possible to new neighbors.
         
         Because there is a risk of an LLDP frame being lost during transmission
         between neighbors, it is recommended to repeat the fast start
         transmission multiple times to increase the possibility of the
         neighbors receiving the LLDP frame. With fast start repeat count it is
         possible to specify the number of times the fast start transmission
         would be repeated. The recommended value is 4 times, given that 4 LLDP
         frames with a 1 second interval will be transmitted, when an LLDP frame
         with new information is received.
         
         It should be noted that LLDP-MED and the LLDP-MED Fast Start mechanism
         is only intended to run on links between LLDP-MED Network Connectivity
         Devices and Endpoint Devices, and as such does not apply to links
         between LAN infrastructure elements, including Network Connectivity
         Devices, or other types of links."
    ::= { vtssLldpConfigMedGlobal 1 }

Meaning

Descriptions

1 unique

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

Number of times to repeat LLDP frame transmission at fast start Rapid startup and Emergency Call Service Location Identification Discovery of endpoints is a critically important aspect of VoIP systems in general. In addition, it is best to advertise only those pieces of information which are specifically relevant to particular endpoint types (for example only advertise the voice network policy to permitted voice-capable devices), both in order to conserve the limited LLDPU space and to reduce security and system integrity issues that can come with inappropriate knowledge of the network policy. With this in mind LLDP-MED defines an LLDP-MED Fast Start interaction between the protocol and the application layers on top of the protocol, in order to achieve these related properties. Initially, a Network Connectivity Device will only transmit LLDP TLVs in an LLDPDU. Only after an LLDP-MED Endpoint Device is detected, will an LLDP-MED capable Network Connectivity Device start to advertise LLDP-MED TLVs in outgoing LLDPDUs on the associated port. The LLDP-MED application will temporarily speed up the transmission of the LLDPDU to start within a second, when a new LLDP-MED neighbor has been detected in order share LLDP-MED information as fast as possible to new neighbors. Because there is a risk of an LLDP frame being lost during transmission between neighbors, it is recommended to repeat the fast start transmission multiple times to increase the possibility of the neighbors receiving the LLDP frame. With fast start repeat count it is possible to specify the number of times the fast start transmission would be repeated. The recommended value is 4 times, given that 4 LLDP frames with a 1 second interval will be transmitted, when an LLDP frame with new information is received. It should be noted that LLDP-MED and the LLDP-MED Fast Start mechanism is only intended to run on links between LLDP-MED Network Connectivity Devices and Endpoint Devices, and as such does not apply to links between LAN infrastructure elements, including Network Connectivity Devices, or other types of links.

Sources for this description

FS.COM official Documentation Hub native MIB packages

See 1 matching source record

Evidence

Source records

1 records

Matching descriptions are grouped; open a group to compare definitions and supporting files.

Records for description 1FS.COM official Documentation Hub native MIB packages1 record · 1 source

Description 1

vtssLldpConfigMedGlobalFastRepeatCount · currentFS.COM official Documentation Hub native MIB packages1 source

Status in source: current.

Names: vtssLldpConfigMedGlobalFastRepeatCount

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "vtssLldpConfigMedGlobalFastRepeatCount",
    "OBJECT-TYPE",
    "SYNTAX",
    "VTSSUnsigned8",
    "(",
    "1",
    ".",
    ".",
    "10",
    ")",
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"Number of times to repeat LLDP frame transmission at fast start Rapid startup and Emergency Call Service Location Identification Discovery of endpoints is a critically important aspect of VoIP systems in general. In addition, it is best to advertise only those pieces of information which are specifically relevant to particular endpoint types (for example only advertise the voice network policy to permitted voice-capable devices), both in order to conserve the limited LLDPU space and to reduce security and system integrity issues that can come with inappropriate knowledge of the network policy. With this in mind LLDP-MED defines an LLDP-MED Fast Start interaction between the protocol and the application layers on top of the protocol, in order to achieve these related properties. Initially, a Network Connectivity Device will only transmit LLDP TLVs in an LLDPDU. Only after an LLDP-MED Endpoint Device is detected, will an LLDP-MED capable Network Connectivity Device start to advertise LLDP-MED TLVs in outgoing LLDPDUs on the associated port. The LLDP-MED application will temporarily speed up the transmission of the LLDPDU to start within a second, when a new LLDP-MED neighbor has been detected in order share LLDP-MED information as fast as possible to new neighbors. Because there is a risk of an LLDP frame being lost during transmission between neighbors, it is recommended to repeat the fast start transmission multiple times to increase the possibility of the neighbors receiving the LLDP frame. With fast start repeat count it is possible to specify the number of times the fast start transmission would be repeated. The recommended value is 4 times, given that 4 LLDP frames with a 1 second interval will be transmitted, when an LLDP frame with new information is received. It should be noted that LLDP-MED and the LLDP-MED Fast Start mechanism is only intended to run on links between LLDP-MED Network Connectivity Devices and Endpoint Devices, and as such does not apply to links between LAN infrastructure elements, including Network Connectivity Devices, or other types of links.\"",
    "::=",
    "{",
    "vtssLldpConfigMedGlobal",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "VTSSUnsigned8",
      [
        "integerSubType",
        [
          [
            1,
            10
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "Number of times to repeat LLDP frame transmission at fast start Rapid startup and Emergency Call Service Location Identification Discovery of endpoints is a critically important aspect of VoIP systems in general. In addition, it is best to advertise only those pieces of information which are specifically relevant to particular endpoint types (for example only advertise the voice network policy to permitted voice-capable devices), both in order to conserve the limited LLDPU space and to reduce security and system integrity issues that can come with inappropriate knowledge of the network policy. With this in mind LLDP-MED defines an LLDP-MED Fast Start interaction between the protocol and the application layers on top of the protocol, in order to achieve these related properties. Initially, a Network Connectivity Device will only transmit LLDP TLVs in an LLDPDU. Only after an LLDP-MED Endpoint Device is detected, will an LLDP-MED capable Network Connectivity Device start to advertise LLDP-MED TLVs in outgoing LLDPDUs on the associated port. The LLDP-MED application will temporarily speed up the transmission of the LLDPDU to start within a second, when a new LLDP-MED neighbor has been detected in order share LLDP-MED information as fast as possible to new neighbors. Because there is a risk of an LLDP frame being lost during transmission between neighbors, it is recommended to repeat the fast start transmission multiple times to increase the possibility of the neighbors receiving the LLDP frame. With fast start repeat count it is possible to specify the number of times the fast start transmission would be repeated. The recommended value is 4 times, given that 4 LLDP frames with a 1 second interval will be transmitted, when an LLDP frame with new information is received. It should be noted that LLDP-MED and the LLDP-MED Fast Start mechanism is only intended to run on links between LLDP-MED Network Connectivity Devices and Endpoint Devices, and as such does not apply to links between LAN infrastructure elements, including Network Connectivity Devices, or other types of links."
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

Current Registration Authority (inferred from ancestor 1.3.6.1.4.1.52642)

FS.COM INC

Siblings (7)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.52642.9.34.1.2.3.4.2 vtssLldpConfigMedGlobalLatitude00
1.3.6.1.4.1.52642.9.34.1.2.3.4.3 vtssLldpConfigMedGlobalLongitude00
1.3.6.1.4.1.52642.9.34.1.2.3.4.4 vtssLldpConfigMedGlobalAltitudeType00
1.3.6.1.4.1.52642.9.34.1.2.3.4.5 vtssLldpConfigMedGlobalAltitude00
1.3.6.1.4.1.52642.9.34.1.2.3.4.6 vtssLldpConfigMedGlobalElinAddr00
1.3.6.1.4.1.52642.9.34.1.2.3.4.7 vtssLldpConfigMedGlobalDatum00
1.3.6.1.4.1.52642.9.34.1.2.3.4.8 vtssLldpConfigMedGlobalCountryCode00