phrozen Posted January 3, 2015 · Report post Всех с новым годом! А нам Cisco сюрприз принесла, всё работало и вдруг инет отпал, захожу в консоль, а там запись no ip routin и маршрут интернета пропал. Кто что может подсказать. Share this post Link to post Share on other sites
YuryD Posted January 3, 2015 · Report post Интерфейс хоть не погас ? траффик и мас-адреса есть на входе ? Share this post Link to post Share on other sites
phrozen Posted January 3, 2015 · Report post интерфейс не погас только no ip route-cache, трафик был не значительный 50 кбит/с маки не смотрел надо было запускать. Share this post Link to post Share on other sites
vurd Posted January 3, 2015 · Report post Вангую на коммунити public с доступом из мира. Share this post Link to post Share on other sites
YuryD Posted January 3, 2015 · Report post интерфейс не погас только no ip route-cache, трафик был не значительный 50 кбит/с маки не смотрел надо было запускать. sho run | incl route sho ip rou | incl 0.0.0.0 Share this post Link to post Share on other sites
phrozen Posted January 3, 2015 · Report post MainRouter#sho run | incl route default-router 172.27.0.1 ip route 0.0.0.0 0.0.0.0 85.93.40.209 MainRouter#sho ip rou | incl 0.0.0.0 Gateway of last resort is 85.93.40.209 to network 0.0.0.0 10.0.0.0/24 is subnetted, 1 subnets C 10.0.0.0 is directly connected, GigabitEthernet0/3 S* 0.0.0.0/0 [1/0] via 85.93.40.209 Share this post Link to post Share on other sites
YuryD Posted January 3, 2015 · Report post S* 0.0.0.0/0 [1/0] via 85.93.40.209 Ну есть же маршрут. осталось посмотреть в интерфейс. трассировка на вас кончается на 7 85.93.61.65 (85.93.61.65) 57.538 ms 56.517 ms 57.066 ms Share this post Link to post Share on other sites
phrozen Posted January 3, 2015 · Report post MainRouter#sh interfaces gigabitEthernet 0/1 GigabitEthernet0/1 is up, line protocol is up Hardware is BCM1250 Internal MAC, address is 0011.92a2.ef1b (bia 0011.92a2.ef1b) Description: INTERNET Internet address is 85.93.ххх.ххх/30 MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec, reliability 255/255, txload 1/255, rxload 9/255 Encapsulation ARPA, loopback not set Keepalive set (10 sec) Full-duplex, 1000Mb/s, link type is force-up, media type is LX output flow-control is unsupported, input flow-control is XON ARP type: ARPA, ARP Timeout 04:00:00 Last input 00:00:00, output 00:00:00, output hang never Last clearing of "show interface" counters never Input queue: 0/75/2121/7193 (size/max/drops/flushes); Total output drops: 0 Queueing strategy: fifo Output queue: 0/40 (size/max) 5 minute input rate 35776000 bits/sec, 4135 packets/sec 5 minute output rate 2883000 bits/sec, 2767 packets/sec 1508336213 packets input, 3484633057 bytes, 0 no buffer Received 48413 broadcasts, 0 runts, 0 giants, 0 throttles 741 input errors, 0 CRC, 0 frame, 741 overrun, 0 ignored 0 watchdog, 216326 multicast, 0 pause input 0 input packets with dribble condition detected 1135859585 packets output, 3041066501 bytes, 0 underruns 2 output errors, 0 collisions, 4 interface resets 0 babbles, 0 late collision, 0 deferred 2 lost carrier, 0 no carrier, 0 pause output 0 output buffer failures, 0 output buffers swapped out Share this post Link to post Share on other sites
Smoke Posted January 3, 2015 · Report post не люблю так говорить, но помоему пора позвонить админу. Share this post Link to post Share on other sites
phrozen Posted January 3, 2015 (edited) · Report post админ вне зоны ((( Edited January 3, 2015 by phrozen Share this post Link to post Share on other sites
YuryD Posted January 3, 2015 · Report post MainRouter#sh interfaces gigabitEthernet 0/1 GigabitEthernet0/1 is up, line protocol is up Internet address is 85.93.ххх.ххх/30 :) Угу, спрятал ip :) зная шлюз и маску /30 любой пионер посчитает ваш ip С киски хоть шлюз пингуется ? А может просто инет выключили за неоплату. Share this post Link to post Share on other sites
Smoke Posted January 3, 2015 · Report post Тогда давайте разбираться show run | i cef show run int gi0/1 ping 85.93.40.209 ping 8.8.8.8 trace 8.8.8.8 Share this post Link to post Share on other sites
phrozen Posted January 3, 2015 · Report post MainRouter#show run | i cef ip cef MainRouter#show run int gi0/1 Building configuration... Current configuration : 201 bytes ! interface GigabitEthernet0/1 description INTERNET ip address 85.93.ххх.ххх 255.255.255.252 ip nat outside ip virtual-reassembly duplex full speed auto media-type gbic no negotiation auto end MainRouter#ping 85.93.40.209 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 85.93.40.209, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms MainRouter#ping 8.8.8.8 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 8.8.8.8, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 32/32/32 ms Share this post Link to post Share on other sites
phrozen Posted January 3, 2015 · Report post MainRouter#trace 8.8.8.8 Type escape sequence to abort. Tracing the route to 8.8.8.8 1 85.93.40.209 0 msec 12 msec 0 msec 2 85.93.61.29 4 msec 4 msec 4 msec 3 85.93.61.62 0 msec 0 msec 4 msec 4 79.126.124.57 4 msec 0 msec 4 msec 5 79.126.126.153 12 msec 8 msec 8 msec 6 * 188.254.78.5 28 msec 36 msec 7 95.167.90.48 92 msec 28 msec 32 msec 8 72.14.215.196 44 msec 88 msec 88 msec 9 216.239.47.149 32 msec 216.239.47.145 28 msec 216.239.47.147 32 msec 10 8.8.8.8 28 msec 28 msec 32 msec Share this post Link to post Share on other sites
Smoke Posted January 3, 2015 · Report post Интернет у вас на железке есть - теперь попробуйте сформулировать проблему чуть более развернуто чем пропал ip routing. Share this post Link to post Share on other sites
phrozen Posted January 3, 2015 (edited) · Report post да сейчас есть. буквально 3 часа тому назад он не был, я зашёл на роутер и вижу в конфиге запись no ip routing на интерфейсах no ip route-cache нет маршрута в интернет (ip route xxx xxx xx), я это исправляю и инет возвращается. Edited January 3, 2015 by phrozen Share this post Link to post Share on other sites
YuryD Posted January 3, 2015 · Report post Интернет у вас на железке есть - теперь попробуйте сформулировать проблему чуть более развернуто чем пропал ip routing. А он и не пропадал, судя по 5-минутным счетчикам 5 minute input rate 35776000 bits/sec, 4135 packets/sec 5 minute output rate 2883000 bits/sec, 2767 packets/sec Share this post Link to post Share on other sites
stepashka Posted January 3, 2015 · Report post MainRouter#sho run | incl route default-router 172.27.0.1 ip route 0.0.0.0 0.0.0.0 85.93.40.209 MainRouter#sho ip rou | incl 0.0.0.0 Gateway of last resort is 85.93.40.209 to network 0.0.0.0 10.0.0.0/24 is subnetted, 1 subnets C 10.0.0.0 is directly connected, GigabitEthernet0/3 S* 0.0.0.0/0 [1/0] via 85.93.40.209 Вы это, определитесь или default или ip routing Share this post Link to post Share on other sites
Smoke Posted January 3, 2015 · Report post Выложите сюда show log желательно до момента отключения cef и routing Share this post Link to post Share on other sites
YuryD Posted January 3, 2015 · Report post да сейчас есть. буквально 3 часа тому назад он не был, я зашёл на роутер и вижу в конфиге запись no ip routing на интерфейсах no ip route-cache нет маршрута в интернет (ip route xxx xxx xx), я это исправляю и инет возвращается. sho log | incl Configured from console Share this post Link to post Share on other sites
phrozen Posted January 3, 2015 · Report post так работало пол года, default-router 172.27.0.1 убрать? MainRouter#sho log Syslog logging: enabled (12 messages dropped, 2 messages rate-limited, 0 flushes, 0 overruns, xml disabled, filtering disabled) No Active Message Discriminator. No Inactive Message Discriminator. Console logging: level debugging, 5630 messages logged, xml disabled, filtering disabled Monitor logging: level debugging, 0 messages logged, xml disabled, filtering disabled Buffer logging: level informational, 5627 messages logged, xml disabled, filtering disabled Logging Exception size (8192 bytes) Count and timestamp logging messages: disabled Persistent logging: disabled No active filter modules. ESM: 0 messages dropped Trap logging: level informational, 5631 message lines logged Share this post Link to post Share on other sites
DVM-Avgoor Posted January 3, 2015 · Report post Может она просто ребутнулась? Share this post Link to post Share on other sites
Smoke Posted January 3, 2015 · Report post Оставьте это админу. Вы не весь лог выложили жмите пробел Share this post Link to post Share on other sites
phrozen Posted January 3, 2015 · Report post Log Buffer (8192 bytes): otocol on Interface Virtual-Access43, changed state to down Jan 3 08:44:35.949: %LINK-3-UPDOWN: Interface Virtual-Access210, changed state to down Jan 3 08:44:36.949: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access210, changed state to down Jan 3 08:44:56.101: %LINK-3-UPDOWN: Interface Virtual-Access40, changed state to down Jan 3 08:44:57.089: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access40, changed state to down Jan 3 08:45:29.049: %LINK-3-UPDOWN: Interface Virtual-Access105, changed state to up Jan 3 08:45:30.049: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access105, changed state to up Jan 3 08:46:37.929: %LINK-3-UPDOWN: Interface Virtual-Access178, changed state to up Jan 3 08:46:38.929: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access178, changed state to up Jan 3 08:48:40.748: %LINK-3-UPDOWN: Interface Virtual-Access5, changed state to up Jan 3 08:48:41.748: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access5, changed state to up Jan 3 08:51:47.701: %LINK-3-UPDOWN: Interface Virtual-Access165, changed state to up Jan 3 08:51:48.701: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access165, changed state to up Jan 3 08:58:17.450: %LINK-3-UPDOWN: Interface Virtual-Access146, changed state to down Jan 3 08:58:18.446: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access146, changed state to down Jan 3 09:01:41.787: %LINK-3-UPDOWN: Interface Virtual-Access155, changed state to down Jan 3 09:01:42.771: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access155, changed state to down Jan 3 09:01:55.719: %LINK-3-UPDOWN: Interface Virtual-Access126, changed state to up Jan 3 09:01:56.719: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access126, changed state to up Jan 3 09:03:05.515: %LINK-3-UPDOWN: Interface Virtual-Access52, changed state to down Jan 3 09:03:06.511: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access52, changed state to down Jan 3 09:04:35.127: %LINK-3-UPDOWN: Interface Virtual-Access235, changed state to up Jan 3 09:04:36.127: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access235, changed state to up Jan 3 09:05:00.747: %LINK-3-UPDOWN: Interface Virtual-Access213, changed state to down Jan 3 09:05:01.743: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access213, changed state to down Jan 3 09:05:09.339: %LINK-3-UPDOWN: Interface Virtual-Access233, changed state to up Jan 3 09:05:10.339: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access233, changed state to up Jan 3 09:06:01.995: %LINK-3-UPDOWN: Interface Virtual-Access85, changed state to down Jan 3 09:06:02.991: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access85, changed state to down Jan 3 09:07:10.864: %IP_VFR-3-SYSTEM_ERROR: GigabitEthernet0/1: IP VFR System failure - A fragment packet with out pak-subblock Jan 3 09:07:13.740: %LINK-3-UPDOWN: Interface Virtual-Access113, changed state to down Jan 3 09:07:14.736: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access113, changed state to down Jan 3 09:07:17.844: %LINK-3-UPDOWN: Interface Virtual-Access77, changed state to up Jan 3 09:07:18.844: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access77, changed state to up Jan 3 09:13:40.900: %LINK-3-UPDOWN: Interface Virtual-Access167, changed state to down Jan 3 09:13:41.892: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access167, changed state to down Jan 3 09:13:57.160: %LINK-3-UPDOWN: Interface Virtual-Access134, changed state to up Jan 3 09:13:58.160: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access134, changed state to up Jan 3 09:15:38.989: %LINK-3-UPDOWN: Interface Virtual-Access110, changed state to down Jan 3 09:15:39.985: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access110, changed state to down Jan 3 09:16:55.885: %LINK-3-UPDOWN: Interface Virtual-Access47, changed state to down Jan 3 09:16:56.881: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access47, changed state to down Jan 3 09:21:16.253: %LINK-3-UPDOWN: Interface Virtual-Access98, changed state to up Jan 3 09:21:17.253: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access98, changed state to up Jan 3 09:23:18.798: %LINK-3-UPDOWN: Interface Virtual-Access223, changed state to down Jan 3 09:23:19.794: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access223, changed state to down Jan 3 09:24:02.906: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access175, changed state to down Jan 3 09:24:04.910: %LINK-3-UPDOWN: Interface Virtual-Access175, changed state to down Jan 3 09:24:32.343: %LINK-3-UPDOWN: Interface Virtual-Access208, changed state to up Jan 3 09:24:33.343: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access208, changed state to up Jan 3 09:24:38.599: %LINK-3-UPDOWN: Interface Virtual-Access5, changed state to down Jan 3 09:24:39.599: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access5, changed state to down Jan 3 09:25:08.347: %LINK-3-UPDOWN: Interface Virtual-Access56, changed state to up Jan 3 09:25:09.347: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access56, changed state to up Jan 3 09:25:59.575: %LINK-3-UPDOWN: Interface Virtual-Access247, changed state to down Jan 3 09:26:00.575: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access247, changed state to down Jan 3 09:26:36.719: %LINK-3-UPDOWN: Interface Virtual-Access61, changed state to down Jan 3 09:26:37.715: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access61, changed state to down Jan 3 09:29:38.931: %LINK-3-UPDOWN: Interface Virtual-Access202, changed state to down Jan 3 09:29:39.931: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access202, changed state to down Jan 3 09:30:26.755: %LINK-3-UPDOWN: Interface Virtual-Access38, changed state to down Jan 3 09:30:27.755: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access38, changed state to down Jan 3 09:33:41.236: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access168, changed state to down Jan 3 09:33:42.040: %LINK-3-UPDOWN: Interface Virtual-Access168, changed state to down Jan 3 09:33:43.392: %LINK-3-UPDOWN: Interface Virtual-Access135, changed state to up Jan 3 09:33:44.392: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access135, changed state to up Jan 3 09:37:41.171: %LINK-3-UPDOWN: Interface Virtual-Access3, changed state to up Jan 3 09:37:42.171: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access3, changed state to up Jan 3 09:38:23.663: %LINK-3-UPDOWN: Interface Virtual-Access235, changed state to down Jan 3 09:38:24.659: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access235, changed state to down Jan 3 09:39:40.852: %LINK-3-UPDOWN: Interface Virtual-Access125, changed state to up Jan 3 09:39:41.852: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access125, changed state to up Jan 3 09:45:39.056: %LINK-3-UPDOWN: Interface Virtual-Access96, changed state to down Jan 3 09:45:40.052: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access96, changed state to down Jan 3 09:46:23.933: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to up Jan 3 09:46:24.933: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state to up Jan 3 09:47:25.745: %LINK-3-UPDOWN: Interface Virtual-Access18, changed state to down Jan 3 09:47:26.741: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access18, changed state to down Jan 3 09:50:06.375: %LINK-3-UPDOWN: Interface Virtual-Access163, changed state to up Jan 3 09:50:07.375: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access163, changed state to up Jan 3 09:50:56.195: %LINK-3-UPDOWN: Interface Virtual-Access66, changed state to up Jan 3 09:50:57.195: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access66, changed state to up Jan 3 10:09:33.365: %LINK-3-UPDOWN: Interface Virtual-Access66, changed state to down Jan 3 10:09:34.361: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access66, changed state to down MainRouter# Share this post Link to post Share on other sites
Smoke Posted January 3, 2015 · Report post весь лог собираете в аттач тхт файл и прикладываете сюда. иначе мы с вами долгенько и show ver канеш Share this post Link to post Share on other sites
