Higher payload data causing packet drop over PPPOE in SVR connection 

Intermittent packet drop

session establishment issue with higher payload data application

++ With the application which exceeds the Maximum transfer unit set on interface alone , we might see the drop in the packet as the first SVR packet carries extra metadata for session setup.

++ Therefore it is recommended to enable PMTUD in the SVR path to determine when/whether fragmentation is necessary.

To enable the PMTUD 

From GUI 

1.

Only enable it under network-interface -> pppoe -> neighborhood <neighborhood-name> on both the adjancencies router. 

2.

From conductor CLI

config authority router <router-name> node <node-name> device-interface <device-interface-name> network-interface <network-interface-name> neighbourhood <neighbourhood-name> path-mtu-discovery enabled  true

++ Once the PMTUD is enabled, please check "show peers details" to check the path MTU discoverved.

e.g.

# show peers detail

================== ==================== =================== ================= ======== ============= ============= ============== ============= ========== ====== ===============

 Peer         Node         Network Interface  Destination    Status  Hostname   Path MTU   Latency (ms)  Jitter (ms)  Loss (%)  MOS  Uptime

================== ==================== =================== ================= ======== ============= ============= ============== ============= ========== ====== ===============

 128t-ro1-hub  128t-br1   pppoe         2.2.2.2   up     unavailable  1476        46        0      0   4.38  6h 15m 39s

++ From the above output the Path MTU is determined between the PPPOE neighbour. This should alleviate the unnecessary fragment/reassembly in the network and therefore the traffic/session would not drop due to extra packet length