1. Xi Yang

Xi Yang

Forum Replies Created

Viewing 10 posts - 1 through 10 (of 10 total)
  • Author
    Posts
  • in reply to: pmservice ‘more destinations’ issue on STAR #6233
    Xi Yang
    Participant

      As the error message told, the same source port was attempted to mirror to more than one destination port. If this was not an experiment script code error, there might be some leaked slice still hanging in there. The whole testbed is in maintenance now. After 1/5/2024, try it again, if the problem remains, we can help check the switch configs.

      in reply to: Role of uplink vlans #6203
      Xi Yang
      Participant

        Let’s break down to discuss the following FABRIC network services.

        • L2Bridge: There is no uplink.
        • L2STS and L3**: VLANs are stripped at the edge and traffic payload is put on MPLS tunnel or on IP routing instances. VLAN notion is not across sites.
        • L2PTP: An EVPN/BGP signaling based pseudowire service. The VLAN tag information is communicated on the pseudowire protocol but this may not be the same as an “uplink” notion.

        @Nik can you explain what you are looking for or trying to achieve?

        in reply to: Port mirroring issue for Bundle-Ether ports #6202
        Xi Yang
        Participant

          Bundle-Ether (400G) interfaces are not supported in our network service templates. We will discuss this internally and would likely support it in a next software release.

          in reply to: pmservice issue for multiple uplink ports #6167
          Xi Yang
          Participant

            I tried a few tests with AMST Hu0/0/0/23 mirrored to Hu0/0/0/3 and Hu0/0/0/4. Both were successful. My guess is that the failed request might have used a port that is unacceptable, or there were dup sessions with conflicting source or destination port.

            in reply to: pmservice issue for multiple uplink ports #6165
            Xi Yang
            Participant

              @Nik Can you tell the source and destination of the mirroring on AMST? I can see HundredGigE0/0/0/23 is one of them. My guess is that there was a dup mirroring session on either the same source or same destination port. I can help check.

              • This reply was modified 3 months, 3 weeks ago by Xi Yang.
              in reply to: Packets with bad checksum being dropped. #3155
              Xi Yang
              Participant

                Arash, can you clarify that by checksum you mean ip header or Ethernet frame?

                For IP header you can try L2PTP. For Ethernet, as Dale pointed out, you may have to consider optical layer solutions.

                in reply to: Packets with bad checksum being dropped. #2968
                Xi Yang
                Participant

                  type='L2Bridge' can only be used for “same site” network. type='L2PTP' can only be used for between two different sites. If you are trying to set up a network within the same site, you cannot use L2PTP.

                  in reply to: Packets with bad checksum being dropped. #2942
                  Xi Yang
                  Participant

                    Can you elaborate “Could not change any device features”? Where do you see that?

                     

                    in reply to: Packets with bad checksum being dropped. #2908
                    Xi Yang
                    Participant

                      There are three types of “layer 2 network” supported on FABRIC. L2Bridge and L2STS are commonly used but may not be completely L3 transparent. The other is L2PTP, which is based on Pseudowire and supposed to be “more” Layer-2.

                      If your two nodes are at the same site, you don’t have other choice but L2Bridge.

                      If your two nodes are from different sites, system will pick L2STS or L2PTP for you. To force the type, use slice.add_network(... type='L2PTP'). See if that helps.

                      • This reply was modified 1 year, 6 months ago by Xi Yang.
                      in reply to: Release 1.1 known bugs and limitations #1728
                      Xi Yang
                      Participant

                        3. When site VMs are allocated along with a FABNetv6 service, the IPv6 address on the VM hosts may lose connectivity due to gateway MAC expiration. This was exhibited as ping disruption.

                        Resolution: Need to change the timing of FABNetv6 service and host interface activation. Or embed the below workaround in the fablib post-slice action.

                        Workaround: Toggle down and up the host interface with the problematic IPv6 address. Then reassign the IPv6 address and re-add the host routes.

                         

                      Viewing 10 posts - 1 through 10 (of 10 total)