me1200LldpmedConfigGlobalFastRepeatCount

ME1200-LLDPMED-MIB · .1.3.6.1.4.1.9.9.815.1.71.1.2.1.1
MIB view Table view

Object

scalar r/w Unsigned32 
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.

Context

MIB
ME1200-LLDPMED-MIB
OID
.1.3.6.1.4.1.9.9.815.1.71.1.2.1.1
Type
scalar
Access
readwrite
Status
current
Parent
me1200LldpmedConfigGlobal
Siblings
6

Syntax

Unsigned32

Values & Constraints

Object Constraints
range: 1-10

Related Objects

Sibling Objects
ObjectTypeSyntaxOID
me1200LldpmedConfigGlobalLatitude
Latitude degrees in 2s-complement as specified in RFC 3825. Positive numbers are north of the equator and negative numbers are south of the equator.
scalarME1200-TCME1200Integer64.1.3.6.1.4.1.9.9.815.1.71.1.2.1.2
me1200LldpmedConfigGlobalLongitude
Longitude degrees in 2s-complement as specified in RFC 3825. Positive values are East of the prime meridian and negative numbers are West of the prime meridian.
scalarME1200-TCME1200Integer64.1.3.6.1.4.1.9.9.815.1.71.1.2.1.3
me1200LldpmedConfigGlobalAltitudeType
Setting altitude type Possible to select between two altitude types (floors or meters). Meters are representing meters of altitude defined by the vertical datum specifi…
scalarME1200lldpmedAltitudeType.1.3.6.1.4.1.9.9.815.1.71.1.2.1.4
me1200LldpmedConfigGlobalAltitude
Altitude value in 2s-complement as specified in RFC 3825
scalarSNMPv2-SMIInteger32.1.3.6.1.4.1.9.9.815.1.71.1.2.1.5
me1200LldpmedConfigGlobalElinAddr
Emergency Call Service ELIN identifier data format is defined to carry the ELIN identifier as used during emergency call setup to a traditional CAMA or ISDN trunk-based PSAP. This…
scalarOctetString.1.3.6.1.4.1.9.9.815.1.71.1.2.1.6
me1200LldpmedConfigGlobalDatum
Setting datum to configure the datum (geodetic system) to use. The Map Datum is used for the coordinates given in these options: WGS84: (Geographical 3D) - W…
scalarME1200lldpmedDatumType.1.3.6.1.4.1.9.9.815.1.71.1.2.1.7