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

    Monitoring AAA Metrics

    AAA server metrics include:

    • Server Up/Down status traps
    • Network element status traps
    • Real-time latency and flow control statistics

    RADIUS logs are useful for troubleshooting an AAA profile. The following sections show logs for create, update, delete, and dynamic requests.

    Create Session requests communicate with the S-GW, the P-GW, and the RADIUS server in the following manner:

    S-GW --> Create Session request --> P-GW --> Access Request --> RADIUSP-GW <-- Access Accept <-- RADIUSP-GW --> Accounting Start request ->> RADIUSS-GW <-- Create Session response <-- P-GWP-GW <-- Accounting Start response <-- RADIUSS-GW <-- Create Session response <-- P-GW

    If apn wait-accounting is enabled (it is disabled by default), then the P-GW sends the Create Session response after receiving the Accounting Start response.

    The following RADIUS logs show how these Create Session requests are processed. When there is a breakdown in AAA communications, the logs help you isolate the cause of the problem.

    1. Access the RADIUS log, enable trace options, and look for Authentication and Accounting messages.
      Jun 24 11:50:19 1001025 gtid:[26]tid: [2] jsimRadius(2) Access-Request IP 10.10.2.11 20024 >...Jun 24 11:50:19 1013620 gtid:[24]tid: [0] Access-Accept...Jun 24 11:50:19 1022764 gtid:[25]tid: [1] jsimRadius(1) Accounting-Request IP 10.10.2.11 20025 >...Jun 24 11:50:19 1033840 gtid:[26]tid: [2] Accounting-Response

    Interim requests can be configured to generate accounting requests periodically or they are generated when the S-GW generates a Modify bearer Request. When a Modify bearer Request is received, communication with the S-GW, P-GW, and RADIUS server flows in the following manner:

    S-GW --> Modify bearer request --> P-GW P-GW --> Interim request --> RADIUSP-GW <-- Dynamic request <-- RADIUSP-GW <-- CoA <-- RADIUSS-GW <-- Update bearer request <-- P-GWS-GW --> Update bearer response --> P-GWP-GW ---> CoA ACK --> RADIUSP-GW ---> Interim accounting response --> RADIUS

    Note: Modify bearer requests are generated by subscriber location information changes, QoS changes, roaming, time-zone changes, and so on.

    The following RADIUS logs show how these interim Accounting messages are processed. When there is a breakdown in AAA communications, the logs help you isolate the cause of the problem.

    1. Access the RADIUS log, enable trace options, and look for Authentication and Accounting messages.
      Jun 24 11:58:28 879452 gtid:[25]tid: [1] Accounting-Request...Jun 24 11:58:28 880542 gtid:[25]tid: [1] Acct-Status-Type [40] 4 0000 0003...Jun 24 11:58:28 880818 gtid:[25]tid: [1] Acct-Input-Octets [42] 4 0000 00064 <— Data flow...Jun 24 11:58:28 880849 gtid:[25]tid: [1] Acct-Output-Octets [43] 4 0000 00064 <— Data flow...Jun 24 11:58:28 891299 gtid:[25]tid: [1] Accounting-Response

    Accounting stop (delete) requests communicate with the S-GW, the P-GW, and the RADIUS server in the following manner:

    S-GW --> Delete Session request --> P-GWP-GW --> Accounting Stop request --> RADIUSS-GW <-- Delete Session response <-- P-GWS-GW <-- Delete Session request <-- P-GWP-GW --> Accounting Sstop --> RADIUS

    For a dynamic stop request, the flow is:

    P-GW <-- Disconnect request <-- RADIUSS-GW <-- Delete Session request <-- P-GWP-GW --> Accounting Stop --> RADIUS

    The following RADIUS logs show how these Delete Accounting messages are processed. When there is a breakdown in AAA communications, the logs help you isolate the cause of the problem.

    1. Access the RADIUS log, enable trace options, and look for Accounting Stop messages.
      Jun 24 12:06:29 957706 gtid:[25]tid: [1] jsimRadius(1) Accounting-Request IP 10.10.2.11 20025 >...Jun 24 12:06:29 958502 gtid:[25]tid: [1] Acct-Status-Type [40] 4 0000 0002...Jun 24 12:06:29 958785 gtid:[25]tid: [1] Acct-Input-Octets [42] 4 0000 00c8 <— Data flow...Jun 24 12:06:29 958815 gtid:[25]tid: [1] Acct-Output-Octets [43] 4 0000 00c8 <— Data flow...Jun 24 12:06:29 974810 gtid:[26]tid: [2] Accounting-Response

    Note: In the displays in this section, acct-status-type ends with a four-digit code. The last number of this code is meaningful. A code that ends in 0001 means the process is starting. A code that ends in 0002 means the process is stopping. A code that ends in 0003 means the process is in an interim state, which allows parameters to be changed.

    The following aggregate show commands are useful for troubleshooting AAA processes.

    • To show AAA statistics authentication details for a specific interface:
      user@host> show unifed-edge ggsn-pgw aaa statistics authentication detail fpc-slot 3 pic-slot 0
    • To show AAA statistics accounting details for a specific interface:
      user@host> show unifed-edge ggsn-pgw aaa statistics accounting detail fpc-slot 3 pic-slot 0
    • To show AAA statistics authentication details for a specific PIC:
      user@host> show unifed-edge ggsn-pgw aaa statistics authentication detail
    • To show AAA statistics accounting details for a specific PIC:
      user@host> show unifed-edge ggsn-pgw aaa statistics accounting detail
    • To show AAA statistics accounting details for a specific RADIUS server interface:
      user@host> show unifed-edge ggsn-pgw aaa statistics radius authentication detail fpc-slot 3 pic-slot 0 name jsimRadius
    • To show AAA statistics accounting details for a specific RADIUS server interface:
      user@host> show unifed-edge ggsn-pgw aaa radius statistics accounting detail fpc-slot 3 pic-slot 0 name jsimRadius
    • To show network element status lists of the RADIUS servers and their status:
      user@host> show unified-edge ggsn-pgw aaa network-element status name ne1 fpc-slot 3 pic-slot 0
      Network-element: ne1   
        Server: radius1, Priority: 1, State: Active  
        Server: radius2, Priority: 1, State: Active
        Server: radius3, Priority: 2, State: Active

    The following clear commands are useful for detecting ongoing activity:

    • To clear AAA authentication statistics:
      user@host> clear unifed-edge ggsn-pgw aaa statistics authentication
    • To clear AAA accounting statistics:
      user@host> clear unifed-edge ggsn-pgw aaa statistics accounting
    • To clear RADIUS server authentication statistics:
      user@host> clear unifed-edge ggsn-pgw aaa radius statistics authentication
    • To clear RADIUS server accounting statistics:
      user@host> clear unifed-edge ggsn-pgw aaa radius statistics accounting

    The following test commands are useful for debugging problems:

    • To test user authentication:
      user@host> test unified-edge ggsn-pgw aaa authentication fpc-slot 1 pic-slot 0 profile abc charging-id 0xffffff username aaa password aaa
    • To start an accounting test:
      user@host> test unified-edge ggsn-pgw aaa accounting fpc-slot 1 pic-slot 0 profile abc charging-id 0xffffff start
    • To stop the accounting test:
      user@host> test unified-edge ggsn-pgw aaa accounting fpc-slot 1 pic-slot 0 profile abc charging-id 0xffffff stop
    • To test the interim interval configuration:
      user@host>test unified-edge ggsn-pgw aaa accounting fpc-slot 1 pic-slot 0 profile abc charging-id 0xffffff interim

    Published: 2011-11-16