园区间业务系统访问故障处理

故障现象:

客户反映园区仓库访问NC系统速度很慢,从园区ping NC服务器地址时有严重的丢包现象。如下图所示:

wKiom1gz1DKi117aAAKQFNfloAw338.png-wh_50

wKiom1gz1DOx2rwHAAFuqD6gfac287.png-wh_50


处理过程:

登录用户两个园区的核心发现,两个园区的portchannel连接正常,但是其中一个园区portchannel成员端口下存在严重的CRC校验错误,如下图所示:

wKioL1gz08HDzqxmAALCiT0OPh0626.png-wh_50

此时关闭端口ten1/5/1,数据转发从另一个端口走,关闭后再次PING NC服务器,数据包正常

wKioL1gz1KDgfrB5AAFB4YDNDbs447.png-wh_50

wKiom1gz1KCTa0kNAAFlB_3Ct-w146.png-wh_50

为进一步确认该故障,再次对ten1/5/1进行开启操作,但打开后发现,问题立即出现

SW#ping 192.168.x.x repeat 1000 source 192.168.x.x

Type escape sequence to abort.

Sending 1000, 100-byte ICMP Echos to 192.168.x.x, timeout is 2 seconds:

Packet sent with a source address of 192.168.x.x

!!!!!!!!!!!!!!!!!!!!.!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!.!!!!!!.!!!!!!!!!!!!!!!!!!!!

!!!!!!!!!!!!!!!!!!!!!!!!!!!.!!!!!!!.!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!!!!!!!!!!!!!!!.!!!!!!!!!!!!!!!!!!!.!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!!!!!.!!!!!!!!!!!!!!!!!!!!.!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!!!!!!!!!!!!.!!!!!!!!!!!!!.!!!!!!!!!!!!!!!!!!!!!!!.!!!!!!!!!!!!!!!!!!!

!!!!!!!!.!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!!!!!!!!!!!!!!.!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!.!!!!!!!!!!!!!!!!!!!!!!!!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!!!!!!!!!!.!!!!!!!!!!!!!!!!!..!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!.!!!!

!!!!!!!!!!!!!!!!!!!!!.!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!.!!!.!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!!!!!!!!!!!!!!!!!!!!

Success rate is 97 percent (978/1000), round-trip min/avg/max = 1/2/20 ms

SW#sh int ten1/5/1

TenGigabitEthernet1/5/1 is up, line protocol is up (connected)

  Hardware is Ten Gigabit Ethernet Port, address is 78da.6e07.7b7a (bia 78da.6e07.7b7a)

  Description: connection to laishanchangqu

  MTU 1500 bytes, BW 10000000 Kbit/sec, DLY 10 usec,

     reliability 245/255, txload 1/255, rxload 1/255

  Encapsulation ARPA, loopback not set

  Keepalive set (10 sec)

  Full-duplex, 10Gb/s, link type is auto, media type is 10GBase-ER

  input flow-control is on, output flow-control is on

  ARP type: ARPA, ARP Timeout 04:00:00

  Last input 00:00:03, output never, output hang never

  Last clearing of "show interface" counters never

  Input queue: 0/2000/0/0 (size/max/drops/flushes); Total output drops: 0

  Queueing strategy: fifo

  Output queue: 0/40 (size/max)

  5 minute input rate 3209000 bits/sec, 358 packets/sec

  5 minute output rate 926000 bits/sec, 685 packets/sec

     4935914010 packets input, 5278619447870 bytes, 0 no buffer

     Received 87068 broadcasts (87050 multicasts)

     0 runts, 0 giants, 0 throttles

     277020288 input errors, 277020288 CRC, 0 frame, 0 overrun, 0 ignored

     0 input packets with dribble condition detected

     9064745454 packets output, 3287137727436 bytes, 0 underruns

     0 output errors, 0 collisions, 4 interface resets

     0 unknown protocol drops

     0 babbles, 0 late collision, 0 deferred

     0 lost carrier, 0 no carrier

     0 output buffer failures, 0 output buffers swapped out

SW#conf t

Enter configuration commands, one per line.  End with CNTL/Z.

SW(config)#int ten1/5/1

SW(config-if)#shut

SW(config-if)#do sh run int ten1/5/1

Building configuration...

 

Current configuration : 171 bytes

!

