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.
Status in source: current.
Names: me1200LldpmedConfigGlobalFastRepeatCount
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"me1200LldpmedConfigGlobalFastRepeatCount",
"OBJECT-TYPE",
"SYNTAX",
"ME1200Unsigned8",
"(",
"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.\"",
"::=",
"{",
"me1200LldpmedConfigGlobal",
"1",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"ME1200Unsigned8",
[
"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
]
}- cisco-products
· Publisher's source file
· Archived source file
· Official repository archive
Source location: ME1200-LLDPMED-MIB::me1200LldpmedConfigGlobalFastRepeatCount.Source version and references
Published package: Cisco ME1200-MIBS 15.6_4_SN; file: ME1200-MIBS/15.6_4_SN/ME1200-LLDPMED-MIB.mib.
Same file in Cisco ME1200-MIBS 15.6_5_SN.
Downloaded: 2026-10-21T03:34:11.171533+00:00. SHA-256:
480c767d128aea1dbeee582e304b9cd015cbdf5d09a964c5af38c1cdecbf5865{'kind': 'OBJECT-TYPE', 'details': {'module': 'ME1200-LLDPMED-MIB', 'imports': {'ME1200-TC': ['ME1200DisplayString', 'ME1200Integer64', 'ME1200InterfaceIndex', 'ME1200RowEditorState', 'ME1200Unsigned16', 'ME1200Unsigned8'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Integer32'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP'], 'CISCOME1200-MIB': ['me1200SwitchMgmt']}, 'document': {'software': 'Cisco ME1200-MIBS', 'original_name': 'ME1200-MIBS/15.6_4_SN/ME1200-LLDPMED-MIB.mib', 'release_sha256': 'fdd5f5f181891a7352b13a73b80cbb24bb2c5ecb0d6d4fd22fc945100c43a009', 'release_version': '15.6_4_SN'}, 'smi_kind': 'OBJECT-TYPE', 'definition': 'me1200LldpmedConfigGlobalFastRepeatCount OBJECT-TYPE\n SYNTAX ME1200Unsigned8 (1..10)\n MAX-ACCESS read-write\n STATUS current\n DESCRIPTION \n "Number of times to repeat LLDP frame transmission at fast start\n \n Rapid startup and Emergency Call Service Location Identification\n Discovery of endpoints is a critically important aspect of VoIP systems\n in general. In addition, it is best to advertise only those pieces of\n information which are specifically relevant to particular endpoint\n types (for example only advertise the voice network policy to permitted\n voice-capable devices), both in order to conserve the limited LLDPU\n space and to reduce security and system integrity issues that can come\n with inappropriate knowledge of the network policy.\n \n With this in mind LLDP-MED defines an LLDP-MED Fast Start interaction\n between the protocol and the application layers on top of the protocol,\n in order to achieve these related properties. Initially, a Network\n Connectivity Device will only transmit LLDP TLVs in an LLDPDU. Only\n after an LLDP-MED Endpoint Device is detected, will an LLDP-MED capable\n Network Connectivity Device start to advertise LLDP-MED TLVs in\n outgoing LLDPDUs on the associated port. The LLDP-MED application will\n temporarily speed up the transmission of the LLDPDU to start within a\n second, when a new LLDP-MED neighbor has been detected in order share\n LLDP-MED information as fast as possible to new neighbors.\n \n Because there is a risk of an LLDP frame being lost during transmission\n between neighbors, it is recommended to repeat the fast start\n transmission multiple times to increase the possibility of the\n neighbors receiving the LLDP frame. With fast start repeat count it is\n possible to specify the number of times the fast start transmission\n would be repeated. The recommended value is 4 times, given that 4 LLDP\n frames with a 1 second interval will be transmitted, when an LLDP frame\n with new information is received.\n \n It should be noted that LLDP-MED and the LLDP-MED Fast Start mechanism\n is only intended to run on links between LLDP-MED Network Connectivity\n Devices and Endpoint Devices, and as such does not apply to links\n between LAN infrastructure elements, including Network Connectivity\n Devices, or other types of links."\n ::= { me1200LldpmedConfigGlobal 1 }', 'syntax_tree': [['SimpleSyntax', 'ME1200Unsigned8', ['integerSubType', [[1, 10]]]], None, ['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.'], None, None, None, None], 'source_encoding': 'utf-8-sig'}, 'parser_version': 'mib-4-q12'}