cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
528
Views
10
Helpful
6
Replies
Highlighted
Beginner

iWAN, Border Service-Provider Flap

Hi!

 

I have a network with iWAN configured. We have 2 data centers and about 60 remote sites configured as Branch-MC. A particular site is presenting problems in the domain, launching the message:

 

*** Domain MC Status ***

Master VRF: Global

Instance Type: Branch
Instance id: 0
Operational status: Down Reason: |Service-Provider Flap
(Automatic restart 00:51:37 later) (Needs manual shut/no shut if resolved earlier)
Configured status: Up

 

We have restarted the domain with the shut/noshut commands without success, since when you turn off the domain and get up again, stay up for a few seconds and again it goes down. We have validated the routing neighborhoods, the DMVPN tunnels without finding any effect.  My question is, validating the provider link, why does the iWAN domain show this message? What meaning this message?

 

Best Regards!

6 REPLIES 6
Highlighted
Beginner

Re: iWAN, Border Service-Provider Flap

Did you eventually get a fix for this issue? We are currently facing the same issue.

Highlighted
Beginner

Re: iWAN, Border Service-Provider Flap

@jesusresendiz & @mtorzewski Did you eventually find a fix for the issue? I will really appreciate your responses.

 

Kind regards.

Highlighted
Beginner

Re: iWAN, Border Service-Provider Flap

The fix in my network was I had an incorrect path name in my tunnel interface. 

domain iwan path MPLS1 path-id 1.

 

All hub routers participating in the same DMVPN cloud should have the same path name.  My network had two hubs each with two routers.  I have two dmvpn clouds.  So the routers in dmvpn cloud1 are named MPLS1 and the routers in dmvpn cloud2 are named MPLS2.  One of my hub routers had the wrong path name.   I corrected this and the problem went away immediately.

 

Hope this helps.

Highlighted
Beginner

Re: iWAN, Border Service-Provider Flap

@mtorzewski Thank you for your response. Please find attached my network diagram for your reference. In my case, I have 2 DMVPN clouds(one for MPLS & one for INET), 2 data centers with 1 ASR each acting as the HUB BR, Tunnel 11 is MPLS and Tunnel 12 is INET at each data center, 1 CSR1000V acting as HUB MC. However, going by the fix to your issue you are saying my config should be 


CAN1-iSAP-1001X-1#sh run int tu 11

<snippet>

domain iwan path MPLS path-id 1


CAN1-iSAP-1001X-1#sh run int tu 12

<snippet>

domain iwan path INET path-id 2

 

----------------------------------------------------

Second Data Center

----------------------------------------------------

BBN1-iSAP-1001X-1#sh run int tu 11

<snippet>

domain iwan path MPLS path-id 3

 

BBN1-iSAP-1001X-1#sh run int tu 12

<snippet>

domain iwan path INET path-id 4

---------------------------------------------------------------------------------

Current Configuration 

--------------------------------------------------------------------------------

 

CAN1-iSAP-1001X-1#sh run int tu 11

<snippet>

domain iwan path MPLS1 path-id 1


CAN1-iSAP-1001X-1#sh run int tu 12

<snippet>

domain iwan path INET1 path-id 2

 

----------------------------------------------------

Second Data Center

----------------------------------------------------

BBN1-iSAP-1001X-1#sh run int tu 11

<snippet>

domain iwan path MPLS2 path-id 3

 

BBN1-iSAP-1001X-1#sh run int tu 12

<snippet>

domain iwan path INET2 path-id 4

 

CAN1-iWAN-MC#sh run | s domain

<snippet>

domain iwan
vrf default
master hub
source-interface Loopback0
site-prefixes prefix-list Datacenter-PREFIXES
password 7 xxxxxxxxxxxx
load-balance
enterprise-prefix prefix-list ENTERPRISE-PREFIXES
collector 10.0.210.100 port 2055
class VOICE sequence 10
match dscp ef policy voice
path-preference MPLS1 MPLS2 fallback INET1 INET2
class CALL-SIGNALING sequence 20
match dscp cs3 policy low-latency-data
match dscp af31 policy low-latency-data
path-preference MPLS1 MPLS2 fallback INET1 INET2
class CRITICAL_DATA sequence 30
match dscp af21 policy low-latency-data
path-preference MPLS1 MPLS2 fallback INET1 INET2
class BULK-DATA sequence 40
match dscp af11 policy scavenger
path-preference INET1 INET2 fallback MPLS1 MPLS2
class DEFAULT sequence 50
match dscp default policy best-effort
path-preference INET1 INET2 fallback MPLS1 MPLS2


Thank you so much in advance for your time!

 

Highlighted
Beginner

Re: iWAN, Border Service-Provider Flap

Jide1 - you are correct - what you show typed in GREEN is the proper way.   The domain pathname should be the same for any tunnel interface of a hub router in the same DMVPN cloud.

Highlighted
Beginner

Re: iWAN, Border Service-Provider Flap

@mtorzewski Thank you! That fixed my issue too.