Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Problems with parser view

Hello.

I configured a parser view to block some commands(configure line, configure username and configure dial-peer cor) for a specific user.

The parser view is working fine untill I perform a "copy run start" or "write memory" and I reboot my router : the parser view is modified and the "blocked" commands are available for all the users...

The IOS I used is the following : c3900-universalk9-mz.SPA.152-1.T1.bin

The parser view I configured is the following :

parser view BLOCKED

secret 5 XXXXXXXXXXXXX

commands configure include-exclusive line

commands configure include-exclusive dial-peer cor

commands configure include-exclusive username

!

While doing a "sh run | sec parser view", I receive the following :

parser view BLOCKED

secret 5 XXXXXXXXXXXXX

commands configure include-exclusive help line

commands configure include-exclusive help dial-peer cor

commands configure include help dial-peer

commands configure include-exclusive help username

!

If I do a copy run start and a reload, after the reboot, the configuration of the parser view is abnormally modified as follow : 

parser view BLOCKED

secret 5 XXXXXXXXXXXXX

commands configure include help help

commands exec include help

commands exec include terminal help

!

I also tried to configure another parser view for my restricted user, with 'commands configure exclude' for line, username and dial-peer cor...

The parser view for restricted user is also working fine untill I save the configuration in nvram and I do a reboot... After the reboot, I encounter the same problem...

I'm not sure if there is a bug in the IOS or if I made a mistake while configuring my parser view... Could somebody help me ?

For information, I also try to use the IOS 15.1(3)T and I had the same problem...

Thx,

H

558
Views
0
Helpful
0
Replies
CreatePlease login to create content