About aweer1234

aweer1234 · 02-25-2016

Dear All, Our equipment Cisco 7609-S today detected numbers of packets to ips not exist in routing table and punted to cpu which caused high cpu loading. Could you please advise if there any solution and how we can prevent such situation happen?As...

aweer1234 · 02-03-2016

Dear All, Our network have two ibgp session running between Cisco and Juniper,and one of ibgp session have higher local preference than another session,and also incoming traffic via the first ibgp session,but everytime we tried to shutdown the bgp...

aweer1234 · 01-13-2016

Dear All, Our company have router cisco 7609-S and detected bunch of packets scan port 53 after running command with debug netdr capture packets, As according to my understanding debug netdr function only detected with packets to cpu in cont...

aweer1234 · 01-05-2016

Dear All, I am new here and our company have one Cisco 7609-S and applied with CoPP policy and set with ICMP rate limited with 1mbps,but after that still have some icmp packet time out when try to ping to interface of router.That's not impact fo...

aweer1234 · 03-16-2016

Hello Giuseppe, Thanks for your reply,i have just adjust to only have one iBGP session from cisco to juniper,and cisco have full views received from juniper router and with ospf running inside.When we shutdown the bgp session juniper, cisco router wi...

aweer1234 · 03-14-2016

Hello Giuseppe, Sorry to re-open this case,i have tried to bgp next-hop tracking solution of building up a lab with Cisco-Juniper router with two ibgp session and running ospf inside now,the first link with lower ospf cost with preferred path,but ho...

aweer1234 · 03-01-2016

Dear Philip, I can't confirm as its always different source ip address and destination ip address,and when the cpu normal also can see many packets to cpu with dst port 53,so i am afraid if its legitimate traffic,and meanwhile i also found many pac...

aweer1234 · 02-26-2016

Hello Giuseppe, Thanks for your information! Beside this i have found a lot of packets with dst port 53,and i know debug netdr suppose only detected packets go to/from our router,and it should be control plane packets. But could you please advise why...

aweer1234 · 02-26-2016

Hi Philip, We do have default route in routing table,but for those problem route after i issue command below and shows drop and didn't lookup to default route,i guess this is the caused why hit to cpu? # show ip cef 248.211.5.0240.0.0.0/4 drop But ...

Member Since	‎12-28-2015 05:38 PM
Date Last Visited	‎08-18-2017 03:53 AM
Posts	21

User Statistics

User Activity

IP route not exist in routing table punted to CPU

High CPU loading after the bgp session down.

Many DNS port 53 scaned packets detected in debug netdr

ICMP issue for CoPP

Hello Giuseppe,

Hello Giuseppe,

Dear Philip,

Hello Giuseppe,

Hi Philip,