Dell Kace K2000 : Multicast NORM - Invalid host
Hi all,
I just upgraded my K2000 Appliance to 4.0 version. Now I have the NORM protocol option for multicast. I try to deploy a WIM image on 2 clients using this protocol but my deployment fails to the "Apply image" step. I tried to run the script manually and here is the returned message (white area are my client IP address):
I defined multicast settings like this:
- Timeout to wait for connection 'Ready to receive' state: 5 minutes
- Multicast protocol: NACK-Oriented Reliable Multicast (NORM)
- Multicast address: 239.252.121.10
- Control channel port: 2112
- Multicast hops: 4
- Transmission rate: 20 MB/s
I don't know what else I can do. Someone can help me?
Thank you in advance.
2 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
gerald_mack
6 years ago
Q) what happens if you change host to 224.0.1.20 instead of 239.252.121.10 ?
Comments:
-
With address 224.0.1.20 multicast deployment starts! But after a few seconds/minutes I have the message endlessly “Proto Error: NormSenderNode::HandleObjectMessage() WriteSegment() error” on my clients - SITEL 6 years ago
-
Are you currently at 4.0 or 6.0 ? What if you set the rate to 2, does the same thing occur? can you post the multicast server and client logs? or you might open a support ticket? - gerald_mack 6 years ago
-
I'm at 6.0. I set the rate to 1Mo/s and I have exactly the same problem but it takes a little bit more time before crashing.
I can send you the server logs but where can I find the client logs?
I already opened a support ticket, sent us logs but they seems as lost as me
EDIT:
Here are the server logs:
Oct 16 12:16:41 k2000 K2000 Multicast: (void MulticastProcessor::EventControl(struct bufferevent *, short)) line: 440 -- A client has dropped away, 2 listeners left (unknown error) --> 21 ...
Oct 16 12:16:38 k2000 K2000 Multicast: (void MulticastProcessor::EventControl(struct bufferevent *, short)) line: 440 -- A client has dropped away, 2 listeners left (unknown error) --> 21 ...
Oct 16 12:02:59 k2000 K2000 Multicast: (virtual void DbSupport::dump_db()) line: 161 -- ip_addr=<ip_client1>, ip_port=49684, timestamp=1539684179, type=1, ordinal=1, message=0
Oct 16 12:02:59 k2000 K2000 Multicast: (virtual void DbSupport::dump_db()) line: 161 -- ip_addr=<ip_client2>, ip_port=49685, timestamp=1539682916, type=1, ordinal=0, message=0
Oct 16 12:02:59 k2000 K2000 Multicast: (virtual void DbSupport::dump_db()) line: 154 -- Receivers DB version=1, max_clients=2, latest_client=2, headerSize=16, recordSize=192
Oct 16 12:02:59 k2000 K2000 Multicast: (void MulticastProcessor::EventAcceptControl(struct evconnlistener *, int, struct sockaddr *, int)) line: 393 -- client accepted ...
Oct 16 11:41:56 k2000 K2000 Multicast: (void MulticastProcessor::EventAcceptControl(struct evconnlistener *, int, struct sockaddr *, int)) line: 393 -- client accepted ...
Oct 16 11:38:32 k2000 K2000 Multicast: (const bool MulticastProcessor::CreateControlChannel()) line: 334 -- event handler is up ...
Oct 16 11:38:32 k2000 K2000 Multicast: (virtual bool DbSupport::create_client_db(unsigned short, std::string &)) line: 94 -- shm: size request = 396 bytes [2 * (12 + 192)]
Oct 16 11:38:32 k2000 K2000 Multicast: (NormImplementation::NormImplementation()) line: 52 -- Using NORM version 1.5r6.
Oct 16 11:38:32 k2000 K2000 Multicast: (const bool MulticastProcessor::ParseArgs(int, const char **)) line: 293 -- TimeToComplete : 2018-10-16 13:16:17 (01:37)
Oct 16 11:38:32 k2000 K2000 Multicast: (int main(int, const char **) ) line: 56 -- spew built on May 9 2018 at 20:06:56
Oct 16 11:38:32 k2000 K2000 Multicast: (EventBuilder::EventBuilder() ) line: 24 -- Compiled with libevent headers version 2.0.21-stable
Oct 16 11:38:32 k2000 K2000 Multicast: (EventBuilder::EventBuilder() ) line: 23 -- Using libevent library version 2.0.21-stable
Oct 16 11:38:32 k2000 K2000 Multicast: (int main(int, const char **) ) line: 38 -- *** Starting K2000 Multicast Sender *** - SITEL 6 years ago
i have also the same problem as dude87. Here my tests :
* If i set the multicast IP to 239.0.0.100, K2000 Multicast Receiver returns a single message "Invalid Host." and the multicast is failing
* if I set the IP to a 224.xxx.xxx.xxx one (other than 224.0.0.xxx) like 224.100.0.1 -or 224.1.0.100-, it returns repeatedly this message :
Proto Error: NormSenderNode::HandleObjectMessage() wainting to sync ... and the multicast is failing
* If I set the IP to a 224.0.0.xxx, MULTICAST'S WORKING
My question : what range of IPs do we have to use for the multicast? it's only limited to the 224.0.0.xxx one?
Thanks for your answers - pg_fr_69 7 years ago
So it's not possible for us to use this range of addresses - SITEL 7 years ago
i'm very surprised that there is no answers about this problem.
I would like to use this new functionnality offers with the version v4 but i can't find any detailled information to how to configure it (specially the multicast IP to use).
we have multiple vlans in our organization and, as dude87 said, 224.0.0.xxx addresses are limited on the same subnet.
I really need help. Thanks for your answers - pg_fr_69 7 years ago
Last information I had from Quest support is that it could be possible to route something accross 224.0.0.0/8. I didn't try yet. But I made some tests in the same subnet using an address in 224.0.0.0/24 and the multicast starts but crashes after a few minutes with the following message on my clients : “Proto Error: NormSenderNode::HandleObjectMessage() WriteSegment() error”. I tried to reduce the speed as advised by the support (I put the lowest speed = 1 Mo/s) but deployment still crashing... Our K2000 is a VM on Hyper-V and I suspect that it's not correctly supported on this system. Let me know if it's better on your side. - SITEL 7 years ago