cancel
Showing results for 
Search instead for 
Did you mean: 

Can't assign non 192.168.1.x address to STM (ver 8.3)

SOLVED
flyddw
Contributor

Can't assign non 192.168.1.x address to STM (ver 8.3)

Our company purchased two Cisco STM appliances (1u computers running STM only). It's in a datacenter without a DHCP server, so it took 192.168.1.100. I cannot configure it to accept a non 192.168.1.X address. It is version 8.3, and I cannot find any working documentation for this version - only 8.0, 9.0, and 9.1.

a) How do I change the IP address if I only can connect via a console?

b) Is it possible to upgrade to the latest, considering we just purchased the SW/HW?

1 ACCEPTED SOLUTION

Accepted Solutions
flyddw
Contributor

Re: Can't assign non 192.168.1.x address to STM (ver 8.3)

Thanks again.

I had to jump thru some physically hoops, but I took a laptop to the server, and forced a static IP of 192.168.1.200, and connected via web interface.

I was then able to change the IP address, and can proceed to login from my desktop now.

So...upward and onward to configuring it now.  Thanks again.

Derek

View solution in original post

4 REPLIES 4
owen
Frequent Contributor

Re: Can't assign non 192.168.1.x address to STM (ver 8.3)

When it first boots, Stingray will attempt to get a temporary address using DHCP, and will fall back to 192.168.1.100 if DHCP was not successful.  You should then proceed to initial configuration, at https://IP-Address:9090, as instructed on the console.

In your case, it looks like Stingray could not obtain a routable address (no DHCP, and 192.168.1.x is not appropriate).  You should log on via the console and run the z-set-initial-address script to configure an appropriate address, then proceed with the initial configuration.

There's more documentation at http://splash.riverbed.com/message/13478#13478 explaining how to get a console and how to debug problems accessing the initial configuration web interface.

The Cisco-based STM appliances are special builds for specific markets, and they may use software releases (e.g. 8.3) that include functionality not in the mainstream releases.  You can find the Getting Started guide in /opt/zeus on the appliance (and via the Admin Interface once you complete initial configuration).

flyddw
Contributor

Re: Can't assign non 192.168.1.x address to STM (ver 8.3)

Thanks for answering. I've trying this last time, and since I'm using a Java KVM, I can't do a cut and paste. I've typed up what I saw:

To configure this appliance, please visit

the web-based Administration Server.

192.168.1.101 login: admin

Password:

Last Login: Wed Fed 27 13:52:22 PST 2013 on tty2

Last Login: 2013-02-27 21:52:22 -08000 from (Console) on zxtm.

-------------------------------------------------------------------------

Stingray Traffic Manager Maintenance CLI

Type 'help' for information on available commands.

-------------------------------------------------------------------------

Maintenance ID:  xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx

-------------------------------------------------------------------------

> z-set-initial-address

Error: Unknown command 'z-set-initial-address'. Type 'help' for a list of

available commands.

> help

help <command>

Prints out help information on the supplied command.

Commands:

  exit (logout, quit)

  firewall-clear

  info

  join-world

  networt-configure

  new-world

  racs

  reboot

  reset-to-factory-defaults

  restart

  rollback-delete

  rollback-list

  rollback-to

  shutdown

  start

  stop

  tcpdump

  trace

  world-status

owen
Frequent Contributor

Re: Can't assign non 192.168.1.x address to STM (ver 8.3)

Hi Derek - your appliance is running in a 'locked down' configuration.  In this case, please create a support case and our technical support team will assist you.  Owen

flyddw
Contributor

Re: Can't assign non 192.168.1.x address to STM (ver 8.3)

Thanks again.

I had to jump thru some physically hoops, but I took a laptop to the server, and forced a static IP of 192.168.1.200, and connected via web interface.

I was then able to change the IP address, and can proceed to login from my desktop now.

So...upward and onward to configuring it now.  Thanks again.

Derek