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

[Mux] Neighbor handling based on FDB entry #1631

Merged
merged 3 commits into from
Feb 11, 2021
Merged

Conversation

prsunny
Copy link
Collaborator

@prsunny prsunny commented Feb 8, 2021

What I did

  1. Neighbor handling based on FDB entries. When a new neighbor is learnt, the code lookup FDB table to get the associated physical port and based on the mux status for the port, the neighbor is programmed as local or tunnel nexthop.
  2. Log level/message revisited based on log observations from current deployments

Why I did it

How I verified it

Ethernet96 mux status is - Standby

show arp
Address       MacAddress         Iface            Vlan
------------  -----------------  ---------------  ------
192.168.0.101  00:00:11:22:33:45  Ethernet96       1000

Feb  6 02:48:21.931004 str2-7050cx3-acs-02 ERR swss#orchagent: :- getPort: Failed to get bridge port ID for FDB entry 00:00:11:22:33:55, rv:-5
Feb  6 02:48:21.931004 str2-7050cx3-acs-02 NOTICE swss#orchagent: :- getMuxPort: FDB entry not found: Vlan Vlan1000, mac 00:00:11:22:33:55
Feb  6 02:48:21.935757 str2-7050cx3-acs-02 NOTICE swss#orchagent: :- addNeighbor: Created neighbor ip 192.168.0.101, 00:00:11:22:33:55 on Vlan1000
Feb  6 02:48:21.937385 str2-7050cx3-acs-02 NOTICE swss#orchagent: :- addNextHop: Created next hop 192.168.0.101 on Vlan1000
Feb  6 02:48:21.938899 str2-7050cx3-acs-02 INFO swss#orchagent: :- update: Neigh 192.168.0.101 on Vlan1000, add 1, state 2
Feb  6 02:48:21.938899 str2-7050cx3-acs-02 NOTICE swss#orchagent: :- disableNeighbor: Neighbor disable request for 192.168.0.101 
Feb  6 02:48:21.940604 str2-7050cx3-acs-02 NOTICE swss#orchagent: :- removeNeighbor: Removed next hop 192.168.0.101 on Vlan1000
Feb  6 02:48:21.952963 str2-7050cx3-acs-02 NOTICE swss#orchagent: :- removeNeighbor: Removed neighbor 00:00:11:22:33:55 on Vlan1000
Feb  6 02:48:21.952989 str2-7050cx3-acs-02 INFO swss#orchagent: :- addTunnelRoute: Add tunnel route DB 'Vlan1000:192.168.0.101/32'
Feb  6 02:48:21.954947 str2-7050cx3-acs-02 NOTICE swss#orchagent: :- create_route: Created tunnel route to 192.168.0.101/32 

Details if related

orchagent/muxorch.cpp Show resolved Hide resolved
orchagent/muxorch.cpp Show resolved Hide resolved
orchagent/muxorch.cpp Show resolved Hide resolved
orchagent/muxorch.cpp Outdated Show resolved Hide resolved
orchagent/muxorch.cpp Outdated Show resolved Hide resolved
orchagent/muxorch.cpp Outdated Show resolved Hide resolved
orchagent/muxorch.cpp Show resolved Hide resolved
orchagent/muxorch.cpp Show resolved Hide resolved
gechiang
gechiang previously approved these changes Feb 10, 2021
@prsunny
Copy link
Collaborator Author

prsunny commented Feb 10, 2021

/AzurePipelines run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@prsunny
Copy link
Collaborator Author

prsunny commented Feb 10, 2021

retest vs please

@prsunny prsunny merged commit 3f11a50 into sonic-net:master Feb 11, 2021
@prsunny prsunny deleted the ipv6 branch February 11, 2021 20:16
daall pushed a commit that referenced this pull request Feb 16, 2021
* Mux neighbor handling based on FDB entry
DavidZagury pushed a commit to DavidZagury/sonic-swss that referenced this pull request Mar 4, 2021
* Mux neighbor handling based on FDB entry
raphaelt-nvidia pushed a commit to raphaelt-nvidia/sonic-swss that referenced this pull request Oct 5, 2021
* Mux neighbor handling based on FDB entry
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.

4 participants