Irregular line protocol flapping on HSSI

I have been experiencing flapping (only line protocol) on this interface from time to time.
I contacted our upstream we are connected to via this interface but there were not any error indications on his side.
I would like to ask you to provide me with some recommendations in this issue.
Please find a printout og "sh int HSSI" below.
Hssi11/0 is up, line protocol is up
Hardware is cxBus HSSI
MTU 4470 bytes, BW 44210 Kbit, DLY 200 usec,
reliability 255/255, txload 17/255, rxload 57/255
Encapsulation FRAME-RELAY IETF, crc 16, loopback not set
Keepalive set (10 sec)
LMI enq sent 710362, LMI stat recvd 705854, LMI upd recvd 0, DTE LMI up
LMI enq recvd 0, LMI stat sent 0, LMI upd sent 0
LMI DLCI 0 LMI type is ANSI Annex D frame relay DTE
Broadcast queue 0/256, broadcasts sent/dropped 0/0, interface broadcasts 0
Last input 00:00:01, output 00:00:00, output hang never
Last clearing of "show interface" counters 11w5d
Queueing strategy: fifo
Output queue 0/40, 807776 drops; input queue 0/75, 5732 drops
30 second input rate 9977000 bits/sec, 1672 packets/sec
30 second output rate 3101000 bits/sec, 1296 packets/sec
1689997250 packets input, 2615467679 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 31 throttles
0 parity
67455362 input errors, 0 CRC, 0 frame, 67455362 overrun,, 0 abort
1851303162 packets output, 661571480 bytes, 0 underruns
0 output errors, 0 applique, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
Please fin

You have a very large nuber of errors:
"67455362 input errors" approx 1% traffic.
Reason:
"overrun
Number of times the serial receiver hardware was unable to hand received data to a hardware buffer because the input rate exceeded the receiver's ability to handle
the data."
With that large number of errors the link
can flap (LMI packets dropped).

