You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Do you want to Breakout the port, continue? [y/N]: y
Running Breakout Mode : 1x100G[40G](4)
Target Breakout Mode : 4x100G
Ports to be deleted :
{
"Ethernet0": "100000"
}
Ports to be added :
{
"Ethernet0": "100000",
"Ethernet2": "100000",
"Ethernet4": "100000",
"Ethernet6": "100000"
}
After running Logic to limit the impact
Final list of ports to be deleted :
{
"Ethernet0": "100000"
}
Final list of ports to be added :
{
"Ethernet0": "100000",
"Ethernet2": "100000",
"Ethernet4": "100000",
"Ethernet6": "100000"
}
sonic_yang(6):Note: Below table(s) have no YANG models: CONSOLE_SWITCH, DHCP_SERVER, RESTAPI, SNMP, SNMP_COMMUNITY, XCVRD_LOG
Dependecies Exist. No further action will be taken
*** Printing dependecies ***
/sonic-sflow:sonic-sflow/SFLOW_SESSION/SFLOW_SESSION_LIST[port='Ethernet0']/port
Describe the results you received:
The sflow design is in conflict with port dependency.
Describe the results you expected:
Output of show version:
(paste your output here)
Output of show techsupport:
(paste your output here or download and attach the file here )
Additional information you deem important (e.g. issue happens only occasionally):
The text was updated successfully, but these errors were encountered:
@chiourung Since the sflow config is not removed explicitly, you will have to use force option while doing a break out. This error is expected.
Please check and get back.
Description
After enabling sflow interface, it can't remove the port configuration from the CLI.
And then it can't do port breakout for the port.
Steps to reproduce the issue:
Describe the results you received:
The sflow design is in conflict with port dependency.
Describe the results you expected:
Output of
show version
:Output of
show techsupport
:Additional information you deem important (e.g. issue happens only occasionally):
The text was updated successfully, but these errors were encountered: