NetConfig: Non Applicable Devices

Unanswered Question
Jul 22nd, 2009

Is it expected behavior by NetConfig that if an "Unrecognized command" is configured in a config-mode job, the devices will be listed as "Non Applicable Devices"? The only device that got passed is currently unreachable. Is that unreachability why NetConfig lets it through, since it cannot verify the validity of the command on it?

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
yjdabear Wed, 07/22/2009 - 10:02

It's known to RME, a 3845 running 12.4(8a). The config being executed is "test", which is unrecognized on all the Non Applicable Devices, all 6500s running 12.2(18)SXF14 in native mode.

Joe Clarke Wed, 07/22/2009 - 11:18

Actually, I assume you created a custom task in Netconfig, and tied it to the Routers group only. Therefore, the 3800 will be supported, but the 6500s (Switches and Hubs) will not be applicable.

yjdabear Wed, 07/22/2009 - 11:41

Pardon my confusion. Is it due to the IOS version differences? The config is an Adhoc one-liner. AFAIK, the user did not tie it to the Router group".

Joe Clarke Wed, 07/22/2009 - 11:50

I don't see how what you describe is possible, then. If this is truly an ad hoc job, then all devices should be applicable. The command is not taken into account.

yjdabear Wed, 07/22/2009 - 12:28

The 6500s have been recently converted from CatOS to IOS. Each had gone through a Conflicting Device stage, which required having RME update DCR with the new sysID OID. It almost appears as if NetConfig is failing to recognize these as valid IOS devices, despite RME realizing it elsewhere.

Joe Clarke Wed, 07/22/2009 - 12:30

I don't understand exactly what you're doing/seeing. I certainly cannot reproduce. Post screenshots illustrating exactly what workflow you're using in NetConfig to arrive at the problem you describe.

Actions

This Discussion