2 Links Troubleshooting v5

Embed Size (px)

Citation preview

  • 8/2/2019 2 Links Troubleshooting v5

    1/39

    Links troubleshooting

  • 8/2/2019 2 Links Troubleshooting v5

    2/39

    2

    Keep in mindimages in this presentation are illustrative images

    - it just show how we are monitoring thatinterfaces. It doesnt show, what is between of

    point A and Z of that links (switches, routers,backbone network etc..)

    2

  • 8/2/2019 2 Links Troubleshooting v5

    3/39

    3

    Linkstroubleshoting

  • 8/2/2019 2 Links Troubleshooting v5

    4/39

    4

    qmpa> ChnState

    Channel 268435520/0: Prot=176 Load=0.000 State=eINPUT_CONNECTOR_ALARM(4),MB2_NoSignal(4) SIM=1 LIM="0" Port="eth1"Channel 268435520/1: Prot=176 Load=0.000 State=eINPUT_CONNECTOR_ALARM(4),MB2_NoSignal(4) SIM=1 LIM="0" Port="eth1"

    Channel 268435694/0: Prot=102 Load=0.000 State=eINPUT_CONNECTOR_ALARM(4),MB2_NoSignal(4) SIM=1 LIM="0" Port="eth1"

    Channel 268435694/1: Prot=102 Load=0.000 State=eINPUT_CONNECTOR_ALARM(4),MB2_NoSignal(4) SIM=1 LIM="0" Port="eth1"

    Channel 268435700/0: Prot=117 Load=0.000 State=eINPUT_CONNECTOR_ALARM(4),MB2_NoSignal(4) SIM=1 LIM="0" Port="eth1"

    Channel 268435700/1: Prot=117 Load=0.000 State=eINPUT_CONNECTOR_ALARM(4),MB2_NoSignal(4) SIM=1 LIM="0" Port="eth1"

    qmpa>

    #>/ x ChnState

    #>/ x perfqmpa> perf

    Sample interval=30

    Cur load = 1804 bps

    Max load = 83083 bps at UCT 05.12.2005 00:13:00

    PDUs/ExPDUs = 31650728

    FISUs = 0

    Ticks = 69153361

    InputConnAlarm = 2SigInputAlarm = 0

    SigInputError = 0

    ProbeAlarm = 0

    LinkStatistics = 41492022

    Suppressed = 0

    Unknown = 0

    qmpa>

    General probe commands

  • 8/2/2019 2 Links Troubleshooting v5

    5/39

    5

    IuCS, Iub, Iur

  • 8/2/2019 2 Links Troubleshooting v5

    6/39

    6

    IuCShow its connected

    Iu-CS

    R1 la Paz RNC1 R1 la Paz Switch/MGW or MCSR1_LAPRN1-LAPSW1_0XY

    ATM/STM-1

    probe

    1st RX pair :

    Port=0 01A,01B

    2nd RX pair:

    Port=1 02A,02B

    DX-VAM

  • 8/2/2019 2 Links Troubleshooting v5

    7/39

    7

    IuBhow its connected

    IuB - NBAP over ATM

    Node B station RNCR9_TECRN1-NODEB_DF0530U850

    ATM/STM-1

    probe

    1st RX pair :

    Port=0 01A,01B

    2nd RX pair:

    Port=1 02A,02B

    DX-VAM

    NodeB

  • 8/2/2019 2 Links Troubleshooting v5

    8/39

    8

    IuRhow its connected

    IuR - RNSAP ove ATM

    RNC1 RNC2R9_TECRN1-URRRN1_01

    ATM/STM-1

    probe

    1st RX pair :

    Port=0 01A,01B

    2nd RX pair:

    Port=1 02A,02B

    DX-VAM

  • 8/2/2019 2 Links Troubleshooting v5

    9/39

    9

    IuCS how its connected

    1st RX pair :

    Port=0 01A,01B

    2nd RX pair:

    Port=1 02A,02B

    Usually four linksetsVPI/VCI depend on sequence of RNC on site:

    RNC1 RNC2 RNC3

    1. R1_LAPRN1-LAPSW1_01A fwd direction first RX pair; VPI/VCI 1,5000 1,5032 1,5064

    R1_LAPRN1-LAPSW1_01A bwd direction first RX pair; VPI/VCI 1,5000 1,5032 1,5064

    2. R1_LAPRN1-LAPSW1_01B fwd direction first RX pair; VPI/VCI 1,5001 1,5033 1,5065

    R1_LAPRN1-LAPSW1_01B bwd direction first RX pair; VPI/VCI 1,5001 1,5033 1,5065

    3. R1_LAPRN1-LAPSW1_02A fwd direction second RX pair; VPI/VCI 1,5000 1,5032 1,5064R1_LAPRN1-LAPSW1_02A bwd direction second RX pair; VPI/VCI 1,5000 1,5032 1,5064

    4. R1_LAPRN1-LAPSW1_02B fwd direction second RX pair; VPI/VCI 1,5001 1,5033 1,5065

    R1_LAPRN1-LAPSW1_02B bwd direction second RX pair; VPI/VCI 1,5001 1,5033 1,5065

    Traffic should be on 2 linksets in

    both directions

  • 8/2/2019 2 Links Troubleshooting v5

    10/39

    IuCS typical problems10

    R5_PVALLAR_ICS02:~# x chnstChannel 268447058/0: Prot=130 Load= 76.263 kbps State=No Alarm SIM=1 LIM="0" Port="0" R5_PVRR2-PVRMG1_01AChannel 268447058/1: Prot=130 Load= 86.015 kbps State=No Alarm SIM=1 LIM="0" Port="0" R5_PVRR2-PVRMG1_01AChannel 268447060/0: Prot=130 Load= 0.000 bps State=No Alarm SIM=1 LIM="0" Port="0" R5_PVRR2-PVRMG1_01BChannel 268447060/1: Prot=130 Load= 0.000 bps State=No Alarm SIM=1 LIM="0" Port="0" R5_PVRR2-PVRMG1_01BChannel 268447062/0: Prot=130 Load= 0.000 bps State=No Alarm SIM=1 LIM="0" Port="1" R5_PVRR2-PVRMG1_02AChannel 268447062/1: Prot=130 Load= 0.000 bps State= eINPUT_CONNECTOR_ALARM(4),MB2_NoSignal(4) SIM=1 LIM="0" Port="1" R5_PVRR2-PVRMG1_02AChannel 268447064/0: Prot=130 Load= 77.055 kbps State=No Alarm SIM=1 LIM="0" Port="1" R5_PVRR2-PVRMG1_02BChannel 268447064/1: Prot=130 Load= 0.000 bps State= eINPUT_CONNECTOR_ALARM(4),MB2_NoSignal(4) SIM=1 LIM="0" Port="1" R5_PVRR2-PVRMG1_02B

    Example 1:

    eINPUT_CONNECTOR_ALARM....NoSignal in 99 % of cases no signal on input

    connectorin this case, 2nd pairport 1, connector 4th (the last one on the bottom of

    STM-1 card)

    Possible reasons:1. wrong Telcel positioncheck with core people whether they change position

    2. wrong cable, connectors, optical splitter in DX-VAMcheck on-site

    3. weak signalcheck on-site

    4. wrong receiver on HDLU STM-1 cardcheck on-site (try to swap that cable

    with working cable from another connector)

  • 8/2/2019 2 Links Troubleshooting v5

    11/39

    11

    [root@R5_BANDERA_ICS01 c110606xjvr006]# x chnstChannel 268438162/0: Prot=130 Load= 0.000 bps State= eINPUT_CONNECTOR_ALARM(4),MB2_NoSignal(4) SIM=1 LIM="0" Port="0" R5_BANR1-BANSW3_01AChannel 268438162/1: Prot=130 Load=242.330 kbps State=No Alarm SIM=1 LIM="0" Port="0" R5_BANR1-BANSW3_01AChannel 268438164/0: Prot=130 Load= 0.000 bps State= eINPUT_CONNECTOR_ALARM(4),MB2_NoSignal(4) SIM=1 LIM="0" Port="0" R5_BANR1-BANSW3_01BChannel 268438164/1: Prot=130 Load= 0.000 bps State=No Alarm SIM=1 LIM="0" Port="0" R5_BANR1-BANSW3_01BChannel 268438166/0: Prot=130 Load= 0.000 bps State= eINPUT_CONNECTOR_ALARM(4),MB2_NoSignal(4) SIM=1 LIM="0" Port="1" R5_BANR1-BANSW3_02AChannel 268438166/1: Prot=130 Load= 0.000 bps State=No Alarm SIM=1 LIM="0" Port="1" R5_BANR1-BANSW3_02AChannel 268438168/0: Prot=130 Load= 0.000 bps State= eINPUT_CONNECTOR_ALARM(4),MB2_NoSignal(4) SIM=1 LIM="0" Port="1" R5_BANR1-BANSW3_02BChannel 268438168/1: Prot=130 Load=240.323 kbps State=No Alarm SIM=1 LIM="0" Port="1" R5_BANR1-BANSW3_02B

    IuCS typical problems

    Example 2:

    no signal on input connectorin this case:

    1st pairport 0, connector 1st

    2nd pairport 1, connector 3rd

    Possible reasons:

    1. wrong Telcel positioncheck with core people whether they change position

    2. wrong cable, connectors, optical splitter in DX-VAMcheck on-site

    3. weak signalcheck on-site

    4. wrong receiver on HDLU STM-1 cardcheck on-site (try to swap that cable

    with working cable from another connector)

  • 8/2/2019 2 Links Troubleshooting v5

    12/39

    12

    R7_LERDOVE_ICS02:~# x chnstChannel 268447096/0: Prot=130 Load= 0.000 bps State=No Alarm SIM=1 LIM="0" Port="0" R7_LERR2_LERMG2_01AChannel 268447096/1: Prot=130 Load= 0.000 bps State=No Alarm SIM=1 LIM="0" Port="0" R7_LERR2_LERMG2_01AChannel 268447098/0: Prot=130 Load= 0.000 bps State=No Alarm SIM=1 LIM="0" Port="0" R7_LERR2_LERMG2_01BChannel 268447098/1: Prot=130 Load= 0.000 bps State=No Alarm SIM=1 LIM="0" Port="0" R7_LERR2_LERMG2_01BChannel 268447100/0: Prot=130 Load= 0.000 bps State=No Alarm SIM=1 LIM="0" Port="1" R7_LERR2_LERMG2_02AChannel 268447100/1: Prot=130 Load= 0.000 bps State=No Alarm SIM=1 LIM="0" Port="1" R7_LERR2_LERMG2_02AChannel 268447102/0: Prot=130 Load= 0.000 bps State=No Alarm SIM=1 LIM="0" Port="1" R7_LERR2_LERMG2_02BChannel 268447102/1: Prot=130 Load= 0.000 bps State=No Alarm SIM=1 LIM="0" Port="1" R7_LERR2_LERMG2_02B

    IuCS typical problems

    Example 3:

    no ALARM on all input connectors but also no traffic on all conectors

    Check:

    check whether VPI/VCI are correctly configured according to availableinformation

    check if there is a traffic (Telcel people)

  • 8/2/2019 2 Links Troubleshooting v5

    13/39

    13

    IuPS

  • 8/2/2019 2 Links Troubleshooting v5

    14/39

    14

    IuPShow its connected

    Iu-PS

    R1 la Paz RNC1 R1 Lomas SGSNR1_LAPRN1-R1LMSGSN_0x

    Fast Ethernet

    probe2x TAP

  • 8/2/2019 2 Links Troubleshooting v5

    15/39

    eth2 193.88.224.2eth3 193.88.224.3

    eth4 193.88.224.4eth5 193.88.224.5

    15

    IuPS how its connected

    Usually two linksets:

    1. R1_LAPRN1-R1LMSGSN_01 fwd direction first link;

    R1_LAPRN1-R1LMSGSN_01 bwd direction first link;

    2. R1_LAPRN1-R1LMSGSN_02 fwd direction second link;

    R1_LAPRN1-R1LMSGSN_02 bwd direction second link;

    Traffic should be on 1 linksets in

    both directions

    1st link : eth2+eth3

    2nd link: eth4+eth5

    Old CT9 BOARD:

  • 8/2/2019 2 Links Troubleshooting v5

    16/39

    eth3 193.88.224.2eth4 193.88.224.3

    eth5 193.88.224.4eth6 193.88.224.5

    16

    IuPS how its connected

    Usually two linksets:

    1. R1_LAPRN1-R1LMSGSN_01 fwd direction first link;

    R1_LAPRN1-R1LMSGSN_01 bwd direction first link;

    2. R1_LAPRN1-R1LMSGSN_02 fwd direction second link;

    R1_LAPRN1-R1LMSGSN_02 bwd direction second link;

    Traffic should be on 1 linksets in

    both directions

    1st link : eth3+eth4

    2nd link: eth5+eth6

    KONTRON BOARD:

  • 8/2/2019 2 Links Troubleshooting v5

    17/39

    17

    IuPS typical problems

    [root@R8_BONAMPA_IPS01 root]# x chnstChannel 268446348/0: Prot=130 Load=418.652 kbps State=No Alarm SIM=1 LIM="0" Port="eth2,eth3" R8_BONR1-R8PASGSN_01Channel 268446348/1: Prot=130 Load=455.375 kbps State=No Alarm SIM=1 LIM="0" Port="eth2,eth3" R8_BONR1-R8PASGSN_01Channel 268446350/0: Prot=130 Load= 0.000 bps State= eINPUT_CONNECTOR_ALARM(4),MB2_NoSignal(4) SIM=1 LIM="0" Port="eth4,eth5" R8_BONR1-R8PASGSN_02Channel 268446350/1: Prot=130 Load= 0.000 bps State=No Alarm SIM=1 LIM="0" Port="eth4,eth5" R8_BONR1-R8PASGSN_02

    Example 1:

    no signal on input connectorin this case:

    2nd

    pairport 1, connector 3rd

    (ETH4)

    Usually its mean, that the link is down on that ETH interface ETH4 in this case

    Check:

    use mii-tool for information about ETH interfaces (test whether interface is up/down)

    try to restart /etc/init.d/qapm stop; /etc/init.d/qapm start

    check TAP, cables, connectors, pozitions on-site (whether monitored links are

    connected and are up; check the connection from TAP -> CT9)

  • 8/2/2019 2 Links Troubleshooting v5

    18/39

    18

    IuPS typical problems

    R4_SANPEDR_IPS02:~# x chnstChannel 268446886/0: Prot=130 Load= 0.000 bps State=No Alarm SIM=1 LIM="0" Port="eth3, eth4" R4_SPERN2-R4ANSGS_01AChannel 268446886/1: Prot=130 Load= 0.000 bps State=No Alarm SIM=1 LIM="0" Port="eth3, eth4" R4_SPERN2-R4ANSGS_01AChannel 268446888/0: Prot=130 Load= 0.000 bps State=No Alarm SIM=1 LIM="0" Port="eth5, eth6" R4_SPERN2-R4ANSGS_01BChannel 268446888/1: Prot=130 Load= 0.000 bps State=No Alarm SIM=1 LIM="0" Port="eth5, eth6" R4_SPERN2-R4ANSGS_01B

    Example 2:

    no traffic on all links

    Usually its mean, that the link is UP on that ETH interfaces, but we have no signaling

    traffic or the probe is correctly connected to TAP, or there is no link on network ports

    (Telcel ports)...

    We are not using any kind of IP filteronly the port filter.

    Check:

    use tcpdump

    i ethX to observer whether there is a traffic no traffic - check cables CT9 TAP and TAP itself; check with Telcel, whether

    there should be a traffic.

    there is a trafficcontinue with next step:

    use tcpdump i ethX vlan and sctp to observer, whether there is a SCTP traffic.

    no sctp trafficask Telcel whether there should be traffic

    sctp traffic is therecheck the configuration of the probe

  • 8/2/2019 2 Links Troubleshooting v5

    19/39

    19

    SIGTRAN, CCN, PSL & A interface

  • 8/2/2019 2 Links Troubleshooting v5

    20/39

    20

    SIGTRAN STP linkshow its connected

    SS7 over IP - SIGTRAN

    general STPgeneral equipment

    MGW, SW, STP, SCPR9_STNE1207MGM601_01

    Fast Ethernet

    TAPs

    STP

    probe

    Extreme SW

    Blade Pass-Thru module

    1xETH

  • 8/2/2019 2 Links Troubleshooting v5

    21/39

    21

    SIGTRAN A int linkshow its connected

    BSS MAP + DTAP over SIGTRAN

    BSC MSCR4_SPETR1-SPSW1

    Fast Ethernet

    2x TAPs

    BSC

    probe

    Extreme SW

    Blade Pass-Thru module

    1xETH

    MSC

  • 8/2/2019 2 Links Troubleshooting v5

    22/39

    22

    SIGTRAN typical problems

    R5_BANDERA_SIG01:~# x chnstChannel 268444100/0: Prot=224 Load= 0.000 bps State=No Alarm SIM=1 LIM="0" Port="eth1" R5_STBA3103VMBA01_01Channel 268444100/1: Prot=224 Load= 0.000 bps State=No Alarm SIM=1 LIM="0" Port="eth1" R5_STBA3103VMBA01_01Channel 268444102/0: Prot=224 Load= 0.000 bps State=No Alarm SIM=1 LIM="0" Port="eth1" R5_STBA3103VMBA02_01Channel 268444102/1: Prot=224 Load= 0.000 bps State=No Alarm SIM=1 LIM="0" Port="eth1" R5_STBA3103VMBA02_01Channel 268444122/0: Prot=224 Load=100.000 kbps State=No Alarm SIM=1 LIM="0" Port="eth1" R5_STBA2315MGPV01_01Channel 268444122/1: Prot=224 Load=100.000 kbps State=No Alarm SIM=1 LIM="0" Port="eth1" R5_STBA2315MGPV01_01Channel 268444134/0: Prot=224 Load=100.000 kbps State=No Alarm SIM=1 LIM="0" Port="eth1" R5_STBA2315MGCM01_01

    Example 1:

    0.000 bps or 100.000 kbps traffic on ports :

    Usually its mean, that we have incorrect configuration of link or the link is down (can be

    seen on Extreme SW only) or we are monitoring incorrect links (more investigation

    needed)

    Check:

    try to find another 2315 port traffic:

    Note: it seems, that when you

    can see that there is exactly

    100.000 kbps traffic mean,

    that there is a traffic

    according to IP filter (on thatport), but there is no traffic

    with filtered OPC/DPC.

  • 8/2/2019 2 Links Troubleshooting v5

    23/39

    23

    SIGTRAN typical problems

    ..continue

    there is a traffic on other 2315 port check whether configuration of the probeis according to Telcel information (OPC/DPC sim filter settings ). When its

    OK, check the settings/links with Telcel.

    there is no traffic on other ports (for example 3103 port):

    find in cabling table current position for example: 3103-> FE TAP1, port

    15+16-> Extreme1 port 29,30,31,32

  • 8/2/2019 2 Links Troubleshooting v5

    24/39

    24

    SIGTRAN typical problems

    ..continue check ports on extreme switch whether ports are UP and there is a traffic:

    If there ports are UP and there is a traffic, we need to do more investigation

    aggregating only this ports on probe, run tcpdump to capture data. Analyze the traffic

    for IP/OPC/DPC. Check this IP/OPC/DPC with Telcel core people to know, whether

    that is a correct traffic on this link or notif the traffic is OK, update configuration of

    the probe according to obtained information.

    If ports are DOWNcheck with Telcel, whether the links should have a traffic. Check

    TAP/cables/connection on-site.

  • 8/2/2019 2 Links Troubleshooting v5

    25/39

    25

    SIGTRAN typical problems

    ..continue If ports are DOWN (for example port 2117)check with Telcel, whether the links

    should have a traffic. Check TAP/cables/connection/positions on-site.

  • 8/2/2019 2 Links Troubleshooting v5

    26/39

    26

    26

    Gn,Gp

  • 8/2/2019 2 Links Troubleshooting v5

    27/39

    27

    Gn, Gp linkshow its connected

    GTP-U, GTP-C

    SGSN GGSNR9_R9MRSGS_Gn_0X

    Gigabit ETH

    TAPs

    SGSN

    probe

    Extreme SW

    Blade Pass-Thru module

    4xETH

    GGSN

    DL380 + LU5 card

  • 8/2/2019 2 Links Troubleshooting v5

    28/39

    28

    Gn typical problems

    R9_MORALES_GGN02:~# x chnstChannel 268438720/0: Prot=233 Load=665.524 kbps State=No Alarm SIM=1 LIM="0" Port="hpe0.0,hpe0.1" R9_R9MRSGS_Gn_01Channel 268438720/1: Prot=233 Load=472.537 kbps State=No Alarm SIM=1 LIM="0" Port="hpe0.0,hpe0.1" R9_R9MRSGS_Gn_01Channel 268438750/0: Prot=233 Load=677.230 kbps State=No Alarm SIM=1 LIM="0" Port="hpe0.2,hpe0.3" R9_R9MRSGS_Gn_02Channel 268438750/1: Prot=233 Load=507.436 kbps State=No Alarm SIM=1 LIM="0" Port="hpe0.2,hpe0.3" R9_R9MRSGS_Gn_02

    Example 1: Gn connected to LU5 card (special card for capturing big amount of traffic)

    Port=hpe0.X, hpe0.X - this indicate using HPE (High Performance card).

    on this card TCPDUMP command cant be used

    necessary to use special commands/programs to capture data, move data to local disk,analyze the traffic using Wireshark

    If there is no traffic,

    ask Telcel core people, whether there should be the traffic

    check Extreme SW port for traffic (use cabling table to find that ports); check TAPs, cables

    we are not using any filter on Gn links - all traffic should be processed

    We are processing GTP-U (user plain) & GTP-C (signaling)

    GTP-U TDRs are generated (every 5 minutes) in /var/nettest/li-doip-gn-kpi/output/

    directory

    GTP-C signaling traffic is processed and stored in probes database (x csdrlog)

  • 8/2/2019 2 Links Troubleshooting v5

    29/39

    29

    Gn typical problems

    R5_BANDERA_GGN01:~# x chnstChannel 268435478/0: Prot=233 Load=398.485 kbps State=No Alarm SIM=1 LIM="0" Port="eth1,eth2" R5_R5BASGS_Gn_Erricson_01Channel 268435478/1: Prot=233 Load=648.865 kbps State=No Alarm SIM=1 LIM="0" Port="eth1,eth2" R5_R5BASGS_Gn_Erricson_01Channel 268435482/0: Prot=233 Load=415.531 kbps State=No Alarm SIM=1 LIM="0" Port="eth3,eth4" R5_R5BASGS_Gn_Erricson_02Channel 268435482/1: Prot=233 Load=112.190 kbps State=No Alarm SIM=1 LIM="0" Port="eth3,eth4" R5_R5BASGS_Gn_Erricson_02

    Example 2: Gn connected via Pass-Thru

    Port=eth1, eth2 - this indicate using standard ETH cards + pass-trhu module.

    TCPDUMP command can be used for analyze the traffic in case of problems

    If there is no traffic,

    ask Telcel core people, whether there should be the traffic

    use TCPDUMP to check the traffic (both GTP-U & GTP-C should be there)

    check Extreme SW port for traffic (use cabling table to find that ports); check TAPs, cables

    we are not using any filter on Gn links - all traffic should be processed

    We are processing GTP-U (user plain) & GTP-C (control - signaling)

    GTP-U TDRs are generated (every 5 minutes) in /var/nettest/li-doip-gn-kpi/output/

    directory

    GTP-C signaling traffic is processed and stored in probes database (x csdrlog)

  • 8/2/2019 2 Links Troubleshooting v5

    30/39

    30

    Gp typical problems

    R9_PORTALE_GGP01:~# x chnstChannel 268439998/0: Prot=233 Load=187.590 kbps State=No Alarm SIM=1 LIM="0" Port="eth1" R9_R9PTBGN_GP_01Channel 268439998/1: Prot=233 Load=232.400 kbps State=No Alarm SIM=1 LIM="0" Port="eth1" R9_R9PTBGN_GP_01

    Example 3: Gp connected via Pass-Thru (always)

    Gp links (Portalers & Morales) are connected only via pass-thru

    TCPDUMP command can be used for analyze the traffic (GTP) in case of problems

    If there is no traffic, ask Telcel core people, whether there should be the traffic

    use TCPDUMP to check the traffic (both GTP-U & GTP-C should be there)

    check Extreme SW port for traffic (use cabling table to find that ports); check TAPs, cables

    we are using IP filter on Gp links - check whether IP filter settings is correct

    We are processing GTP-U (user plain) & GTP-C (control - signaling) GTP-U TDRs are generated (every 5 minutes) in /var/nettest/li-doip-gn-kpi/output/

    directory

    GTP-C signaling traffic is processed and stored in probes database (x csdrlog)

  • 8/2/2019 2 Links Troubleshooting v5

    31/39

    31

    31

    Gi/Gy links

  • 8/2/2019 2 Links Troubleshooting v5

    32/39

    32

    Gi/Gy linkshow its connected

    IP traffic, DNS, RADIUS/DIAMETER, GTP

    GGSNR9_R9MRGGSN_Gi_DNS

    R9_R9MRGGSN_Gy_Diameter

    R9_R9MRGGSN_Gi_Radius

    Fiber optic

    probe

    VSS24 FO TAP

    Blade Pass-Thru module

    1xETH

    GGSN

    Internet

    DX VAM

    SGSN

    OCS(online

    charging

    system)

    MAC

    switchGy (VLAN x)

  • 8/2/2019 2 Links Troubleshooting v5

    33/39

    33

    Gi/Gy overview33

  • 8/2/2019 2 Links Troubleshooting v5

    34/39

    34

    Gi/Gy typical problems

    R9_MORALES_GGI01:~# x chnstChannel 268446060/0: Prot=230 Load= 3.764 Mbps State=No Alarm SIM=1 LIM="0" Port="eth1" R9_R9MRGGSN_Gi_DNS_01Channel 268446060/1: Prot=230 Load= 1.596 Mbps State=No Alarm SIM=1 LIM="0" Port="eth1" R9_R9MRGGSN_Gi_DNS_01Channel 268446078/0: Prot=232 Load= 0.000 bps State=No Alarm SIM=1 LIM="0" Port="eth1" R9_R9MRGGSN_Gy_Diameter_01Channel 268446078/1: Prot=232 Load= 2.563 Mbps State=No Alarm SIM=1 LIM="0" Port="eth1" R9_R9MRGGSN_Gy_Diameter_01Channel 268446388/0: Prot=230 Load= 49.403 kbps State=No Alarm SIM=1 LIM="0" Port="eth1" R9_R9MRGGSN_Gi_Radius_01Channel 268446388/1: Prot=230 Load=451.284 kbps State=No Alarm SIM=1 LIM="0" Port="eth1" R9_R9MRGGSN_Gi_Radius_01

    Example 1: Gi/Gy connected via Pass-Thru

    TCPDUMP command can be used for analyze the traffic in case of problems

    If there is no traffic, use TCPDUMP to check the traffic (internet traffic /www, snmp, etc./ should be there)

    when there is no traffic, ask Telcel core people, whether there should be the traffic

    check VSS24 ports for traffic (use cabling table to find that ports) - we shoud have traffic on

    all FO ports (1,2,3,4 in this example):

    35

  • 8/2/2019 2 Links Troubleshooting v5

    35/39

    35

    Gi/Gy typical problems

    .....continue of Example 1: Gi/Gy connected via Pass-Thru

    all FO ports shouldnt have BAD PACKETS - on example figure you can see a lot ofBAD PACKETS on port 4 and some BAD PACKETS on port 3:

    no signal on all or some ports:

    check links with Telcel core whether there should be the traffic

    check cables, FO connectors, signal levels on DX VAM output and VSS24 input

    (signal level should be at least -15 dBm, recommended -12 dBm)

    BAD PACKETS on some ports:

    check cables, FO connectors, signal levels on DX VAM output and VSS24 input

    (signal level should be at least -15 dBm, recommended -12 dBm)

    36

  • 8/2/2019 2 Links Troubleshooting v5

    36/39

    36

    Gi/Gy typical problems

    .....continue of Example 1: Gi/Gy connected via Pass-Thru

    we are filtering the traffic directly on VSS24 - its because big amount of traffic -

    filter definition can be found on VSS24 under Monitor Filtering tab:

    If there is no traffic on probe, check also that filters (ports) on VSS24

    the same filter are on probe to divide traffic on logical links (check it in

    Configuration Editor)

    37

  • 8/2/2019 2 Links Troubleshooting v5

    37/39

    37

    37

    Gb, HSL, LSL links

    38

  • 8/2/2019 2 Links Troubleshooting v5

    38/39

    38

    Gb/HLS/LSL linkshow its connected

    Sigtran traffic

    BSC,STP SGSN, other eqipmentR9_VLEBS1-R9MRSGS01

    R3_HSL_STCE3307S00TXX_R0RAMS01

    R3_LSL_STCE3311S00T03_R0LOST01

    E1

    probe

    E1cableRx+Tx

    BSC

    coaxial splitter

    SGSN

    balun

    coax -> twist

    39

  • 8/2/2019 2 Links Troubleshooting v5

    39/39

    39

    Gb/HLS/LSL typical problems

    R6_MARQUES_BOS01:~# x chnst

    Channel 268442870/0: Prot=224 Load= 0.000 bps State= eINPUT_CONNECTOR_ALARM(4),MB2_NoSignal(4) SIM=1 LIM="0" Port="0" R6_LSL_STMR1311S00T01_R2AZTM01_A_01Channel 268442870/1: Prot=224 Load= 0.000 bps State= eINPUT_CONNECTOR_ALARM(4),MB2_NoSignal(4) SIM=1 LIM="0" Port="0" R6_LSL_STMR1311S00T01_R2AZTM01_A_01Channel 268442872/0: Prot=224 Load= 0.000 bps State= eINPUT_CONNECTOR_ALARM(4),MB2_NoSignal(4) SIM=1 LIM="0" Port="1" R6_LSL_STMR1312S01T01_R2AZTM01_A_01Channel 268442872/1: Prot=224 Load= 0.000 bps State= eINPUT_CONNECTOR_ALARM(4),MB2_NoSignal(4) SIM=1 LIM="0" Port="1" R6_LSL_STMR1312S01T01_R2AZTM01_A_01

    Example 1:

    eINPUT_CONNECTOR_ALARM(4),MB2_NoSignal(4) - this means, no signal on input connector

    check this link with Telcel whether we should have traffic on this link (find this link in cabling

    table file),

    check configuration of links (timeslots) if they are according to Telcel information & cablingtable

    check balun, cables & connectors on-site

    There is no possibility to check traffic like using TCPDUMP - you need to correctly configure links andcheck the traffic in Protocol Analysis.