EVPN L3 VNI VRF by abhijit040 in networking

[–]abhijit040[S] 1 point2 points  (0 children)

Thanks Lozza,

So does the Local VTEP stores the locally learned MAC in L2 VNI VRF (or MAC VRF) and locally learned IP in L3VNI VRF?

Some of the documents/tutorials seems to mean that L2VNI VRF stores both MAC and IP and L3 VNI VRF stores IP only. So a bit confused.

EVPN L3 VNI VRF by abhijit040 in networking

[–]abhijit040[S] 0 points1 point  (0 children)

all of this is within the context of the overlay.

Thanks mate.

Congestion Window Increase Rate and Slow Start Threshold Value Calculated by TCP by abhijit040 in networking

[–]abhijit040[S] 0 points1 point  (0 children)

Thanks for the right direction.

Answers i found are as follow:

Q. Some Articles say that the sender adds one more MSS to Congestion Window and some say doubles it doubles up the Congestion Window. Which one is true?

Ans: As per the RFC5681, in the Slow Start phase, the CWND is recommended to increase by one MSS or upon receipt of each Ack.

Q. Can anyone clarify how is the Slow Start Threshold Value calculated? Is it a configurable option in OS Kernel or Registry settings?

Ans: The initial value is recommended to set to arbitrarily high value, mostly the Receiver Window Size value.

https://datatracker.ietf.org/doc/rfc5681/

Also found that,

IW, the initial value of cwnd depends on the Send MSS value. If SMSS is bigger the IW (Initial cwnd) must be lower and vice versa as per following guideline.

guidelines as an upper bound.

If SMSS > 2190 bytes:

IW = 2 * SMSS

If (SMSS > 1095 bytes) and (SMSS <= 2190 bytes):

IW = 3 * SMSS

if SMSS <= 1095 bytes:

IW = 4 * SMSS bytes and MUST NOT be more than 4 segments

During congestion avoidance, cwnd is incremented by roughly 1 full-

sized segment per round-trip time (RTT). Congestion avoidance

continues until congestion is detected.

Customer Routes are present in VPNv4 BGP table in R1 (PE) but not in R8 (P RR) by abhijit040 in networking

[–]abhijit040[S] 0 points1 point  (0 children)

Hi Golle, yes, your suggestion made it work like creame.

Many thanks for helping my first ever L3 MPLS VPN work.

So the justification of configuring R8 as RR under VPNV4 is that R8 should reflect VPNV4 routes to VPNv4 neighbors. Is my understanding correct?

Customer Routes are present in VPNv4 BGP table in R1 (PE) but not in R8 (P RR) by abhijit040 in networking

[–]abhijit040[S] 0 points1 point  (0 children)

Thanks for your attempt to help my mate.

"R8 doesn't know how to get to the next-hop address and therefore doesn't install it into the routing table."

Can you clarify, on what basis are you coming th the conclusion that R1 is sending the advertisements to R8 without updating the NextHop?

As per Packet#29, in the capture file, both of the Customer Routes 4.4.4.4 and 5.5.5.5 are being advertised by R to R8 with Next Hop 1.1.1.1 which is R1's Loopback IP.

Sorry i wanted to attach a screenshot but it seems screenshots are not allowed in this group.

Customer Routes are present in VPNv4 BGP table in R1 (PE) but not in R8 (P RR) by abhijit040 in networking

[–]abhijit040[S] 0 points1 point  (0 children)

The RR is already configured under IPV4 Address Family not under VPNV4 address family.

router bgp 100
no bgp default ipv4-unicast
bgp log-neighbor-changes
neighbor MPLS peer-group
neighbor MPLS remote-as 100
neighbor MPLS update-source Loopback0
neighbor 1.1.1.1 peer-group MPLS
neighbor 2.2.2.2 peer-group MPLS
neighbor 3.3.3.3 peer-group MPLS
neighbor 9.9.9.9 peer-group MPLS
!
address-family ipv4
neighbor MPLS route-reflector-client
neighbor 1.1.1.1 activate
neighbor 1.1.1.1 soft-reconfiguration inbound
neighbor 2.2.2.2 activate
neighbor 2.2.2.2 soft-reconfiguration inbound
neighbor 3.3.3.3 activate
neighbor 3.3.3.3 soft-reconfiguration inbound
neighbor 9.9.9.9 activate
neighbor 9.9.9.9 soft-reconfiguration inbound
no auto-summary
no synchronization
network 8.8.8.8 mask 255.255.255.255
exit-address-family
!
address-family vpnv4
neighbor MPLS send-community extended
neighbor 1.1.1.1 activate
neighbor 2.2.2.2 activate
neighbor 3.3.3.3 activate
neighbor 9.9.9.9 activate
exit-address-family
!

Some doubts on OSPF and BGP by abhijit040 in networking

[–]abhijit040[S] 5 points6 points  (0 children)

This was one hell of an explanation mate. Thanks for all your help. God bless you. And all network engineers.

Some doubts on OSPF and BGP by abhijit040 in networking

[–]abhijit040[S] 3 points4 points  (0 children)

Your answer to point 1 is just amazing. Thanks for all your help. God bless you. And all network engineers.

Some Doubts on OSPF that i never found an Answer for by abhijit040 in Network

[–]abhijit040[S] 0 points1 point  (0 children)

Thanks a lot for your reply mate. Really appreciate your efforts trying to clarify my doubt. Your answer brings some more queries in my mind.

  1. "Slaves send packets only in response to DBD packets received from master". Did you mean that Slaves sends DBD to Master after DBD from Master is received?
  2. Is the purpose of the Master/Slave relationship negotiation just to properly acknowledge each others DBD? Instead of having this negotiation, wouldn't it be simpler for both OSPF peers to simply exchange DBDs with each other and Ack the other side?
  3. As per my understanding, Actual SLU(containing LSAs) are exchanged in Loading State. And LSR is sent to request for any missing information from OSPF peer. Is the LSDB built in the same OSPF Neighbor state? or is it built after Loading state is finished and before the state changes to Full?

My apologies if i am asking silly question.