cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
700
Views
4
Helpful
5
Replies

Edge is in good status

interfacedy
Spotlight
Spotlight

.Hello, Why 6 Edge is up and it also shows "Partial" with yellow? Please see the below. Is this normal?  Thanks

interfacedy_0-1678599137386.png

Is this relative with "connet"? Please see the below

interfacedy_0-1678600421774.png

 

 

 

 

2 Accepted Solutions

Accepted Solutions

Hi,

it is relevant,but indirectly.

Basically partial overlay connectivity means that, not all TLOCs (transport interfaces) have been joined to overlay.

In order to join to overlay, you need connection with vSmart (control plane connectivity) and connection with other vEdges.

In your case, router's "public-internet" TLOC does not have control connection to vSmart, because it even cannot connect to vBond. Whenever you fix the issue, you will have full connectivity.

Begin to do troubleshooting why interface cannot connect to vBond (your highlighted). Then it should reach vSmart, after that must connect to other routers respective TLOCs.

HTH,

HTH,
Please rate and mark as an accepted solution if you have found any of the information provided useful.

View solution in original post

Hi,

yes, it is normal. Each TLOC (interface) will use its interface based default route  next-hop to reach controllers. So, normally TLOC1 does not use default route over TLOC2. You should have explicit path via TLOC1 to reach controllers which clearly indicates that you have path directly from TLOC1.

HTH,

Please rate and mark as an accepted solution if you have found any of the information provided useful.

HTH,
Please rate and mark as an accepted solution if you have found any of the information provided useful.

View solution in original post

5 Replies 5

Hi,

it is relevant,but indirectly.

Basically partial overlay connectivity means that, not all TLOCs (transport interfaces) have been joined to overlay.

In order to join to overlay, you need connection with vSmart (control plane connectivity) and connection with other vEdges.

In your case, router's "public-internet" TLOC does not have control connection to vSmart, because it even cannot connect to vBond. Whenever you fix the issue, you will have full connectivity.

Begin to do troubleshooting why interface cannot connect to vBond (your highlighted). Then it should reach vSmart, after that must connect to other routers respective TLOCs.

HTH,

HTH,
Please rate and mark as an accepted solution if you have found any of the information provided useful.

interfacedy
Spotlight
Spotlight

Thank you very much for your reply!

After adding another default route at vEdge, the issue is resolved. so that each vEdge has two default route to the controller, one via biz-internet, second via public-internet. Is this correct way to configure vEdge? 

Hi,

yes, it is normal. Each TLOC (interface) will use its interface based default route  next-hop to reach controllers. So, normally TLOC1 does not use default route over TLOC2. You should have explicit path via TLOC1 to reach controllers which clearly indicates that you have path directly from TLOC1.

HTH,

Please rate and mark as an accepted solution if you have found any of the information provided useful.

HTH,
Please rate and mark as an accepted solution if you have found any of the information provided useful.

interfacedy
Spotlight
Spotlight

Thank you very much! you gave a very good explanation

svemulap@cisco.com
Cisco Employee
Cisco Employee
Hi,

It could be for various reasons.
You didn't mention, which release is the vManage running ON.
Try restarting application-server NMS process to see, if it fixes the GUI issue.
CLI: request nms application-server {stop/start} or {restart}

HTH

Review Cisco Networking for a $25 gift card