RADIUS isn't configured for Core LAN Switches

RADIUS isn't configured for dispatch/RF LAN Switches

ASTRO

Domain Controller

HP switch

STEP 1:  ADDING CORE LAN SWITCH TO RADIUS CLIENTS LIST ON DOMAIN CONTROLLER

• Remote into Zone level DC
• Verify core lan switch doesn’t exist in Radius Client list in path below.
• Windows Administrative Tools -> Network Policy Server -> Radius Clients
• Create New -> Add Core LAN Switch Friendly Name, IP, and shared secret (nslookup will help grab details for friendly name)

NOTE: When entering IP make sure to hit Verify -> Resolve -> Ok

NOTE: If you do not know the shared secret right click another radius client -> properties click the generate button, it will display the shared secret in plain text

STEP 2: ENABLING / CONFIGURING RADIUS ON CORE LAN SWITCHES (10.x.233.230 & 10.x.233.228)

• Putty into Core LAN Switches -> type Config <Enter> -> Copy Paste following Commands to enable Radius:

HP Switch Radius Setup Commands;  x= zone & SecretKey = Radius/Shared Secret

aaa authentication ssh login radius local

aaa authentication telnet login radius local

aaa authentication console login radius local

aaa authentication login privilege-mode

radius-server host 10.x.233.166 key <SharedSecretKey>

radius-server host  10.0.0.223 key <SharedSecretKey>

After these commands are entered, open up a new putty session and try to login with astrousr, if successful continue if not then go back to the beginning and confirm the steps taken. If successful type write mem in the cli for the switch then exit config mode.

STEP 3: Configured UNC communication to RADIUS USER rather than the local.

• Find core lan switch -> Right Click -> Properties -> Communication -> Authentication User -> needs to be changed to the configured RADIUS user account (User needs to be configure with a domain account ) then test credentials and make sure its successful
• Pull Config on the core lan switch