To find if the program image on the system you are running facilitates MOP, enter
the display subsys | include mop CLI control. If the platform facilitates MOP, it shall display a range with mop Protocol , as demonstrated in the next example:

        Router#display subsys | include mop
   mop Protocol 1.000.001
   Router#

If these devices doesn’t support MOP, it’ll return absolutely nothing as shown in the next example:

        Router#display subsys | include mop
   Router#

In case a platform doesn’t assistance MOP, then your commands to disable MOP won’t be visible in the command help and you may get an error in the event that you make an effort to configure it, as shown in the next examples:

     Router(config)#interface gigabitEthernet 1 
Router(config-if)#no mop ? 
% Unrecognized command 
Router(config-if)#simply no mop enable 
                      ^ 
% Invalid insight detected at '^' marker.
Router(config-if)#

      Step two 2: Determine If the Platform is Working MOP          

For those who have confirmed that the systems supports MOP, utilize the display procedures | include
MOP CLI command to observe if the MOP procedure is in fact running on these devices. If the system has MOP allowed (either automagically or by way of a configuration), it will display the MOP Protocols in the result, as proven in the next example:

     Router#display processes | include MOP
208 Mwe 5632C4164FCE 7 66 10622408/24000 0 MOP Protocols
Router#

If these devices isn’t running MOP, it’ll return absolutely nothing as shown in the next example:

        Router#display processes | include MOP
   Router#

The system shall accept MOP RC classes only if it really is running MOP.

Managing MOP RC Periods on the VTY Outlines

After we have determined that the picture facilitates MOP and that the MOP procedure is running, just how do we manage MOP access and utilization? The next question came through to the external forum, also it was described in the initial blog: How come MOP RC traffic actually accepted once the VTY outlines had been configured with transport insight ssh , that ought to drop all administration protocols apart from SSH on the VTY lines, particularly when transportation input does are the keyword choice of mop?

The solution is that it is a bug and contains been addressed with Cisco Bug ID CSCwa57951. The !x will be contained in Cisco IOS XE Software program releases 17.9(1) and later. Once you put into action the !x, should you choose have the recommended construction of transport insight on the VTY ranges ssh, even though MOP is running after that, no connections that make use of MOP RC will be permitted.

      Take note:           MOP RC sessions still are at the mercy of whatever authentication options are usually configured on the VTY outlines.
 

As of this true point you might ask, “Hang on… isn’t right now there a worldwide command to simply disable MOP? Something such as the no cdp operate command?” The short solution is no. But an attribute request has been elevated for the support of the control via Cisco Bug ID CSCwa91505 .

Also, make sure that you possess your VTY and TTY lines configured relative to the Cisco Tutorial to Harden Cisco IOS Gadgets . Doing this will make sure that you improve your Cisco IOS XE launch beyond 17 once.9(1), you will end up protected of the MOP configuration status regardless.

THINK ABOUT MOP sysid?

This blog and the prior one centered on no mop enable . You’ll likely also start to see the no mop sysid user interface configuration order. When MOP is allowed, the MOP server will periodically multicast something ID information out to the Ethernet interfaces if mop sysid is enabled.

So if you notice frames on your own system with the Ethertype 0x6002, then there’s an excellent chance you not merely have MOP allowed but mop sysid allowed as well. Disabling MOP with the simply no mop enable user interface configuration command disables delivering MOP periodic program ID also.

Final Worries