Some time i got anomaly traffic like below pic.We can see below my NPM
server (10.103.248.55) monitor on of my VM on azure (10.201.1.7).All non
PING traffic have right path where the traffic routed to Azure Tunnel
Interface.But PING traffic routed to...
I have topology with this details - Hub subnet 10.103.0.0/16 - Spoke1
subnet 10.100.0.0/16 - Spoke2 subnet 10.4.0.0/16 and 10.107.0.0/16 - Hub
and Spoke have 2 internet connection. - ADVPN and BGP was established
also with the shortcut tunnel - ADVPN...
My fortigate hub have BGP connection to the spoke, the spoke ip is
10.10.112.11 and BGP was established. But why i can't ping to that spoke
bgp peer ip? So traffic from the hub can't reach the spoke using this
tunnel interfaceIf i ping 10.10.112.1 fr...
hi @syordanov Yes now if tunnel to azure down the traffic will be use
default route (to interent).Let me try to configure the black hole for
every spoke and hub.
Hi @syordanov Thanks for your reply.Currently i use hub and spoke with
BGP and SDWAN enabled. The hub connect to 5 spoke and every spoke have
ipsec tunnel also to the azure. Below my subnet :Hub :
10.100.0.0/16spoke1 : 10.101.0.0/16spoke2 : 10.102.0....
The BGP was established and routing to teh spoke from hub via
10.10.112.6 B 10.4.0.0/16 [200/0] via 10.10.112.6 (recursive is directly
connected, DC-SEG-BALI), 00:01:30, [1/0][200/0] via 10.103.113.6
(recursive is directly connected, DC-SEG-MPLS), 00...
Hi, The reason why we see only 40 second is I shutdown the tunnel
interface if i'm not troubleshoot this. Let this tunnel up will make
connection from hub subnet to the spoke subnet will be not established.
So i shutdown to let bgp send the traffic u...
