Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    show unified-edge ggsn-pgw charging local-persistent-storage statistics

    Syntax

    show unified-edge ggsn-pgw charging local-persistent-storage statistics

    Release Information

    Command introduced in Junos OS Mobility Release 11.2W.

    Description

    Displays the storage statistics of the Charging Data Record (CDR) files on the local Routing Engine disk.

    Required Privilege Level

    view

    List of Sample Output

    show unified-edge ggsn-pgw charging local-persistent-storage statistics

    Output Fields

    Table 1 lists the output fields for the show unified-edge ggsn-pgw charging local-persistent-storage statistics command. Output fields are listed in the approximate order in which they appear.

    Table 1: show unified-edge ggsn-pgw charging local-persistent-storage statistics Output Fields

    Field Name

    Field Description

    Batch Messages received

    The CDRs generated in services PICs are sent to the local Routing Engine disk as batch messages. This counter represents the total number of batch messages sent from services PICs to the Routing Engine disk.

    Batch Responses sent

    The total number of responses sent to the batch messages received.

    Invalid Messages received

    The total number of invalid batch messages sent from services PICs to the Routing Engine disk.

    Number of temp log files opened

    The total number of temporary CDR files opened on the Routing Engine disk.

    These files are closed and copied from the temporary location to a final location (/opt/mobility/charging/ggsn/final_log) within the same Routing Engine disk, from where these can be transferred by SFTP. A file is closed when the file size, file age, or the maximum number of CDRs added to the file reaches the configured limit (or the default limit, when no limit is configured separately).

    Number of journal files opened

    Journaling logs the file-write information into the temporary log CDR files. This sanitizes and truncates the temporary log CDR files when the charging daemon comes up after a crash or reboot, in case of inconsistency. For each temporary log CDR file, a separate journal file is opened. This counter indicates the total number of opened journal files.

    Number of journal files closed

    This counter indicates the total number of closed journal files.

    Number of CDR log files closed

    The total number of closed CDR files.

    Authorized users can use SFTP to transfer these files from the /opt/mobility/charging/ggsn/final_log location.

    Number of CDR files closed due to file-age

    The total number of CDR files closed due to the age of the files reaching the configured limit (or the default limit, when no limit is configured separately).

    The default value for the file age is 120 minutes.

    Number of CDR files closed due to file-size

    The total number of CDR files closed due to the size of the files reaching the configured limit (or the default limit, when no limit is configured separately).

    The default file size is 10 MB.

    Number of CDR files closed due to cdr-count

    The total number of CDR files closed due to the maximum number of CDRs added to the files reaching the configured limit.

    There is no default limit.

    Abnormal file closures

    This counter is incremented when the temporary log CDR file closures are triggered as the charging daemon comes up after a system reboot or crash.

    Normal file closures

    This counter is incremented when the temporary log CDR file closures are triggered due to changes in the configuration, such as a file format change.

    Number of CDR log files closed in TS_32_297 format

    The total number of closed CDR files that are compliant with the format specified in the 32297 technical specification release.

    Number of CDR log files closed in raw asn1 format

    The total number of closed CDR files that are in the raw ASN1 format.

    Total number of CDRs backed up

    The total number of CDRs that have been backed up to the standby Routing Engine.

    Disk Full messages sent

    The total number of messages sent by the Routing Engine to the services PICs to indicate that its disk is full and is unable to accept any more charging data.

    You may want to use SFTP to transfer the files from the /opt/mobility/charging/ggsn/final_log location to free the disk space, or remove the disk and copy the files.

    You can remove the disk by issuing the following commands in this order:

    • request system storage unified-edge charging media stop
    • request system storage unified-edge media eject

    Disk Full resolve messages sent

    When the disk space is freed, the Routing Engine sends messages to the services PICs indicating that it can now receive charging data. This counter indicates the total number of these messages sent.

    Disk Offline messages sent

    The total number of messages sent by the Routing Engine to the services PICs to indicate that its disk is offline or is not mounted, and is unable to accept any more charging data.

    You may want to configure the disk (storage media) to store charging data by issuing these commands:

    • request system storage unified-edge media prepare
    • request system storage unified-edge charging media start

    Disk Available messages sent

    When the disk is prepared and mounted, the Routing Engine sends messages to the services PICs to indicate that it can now receive charging data. This counter indicates the total number of these messages sent.

    Number of async IO reqs written

    This counter is incremented once for every write operation into the temporary log CDR file.

    Number of CDR storage files on disk

    The total number of CDR files stored on the local Routing Engine disk.

    Disk space status

    Indicates whether disk space is available for storage. The possible values are:

    • DISK_AVAILABLE
    • DISK_AT_WATERMARK_LEVEL1
    • DISK_AT_WATERMARK_LEVEL2
    • DISK_AT_WATERMARK_LEVEL3
    • DISK_OFFLINE—Indicates a disk is not present or the request system storage unified-edge charging media stop command has been issued.
    • DISK_OFFLINE_PENDING—Indicates whether any CDRs are being written or mirrored on the backup Routing Engine. This interim status message displays after the request system storage unified-edge charging media stop command has been issued but before the disk goes offline.

    Current storage space in use (MB)

    The storage space, in MB, that is currently being used.

    Available storage space on disk (MB)

    The total free space available for storage on the disk, in MB.

    Total storage space on disk (MB)

    The total storage space on the disk, in MB.

    Watermark level1 at (MB)

    Indicates the percentage of the total Routing Engine disk space configured for storage. By default, watermark level 1 is set to 70 percent of the total disk space.

    When this limit is reached, an alert (if configured) is issued and you can take corrective measures to free the disk space.

    Watermark level2 at (MB)

    Indicates the percentage of the total Routing Engine disk space configured for storage. By default, watermark level 2 is set to 80 percent of the total disk space.

    When this limit is reached, an alert (if configured) is issued and you can take corrective measures to free the disk space.

    Watermark level3 at (MB)

    Indicates the percentage of the total Routing Engine disk space configured for storage. By default, watermark level 3 is set to 90 percent of the total disk space.

    When this limit is reached, an alert (if configured) is issued and you can take corrective measures to free the disk space. If an alert is not configured, the services PICs stop sending the charging data to the Routing Engine disk and you must use SFTP to transfer the files to free the disk space. However, this data is not lost because it is buffered in the services PICs. The services PICs can buffer up to a maximum of 2 GB of data, after which a Call Admission Control (CAC) is triggered.

    The output contains the following information for the temporary CDR files on the router.

    File Name

    Name of the temporary CDR file.

    Journal file name

    Name of the journal file associated with the temporary CDR file.

    Current number of CDRs

    The total number of CDRs that have been currently added to the temporary CDR file.

    Current file size(bytes)

    The current size of the temporary CDR file, in bytes.

    File age trigger(mins)

    The duration after which the temporary CDR file is closed, in minutes. The output shows the configured value or the default value, if none is configured.

    File size trigger(bytes)

    The size the temporary CDR file can reach, in bytes, after which it is closed. The output shows the configured value or the default value, if none is configured.

    CDR count trigger 

    The maximum number of CDRs that can be added to the temporary CDR file, after which it is closed. The output shows the configured value or the default value, if none is configured.

    Sample Output

    show unified-edge ggsn-pgw charging local-persistent-storage statistics

    user@host> show unified-edge ggsn-pgw charging local-persistent-storage statistics
    Charging local-persistent-storage Statistics
      Batch Messages received                             : 2
      Batch Responses sent                                : 2
      Invalid Messages received                           : 0 
      Number of temp log files opened                     : 1 
      Number of journal files opened                      : 1 
      Number of journal files closed                      : 0 
      Number of CDR log files closed                      : 0 
      Number of CDR files closed due to file-age          : 0 
      Number of CDR files closed due to file-size         : 0 
      Number of CDR files closed due to cdr-count         : 0 
      Abnormal file closures                              : 0 
      Normal file closures                                : 0 
      Number of CDR log files closed in TS_32_297 format  : 0 
      Number of CDR log files closed in raw asn1 format   : 0 
      Total number of CDRs backed up                      : 2 
      Disk Full messages sent                             : 0
      Disk Full resolve messages sent                     : 0
      Disk Offline messages sent                          : 0
      Disk Available messages sent                        : 1
      Number of async IO reqs written                     : 2
      Number of CDR storage files on disk                 : 539 
      Disk space status                                   : DISK_AVAILABLE 
      Current storage space in use(MB)                    : 11557 
      Available storage space on disk(MB)                 : 22990 
      Total storage space on disk(MB)                     : 34547 
      Watermark level1 at(MB)                             : 13818(40%)
      Watermark level2 at(MB)                             : 27637(80%)
      Watermark level3 at(MB)                             : 31092(90%)
      
    Temporary CDR log file Statistics
    File Name: /opt/mobility/charging/ggsn/temp_log/templog_file_1.log
        Journal file name          : /opt/mobility/charging/ggsn/jrnl/jrnl_1.log 
        Current number of CDRs     : 2 
        Current file size(bytes)   : 652    
        File age trigger(mins)     : 120    
        File size trigger(bytes)   : 1048576 
        CDR count trigger          : 5000 

    Published: 2011-11-16