Issue Description
Topology : BAS--(eth-trunk0)---S9306(g1/0/1)====DSLAM---clients
The manage IP addresses of S9306 and dslam are both static users fo BAS device. And we cant ping from S9306 and DSLAM to BAS. But S9306 and DSLAM ping each other is normal.
Handling Process
1, As we found that hang DSLAM pc dialing is successful, pc to BAS link is smooth; simultaneously view up and down the line 9306 port, errors are 0;
2,And we confirmed the configuration is ok too.
4, S9306 supports access direction traffic statistics, and ETH-Trunk interface is also support for the issue provides a powerful tool to locate specific statistical methods are as follows:
First, the definition of good BAS to dslam and bas dslam to the icmp data stream:
[S9306-acl-adv-3031]rule per icmp s 10.191.124.218 0 des 10.191.124.220 0
[S9306-acl-adv-3030]rule per icmp source 10.191.124.220 0 des 10.191.124.218 0
Then do the traffic statistics action, binding C / B pair, traffic statistics defined strategy:
[S9306-behavior-tj]statistic enable
[S9306-1-trafficpolicy-BastoDSLAM]c BastoDSLAM b tj
[S9306-1-trafficpolicy-DSLAMtoBas]c DSLAMtoBas b tj
Then apply the policy direction in and out of the corresponding interface must be correct, then the S9300 BAS interface in the inbound direction, then the direction of the hair BastoDSLAM strategy under DSLAM; S9300 pick BAS interface in the outbound direction, then the inbound direction issued under DSLAM DSLAMtoBas strategy:
[S9306-1-Eth-Trunk0]traffic-policy BastoDSLAM in
[S9306-1-Eth-Trunk0]traffic-policy DSLAMtoBas out
Then on the bas active ping dslam 5 packets, viewed on 9306 traffic statistics and found two interfaces four directions values are 5, 9306 forwarding instructions properly:
<RH-S9306-1> dis traffic po st int Eth-Trunk 0 out
Interface: Eth-Trunk0
Traffic policy outbound: 5to2
Rule number: 1
Current status: OK!
Board : 4
Item Packets Bytes
---------------------------------------------------------------------
Matched 0 0
+--Passed 0 0
+--Dropped 0 0
+--Filter 0 0
+--URPF - -
+--CAR 0 0
Board : 5
Item Packets Bytes
---------------------------------------------------------------------
Matched 5 540
+--Passed 5 540
+--Dropped 0 0
+--Filter 0 0
+--URPF - -
+--CAR 0 0
After that BAS side check to make sure BAS exception.
Root Cause
Analysis:
1, link failure;
2, configuration issues;
3,9306 forwarding problem;
4, other equipment issues;
Suggestions
Available for inbound / outbond direction while under S9300 port traffic statistics, very easy for us to locate the problem.