sonic-buildimage/device/mellanox/x86_64-mlnx_msn4700-r0/Mellanox-SN4700-A96C8V8/sai.profile

SAI_INIT_CONFIG_FILE=/usr/share/sonic/hwsku/sai_4700_8x200g_8x100g_96x25g.xml
SAI_DUMP_STORE_PATH=/var/log/mellanox/sdk-dumps
SAI_DUMP_STORE_AMOUNT=10
SAI_DUMP_MFT_CFG_PATH=/etc/sonic/mft/fwtrace_cfg
[Mellanox] [SKU] Added Mellanox-SN4700-A96C8V8 SKU (#12347) - Why I did it A new SKU for MSN4700 Platform i.e. Mellanox-SN4700-V16A96 Requirements: Breakout: Port 1-24: 4x25G(4)[10G,1G] Port 25-28: 2x100G[200G,50G,40G,25G,10G,1G] Port 29-32: 2x200G[100G,50G,40G,25G,10G,1G] Downlinks: 96 (1-24) + 4 (25-28) Uplinks: 4 (29-32) Shared Headroom: Enabled Over Subscribe Ratio: 1:4 Default Topology: T0 Default Cable Length for T1: 5m VxLAN source port range set: No Static Policy Based Hashing Supported: No Additional Details: QoS params: The default ones defined in qos_config.j2 will be applied Small Packet Percentage: Used 50% for traditional buffer model Note: For dynamic model, the value defined in LOSSLESS_TRAFFIC_PATTERN\|AZURE\|small_packet_percentage is used SKU was drafted under the assumption that the downlink ports uses xcvr's that will only support the first 4 lanes of the physical port they are connected to. Hence for the ports 1-24, the last four lanes are not used Cable Lengths used for generating buffer_defaults_{t0,t1}.j2 values Signed-off-by: Vivek Reddy Karri <vkarri@nvidia.com> 2022-10-20 01:50:07 -05:00			`SAI_INIT_CONFIG_FILE=/usr/share/sonic/hwsku/sai_4700_8x200g_8x100g_96x25g.xml`
			`SAI_DUMP_STORE_PATH=/var/log/mellanox/sdk-dumps`
			`SAI_DUMP_STORE_AMOUNT=10`
[Mellanox] Add mlxtrace to techsupport (#15961) (#16215) 2023-08-20 10:51:38 -05:00			`SAI_DUMP_MFT_CFG_PATH=/etc/sonic/mft/fwtrace_cfg`