>>> On 11/19/2008 at 7:23 AM, LJ Mace <[EMAIL PROTECTED]> wrote: > First I check the routes and eth) set up(route/ ifconfig) > ifconfig eth0 10.14..80.41 netmask 255.255.255.0 broadcast 10.14.80.255 > This then kills my ssh session, so I then go to the VM console for this > machine > route add default gw 10.14.80.1 dev eth0 > (per instructions I don't have to have the dev stmt but I do for my own > sanity) > Then after a few minutes VM reports:
VM? That's Samba's nmbd process, not CP. > Nov 18 07:54:28 linux2 nmbd[960]: > Nov 18 07:54:28 linux2 nmbd[960]: Samba name server LINUX2 is now a local > master browser for workgroup DOMDOLC on subnet 10.14.80.41 This isn't much of an indication of anything. Samba will put out that message as long as the network interface is up, whether or not any traffic is flowing over it. -snip- > Login timed out after 60 seconds Which login is it that's timing out? > I then take a look(ifconfig) and get: > ifconfig > eth0 Link encap:Ethernet HWaddr 02:00:00:00:00:06 > inet addr:10.14.80.41 Bcast:10.14.80.255 Mask:255.255.255.0 This looks fine to me. What do you think is wrong with it? > The strange part is when I look at my routes again I dont get a default > route only the original. That seems a little odd. I would only expect that if the interface had been brought down and back up again after setting the route. > I have also tried deleting the default route then adding the new route with > the same results. So, where's the "network unreachable" error? I don't see that here. If I were doing what you're doing, I would try doing all the work from the z/VM guest's console. I would do: ifconfig eth0 ---> Take a look at how many bytes and packets have been sent and received so far ifconfig eth0 down ifconfig eth0 10.14.80.41/24 route add default gw 10.14.80.1 dev eth0 route -n ping -c 3 10.14.80.1 ---> This should work. If not, something is wrong. ifconfig eth0 ---> Again, look at the number of bytes and packets to see if they've changed. qetharp -q eth0 ---> Are there any entries in the ARP table? #cp q nic details #cp q vswitch detals Has the external switch been configured to route packets to the 10.14.80.0/24 network to the OSA? Are they doing any VLAN tagging? Are they running Layer 2 or Layer 3? Mark Post ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
