7210 SAS-MXP, R6, R12, S, SX, T BASIC SYSTEM
CONFIGURATION GUIDE RELEASE 22.9.R1
System management
Each LLDPDU contains four mandatory TLVs and optional TLVs selected by the Network Management.
The following is the format of an LLDPDU:
• Chassis ID TLV
• Port ID TLV
• Time To Live (TTL) TLV
• zero or more optional TLVs, depending on the maximum size of the LLDPDU allowed
• End of LLDPDU TLV
A concatenated string formed by the Chassis ID TLV and the Port ID TLV is used by a recipient to identify
an LLDP port or agent. The combination of the Port ID and Chassis ID TLVs remains unchanged until the
port or agent is operational.
The TTL field of a Time-To-Live TLV can be a zero or non-zero value. A zero TTL field value notifies the
receiving LLDP agent to immediately discard all information related to sending LLDP agent. A non-zero
TTL field value indicates the time duration for which the receiving LLDP agent should retain the information
of the sending LLDP agent. The receiving LLDP agent discards all information related to the sending LLDP
agent after the time interval indicated in the TTL field is complete.
Note:
A TTL zero value is used to signal that the sending LLDP port has initiated a port shutdown
procedure.
The End Of LLDPDU TLV indicates the end of the LLDPDU.
The following information is included in the protocol as defined by the IEEE 802.1ab standard:
• Connectivity and management information about the local station to adjacent stations on the same IEEE
802 LAN is advertised.
• Network management information from adjacent stations on the same IEEE 802 LAN is received.
• It operates with all IEEE 802 access protocols and network media.
• Network management information schema and object definitions suitable for storing connection
information about adjacent stations is established.
• It supports compatibility with a number of MIBs.
6.8 System resource allocation
This section describes system resource allocation including the allocation of TCAM resources,
configuration guidelines and examples.
6.8.1 Allocation of ingress internal TCAM resources
In previous releases, the system statically allocated ingress TCAM resources for use by SAP ingress QoS
classification, SAP ingress access control list (ACLs), identifying and sending CFM OAM packets to CPU
for local processing, and so on. The resource allocation is not user-configurable. With the introduction of
new capabilities including IPv6 classification, UP MEP support, and G8032-fast-flood, the static allocation
of resources by software does not meet requirements of customers who typically want to use different
features.
3HE 18197 AAAB TQZZA
© 2022 Nokia.
Use subject to Terms available at: www.nokia.com/terms/.
287
SPACER TEXT
To Next Page
Loading...