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

[dhcpv6_relay] [counters] counters doesn't rise on tagged Physical Interface #17377

Open
vivekrnv opened this issue Dec 1, 2023 · 6 comments
Labels
Triaged this issue has been triaged

Comments

@vivekrnv
Copy link
Contributor

vivekrnv commented Dec 1, 2023

Description

With this new ability sonic-net/sonic-dhcp-relay#43 to see dhcp_relay counters in Physical interfaces in addition to L3 Vlan interface, I can't see Reply and Advertise counters rising on Physical interfaces connected to dhcp client, But I can see it on L3 Vlan interace.

The sonic-mgmt test covers this scenario, but for untagged interfaces.

root@qa-eth-vt01-5-2700a0:/home/admin# show dhcp_relay ipv6 counters 
       Message Type    Ethernet0(RX)
-------------------  ---------------
          Advertise                0
            Confirm                0
            Decline                0
Information-Request                0
          Malformed                0
             Rebind                0
        Reconfigure                0
      Relay-Forward                0
        Relay-Reply                2
            Release                0
              Renew                0
              Reply                0
            Request                0
            Solicit                0
            Unknown                0

       Message Type    Ethernet0(TX)
-------------------  ---------------
          Advertise                0
            Confirm                0
            Decline                0
Information-Request                0
          Malformed                0
             Rebind                0
        Reconfigure                0
      Relay-Forward                2
        Relay-Reply                0
            Release                0
              Renew                0
              Reply                0
            Request                0
            Solicit                0
            Unknown                0

       Message Type    Ethernet4(RX)
-------------------  ---------------
          Advertise                0
            Confirm                0
            Decline                0
Information-Request                0
          Malformed                0
             Rebind                0
        Reconfigure                0
      Relay-Forward                0
        Relay-Reply                0
            Release                0
              Renew                0
              Reply                0
            Request                1
            Solicit                1
            Unknown                0

       Message Type    Ethernet4(TX)
-------------------  ---------------
            Unknown                0
            Solicit                0
          Advertise                0
            Request                0
            Confirm                0
              Renew                0
             Rebind                0
              Reply                0
            Release                0
            Decline                0
        Reconfigure                0
Information-Request                0
      Relay-Forward                0
        Relay-Reply                0
          Malformed                0

       Message Type    Vlan2024(RX)
-------------------  --------------
          Advertise               0
            Confirm               0
            Decline               0
Information-Request               0
          Malformed               0
             Rebind               0
        Reconfigure               0
      Relay-Forward               0
        Relay-Reply               2
            Release               0
              Renew               0
              Reply               0
            Request               1
            Solicit               1
            Unknown               0

       Message Type    Vlan2024(TX)
-------------------  --------------
          Advertise               1
            Confirm               0
            Decline               0
Information-Request               0
          Malformed               0
             Rebind               0
        Reconfigure               0
      Relay-Forward               2
        Relay-Reply               0
            Release               0
              Renew               0
              Reply               1
            Request               0
            Solicit               0
            Unknown               0

Setup description

dhcp client -> Ethernet4 -> Vlan2024 -> Ethernet0 -> dhcp server

Steps to reproduce

  1. Configure interfaces to IPv6 DHCP server and Client
  2. Configure IPv6 dhcp_
  3. Request IPv6 address from ipv6 client
  4. check IPv6 dhcp relay counters
@vivekrnv
Copy link
Contributor Author

vivekrnv commented Dec 1, 2023

@yaqiangz @yxieca @kellyyeh, Please check

@yaqiangz
Copy link
Contributor

yaqiangz commented Dec 4, 2023

@vivekrnv I wonder whether we can confirm the advertise and reply packets is actually send to client in scenario you mentioned?

@vivekrnv
Copy link
Contributor Author

vivekrnv commented Dec 4, 2023

yes, it is sent. Client receive address, and we can see these counters rised on Vlan Interface

@yaqiangz
Copy link
Contributor

yaqiangz commented Dec 5, 2023

yes, it is sent. Client receive address, and we can see these counters rised on Vlan Interface

From dump file you shared, seems this is a ToRRouter? Could you share more details about this use case like why tagged is needed to let me fully understand this scenario?

@prgeor prgeor added the Triaged this issue has been triaged label Dec 6, 2023
@prgeor
Copy link
Contributor

prgeor commented Dec 6, 2023

@vivekrnv please confirm this is a valid scenario

@vivekrnv
Copy link
Contributor Author

vivekrnv commented Dec 7, 2023

yes, it is sent. Client receive address, and we can see these counters rised on Vlan Interface

From dump file you shared, seems this is a ToRRouter? Could you share more details about this use case like why tagged is needed to let me fully understand this scenario?

@yaqiangz , good point. Seems trunk vlan is not a general use case. Keeping the issue as open, as documentation

@vivekrnv vivekrnv changed the title [dhcpv6_relay] [counters] Advertise and Reply counters doesn't rise on tagged client Physical Interface [dhcpv6_relay] [counters] counters doesn't rise on tagged Physical Interface Dec 7, 2023
@moshemos moshemos assigned vivekrnv and unassigned vivekrnv Mar 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Triaged this issue has been triaged
Projects
None yet
Development

No branches or pull requests

4 participants