cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
723
Views
7
Helpful
15
Replies

Reducing the required Privilege Level to write to memory

JXGulotta
Level 1
Level 1

Hello all,

I'm currently running a C9300 on 17.03.03 firmware. My security team has an AD RADIUS server that we have programmed into AAA which provides user groups with a privilege level. One of these privilege levels is for junior network admins to make basic changes like switch a vlan on a port, however I've come across an error that they're hitting when trying to write these changes to memory. 

Switch#copy run start
Destination filename [startup-config]?
startup-config file open failed (Permission denied)

Switch#wr mem
startup-config file open failed (Permission denied)

For transparency, here is the full permission 14 list:

privilege interface level 14 power inline
privilege interface level 14 power
privilege interface level 14 shutdown
privilege interface level 14 ip address
privilege interface level 14 ip
privilege interface level 14 switchport
privilege interface level 14 no power inline
privilege interface level 14 no power
privilege interface level 14 no shutdown
privilege interface level 14 no ip address
privilege interface level 14 no ip
privilege interface level 14 no switchport
privilege interface level 14 description
privilege interface level 14 no description
privilege interface level 14 no
privilege configure level 14 interface
privilege exec level 14 write memory
privilege exec level 14 write
privilege exec level 14 configure terminal
privilege exec level 14 configure
privilege exec level 15 reload
privilege exec level 14 test cable-diagnostics tdr interface
privilege exec level 14 test cable-diagnostics tdr
privilege exec level 14 test cable-diagnostics
privilege exec level 14 test
privilege exec level 14 show cable-diagnostics tdr interface
privilege exec level 14 show cable-diagnostics tdr
privilege exec level 14 show cable-diagnostics
privilege exec level 14 show device-tracking database interface
privilege exec level 14 show device-tracking database
privilege exec level 14 show device-tracking
privilege exec level 14 show ip interface
privilege exec level 14 show ip
privilege exec level 14 show running-config
privilege exec level 14 show

Any assistance would be greatly appreciated.

1 Accepted Solution

Accepted Solutions

JXGulotta
Level 1
Level 1

Figured out a solution. Posting here to share with others. The line that was missing was:

file privilege 14

This command lowers the privilege level required to access the file system to 14. Here's hoping someone else in the future finds this useful.

View solution in original post

15 Replies 15

M02@rt37
VIP
VIP

Hello @JXGulotta,

To resolve this, you need to add the write memory privilege at the appropriate level. You have already added privilege exec level 14 write memory, but you need to ensure that the write command also includes the copy running-config startup-config subcommand at the same level.

Switch(config)# privilege exec level 14 copy running-config startup-config
Switch(config)# privilege exec level 14 copy running-config

--Verify that the privilege levels are correctly set:

Switch# show privilege

Best regards
.ı|ı.ı|ı. If This Helps, Please Rate .ı|ı.ı|ı.

JXGulotta
Level 1
Level 1

Hello M02@rt37,

I've confirmed that my test account is at the correct priv level and input the lines you've outlined above, but I'm still getting the same error: startup-config file open failed (Permission denied)

Access via User 

Do 

Show privilege 

It must be 14.

Share output here 

MHM

JXGulotta
Level 1
Level 1

Switch#sh pri
Current privilege level is 14

Did you use any 

Aaa authorization command? 

MHM

aaa new-model
!
!
aaa group server radius servergroup
server name servername
server name servername
!
aaa authentication login default group servergroup local
aaa authentication enable default group servergroup enable
aaa authorization config-commands
aaa authorization exec default group servergroup local
aaa authorization configuration default group servergroup
aaa accounting exec default start-stop group servergroup
!

aaa session-id common

So the command is send aaa to authz it or not 

It not issue of priv it missing or misconfig command of 

Aaa authz config 

Let me check before answer 

But you can help to make sure that this is issue by run debug  aaa authorization 

Thanks 

MHM

Here's the output for the debug command:

Switch#debug aaa authorization
AAA Authorization debugging is on
Switch#

No other output and nothing in the logs.

My other thought is every other command change in the priv list functions when it did not prior to it being added, which would also not work if it were a AAA authz misconfig, correct?

Correct any command you enter will return error

MHM

So since the other commands function properly, is there a different set of permissions with regards to the start config?

I just wanted to follow up on this and see if you any other ideas. I haven't been able to find anything.

JXGulotta
Level 1
Level 1

Figured out a solution. Posting here to share with others. The line that was missing was:

file privilege 14

This command lowers the privilege level required to access the file system to 14. Here's hoping someone else in the future finds this useful.

THANK YOU! This is exactly what I needed.