Monitoring the Subscriber

Use the following CLI command to monitor the subscriber in the SMF.

monitor subscriber supi supi_id [ capture-duration duration_sec |  internal-messages { yes } | transaction-logs { yes } ] 

NOTES:

  • supi supi_id : Specifies the subscriber identifier. For example, imsi-123456789, imsi-123*

  • capture-duration duration_sec : Specifies the duration in seconds during which the monitor subscriber is enabled. The default is 300 seconds (5 minutes).

  • internal-messages { yes } : Enables internal messages. By default, internal messages are disabled.

  • transaction-logs { yes } : Enables transaction logs. By default, transaction logs are disabled.

The monitor subscriber CLI command can be run simultaneously on multiple terminals. For example, run the CLI simultaneously in two SMF Ops Center terminals for two subscribers (for example, imsi-123456789012345 and imsi-456780123456789) to implement the following:

  • Monitor the duration when the monitor subscriber is enabled.

  • View internal messages for the specified subscriber.

  • View transaction logs for the specified subscriber

Terminal 1: The following command monitors and displays subscriber messages for the specified subscriber.

monitor subscriber supi imsi-123456789012345 capture-duration 1000 internal-messages yes

Terminal 2: The following command monitors and displays transaction logs for the specified subscriber.

monitor subscriber supi imsi-456780123456789 capture-duration 500 internal-messages yes transaction-logs yes

After the capture-duration is over or to stop the CLI, use the Ctrl+C keys. The captured messages are reordered and stored in a file. To retrieve the list of stored files, use the monitor subscriber list CLI command.

For example:

monitor subscriber list
RELEASE_NAMESPACE: 'smf'
'monsublogs/subscriberID_imsi-*_AT_2019-10-22T09:19:05.586237087.txt.sorted'
monsublogs/subscriberID_imsi-123456789012345_AT_2019-10-22T09:20:11.122225534.txt.sorted