B. IPN interpod network, routing is involved, networks in one pod must be routed over to other pod and vice versa. D. Adjust MTU to accommodate VXLAN header size.
Spine Switches and IPN Connectivity
If you have multiple spine switches in each pod, it is not mandatory to connect every spine
that is deployed in a pod to the IPN devices, even though two should be a minimum for
redundancy. For example, when you have four spine switches in a pod, you can connect
only two to the IPN, without functional implications for unicast communication across sites.
The local leaf nodes that encapsulate the traffic to a remote pod would always prefer the
paths through the spine switches that are actively connected to the IPN devices (based on
IS-IS routing metric). Similarly, you won’t experience issues with the BUM traffic that needs
to be sent to remote pods, since only the spine nodes that are connected to the IPN
devices will be responsible for handling such traffic.
This section is not available anymore. Please use the main Exam Page.300-630 Exam Questions
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
kamkol
10 months agoTito234
2 years agoPrimax
2 years, 2 months agoThenji0202
1 year, 6 months agoapot
3 years, 4 months ago