LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Server (https://www.linuxquestions.org/questions/linux-server-73/)
-   -   I have Problem In me server *NETWORK* (https://www.linuxquestions.org/questions/linux-server-73/i-have-problem-in-me-server-%2Anetwork%2A-808588/)

manuel19 05-18-2010 07:48 AM

I have Problem In me server *NETWORK*
 
Hi, i have a Pentium 4, exactly the same as the CPU in the picture
http://i39.tinypic.com/sb7sed.jpg
and sometimes my network go down without reason, at least i don't know why. I know that sometimes it go down because my ping test fails replying
Ping request time out.
But is just sometimes and then a few seconds it come up again....
in that server is running a PBX service and the OS running there is Fedora Core 8. Everything is running well excluding the network device (the network device is integrated in the motherboard)

What you recommend me?
When i run lspci in the command line i get this output


Code:

[root@TornadoR3 ~]# lspci -m
00:00.0 "Host bridge" "Intel Corporation" "82845G/GL[Brookdale-G]/GE/PE DRAM Controller/Host-Hub Interface" -r01 "" ""
00:02.0 "VGA compatible controller" "Intel Corporation" "82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device" -r01 "Compaq Computer Corporation" "Evo D510 SFF"
00:1d.0 "USB Controller" "Intel Corporation" "82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1" -r01 "Compaq Computer Corporation" "Unknown device 00b9"
00:1d.1 "USB Controller" "Intel Corporation" "82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2" -r01 "Compaq Computer Corporation" "Unknown device 00b9"
00:1d.7 "USB Controller" "Intel Corporation" "82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller" -r01 -p20 "Compaq Computer Corporation" "Unknown device 00b9"
00:1e.0 "PCI bridge" "Intel Corporation" "82801 PCI Bridge" -r81 "" ""
00:1f.0 "ISA bridge" "Intel Corporation" "82801DB/DBL (ICH4/ICH4-L) LPC Interface Bridge" -r01 "" ""
00:1f.1 "IDE interface" "Intel Corporation" "82801DB (ICH4) IDE Controller" -r01 -p8a "Compaq Computer Corporation" "Unknown device 00b9"
00:1f.5 "Multimedia audio controller" "Intel Corporation" "82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller" -r01 "Compaq Computer Corporation" "Unknown device 00ad"
05:08.0 "Ethernet controller" "Intel Corporation" "82801DB PRO/100 VM (LOM) Ethernet Controller" -r81 "Compaq Computer Corporation" "Unknown device 0012"
05:09.0 "Communication controller" "Tiger Jet Network Inc." "Tiger3XX Modem/ISDN interface" "Unknown vendor b100" "Unknown device 0003"
[root@TornadoR3 ~]#


centosboy 05-18-2010 07:56 AM

Quote:

Originally Posted by manuel19 (Post 3972721)
Hi, i have a Pentium 4, exactly the same as the CPU in the picture
http://i39.tinypic.com/sb7sed.jpg
and sometimes my network go down without reason, at least i don't know why. I know that sometimes it go down because my ping test fails replying
Ping request time out.
But is just sometimes and then a few seconds it come up again....
in that server is running a PBX service and the OS running there is Fedora Core 8. Everything is running well excluding the network device (the network device is integrated in the motherboard)

What you recommend me?
When i run lspci in the command line i get this output


Code:

[root@TornadoR3 ~]# lspci -m
00:00.0 "Host bridge" "Intel Corporation" "82845G/GL[Brookdale-G]/GE/PE DRAM Controller/Host-Hub Interface" -r01 "" ""
00:02.0 "VGA compatible controller" "Intel Corporation" "82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device" -r01 "Compaq Computer Corporation" "Evo D510 SFF"
00:1d.0 "USB Controller" "Intel Corporation" "82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1" -r01 "Compaq Computer Corporation" "Unknown device 00b9"
00:1d.1 "USB Controller" "Intel Corporation" "82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2" -r01 "Compaq Computer Corporation" "Unknown device 00b9"
00:1d.7 "USB Controller" "Intel Corporation" "82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller" -r01 -p20 "Compaq Computer Corporation" "Unknown device 00b9"
00:1e.0 "PCI bridge" "Intel Corporation" "82801 PCI Bridge" -r81 "" ""
00:1f.0 "ISA bridge" "Intel Corporation" "82801DB/DBL (ICH4/ICH4-L) LPC Interface Bridge" -r01 "" ""
00:1f.1 "IDE interface" "Intel Corporation" "82801DB (ICH4) IDE Controller" -r01 -p8a "Compaq Computer Corporation" "Unknown device 00b9"
00:1f.5 "Multimedia audio controller" "Intel Corporation" "82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller" -r01 "Compaq Computer Corporation" "Unknown device 00ad"
05:08.0 "Ethernet controller" "Intel Corporation" "82801DB PRO/100 VM (LOM) Ethernet Controller" -r81 "Compaq Computer Corporation" "Unknown device 0012"
05:09.0 "Communication controller" "Tiger Jet Network Inc." "Tiger3XX Modem/ISDN interface" "Unknown vendor b100" "Unknown device 0003"
[root@TornadoR3 ~]#





show packet counters on said network device


Code:


ifconfig <ethX>

check network interface is operating at correct speed and duplex

Code:

mii-tool -v

or if your device does not support MII, use ethtool


Code:

ethtool <ethX>

show some logs

manuel19 05-18-2010 09:09 AM

RE:
 
Hi, look i recently execute this
vi /var/log/messages and i read something like i ave to install nss-mdn
so i download the nss-mdn RPM file...
Now i proceed to execute each command you said...

ifconfig output:
Code:

[root@TornadoR3 ~]# ifconfig
eth1      Link encap:Ethernet  HWaddr 00:08:02:F9:AB:FF
          inet addr:10.0.1.217  Bcast:0.0.0.0  Mask:255.255.255.0
          inet6 addr: fe80::208:2ff:fef9:abff/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:51256 errors:0 dropped:0 overruns:0 frame:0
          TX packets:51662 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:10678052 (10.1 MiB)  TX bytes:12461723 (11.8 MiB)

eth1:3    Link encap:Ethernet  HWaddr 00:08:02:F9:AB:FF
          inet addr:10.0.1.112  Bcast:10.0.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:1017 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1017 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:287085 (280.3 KiB)  TX bytes:287085 (280.3 KiB)

[root@TornadoR3 ~]#





mii-tool -v
Code:

[root@TornadoR3 ~]# mii-tool -v
eth1: negotiated 100baseTx-FD, link ok
  product info: vendor 00:aa:00, model 50 rev 0
  basic mode:  autonegotiation enabled
  basic status: autonegotiation complete, link ok
  capabilities: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
  advertising:  100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD flow-control
  link partner: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
[root@TornadoR3 ~]#


ethtool eth1
Code:

[root@TornadoR3 ~]# ethtool eth1
Settings for eth1:
        Supported ports: [ TP MII ]
        Supported link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
        Supports auto-negotiation: Yes
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
        Advertised auto-negotiation: Yes
        Speed: 100Mb/s
        Duplex: Full
        Port: MII
        PHYAD: 1
        Transceiver: internal
        Auto-negotiation: on
        Supports Wake-on: g
        Wake-on: g
        Current message level: 0x00000007 (7)
        Link detected: yes
[root@TornadoR3 ~]#

What you think about this outputs and about my problem?

centosboy 05-18-2010 09:25 AM

Quote:

Originally Posted by manuel19 (Post 3972811)
Hi, look i recently execute this
vi /var/log/messages and i read something like i ave to install nss-mdn
so i download the nss-mdn RPM file...
Now i proceed to execute each command you said...

ifconfig output:
Code:

[root@TornadoR3 ~]# ifconfig
eth1      Link encap:Ethernet  HWaddr 00:08:02:F9:AB:FF
          inet addr:10.0.1.217  Bcast:0.0.0.0  Mask:255.255.255.0
          inet6 addr: fe80::208:2ff:fef9:abff/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:51256 errors:0 dropped:0 overruns:0 frame:0
          TX packets:51662 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:10678052 (10.1 MiB)  TX bytes:12461723 (11.8 MiB)

eth1:3    Link encap:Ethernet  HWaddr 00:08:02:F9:AB:FF
          inet addr:10.0.1.112  Bcast:10.0.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:1017 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1017 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:287085 (280.3 KiB)  TX bytes:287085 (280.3 KiB)

[root@TornadoR3 ~]#





mii-tool -v
Code:

[root@TornadoR3 ~]# mii-tool -v
eth1: negotiated 100baseTx-FD, link ok
  product info: vendor 00:aa:00, model 50 rev 0
  basic mode:  autonegotiation enabled
  basic status: autonegotiation complete, link ok
  capabilities: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
  advertising:  100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD flow-control
  link partner: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
[root@TornadoR3 ~]#


ethtool eth1
Code:

[root@TornadoR3 ~]# ethtool eth1
Settings for eth1:
        Supported ports: [ TP MII ]
        Supported link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
        Supports auto-negotiation: Yes
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
        Advertised auto-negotiation: Yes
        Speed: 100Mb/s
        Duplex: Full
        Port: MII
        PHYAD: 1
        Transceiver: internal
        Auto-negotiation: on
        Supports Wake-on: g
        Wake-on: g
        Current message level: 0x00000007 (7)
        Link detected: yes
[root@TornadoR3 ~]#

What you think about this outputs and about my problem?


i dont think nss has anything to do with the problem.



i think you will have to use normal network troubleshooting techniques from a remote host or another host on the network
..

any of

ping
traceroute
netstat
mtr


might help you find the problem.
also tail the message log file. and check dmesg too.

Code:


tail -f /var/log/messages


Code:

dmesg

manuel19 05-18-2010 10:12 AM

RE:
 
Look, before i install nss-mdn in /var/log/messages the file content has this lines

May 17 19:54:50 TornadoR3 avahi-daemon[2084]: avahi-daemon 0.6.21 starting up.
May 17 19:54:50 TornadoR3 avahi-daemon[2084]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
May 17 19:54:50 TornadoR3 avahi-daemon[2084]: Successfully called chroot().

Now before installed the nss-mdn RPM file hte /var/log/messages
have this line


May 17 19:54:50 TornadoR3 avahi-daemon[2084]: avahi-daemon 0.6.21 starting up.
May 17 19:54:50 TornadoR3 avahi-daemon[2084]: Successfully called chroot().

Look that the line
May 17 19:54:50 TornadoR3 avahi-daemon[2084]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns! Is not present... and now the ping test don't fail... What you think, is this the nss-mdn the Solution or is just coincidence?

centosboy 05-18-2010 11:00 AM

Quote:

Originally Posted by manuel19 (Post 3972882)
Look, before i install nss-mdn in /var/log/messages the file content has this lines

May 17 19:54:50 TornadoR3 avahi-daemon[2084]: avahi-daemon 0.6.21 starting up.
May 17 19:54:50 TornadoR3 avahi-daemon[2084]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
May 17 19:54:50 TornadoR3 avahi-daemon[2084]: Successfully called chroot().

Now before installed the nss-mdn RPM file hte /var/log/messages
have this line


May 17 19:54:50 TornadoR3 avahi-daemon[2084]: avahi-daemon 0.6.21 starting up.
May 17 19:54:50 TornadoR3 avahi-daemon[2084]: Successfully called chroot().

Look that the line
May 17 19:54:50 TornadoR3 avahi-daemon[2084]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns! Is not present... and now the ping test don't fail... What you think, is this the nss-mdn the Solution or is just coincidence?



are the pings still failing??
mdns uses multicast to find hosts on a small network, so it could have been the problem,but the question is - is ping working ok now?

manuel19 05-18-2010 11:53 AM

RE:
 
Yes, for now the ping test doesn't fail anymore.
But i will still testing using more ping tests to be sure that that was the solution to the problem.
Thanks, buddy if me problem still there, i will write to contact you again :D.

manuel19 05-18-2010 02:36 PM

RE:
 
Sorry, I still have the same problem
i make ping for some hours and
Of 8247 sent packages just 8084 was received.
Please, what can i do? In this cpu is running a PBX system and the calls sometimes are dropped by this.


All times are GMT -5. The time now is 10:09 PM.