Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

5.0.7 cannot ping rest of network

Status
Not open for further replies.

ak714

Vendor
Aug 11, 2009
6
0
0
US
I have rebuilt a 5.0.7 server, cannot ping the gateway (172.16.1.1) or any other device on the network. Can ping itself (172.16.1.22) and the loopback (127.1.1.1).
I think i'm missing some routing but it looks ok.
Do I need to start/create any daemons?

Any suggestions.
 
No suspicious messages in /var/adm/syslog since the rebuild ?

Hope This Helps, PH.
FAQ219-2884
FAQ181-2886
 
Is it a duplicate license of an existing box on the network?

If it is and you need to transfer data from the existing box, you can restart the new box with the network cable disconnected and when it is up plug the cable in. It will complain but should allow you to transfer the data.
 
Shouldn't be a routing issue if you are trying to ping local IP's. What's the output of this command:
# ifconfig -a

It's plugged in, right? (sometime you have to ask those questions too).
Any chance the connection point is a managed switch that needs a bit of configuration before it allows traffic to flow? I've been there....

"Proof that there is intelligent life in Oregon. Well, Life anyway.
 
Here the ifconfig -a

# ifconfig -a
net1: flags=4043<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 172.16.1.22 netmask ffffff00 broadcast 172.16.1.255
perf. params: recv size: 32768; send size: 32768; full-size frames: 1
ether 00:c0:9f:24:3f:cf
lo0: flags=4049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 8232
inet 127.0.0.1 netmask ff000000
perf. params: recv size: 57344; send size: 57344; full-size frames: 1
atl0: flags=404a<BROADCAST,LOOPBACK,RUNNING,MULTICAST> mtu 8232
inet 0.0.0.0 netmask ff000000
perf. params: recv size: 4096; send size: 8192; full-size frames: 1

 
The syslog looks good, the network connection is good, with a known working connection to the switch. I tested it with another system.

Are there are processes that need to be started at bootup?
I also update the drivers for the nic Intel PRO/1000.

 
Here's a copy of the syslog

