Recent changes to fix MTU to use the max device supported value causes the SSR to set MTU to 9K. However since NetVSC does not support Scatter RX, it fails to bind because the SSR uses packet buffers of size 2K, and cannot span multiple mbufs.
Issue ID: I95-54541
Last Updated: 2024-04-25
Introduced in SSR Version: 6.1.5
Problem
NetVSC does not support Scatter RX, so with new change to use 9K max RX, it is unable to span multipe 2K packet buffers. When matched with MLX in accelerated networking, the MLX device fails to initialize. During device configuration, user specified MTU exceeding 2K will cause init failure for that device interface.
Limit the MTU (also max RX size in DPDK) of NetVSC devices to SSR packet buffer size.
Release Notes
Fixes an issue where device-interfaces configured in Azure VM would fail during initialization and port remains operationally down.
Severity
Details
The potential impact of a software defect if encountered. Severity levels are:
- Critical: Could severely affect service, capacity/traffic, and maintenance capabilities. May have a prolonged impact to the entire system.
- Major: Could seriously affect system operation, maintenance, administration and related tasks.
- Minor: Would not significantly impair the functioning or affect service.
Major
Status
Closed
Resolved In
Product
Azure SSR AMI
Functional Area
Interface Binding
Workaround
Details
Juniper may provide a method to temporarily circumvent a problem; workarounds do not exist for all issues.
Disabling the accelerated networking to allow the device to be bound via PCLI address instead of vmbus-id