The following steps are the most basic, essential steps to get a Netscaler Application Switch up and running.
#set root password
set system user nsroot newpasswd1
#add mapped ip, this is the interface for connections to servers (inside)
add ns ip x.x.x.x 255.255.255.0 -type mip
#set netscaler ip (nsip), this ip used for administration only
set ns config -ipaddress x.x.x.x -netmask 255.255.255.0
#set default gateway on nsip
add route 0.0.0.0 0.0.0.0 x.x.x.x
#save config
save ns config
reboot
#open the gui
http://nsip/
=====
Friday, December 28, 2007
Wednesday, December 5, 2007
Using IP's instead of domain names for NTP server configuration
To prevent devices from the extra step of having to resolve domain name, I often use the IP for NTP servers references. These IP's dont change very often, so its a pretty safe bet to use IP's and not the domain names. Typically I configure NTP with a list of 5-10 servers.
Typically I set my monitoring server up as the NTP check point for all the other servers and network devices in my network. But I also provide each system with a list of fallback servers.
I like to use the pool servers from ntp.org
There are about 1700 active servers, today.
Typically I set my monitoring server up as the NTP check point for all the other servers and network devices in my network. But I also provide each system with a list of fallback servers.
I like to use the pool servers from ntp.org
There are about 1700 active servers, today.
Subscribe to:
Posts (Atom)