[BlueOnyx:22068] Re: 5209R cannot change nameserver settings in tcp/ip

[Adam Lepp]

I haven't been able to change mine for months.
Same scenario as described by others.

-----Original Message-----
From: Blueonyx [mailto:blueonyx-bounces at mail.blueonyx.it] On Behalf Of Dirk
Estenfeld
Sent: Tuesday, May 15, 2018 10:49 AM
To: BlueOnyx General Mailing List
Subject: [BlueOnyx:22064] Re: 5209R cannot change nameserver settings in
tcp/ip

Hello,

is there nobody who also have issues changing settings in tcp/ip?
I have the problem on several 5209R servers (I did not check every server)
and it is a very unhandy workaround to use cceclient to do the changes.

Best regards,
Dirk



---

blackpoint GmbH - Friedberger Straße 106b - 61118 Bad Vilbel
 


-----Ursprüngliche Nachricht-----
Von: Blueonyx [mailto:blueonyx-bounces at mail.blueonyx.it] Im Auftrag von Dirk
Estenfeld
Gesendet: Montag, 14. Mai 2018 09:05
An: BlueOnyx General Mailing List <blueonyx at mail.blueonyx.it>
Betreff: [BlueOnyx:22052] Re: 5209R cannot change nameserver settings in
tcp/ip

Hello Michael,

thank you for your email.
I did send you the logfile by email. 

I did remove /etc/DEBUG file after getting the logs.

Changing the dns with /usr/sausalito/bin/cceclient is not working.
I always get "BAD PARAMETERS"

SET 1 . dns = "&1.1.1.1&8.8.8.8&"
403 BAD PARAMETERS
set 1.dns = "&1.1.1.1&8.8.8.8&"
403 BAD PARAMETERS
SET 1 . dns = "&8.8.8.8&8.8.4.4&"
403 BAD PARAMETERS
SET 1.dns = "&8.8.8.8&8.8.4.4&"
403 BAD PARAMETERS

Thank you also for the small script.
The syntax is slightly different:

/usr/sausalito/sbin/set_dns.pl configure "1.1.1.1&8.8.8.8"

But it was working.

Best regards,
Dirk


---

blackpoint GmbH - Friedberger Straße 106b - 61118 Bad Vilbel


-----Ursprüngliche Nachricht-----
Von: Blueonyx [mailto:blueonyx-bounces at mail.blueonyx.it] Im Auftrag von
Michael Stauber
Gesendet: Montag, 14. Mai 2018 08:31
An: blueonyx at mail.blueonyx.it
Betreff: [BlueOnyx:22048] Re: 5209R cannot change nameserver settings in
tcp/ip

Hi Dirk,

> It is not possible to safe settings in TCP/IP. I do always get a blank 
> TCP/IP page and an error in the messages log May 13 13:09:08 hostname 
> cced(smd)[4404]: client 0:[49:1305]: AUTHKEY to user "" failed

Every time a GUI page is loaded we check the authentication of the user
who's accessing the page to determine if the user is logged in, valid and
privileged enough to see the page. There are two forms how CCE can
authenticate a user

The AUTH or AUTHKEY command.

AUTH requires username and password and (if the login is valid) returns a
sessionID. This is usually only used during login to the GUI and after that
we use the username and password.

AUTHKEY requires the username and sessionId and (if valid) returns the OID
of the user in question.

If you get 'AUTHKEY to user "" failed' this tells me that the GUI page tried
to authenticate you via AUTHKEY, but no username was sent.

For debugging could you please do this?

Run "touch /etc/DEBUG" to create the empty file /etc/DEBUG. Then run "tail
-f /var/log/admserv/adm_error" while you login to the GUI, go to TCP/IP,
make the change you wish to make and hit save.

Please send me the result from the logfile afterwards. But *please* edit the
file to obscure your password. It will be logged (once) as well during the
AUTH stage right after login.

While /etc/DEBUG is present the GUI will log *all* CCE transactions to
/var/log/admserv/adm_error. This will be *very* helpful to debug this issue.

In the meantime (until this problem is fixed) you still might want to make
your DNS changes. You can do so via cceclient.

Example_

[root at 5209r ~]# /usr/sausalito/bin/cceclient
100 CSCP/0.99
200 READY
find System
104 OBJECT 1
201 OK

This tells us the 'System'-object has the OID #1. Yours might be different.

Run this command to look at the content of your System object (substitute
the correct OID if yours isn't #1:

get 1
102 DATA productBuild = "5209R"
102 DATA NAMESPACE = ""
102 DATA productIdentity = "20180208"
102 DATA CLASSVER = "1.2"
102 DATA OID = "1"
[...]
102 DATA dns = "&8.8.8.8&4.2.2.2&"
[...]

As you can see: This example has the DNS servers 8.8.8.8 and 4.2.2.2
configured. The format here is Scalar, meaning: The values are encapsulated
in '&' characters.

Say you want to change the 2nd DNS server from 4.2.2.2 to 8.8.4.4, then the
command to do it would be this:

SET 1 . dns = "&8.8.8.8&8.8.4.4&"

That will then deploy the new DNS servers to the respective config files.

The second way is to use a small tool that comes with the CD-version of
BlueOnyx: /usr/sausalito/sbin/set_dns.pl

If I wanted to set 8.8.8.8 and 8.8.4.4 as DNS servers, I would use the tool
this way:

/usr/sausalito/sbin/set_dns.pl 8.8.8.8&8.8.4.4

Note that there is no leading and trailing "&", because the tool adds them
itself when submitting to CODB. But if more than one DNS server is
specified, we need to separate them with "&" and no spaces.


--
With best regards

Michael Stauber
_______________________________________________
Blueonyx mailing list
Blueonyx at mail.blueonyx.it
http://mail.blueonyx.it/mailman/listinfo/blueonyx

_______________________________________________
Blueonyx mailing list
Blueonyx at mail.blueonyx.it
http://mail.blueonyx.it/mailman/listinfo/blueonyx

_______________________________________________
Blueonyx mailing list
Blueonyx at mail.blueonyx.it
http://mail.blueonyx.it/mailman/listinfo/blueonyx