Fortinet black logo

Handbook

GTP performance

6.0.0
Copy Link
Copy Doc ID 4afb0436-a998-11e9-81a4-00505692583a:107121
Download PDF

GTP performance

There are independent Receive and Transmit queues for gtp-u process. These queues are and their associated resources are initialized when the gtp-enhance-mode is enabled.

CLI changes under system npu

gtp-enhance-mode

config system npu

set gtp-enhance-mode {enable|disable}

end

tooltip icon This configuration requires a reboot of the device to initialize the changes.

gtp-enhance-cpu-range

This is used to set the CPUs which can process the GTP-U packet inspection.

config system npu

set gtp-enhance-cpu-range {0|1|2}

end

Option Description
0 Inspect GTPU packets by all CPUs
1 Inspect GTPU packets by primary CPUs
2 Inspect GTPU packets by secondary CPUs

Diagnose commands

diagnose npu np6 hbq-stats {all|np xx}

Used to see the GTP-U packet counter by all NP or the corresponding np.

diagnose npu np6 hbq-stats-clear all /np xx

Used to clear the GTP-U packet counter by all NP or the corresponding np.

Verifying the enhance-mode is disabled

Before execute the test or enable/disable the gtp enhance, first check the gtp-enhance-mode status as in the example below:

config system npu

get

gtp-enhance-mode: disable

gtp-enhance-cpu-range: 0

end

If the gtp-enhance-mode is disable, use the command diagnose npu np6 hbq-stats all.

The output will be similar to below:

# diagnose npu np6 hbq-stats all

Total :0

If the gtp-enhance-mode is enable, use the command diagnose npu np6 hbq-stats all

The output will be similar to below:

# diagnose npu np6 hbq-stats all

cpu_ 0:0

cpu_ 1:0

cpu_ 2:0

cpu_ 3:0

cpu_ 4:0

cpu_ 5:0

cpu_ 6:0

cpu_ 7:0

cpu_ 8:0

cpu_ 9:0

cpu_10:0

cpu_11:0

cpu_12:0

cpu_13:0

cpu_14:0

cpu_15:0

cpu_16:0

cpu_17:0

cpu_18:0

cpu_19:0

cpu_20:0

cpu_21:0

cpu_22:0

cpu_23:0

cpu_24:0

cpu_25:0

cpu_26:0

cpu_27:0

cpu_28:0

cpu_29:0

cpu_30:0

cpu_31:0

cpu_32:0

cpu_33:0

cpu_34:0

cpu_35:0

cpu_36:0

cpu_37:0

cpu_38:0

cpu_39:0

Total :0

Sometimes, when loading the new configure file, and the new configure file does not match the old configure file,

the gtp-enhance-mode status will be confused.

You can see :

#config system npu

#get

gtp-enhance-mode: enable

but you can also see that

diagnose npu np6 hbq-stats all

Total :0

This means the gtp-enhance-mode is actually set to disable.

The inverse is also possible, when you see

#config system npu

#get

gtp-enhance-mode: disable

but you also see that

# diagnose npu np6 hbq-stats all

cpu_ 0:0

...

cpu_39:0

Total :0

This means the gtp-enhance-mode is actually set to enable.

If these combinations occur, just run the command below:

config system npu

set gtp-enhance-mode enable

end

or

config system npu

set gtp-enhance-mode disable

end

Once this is done, reboot the device to let the 2 statuses match.

GTP performance

There are independent Receive and Transmit queues for gtp-u process. These queues are and their associated resources are initialized when the gtp-enhance-mode is enabled.

CLI changes under system npu

gtp-enhance-mode

config system npu

set gtp-enhance-mode {enable|disable}

end

tooltip icon This configuration requires a reboot of the device to initialize the changes.

gtp-enhance-cpu-range

This is used to set the CPUs which can process the GTP-U packet inspection.

config system npu

set gtp-enhance-cpu-range {0|1|2}

end

Option Description
0 Inspect GTPU packets by all CPUs
1 Inspect GTPU packets by primary CPUs
2 Inspect GTPU packets by secondary CPUs

Diagnose commands

diagnose npu np6 hbq-stats {all|np xx}

Used to see the GTP-U packet counter by all NP or the corresponding np.

diagnose npu np6 hbq-stats-clear all /np xx

Used to clear the GTP-U packet counter by all NP or the corresponding np.

Verifying the enhance-mode is disabled

Before execute the test or enable/disable the gtp enhance, first check the gtp-enhance-mode status as in the example below:

config system npu

get

gtp-enhance-mode: disable

gtp-enhance-cpu-range: 0

end

If the gtp-enhance-mode is disable, use the command diagnose npu np6 hbq-stats all.

The output will be similar to below:

# diagnose npu np6 hbq-stats all

Total :0

If the gtp-enhance-mode is enable, use the command diagnose npu np6 hbq-stats all

The output will be similar to below:

# diagnose npu np6 hbq-stats all

cpu_ 0:0

cpu_ 1:0

cpu_ 2:0

cpu_ 3:0

cpu_ 4:0

cpu_ 5:0

cpu_ 6:0

cpu_ 7:0

cpu_ 8:0

cpu_ 9:0

cpu_10:0

cpu_11:0

cpu_12:0

cpu_13:0

cpu_14:0

cpu_15:0

cpu_16:0

cpu_17:0

cpu_18:0

cpu_19:0

cpu_20:0

cpu_21:0

cpu_22:0

cpu_23:0

cpu_24:0

cpu_25:0

cpu_26:0

cpu_27:0

cpu_28:0

cpu_29:0

cpu_30:0

cpu_31:0

cpu_32:0

cpu_33:0

cpu_34:0

cpu_35:0

cpu_36:0

cpu_37:0

cpu_38:0

cpu_39:0

Total :0

Sometimes, when loading the new configure file, and the new configure file does not match the old configure file,

the gtp-enhance-mode status will be confused.

You can see :

#config system npu

#get

gtp-enhance-mode: enable

but you can also see that

diagnose npu np6 hbq-stats all

Total :0

This means the gtp-enhance-mode is actually set to disable.

The inverse is also possible, when you see

#config system npu

#get

gtp-enhance-mode: disable

but you also see that

# diagnose npu np6 hbq-stats all

cpu_ 0:0

...

cpu_39:0

Total :0

This means the gtp-enhance-mode is actually set to enable.

If these combinations occur, just run the command below:

config system npu

set gtp-enhance-mode enable

end

or

config system npu

set gtp-enhance-mode disable

end

Once this is done, reboot the device to let the 2 statuses match.