RME Netconfig Jobs

Answered Question
Nov 20th, 2009

I'm looking to deply "no mop enabled" and "no lat enabled" via Netconfig to some of our device interfaces.


Is the option "port based" the right option to choose since this an interface level command?



I chose 100 mbps Ethernet, 1 Gbps Ethernet port, and links ports

Correct Answer by Joe Clarke about 7 years 3 months ago

There is not.  You will have to schedule compliance jobs.  However, you can schedule a compliance check job to run automatically, and you can choose to run it on a dynamic group of devices.  So, essentially, RME can scan newly added devices, but it just won't happen as they are added.

Correct Answer by Joe Clarke about 7 years 3 months ago

Yep, provided the name of the interfaces contained the word, "Serial".

Correct Answer by Joe Clarke about 7 years 3 months ago

In Netconfig, create a new Netconfig job, and select Device based from the first screen.  Then you can use the Ad hoc template to fill out the necessary parameters.

Correct Answer by Joe Clarke about 7 years 3 months ago

No, the option will be device-based as port-based is only applicable for switch ports, not router interfaces.  If there are only specific interfaces to which these commands should be deployed, create a device-based template, and specify the interfaces and the commands.  If, however, you want to deploy the commands to a whole class of interfaces, it would be easier to use the baseline compliance feature of RME.  Using this, you can create a template with a submode such as:


interface [#.*Ethernet.*#]


Then under that submode, add:


+ no mop enable

+ no lat enable

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Correct Answer
Joe Clarke Fri, 11/20/2009 - 10:05

No, the option will be device-based as port-based is only applicable for switch ports, not router interfaces.  If there are only specific interfaces to which these commands should be deployed, create a device-based template, and specify the interfaces and the commands.  If, however, you want to deploy the commands to a whole class of interfaces, it would be easier to use the baseline compliance feature of RME.  Using this, you can create a template with a submode such as:


interface [#.*Ethernet.*#]


Then under that submode, add:


+ no mop enable

+ no lat enable

dionjiles Fri, 11/20/2009 - 10:08

Okay I guess I was reading the documentation wrong.....let me get a template created since this is going out to router interfaces.

Correct Answer
Joe Clarke Fri, 11/20/2009 - 10:33

In Netconfig, create a new Netconfig job, and select Device based from the first screen.  Then you can use the Ad hoc template to fill out the necessary parameters.

dionjiles Mon, 11/23/2009 - 11:37

If I wanted to do Serial interfaces would this syntax work?



interface [#.*Serial.*#]


Then under that submode, add:


+ no mop enable

+ no lat enable

Correct Answer
Joe Clarke Mon, 11/23/2009 - 11:50

Yep, provided the name of the interfaces contained the word, "Serial".

dionjiles Mon, 11/23/2009 - 12:14

Wow I have been really scared to use RME compliance manager until now.....this makes life so much easier.


I wish they was a way when devices get add that Compliance manager would check the device, it could be I haven't

had the chance to really read up on it.

Correct Answer
Joe Clarke Mon, 11/23/2009 - 12:16

There is not.  You will have to schedule compliance jobs.  However, you can schedule a compliance check job to run automatically, and you can choose to run it on a dynamic group of devices.  So, essentially, RME can scan newly added devices, but it just won't happen as they are added.

Joe Clarke Mon, 11/23/2009 - 12:35

No, I don't think so.  Definitely more is going into compliance management in 4.0, but I haven't seen a trigger-based compliance check yet.

Actions

This Discussion