iWAN over 4G - Not Working

[wmoody329]

We are trying to replace a T1/MPLS transport with a 4G-LTE transport.  The routing comes up, but the connection to the Master-Controller never comes up. 'show domain IWAN2 master status' - reveals a few things that are really different:

Minimum Bytes Loss Calculation Threshold: 10240 bytes
Minimum Requirement: Not Met

In the logs I see:

Jul 31 11:26:57.235 EST: %DOMAIN-4-BR_SHUTDOWN: Reason=Minimum Requirement Not Met. Details:Instance=0: VRF=default: Min Requirement Mask=9
Jul 31 11:26:58.285 EST: %DOMAIN-4-MC_SHUTDOWN: Reason=Minimum Requirement Not Met. Details:Instance=0: VRF=default: Min Requirement Mask=1
Jul 31 11:26:58.291 EST: %DUAL-5-NBRCHANGE: EIGRP-SFv4 59501: Neighbor 10.42.0.250 (Loopback0) is down: static neighbor unconfigured

is there some obvious answer for this?  I keep thinking it's MTU related, buy maybe it's multicast related.  I'm not sure

[WVRD]

Did you ever figure out what was causing this? I have this same issue with a new site I'm trying to get up.

Many Thanks

[marce1000]

@WVRD  , Ah that good-ole 'did you ever fix this question' , note that I don't intend bashing or impoliteness. But such iterations are usually less productive for a number of reasons. 1) There is a time-delay (can be big) between message and your query 2) Poster might be doing something else 3) Posters-profile may even be no longer active or monitored. Better is to just post a new thread which also gives the benefit of describing your current environment and related problem (extra info's may then become available too)

 M.

[WVRD]

Thanks @marce1000 
|
|
|
but if anyone does have information on this issue that would be great.

[Georg Pauwen]

Hello,

can you post the full config of the 4G-LTE router ?

[WVRD]

Morning Georg,

I do not have access to ISP equipment unfortunately, there is the thought that the problem may be stemming from the ISP side though.

Not entirely sure what it could be but I see MC/BR status messages reference to a Minimum Requirement not met, no idea what that is though.

This is our 94th site activation and the first time seeing this occur.

Feb 21 04:43:35.366 GMT: %DOMAIN-5-MC_STATUS: Minimum Requirement Not Met. Details:Instance=0: VRF=default: Min Requirement Mask=1
Feb 21 04:45:31.123 GMT: %DOMAIN-5-BR_STATUS: Minimum Requirement Not Met. Details:Instance=0: VRF=default: Min Requirement Mask=9
Feb 21 05:03:36.966 GMT: %DOMAIN-4-MC_SHUTDOWN: Reason=Minimum Requirement Not Met. Details:Instance=0: VRF=default: Min Requirement Mask=1
Feb 21 05:05:31.915 GMT: %DOMAIN-4-BR_SHUTDOWN: Reason=Minimum Requirement Not Met. Details:Instance=0: VRF=default: Min Requirement Mask=9
Feb 21 05:05:34.992 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel0, changed state to up
Feb 21 05:23:38.536 GMT: %DOMAIN-5-MC_STATUS: Minimum Requirement Not Met. Details:Instance=0: VRF=default: Min Requirement Mask=1
Feb 21 05:25:34.282 GMT: %DOMAIN-5-BR_STATUS: Minimum Requirement Not Met. Details:Instance=0: VRF=default: Min Requirement Mask=9
Feb 21 05:43:39.608 GMT: %DOMAIN-4-MC_SHUTDOWN: Reason=Minimum Requirement Not Met. Details:Instance=0: VRF=default: Min Requirement Mask=1
Feb 21 05:45:36.193 GMT: %DOMAIN-4-BR_SHUTDOWN: Reason=Minimum Requirement Not Met. Details:Instance=0: VRF=default: Min Requirement Mask=9
Feb 21 05:45:53.609 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel0, changed state to up
Feb 21 06:03:54.625 GMT: %DOMAIN-5-MC_STATUS: Minimum Requirement Not Met. Details:Instance=0: VRF=default: Min Requirement Mask=1
Feb 21 06:05:52.928 GMT: %DOMAIN-5-BR_STATUS: Minimum Requirement Not Met. Details:Instance=0: VRF=default: Min Requirement Mask=9
Feb 21 06:23:55.731 GMT: %DOMAIN-4-MC_SHUTDOWN: Reason=Minimum Requirement Not Met. Details:Instance=0: VRF=default: Min Requirement Mask=1
Feb 21 06:25:54.364 GMT: %DOMAIN-4-BR_SHUTDOWN: Reason=Minimum Requirement Not Met. Details:Instance=0: VRF=default: Min Requirement Mask=9
Feb 21 06:26:04.609 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel0, changed state to up
Feb 21 06:37:59.677 GMT: %SEC_LOGIN-5-LOGIN_SUCCESS: Login Success [user: XXX] [Source: 10.60.20.146] [localport: 23] at 06:37:59 GMT Mon Feb 21 2022
XXXINET01# sh domain default master status

*** Domain MC Status ***

Master VRF: Global

Instance Type: Branch
Instance id: 0
Operational status: Up
Configured status: Up
Loopback IP Address: 10.240.3.95
Operational Mode: With Hub
Load Balancing:
Operational Status: Down
Route Control: Enabled
Transit Site Affinity: Disabled
95% Bandwidth Check: Enabled
Remote Branch Bandwidth Check: Disabled
Load Sharing: Disabled
Connection Keepalive: 10 seconds
Mitigation mode Aggressive: Disabled
Policy threshold variance: 20
Minimum Mask Length Internet: 24
Minimum Mask Length Enterprise: 24
Syslog TCA suppress timer: 180 seconds
Traffic-Class Ageout Timer: 5 minutes
Global Fallback Timer: 3 minutes
Minimum Packet Loss Calculation Threshold: 15 packets
Minimum Bytes Loss Calculation Threshold: 10240 bytes
Branch to Branch Traffic Control: Enabled
Direct Cloud Access : Disabled
Maximum Traffic Classes Supported: 4000
Minimum Requirement: Not Met
Policy update: Not received
Globals Update: Not received
Capability update from hub: Not received
(Will attempt shut/no-shut if min requirement not meet in 340 secs)

Borders:
IP address: 10.240.3.95
Version: 2
Connection status: CONNECTED (Last Updated 00:12:28 ago )
Interfaces configured:

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

[WVRD]

Turn's out there was indeed a static nat rule on the ISP's routers WAN interface. After deletion tunnels came up fine.

Regards

[Georg Pauwen]

Hello,

if possible, post the output of the command:

show domain border status