[c-nsp] no mop enabled

[Jared Mauch]

On Mon, Jun 25, 2007 at 07:30:25AM -0700, Curtis Doty wrote:
> Exactly. And especially on 12.4T+ trains, Cisco please make it go away by 
> default. Barring that, at least flip the show *conf logic:

	So a few comments, since nobody from cisco is here
chiming in:

	1) Cisco is not supposed to enable "new" features by default.  If
you catch them doing this, (be it in CEV, Beta, EFT), yell at them.

	2) Any new stuff should nvgen the 'default' state, so if it's
something that is enabled by default (and new) it should be there.  eg:
if you have a platform that now has lldp functionality and it's on, it
should nvgen that fact.  If it does not, it is a bug.  TAC should file
that bug.

	3) Rumor is that folks doing SOX compliance and auditing (UGH!)
are finally pushing cisco to get a "sh run full" or similar (FINALLY!).
I'd heard about some projects in the past to work on this, but it seems
to be finally happening.

	YMMV, Caveat Emptor, etc...

	Overall, yes, the 'mop' thing is obnoxious, but i assume
you know how to use the interface range command (if you are not using
some sort of provisioning tool that adds your favorite templated interface
magic).

	here's an example from one of my routers:

interface GooBar0/0
 no ip redirects
 no ip proxy-arp
 ip route-cache same-interface
 logging event link-status
 load-interval 30
 no mop enabled
end


-- 
Jared Mauch  | pgp key available via finger from jared at puck.nether.net
clue++;      | http://puck.nether.net/~jared/  My statements are only mine.