Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Multi-AISC] Pass the asic instance as SAI attribute during switch_create #1269

Merged
merged 4 commits into from
Apr 23, 2020

Conversation

judyjoseph
Copy link
Contributor

What I did
Added the new option [-i INST_ID] in orchagent to get the asic instance id passed by user and populate it in SAI_SWITCH_ATTR_SWITCH_HARDWARE_INFO during create_switch().

Why I did it
In multi-ASIC platforms the create_switch API should inform the syncd/SAI/SDK the particular ASIC instance to be initialized and controller by this orchagent.

How I verified it
Verified on a multi-ASIC and single ASIC devices the orchagent/syncd is up interfaces in good state.

Need additional change in the file sonic-buildimage/dockers/docker-orchagent/orchagent.sh to pass the instance ID with -i option.

Details if related

…rchagent to accept the

instance ID which is fills in HARDWARE_INFO and passes to switch create.
orchagent/main.cpp Outdated Show resolved Hide resolved
orchagent/main.cpp Outdated Show resolved Hide resolved
@lguohan lguohan merged commit d304673 into sonic-net:master Apr 23, 2020
rlhui pushed a commit that referenced this pull request Apr 30, 2020
…eate (#1269)

* SAI 3.7 Supports multiple ASIC instances. This change is needed for orchagent to accept the
instance ID which is fills in HARDWARE_INFO and passes to switch create.

* Update the usage help string with the new option [-i INST_ID]
@judyjoseph judyjoseph deleted the sai_instance branch April 30, 2020 21:20
EdenGri pushed a commit to EdenGri/sonic-swss that referenced this pull request Feb 28, 2022
…c-net#1269)

**- What I did**

When adding or deleting an DHCP relay destination address to a VLAN, previously, the service was simply restarted. However, we have set a start limit on services in SONiC, such that if a service is restarted X times within Y time, the service will enter a failed state and cannot be started until the failed state is cleared (currently 3 times within 20 minutes). However, if someone attempts to perform more than 3 add or delete operations within 20 minutes, it would trigger this failure condition. This change prevents this form occurring.

**- How I did it**

Rather than simply calling `systemctl restart dhcp_relay` after adding or deleting a DHCP relay destination IP address, we now call:

```
systemctl stop dhcp_relay
systemctl reset-failed dhcp_relay
systemctl start dhcp_relay
```
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants