RME 4.3.0 compliance Management

[mkruseonline]

Hello,

I try to change UserPort settings with Compliance Management :

Name:

CheckPort

SubMode: Yes     

isPrerequisite: Yes

Ordered : No    

Prerequisite-Commandset : none    

Parent: none

  interface [#.*#]

[#description user_10#]

Name:

Port

SubMode: No     

isPrerequisite: No

Ordered : No    

Prerequisite-Commandset : CheckPort    

Parent: CheckPort

  +   description   test_rme

But it's not working.

Any hint for me ?

regards

Michael

[Joel Monge]

What is it you are trying to do, change to "description test_rme" if an interface currently has "description user_10"?  If so, you are missing:

+ [#description user_10#]

[mkruseonline]

Hi,

yes I want to change the description of each Port.

If the description is "user_10" it has to be changed to "test_rme"

I use this Template, but nothing happens :

Name: CheckPort

SubMode: Yes     

isPrerequisite: Yes

Ordered : No                              

Prerequisite-Commandset : none                              

Parent: none

   interface [#.*#]

   + [#description  user_10#]

Name:

Port

SubMode: No     

isPrerequisite: No

Ordered : No                              

Prerequisite-Commandset : CheckPort                              

Parent: CheckPort

   + description test_rme

regards

Michael

[Joel Monge · Accepted solution]

I just tested this template on my server and I had no problems.  The device originally had:

interface FastEthernet0/1
 description user_10
 no ip address

Ran compliance check and device was non-compliant as these commands needed to be deployed:

+interface FastEthernet0/1

+  description test_rme

Ran deploy of this compliance job and now my device has:

interface FastEthernet0/1
 description test_rme
 no ip address

Now I do not have RME 4.3.0 to test so there might be a problem in the version.  What does the compliance job say as a result, is it correct?  If so, what happens when you deploy the job?  These jobs run against the latest archived configuration in RME, so make sure the current running configuration is stored in RME or you might be getting unexpected results.  You can check latest config under RME > Config Mgmt > Archive Mgmt > Version Tree.

My template:

[mkruseonline]

Hello,

working. Thanks.

Joel Monge schrieb:
 These jobs run against the latest archived configuration in RME, so make sure the current running configuration is stored in RME  or you might be getting unexpected results.  You can check latest  config under RME > Config Mgmt > Archive Mgmt > Version Tree.

That was the reason. We had trouble fetching actual configuration.

regards

Michael