LLDP Tunneling for Epipe Service
Page 42 7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide
Note that a TTL value of zero can be used, for example, to signal that the sending port has initiated
a port shutdown procedure. The End Of LLDPDU TLV marks the end of the LLDPDU.
The implementation defaults to setting the port-id field in the LLDP OAMPDU to tx-local. This
encodes the port-id field as ifIndex (sub-type 7) of the associated port. This is required to support
some releases of SAM. SAM may use the ifIndex value to properly build the Layer Two Topology
Network Map. However, this numerical value is difficult to interpret or readily identify the LLDP
peer when reading the CLI or MIB value without SAM. Including the port-desc option as part of
the tx-tlv configuration allows an ALU remote peer supporting port-desc preferred display logic to
display the value in the port description TLV instead of the port-id field value. This does not
change the encoding of the port-id field. That value continues to represent the ifIndex. In some
environments, it may be important to select the specific port information that is carried in the port-
id field. The operator has the ability to control the encoding of the port-id information and the
associated subtype using the port-id-subtype option. Three options are supported for the port-
idsubtype:
tx-if-alias — Transmit the ifAlias String (subtype 1) that describes the port as stored in the
IFMIB, either user configured description or the default entry (ie 10/100/Gig ethernet SFP)
tx-if-name — Transmits the ifName string (subtype 5) that describes the port as stored in the
IFMIB, ifName info.
tx-local — The interface ifIndex value (subtype 7)
IPv6 (address subtype 2) and IPv4 (address subtype 1) LLDP System Management addresses are
supported.
LLDP Tunneling for Epipe Service
Customers who subscribe to Epipe service consider the Epipe as a wire, and run LLDP between
their devices which are located at each end of the Epipe. To facilitate this, the 7210 devices
support tunneling of LLDP frames that use the nearest bridge destination MAC address.
If enabled using the command tunnel-nearest-bridge-dest-mac, all frames received with the
matching LLDP destination mac address are forwarded transparently to the remote end of the
Epipe service. To forward these frames transparently, the port on which tunneling is enabled must
be configured with NULL SAP and the NULL SAP must be configured in an Epipe service.
Tunneling is not supported for any other port encapsulation or other services.
Additionally, before enabling tunneling, admin status for LLDP dest-mac nearest-bridge must be
set to disabled or Tx only, using the command admin-status available under configure> port>
ethernet> lldp> destmac-nearest-bridge. If admin-status for dest-mac nearest-bridge is set to
receive and process nearest-bridge LLDPDUs (that is, if either rx or tx-rx is set) then it overrides
the tunnel-nearest-bridge-dest-mac command.
To Next Page
Loading...
Need help?
General