Similar Messages

  • Line Protocol flapping between 2 routed ports over a 1Gb circuit

    Hi,
    We currently have a 1Gb circuit between 2 sites that is presented to us as copper ethernet on both ends. 
    One end is a Cisco 4948, the other a 3750E.
    Our switching connect into the ISP NTE devices.
    Both our switch ports are routed ports on a P2P subnet.
    The A-end (3750E) of the circuit is showing up/up
    But the B-end (4948) the interface flaps constantly (up then drops after 3 seconds). The time until the interface shows up again varies between 4-10 seconds.
    Throughout the flaps there is not a time when we can ping between both switches.
    The B-end switch has been replaced. And the cable between the B-end switch and the B-end NTE has been tested fully.
    The configuration on the interfaces are fairly standard:
    - ip address
    - speed auto
    - duplex auto
    (I've tried all combinations of speed/duplex settings at both ends)
    The ISP attended the B-end NTE and reported a loss of signal from our B-end Switch. They report that a test from the B-end NTE to the A-end is successful.
    What further steps could be taken to troubleshoot this?
    No configuration changes were made at the time of the issue.
    Is this firmly an ISP issue to investigate?
    Any suggestions welcome.
    Thanks,
    Kyle

    Hello
    i am suprised the ISP didn't investige both end on this circuit !
    - Have you check physically on the Nte device for errors ( rx -tx  link LEDs etc )
     - powered the Nte down -chaned the cabling BOTH of ends?
     - used a different port?
      - performed a TDR ?
     - get the isp to attend site A
    res
    paul

  • Line protocol question

    Okay, this might seem like a really stupid question but it's got me stumped.
    What the hell does "line protocol down" mean and how the hell do I fix it? I'm using a Cisco 2500 series router, and it's occuring on serial port 0 on BOTH routers. I've checked, double checked, re double checked, and triple checked (quadruple checked?) the wiring and the physical wiring is fine...
    Can anyone provide any insights to this at all for me? I'd greatly appreciate it.
    TIA

    The line protocol state (up or down) reflects the layer 2 status of the interface. If your serial interface is saying that its state is up/down it means that it knows that it is plugged into something on the interface but that there is a layer 2 connectivity problem.
    The nature of how the router determines the layer 2 status depends somewhat on the type of interface. On Serial interfaces the determination is based on the keepalives. So basically what the router is saying is that keepalives are not working on the router. There are a couple of things that can prevent keepalives on the serial interface, such as different protocols being configured (one end may be Cisco HDLC and the other end is PPP). If it was Frame Relay a mismatch of LMI type may cause it. Given your comment about using 2500 and that both sides are showing protocol down I am going to guesss that you have the routers configured back to back. And I am going to guess that you have not configured clock rate on whichever router has the DCE serial cable connected. When routers are back to back and do not connect to provider equipment, you need one of them to generate clocking (and it needs to be the one with the DCE cable). So check your cables, find which one is DCE, and configure clock rate on that router.
    HTH
    Rick

  • C819G-4G-V-K9 help (no ip address) Cellular0 is up (spoofing), line protocol is up (spoofing)

    We recently purchased a C819G-4G-V-K9 for a remote site that has no ISP available.  I can't seem to get this working properly.  I can tell the cell portion is up and working becuase I can send the router a text message and I receive it on the router.  The cell 0 interface however, is not getting a dhcp address.  Below is my configuration:
    hostname Router
    boot-start-marker
    boot system flash:c800-universalk9-mz.SPA.153-3.M.bin
    boot-end-marker
    aqm-register-fnf
    no aaa new-model
    memory-size iomem 10
    ip cef
    no ipv6 cef
    multilink bundle-name authenticated
    chat-script lte "" "AT!CALL1" TIMEOUT 60 "OK"
    license udi pid C819G-4G-V-K9 sn FTX180680R8
    vtp domain MobileCell
    vtp mode transparent
    controller Cellular 0
    interface Cellular0
     ip address negotiated previous
     ip nat outside
     ip virtual-reassembly in
     encapsulation slip
     dialer in-band
     dialer string lte
     dialer-group 1
     async mode interactive
    interface FastEthernet0
     no ip address
    interface FastEthernet1
     no ip address
    interface FastEthernet2
     no ip address
    interface FastEthernet3
     no ip address
    interface GigabitEthernet0
     no ip address
     shutdown
     duplex auto
     speed auto
    interface Serial0
     no ip address
     shutdown
     clock rate 2000000
    interface Vlan1
     ip address 192.168.0.1 255.255.255.0
     ip nat inside
     ip virtual-reassembly in
    ip forward-protocol nd
    no ip http server
    no ip http secure-server
    ip nat inside source list 1 interface Cellular0 overload
    ip route 0.0.0.0 0.0.0.0 Cellular0
    dialer-list 1 protocol ip list 1
    access-list 1 permit any
    control-plane
    mgcp behavior rsip-range tgcp-only
    mgcp behavior comedia-role none
    mgcp behavior comedia-check-media-src disable
    mgcp behavior comedia-sdp-force disable
    mgcp profile default
    line con 0
     script dialer lte
     no modem enable
    line aux 0
     script dialer lte
     modem InOut
     no exec
    line 2
     no activation-character
     no exec
     transport preferred none
     transport input all
     stopbits 1
    line 3
     script dialer lte
     modem InOut
     no exec
    line vty 0 4
     login
     transport input all
    scheduler allocate 20000 1000
    end
    Cellular0 is up (spoofing), line protocol is up (spoofing)
      Hardware is 4G WWAN Modem - Verizon Multimode LTE/eHRPD/EVDO RevA/Rev0/1xRTT
      Internet address will be assigned dynamically by the network
      MTU 1500 bytes, BW 9 Kbit/sec, DLY 100000 usec,
         reliability 255/255, txload 1/255, rxload 1/255
      Encapsulation SLIP, loopback not set
      Keepalive not supported
      Last input never, output never, output hang never
      Last clearing of "show interface" counters never
      Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
      Queueing strategy: fifo
      Output queue: 0/10 (size/max)
      5 minute input rate 0 bits/sec, 0 packets/sec
      5 minute output rate 0 bits/sec, 0 packets/sec
         0 packets input, 0 bytes, 0 no buffer
         Received 0 broadcasts (0 IP multicasts)
         0 runts, 0 giants, 0 throttles
         0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
         0 packets output, 0 bytes, 0 underruns
         0 output errors, 0 collisions, 0 interface resets
         0 unknown protocol drops
         0 output buffer failures, 0 output buffers swapped out
         0 carrier transitions
         DCD=down  DSR=down  DTR=up  RTS=up  CTS=up
    Router#sh ip int bri
    Interface                  IP-Address      OK? Method Status                Protocol
    Cellular0                  unassigned      YES manual up                    up
    FastEthernet0              unassigned      YES unset  down                  down

    Not sure if you solved your problem yet, but my Cell0 has a few extra lines. I also have a static IP, so it might not be exactly the same as yours.
    interface Cellular0
    ip address negotiated
    no ip unreachables
    ip nat outside
    ip virtual-reassembly in
    encapsulation slip
    load-interval 30
    dialer in-band
    dialer idle-timeout 0
    dialer string lte
    dialer watch-group 1
    async mode interactive
    routing dynamic
    ip sla auto discovery
    access-list 100 permit ip any any
    dialer watch-list 1 ip 5.6.7.8 0.0.0.0
    dialer watch-list 1 delay route-check initial 60
    dialer watch-list 1 delay connect 1
    dialer-list 1 protocol ip permit
    Cellular0 is up, line protocol is up
      Hardware is 4G WWAN Modem - Verizon Multimode LTE/eHRPD/EVDO RevA/Rev0/1xRTT
      Internet address is xxx.xxx.xxx.xxx/32
      MTU 1500 bytes, BW 50000 Kbit/sec, DLY 100000 usec,
         reliability 255/255, txload 1/255, rxload 1/255
      Encapsulation SLIP, loopback not set
      Keepalive not supported
      Last input 00:00:00, output never, output hang never
      Last clearing of "show interface" counters never
      Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 264
      Queueing strategy: fifo
      Output queue: 0/10 (size/max)
      30 second input rate 11000 bits/sec, 16 packets/sec
      30 second output rate 11000 bits/sec, 16 packets/sec
         1242186 packets input, 660512785 bytes, 0 no buffer
         Received 0 broadcasts (0 IP multicasts)
         0 runts, 0 giants, 0 throttles
         0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
         1164618 packets output, 233386561 bytes, 0 underruns
         0 output errors, 0 collisions, 2 interface resets
         0 unknown protocol drops
         0 output buffer failures, 0 output buffers swapped out
         0 carrier transitions
         DCD=up  DSR=up  DTR=up  RTS=up  CTS=up

  • WLC 5508 APs showing Line Protocol Down

    I have a WLC 5508 (software version 7.5.102.0) and it has 175 APS (mixture of 1131, 1142, 1602, 2602).  Recently I've noticed that
    about 40 of those APs don't work on the 2.4G Dot11Radio0.  sh int dot11 0 shows me:
    Dot11Radio0 is up, line protocol is down
      Hardware is 802.11N 2.4GHz Radio, address is 1833.9d0c.2180 (bia 1833.9d0c.2180)
      MTU 1500 bytes, BW 54000 Kbit/sec, DLY 1000 usec,
         reliability 255/255, txload 1/255, rxload 1/255
      Encapsulation ARPA, loopback not set
      Keepalive set (10 sec)
      ARP type: ARPA, ARP Timeout 04:00:00
      Last input never, output 00:00:00, output hang never
      Last clearing of "show interface" counters never
      Input queue: 0/9355/42086/0 (size/max/drops/flushes); Total output drops: 3769399
      Queueing strategy: fifo
      Output queue: 0/30 (size/max)
      5 minute input rate 11000 bits/sec, 13 packets/sec
      5 minute output rate 0 bits/sec, 0 packets/sec
         150800958 packets input, 597188558 bytes, 0 no buffer
         Received 0 broadcasts (0 IP multicasts)
         0 runts, 0 giants, 0 throttles
         0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
         0 input packets with dribble condition detected
         217132697 packets output, 1132963042 bytes, 0 underruns
         55238 output errors, 0 collisions, 8 interface resets
         0 unknown protocol drops
         0 babbles, 0 late collision, 0 deferred
         0 lost carrier, 0 no carrier
         0 output buffer failures, 0 output buffers swapped out
    I've tried restarting the interface,to no avail, but rebooting the whole AP does bring it back up, but I expect that's a solution to the symptom, not the problem.

    Hi Sean,
    There are certain related bugs of this version. You may need to check whether you are hitting one these. I would suggest staying in 7.4.121.0 code would be a good idea unless you require new features available in 7.5 or 7.6.
    CSCui66891:Marvell-based radio goes down due to stuck multicast packets in driverSymptom:AP's radio interface goes down and does not recover on its own without an AP reboot.Conditions:With releases 7.2.103.0 - 7.2.115.2, 7.3.101.0 - 7.3.112.0, and 7.4.100.0 - 7.4.110.0, this bug applies to all Marvell-based 802.11n Cisco Aironet access points *except* the 1140, 1040, and certain mesh APs.With releases 7.5.90.0 - 7.5.102.0, this bug applies to *all* Marvell-based 802.11n Cisco Aironet access points.Workaround:None. Reboot the AP.
    Known Affected Releases(6)7.6(1.52)7.6(1.50)7.5(102.0)7.6(1.226)7.6(1.95)15.2(4)JA
    Known Fixed Releases(10)10.1(0.74)7.6(1.55)7.5(102.8)10.1(100.0)15.2(4)JN7.6(1.103)10.1(11.5)7.4(111.7)15.2(4)JB7.4(121.0)
    CSCum14069: AP1600/2600 radio down with 7.5.102.0 release  Symptom:[AIR-CAP1602I-Q-K9 (AC power supply) ]---------[Catalyst switch]------------[AIR-CT5508-K9 (7.5.102.0)][AIR-CAP1602I-Q-K9 (PoE) ]----[AIR-PWRINJ5=]-----[ Catalyst switch]------------[AIR-CT5508-K9 (7.5.102.0)][AIR-CAP1602I-Q-K9 (AC power supply) ]---------[non-Cisco non-PoE switch]------------[AIR-CT5508-K9 (7.5.102.0)]AP1600/2600 radios never go UP on above topology if the Catalyst switch was running older IOS such as c3750-ipservices-mz.122-25.SEB4
    Conditions:WLC release 7.5.102.0 specific issue.AP1600/2600 specific issue.Older Catalyst IOS software (e.g. 12.2(25)SEB4)non-Cisco 3rd party switch
    Workaround:Enable "Pre-standard 802.3af switches" option on AP from WLC GUI;WIRELESS => Access Points => All APs => target AP name => Advanced tab => Power Over Ethernet SettingsThis option is required to workaround this problem even if you don't have Pre-standard 802.3af switch nor you're using AC adapter/Power Injector.
    Known Affected Releases:(1)7.5(102.0)Known Fixed Releases:(1)7.5(102.18)
    HTH
    Rasika
    **** Pls rate all useful responses *****

  • AIR-LAP1252AG Line protocol Error

    What are the reason for my Access Point to display interface up and line protocol down?
    I have tried to shut and unshut the interface and it still remain the same?
    AP# sh ip int br
    Interface IP-Address OK? Method Status Protocol
    BVI1 xx.xx.xx.xx YES NVRAM up up
    Dot11Radio0 unassigned YES NVRAM up up
    Dot11Radio0.aa unassigned YES unset up up
    Dot11Radio0.bb unassigned YES unset up up
    Dot11Radio0.cc unassigned YES unset up up
    Dot11Radio1 unassigned YES NVRAM up down
    Dot11Radio1.aa unassigned YES unset up down
    Dot11Radio1.bb unassigned YES unset up down
    Dot11Radio1.cc unassigned YES unset up down
    GigabitEthernet0 unassigned YES NVRAM up up
    GigabitEthernet0.bb unassigned YES unset up up
    GigabitEthernet0.cc unassigned YES unset up up

    dot11 ssid SSID
    vlan 12
    authentication open
    power inline negotiation prestandard source
    username uuuuuu password ppppp
    bridge irb
    interface Dot11Radio0
    no ip address
    no ip route-cache
    ssid SSID
    speed basic-5.5 11.0 6.0 9.0 12.0 18.0 24.0 36.0 48.0 54.0 m4. m5. m6. m7. m8. m9. m10. m11. m12. m13. m14. m15.
    channel 2437
    station-role root
    rts threshold 2312
    interface Dot11Radio0.12
    encapsulation dot1Q 12
    no ip route-cache
    bridge-group 255
    bridge-group 255 subscriber-loop-control
    bridge-group 255 block-unknown-source
    no bridge-group 255 source-learning
    no bridge-group 255 unicast-flooding
    bridge-group 255 spanning-disabled
    interface Dot11Radio0.13
    encapsulation dot1Q 13 native
    no ip route-cache
    no cdp enable
    bridge-group 1
    bridge-group 1 subscriber-loop-control
    bridge-group 1 block-unknown-source
    no bridge-group 1 source-learning
    no bridge-group 1 unicast-flooding
    bridge-group 1 spanning-disabled
    interface Dot11Radio1
    no ip address
    no ip route-cache
    ssid SSID
    dfs band 3 block
    speed basic-6.0 9.0 12.0 18.0 24.0 36.0 48.0 54.0 m0. m1. m2. m3. m4. m5. m6. m7. m8. m9. m10. m11. m12. m13. m14. m15.
    channel dfs
    station-role root
    rts threshold 2312
    interface Dot11Radio1.12
    encapsulation dot1Q 12
    no ip route-cache
    bridge-group 255
    bridge-group 255 subscriber-loop-control
    bridge-group 255 block-unknown-source
    no bridge-group 255 source-learning
    no bridge-group 255 unicast-flooding
    bridge-group 255 spanning-disabled
    interface Dot11Radio1.13
    encapsulation dot1Q 13 native
    no ip route-cache
    no cdp enable
    bridge-group 1
    bridge-group 1 subscriber-loop-control
    bridge-group 1 block-unknown-source
    no bridge-group 1 source-learning
    no bridge-group 1 unicast-flooding
    bridge-group 1 spanning-disabled
    interface GigabitEthernet0
    no ip address
    no ip route-cache
    duplex auto
    speed auto
    bridge-group 1
    no bridge-group 1 source-learning
    bridge-group 1 spanning-disabled
    interface GigabitEthernet0.12
    encapsulation dot1Q 12
    no ip route-cache
    bridge-group 255
    no bridge-group 255 source-learning
    bridge-group 255 spanning-disabled
    interface BVI1
    ip address xx.xx.xxx.xx 255.255.255.0
    no ip route-cache
    ip default-gateway xx.xx.xx.1
    no ip http server
    ip http authentication aaa
    no ip http secure-server
    ip http help-path http://www.cisco.com/warp/public/779/smbiz/prodconfig/help/eag
    ip radius source-interface BVI1

  • What trigger Line Protocol Down?

    Hi,
    Recently I encountered a problem on "line protocol down" as I'd posted on 4th April.
    Could anyone direct me to any webpage or sites where there's a detail explaination of how & what would trigger a line protocol down. Or these kinda data-link failure. Thanks!
    With regards

    Hi Friend,
    There could be few reasons majorly physical layer issue when the line protocol goes down.
    Can you please update which interface was showing line protocol down. Logical interface (SVI) on layer 3 switch, physical port on layer 2/3 switch or any physical interface on router?
    If it is a physical interface on layer 2 switch it is majorly a physical layer issue or may be that particular vlan asscosiated to that port got deleted.
    If it is a layer 3 logical interface showing line protocol down may be there is no vlan associated to that vlan configured on layer 2 switch port or no trunk carrying that vlan on that switch.
    HTH, if yes please rate the post.
    Ankur

  • Line protocol down

    what are all possibilities for having line protocol down status.pls discuss in detail.

    please see below link to get detailed information.
    http://www.cisco.com/univercd/cc/td/doc/cisintwk/itg_v1/tr1915.htm

  • IPsec over GRE tunnel's line protocol is down but able to ping the tunnel destination

    >>both routers are located in different countries and connected with ISP
    >>IPsec over GRE tunnel is configured on both the routers 
    >>tunnel's line protocol is down for both the ends but able to reach the tunnel destination with tunnel source
    >>Packet is not receiving on the router_1 and but could see packets are getting encrypting on the Router_2
    >>ISP is not finding any issue with their end 
    >>Please guide me how i can fix this issue and what need to be check on this ????
    ========================
    Router_1#sh run int Tunnel20
    Building configuration...
    Current configuration : 272 bytes
    interface Tunnel20
     bandwidth 2048
     ip address 3.85.129.141 255.255.255.252
     ip mtu 1412
     ip flow ingress
     delay 1
     cdp enable
     tunnel source GigabitEthernet0/0/3
     tunnel destination 109.224.62.26
    end
    ===================
    Router_1#sh int Tunnel20
    Tunnel20 is up, line protocol is up>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>Keepalive is not set
      Hardware is Tunnel
      Description: *To CRPrgEIQbaghd01 - 2Mb GRE over Shared ISP Gateway*
      Internet address is 3.85.129.141/30
      MTU 17916 bytes, BW 2048 Kbit/sec, DLY 10 usec,
         reliability 255/255, txload 1/255, rxload 1/255
      Encapsulation TUNNEL, loopback not set
      Keepalive not set
      Tunnel source 195.27.20.14 (GigabitEthernet0/0/3), destination 109.224.62.26
       Tunnel Subblocks:
          src-track:
             Tunnel20 source tracking subblock associated with GigabitEthernet0/0/3
              Set of tunnels with source GigabitEthernet0/0/3, 32 members (includes iterators), on interface <OK>
      Tunnel protocol/transport GRE/IP
        Key disabled, sequencing disabled
        Checksumming of packets disabled
      Tunnel TTL 255, Fast tunneling enabled
      Tunnel transport MTU 1476 bytes
      Tunnel transmit bandwidth 8000 (kbps)
      Tunnel receive bandwidth 8000 (kbps)
      Last input 1w6d, output 14w4d, output hang never
      Last clearing of "show interface" counters 2y5w
      Input queue: 0/375/0/0 (size/max/drops/flushes); Total output drops: 0
      Queueing strategy: fifo
      Output queue: 0/0 (size/max)
      5 minute input rate 0 bits/sec, 0 packets/sec
      5 minute output rate 0 bits/sec, 0 packets/sec
         1565172427 packets input, 363833090294 bytes, 0 no buffer
         Received 0 broadcasts (0 IP multicasts)
         0 runts, 0 giants, 0 throttles
         0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
         1778491917 packets output, 1555959948508 bytes, 0 underruns
         0 output errors, 0 collisions, 0 interface resets
         0 unknown protocol drops
         0 output buffer failures, 0 output buffers swapped out
    =============================
    Router_1#ping 109.224.62.26 re 100 sou 195.27.20.14
    Type escape sequence to abort.
    Sending 100, 100-byte ICMP Echos to 109.224.62.26, timeout is 2 seconds:
    Packet sent with a source address of 195.27.20.14
    Success rate is 92 percent (92/100), round-trip min/avg/max = 139/142/162 ms
    Router_1#
    ============================================
    Router_1#sh cry ip sa pe 109.224.62.26 | in caps
        #pkts encaps: 831987306, #pkts encrypt: 831987306, #pkts digest: 831987306
        #pkts decaps: 736012611, #pkts decrypt: 736012611, #pkts verify: 736012611
    Router_1#sh clock
    15:09:45.421 UTC Thu Dec 25 2014
    Router_1#
    ===================
    Router_1#sh cry ip sa pe 109.224.62.26 | in caps
        #pkts encaps: 831987339, #pkts encrypt: 831987339, #pkts digest: 831987339
        #pkts decaps: 736012611, #pkts decrypt: 736012611, #pkts verify: 736012611>>>>>>>>>>>>>>>>>>>>Traffic is not receiving from Router 2 
    Router_1#sh clock
    15:11:36.476 UTC Thu Dec 25 2014
    Router_1#
    ===================
    Router_2#sh run int Tu1
    Building configuration...
    Current configuration : 269 bytes
    interface Tunnel1
     bandwidth 2000
     ip address 3.85.129.142 255.255.255.252
     ip mtu 1412
     ip flow ingress
     load-interval 30
     keepalive 10 3
     cdp enable
     tunnel source GigabitEthernet0/0
     tunnel destination 195.27.20.14
    end
    Router_2#
    =======================
    Router_2#sh run | sec cry
    crypto isakmp policy 10
     authentication pre-share
    crypto isakmp key Router_2 address 195.27.20.14
    crypto isakmp key Router_2 address 194.9.241.8
    crypto ipsec transform-set ge3vpn esp-3des esp-sha-hmac
     mode transport
    crypto map <Deleted> 10 ipsec-isakmp
     set peer 195.27.20.14
     set transform-set ge3vpn
     match address Router_2
    crypto map <Deleted> 20 ipsec-isakmp
     set peer 194.9.241.8
     set transform-set ge3vpn
     match address Router_1
     crypto map <Deleted>
    Router_2#
    ====================================
    Router_2#sh cry ip sa pe 195.27.20.14 | in caps
        #pkts encaps: 737092521, #pkts encrypt: 737092521, #pkts digest: 737092521
        #pkts decaps: 828154572, #pkts decrypt: 828154572, #pkts verify: 828154572>>>>>>>>>>>>Traffic is getting encrypting from router 2 
    Router_2#sh clock
    .15:10:33.296 UTC Thu Dec 25 2014
    Router_2#
    ========================
    Router_2#sh int Tu1
    Tunnel1 is up, line protocol is down>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>Down
      Hardware is Tunnel
      Internet address is 3.85.129.142/30
      MTU 17916 bytes, BW 2000 Kbit/sec, DLY 50000 usec,
         reliability 255/255, txload 1/255, rxload 1/255
      Encapsulation TUNNEL, loopback not set
      Keepalive set (10 sec), retries 3
      Tunnel source 109.224.62.26 (GigabitEthernet0/0), destination 195.27.20.14
       Tunnel Subblocks:
          src-track:
             Tunnel1 source tracking subblock associated with GigabitEthernet0/0
              Set of tunnels with source GigabitEthernet0/0, 2 members (includes iterators), on interface <OK>
      Tunnel protocol/transport GRE/IP
        Key disabled, sequencing disabled
        Checksumming of packets disabled
      Tunnel TTL 255, Fast tunneling enabled
      Tunnel transport MTU 1476 bytes
      Tunnel transmit bandwidth 8000 (kbps)
      Tunnel receive bandwidth 8000 (kbps)
      Last input 1w6d, output 00:00:02, output hang never
      Last clearing of "show interface" counters never
      Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 14843
      Queueing strategy: fifo
      Output queue: 0/0 (size/max)
      30 second input rate 0 bits/sec, 0 packets/sec
      30 second output rate 0 bits/sec, 0 packets/sec
         1881547260 packets input, 956465296 bytes, 0 no buffer
         Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
         0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
         1705198723 packets output, 2654132592 bytes, 0 underruns
         0 output errors, 0 collisions, 0 interface resets
         0 unknown protocol drops
         0 output buffer failures, 0 output buffers swapped out
    =============================
    Router_2#ping 195.27.20.14 re 100 sou 109.224.62.26
    Type escape sequence to abort.
    Sending 100, 100-byte ICMP Echos to 195.27.20.14, timeout is 2 seconds:
    Packet sent with a source address of 109.224.62.26
    Success rate is 94 percent (94/100), round-trip min/avg/max = 136/143/164 ms
    Router_2#
    =========================

    Hello.
    First of all, try to reset IPSec (clear crypto isakmp sa ..., clear crypto session ...).
    Configure inbound ACL on the router to match esp protocol and check if the packets arrive.
    Please provide full output "show crypto ipsec sa"
     from both sides.

  • GigabitEthernet1/1 is up, line protocol is down (notconnect)

    Hi All,
    I am really curious to investigate a possible reason behind this error message.
    During the configuration of a port channel bundled with 2 links I have the error in the subject but only for one side of the connection and only for one link part of the port channel.
    On the other side the corrispondent interface was up/up and the other link part of the port channel was able to go up with no issue (for all the configuration is the same).
    Background info:
    - The link in discussion was connecting the two Multilayer swicthes before the configuration of the port channel with no issue
    - The port channel is a L2 etherchannel
    - What was done was simply to shutdown the interface on both swicthes, add the command channel group xx mode on  on both side of the connection and then bring up the connection with the result above showed: one side up/down (not connect) and the other side up/up
    I am excluding problem with the configuration. The reason is simple: i just reply the configuration to the all links (total 2) part of the port channel with no issue.
    Can be a cabling problem (SFP)? Again keep in mind that before the change, this link was active with no issue for 4 years.
    Thanks all.

    Hi Peter,
    Find below the requested output.
    I forgot to mention something:
    The etherchannel is a L2
    The mode employed to create the port channel was on
    In any case what I did in the meanwhile was:
    - To check the cable -> It is ok
    - I did not check the SFP but I configured the involved interfaces as L3 and I bringed up both with no issue. They are connected so I am assuming that the SFP is ok. Do you agree?
    At this point due to the fact that:
    Configuration is working properly for the second link part of the same portchannel
    The cable and sfp is ok
    The only problem that I can see here is the Etherchannel Modes adopted: I heard that on modes is not the best practice. The best is use the LACP
    Here the requested output:
    show int gi1/1 capa
    Dot1x:                 yes
      Model:                 WS-X6748-SFP
      Type:                  1000BaseSX
      Speed:                 1000
      Duplex:                full
      Trunk encap. type:     802.1Q,ISL
      Trunk mode:            on,off,desirable,nonegotiate
      Channel:               yes
      Broadcast suppression: percentage(0-100)
      Flowcontrol:           rx-(off,on,desired),tx-(off,on,desired)
      Membership:            static
      Fast Start:            yes
      QOS scheduling:        rx-(1q8t), tx-(1p3q8t)
      CoS rewrite:           yes
      ToS rewrite:           yes
      Inline power:          no
      SPAN:                  source/destination
      UDLD                   yes
      Link Debounce:         yes
      Link Debounce Time:    yes
      Ports on ASIC:         25,27,29,31,33,35,37,39,41,43,45,47
      Port-Security:         yes
    GigabitEthernet1/1 is up, line protocol is down (notconnect)
      Hardware is C6k 1000Mb 802.3, address is 0019.aa70.0000 (bia 0019.aa70.0006)
      Description:
      MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec,
         reliability 255/255, txload 1/255, rxload 1/255
      Encapsulation ARPA, loopback not set
      Keepalive set (10 sec)
      Full-duplex, 1000Mb/s, media type is SX
      input flow-control is off, output flow-control is off
      Clock mode is auto
      ARP type: ARPA, ARP Timeout 04:00:00
      Last input 00:00:58, output 02:08:13, output hang never
      Last clearing of "show interface" counters 4y10w
      Input queue: 0/2000/66318/0 (size/max/drops/flushes); Total output drops: 1731225685
      Queueing strategy: fifo
      Output queue: 0/40 (size/max)
      5 minute input rate 17000 bits/sec, 25 packets/sec
      5 minute output rate 0 bits/sec, 0 packets/sec
         1705750435550 packets input, 2106584160022948 bytes, 1 no buffer
         Received 245618852 broadcasts (148781910 multicasts)
         0 runts, 48 giants, 1 throttles
         0 input errors, 0 CRC, 0 frame, 66317 overrun, 0 ignored
         0 watchdog, 0 multicast, 0 pause input
         0 input packets with dribble condition detected
         3762458417011 packets output, 3133012553118384 bytes, 0 underruns
         0 output errors, 0 collisions, 4 interface resets
         0 babbles, 0 late collision, 0 deferred
         0 lost carrier, 0 no carrier, 0 PAUSE output
         0 output buffer failures, 0 output buffers swapped out
    show interfaces status err-disabled
    empty
    show etherchannel summary
    120    Po120(SU)        -        Gi1/2(P) Gi1/1(D)

  • %LINEPROTO-CLUSTER_MEMBER_1-5-UPDOWN: Line protocol on Interface FastEthern

    anyone knows this massage from a WS-C3548-XL-EN ?
    %LINEPROTO-CLUSTER_MEMBER_1-5-UPDOWN: Line protocol on Interface FastEthern

    This message is displaying on switch log and it is cause by a possible reload of one of the members switch when the IOS are not the same in all of the switch members. Reloading one of the member switch may cause drop of communications for a couple of sec.

  • LIN protocol

    I am using Labview 7.1 as SW to send LIN command(Identifier+databytes) to an Atmega board which generate the protocol, does anybody know how to calculate in LV the checksum for the identifier and databyte(see the comment below)?
    The checksum is the inverted modulo-256 sum
    over all data bytes(Identifier+databytes). The sum is calculated by an 'add with carry' operation with the carry bit of
    every addition being added to the LSB of the resulting sum.

    HI JB,
    I have used your via in the following way (see attached pic).
    Thanks again
    Attachments:
    Parity in LIN.jpg ‏117 KB

  • Interface flapping and always shows up/up even other side is shutdown

    Hi, there, I have a interface flapping issue in my network. 2 Cat3560 is connected through 2 trunk port configured with port-channel. When I shutdown one of port in Vlan100, other 2 ports in the same vlan will flap going up and down and OSPF will lose the neighbor. One thing I notice that is when I shutdown the switch port, on the other side of router, the L1-L2 is still up/up. I think it should be up/down. I have a keepalive setting on the router interface to 1800. Any body can give me some hints here to troubleshoot?
    Here is the switch configs.
    Building configuration...
    no service pad
    ip subnet-zero
    ip routing
    no ip domain-lookup
    spanning-tree mode pvst
    no spanning-tree optimize bpdu transmission
    spanning-tree extend system-id
    interface Port-channel1
    switchport trunk encapsulation dot1q
    switchport trunk native vlan 999
    switchport trunk allowed vlan 100,200,300,400,600,700
    switchport mode trunk
    interface GigabitEthernet0/1
    switchport access vlan 600
    speed 100
    duplex full
    interface GigabitEthernet0/2
    switchport access vlan 100
    speed 100
    duplex full
    interface GigabitEthernet0/3
    switchport access vlan 600
    speed 100
    duplex full
    interface GigabitEthernet0/4
    switchport access vlan 700
    speed 100
    duplex full
    interface GigabitEthernet0/5
    switchport access vlan 700
    speed 100
    duplex full
    interface GigabitEthernet0/6
    switchport access vlan 100
    speed 100
    duplex full
    interface GigabitEthernet0/7
    switchport access vlan 100
    speed 100
    duplex full
    interface GigabitEthernet0/8
    switchport access vlan 100
    interface GigabitEthernet0/9
    switchport access vlan 100
    speed 100
    duplex full
    interface GigabitEthernet0/10
    switchport access vlan 100
    speed 100
    duplex full
    interface GigabitEthernet0/11
    switchport access vlan 100
    speed 100
    duplex full
    interface GigabitEthernet0/12
    switchport access vlan 100
    speed 100
    duplex full
    interface GigabitEthernet0/13
    switchport access vlan 100
    speed 100
    duplex full
    interface GigabitEthernet0/14
    switchport access vlan 100
    speed 100
    duplex full
    interface GigabitEthernet0/15
    switchport access vlan 100
    speed 100
    duplex full
    interface GigabitEthernet0/16
    switchport access vlan 100
    speed 100
    duplex full
    interface GigabitEthernet0/17
    speed 100
    duplex full
    interface GigabitEthernet0/27
    switchport access vlan 400
    interface GigabitEthernet0/28
    switchport access vlan 400
    interface GigabitEthernet0/29
    switchport access vlan 400
    interface GigabitEthernet0/30
    switchport access vlan 200
    interface GigabitEthernet0/31
    switchport access vlan 200
    interface GigabitEthernet0/45
    switchport access vlan 500
    speed 100
    duplex full
    interface GigabitEthernet0/46
    switchport access vlan 500
    speed 100
    duplex full
    interface GigabitEthernet0/47
    switchport trunk encapsulation dot1q
    switchport trunk native vlan 999
    switchport trunk allowed vlan 100,200,300,400,600,700
    switchport mode trunk
    channel-group 1 mode on
    interface GigabitEthernet0/48
    switchport trunk encapsulation dot1q
    switchport trunk native vlan 999
    switchport trunk allowed vlan 100,200,300,400,600,700
    switchport mode trunk
    channel-group 1 mode on
    interface Vlan1
    no ip address
    shutdown
    interface Vlan100
    ip address 192.168.40.11 255.255.252.0
    no ip redirects
    no ip proxy-arp
    standby 1 ip 192.168.40.1
    standby 1 priority 110
    standby 1 preempt
    standby 1 track Vlan600 20
    interface Vlan200
    no ip address
    interface Vlan600
    ip address 192.168.35.1 255.255.255.0
    router ospf 7
    log-adjacency-changes
    network 192.168.0.0 0.0.255.255 area 0
    ip classless
    =====================
    When I shutdown interface gig 0/2, interface gig0/3 and gig0/4 will go down as well and come back online after a while.
    Thanks for your help.

    Your question is really missing a BUNCH of details, but I will take a stab at it:
    1) Why on earth do you have a keepalive set to 1800 seconds on the router?
    2) Your discussion and config above only talks about qty 2 c3560 switches. Where is the router in this topology?
    3) You are going against several Cisco best practices here with your trunk ports:
    a) I would never config a port-channel as mode 'on' because the switches will ignore any errors on the ports that would not keep the channel stable because you have configured them to hard set on. ALWAYS set the port channel to mode 'desirable silent'. The config needs to match on both ends of the link.
    b) I would never config a port as a trunk mode 'on' without also running UDLD. It appears that your 2-port port-channel trunk above is using copper ports. You MUST enable UDLD on the copper gigabit ports manually (UDLD is enable by default on fiber gigabit ports). You may need to 'udld enable' globally on the switch depending on the IOS version. Obviously, as above, the same config needs to be done on both switches.
    4) The log message that you get when you say ports g0/3 and g0/4 go down, is that for just VLAN 100 or are they line-protocol messages?
    5) When port g0/2 goes down, are there any other ports in VLAN 100 still up?
    6) What are the results of the following commands:
    show int g0/3 switchport
    show spanning-tree summary
    show spanning-tree int po1
    show spanning-tree int g0/2
    show spanning-tree int g0/3
    show spanning-tree int g0/4
    show spanning-tree vlan 100
    show spanning-tree vlan 600
    show int status
    show etherchannel summary
    show etherchannel detail
    show int trunk mod 0
    Post more details and I'll try to help...

  • MAC Flapping Issue

    Dear Folks,
    I am working with a IT organization as network administrator, at client site we are getting the MAC FLAPPING issue since 1 month, due to that some time it completely down my whole network. Scenario is like that, we are using Ruckus AP and Zone director as a WLAN controller which is directly conecteted with our core switch. Rest of indoor AP's are connected with Distribute and access switch. Now since 1 month we are getting in core switch below mention notification -
    #sh log
    Log Buffer (8192 bytes):
    889842: Nov 18 13:46:37.182 IST: %SYS-5-CONFIG_I: Configured from console by iympladmin on console
    889843: 001585: Nov 18 13:47:09.724 IST: %SW_MATM-4-MACFLAP_NOTIF: Host c4d9.879b.cf99 in vlan 13 is flapping between port Gi1/1/4 and port Gi1/1/3 (nhcin-sjp01-2)
    889844: Nov 18 13:49:17.806 IST: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/37, changed state to up
    889845: Nov 18 13:49:19.818 IST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/37, changed state to up
    889846: 001586: Nov 18 14:04:57.394 IST: %SW_MATM-4-MACFLAP_NOTIF: Host c4d9.87aa.d584 in vlan 13 is flapping between port Gi2/0/41 and port Gi2/0/35 (nhcin-sjp01-2)
    889847: 001587: Nov 18 14:13:39.784 IST: %SW_MATM-4-MACFLAP_NOTIF: Host 0008.2292.1440 in vlan 12 is flapping between port Gi2/1/2 and port Gi1/1/4 (nhcin-sjp01-2)
    889848: 001588: Nov 18 14:15:35.735 IST: %SW_MATM-4-MACFLAP_NOTIF: Host 1c3e.843e.c441 in vlan 13 is flapping between port Gi2/0/41 and port Gi2/0/35 (nhcin-sjp01-2)
    889849: Nov 18 14:23:23.346 IST: %SW_MATM-4-MACFLAP_NOTIF: Host 14f6.5afa.ecb9 in vlan 12 is flapping between port Gi2/0/37 and port Gi2/0/35
    889850: 001589: Nov 18 14:23:23.415 IST: %SW_MATM-4-MACFLAP_NOTIF: Host 14f6.5afa.ecb9 in vlan 12 is flapping between port Gi2/0/37 and port Gi2/0/35 (nhcin-sjp01-2)
    889851: Nov 18 14:32:33.860 IST: %SW_MATM-4-MACFLAP_NOTIF: Host c0cb.3886.30cb in vlan 13 is flapping between port Gi2/0/41 and port Gi2/0/35
    889852: 001590: Nov 18 14:32:33.954 IST: %SW_MATM-4-MACFLAP_NOTIF: Host c0cb.3886.30cb in vlan 13 is flapping between port Gi2/0/41 and port Gi2/0/35 (nhcin-sjp01-2)
    889853: 001591: Nov 18 14:33:05.755 IST: %SW_MATM-4-MACFLAP_NOTIF: Host 843a.4b15.187a in vlan 12 is flapping between port Gi2/0/41 and port Gi2/0/35 (nhcin-sjp01-2)
    889854: 001592: Nov 18 14:33:07.017 IST: %SW_MATM-4-MACFLAP_NOTIF: Host 6c88.14a0.93d8 in vlan 12 is flapping between port Gi2/0/41 and port Gi2/0/35 (nhcin-sjp01-2)
    nhcin-sjp01#
    As mentioned in msg 12 & 13 VLAN is our WLAN.
    After getting this msg automatically all network goes down, I need to shut down the associated port winch is directly or indirectly connected with AP, and after some time it will work properly.
    Now I need some mechanism which can be block the duplicate source mac address to preventing from this kind of scenario.
    Regards,
    Shekhar 

    Hi Devils,
    Answer is in below -
    1. Are those MAC addresses actual Wireless Hosts? i.e have you traced them?
    = Yes, those are actual wireless MAC add, I have check in zone director controller.
    2. Are the SSID's set to tunnel?
    =No
    3. Do you have one ZoneDirector or two?
    =Two, both of them are connected with core switch.
    I have been confirmed about that  if wireless users are roaming between two AP or more it will appear the same error msg, now what would be the solution. ????
    What extly the solution is?>
    Where should i implement the solution on switch or zone director?
    Please suggest!!!!!

  • Flapping circuit question and loopback question...

    Two questions)
    1) If someone reset a pc or cable modem will that cause the circuit to flap (as shown below)?
    054396: Oct 21 19:51:24.288 PDT: %LINK-3-UPDOWN: Interface FastEthernet0/25, changed state to down
    054397: Oct 21 19:51:25.289 PDT: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/25, changed state to down
    054398: Oct 22 04:11:50.740 PDT: %LINK-3-UPDOWN: Interface FastEthernet0/25, changed state to up
    054399: Oct 22 04:11:51.776 PDT: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/25, changed state to up
    054400: Oct 22 04:12:29.280 PDT: %LINK-3-UPDOWN: Interface FastEthernet0/25, changed state to down
    054401: Oct 22 04:12:30.308 PDT: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/25, changed state to down
    2) Does this mean someone plugged a loopback adaptor into a switch port?
    020561: Oct 20 02:21:12.212 PDT: %LINK-3-UPDOWN: Interface FastEthernet0/12, changed state to up
    020562: Oct 20 02:21:14.004 PDT: %ETHCNTR-3-LOOP_BACK_DETECTED: Keepalive packet loop-back detected on FastEthernet0/12.
    020563: Oct 20 02:21:14.004 PDT: %PM-4-ERR_DISABLE: loopback error detected on Fa0/12, putting Fa0/12 in err-disable state
    020564: Oct 20 02:21:16.048 PDT: %LINK-3-UPDOWN: Interface FastEthernet0/12, changed state to down
    020565: Oct 20 02:21:43.196 PDT: %PM-4-ERR_RECOVER: Attempting to recover from loopback err-disable state on Fa0/12
    Thank you,

    Thanks for your reply....why would a fe connection go up/down just suddenly then never again (as of yet)....could it be a slightly loose cable that got bumped or due to vibrations?
    098422: Oct 24 00:50:15.227 PDT: %RTD-1-LINK_FLAP: FastEthernet0/1 link down/up 5 times per min
    098424: Oct 24 00:50:25.225 PDT: %RTD-1-LINK_FLAP: FastEthernet0/1 link down/up 5 times per min
    098425: Oct 24 00:50:30.303 PDT: %RTD-1-LINK_FLAP: FastEthernet0/1 link down/up 5 times per min
    098426: Oct 24 00:52:37.483 PDT: %LINK-3-UPDOWN: Interface FastEthernet0/1, changed state to up
    098427: Oct 24 00:52:37.821 PDT: %LINK-3-UPDOWN: Interface FastEthernet0/1, changed state to down
    098428: Oct 24 00:52:41.693 PDT: %LINK-3-UPDOWN: Interface FastEthernet0/1, changed state to up
    098429: Oct 24 00:52:42.535 PDT: %LINK-3-UPDOWN: Interface FastEthernet0/1, changed state to down
    098430: Oct 24 00:52:44.640 PDT: %LINK-3-UPDOWN: Interface FastEthernet0/1, changed state to up

Maybe you are looking for