Aug 18 12:02:45 venus syslogd: restart
Aug 18 12:02:45 venus SCO OpenServer(TM) Release 5
Aug 18 12:02:45 venus
Aug 18 12:02:45 venus (C) 1976-2003 Caldera International, Inc. and its suppliers.
Aug 18 12:02:45 venus All rights reserved.
Aug 18 12:02:45 venus
Aug 18 12:02:45 venus For complete copyright credits,
Aug 18 12:02:45 venus enter "copyrights" at the command prompt.
Aug 18 12:02:45 venus
Aug 18 12:02:45 venus device address vec dma comment
Aug 18 12:02:45 venus -------------------------------------------------------------------------------
Aug 18 12:02:45 venus %kernel - - - rel=3.2v5.0.7 kid=2003-02-18
Aug 18 12:02:45 venus %cpu - - - unit=1 family=15 type=Intel Xeon
Aug 18 12:02:45 venus %cpuid - - - unit=1 vend=GenuineIntel tfms=0:15:2:7(11)
Aug 18 12:02:45 venus %fpu - 13 - unit=1 type=80387-compatible
Aug 18 12:02:45 venus %pci 0x0CF8-0x0CFF - - am=1 sc=0 buses=3
Aug 18 12:02:45 venus %PnP - - - nodes=0
Aug 18 12:02:45 venus %clock - - - type=TSC/2.392282769Ghz
Aug 18 12:02:45 venus %serial 0x03F8-0x03FF 4 - unit=0 type=Standard nports=1 base=0 16550A/16
Aug 18 12:02:45 venus %console - - - unit=vga type=0 num=12 scoansi=1 scroll=50
Aug 18 12:02:45 venus %mc - - - version=4.0.0r type=mc
Aug 18 12:02:45 venus mc: initialization error 23: Drive not found
Aug 18 12:02:45 venus sco_pmd[54]: PMD started - PID 55
Aug 18 12:02:45 venus %floppy 0x03F2-0x03F7 6 2 unit=0 type=135ds18
Aug 18 12:02:45 venus %kbmouse 0x0060-0x0064 12 - type=Keyboard|PS/2 mouse id=0x00
Aug 18 12:02:45 venus %udi - - - UDI environment
Aug 18 12:02:45 venus %adapter - - - ha=0 type=usb_msto UDI SCSI HBA
Aug 18 12:02:45 venus %adapter 0x0170-0x0177 15 - type=IDE ctlr=1 dvr=wd
Aug 18 12:02:45 venus %adapter 0xDC00-0xDC80 3 0 type=lsil ha=0 id=7 Chip=1030 10328
Aug 18 12:02:45 venus %eeG0 0xECC0-0xECDF 11 - type=PRO/1000 00:c0:9f:24:3f:cf
Aug 18 12:02:45 venus %cd-rom - - - type=IDE ctlr=1 cfg=slv unit=0 dvr=Srom->wd
Aug 18 12:02:45 venus %cd-rom - - - type=IDE ctlr=0 cfg=mst unit=1 dvr=Srom->wd
Aug 18 12:02:45 venus %tape - - - type=S ha=0 id=6 lun=0 bus=0 ht=lsil unit=0
Aug 18 12:02:45 venus %disk 0x0170-0x0177 15 - type=W1/0 unit=0 cyls=9729 hds=255 secs=63
Aug 18 12:02:45 venus %usb_ohci - 10 - PCI bus=0 dev=15 func=2
Aug 18 12:02:45 venus mem: total = 523836k, kernel = 73056k, user = 450780k
Aug 18 12:02:45 venus swapdev = 1/41, swplo = 0, nswap = 2095104, swapmem = 1047552k
Aug 18 12:02:46 venus rootdev = 1/42, pipedev = 1/42, dumpdev = 1/41
Aug 18 12:02:46 venus kernel: Hz = 100, i/o bufs = 51956k (high bufs = 50932k)
Aug 18 12:02:46 venus
Aug 18 12:02:45 venus sco_pmd[55]: *Notice* Unregistered SCO software is installed on your system.
Aug 18 12:02:45 venus sco_pmd[55]: Please refer to SCO's online help for registration information,
Aug 18 12:02:45 venus sco_pmd[55]: or access Aug 18 12:02:46 venus prngd[86]: prngd 0.9.29 (12 Jul 2004) started up for user root
Aug 18 12:02:46 venus prngd[86]: have 7 out of 110 filedescriptors open
Aug 18 12:03:10 venus noded[312]: Started
Aug 18 12:03:10 venus prngd[348]: socket /etc/egd-pool already used by another process, exiting.
Aug 18 12:03:10 venus snmpd[356]: Agent started (pid 356)
Aug 18 12:03:11 venus sshd[361]: Server listening on 0.0.0.0 port 22.
 
Since you mention routing... what's the output of netstat -rn?

Annihilannic.
 
Here's the netstat -rn

netstat -rn
Routing tables
Destination Gateway Flags Refs Use Interface
default 172.16.1.1 UGS 1 0 net1
127.0.0.1 127.0.0.1 UH 2 2 lo0
172.16.1 172.16.1.22 UC 1 0 net1
172.16.1.22 127.0.0.1 UGHS 4 36 lo0
224 172.16.1.22 UCS 0 0 net1
 
Nothing exciting there, which is good.

Perhaps try booting off a Linux live CD (Knoppix or similar) to eliminate the OS completely and see if the hardware is working at all.

Annihilannic.
 
This issue has been resolved, turns out the setup was ok and it was on the port I was connected to, only allowed a totally different subnet. Once I move the server into the correct port, everything was fine.

 
I think that the ip-network must be 192.xxx.xxx.xxx and not 172.xxx.xxx.xxx
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top