Forum Discussion

JimW_156953's avatar
JimW_156953
Icon for Nimbostratus rankNimbostratus
Jun 07, 2014

Unable to add 7200v to a sync-group - HTTP compression license error

Landscape: EXISTING: 3600 x 2 in HA, Sync and Failover group. Both running 11.4.1.HF2 with LTM, APM provisioned.

 

NEW : Trying to add a new 7200v to the sync and failover group. New 7200 running same 11.4.1.HF2 with LTM, APM provisioned.

 

Plan is to add 7200v into existing sync-and-failover group; once synced will decommission 3600s.

 

DONE SO far: Added the devices to each other - build device trust among each other - they are both able to see each other through network - no issues.

 

ISSUE: Everytime I run sync-and-failover config - it syncs the Admin and root passwords and thereafter fails with error message on LTM7200

 

"Jun 7 12:04:52 LTM7200v warning mcpd[7391]: 010712e9:4: log.pva.level is not in BigDB.dat. Jun 7 12:04:52 LTM7200v warning mcpd[7391]: 010712e9:4: mapi.discover.exchange.server is not in BigDB.dat. Jun 7 12:04:52 LTM7200v warning mcpd[7391]: 010712e9:4: md.enablemaxandglobalhttpstats is not in BigDB.dat. Jun 7 12:04:52 LTM7200v warning mcpd[7391]: 010712e9:4: md.maxcspminjectionratio0 is not in BigDB.dat. Jun 7 12:04:52 LTM7200v warning mcpd[7391]: 010712e9:4: md.maxcspminjectionratio1 is not in BigDB.dat. Jun 7 12:04:52 LTM7200v warning mcpd[7391]: 010712e9:4: Per-invocation log rate exceeded; throttling. Jun 7 12:04:54 LTM7200v err mcpd[7391]: 01070356:3: HTTP compression feature not licensed. Jun 7 12:04:54 LTM7200v err mcpd[7391]: 01071488:3: Remote transaction for device group /Common/SYNC-And-Failover to commit id 23 6022032392778850511 /Common/LTM3600-1 0 failed with error 01070356:3: HTTP compression feature not licensed..

 

BIPGIP7200 has the BEST license enabled which has almost what is required for it to function. But there is no exclusive mention of HTTP Compression license

 

Any suggestions?

 

  • issue resolved. It was licensing issue being fixed at the back end, re-activated the license and now could add new devices to sync-failover-group. Thanks,

     

  • I don't think this will work. I'd suggest you take the route of using an SCF or UCS file for this.