网络建设相关问题，求大神帮忙。_seo吧_百度贴吧
&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&签到排名：今日本吧第个签到，本吧因你更精彩，明天继续来努力！
本吧签到人数：0成为超级会员，使用一键签到本月漏签0次！成为超级会员，赠送8张补签卡连续签到：天&&累计签到：天超级会员单次开通12个月以上，赠送连续签到卡3张
关注：240,977贴子：
网络建设相关问题，求大神帮忙。收藏
这个网站之前是用做汽车的模板
最后改到这里，发布图片
出现这个情况产品名称什么的
都改过了，不知道是哪里的原因 ，求大神帮忙啊。
「达内」seo培训,人手一个SEO优化网站,名企实战优化,90天速成SEO专家!达内seo培训,上市公司,培养懂营销,会策划,精技术,善实战的SEO高端人才!
那么大的贴吧
竟然没人？？？
没有知道的吗
登录百度帐号推荐应用
为兴趣而生，贴吧更懂你。或你查询的内容不存在已有96人收藏
查看: 5834|回复: 16
求网络大神帮忙分析网络掉线的原因
公司用的10M光纤接进机房的。
连接了H3C MSR20-11路由器。下面接的交换机和10几台服务器。&&
从上周开始每天突然断网四五次。。断了后20多秒就自动连接上正常了。断的时候所有的客户端都断线。
ping 网关192.168.1.1也不通。Ping外网的网址也不通。。
断网时使用arp -a查看，网关的IP和MAC都是正确的，和没断网时是一样的。
客户端也全部杀毒了，排除了arp病毒问题。
请大神们帮忙分析分析原因。
路由器的日志显示端口反复的up/down。
我给联通负责光纤的工程师打电话，
他说是可能是网线没插好，或者是光纤收发器问题、也有可能是华三路由器问题。
下面是断网时显示的日志。请大家帮忙看看原因在哪里。。是不是需要联通的去机房检测一下路由器和收发器。
&H3C&dis log
Logging buffer configuration and contents:enabled
Allowed max buffer size : 1024
Actual buffer size : 512
Channel number : 4 , Channel name : logbuffer
Dropped messages : 0
Overwritten messages : 3
Current messages : 512
%Jan&&1 00:01:29:721 2007 H3C IFNET/3/LINK_UPDOWN: Ethernet0/0 link status is UP
%Jan&&1 00:01:29:721 2007 H3C IFNET/5/LINEPROTO_UPDOWN: Line protocol on the int
erface Ethernet0/0 is UP.
%Jan&&1 00:01:29:722 2007 H3C IFNET/3/LINK_UPDOWN: Ethernet0/1 link status is UP
%Jan&&1 00:01:29:722 2007 H3C IFNET/3/LINK_UPDOWN: Ethernet0/2 link status is UP
%Jan&&1 00:01:29:816 2007 H3C IFNET/3/LINK_UPDOWN: Vlan-interface1 link status i
%Jan&&1 00:01:29:816 2007 H3C IFNET/5/LINEPROTO_UPDOWN: Line protocol on the int
erface Vlan-interface1 is UP.
%Jan&&1 00:03:45:114 2007 H3C DHCPSD/5/DHCPS_ALLOCATE_IP: DHCP server informatio
n: Server IP = 192.168.1.1, DHCP client IP = 192.168.1.6, DHCP client hardware a
ddress = 001b-e, DHCP client lease = 86400.
%Jan&&1 05:05:14:962 2007 H3C SC/6/SC_AAA_LAUNCH: -AAAType=AUTHEN-AAAScheme= loc
al-Service=login-UserName=root@ AAA launched.
%Jan&&1 05:05:14:963 2007 H3C SHELL/5/SHELL_LOGINFAIL:&&TELNET user root failed
to log in from 197.7.65.22 on VTY0.
%Jan&&1 08:36:17:821 2007 H3C SHELL/5/SHELL_LOGINFAIL:&&TELNET user root failed
to log in from 59.165.108.194 on VTY0.
%Jan&&1 08:36:17:821 2007 H3C SC/6/SC_AAA_LAUNCH: -AAAType=AUTHEN-AAAScheme= loc
al-Service=login-UserName=root@ AAA launched.
%Jan&&1 16:12:33:373 2007 H3C DHCPSD/5/DHCPS_ALLOCATE_IP: DHCP server informatio
n: Server IP = 192.168.1.1, DHCP client IP = 192.168.1.10, DHCP client hardware
address = 8c89-a570-32c6, DHCP client lease = 86400.
%Jan&&1 16:16:35:474 2007 H3C DHCPSD/5/DHCPS_ALLOCATE_IP: DHCP server informatio
n: Server IP = 192.168.1.1, DHCP client IP = 192.168.1.11, DHCP client hardware
address = f0de-f160-c3b0, DHCP client lease = 86400.
%Jan&&1 16:27:04:973 2007 H3C DHCPSD/5/DHCPS_ALLOCATE_IP: DHCP server informatio
n: Server IP = 192.168.1.1, DHCP client IP = 192.168.1.7, DHCP client hardware a
ddress = f0de-f1e8-ff33, DHCP client lease = 86400.
%Jan&&1 16:30:39:542 2007 H3C DHCPSD/5/DHCPS_ALLOCATE_IP: DHCP server informatio
n: Server IP = 192.168.1.1, DHCP client IP = 192.168.1.12, DHCP client hardware
address = f0de-f1e8-f0a6, DHCP client lease = 86400.
%Jan&&1 16:42:26:973 2007 H3C DHCPSD/5/DHCPS_ALLOCATE_IP: DHCP server informatio
n: Server IP = 192.168.1.1, DHCP client IP = 192.168.1.8, DHCP client hardware a
ddress = f0de-f142-e714, DHCP client lease = 86400.
%Jan&&1 17:39:52:504 2007 H3C DHCPSD/5/DHCPS_ALLOCATE_IP: DHCP server informatio
n: Server IP = 192.168.1.1, DHCP client IP = 192.168.1.14, DHCP client hardware
address = 4437-e6ae-320d, DHCP client lease = 86400.
%Jan&&1 18:16:00:904 2007 H3C DHCPSD/5/DHCPS_ALLOCATE_IP: DHCP server informatio
n: Server IP = 192.168.1.1, DHCP client IP = 192.168.1.17, DHCP client hardware
address = 001f-d048-016c, DHCP client lease = 86400.
%Jan&&1 19:17:39:004 2007 H3C SC/6/SC_AAA_LAUNCH: -AAAType=AUTHEN-AAAScheme= loc
al-Service=login-UserName=telnet@ AAA launched.
%Jan&&1 19:17:39:005 2007 H3C SC/6/SC_AAA_SUCCESS: -AAAType=AUTHEN-AAAScheme= lo
cal-Service=login-UserName=telnet@ AAA is successful.
%Jan&&1 19:17:39:005 2007 H3C SC/6/SC_AAA_LAUNCH: -AAAType=AUTHOR-AAAScheme= loc
al-Service=login-UserName=telnet@ AAA launched.
%Jan&&1 19:17:39:006 2007 H3C SC/6/SC_AAA_SUCCESS: -AAAType=AUTHOR-AAAScheme= lo
cal-Service=login-UserName=telnet@ AAA is successful.
%Jan&&1 19:17:39:007 2007 H3C SC/6/SC_AAA_LAUNCH: -AAAType=ACCOUNT-AAAScheme= lo
cal-Service=login-UserName=telnet@ AAA launched.
&H3C&dis log
Logging buffer configuration and contents:enabled
Allowed max buffer size : 1024
Actual buffer size : 512
Channel number : 4 , Channel name : logbuffer
Dropped messages : 0
Overwritten messages : 56
Current messages : 512
%Jan&&1 22:51:57:782 2007 H3C SC/6/SC_AAA_LAUNCH: -AAAType=AUTHEN-AAAScheme= lo
al-Service=login-UserName=root@ AAA launched.
%Jan&&1 22:51:57:783 2007 H3C SHELL/5/SHELL_LOGINFAIL:&&TELNET user root failed
to log in from 115.197.248.169 on VTY1.
%Jan&&1 22:52:00:559 2007 H3C SC/6/SC_AAA_LAUNCH: -AAAType=AUTHEN-AAAScheme= lo
al-Service=login-UserName=root@ AAA launched.
%Jan&&1 22:52:00:561 2007 H3C SHELL/5/SHELL_LOGINFAIL:&&TELNET user root failed
to log in from 115.197.248.169 on VTY0.
%Jan&&1 22:52:05:360 2007 H3C SC/6/SC_AAA_LAUNCH: -AAAType=AUTHEN-AAAScheme= lo
al-Service=login-UserName=admin@ AAA launched.
%Jan&&1 22:52:05:364 2007 H3C SHELL/5/SHELL_LOGINFAIL:&&TELNET user admin faile
to log in from 115.197.248.169 on VTY1.
%Jan&&1 22:52:07:694 2007 H3C SC/6/SC_AAA_LAUNCH: -AAAType=AUTHEN-AAAScheme= lo
al-Service=login-UserName=root@ AAA launched.
%Jan&&1 22:52:07:695 2007 H3C SHELL/5/SHELL_LOGINFAIL:&&TELNET user root failed
to log in from 115.197.248.169 on VTY0.
%Jan&&1 22:52:10:559 2007 H3C SC/6/SC_AAA_LAUNCH: -AAAType=AUTHEN-AAAScheme= lo
al-Service=login-UserName=admin@ AAA launched.
%Jan&&1 22:52:10:561 2007 H3C SHELL/5/SHELL_LOGINFAIL:&&TELNET user admin faile
to log in from 115.197.248.169 on VTY1.
%Jan&&2 01:39:17:058 2007 H3C SC/6/SC_AAA_LAUNCH: -AAAType=AUTHEN-AAAScheme= lo
al-Service=login-UserName=root@ AAA launched.
%Jan&&2 01:39:17:059 2007 H3C SHELL/5/SHELL_LOGINFAIL:&&TELNET user root failed
to log in from 197.7.21.81 on VTY0.
%Jan&&2 04:24:07:763 2007 H3C SC/6/SC_AAA_LAUNCH: -AAAType=AUTHEN-AAAScheme= lo
al-Service=login-UserName=telnet@ AAA launched.
%Jan&&2 04:24:07:764 2007 H3C SC/6/SC_AAA_SUCCESS: -AAAType=AUTHEN-AAAScheme= l
cal-Service=login-UserName=telnet@ AAA is successful.
%Jan&&2 04:24:07:764 2007 H3C SC/6/SC_AAA_LAUNCH: -AAAType=AUTHOR-AAAScheme= lo
al-Service=login-UserName=telnet@ AAA launched.
%Jan&&2 04:24:07:764 2007 H3C SC/6/SC_AAA_SUCCESS: -AAAType=AUTHOR-AAAScheme= l
cal-Service=login-UserName=telnet@ AAA is successful.
%Jan&&2 04:24:07:765 2007 H3C SC/6/SC_AAA_LAUNCH: -AAAType=ACCOUNT-AAAScheme= l
cal-Service=login-UserName=telnet@ AAA launched.
%Jan&&2 04:24:07:766 2007 H3C SC/6/SC_AAA_SUCCESS: -AAAType=ACCOUNT-AAAScheme=
ocal-Service=login-UserName=telnet@ AAA is successful.
%Jan&&2 04:24:07:768 2007 H3C SHELL/5/SHELL_LOGIN: telnet logged in from 116.11
%Jan&&2 04:24:12:443 2007 H3C SHELL/6/SHELL_CMD: -Task=vt0-IPAddr=116.113.89.19
-User= Command is ping 172.16.1.3
%Jan&&2 04:24:14:645 2007 H3C PING/6/PING_LOG: 172.16.1.3 ping statistics: 1 pa
ket(s) 0 packet(s) packet loss: 100.00%.
%Jan&&2 04:24:16:307 2007 H3C SHELL/6/SHELL_CMD: -Task=vt0-IPAddr=116.113.89.19
-User= Command is ping 172.16.1.4
%Jan&&2 04:24:20:510 2007 H3C PING/6/PING_LOG: 172.16.1.4 ping statistics: 2 pa
ket(s) 0 packet(s) packet loss: 100.00%.
&&---- More ----
精彩评论 16
发帖辛苦了,楼主 支持
感觉像路由器问题 如果光纤收发器有问题的话 内网ping网关不会不通 你找个别的路由器替换一下吧
顶下 :default4:
DHCP冲突呀，可能是ARP病毒之类的东东。
你i内网网关应该是在路由器上的吧，如果你所有的跳线都是好的，你掉线的时候ping内网的网关都不通，应该就是路由器的问题了，你可以进去看看路由器的配置，看看路由器的报错，试试找找看原因。
建议在路由器上绑定IP,MAC，在断网的时候CONSOL登陆路由器，测试一下外网
建议有备份的路由器没有 先替换个 试试
路过，什么接入交换机呀
display interface下，接口有无错误包？
在断网的时候做个流统计看一下，方法如下
在连PC和服务器的接口上进行如下操作：
acl number 3555
rule permit icmp source 10.100.2.5 0 destination 10.100.1.2 0
//使用ACL抓取对应的流量，这里要注意方向。
traffic classifier 1 operator and
if-match acl 3555
//使用classifier匹配下流量
traffic behavior 1
accounting
//定义流统计
qos policy 1
classifier 1 behavior 1
//定义QOS policy
interface GigabitEthernet0/1
qos apply policy 1 inbound
//在对应的接口上应用（这里要注意方向）
应用在2个接口
PC端口为inbound方向，&&服务器的端口为outbound方向
然后加载一个应用，匹配下我们抓取的流量，使用以下命令查看下流统计：
[H3C-GigabitEthernet1/0/42]dis qos po int g1/0/42
&&Interface: GigabitEthernet1/0/42
&&Direction: Outbound
&&Policy: 1
& &Classifier: 1
& &&&Operator: AND
& &&&Rule(s) : If-match acl 3000
& &&&Behavior: 1
& && &Accounting Enable:
& && &&&5957 (Packets)
分别在多台设备上查看流量来计算丢包在那里，丢包率多少。（reset没有找到清空的选项，比较简单的清空统计方法就是接口下undo掉qos policy然后再应用下。）
扫描二维码，关注H3C微社区}