Scribd Logo
Upload

Welcome to Scribd!

  • 169 views

    HP-MSR Router Troubleshooting: Contents

    Uploaded by

    Heera Singh
    The document provides standard operating procedures (SOPs) for troubleshooting issues on HP-MSR routers. The SOPs include instructions for checking interface status, troubleshooting packet drops, verifying BGP neighborship and state, troubleshooting Finacle application issues, and switching between primary and secondary WAN links.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd

    HP-MSR Router Troubleshooting: Contents

    Uploaded by

    Heera Singh
    169 views7 pages
    The document provides standard operating procedures (SOPs) for troubleshooting issues on HP-MSR routers. The SOPs include instructions for checking interface status, troubleshooting packet drops, verifying BGP neighborship and state, troubleshooting Finacle application issues, and switching between primary and secondary WAN links.

    Original Title

    SOP_For_HP-MSR_Router_Troubleshoot

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    The document provides standard operating procedures (SOPs) for troubleshooting issues on HP-MSR routers. The SOPs include instructions for checking interface status, troubleshooting packet drops, verifying BGP neighborship and state, troubleshooting Finacle application issues, and switching between primary and secondary WAN links.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    169 views7 pages

    HP-MSR Router Troubleshooting: Contents

    Uploaded by

    Heera Singh
    The document provides standard operating procedures (SOPs) for troubleshooting issues on HP-MSR routers. The SOPs include instructions for checking interface status, troubleshooting packet drops, verifying BGP neighborship and state, troubleshooting Finacle application issues, and switching between primary and secondary WAN links.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    of 7

    Contents :

    HP-MSR Router Troubleshooting


    1. SOP To Find Interface Status..........................................................................................................2
    2. SOP To Troubleshoot Packet Drops Problems...............................................................................3
    3. SOP To Find out BGP neighborship & state....................................................................................5
    4. SOP To Troubleshoot Finacle Application Not Working From Branch Side.....................................6
    5. SOP To Switch over WAN link from BSNL MPLS (Primary Link) to Tata MPLS (Secondary link) in
    case of Reliability issue / Packet Drops Issue or Flapping Issue in BSNL Link................................7
    HP-MSR Router Troubleshooting
    SOP To Find Interface Status
    [router]dis ip int brie
    Interface Physical Protocol I P Address Description
    GE0/0 up up 172.17.11.1 Local LAN
    GE0/1 up up 10.210.15.142 Tata MPLS
    S1/0 down down 10.201.22.18 BSNL MPLS

    If any IP Assign used interface administratively down , then make it up with `undo’ command

    <router>sys

    [router]int s1/0

    [router-Serial1/0]undo shut

    [router-Serial1/0]quit

    [router]

    [router]dis ip int brie


    Interface Physical Protocol I P Address Description
    GE0/0 up up 172.17.11.1 Local LAN
    GE0/1 up up 10.210.15.142 Tata MPLS
    S1/0 up up 10.201.22.18 BSNL MPLS

    Now Serial interface status showing UP if link is properly terminated & working ok.

    If still serial interface status shows down then there will be link or modem issue.
    SOP To Troubleshoot Packet Drops Problems
    Step -1 : Check for CRC error.

    [router]dis int s1/0


    Serial1/0
    Current state: UP
    Line protocol state: UP
    Input:
    12659168 packets, 3991886214 bytes
    84325 errors, 4 runts, 0 giants
    15 CRC, 42126 align errors, 0 overruns
    42180 aborts, 0 no buffers, 0 frame errors
    Output:
    18150774 packets, 3239492011 bytes
    0 errors, 0 underruns, 0 collisions
    0 deferred
    DCD: UP, DTR: UP, DSR: UP, RTS: UP, CTS: UP

    There should be 0 count for CRC errors.

    If any CRC errors showing , then clear it & recheck again by below command.

    [router]quit
    <router>reset counters interface s1/0
    [router]dis int s1/0

    Input:
    639 packets, 41974 bytes
    0 errors, 0 runts, 0 giants
    0 CRC, 0 align errors, 0 overruns
    0 aborts, 0 no buffers, 0 frame errors
    Output:
    1101 packets, 1195782 bytes
    0 errors, 0 underruns, 0 collisions
    0 deferred
    DCD: UP, DTR: UP, DSR: UP, RTS: UP, CTS: UP
    Step -2 : If CRC error not showing , still packet drops occurs then check for which system utilized more
    bandwidth by ‘dis ip netstream ca’

    IP NetStream cache information:


    Flow active timeout (minutes) : 1
    Flow inactive timeout (seconds) : 15
    Max number of entries : 10000
    IP active flow entries : 303
    MPLS active flow entries :0
    L2 active flow entries :0
    IPL2 active flow entries :0
    IP flow entries been counted : 5626465
    MPLS flow entries been counted : 0
    L2 flow entries been counted : 0
    IPL2 flow entries been counted : 0
    Last statistics reset time : Never

    IP packet size distribution (60929693 packets in total):

    Protocol Total Packets Flows Packets Active(sec) Idle(sec)


    Flows /sec /sec /flow /flow /flow
    ---------------------------------------------------------------------------
    IP-other 1257 0 0 61 28 10
    UDP-other 508090 22 2 8 2 14
    TCP-other 3159330 155 16 9 2 11
    ICMP 1433002 11 7 1 1 14
    UDP-DNS 420387 4 2 1 2 15

    Type DstIP(Port) SrcIP(Port) Pro ToS If(Direct) Pkts


    DstMAC(VLAN) SrcMAC(VLAN)
    TopLblType(IP/MASK) Lbl-Exp-S-List
    ---------------------------------------------------------------------------
    IP 172.28.1.66(61377) 172.16.6.12(2000) 6 96 GE0/0(O) 99
    IP 172.28.1.40(63697) 172.16.13.37(53) 17 0 S1/0(I) 122
    IP 172.28.1.89(771) 172.16.4.103(0) 1 0 GE0/0(O) 45

    As per above o/p system having IP add. 172.28.1.40 utilized more bandwidth.

    [router]quit
    <router>reset ip netstream sta (To reset ip accounting)

    [router] dis ip netstream ca


    SOP To Find out BGP neighborship & state.
    [router]dis bgp peer ipv4

    BGP local router ID: 10.101.23.1


    Local AS number: 65003
    Total number of peers: 2 Peers in established state: 2

    Peer AS MsgRcvd MsgSent OutQ PrefRcv Up/Down State

    10.101.23.2 9583 5525 3787 0 119 0054h13m Established


    10.201.3.218 9829 91776 3502 0 5184 0054h13m Established

    *** To see what routes you're getting from a neighbor, use the command

    [router]display bgp routing-table ipv4 peer <ip-address of neighbor> advertised-routes

    *** To clear a BGP session

    <router>reset bgp <ip-address of neighbor> ipv4

    *** To ignore neighbor ship with peer


    [router]bgp 65003

    [router-bgp]peer 10.201.35.18 ignore

    [router]dis bgp peer ipv4

    BGP local router ID: 10.101.23.1


    Local AS number: 65003
    Total number of peers: 2 Peers in established state: 2

    Peer AS MsgRcvd MsgSent OutQ PrefRcv Up/Down State

    10.101.23.2 9583 5525 3787 0 119 0054h13m Established


    10.201.3.218 9829 91776 3502 0 5184 0054h13m Idle(Admin)

    [router]bgp 65003

    [router-bgp]undo peer 10.201.3.218 ignore (To remove ignore BGP peer)


    SOP To Troubleshoot Finacle Application Not Working From Branch
    Side.
    Step1 : Ask for branch code to branch person. According to branch code findout LAN IP address of
    that branch & Telnet it.

    Eg. Branch Code  7323 , LAN IP Address of that Branch  172.17.11.1

    login: cmsfmnw
    Password:
    <AHD-Anand-7323>sys
    System View: return to User View with Ctrl+Z.
    [AHD-Anand-7323]dis ip int brie
    Interface Physical Protocol I P Address Description
    GE0/0 up up 172.17.11.1 *****LOCA...
    GE0/1 up up 10.210.135.142 Connected...
    S3/0 up up 10.201.22.13 Connected...

    Step2 : Ping Finacle IP as per RO using source IP as a LAN IP as per below

    [AHD-Anand-7323]ping -a 172.17.11.1 172.16.3.37


    Ping 172.16.3.37(172.16.3.37): 56 data bytes, press escape sequence to break
    Request time out
    Request time out
    --- Ping statistics for 172.16.3.37 ---
    5 packet(s) transmitted, 0 packet(s) received, 100.0% packet loss

    Step3 : If it is pinging OK , means Fincle application working fine.


    If it is not pinging then do as per below.

    [AHD-Anand-7323]quit(cntrl+Z)
    <AHD-Anand-7323>reset ike sa
    <AHD-Anand-7323>reset ike stat

    Step4 : Again Ping Finacle IP using source IP as a LAN IP as per below

    [AHD-Anand-7323]ping -a 172.17.11.1 172.16.3.37


    Ping 172.16.3.37 (172.16.3.37) from 172.17.11.1: 56 data bytes, press escape seuence to break
    56 bytes from 172.16.3.37: icmp_seq=0 ttl=252 time=53.773 ms
    56 bytes from 172.16.3.37: icmp_seq=1 ttl=252 time=54.844 ms
    56 bytes from 172.16.3.37: icmp_seq=2 ttl=252 time=55.115 ms
    --- Ping statistics for 172.16.3.37 ---
    5 packet(s) transmitted, 5 packet(s) received, 0.0% packet loss
    round-trip min/avg/max/std-dev = 53.773/54.543/55.196/0.634 msSuccess rate is 100 percent (5/5),

    Means Fincle application working fine.


    SOP To Switch over WAN link from BSNL MPLS (Primary Link) to
    Tata MPLS (Secondary link) in case of Reliability issue / Packet Drops
    Issue or Flapping Issue in BSNL Link.
    [router]dis bgp peer ipv4
    BGP local router ID: 10.201.35.17
    Local AS number: 65003
    Total number of peers: 2 Peers in established state: 1

    Peer AS MsgRcvd MsgSent OutQ PrefRcv Up/Down State


    10.201.35.18 9829 0 0 0 0 00:00:01 Established
    10.210.129.117 4755 118 20 0 3792 00:15:14 Established

    [router]bgp 65003

    [router-bgp]peer 10.201.35.18 ignore (To ignore neighbor ship with BSNL peer 10.201.35.18)

    [router]dis bgp peer ipv4

    BGP local router ID: 10.201.35.17


    Local AS number: 65003
    Total number of peers: 2 Peers in established state: 1

    Peer AS MsgRcvd MsgSent OutQ PrefRcv Up/Down State


    10.201.35.18 9829 0 0 0 0 00:00:01 Idle(Admin)
    10.210.129.117 4755 150 27 0 3797 00:21:51 Established

    Now packet will pass through Tata MPLS Link (via 10.210.129.117)

    Remember again when BSNL Link will stable , we have to switch over from Tata to BSNL link with below
    commands

    [router]bgp 65003

    [router-bgp]undo peer 10.201.35.18 ignore (To remove ignore BGP peer 10.201.35.18)

    [router]dis bgp peer ipv4


    BGP local router ID: 10.201.35.17
    Local AS number: 65003
    Total number of peers: 2 Peers in established state: 1

    Peer AS MsgRcvd MsgSent OutQ PrefRcv Up/Down State


    10.201.35.18 9829 0 0 0 0 00:05:01 Established
    10.210.129.117 4755 118 20 0 3792 00:15:14 Established

    Now packet will pass through BSNL link (via 10.201.35.18)

    You might also like