---------------------
Peter Zeiszler
When you changed the IP did you disable the second NIC and restart that NIC?
Does the first NIC and second NIC start with the same octet? I know on MU 4.4 we have the issue that the first octet has to be different or it will go out the default route of the system.
Peter, you've pointed out a procedural error on my part - I did not shut the interface down before I made the changes. I have, since reading this, gone back & disabled the interface
---------------------
Richard Whalen
SDA> SHOW LAN will tell you whether or not the interface is listening for IP packets, then the question becomes what sequence of MultiNet commands were done to stop the interface and start it with the new address. It's possible that old arp data would remain until it times out.
Richard, the old arp data was out there, but I did (after disabling the interface) go back and delete the old info
One more thing to show what MultiNet thinks the interface is using as an address:
$ define mu$sda multinet:multinet$sda
$ ana/sys
SDA> MU SHOW INTERFACE
a most handy set of commands to have - tnx:
SDA>
MultiNet Interface information:
Name IP address IPX address Flags SoftC IPkts OPkts
------ --------------- -------------------------- ---------------------- -------- -------- --------
se2 10.160.13.23 -none- Up,Brd,NoTrl,Run,Smpx, 90246678 ******** ********
se4 10.253.0.101 -none- Up,Brd,NoTrl,Run,Smpx, 90246B90 3324 6
lo0 127.0.0.1 -none- Up,Loop,NoTrl,MltC 9022C100 35248190 17624095
SDA>
SDA> exit
---------------------
Jim McKinney
> 192.168.1.32
As Hoff suggested you should insure that your subnet masking is all correct.
Sub-net matches a test system I have running in another cluster - I don't remember if I had to boot the node to get it to work or not (a year ago)
Have you attempted both inbound and outbound connections?
The out-bound isn't important, just the in-bound, but yes, I've tried both. Ping does not work either
Inbound connections should just work if the subnetting is correct and the surrounding network is correctly configured.
Sub-net is 255.255.255.0 - can't get much simpler I'd guess
For outbound connections, if there's a router on this subnet and it is not your default router/gateway, you'll need to add directives to your routing table to force outbound connections in that direction for certain targets that you wish to be reachable. Presuming class C subnetting, you might do the following
$ mu set/route/add=(dest=192.168.1.0, gate=xxx.xxx.xxx.xxx)/force_network
to force all outbound connections to that entire network (192.168.1.*) out through that interface (replace those x's with the address of the router on that network). Without such direction, outbound connections will be directed to your default gateway/router.
You may also want to force connections to some specific host out through that interface. For those you'd do something like
$ mu set/route/add=(dest=192.168.2.2, gate=xxx.xxx.xxx.xxx)
where the x's again represent your router and the 192.168.2.2 might be address of whatever host you're targetting.
If you end up having to set up these sorts of static routes you'll want to place the exact commands used to set them up into a file named MULTINET:LOCAL_ROUTES.COM and it will be executed during startup so that the routes will persist across reboots.
No router on the sub-net - just a 3com 10baseT hub that allows a dial-in modem to connect to either of 2 systems (the one in question will be #2)
> It's possible that old arp data would remain until it times out.
$ mu show/arp
$ mu set/arp/dele=10.253.0.101
thank you - I did & it did - it's gone now....
