8.2 simulator, peering, licenses and serial numbers

[#1]

Hi folks,

Just installed and configured a pair of 8.2 simulators, but I'm wondering what will happen if I need to setup a second cluster and establish peering relationship and mirrors.

I had issues in the past with 7-mode snapmirroring to a simulator with the same serial number, would that be the same ?

In that case, we are short of two serial number/license couple !

Did somebody already think about this ?

Thanks !

[#2]

Good point...I used the ESX and non-ESX licenses... a pair as the source and single-node as the target...all separate keys this way.  I will have to test it out and see if any issue if using the same serial, but if you go single node on the target they did provide the extra license.

[#3]

That's interesting.

First time I deployed my 2 nodes, I setup a random serial number, like I used to do before, but I could not set the licenses… No error message either, but key and serial didn't match so it was ignored.

Now, the installation documentations mentions only two different serial numbers : The original one which does not look like it should be changed (4079432-74-1), and the one for the second node which is 4034389-06-2.

And this is the same documentation for ESX or non-ESX platforms.

Here is how my license show looks like :

clus3::> license show

  (system license show)

Serial Number: 1-80-000008

Owner: clus3

Package           Type    Description           Expiration

----------------- ------- --------------------- --------------------

Base              license Cluster Base License  -

Serial Number: 1-81-0000000000000004034389062

Owner: clus3-02

Package           Type    Description           Expiration

----------------- ------- --------------------- --------------------

NFS               license NFS License           -

CIFS              license CIFS License          -

iSCSI             license iSCSI License         -

FCP               license FCP License           -

SnapRestore       license SnapRestore License   -

SnapMirror        license SnapMirror License    -

FlexClone         license FlexClone License     -

SnapVault         license SnapVault License     -

SnapLock          license SnapLock Compliance License -

SnapManagerSuite  license SnapManagerSuite License -

SnapProtectApps   license SnapProtectApp License -

SnapLock_Enterprise license SnapLock Enterprise License -

Insight_Balance   license OnCommand Balance     -

Serial Number: 1-81-0000000000000004079432741

Owner: clus3-01

Package           Type    Description           Expiration

----------------- ------- --------------------- --------------------

NFS               license NFS License           -

CIFS              license CIFS License          -

iSCSI             license iSCSI License         -

FCP               license FCP License           -

SnapRestore       license SnapRestore License   -

SnapMirror        license SnapMirror License    -

FlexClone         license FlexClone License     -

SnapVault         license SnapVault License     -

SnapLock          license SnapLock Compliance License -

SnapManagerSuite  license SnapManagerSuite License -

SnapProtectApps   license SnapProtectApp License -

SnapLock_Enterprise license SnapLock Enterprise License -

Insight_Balance   license OnCommand Balance     -

27 entries were displayed.

[#4]

I used to do the same...using different serials for each node but like you said the license adds but won't work if it doesn't match.  The license file on the simulator site has these 3 serials and keys for each.

4079432737     # esx   

4079432741     # non-esx node1

4034389062     # non-esx node2

[#5]

I also changed the serial number again and found it can't boot to reassign the disks after so have to set right the first time or start over.

[#6]

It looks like the serial number shouldn't be an issue in most case.

As far as DOT is concerned, serial number doesn't matter for snapmirror or peer relationships, but some third party products may, I thinking about VMware SRM…