The BB101301 Radium8750 broadband

multi-service switch (V500)

Troubleshooting

Learning Objectives

The principle of routine

maintenance
Physical layer fault location
method
Link layer fault location
Common troubleshooting
methods

Executive Summary

Routine maintenance
The basic idea

Common scenarios

Routine maintenance Attention

Power supply module and fan working
condition
SFUs health
Master Main from health
The SPU board running condition
The reign information of each board,
daughter card
ATM interface information
Log information
Alarm status
SRPU time

Physical layer troubleshooting ideas

1, the test card status
R8750 # pingslot SlotNum (SlotNum for board slot number)
2 business channel test
Determine how the business does not make sense
pingR8750 address of the interface
ping the address of other users (Note: If PPPoE users can
easily ping another user if the user IPoEoA to ping VE
interface under another user to ping through)
pingR8750 uplink access GSR interface address.
Can be positioned substantially above problem in which part
of the following reSpecific position.

Physical layer troubleshooting ideas

3, LPUc received normally.
Incoming message through LPUc optical port. First Show atm pvc by
MPU command line system which PVC.
R8750 # show atm pvc
Interface VPI VCI Type X-Interface X-VPI X-VCI Encap Status
Atm5/0/0 0 33 p2p Atm12/0/1 10 100 SYSTEM UP
Atm5/0/0 0 34 p2p Atm12/0/0 11 349 SYSTEM UP
Atm5/0/0 0 35 p2p Atm12/0/0 11 200 SYSTEM UP
Atm5/0/0 0 36 p2p Atm12/0/0 11 201 SYSTEM UP
Atm5/0/0 0 37 p2p Atm12/0/0 11 202 SYSTEM UP
Atm5/0/0 0 38 p2p Atm12/0/0 11 203 SYSTEM UP
......
The analysis the Bold PVC: PVC from LPUc, built to SPU external
PVC, LPUc port daughter card No. 12 slot 0 port 0, SPU 0 No. daughter
card slot 5 0 port, the port for the internal port.

Physical layer troubleshooting ideas

And then execute the Show atm pvc traffic can see the transceiver cell

statistics are as follows

R8750#show atm pvc traffic int atm 12/0/0 11 202
Interface VPI VCI Type rx-cell-cnts
Atm12/0/0 11 202 P2P 0x000010FF

tx-cell-cnts
0x0000316A

rx-cell-cnts the PVC from LPUC external port to receive the number
of cells, tx-cell-cnts expressed from LPUC external port number
of cells sent.
If this count is going up, the transceiver normal LPUC.

Physical layer troubleshooting ideas

4SPU The transceiver whether the normal
R8750#show atm pvc traffic int atm 5/0/0 0 37
Interface
Atm5/0/0

VPI VCI Type rx-cell-cnts

0 37
P2P 0x0000161D

tx-cell-cnts
0x00003EA8

rx-cell-cnts cell number of the PVC received from the switching

network, tx-cell-cnts cell number sent to the switching network.
These statistics are APC cell statistics module.
If this count is going up, the the SPU transceiver normal.

Physical layer troubleshooting ideas

5, L2 Processor transceiver is correct
6, 1200 processing packets correctly


PPPOEOA
1PPPoE

PPPoEoA

R8750#show vpdn session all

SID

RemMAC

LocMAC

Intf

VASt OIntf

00a0.c93d.0495 00e0.fc00.0000 Virtual-Template1:4 UP Virtual-Ethernet5/0/0

0010.a497.bcf5 00e0.fc00.0000 Virtual-Template1:5 UP Virtual-Ethernet5/0/0

0000.e859.42e7 00e0.fc00.0000 Virtual-Template1:3 UP Virtual-Ethernet5/0/0

3PPPoESession3


2AAA
R8750#show aaa user
User Name UserID Type IP Address AcctTime State CID
ISN00001-0
0
PPP 61.175.202.130 00:32:12 3 40965
ISN00001-0
1
PPP 61.175.202.132 00:36:12 3 40967
ISN00001-0
2
PPP 61.175.202.131 00:38:04 3 40966
3
User NameIP Hotel
3

IP AddressIP
AcctTime
CIDID


