CPU info
> get perf cpu detail
Average System Utilization: 1%
Last 60 seconds:
59: 2 58: 2 57: 2 56: 2 55: 2 54: 2
53: 2 52: 2 51: 2 50: 2 49: 2 48: 2
47: 2 46: 2 45: 2 44: 2 43: 2 42: 2
41: 2 40: 2 39: 2 38: 2 37: 2 36: 2
35: 2 34: 2 33: 2 32: 2 31: 2 30: 2
29: 2 28: 2 27: 2 26: 2 25: 2 24: 2
23: 2 22: 2 21: 2 20: 2 19: 2 18: 2
17: 2 16: 2 15: 2 14: 2 13: 2 12: 2
11: 2 10: 2 9: 2 8: 2 7: 2 6: 2
5: 2 4: 2 3: 2 2: 2 1: 2 0: 2Last 60 minutes:
59: 2 58: 1 57: 2 56: 2 55: N/A 54: N/A
53: N/A 52: N/A 51: N/A 50: N/A 49: N/A 48: N/A
47: N/A 46: N/A 45: N/A 44: N/A 43: N/A 42: N/A
41: N/A 40: N/A 39: N/A 38: N/A 37: N/A 36: N/A
35: N/A 34: N/A 33: N/A 32: N/A 31: N/A 30: N/A
29: N/A 28: N/A 27: N/A 26: N/A 25: N/A 24: N/A
23: N/A 22: N/A 21: N/A 20: N/A 19: N/A 18: N/A
17: N/A 16: N/A 15: N/A 14: N/A 13: N/A 12: N/A
11: N/A 10: N/A 9: N/A 8: N/A 7: N/A 6: N/A
5: N/A 4: N/A 3: N/A 2: N/A 1: N/A 0: 2Last 24 hours:
23: N/A 22: N/A 21: N/A 20: N/A 19: N/A 18: N/A
17: N/A 16: N/A 15: N/A 14: N/A 13: N/A 12: N/A
11: N/A 10: N/A 9: N/A 8: N/A 7: N/A 6: N/A
5: N/A 4: N/A 3: N/A 2: N/A 1: N/A 0: N/A
Session thrash/ramp-up rate
> get perf session detail
Last 60 seconds:
0: 2 1: 2 2: 3 3: 7 4: 8 5: 7
6: 7 7: 2 8: 4 9: 2 10: 3 11: 9
12: 6 13: 14 14: 12 15: 5 16: 18 17: 6
18: 5 19: 6 20: 2 21: 74 22: 3 23: 8
24: 5 25: 4 26: 4 27: 2 28: 12 29: 5
30: 6 31: 5 32: 3 33: 35 34: 3 35: 5
36: 5 37: 3 38: 3 39: 5 40: 2 41: 3
42: 2 43: 6 44: 3 45: 2 46: 11 47: 4
48: 2 49: 4 50: 2 51: 2 52: 3 53: 13
54: 57 55: 10 56: 9 57: 6 58: 3 59: 5Last 60 minutes:
0: 218 1: 475 2: 403 3: 412 4: 832 5: 439
6: 568 7: 1076 8: 0 9: 0 10: 0 11: 0
12: 0 13: 0 14: 0 15: 0 16: 0 17: 0
18: 0 19: 0 20: 0 21: 0 22: 0 23: 0
24: 0 25: 0 26: 0 27: 0 28: 0 29: 0
30: 0 31: 0 32: 0 33: 0 34: 0 35: 0
36: 0 37: 0 38: 0 39: 0 40: 0 41: 0
42: 0 43: 0 44: 0 45: 0 46: 0 47: 0
48: 0 49: 0 50: 0 51: 0 52: 0 53: 0
54: 0 55: 0 56: 0 57: 0 58: 0 59: 0Last 24 hours:
0: 4423 1: 0 2: 0 3: 0 4: 0 5: 0
6: 0 7: 0 8: 0 9: 0 10: 0 11: 0
12: 0 13: 0 14: 0 15: 0 16: 0 17: 0
18: 0 19: 0 20: 0 21: 0 22: 0 23: 0
Showing VPN SA status
(VPN Security Association Status)
ns5gt-> get sa
total configured sa: 2
HEX ID Gateway Port Algorithm SPI Life:sec kb Sta PID vsys
00000002< aa.bbb.cc.dd 500 esp:3des/sha1 2129eede 3434 unlim A/- 3 0
00000002> aa.bbb.cc.dd 500 esp:3des/sha1 d65705f3 3434 unlim A/- 2 0
00000003< aa.bbb.cc.dd 500 esp:3des/sha1 00000000 expir unlim I/I 5 0
00000003> aa.bbb.cc.dd 500 esp:3des/sha1 00000000 expir unlim I/I 4 0
Each policy has its own SA. So a bidirectional VPN policy, which is really two policies glued together, has two SAs, one for each direction.
In the example above,
aa.bbb.cc.dd is the IP address of the remote gateway.
The Status has two characters. The first is the status of the SA, the second is whether or not VPN Monitoring is enabled on the SA. In the example above, one of the SA pairs is up with no monitoring enabled (indicated with
A/-) and the other is not (indicated with
I/I).