Dell PowerConnect W Clearpass 100 Software Implementing Accounting-Based Autho - Page 20

Check landing Check traffic limit

Page 20 highlights

• Is the correct shared secret configured on both the NAS and the Amigopod RADIUS Server? • Is the guest account authorized? Check that the account is enabled, has the correct role, and that the authorization is not failing. Authorization failures are indicated with a log message in Administrator>System Logs. Check landing page At the landing page, verify that your username is displayed, along with your current usage information and the remaining quota. Verify that clicking the Go to my home page link redirects you to your home page. This indicates that the login has been successful and you are now authorized to use the network. Using the Amigopod WebUI, navigate to Guests>Active Sessions and verify that there is a session listed for your username. Perform some Internet browsing while you wait for the interim accounting interval to elapse (RFC 2869 recommends a minimum interval of 600 seconds, or 10 minutes, however it may be configured to a smaller value to gain tighter control over traffic limits and provide a more up-to-date view of session statistics on the landing page). Verify that the interim accounting update is reflected in both the Active Sessions list, and on the guest's landing page. Log out of the network, and then log back in. Verify that the traffic statistics displayed include the previous session's traffic. Check traffic limit While connected to the guest network, generate enough traffic to exceed the traffic limit. Verify that the session is disconnected via an RFC 3576 Disconnect-Request. An authorization failure message should be logged in the application log (check in Administrator>System Logs), as well as a message related to the session disconnection. Troubleshooting tips: If the session is not disconnected, check the following items: • Is the correct authorization condition configured in the RADIUS user role? • Is the NAS device receiving an RFC 3576 request? • Is the correct shared secret configured on both the NAS and the Amigopod RADIUS Server? 20| Implementing Accounting-Based Authorization Amigopod |Technical Note

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22

20
| Implementing Accounting-Based Authorization
Amigopod
|Technical Note
Is the correct shared secret configured on both the NAS and the Amigopod RADIUS
Server?
Is the guest account authorized?
Check that the account is enabled, has the correct
role, and that the authorization is not failing.
Authorization failures are indicated with
a log message in
Administrator
>
System Logs
.
Check landing page
At the landing page, verify that your username is displayed, along with your current usage
information and the remaining quota.
Verify that clicking the
Go to my home page
link redirects you to your home page. This
indicates that the login has been successful and you are now authorized to use the
network.
Using the Amigopod WebUI, navigate to
Guests
>
Active Sessions
and verify that there is
a session listed for your username.
Perform some Internet browsing while you wait for the interim accounting interval to
elapse (RFC 2869 recommends a minimum interval of 600 seconds, or 10 minutes, however
it may be configured to a smaller value to gain tighter control over traffic limits and
provide a more up-to-date view of session statistics on the landing page).
Verify that the
interim accounting update is reflected in both the Active Sessions list, and on the guest’s
landing page.
Log out of the network, and then log back in.
Verify that the traffic statistics displayed
include the previous session’s traffic.
Check traffic limit
While connected to the guest network, generate enough traffic to exceed the traffic limit.
Verify that the session is disconnected via an RFC 3576 Disconnect-Request. An
authorization failure message should be logged in the application log (check in
Administrator
>
System Logs
), as well as a message related to the session disconnection.
Troubleshooting tips:
If the session is not disconnected, check the following items:
Is the correct authorization condition configured in the RADIUS user role?
Is the NAS device receiving an RFC 3576 request?
Is the correct shared secret configured on both the NAS and the Amigopod RADIUS
Server?