3
R8750#show fib
Flag: B-Broadcast,M-Muticast,O-blackhOle,D-Dynamic,
G-Gateway,H-Host,L-Llinfo,S-Static,U-Up
Destination/Mask Nexthop
Flag Interface
VlinkIndex
61.175.202.130/32 61.175.202.130 GHU Virtual-Template1 0X00450005
61.175.202.132/32 61.175.202.132 GHU Virtual-Template1 0X00050007
61.175.202.131/32 61.175.202.131 GHU Virtual-Template1 0X00050006
128.0.0.0/1
61.175.202.113 GSU Atm5/0/0
0X00050003
0.0.0.0/1
61.175.202.113 GSU Atm5/0/0
0X00050003
61.175.202.113/32 61.175.202.113 GHU Atm5/0/0
0X00050003
61.175.202.112/30 61.175.202.114 U
Atm5/0/0
0X00000000
61.175.202.114/32 127.0.0.1
GHU LoopBack0
0X00000000

3IPFIB


4CIB
R8750#show cib 5 0
slot:5 subslot:0 baseCID:0xa000
offs CID LowCID ConnType State Prtl UpperN Slot SubSlot Port
0 40960 -1 ATM_PORT CONN
0 129 5 0
0
1 40961 -1 BRI_PVC CONN
0 0
5 0
0
2 40962 -1 BRI_PVC CONN
0 0
5 0
1
3 40963 40993 IPOA
CONN
0 0
5 0
0
4 40964 40994 MAC_CONN CONN
0 0
5 0
1
6 40966 40996 PPPOE CONN
0 0
5 0
0
7 40967 41010 PPPOE CONN
0 0
5 0
0
8 40968 41000 PPPOE CONN
0 0
5 0
0
33 40993 40960 PVC
CONN
0 1
5 0
0

3PPPoECIB
FIBVlinkIndex12bit
CID12bit
pingping


IPOEOA
FIBCIBPPPoE
AAA USERVPDN SessionARP
R8750#show arp 5
IpAddress
Mac_Address
Type
61.175.203.65 00e0.fc00.0000 Interface
61.175.203.126 0000.0000.0000 Dynamic
61.175.203.72 0000.0000.0000 Dynamic
61.175.203.129 00e0.fc00.0000 Interface
61.175.203.207 0000.0000.0000 Dynamic
61.175.203.131 00e0.4ce0.51e7 Dynamic

5SPUARPIP
MAC20
IPFIB

PPPOEOA

PPPOEOA

Radius
Server
Radius

PPP/PP
POE

PC
PPPOE

RTU

Radium8750
MA5100
A
D
L

M
M
X

M
P
U

Internet

S
P
U

L
P
U
C

Web
Server

Internet

PPPOEOA

PPPPPPOE

CC

PADI
PPPOE

PADO
PADR
PPPOE UP

PPPOE UP

PADS
LCP

IPCP-

PPP UP

PPP
PPP
PPP

PPPOEOA

PPPOE
PPPLCP
PPP
PPPIP

--PPPOE

--PPPOE
R8750
R8750MPUshow vpdn session spu-slot

MACPPPOE
ESR#show vpdn session 5
SID Cid RemMAC
LocMAC
Intf VASt OIntf
Total Session is: 23
342 190006b8 0050.ba19.c6fc 00e0.fc00.0000 VT1:6389
345 19000145 0000.21e2.59ae 00e0.fc00.0000 VT1:6393
355 19000101 0050.ba19.3af5 00e0.fc00.0000 VT1:6541
363 1900000b 0050.ba19.c6f7 00e0.fc00.0000 VT1:6379
364 19000435 0050.ba1a.1447 00e0.fc00.0000 VT1:6380
366 190002fc 0050.ba19.c148 00e0.fc00.0000 VT1:6608
418 1900009e 0050.baf2.c848 00e0.fc00.0000 VT1:6365

UP Virtual-Ethernet5/0/0
UP Virtual-Ethernet5/0/0
UP Virtual-Ethernet5/0/0
UP Virtual-Ethernet5/0/0
UP Virtual-Ethernet5/0/0
UP Virtual-Ethernet5/0/0
UP Virtual-Ethernet5/0/0

--PPPOE

R8750SPUPVC
PPPOESPU
PPPOE

R8750PVC

--PPPOE

1MA5100R8750
PVC
2R8750SPUPVC
3R8750PPPOE

4R8750PVC
R8750R8750
PVCR8750

