Review: Agere ORiNOCO AS-2000, part 2 - Page 3

By Lisa Phifer | Posted Sep 6, 2001
Page 3 of 3   |  Back to Page 1
Print ArticleEmail Article
  • Share on Facebook
  • Share on Twitter
  • Share on LinkedIn

RADIUS Authentication
Click for full sized image Because the AS-2000 relies on RADIUS for authentication, RADIUS parameters must be configured, no matter which address assignment type is used (left). Two sets of parameters are required: a primary authentication server and a primary accounting server. Backup servers can also be configured.

Each RADIUS server is identified by IP address, destination port, and shared secret. These values must match those defined on your RADIUS serverin our case, the Interlink AAA Engine. The RADIUS Statistics button displays counters that are useful in diagnosing connectivity problems.

For example, if an AS Client cannot connect, check the Access Request counter. If this counter is not incrementing, the problem lies between the client and the AS-2000. Otherwise, check the Access Retransmissions counterthis signals connectivity or access issues between the AS-2000 and the RADIUS server. Otherwise, check the Access Rejects counterthis signals authentication failure, such as when the user supplied bad credentials.

We had no real issues integrating the AS-2000 with the Interlink AAA Engine. A bad route caused early retransmissionsthis is where traceroute would have been handy in the AS-2000. We also configured the AAA Engine to ignore an unencapsulated vendor-specific attribute (MAC address) supplied by the AS-2000. After this, it was smooth sailing.

--
In Part 3, we will cover monitoring.

Comment and Contribute
(Maximum characters: 1200). You have
characters left.
Get the Latest Scoop with Enterprise Networking Planet Newsletter