You must design an OTV implementation that supports packets fragmentation. Which option do you use?

An adjacency server in OTV tracks overlay membership and reachability, but it does not directly enable or manage packet fragmentation support.

OTV headers are designed to allow the core to hash traffic for load balancing, which is unrelated to supporting packet fragmentation.

Cisco ASR 1000 Series Aggregation Services Routers running Advanced IP Services (or equivalent IP services feature set) are capable of handling OTV operations, including the reassembly and fragmentation of IP packets. This capability is crucial when OTV needs to transport fragmented IP packets without issues across varying MTUs in the core network.

Setting an MTU of 9216 bytes on join interfaces configures jumbo frames to avoid fragmentation for larger packets, but it does not inherently enable support for reassembling already fragmented packets from the overlay.