--PPPOE

1PPPOE
Contacting Server =-=-

2BASR8750PPPOE
PPPOEprofile
profileBAS
BASPPPOE SERVER

R8750PPPOE SERVERProfile
Profile

--PPPLCP

--PPPLCP
R8750
R8750MPUshow vpdn session spu-slot
MACPPPOE

PPPOE
Contacting Server =-=-=-=-R8750
PPPOE

--PPPLCP

R8750SPUPVC
PPPOELCP

R8750LCP

1LCP

2R8750MPUPPP

--PPP

--PPP

R8750RadiusServerAAA
R8750RadiusServer

R8750AAA
RadiusServer

--PPP

1R8750AAA
2RadiusServer

RadiusServer
3R8750AAA
RadiusServer

--PPP
Radius
R8750RadiusServer

R8750RadiusServerIP
RadiusServerPING
RadiusServer

R8750RadiusRadiusServer

RadiusServer

R8750Radius RadiusServer

RadiusServerR8750-NAS

RadiusServerR8750
RadiusServerNASR8750
RadiusServerR8750
R8750RadiusServerNASR8750

--PPPIP

Dialing unsuccessful - PPP the IP parameter negotiation

failure
Fault basic reasons
R8750 VT virtual template interface address is not configured
IPCP negotiation process between the client and the R8750 is
completely normal, but Client Profile, you need to re-create a
profile

Fault location method

VT address of the interface on the R8750, first check whether it
has been configured (not necessarily the user dial address pool

on the same network segment, configure a correct address);

2, VT address configuration is correct, the client will PPPPOE
profile to delete and re-create a profile to dial again.

Dial-up users abnormalities dropped

Dial-up users abnormalities dropped

Fault common cause of
Unable to maintain the PPP connection has been established between
the client and the R8750
A communication link failure between the client and the R8750
R8750 on 1200 CPU occupancy rate is too high, unable to deal with
R8750 with Radius Server communication failure occurs, R8750 users all
forced off the assembly line (when not configured aaa accounting
optional)
Physical link failure between R8750 and Radius Server
The routing information is missing, R8750 or Radius Server, mutual
nowhere PING
Radius Server software itself operational failure, such as shiver Beta
software itself unreliable and very prone to failure in the case of many
users
R8750 Radius module operational failure
MA5100 ADL port parameters are set incorrectly
Should be set to interlaced mode, and interleaving depth should take 16.

Dial-up users abnormalities dropped

Specific positioning method
1, R8750 console is PING RadiusServer, check whether the
PING pass;
View RadiusServer on whether the abnormal alarms
phenomenon, check RadiusServer whether operating

normally
Increase the RadiusServer R8750 console aaa accounting
optional configuration to see whether the situation has
improved
MA5100 on 4, checks whether the user ADL port correct
setting parameters, namely: the interleaving pattern and
depth of 16

Dial-up user services are unavailable

Failure phenomenon
PPPOE users normally are on the line, and the PPP
connection can maintain normal, but is no Internet access,
such as can not find the site, not open web pages.
The cause of the malfunction
Defective from the client to the data path between the external
network, focus on the R8750, egress router, external website
links

Dial-up user services are unavailable

Fault location method
1, first to the failure of the user to ask his or her account or dial-up IP
address
, According to the user account or the dial-up IP address, view the user's
the AAA online status is normal
3, check the routing of the user in the SPU and the MPU is normal
Confirm the routing of the user on the R8750 correct, confirm the user's
client routing is correct
5, has determined that the user side is completely normal, check the
uplink port is normal
6, check specific users to access external sites

Slow dial-up Internet users

Failure phenomenon
PPPOE users normally are on the line, and all business is normal, but
are not satisfied with the Internet speed, including open web pages slow,
slow download speed.
Failure and positioning
1 the slow access MA5100 ADL port intertwined mode interleaving depth
parameter settings have a great relationship, and therefore should first
check the user on the MA5100 ADL port parameters.
2, if the above-mentioned modified user speed has not improved, the
need to check the R8750 on the following exceptions:
The corresponding SPU whether the business is too busy, too late to
deal with the user data
SPU forwarding process more error
Whether a large number of the packet should be forwarded by the
microcode to the Core processing software (such as into a slice) specific
by SPU console the L2P, count, error, drecv, dsend command View