interface TenGigabitEthernet1/5/1

 switchport access vlan 133

 switchport mode access

 shutdown

 channel-group 10 mode on

end

 

SW(config-if)#exit

SW(config)#exit

SW#wr

Building configuration...

Compressed configuration from 21267 bytes to 7568 bytes[OK]

SW#ping 192.168.x.x repeat 1000 source 192.168.x.x

Type escape sequence to abort.

Sending 1000, 100-byte ICMP Echos to 192.168.x.x timeout is 2 seconds:

Packet sent with a source address of 192.168.x.x

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!!!!!!!!!!!!!!!!!!!!

Success rate is 100 percent (1000/1000), round-trip min/avg/max = 1/2/20 ms


经最终确认,NC访问问题主要是由于该端口的CRC校验错误引起。


解决建议:

1、检查两厂区之间的链路

2、检查模块

3、检查尾纤


                                                               *********************

终:

       第二天测试两个园区之间的链路,发现一根光纤的衰减在-21左右,而该接口上的万兆模块可接受的衰减最小值是-15.8,后来运营商对线路进行调优检测,最终恢复正常,测试,网络访问正常

                                                               *********************









本文转自 弯月楼主 51CTO博客,原文链接:http://blog.51cto.com/05wylz/1875378,如需转载请自行联系原作者
### 关于智慧园区招商管理系统的实现方案 #### 系统架构设计 智慧园区招商管理系统通常采用分层架构设计,分为前端交互层、业务逻辑层以及数据存储层。这种结构能够有效分离关注点,提高开发效率和系统可维护性。 - **前端交互层**:主要面向用户操作界面的设计与实现,支持多种终端访问(PC端、移动端),通过现代框架 Vue.js 提供动态用户体验[^2]。 - **业务逻辑层**:该部分负责处理核心功能模块的逻辑运算和服务调用,例如投资政策协作管理中的跨部门沟通机制[^1]。此层次可以利用 Spring Boot 来快速搭建微服务环境,从而增强系统的灵活性和扩展能力。 - **数据存储层**:用于持久化保存各类信息资源,包括但不限于项目详情、部门互动历史等重要资料。推荐选用关系型数据库 MySQL 或者 NoSQL 数据库 MongoDB 根据实际需求选择合适的数据管理模式。 #### 技术选型分析 为了满足高效稳定运行的要求,在技术栈方面需谨慎考量: - 前端技术:Vue.js 结合 Element UI 组件库构建响应式布局页面,简化样式定义流程的同时保证视觉一致性[^2]; - 后端框架:Spring Cloud 微服务体系作为基础支撑平台,配合 MyBatis 进行 ORM 映射操作,优化 SQL 查询性能; - 中件应用:Redis 缓存热点数据减少重复计算开销,RabbitMQ 实现异步消息队列传输保障实时通知推送效果; - 安全防护措施:JWT (JSON Web Token) 认证授权方式保护敏感接口免受未授权访问威胁,HTTPS 协议加密网络通信防止窃听篡改行为发生。 ```java // 示例代码片段 - 使用 JWT 验证登录状态 @RestController public class AuthController { @PostMapping("/login") public ResponseEntity<?> authenticateUser(@RequestBody LoginRequest loginRequest){ Authentication authentication = authenticationManager.authenticate( new UsernamePasswordAuthenticationToken(loginRequest.getUsername(), loginRequest.getPassword()) ); SecurityContextHolder.getContext().setAuthentication(authentication); String jwt = tokenProvider.generateToken(authentication); return ResponseEntity.ok(new JwtResponse(jwt)); } } ``` #### 功能模块规划 依据引用描述内容可知,完整的智慧园区招商管理系统应至少涵盖以下几个关键子系统及其对应的功能要点: - **投资政策协作管理** - 创建任务工单提交至相关部门审批; - 自动追踪每一步骤完成状况直至最终关闭结案; - 归档所有交流文档备查以便后续审计工作开展。 - **物业综合管控中心** - 制定详细的规章制度并向全体住户公开宣导; - 登记日常巡查发现的问题安排专人解决跟进整改进度; - 设置固定周期养护计划确保公共空整洁美观度达标。 - **资产管理服务平台** - 对固定资产实施编号登记造册便于查询盘点; - 接收业主申报故障请求迅速派遣技术人员上门检修恢复正常使用; - 跟踪记录每次保养活动积累经验教训促进持续改进质量水平。 ---
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值