Description

This article provides information on how to check SRX-IDP for memory exhaustion or leak.

Symptoms

Administrators may want to check f the IDP process is running out of memory due to memory leak  or exhaustion.

Solution

 

To check the state of IDP memory, shell into the vty prompt and run show usp idp status . In this example, shell was performed into a high-end SRX device.

Note : For branch SRX devices, the administrator will vty into fwdd; instead of pic .

[email protected]> start shell
root@srx3400-172% tnpdump (to get the PIC infor)
node1.fpc6.pic0 0x2100116 02:00:00:02:01:16 em0 1500 2 0 3

root@srx3400-172% vty node1.fpc6.pic0

[flowd]FPC6.PIC0(vty)# show usp idp status
IDP module initialized : yes
State (0-off, 1-on, 2-default): 2
Total active sessions : 0, limit 131072
Loopback mode : no
Datapath memory used : 21221024 bytes, limit 180000000 bytes
Control memory used : 34250696 bytes, limit 180355072 bytes
Policy information :
Subscriber: 's0', Installed policies: 1
id name sessions memory detector appid
5 HTTP_Audit 0 0 12.6.140120907 5056064
Platform information :
4G SPU(yes), Flow SPUs(1) CP present(yes) CP(yes) SPU(yes)
Mode : regular
Cluster(yes) coldsync(complete) state(complete)
The datapath memory is being used, which will show the memory that is used on the fowarding plane. Control memory is for the routing engine. Typically, the datapath memory is to be given more attention. If the datapath memory is approaching the limit or constantly rising and staying high during off hours, there could be memory leak or memory exhaustion.

Modification History

+ This issue seen on SRX300