DLM License Violation

[tmnt1981]

I have a 6 site Cluster (without SWA) and my DLM is in license violation.
This is because a colleague was working an audio issue and decided to replace the MXE controller thus changing the hardware id in the DLM.
I changed it to reflect the new hardware id in both the DLM and AMC.
I performed a sync for all network elements but I continue to get a License violation:
"Lost Connectivity to Peers"
I've repeated the sync process and the alarm clears but then comes back as a "major alarm."
Am I missing something?
Obviously I cannot call Tech Support since no SWA but I have contacted AMC.
They tell me its in license violation because the customer doesn't have SWA.
If we switch it back to the original controller and reset the hardware id's will it still be in license violation?
Is it in license violation because we broke the Group Licensing without SWA?
Any help would be appreciated, thanks.

[Sube100]

A couple of things here, on the DLM form on the designated license manager, does it show the controller that was switched out in license violation?

When the other controller was swapped out, did you keep the iButton and put it in the new controller?

Is the other controller contactable?

[tmnt1981]

The first thing I noticed was the hardware id was different than what I showed in records.
It was set to "no" for being the DLM.
I switched it to "yes."
I then logged in to AMC and cleared the hardware id.
I then did a sync from the DLM to AMC by clicking "retrieve licenses."
I then did a sync from the DLM controller Network Elements page to the other sites.
The alarm cleared, I thought we were in the clear.
Then the alarm came back.
I did the same thing, the alarm cleared then came back.
I tried it again, and the alarm has not cleared this time.
I called AMC and they told me to call Tech Support.
Unfortunately this is not an option since our sale rep dropped the ball on SWA.
What is the ibutton?

[Dogbreath]

What is the ibutton?

That's the thing that tells the 3300 chassis what its hardware ID is. You can move it around if you want to replace the chassis without changing the hardware ID.

[Sube100]

tmnt, I think what you need to do is a RMESS VERIFY command from the DLM controller to the one you replaced, see what the printout is.

Can you ping the other controller etc?

[tmnt1981]

Yes all controllers are pingable from the DLM controller.

[PC77375]

TMNT- I had a similar issue, but SWA was not expired. My process was to Sync the suspect controller with the AMC and make sure that this was clear. Then there were a few things to to happen on the DLM, a sync of the DLM controller  under license and option selection then under Application Group Licensing, and finally a sync with the network elements. Make sure to check "application group licensing" if it is not already checked. If SWA expiration is the actual issue, then there will probably be no way to resolve at this point aside from renewing SWA.

[tmnt1981]

Thanks, I performed that step by step.
The license violation persists.
This is what I get when I issue the command "License Status" in maintenance commands.
Designated License Manager - GARID     : 548209
License Violation Level                : Critical
Local Violation Cause(s):
   - Lost Connectivity to Peer(s)
Member 6838484 Violation Cause(s):
   - Application Group is in Violation       Critical   
Member 17607520 Violation Cause(s):
   - Application Group is in Violation       Critical   
Member 30646941 Violation Cause(s):
   - Application Group is in Violation       Critical   
Member 43931201 Violation Cause(s):
   - Application Group is in Violation       Critical   
Member 66855511 Violation Cause(s):
   - Lost Connectivity to the DLM            Critical   
   - Application Group is in Violation       Critical   
Member 68473406 Violation Cause(s):
   - Application Group is in Violation       Critical   
Member 90005918 Violation Cause(s):
   - Application Group is in Violation       Critical
The interesting thing is in AMC the DLM shows status green but the ULM shows status yellow.
Its a ticking clock, any ideas?

[VinceWhirlwind]

Are you absolutely sure the new controller has all the correct IP addresses entered for each of itself AND the other 5 controllers in the cluster in both
Network Elements
and
ICP/PBX Networking
forms?

[tmnt1981]

Yes, they are correct.
I can ping each controller from the maintenance window.

[VinceWhirlwind]

Being able to ping a controller doesn't tell you you have configured the ICP/PBX form correctly.

[jemson]

Thanks, I performed that step by step.
The license violation persists.
This is what I get when I issue the command "License Status" in maintenance commands.
Designated License Manager - GARID     : 548209
License Violation Level                : Critical
Local Violation Cause(s):
   - Lost Connectivity to Peer(s)
Member 6838484 Violation Cause(s):
   - Application Group is in Violation       Critical   
Member 17607520 Violation Cause(s):
   - Application Group is in Violation       Critical   
Member 30646941 Violation Cause(s):
   - Application Group is in Violation       Critical   
Member 43931201 Violation Cause(s):
   - Application Group is in Violation       Critical   
Member 66855511 Violation Cause(s):
   - Lost Connectivity to the DLM            Critical   
   - Application Group is in Violation       Critical   
Member 68473406 Violation Cause(s):
   - Application Group is in Violation       Critical   
Member 90005918 Violation Cause(s):
   - Application Group is in Violation       Critical
The interesting thing is in AMC the DLM shows status green but the ULM shows status yellow.
Its a ticking clock, any ideas?

I had this recently. Tried everything. License syncs, SDS syncs, override SDS syncs with the "Lost Connectivity" controller.
Solution in the end was to log into the "Lost Connectivity to DLM" controller (not the DLM itself) and under application group licensing, hit change, toggled the DLM radio button to Yes, then without saving back to No, and hit save. Violation disappeared immediately.