Cisco Switching/Routing :: 888 And 878 Router Unreachable?
Dec 13, 2012
The problem is that that the routers are not reachable form the corporate LAN after some time. Pinging the routers IP is not working anymore. When the network cable is unplugged and plugged in again the routers are responding again. The same applies when I connect my Laptop to the router. The interface is responsive right after I connect the cable. Also other devices on the network can ping the router. But after a few hours or sometimes 1,5 day the router is unreachable form the corporate network.
The problem first started a few weeks ago. The configuration did not change. The router 878 was not responsing and after changing all the cables and conncting it to another swith the problem remained. So I suspected a hardware failure and bought a replacement 888. After configuring the 888 it showed the same behaviour as the 878 router. The DSL connection is working all the time. I can even set up a vpn connection to the router and start a telnet session. than I can ping the internap IP of the router but pinging another device is not working.
What I noticed after the command sh int vlan1 is that the last input counter keeps increasing.whats causing this or how to debug?
the IP next hop 10.84.23.254 is cascaded on my customer LAN . At nominal time the router advertsed the route in BGP
pjnb1376#sh ip bgp nei 57.213.169.169 ad Next Hop Metric LocPrf Weight Path *> 10.84.22.0/23 10.84.23.254 0 32768 i
When the lan interface of the router goes down , the router still advertise the route !!! Even if the IP next hop 10.84.23.254 is not reacheable anymore ....
The box is a Cisco 1941 using 1900-universalk9-mz.SPA.151-4.M1
My company has a Cisco IAD 2400 which is handling our phones and the internet (from Service Provider). We are adding a second router, a Cisco 1921, to our network,I think I have everything set up correctly. One department is using the 192.168.2.0/27 subnet. I can ping each computer within that subnet. Also, within this subnet, I can ping the router interface at 192.168.2.1. I can ping 192.168.1.2 successfully as well. This is the interface on the 1921 that goes to the 2400. However, if I try to ping 192.168.1.1 (interface on 2400), I get "Reply From 192.168.1.236: Destination Host Unreachable" I get the same thing if I ping 8.8.8.8.Within the 1921, I can ping 192.168.1.1 and 74.125.224.72 (random google ip) successfully.
While working at a client site today, I was troubleshooting some ICMP connectivity for a network we have created.I turned on 'debug ip icmp" on the 3550 switch int he middle, and was inundated with the following debug output:
Jan 25 11:01:14.641: ICMP: dst (172.16.1.7) port unreachable rcv from 172.16.1.5 Jan 25 11:01:14.641: ICMP: dst (172.16.1.7) port unreachable rcv from 172.16.1.5 Jan 25 11:01:14.641: ICMP: dst (172.16.1.7) port unreachable rcv from 172.16.1.5 Jan 25 11:01:14.641: ICMP: dst (172.16.1.7) port unreachable rcv from 172.16.1.5
[code]....
This output fires several times a second, and based on how often it is firing, I am curious if it may be a culprit with respect to the fact that the client has indicated that they have some slow internet.Should the next step be to look at the workstation at 172.16.1.5?
Today one of our 9 Cisco switches a "WS-C2950S" (we also got 2 other WS-C2950S on same network) stop responding icmp ping packages. When i tried to telnet the switch its network was unreachable but i was able to see its existance from other switches by "sh cdp neig". So i decided to fix the situation on a suitable night time work, checking by console cable or even rebooting the device.
Then i started to wonder... what this could possibly be about?We have like 40 clients behind that switch and there was no communication problem during the problem.
I have used this WRT54gl for several years and it's performed flawlessly both wireless and wired. Recently I've extended the reach of my home network by adding a second WRT54g cabled to the network. I also added another PC in a nearby home with a wireless dongle attachment to the network. In setting all this up I've just noticed that the 'Traceroute' and 'Ping' functions in the original WRT54gl do not work. That is, when in the Administration, Diagnostics window and select either function I get a 'Network is unreachable' message instead of the ping/traceroute information.
All other functions on the network seem to work fine, ie..., I can ping the router from anywhere. Both wireless and ethernet connections work fine through it. The newer WRT54G addition to the lan is setup identical and the ping/ trace router work fine with it.Both routers have DHCP disabled. My modem handles it.
Once in a while, I lose Internet connection and at the same time cannot reach my Siemens Speetstream 4100b DSL modem's setup page 192.168.0.1 ; it happened again this morning (from both wired and wirelessy connected computers). When I go to the router's setup page 192.168.1.1 , it would usually in that situation show that the router has not acquired the Internet IP Address; I power-recycle (a few times) both modem and router and eventually the router reports that it has acquired the Internet IP Address, but there is still no Internet, and the DSL modem's setup page 192.168.0.1 is unreacheable.The situation usually self-resolves only in an hour or so after the time the router has acquired the Internet IP Address: Internet starts working, and the DSL modem's setup page 192.168.0.1 becomes reacheable.
I have different types of network clients connecting to both bands of router (5 ghz and 2.4 ghz), and both bands set to WPA2 only. Everything has been set up and working for the past year with no problems.
Suddenly this morning, none of the 2.4 ghz clients can connect and get authenticated. When I attempt to ping them from a Windows 7 desktop connected by a LAN cable, I get Destination Host Unreachable.
The 5 ghz clients are fine and have had no problems. I tested this with the New iPad connected to the 5 ghz band.
Rebooted the E3000 router and the Comcast cable modem, then installed the newest firmware on the E3000 using the web access portal at 192.168.1.1, and still not working.
Changed the WPA2 Personal security mode for the 2.4 ghz band to WPA2 Personal/WPA Mixed Mode, and now all the clients are connected and authenticated and working OK, albeit slower.
What happened? And how can I fix this so I can change the security mode for the 2.4 ghz band back to WPA2 Personal?
P.S. The types of clients that connect to the 2.4 ghz band are 2 Windows 7 desktops, a Windows 7 laptop, and 5 Cisco Wireless N Internet Home Monitoring Cameras. The camera feeds have slowed down considerably using this Mixed mode.
I've tried everything that has been posted so far except for opening up the router itself which I will refuse to do.- Getting = Host Unreachable 192.168.1.20 (I am using 192.168.1.1 as the gateway)- No ping whatsoever even when turning on the router over and over.
I attempted to upgrade the firmware on the WRT54G2 V1 (the newer, slim black model) but it failed. I let the upgrade run for about 10 minutes and it just sat there and link to router disconnected I run ping for 192.168.1.1 but response is "DESTINATION HOST UNREACHABLE". The router is now completely unusable and the ALL LAN ports lights are ON and Internet light is also ON.
After reconfiguring my LMS 4.1 from snmp v2 to snmp v3 the endhost aren't reachable anymore. Before configuring the snmp v3 I have purged the endhost database in order to repopulate it. After the jobs run no endhost could be added to repository. It just says unreachable.
Could it really be a snmpv3 issue? Everytihng else is working as before. I'll have to go back to snmp v2.
So we have a cisco asa 5505. Once a day now (random times) it will suddenly be unreachable along with the hosts connected. If I console in and ping a host from the asa, suddenly it becomes reachable from the outside world again. My job prohibits me from posting the configuration online.
I any running Cisco Works LMS 4.0 on Windows 2008 Enterperise Edition with SP2.I am facing 2 issue which are below:
1. Get message "You are using unsupported Version". As per Cisco document Windows 2008 Ent edition is support by LMS 4.0 2. All of my devices are showing unreachable. I already double check the Devices Credential include SNMP (Read and Write community) and Username and passwords.I can accessble all devices via telnet from the same Cisco Works Machine.
in my test LAB i have used a 5505 running 9.1.1.I have setup a DC (2008R2) and then AD Agent.I have configured and used Identity firewall rules which worked like a charm.I have also used LDAP Auth which also worked fine.I then disabled all the rules but kept the identity firewall checked.Since it was a lab environment, i had to remove the DC for other tests.A few hours later the ASA initially was stuck.I used the console and i saw it could ping noone! not even directly attached PCs or defgw (i was able to ping them before it stucked).No arp table also!the asa did no NATing so no xlate entries were vavailable.Then i sshed to it.I got a blank screen and from console i could see cpu-usage from ssh to 20%I opened a second ssh: nothing. Blank Screen again. cpu-usage from ssh to 40% (overall ~50%)I opened a third ssh: nothing. Blank Screen again. cpu-usage from ssh to 65% (overall ~75%)I issued reload from console! Nothing! it was trying to shut down!I issued reload quick-> that is when console was lost!!I have to unplug it.
The DC that was removed was also the DNS for the ASA.The only log message i could see, before it stuck was "AD Agent is out of reach".i have ttried this 4 times. Always the same. 100% reproducible.I disabled the identity firewall-> no problem! it worked for days.100% reproducable.I downgraded to 8.4.5--> the same for both above actions.
I'm having an issue where when I upgrade from 8.2(5) to 8.4(2) on an active/passive asa 5585 running in transparent mode I can no longer reach the standby ip. The BVI interface appears to be created properly, the device IP and standby IP are listed in the config under the BVI interface and my inside and outside interfaces are both joined to BVI1-group.
I have one instance of WCS 7.0.172.0 (on a Linux host) and a fleet of WiSMs that I'm upgrading from 7.0.98.0 to 7.0.116.0. Every time I run thru the upgrade process from within WCS (scheduled to run overnight, off peak hours) all of the controllers that were upgraded then show as "unreachable". Grepping thru wcs-0-0.log shows messages that the controllers are unreachable via SNMP but running an "snmpget" from the command line to any of the affected controllers works just fine. The only way I've found to remedy this is to stop and restart the WCS service. Considering how long that takes with my deployment...I'd rather not do that every time .
I added Cisco AIR-1142 AP which is registered with WLC 5508 in to LMS 4.1. After restarting AP, the status in LMS showing as unreachable. I am not able to save the configuration in AP and also not able to add SNMP parameters . what is the issue or what are the normal procedure to add a LWAPP in LMS.
Is it really the case that the ASA will not generate ICMP Host Unreachable messages for sub nets connected to any of its interfaces (in breach of RFC1812) as claimed here: [URL]
I'm investigating a situation where an organization uses ASAs to control traffic between different v lans in their internal production systems as well as Internet traffic. They are having problems with internal load balancing because the ASAs do not (as currently configured) generate Host Unreachable packets. Can this be changed in the configuration or not? I have to say, if it can't then I'd urge them to find something else to route between their internal sub nets.
i have my 9 computers 1 prolink modem/router h5200 and tplink switch...for 3 months my connection is quite good..but in the 4th month its starting to Reply 192.168.1.1 Destination net Unreachable..i called up a technician from the network..He changed my modem/router with the same model and it runs for an hour... 5-6 hrs..the problem starts again it begins to ping Reply 192.168.1.1 Destination net Unreachable...b4 my TCP/IP i configured it automatically but now i try to put it manually...my modem/router starts with 192.168.1.1 my first unit starts in 192.168.1.2 and so on.
I am triing to migrate my old ACS to the new one. I am using ACS 5.3 on appliance CSACS-1121. Sometime, i loose the connection to the appliance and i could not connect to the appliance with SSH, i could not start the GUI and the authentication is switched to the secondary instance. As soon as I have traffic, the connection is restored.
I'm trying to configure an snmp notification reciever on WCS 7.0, so that critical alarms get reported to our central console. Following the configuration guide I was able to add the reciever as northbound, but after adding it I get an alarm saying that it is unreachable by WCS so all alarm notification will be suspended. I have tested snmp and ping connectivity between the WCS box and the notification reciever and it works ok, is there some other traffic that I might be missing?. I've seen some packets going from the WCS box to TCP port 7 on the reciever, which as far as I know is the echo service, is that what WCS uses to test connectivity?
I am getting an alarm on WCS where a one controller is down, unreachable from WCS, while the other one is reachable on the same WiSM module. Upon investigation, Status of controller is shown as "Oper-Up" for all controllers on Supervisory engine. Hardware platform is Cisco 6509-E.
WLAN Slot Controller Service IP Management IP SW Version Status ----+-----------+----------------+----------------+-----------+--------------- 2 1 192.167.10.11 172.19.47.65 6.0.196.0 Oper-Up 2 2 192.167.10.12 172.19.47.66 6.0.196.0 Oper-Up
However, I can not ping the managment interface of the down controller while the other controller management interface is pingable. All these interfaces are in the same VLAN.
ping 172.19.47.65 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 172.19.47.65, timeout is 2 seconds: ..... Success rate is 0 percent (0/5)
Problem is fixed when I reboot the problematic Controller. However, this problem re-appears after some time. I am not able to figure out why controller is not able to ping its default-gateway which is an SVI interface on Supervisory card on the same chassis, and showing status UP/UP. Is it a software bug or backplane fault or any other reason ?
Im running 10 units of computers, anyhow my server has no internet connection, the other 9 units has net connection,when i ping the diagnosis is destination host unreachable.I'm using windows XP.
My old router recently died and my ISP was kind enough to offer this Thomson one free. But ever since I got it, my PCs cant see each other on the homegroup. They can all get onto the internet - and by using programs like Dropbox or Teamviewer I can share info from one to the other- but I'd like to get my homegroup working again, Both my PCs are running Win 7, connecting wirelessly to the network. When trying to tracert from one to the other it gives this message: Tracing route to GLaptop.lan [192.168.1.79] over a maximum of 30 hops: 1 GDesktop.lan [192.168.1.82] reports: Destination host unreachable. The problem persists when firewalls on both PCs are disabled, and I've attempted to delete the homegroup on both PCs and re-create it.
My internet connection started to disconnect after an office mate used my PC. I thought it was just the cables but it's not. I pinged my ip address and its okay (sent=4; received=4). But when i ping Yahoo! and other websites, it said that "Destination host unreachable" (sent=4;received=0;lost=4;100% loss). What should I do to make my connection okay? I didn't ask assistance from our IT personnel bcoz they said if i want to reconnect/reinstall connection, I have to get an approved request from our bosses. And I don't like being asked bcoz they are like tyrant bosses.
I am having some issues with my ASA 5510 (running ASA 8.2) dropping ICMP unreachable-fragmentation-required-but-df-bit-set type messages coming in on the outside interface. I have the following entry in the ACL for the outside interface:access-list outside_acl extended permit icmp any interface outside and there are no other entries in that list that should take precedence and drop the packet. Pings from outside to the ASA work when this ACE is present and do no when it is absent so it is clearly taking effect. I see the following entries in the debug log when sending a large non-fragmentable packet (that would cause an intermediate router to send back this ICMP response) out to the internet through the ASa,As far as I can tell I am not running ICMP inspection; I don't want it to do any stateful magic here since the outgoing traffic would have been ordinary data from another protocol and would not have caused an outgoing ICMP connection to be built to match against.
Up until recently one of my sites was able to get to a postilion subnet. Then we started receiving "host unreachable" e-mails. Posting told us SMTP traffic was not getting let in. I've compared the current config to a config that was saved before the issue popped up and found really no noticeable difference.
I tried a packet tracer trace with no luck: SiteB- Firewall# packet-tracer input outside tcp 11.2.2.36 12345 65.19.0.0 25.
Phase: 1 Type: FLOW-LOOKUP Subtype: Result: ALLOW Config: Additional Information: Found no matching flow, creating a new flow [code]...
Result: input-interface: outside input-status: up input-line-status: up output-interface: outside output-status: up output-line-status: up Action: drop Drop-reason: (acl-drop) Flow is denied by configured rule
Attached is a sanitized config. I'm not entirely convinced it's a firewall issue, but I need to some successful testing to prove otherwise.
I bought a RV042G router some days ago to manage 2 adsl lines at my home. Everything works correctly except one thing : i can't configure the bandwidth management. When i go to "Bandwidth Management" menu, then "Bandwidth Management Type" then i choose rate control or priority and i a had some rules to priorize http protocol for example, then i click on save button. After a few seconds of internet usage i loss connectivity to the router and internet and 192.168.1.1 became unreachable to ping. I had to unplung the power cord to restart the router, the same problem still occurs until i remove all the rules ! Some times i even had to do a factory reset because my adsl modems are unreachable behind the router (unable to ping the gateway).
I have 2 brand new systems, a desktop running Windows 7 Pro connected with a had line, and a laptop running Windows 7 Home Premium connected wirelessly. Both can access the router, both can access the internet, both can be pinged from the router. However, they absolutely cannot see each other on the network. If I try to ping by name, the addresses don't resolve. If I try to ping by IP, I get either no reply or the "destination host unreachable."I've disabled firewall completely on both. I've double, triple, quadruple checked all sharing settings (network discovery is enabled on both, sharing enabled everywhere, etc. etc.). I've tried disabling all other network adapters on the laptop, no difference. I've tried all of the online tips about repairing winsock.
We are using Catalyst 3750 switch stacks with software 12.2(44)SE. We have two stacks, only one with IP routing enabled.When we try to run an Acquisition Action on this, from Admin> Collection Settings> User Tracking, the system replies with an error "Failed to start acquisition: Device unreachable. Please enter a valid device"device Center reports "success" on all collector status.Acquisition starts successfully when we try with the other stack.With LMS 4.1 demo, users acquisition runs successfully.
ping 10.0.0.1 -t give me destination host unreachable in the same time when i wright ping 192.168.1.1 -t it give me the correct reply but the net doesnt work
