It is possible to convert devices from an old modeltype to a new custom model type using NewMM.pl. You will just need to manually modify the NewMM.pl script to perform the conversion. In order to use the NewMM.pl for this conversion though each device TYPE that you want to convert has to be identifiable by SysOID. NewMM.pl goes out and finds all models of a given model type, and with a given SysOID, and converts those to the correct model type.
The first criteria is that these modeltypes are contactable by SNMP when running the script.
1) Back up NewMM.pl.
2) Open NewMM.pl in a text editor, and look around the 350 line number block. You should see a lot of information within square brackets that look similar to this:
["CiscoBTS", "0x4d70003", 0,0, "$sysObjectID", "18.104.22.168.4.1.5296.1", "", "0:0", "0x3d0002"],
3) Copy one of these lines, and modify it as follows:
["<destination_model_type_name", "<destination_model_type_handle", 0,0, "$sysObjectID", "<sysOID1> <sysOID2> <sysOID3>", "", "0:0", "<originating_model_type>"],
Note that you can specify multiple SysOIDs to convert by adding them one after another in a space delimitated list (show above). So, for example, assume you want to convert the Cisco 7204 device which has a SysOID of 22.214.171.124.126.96.36.199.223 to your new model type, "CA" with model handle, 0xffff0001, from the GnSNMPDev Model type. To do this, you would create your new ModelType using MTE, make sure it is loaded and then you would modify NewMM.pl and add this line to the end of the chunk around 380:
["CA", "0xffff0001", 0,0, "$sysObjectID", "188.8.131.52.184.108.40.206.223", "", "0:0", "0x3d0002"],
Destination MT Destination Handle SysOID of the device Originating Model Type Handle.
4) Run the NewMM.pl as you would normally.
(Legacy KB ID CNC TS29989 )