Palo Alto College**We aren't endorsed by this school
Course
BIOL 123
Subject
Computer Science
Date
Dec 18, 2024
Pages
17
Uploaded by misagova
urses 1 2.1 - RADI US DEVice ISE 301 for Field Engineers Admin Support 12.1 - RADIUS Device Admin Support v Done: View Attempt: 1 You have earned 0 point(s) out of 0 point(s) thus far. 1. First, we need to create a User Identity Group for Switch Admins. On ""' npel D. navigate to Administration > Identity Management > Groups.
4. Name the Identity Group STARK_DEVICE_ADMINS . Then click the Submit button. User Identity Groups > New User Identity Group Identity Group Submit 5. Next, create a user account in ISE. Navigate to Administration > Identity Management > Identities. 6. Click the + Add button. Network Access Users 7. Configure the Network Access User with the following values and then click Submit. o Name: netadmin o On the Login Password line, enter C1sco12345 for the Password and Re- Enter Password fields. o User Groups: STARK_DEVICE_ADMINS
G 8. Next, create a new Network Device Group (NDG) to represent devices to be managed with RADIUS. This could act as a parent group for other device groups. Navigate to Administration > Network Resources > Network Device Groups. 9. Click + Add. Network Device Groups 10. Name the Group Routers and select All Device Types as the Parent Group. Then click Save. -
* All Device Typesx 11. Next, let's add a new network device to utilize Device Admin. Navigate to Administration > Network Resources > Network Devices. 13. Configure a new network device. Then scroll down and Save. o Name: BRRTR o IP Address: 198.18.133.101 /32 o Device Type: Routers o RADIUS Authentication Settings: Checked o Shared Secret: C1sco12345
14. We need to create a new condition to use in our policy. Navigate to Policy > Policy Elements > Conditions. 15. In the Editor, Click to add an attribute, and select the Radius Dictionary from the dropdown, then select NAS-Port-Type attribute. 16. Select Virtual for the Attribute value. [
18. Select attribute for condition, and select the Radius Dictionary from the dropdown, then select Service-Type attribute.
20. We need to add yet another final condition. Click New. Click to add an attribute, and select the DEVICE Dictionary from the dropdown, then select Device Type attribute. 111 O L ii 21. Set it to Equals and then All Device Types#Routers. Finally, Save your condition. 22. Save the new Library Condition as STARK_RADIUS_DEVICE_ADMIN. Then click the Save button.
27. Expand Authorization Policy and Add a new rule by clicking the + button. \vAuthorization Policy(1) 28. Rename the rule Router Consoles, then click on + to add Conditions. | tomoomiw 4 29. In the Editor, click the Click to add an attribute field. Select the DEVICE icon the Dictionary dropdown, then click Device Type. DOED0 - DRODDoon ‘H‘ I R E — 30. Set it Equals to All Device Types#Routers. Then, add another condition by clicking New. 31. Click to add an attribute. Select the IdentityGroup icon, then click InternalUser:ldentityGroup : R - . hjflfl\ « IEICIEEIEIEIRIRICIEEE
32. Set it Equals to User Identity Groups:STARK_DEVICE_ADMINS.Then scroll down and click Use. 34. Open a PuTTY SSH connection to BRRTR. Login as admin : C1sc012345. #R PuTTY Configuration Category: () Session - Logging - Terminal - Keyboard ? Basic options for your PuTTY session Specify the destination you want to connect to X Host Name (or IP address) Port [198.18.133.101 |[23 Connection type: OSSH (Serial @ Other: | Telnet v
N s122 12.1- BRRTR RADIUS Device Admin Config ~ [Gw 39. Return to your PuTTY session to paste the configuration into BRRTR. BRRTR#configure terminal nter configuration commands, one per line. End with CNTL/Z. RRTR (config) #radius server ISE BRRTR (config-radius-server) faddress ipv4 198.19.10.13 RRTR (config-radius-server) $key Clscol2345 BRRTR (config-radius-server) §timeout 60 RRTR (config-radius-server) fexit BRRTR (config) #aaa authentication login ISE-RADIUS group radius local RRTR (config) #line vty 1 4 BRRTR (config-line) #login authentication ISE-RADIUS BRRTR (config-line) #end BRRTR#write memory Building configuration.. [OK) RRTR#] v D We are specifying VTY lines 1-4 so that the first session (line 0) continues to use local authentication to avoid potential lockouts in our lab. 40. To test our configuration, keep the current PuTTY client session open and connected to the router. Configure a new PuTTY session by right-clicking on the PUTTY icon and selecting Duplicate Session. Restore DIUS group radius local Move Size | - Minimize o Maximize x Close Alt+F4 Special Command > Event Log New Session... Duplicate Session Saved Sessions > Change Settings... Copy All to Clipboard Clear Scrollback Reset Terminal Full Screen
45. Iser |dentity Groups:STARK_DEVICE_ADMIN: PAP_ASCII Notice the Authentication Method and Protocol are PAP_ASCII. Either of these could also be used as a matching condition for RADIUS Device Admin with devices that use PAP_ASCII as a password authentication protocol. Also notice the Service Type and NAS Port Type values match as set in the Policy Set match condition. This also presents an opportunity to maximize efficiency of protocol processing. Rather than using the Default Network Access Protocols for the Policy Set, which allows Process Host Lookup, EAP-MD5, PEAP, and other protocols including PAP/ASCII, you could create a custom Allowed Protocols that just allows PAP/ASCII. Another item to notice here is that this session selected Internal Users, All_AD_Join_Points, and Guest Users as identity sources to check as shown below.