Solaris Container Migration Analiser - Explorer Parser

I want to share with you a useful perl script to analyse explorer files and highlights issues that can gets you in trouble in case of  Solaris Containers (such as Solaris 8 and Solaris 9 branded zone)  migration. Explorer files you will pass obviously refers to the system you want to migrate.

It will give you the column listed on the bottom of this page into a "csv" file. So you will have a quick reference on the most important thing to pay attention on migrating Solaris 8 and Solaris 9 host on Solari 10 Containers for each system you have got to migrate and looking at this file you can easly decide the order of migration (starting from the easy one for example), the storage space you will need to prepare, check if you have vxvm or not, network complexity, and so on.

On my experience I think the most important thing to check with Solris Container is kernel modules and the amazing thing is about the filtering on supposed non migrable modules listed in the column "MODULES" on the builded csv file.

On the migration experiences basis, you could optimize and eventually populate the migrable kernel module list (modinfo-sol8.out,modinfo-sol9.out,modinfo-all) in the attached zipped script directory "ExplorerParser_vx.x.tar.gz". Help me to update this list attaching the list of new modules only you will find on you experience (call the file "newmodulels"), I will update the modinfo file in the next release .

You can find all downloadable versions either on the right corner of this page under Tools-->Attachments or at the direct link below:

http://wikis.sun.com/pages/viewpageattachments.action?pageId=52726576

Prerequisite will be sotisfing these settings at the beginning of the perl script:

my $TAR = "/usr/sfw/bin/gtar";
my $GZ = "/usr/bin/gzip";
my $GREP = "/bin/grep";

my $JAVA_DATE = "java -classpath DateDiff.jar it.sorintlab.explorerparser.datediff.DateDiff ";

The syntax is as follow:

./eparser.pl <explorer directory> <file_outoput> <file_log>

./eparser.pl /explorer/ExplorersToAnalyzeDirectory/  out.csv  out.log

Columns you will get:

NODENAME;EXPLORER DATE;RELEASE;IPMP;VOLUME MANAGER;CLUSTER_VERSION;RAW DEVICE;USED DATA;AVAILABLE DATA;USED SYSTEMS;AVAILABLE SYSTEMS;USED /export/home;AVAILABLE /export/home;SWAP;N INTERFACES;N AGGR;N TAGGED;N ROUTES;MEMORY SIZE;N CORE;CPU FREQ;NFS MOUNT;NFS SHARE;MODEL;Last Login Week;Last Login Month;Last Login 6 Month;Last Login Year;Last Login Week Root;Last Login Month Root;Last Login 6 Month Root;Last Login Year Root;Uptime;IPKTS;OPKTS;LEGATO;MODULES

I want to thanks people who developed the script and mantain them: Paolo Sella And Fabio Seregni by Sorint.Lab.