Filter by:
  • Solution
  • Technology

answers

New install of LTM VE 10.2.2 - chmand error

Updated 6/19/2012 • Originally posted on 19-Jun-2012 by Leonardo 55

local/localhost emerg logger: Re-starting chmand

Getting the above error message out of the gate when I first console into my VE; it repeats about every 2 seconds.  It doesn't seem to allow me to add a management IP.

I also get a few errors below when I run the "config" utility:

1. This operation is only allowed on a primary cluster member
2. Error publishing admin_ip = 1070710
3. Error publishing mgmt route = 1070712
4. Bigpipe unknown query error:
    This operation is only allowed on a primary cluster member

See attached for screenshots... 

Thanks for looking... Leonardo
0
Rate this Question

Answers to this Question

7 Answers:

placeholder+image
USER ACCEPTED ANSWER & F5 ACCEPTED ANSWER
Updated 19-Jun-2012 • Originally posted on 19-Jun-2012 by qe
What hypervisor are you running it on? 10.2.3 and later support ESXi 5.x and later (unsupported, but workstation 8 and later will need 10.2.3 or later)

placeholder+image
USER ACCEPTED ANSWER & F5 ACCEPTED ANSWER
Updated 20-Jun-2012 • Originally posted on 20-Jun-2012 by Leonardo 55
Talked to my VMware guys and this one is running on a later version than our others so that may be the problem. I'll get a new version of LTM VE on there and let you know. Thanks!!

Leonardo
placeholder+image
USER ACCEPTED ANSWER & F5 ACCEPTED ANSWER
Updated 20-Jun-2012 • Originally posted on 20-Jun-2012 by Leonardo 55
The new version of LTM VE did the trick... thanks qe!
placeholder+image
USER ACCEPTED ANSWER & F5 ACCEPTED ANSWER
Updated 22-Jun-2012 • Originally posted on 22-Jun-2012 by Doris 0
This is helpful, learning from it. Thanks!
placeholder+image
USER ACCEPTED ANSWER & F5 ACCEPTED ANSWER
Updated 07-Oct-2013 • Originally posted on 07-Oct-2013 by S Young 4

The new version (10.2.3) of LTM VE worked for me also.... Thx!

placeholder+image
USER ACCEPTED ANSWER & F5 ACCEPTED ANSWER
Updated 07-Oct-2013 • Originally posted on 07-Oct-2013 by Stephan Manthey 3588

The main reason for failing VE implementations is a network adapter mismatch, imho. It´s required to stop (not hibernate) the VE and to modify the .vmx file. A .vmx file for TMOS v10 should have the following entries to emulate the expected hardware:

ethernet1.virtualDev = "vmxnet3"
ethernet2.virtualDev = "vmxnet3"

The ethernet0.virtualDev may be left untouched. Sometimes it was necessary to set it to "e1000". The ethernet0. will usually be mapped to eth0, your VE managment interface. All remaining adapters will be mapped to interfaces 1.1 and up.

placeholder+image
USER ACCEPTED ANSWER & F5 ACCEPTED ANSWER
Updated 09-Jul-2015 • Originally posted on 09-Jul-2015 by jaked 117

I am trying to install LTM VE 10.2.1 on ESXi 6. I am getting error "emerg logger : re-starting chmand" and mcpd is not starting up saying it is waiting for chmand to release start semaphore.

Can someone help me with this please?

;