Netbotz 755 DHCP hostname

[Lincoln_Darran]

Afternoon Supporters,

We've recently refreshed a lot of our Netbotz estate and moved from 355s to 755s.

Got them all running 5.4.0.11, most things I've worked out and got working.

However, keep getting dns info being stomped all over by the devices registering in DHCP as snarc-soca9

Hostname is configured on all the devices, but on DHCP refresh they change to snarc-soca with a "strange" MAC address. 

Anyone found a work around or fix?

Darran

[Cory_McDonald]

Hello @Lincoln_Darran,

I recommend reaching out to technical support to look into this issue further.  I have also reached out to some people internally within Schneider to see if I can get more guidance on this, but getting something officially logged through support should help move this issue along for you.

If I hear anything back, I'll ensure to reach out, but I still recommend you reach out to support.

Kind Regards,

Cory

[Lincoln_Darran]

@Cory_McDonald thanks for kepeing a watch on the thread.

I've got an open ticket with support for this.

I'll post once I've got something back 🙂

[APC_Steve]

Hi @Lincoln_Darran ,

I spoke with engineering on this and I believe there is also a case opened on this with a rep. I've told them the same thing as I'll write here to you.
Engineering believes we're going by the RFC for this but they're still looking into how they might make it easier for you. This may take time however and you'll definitely run into this issue multiple times before and if this is addressed.
Engineering suggested that you create DHCP reservations for these devices and they feel that will resolve the issue. Assuming you're also the one that opened the case with the rep, I'll ask that any future correspondence on this issue take place there as this forum is not monitored as thoroughly.

Thanks,
Steve

[Lincoln_Darran]

Hi @APC_Steve 

Yep, I have a case open.

Tried DHCP reservations, to no effect.  Think it's down to interpretation of the DHCP RFCs.  Noticed that the newer UPS NMCs are also starting to use what looks like the same kernel as the 755s, and they're not honouring the domain name in the DHCP negotiations.

I realise the M$ DHCP implementation isn't the best, but it does seem a common issue with device using newer linux distros with a DHCP client enabled.

Thanks for your help

[APC_Steve]

Hi @Lincoln_Darran ,

I've noted your comments in the engineering log for this. Hopefully it helps.

Steve

[joshellisSE]

Hello @Lincoln_Darran , which UPS NMC's are you noticing this with?  You mentioned that they're using the same kernel as the Netbotz 750 so I'm going to assume you're referring to the NMC4, used in our Galaxy VS/VL UPS line?   Does that sound correct?

[Lincoln_Darran]

Hi @joshellisSE 

I don't have any real evidence of a common kernel.  Just a a feeling of how both devices operate.  

And yes, it is the NMC4 cards I was talking about, in Galaxy VS's.

HTH

[Lincoln_Darran]

Think I might have solved it!

For some reason the snarc-soca9 hostname is used against the 127.0.1.1 interface, which somehow gets pushed out over the public interface during the DHCP process. Strange behaviour.

Anyway, login as root over ssh. edit /etc/hosts and insert the "real" hostname in front of snarc-soca9 on the 127.0.1.1 host record line. as below

127.0.1.1    MyRealHostname snarc-soca9

Use the reboot command to make that the live config, and those pesky snarc-soca9 records will slowly TTL out of your dhcp/dns.