OneTrueDabe
Technical User
Is the following a bug or a feature:
I have a CSS-SCA-2FE-K9 SCA Secure Content (SSL) Accelerator connected to a CSS 11501 Content Services Switch (Load Balancer) in one-armed proxy mode.
When the SCA Acclerator reloads, it does the following:
[ul]
[li]Sets "one-port" mode (Good)[/li]
[li]Sets the device's IP address and hostname (Good)[/li]
[li]Sets and queries the SNTP server[/li]
[li]Sets the default gateway ("ip route 0.0.0.0 ...")[/li]
[/ul]
The problem is: It Needs The Default Gateway Set BEFORE It Can Talk To The SNTP Server!!
The only device this box plugs into is the CSS Load Balancer, which doesn't respond to SNTP requests, so there's no way for it to set its date & time. (And date/time are VERY important for SSL certificate authorization.)
If I log into the Accelerator, I can run:
That works fine, but I shouldn't have to manually tell the box to set its time and date every time it powers up.
Currently, my "solution" (read: "work-around") is to crank the "sntp interval" down to once a minute. It's not a LOT of overhead, but still, having to query the SNTP server 86399 extra times a day seems a bit excessive to me.
Has anybody else run into this problem? For the record I'm using MaxOS 4.1.0.11 (build 200211151311) but even the Release Notes for 4.2 don't mention this.
As always, any help would be greatly appreciated. Thanks in advance!
--
Dabe
I have a CSS-SCA-2FE-K9 SCA Secure Content (SSL) Accelerator connected to a CSS 11501 Content Services Switch (Load Balancer) in one-armed proxy mode.
When the SCA Acclerator reloads, it does the following:
[ul]
[li]Sets "one-port" mode (Good)[/li]
[li]Sets the device's IP address and hostname (Good)[/li]
[li]Sets and queries the SNTP server[/li]
[li]Sets the default gateway ("ip route 0.0.0.0 ...")[/li]
[/ul]
The problem is: It Needs The Default Gateway Set BEFORE It Can Talk To The SNTP Server!!
The only device this box plugs into is the CSS Load Balancer, which doesn't respond to SNTP requests, so there's no way for it to set its date & time. (And date/time are VERY important for SSL certificate authorization.)
If I log into the Accelerator, I can run:
Code:
> [navy]enable[/navy]
# [navy]conf t[/navy]
config# [navy]no sntp server[/navy]
config# [navy]sntp server 10.0.100.1[/navy]
That works fine, but I shouldn't have to manually tell the box to set its time and date every time it powers up.
Currently, my "solution" (read: "work-around") is to crank the "sntp interval" down to once a minute. It's not a LOT of overhead, but still, having to query the SNTP server 86399 extra times a day seems a bit excessive to me.
Has anybody else run into this problem? For the record I'm using MaxOS 4.1.0.11 (build 200211151311) but even the Release Notes for 4.2 don't mention this.
As always, any help would be greatly appreciated. Thanks in advance!
--
Dabe