82873c24ce
Why I did it SONiC currently does not identify 'EdgeZoneAggregator' neighbor. As a result, the buffer profile attached to those interfaces uses the default cable length which could cause ingress packet drops due to insufficient headroom. Hence, there is a need to update the buffer templates to identify such neighbors and assign the same cable length as used by the T1. How I did it Modified the buffer template to identify EdgeZoneAggregator as a neighbor device type and assign it the same cable length as a T1/leaf router. How to verify it Unit tests pass, and manually checked on a 7260 to see the changes take effect. |
||
|---|---|---|
| .. | ||
| per_namespace | ||
| share_image | ||
| arp_update_vars.j2 | ||
| backend_acl.j2 | ||
| buffers_config.j2 | ||
| cbf_config.j2 | ||
| config-chassisdb.service.j2 | ||
| config-setup.service.j2 | ||
| database.service.j2 | ||
| dhcp_relay.service.j2 | ||
| docker_image_ctl.j2 | ||
| iccpd.service.j2 | ||
| init_cfg.json.j2 | ||
| kube_cni.10-flannel.conflist | ||
| lldp.service.j2 | ||
| lldp.timer.j2 | ||
| manifest.json.j2 | ||
| mgmt-framework.service.j2 | ||
| mgmt-framework.timer | ||
| mux.service.j2 | ||
| nat.service.j2 | ||
| organization_extensions.sh | ||
| p4rt.service.j2 | ||
| packages.json.j2 | ||
| pde.service.j2 | ||
| pmon.service.j2 | ||
| pmon.timer | ||
| qos_config.j2 | ||
| radv.service.j2 | ||
| restapi.service.j2 | ||
| sflow.service.j2 | ||
| snmp.service.j2 | ||
| snmp.timer | ||
| sonic_debian_extension.j2 | ||
| sonic_version.yml.j2 | ||
| sonic-delayed.target | ||
| sonic.target | ||
| swss_vars.j2 | ||
| tacacs-config.service | ||
| tacacs-config.timer | ||
| telemetry.service.j2 | ||
| telemetry.timer | ||
| updategraph.service.j2 | ||