are able to ping P2P and loopback IP from A to B and also vice versa.

【Problem Description】

are able to ping P2P and loopback IP from A to B and also viceversa.

And ping from Device A to C and C to A is also fine.  

We are also able to ping between B and C but if we are pingingrouter A from B by taking source IP as for C then we are unable to ping.

【Problem Analysis】

As just remote session, C cannot ping A, also B cannot ping A bytaking source address 172.30.250.2.

That means A cannot create connectivity with 172.30.250.0/30segment, this is in line with our judgment.

Because the fib table is fully.

Also you can see there are alarms for the L3 resource usage.

And as we found, much many 32-bit detailed bgp route learned onthe A-hyd device which is crazy

Generally, the learned BGP routes are summarized routes.

1. Asyou can see the fib entry count, and the mode is enhanced-arp that is defaultmode.

<hyd.br1-tdc.r1-hua-6720>disfib 0 statistics

RouteEntry Count : 13737

RoutePrefix Count : 13737

<hyd.br1-tdc.r1-hua-6720>disresource-mode configuration

Slot      Current Mode    Next Mode

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

0          enhanced-arp   enhanced-arp

Italready exceeds the ipv4 fib resource specification. Andyou cannot change the resource allocation mode because mac-addresses of thedevice are also large. Thereare still a lot of 32-bit detailed bgp route learned on this device, you maycontinue to aggregate them.

【Root Cause】

routing exceeds the ipv4 fib resource specification

【Solution Description】

Please aggregate the bgp routes on your network.