3.3. Show Commands#
- show memory dataplane#
Display the amount of memory used by objects of the Data Plane. You can use this command to find out how much memory is used by different objects like IP pools in NAT, ACL, etc.
- show memory dataplane pools#
Display resource usage for each entity (like subscribers, sessions, etc) per socket:
# show memory dataplane pools --------------------------------------------------------------------------------------- Statistics for Socket 0 --------------------------------------------------------------------------------------- Total Used Free Drops Load --------------------------------------------------------------------------------------- Subscribers 1527648 161520 1366128 0 10.6% Mappings 85027648 1096285 83931363 0 1.3% Sessions 85027648 1164505 83863143 0 1.4% Fragments 65536 0 65536 0 0.0% Pending Fragments 1024 2 1022 0 0.2% --------------------------------------------------------------------------------------- --------------------------------------------------------------------------------------- Statistics for Socket 1 --------------------------------------------------------------------------------------- Total Used Free Drops Load --------------------------------------------------------------------------------------- Subscribers 1527648 144786 1382862 0 9.5% Mappings 85027648 970063 84057585 0 1.1% Sessions 85027648 1030252 83997396 0 1.2% Fragments 65536 4 65532 0 0.0% Pending Fragments 1024 2 1022 0 0.2% --------------------------------------------------------------------------------------- --------------------------------------------------------------------------------------- Total Used Free Drops Load --------------------------------------------------------------------------------------- IPv4 neighbors 1024 12 1012 0 1.2% IPv6 neighbors 1024 0 1024 0 0.0% ARP wait_ctx 0 69632 15 69617 0 0.0% ARP wait_ctx 1 69632 15 69617 0 0.0% ---------------------------------------------------------------------------------------
- clear memory dataplane pools#
Clear
Dropsstatistics in memory dataplane pools table.
- show memory dataplane debug NAME...#
Display detailed information on the amount of memory used by the Data Plane objects. Also, you can see the memory addresses of the objects.
- show overruns#
- clear overruns#
All of these counters are packet losses that have occurred because a particular internal queue has run out of space:
Counter
Description
Internal OverrunsInternal Overruns are internal packet queues sent to the operating system kernel. This is all traffic that goes to the IP addresses configured on the NAT interface
Work OverrunsAfter we have read a packet from the queue of the network interface, the RXTX tasks balance the Work tasks where all the packet processing takes place. The overrun data tells us that the packet was lost because it could not be passed to the next processing stage after being read from the interface
TX OverrunsAfter processing, the packets are delivered to the RXTX tasks that send them to the network interface. These losses indicate an overflow of queues for sending between Work and RXTX tasks
- show cpu#
Display the maximum load of the processor core at the moment. If, for example, you have 50 cores and, for some reason, only one is loaded, and all the others are idle, then the command will show exactly this load, and there will be no averaging.
- show cpu debug#
Display the load for each processor core:
socket- processor IDcore- the number of the physical corelcore- the number of the logical cores. One physical core may have several logical ones
- show cpu task#
Display which core is responsible for which tasks.
- show debugging nat-hash-stats#
Display bucket information for Session, Mapping, Subscriber, and IP fragment: the amount of the elements in the bucket and how many buckets with such elements are in the system.
- show debugging packets-pool#
Display information about packet pools. NAT is the device that handles packet processing. After a packet arrives at the NIC, we read it into our internal mbuf data structure. The packet pool is a predefined and prepared pool from which we can take the mbuf internal packet data structure. The size of the pool is the number of packets that can be in the system at the same time.
- show debugging queues-internal#
Display debugging information on internal queues.
- show license host-id#
Display the host ID that is used for licensing.
- show license limits [FILENAME]#
Display the limits on the host issued by the license. When specifying the file name, check this information from it.
- show platform settings#
Display the low-level vCGNAT settings.
- show port [(0-255)]#
Display full information about the physical port.