Hello forum friends,
There are a lot of postings that speak about why you might receive a DIFFERENT MODEL TYPE alarm
and instructing you to use CA's NewMM.pl script to correct this problem,
but I was unable to find a practical example of NewMM.pl usage online.
So I am providing one here.
I hope this post is helpful to others who may not realize that this sort of update is possible.
If so, please give it a Thumbs Up!
Scenario:
I had several F5 devices of the same type (BigIP 6800) discovered and modeled in Spectrum.
However, one of them had been discovered and modeled long ago, in a prior hotfix, and existed as model type BigIPLoadBlncr.
CA had changed the discovered Model Type in 9.2.1 H06; the newer devices were discovered correctly as model type F5BigIPDev, which includes several customized views for F5 devices.
Rather than delete and rediscover the device, I decided to correct this using the NewMM.pl script, which is supposed to preserve container and connection information.
When you run NewMM.pl without any parameters, it detects known updates to Model Types and helps you update any affected devices.
However, by default, NewMM.pl will only check a limited list of source model types. As of 9.2.1 H06, this list is:
[font=Courier New]@source_mtype = ( "0x3d0002", # GnSNMPDev
"0x21000c", # Rtr_Cisco
"0x11c001a", # SwCat35xx
"0x11c0011", # SwCat4***
"0x11c0013", # SwCat6***
"0x2100a3", # Cisco_12000
"0x21008f", # UBR72xxCMT
"0x3cc0002", # GenCiscoCSS
"0x2100cb" # GnCiscoDev
);[font]
As you can see, BigIPLoadBlncr is not part of that list.
So when I executed NewMM.pl with default settings, nothing was changed.
In order to correct my device, I needed to invoke NewMM.pl with the following information:
[list=1]
[*]my SpectroServer hostname = spectrum01
[*]my SpectroServer landscape ID (in hex) = 0x10000
[*]the -m parameter, which indicates "manual" customization
[*]System OID of the device = 1.3.6.1.4.1.3375.2.1.3.4.11
[*]Current Model Type Name = BigIPLoadBlncr (note, this is NOT the model type handle!)
[*]Correct Model Type Name = F5BigIPDev (note, this is NOT the model type handle!)
[list]
The script invocation and output is shown below.
There are several things I wish to point out:
:what:First, please note that on a Windows platform, you must run NewMM.pl in a Bash shell for it to complete properly.
:what:Second, please note that the my device's model handle was changed from 0x10318f to 0x108210 during the modification;
effectively, this behaves the same as a delete and re-discovery. However, NewMM.pl preserves container and connection details.
:smileThird, please note that my other F5 devices were unaffected by this script.
[font=Courier New]D:\> bash --login
spectrum01%/d/win32app/Spectrum
cd $SPECROOT/Install-Tools/PostInstall/
spectrum01%/d/win32app/Spectrum/Install-Tools/PostInstall
./NewMM.pl `hostname` 0x100000 -m 1.3.6.1.4.1.3375.2.1.3.4.11 BigIPLoadBlncr F5BigIPDev
NewMM.pl is running using custom conversion criteria. To use out-of-the-box conversion criteria, run NewMM.pl without the `-m' option.
connect: successful spectrum01
current landscape is 0x100000
WARNING: CLI is a powerful tool that allows a user to make changes
directly to the SPECTRUM knowledge-base without the error checking
provided by OneClick. Please read the accompanying CLI user
documentation before using the create, destroy, or update commands.
Collecting data...
Processing data...
/ Please Wait...
_______________________________________________________________
The script may have discovered one or more models of type
0x3b70005 which can be converted to the following new model type:
Model Type: F5BigIPDev
Only eligible models matching the conversion criteria
will be converted to the new model type.
The following models have been discovered and will be
converted upon request:
MHandle: 0x10318f
MName: ct1-f56800dqs-02
MType: 0x3b70005
_______________________________________________________________
_______________________________________________________________
Would you like to convert the eligible source model(s)
to this new model type? (y/n): y
_______________________________________________________________________________
Converting select models to new model type: F5BigIPDev. Please wait...
Enterprise DBconv v6.15
(c) Copyright 2002 CA, Inc.
* Single Landscape Mode
* Landscape : 0x100000 (spectrum01 @ spectrum01)
* Source Model Type : 0x3b70005 (BigIPLoadBlncr)
* Destination Model Type : 0x3b7000e (F5BigIPDev)
* Validating Transfer Attributes
* Validating Filter Attributes
Landscape 0x100000 has 1 model(s)
+ Changing discovery attributes
+ OK to convert model 0x10318f - ct1-f56800dqs-02
+ Converting shared SCM configurations
+ Creating New Models
+ Converted 0x10318f -> 0x108210
+ Converting nonshared SCM configurations
+ Restoring container associations
+ Restoring device associations
+ Restoring connections for 0x108210
* Conversion Complete !
Removing Temporary Files
-disconnect: successful from spectrum01 - connected for 0 hours, 1 minutes
New Management Module Conversion script has successfully completed.
To view log report, read NewMM_log_Jun_25_12_03_02_00_PM
file.
spectrum01%/d/win32app/Spectrum/Install-Tools/PostInstall
>
[font]
Thank you,
--Mark S
Mark Serencha – Inforonics Global Services, LLC – (m) +1-781-439-0519 – Mark.Serencha_AT_inforonics.com