Using CLI Data
This section describes the show and clear commands that are used for troubleshooting.
show subscriber
This section describes the show subscriber commands for the existing subscribers sessions.
Field |
Description |
---|---|
| |
Output modifiers. |
all |
Displays all the existing subscriber sessions. |
supi |
Displays subscriber sessions based on SUPI ID. |
gnodeb-id |
Displays the gnodeb-id of the session. |
clear subscriber
This section describes the clear subscriber commands for the existing subscribers sessions.
Field |
Description |
---|---|
| |
Output modifiers. |
all |
Clears all the subscriber sessions. |
gnodeb-id |
Clears the sessions that have the specified gnodeb-id. |
supi |
Clears the sessions based on the SUPI value. |
Monitor Subscriber
Feature Name |
Release Information |
Description |
---|---|---|
Monitor Subscriber |
2023.04 |
Cisco AMF supports the monsub to capture the N1/N2/N8/N11/N12/N15/N20/N22/N26 interface level messages. Default Setting: Disabled – Configuration Required |
Feature Description
The "Monitor Subscriber" is a debugging and troubleshooting tool which captures the N1/N2/N8/N11/N12/N15/N20/N22/N26 interface level messages. The messages are logged only if SUPI is present or can be found from AMF database.
Configuring the Monitor Subscriber
Following are the various CLI options available for the monitor subscriber.
Option: 1
[amf-ops-center] amf# monitor subscriber supi imsi-123456789012345 capture-duration 200 internal-messages yes
With the preceding CLI option, both internal and external messages are logged for duration of 200 seconds. To explicitly record N1N2 messages, you must configure the 'internal-messages' option with the value "yes."
Option: 2
monitor subscriber supi imsi-123456789012345
With the preceding CLI option, only N26 and rest API messages are logged for a duration of 300 secs (default capture duration).
Option: 3
[amf-ops-center] amf# monitor subscriber supi imsi-123456789012345 capture-duration 50000 transaction-logs yes
logging transaction message enable.
With the preceding CLI option, transaction level messages are logged which are used for internal debugging.
Option: 4
[amf] amf# monitor subscriber supi imsi-123456789012345 capture-duration 3000 internal-messages yes file-name amf
With the preceding CLI option, MonSub file is generated with provided file-name in CLI.
Limitations
Following are the limitations for the monsub:
-
If OAM pod restarts, the previously stored MonSub logs gets deleted.
-
Enabling MonSub for a large number or all subscribers in a production environment impacts the system performance. So, it is recommended to enable the Monsub for few or specific subscribers.
Note |
The CLI option for enabling Monsub with imsi-* is not recommended in loaded system with bulk calls. As mentioned in the preceding section, specific SUPI (example - imsi-1234567890) should be used to capture the message logging with available options. |
Not Supported
The MonSub doesn't support the following.
-
Messages related to Non-UE
-
Monsub CLI (Monitor Subscriber IMSI) and (Monitor Subscriber IMEI)
-
Messages towards Lawful Intercept (LI) interface
-
All the SBI messages towards NRF
-
N2 interface messages like NGSETUP, NGAP_ERROR_INDICATION and NG_RESET