swicthing iprb0 & spwr0 when upgrade from 3.x to 4.x signature

infinitingr2 · ‎05-24-2004

I am managing 8 4230FE NetRangers currently running old 3.1 sig. I read somewhere on Cisco www that PRIOR to upgrading from 3.x to 4.x one must change the cables so that the iprb0 which was normally used for command & control would now be used for capturing packets (monitoring interface whcih was formally spwr0) and vice versa. D problem is ifconfig -a doesn't show spwr0 but only iprb0. How do I assign IP address to the new command & control interface spwr0 which doesn't show up! Or does the mere change of the cable automatically reconfigue the interfaces so that now I get to see spwr0 using ifconfig -a.

In the same vein, if the goal is to "hide" iprb0 so that it doesn't show up on ifconfig -a, how do I then ensure that the old iprb0 remains hidden. I mean, just assigning no IP to it still doesn't mean that the interface would not come up in ifconfig -a

pcomeaux · ‎05-24-2004

When you perform the re-image of the sensors from 3.x to 4.x, the sensor will default to an IP address of 10.1.9.201.

You will need to bootstrap the sensor running 4.x code to change the IP address and other settings to communicate with your environment. Here's a link to getting started with a 4.x sensor: http://www.cisco.com/univercd/cc/td/doc/product/iaabu/csids/csids10/hwguide/hwchap9.htm

If you currently are using VMS, the configurations can be converted from 3.x to 4.x and deployed to the sensors once the re-image and bootstrap is complete. If not, all configuration on the sensors will NOT be retained.

Hope this helps. Let us know more about your situation and we can help further.

thanks

peter

infinitingr2 · ‎06-01-2004

I am able to log on to the IDS device using SSH and the netrangr account and later su -root. But although I got the # sign, when I issue the configure terminal command, it came back with a configure not found message.

Here is a screen capture...

Last login: Tue Jun 1 18:22:03 2004 from 10.31.166.30

Sun Microsystems Inc. SunOS 5.8 Generic February 2000

You have logged in from 10 using vt100

using DISPLAY=10:0

netrangr@nr-inside:/usr/nr

>su -root

Password:

Sun Microsystems Inc. SunOS 5.8 Generic February 2000

# configure terminal

configure: not found

#

I checked my working directory it was root. See below

# pwd

/root

# ls -al

total 25490

-rw-r--r-- 1 root other 7784 May 11 15:01 -r

drwxr-xr-x 4 root other 512 May 11 15:10 .

drwxr-xr-x 21 root root 512 May 20 16:03 ..

drwx------ 2 root root 512 Dec 6 2001 .ssh

-rw-r--r-- 1 root other 69680 May 11 15:00 r

drwxr-xr-x 2 root other 512 Dec 3 2003 tmp

What directory should I be in before I can issue the configure terminal command. I am logging in remotely using ssh. The device is IDS NetRanger 4235FE.

Thanks.

a.arndt · ‎06-04-2004

First off, I've noticed you're now using an IDS-4235FE, vice the IDS-4230FE of your original post. Obviously, the cable swap issue only applies to the older chassis.

Second, the commands your trying to use only apply to the CLI for CSIDS 4.x. Your sensor is still running 3.x, since the capture clearly shows that the x86 Solaris 8 OS is present.

CSIDS 4.x using an IOS-like user environment in the CLI, so you'll need to follow Peter Comeaux's advice offered in reply to your original post and upgrade your sensor(s) to 4.x in order to use any of the new commands.

I've been using Cisco IDS since the beginning, so I can say with some confidence that the whole 4.x experience is superior to everything that has come before it.

Alex Arndt