checklist network v0.3

Upload: francisco-manas

Post on 06-Jul-2018

233 views

Category:

Documents


0 download

TRANSCRIPT

  • 8/18/2019 Checklist Network v0.3

    1/16

    Network Troubleshooting checklist (v0.3)

    Incident / problem Reference

    Checklist completed by

    Critical checks have been completed  Yes No

    Important checks have been completed  Yes No

    !. In"ormation

    1.1)

    1.2) Is it a loss of connectivity? Yes No

    1.3) Is it a deradation of

    services?

     Yes

    No

    1.!) "re there any vis#al records

    or photos available?

     Yes

    No

    1.$) %as a physical inspection

    been cond#cted?

     Yes

    No

    1.6)

    1.&)Conditions

  • 8/18/2019 Checklist Network v0.3

    2/16

    2.3) ,ime of dianosis -#nderlyin ca#se ekno hat happened?) 

    /dd0mm0y

    y /hhmm   ,ime to repair

    as acceptable?

     Yes <

    >

    2.!) ,ime of repair -process to *< fail#restarted or corrective action initiated) 

    /dd0mm0y

    y /hhmm  No <

     X 

    >

    2.$) ,ime of recovery -component recovered the component is back in prod#ction b#siness ready to

    be res#med) 

    /dd0mm0y

    y /hhmm   ,ime to restore

    service to

    operational

    state as

    acceptable?

     Yes <

    >

    2.=) ,ime of restoration -normal operationsres#me the service is back in prod#ction) 

    /dd0mm0y

    y /hhmm  No <

     X 

    >

    2.&) ,ime of orkaro#nd -8ervice is back inprod#ction ith orkaro#nd) 

    /dd0mm0yy 

    /hhmm  4orkaro#ndsand escalation

    ere

    acceptable?

     Yes <√

    >

    2.') ,ime of escalation -to third level s#pportif re>#ired) 

    /dd0mm0y

    y /hhmm  No <

     X 

    >

    2..1) ,ime period service as #navailable -87"meas#re) 

    /min#tes ..3) %&'

    targets

    achieved* 

     Yes <

    >

    2..2) ,ime period service as deraded -87" meas#re) /min#tes No < X 

    >

    3. ;ro

  • 8/18/2019 Checklist Network v0.3

    3/16

    '>3.&) "re

    there

    any

    other

    circ#itsith

    similar

    iss#es?

     Ye

    s

    No < X 

    >

    3.') ;ro

  • 8/18/2019 Checklist Network v0.3

    4/16

    fan speed

    stat#s

    No

    !.1.2) (evice

    temperat#re

    stat#s

  • 8/18/2019 Checklist Network v0.3

    5/16

    5,,,,,,,,,,,,,,,,, 78 D7%&C 7&:;77N! 7::&7 "N/9&!"9N ,,,,,,,,,,,,,,,,,,5

    = =%ocal=emote = = = =Delay =itter =ep =

    =:er+ice =epid=ac &ddress =ep=D =D =in us =in us =!ime=

    5,,,,,,,,,,,,,,,,5,,,,,5,,,,,,,,,,,,,,,,,5,,,,5,,,,5,,,,5,,,,,,,,5,,,,,,,,5,,,,5

    =ta6? =1 =@(@1A@6?@'B@=1 =1 =1 =1?B =3 =2 =

    5,,,,,,,,,,,,,,,,5,,,,,5,,,,,,,,,,,,,,,,,5,,,,5,,,,5,,,,5,,,,,,,,5,,,,,,,,5,,,,5

    !.&) GtiliHation +.,.!) Is there a customerutili-ation problem* 

     Yes No /B

    !.&.2) 7on

    term -eekly)

    #tiliHation

    raph

    !.&.3) 8hort

    term -daily)

    #tiliHation

    raph

    !.&.!) Realtime #tiliHation

    raph

    !.&.$) 5Jered

    capacity

    4hat is the capacity bein

    transmitted or received from the

    core areation point to the

    rin #nder investiation?

    Is this

    oJered

    capacity

    e

  • 8/18/2019 Checklist Network v0.3

    6/16

    $. ;ort checks1.!) Con2guration 1.!.!)

    thernet

    port speed

    setting

    1 $.1.2) "re

    the

    +thernet

    port speed

    settins

    correct?

     Yes

    1

    1 No

    1

    "#to

    1.!.3)

    thernet

    port

    duple4

    setting

    %alf  $.1.!) "re

    the

    +thernet

    port d#ple<

    settins

    correct?

     Yes

    F#ll No

    (#ple<

    $.2) 8tatistics $.2.1) "re the port statistics

    ithin acceptable limits?

     YesNo

    $.2.2) (o the link 7+(Ks

    indicate proper cable

    connection?

     YesNo

    $.2.3) 8itch

    port statistics

    $.2.!) Radio

    statistics

    $.3) +rrors 1.3.!) 're there C5Cerrors displa#ed on the

    port* 

     Yes $.3.2) "re theseerrors cablin

    related?

     Yes $.3.3) "re

    these errors

    radio

    related?

     Yes

    No No No

    $.3.!) "re there any

    pa#se frames on the

    sitch?

     Yes $.3.$) "re there

    any pa#se frames

    on the radio?

     Yes $.3.=) "re

    the traLc

    co#nters

    incremente

    d in both

    directions?

     Yes

    No No No

    $.!)

    "dministrativ

    e

    $.!.1) %as the port been

    administratively reset?

     Ye

    s

    $.!.2) %as the port been

    physically reset?

     Ye

    sNo No

    $.!.3) Is the sitch port

    correctly con*#red as a

    tr#nk or access port as per

    the re>#irement?

     Ye

    s

    $.!.!) Is the port disabled

    either administratively or

    d#e to a fa#lt?

     Ye

    sNo No

    $.!.$) %as the port and

    cable been correctly

    labelled physically?

     Ye

    s

    $.!.=) (o the physical

    connections correspondin

    to the labellin?

     Ye

    sNo No

    $.!.&) %ave the ports been Ye $.!.') (o the sitch and Ye

    N+,45R6 C%+C67I8,9 Critical

    = : ; a e

  • 8/18/2019 Checklist Network v0.3

    7/16

    labelled in the sitch or

    device con*#ration?

    s device labels correspond to

    the physical connections?

    s

    No No

    $.$) 5"@ $.$.1) %as an +thernet 5"@

    loopback been performed

    on the last mile link?

     Ye

    s

    2.2.)

    No

    6. 5eticulation checks

    =.1) Cablin 6.!.) 7as a visual check 

    o" the cabling been

    conducted and is it

    acceptable* 

     Ye

    s

    <

    >

    =.1.3) "re photos available of the

    retic#lation?

     Yes

    No <

     X 

    >

    No

    =.1.!) ,ype of cablin

    bein #sed for circ#it

    =.1.!.1)

    Copper

     Yes =.1.$) Is

    the patch

    cablin

    damaed?

     Yes =.1.=) Is

    the port

    sfp or

  • 8/18/2019 Checklist Network v0.3

    8/16

    &. ,raLc checks

    &.1.1) Rate

    limit

    provisioned

    ,.!.) Is this

    the rate limit

    ordered b#customer*

     Ye

    s

    No < X 

    >

    &.1.3) "re the

    manaement

    D7"Ns set#p

    correctly

    -eoraphically

    partitioned) and

    rate limited?

     Ye

    s

    No

    &.2.1) Filters &.2.2) 4hat isthe ratio of

    #nicasts vers#s

    broadcasts and

    is it normal -less

    than 1M)?

    Ratio

    F

     Ye

    sNo

    &.2.3) %as

    broadcast *lter

    been

    con*#red?

     Ye

    sNo

    &.2.!) Is there abroadcast

    problem?

     YesNo

    &.3) I; Checks If (%C; is bein #sed are

    I; bein correctly

    assined?

     Ye

    s

    "re pins and tracerts

    operatin as e

    ,.+.) Is there a la#er loop (or

    s#mptoms o" one) present on

     Ye

    s

    N+,45R6 C%+C67I8,9 Critical

    ' : ; a e

  • 8/18/2019 Checklist Network v0.3

    9/16

    an# o" the transmission paths*  No <

     X 

    >

    &.!.2) 4hat type of

    path protectionprotocol is bein

    #sed?

    ;AA,+ "re there any path protection aps

    bein recorded or loed?

     Ye

    sO.'32 NoI+++ '2.1( Is the con*#ration of the path

    protection correct?

     Ye

    s5ther -radio

    or

    proprietary)

    No

    &.!.3) ;rimary

    path bein #sed

    con*#ration

    &.!.!) ;rimary

    path capacity

    &.!.$) ,otal

    provisioned

    capacity to

    s#bscribers

    incl#din A,8

    &.!.=) ,otal

    act#al

    provisioned

    capacity on

    the

    transmission

    backha#l

    &.!.&) 8old vs

    act#al

    provisioned

    overs#bscripti

    on rate

    < F >

    &.$.1) Aack#p

    path bein #sed

    con*#ration

    &.$.2) Aack#ppath capacity

    &.=) Aackha#l &.=.1) Is the

    same vrf bein

    #sin for RB and

     ,B

    -asymmetrical

    ro#tin)?

     Yes &.=.2) (o yo#

    *nd c#rvy

    blondes

    attractive?

     Yes

    No No

    '. 7os.!) 8o the logs report a network or port 9ap*  Yes /P

    No /B

    .) 8o the logs highlight an inter"erence problem*  Yes /P

    No /B

    N+,45R6 C%+C67I8,9 Critical

    : ; a e

  • 8/18/2019 Checklist Network v0.3

    10/16

    .3) 8o the logs highlight another problem*  Yes /P

    No /B

    .+) %witch logs

    .1) 5adio logs

    A.6)

    . Radio checks.1) RF Checks .1.1) 4hat type

    of RF e>#ipment

    is bein #sed?

    .1.2) If this is a

    ;t@; and has

    the con*#ration

    been

    disabled0reapplie

    d? -alternatively

    removed0reapplied) to resolve

    any connectivity

    iss#es?

     Yes

    No

    .1.3) (o yo#

    have pict#res of

    the 758?

     Yes .1.!) "re there

    visible 758

    iss#es?

     YesNo No

    Is the antennae

    correctly

    alined?

     Yes Is e

  • 8/18/2019 Checklist Network v0.3

    11/16

    acceptable?

    Is there a

    problem ith

    A+Rs?

     Yes "re the links at

    the hih site

    synchronised?

     Yes

    No No

    %as selfinterference

    been eliminated?

     Yes %as e#ipment or

    devices?

     Yes

    No No

    Is the ;5+

    e>#ipment

    f#nctionin

    correctly?

     Yes Is the device

    manaement

    f#nctionin and

    reportin no

    problems?

     Yes

    No No

    .2) @,G settins

  • 8/18/2019 Checklist Network v0.3

    12/16

    there an

    a#thenticat

    ion

    problem?

    there a

    provisionin

    problem?

    there a

    path or

    ro#te

    problem?

    No No No

    !0.+) 7as the :%% been checked

    "or this I or subscriber* 

     Yes 1.$) Is

    there aproblem

    ith the

    provisionin

    of the I;

    or

    s#bscriber

    on the

    588?

     Yes

    No

    No

    1.=) Is

    the correct

    static I;address

    bein

    allocated?

     Ye

    s

    1.&) Is there

    a c#rrent

    problem ithanonymo#s

    s#bscriber

    levels on the

    netork bein

    hih?

     Yes 1.') Is thethro#hp#t

    test from theC;+ to the

    Core

    acceptable?

    -Yes

    bandidth

    test tool on

    C;+ and from

    a 4indos ;C)

     Yes 1.) Is thelatency from

    the C;+ to thecore

    acceptable?

     Yes

    No No No No

    1.1)

    8tatic I;

    address

    bein

    #sed

    1.11)

    "dditional

    static I;

    addresses

    bein #sed

    1.12)

    8hared

    D7"N be

    #sed

    1.13) ;5;

    bein #sed

    1.1!) "re there any other

    s#bscribers ith a problem?

     Yes

    1.1$) Is

    this related

    to a

    transmissio

    n or access

    problem?

     Yes

    No No

    1.1=) (o all the session

    a#thentication servers pass a

    health test?

     Yes

    1.1&) Is

    there a

    problem in

    the Core I;

    netork?

     Yes

    No No

    1.1') GtiliHation raphs

    c#stomer -realtime daily

    eekly)

    1.1) Is

    there a

    c#stomer

    #tiliHation

    problem?

     Yes

    No

    1.2) GtiliHation raphs

    Core and peerin -realtime

    daily eekly)

    1.21) Is

    there a

    core or

    peerin

    #tiliHation

    problem?

     Yes

    No

    N+,45R6 C%+C67I8,9 Critical

    12 : ; a e

  • 8/18/2019 Checklist Network v0.3

    13/16

    1.2!) 4hat is the

    @"C address or

    #ni>#e identi*er of

    the s#bscriber?

    1.2$)

    4hat is

    the A,8-s)

    to hich

    the

    s#bscriberconnects?

  • 8/18/2019 Checklist Network v0.3

    14/16

    11. DoI;

    11.1) ;rovide a

    snapshot of the

    c#rrent @58 scoresfor DoI;.

    11.2) Interconnectionstat#s

  • 8/18/2019 Checklist Network v0.3

    15/16

    11.&) ,ests 11.&.2) "re DoI; test

    res#lts from a s#itable

    eb based voice

    testin service

    acceptable?

     Yes

    No

    12. E"

    11.1) Installation and provisionin %as an RFC2!! test beencompleted?

     Yes

    No

    If the C;+ is #nable to

    perform an RFC2$!! test

    then has an @,R test been

    done to a core device in

    the (C?

     Yes

    No

    11.2) ,estin %ave yo# performedbandidth testin #sin a

    tool?

     Yes

    No

    !!.3) 5esults o" 

    ;andwidth tests

    (initial installation)

  • 8/18/2019 Checklist Network v0.3

    16/16

    N+,45R6 C%+C67I8,9 Critical

    1= : ; a e