Jump to content

перегружається cisco 3550

needhelp

By needhelp,
in Router Layer 3

 Share Followers 2

Recommended Posts

needhelp

needhelp 3

Posted
Posted

Періодично перегружається cisco 3550, в чому може бути проблема?

 

sh ver:

Cisco IOS Software, C3550 Software (C3550-IPSERVICESK9-M), Version 12.2(55)SE9, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2014 by Cisco Systems, Inc.
Compiled Tue 04-Mar-14 00:47 by prod_rel_team
Image text-base: 0x00003000, data-base: 0x01608EB8

ROM: Bootstrap program is C3550 boot loader

termv_lan uptime is 37 minutes
System returned to ROM by error - Software Forced Crash Exception (0x0700)!, PC 0x513BC0
System restarted at 17:45:57 UTC Sat Feb 13 2016
System image file is "flash:c3550-ipservicesk9-mz.122-55.SE9/c3550-ipservicesk9-mz.122-55.SE9.bin"

використовується як термінатор vlan ubilling, нагрузка до 300мбіт

Link to post
Share on other sites
needhelp

needhelp 3

Posted
  • Author
Posted (edited) 
show stack:

Minimum process stacks:
 Free/Size   Name
 3644/6000   vegas_flash init
 2592/6000   SaveCrashBuffer
 5720/6000   CDP BLOB
 8512/9000   IP Background
 8684/9000   EEM ED RF
 4188/6000   EEM Shell Director
 5596/6000   vqpc_shim_create_addr_tbl
 5580/6000   SPAN Subsystem
58800/60000  EEM Auto Registration Proc
 5552/6000   SASL MAIN
 6824/12000  Init
 4944/6000   vegas IPC process
 8700/9000   cdp init process
 5408/6000   RADIUS INITCONFIG
 4928/6000   Vegas CrashBuffer
 5660/6000   URPF stats
 2536/3000   Rom Random Update Process
 8216/12000  SSH Process
34864/36000  TCP Command
10692/12000  Virtual Exec

Interrupt level stacks:
Level    Called Unused/Size  Name
  4      279031   6808/9000  CPU NETWORK INTERFACE CHIP
  5       28031   8904/9000  Vegas miami tty xmit hack timer
  6      964688   8936/9000  Clock Timer Vector

Spurious interrupts: 1033

System was restarted by error - Software Forced Crash Exception (0x0700)!, PC 0x513BC0
C3550 Software (C3550-IPSERVICESK9-M), Version 12.2(55)SE9, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Compiled Tue 04-Mar-14 00:47 by prod_rel_team (current version)
Image text-base: 0x00003000, data-base: 0x01608EB8


Stack trace from system failure:
FP: 0x354B5E4, RA: 0x513BC0
FP: 0x354B5F4, RA: 0x513B84
FP: 0x354B624, RA: 0x1292648
FP: 0x354B63C, RA: 0x129246C
FP: 0x354B68C, RA: 0x128B6F8
FP: 0x354B704, RA: 0x12894B4
FP: 0x354B724, RA: 0x128A63C
FP: 0x354B74C, RA: 0x1F84D4


***************************************************
******* Information of Last System Crash **********
***************************************************


Using flash:/crashinfo/crashinfo_1.
Cisco IOS Software, C3550 Software (C3550-IPSERVICESK9-M), Version 12.2(55)SE9, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2014 by Cisco Systems, Inc.
Compiled Tue 04-Mar-14 00:47 by prod_rel_team

Software Forced Crash Exception (0x0700)!
CPU Register Context:
Vector = 0x00000700  PC = 0x00513BC0  MSR = 0x0002B030  CR = 0x42008002
LR = 0x00513B84  CTR = 0x000E5814  XER = 0x00000000
R0 = 0x00513B84  R1 = 0x0354B5E4  R2 = 0x00000000  R3 = 0x00000000
R4 = 0xFFFFFFFE  R5 = 0xFEC0FEC0  R6 = 0xFEE00000  R7 = 0x00003030
R8 = 0x0000B030  R9 = 0x01EB81AC  R10 = 0x01D30000  R11 = 0x00000000
R12 = 0x22000002  R13 = 0x83FC65FF  R14 = 0x00000000  R15 = 0x00000000
R16 = 0x001F84D0  R17 = 0x01CD0000  R18 = 0x00000000  R19 = 0x00000000
R20 = 0x00000000  R21 = 0x01D30000  R22 = 0x0354B6A0  R23 = 0x801370C0
R24 = 0x01E810CC  R25 = 0x0000017C  R26 = 0x00000000  R27 = 0x00000000
R28 = 0x00000001  R29 = 0x01774408  R30 = 0x801370C0  R31 = 0x00000000

Stack trace:
PC = 0x00513BC0, SP = 0x0354B5E4
Frame 00: SP = 0x0354B5F4    PC = 0x00513B84
Frame 01: SP = 0x0354B624    PC = 0x01292648
Frame 02: SP = 0x0354B63C    PC = 0x0129246C
Frame 03: SP = 0x0354B68C    PC = 0x0128B6F8
Frame 04: SP = 0x0354B704    PC = 0x012894B4
Frame 05: SP = 0x0354B724    PC = 0x0128A63C
Frame 06: SP = 0x0354B74C    PC = 0x001F84D4
Frame 07: SP = 0x0354B76C    PC = 0x001F8924
Frame 08: SP = 0x0354B794    PC = 0x001F906C
Frame 09: SP = 0x0354B7B4    PC = 0x001F7640
Frame 10: SP = 0x0354B81C    PC = 0x00A105FC
Frame 11: SP = 0x0354B8B4    PC = 0x00A116BC
Frame 12: SP = 0x0354B93C    PC = 0x00A11DE0
Frame 13: SP = 0x0354B954    PC = 0x0050BB24
Frame 14: SP = 0x0354B96C    PC = 0x00515EE8
Frame 15: SP = 0x0354B9B8    PC = 0x0050A48C

як правильно core dupm зняти? логи після перезагрузки зберігаються?

по дампах знайшов таке:

Note: Core dumps can be difficult to obtain. Only Cisco technical personnel who have access to source code and detailed memory maps must attempt to interpret core dumps. On many platforms, the use of the crashinfo feature can make core dumps unnecessary.

(Тільки технічний персонал Cisco , які мають доступ до вихідного коду і докладних карт пам'яті повинен намагатися інтерпретувати файл дампу пам'яті) взято звідси - http://www.cisco.com/c/en/us/support/docs/ios-nx-os-software/ios-software-releases-122-mainline/12687-appA.html

Edited by needhelp
Link to post
Share on other sites
BARVIT

BARVIT 113

Posted
Posted (edited)

Вы сначала разберите ее и посмотрите на кондеры. Приходила такая - как раз L1ght у меня был, говорит давай откроем почистим, открыли там писец, практически все кондеры вздутые, но при этом он ее до разбора успел прошить и вроде как работала на столе, не успели ее поставить. Перед возвратом отнесли ремонтнику, то заказал кондеры :) 20 с лихуем штук пришли кондеры, в итоге он старые так и не смог выпаять из нее :) Говорит не смог прогреть :)  Хорошо продавец хороший, без вопросов поменял. 

Edited by BARVIT
Link to post
Share on other sites
needhelp

needhelp 3

Posted
  • Author
Posted

Crashinfo:

 

 

Feb 12 11:14:06.300: %DHCP_SNOOPING-5-DHCP_SNOOPING_NONZERO_GIADDR: DHCP_SNOOPING drop message with non-zero giaddr or option82 value on untrusted port, message type: DHCPINFORM, MAC sa: 001d.92d7.83b5
Feb 13 10:25:20.841: %DHCP_SNOOPING-5-DHCP_SNOOPING_NONZERO_GIADDR: DHCP_SNOOPING drop message with non-zero giaddr or option82 value on untrusted port, message type: DHCPREQUEST, MAC sa: 001d.92d7.83b5
Feb 13 10:25:30.149: %DHCP_SNOOPING-5-DHCP_SNOOPING_UNTRUSTED_PORT: DHCP_SNOOPING drop message on untrusted port, message type: DHCPACK, MAC sa: 001d.92d7.83b5
Feb 13 17:42:44.756: %SYS-3-CPUHOG: Task is running for (2000)msecs, more than (2000)msecs (3/2),process = DHCP Snooping.
-Traceback= 15D9090 A4F0C4 A72934 A72FA4 515B90 50C608
Feb 13 17:42:46.760: %SYS-3-CPUHOG: Task is running for (4000)msecs, more than (2000)msecs (4/2),process = DHCP Snooping.
-Traceback= 15D9090 A4F0C4 A72934 A72FA4 515B90 50C608
Feb 13 17:42:48.768: %SYS-3-CPUHOG: Task is running for (6000)msecs, more than (2000)msecs (6/2),process = DHCP Snooping.
-Traceback= 15D9090 A4F0C4 A72934 A72FA4 515B90 50C608
Feb 13 17:42:50.768: %SYS-3-CPUHOG: Task is running for (8000)msecs, more than (2000)msecs (6/2),process = DHCP Snooping.
-Traceback= 15D9090 A4F0C4 A72934 A72FA4 515B90 50C608
Feb 13 17:42:52.528: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0xDC981C00) from satellite -1
Feb 13 17:42:52.532: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0xAD000000) from satellite -1
Feb 13 17:42:52.552: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0xDD000039) from satellite -1
Feb 13 17:42:52.560: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0xA548EB80) from satellite -1
Feb 13 17:42:52.560: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0x70000000) from satellite -1
Feb 13 17:42:52.580: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0x58000000) from satellite -1
Feb 13 17:42:52.580: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0x58000000) from satellite -1
Feb 13 17:42:52.588: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0x4204C963) from satellite -1
Feb 13 17:42:52.588: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0x61000039) from satellite -1
Feb 13 17:42:52.596: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0xAD000000) from satellite -1
Feb 13 17:42:52.624: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0x33000000) from satellite -1
Feb 13 17:42:52.656: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0xF7D1218F) from satellite -1
Feb 13 17:42:52.672: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0x00000000) from satellite -1
Feb 13 17:42:52.732: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0x6D7E9900) from satellite -1
Feb 13 17:42:52.732: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0x50E894F6) from satellite -1
Feb 13 17:42:52.772: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0xAD000000) from satellite -1
Feb 13 17:42:52.780: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0xAD000000) from satellite -1
Feb 13 17:42:52.860: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0xAD000000) from satellite -1
Feb 13 17:42:52.896: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0x1AE03F49) from satellite -1
Feb 13 17:42:52.944: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0x994F4CC0) from satellite -1
Feb 13 17:42:52.948: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0x00000000) from satellite -1
Feb 13 17:42:52.960: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0x4B4FBA0C) from satellite -1
Feb 13 17:42:52.960: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0xFF000000) from satellite -1
Feb 13 17:42:53.036: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0x00007800) from satellite -1
Feb 13 17:42:53.044: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0x00007800) from satellite -1
Feb 13 17:42:53.048: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0x00007800) from satellite -1
Feb 13 17:42:53.048: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0x00007800) from satellite -1
Feb 13 17:42:53.076: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0x0D8008A6) from satellite -1
Feb 13 17:42:53.160: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0x0D800A05) from satellite -1
Feb 13 17:42:53.208: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0x00007800) from satellite -1
Feb 13 17:42:53.212: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0x00007800) from satellite -1
Feb 13 17:42:53.252: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0x23376EB9) from satellite -1
Feb 13 17:42:53.256: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0x4357FE0C) from satellite -1
Feb 13 17:42:53.256: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0xB49DB174) from satellite -1
Feb 13 17:42:53.260: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0x8036F201) from satellite -1
Feb 13 17:42:53.260: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0x58D6A274) from satellite -1
Feb 13 17:42:53.264: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0x51707065) from satellite -1
Feb 13 17:42:53.264: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0x8EFAE40B) from satellite -1
Feb 13 17:42:53.268: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0x23376EB9) from satellite -1
Feb 13 17:42:53.272: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0x4357FE0C) from satellite -1
Feb 13 17:42:53.272: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0xB49DB174) from satellite -1
Feb 13 17:42:53.276: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0x000A4000) from satellite -1
Feb 13 17:42:53.276: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0xF92BFC52) from satellite -1
Feb 13 17:42:53.280: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0x8036F201) from satellite -1
Feb 13 17:42:53.280: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0x58D6A274) from satellite -1
Feb 13 17:42:53.284: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0x51707065) from satellite -1
Feb 13 17:42:53.284: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0x8EFAE40B) from satellite -1
Feb 13 17:42:53.288: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0x23376EB9) from satellite -1
Feb 13 17:42:53.292: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0x4357FE0C) from satellite -1
Feb 13 17:42:53.292: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0xB49DB174) from satellite -1
Feb 13 17:42:53.296: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0x8036F201) from satellite -1
Feb 13 17:42:53.296: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0x58D6A274) from satellite -1
Feb 13 17:42:53.300: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0x51707065) from satellite -1
Feb 13 17:42:53.300: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0x8EFAE40B) from satellite -1
Feb 13 17:42:53.304: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0xAD000000) from satellite -1
Feb 13 17:42:53.304: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0x23376EB9) from satellite -1
Feb 13 17:42:53.308: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0x4357FE0C) from satellite -1
Feb 13 17:42:53.312: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0xB49DB174) from satellite -1
Feb 13 17:42:53.312: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0x11010600) from satellite -1
Feb 13 17:42:53.316: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0x8036F201) from satellite -1
Feb 13 17:42:53.316: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0x58D6A274) from satellite -1
Feb 13 17:42:53.320: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0x51707065) from satellite -1
Feb 13 17:42:53.320: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0x8EFAE40B) from satellite -1
Feb 13 17:42:53.324: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0x23376EB9) from satellite -1
Feb 13 17:42:53.324: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0x4357FE0C) from satellite -1
Feb 13 17:42:53.328: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0xB49DB174) from satellite -1
Feb 13 17:42:53.332: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0x8036F201) from satellite -1
Feb 13 17:42:53.332: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0x58D6A274) from satellite -1
Feb 13 17:42:53.336: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0x51707065) from satellite -1
Feb 13 17:42:53.336: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0x8EFAE40B) from satellite -1
Feb 13 17:42:53.340: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0xAD000000) from satellite -1
Feb 13 17:42:53.340: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0x23376EB9) from satellite -1
Feb 13 17:42:53.344: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0x4357FE0C) from satellite -1
Feb 13 17:42:53.344: %ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access Write request (0xB49DB174) from satellite -1

=== Start of Crashinfo Collection (17:42:57 UTC Sat Feb 13 2016) ===

For image:
Cisco IOS Software, C3550 Software (C3550-IPSERVICESK9-M), Version 12.2(55)SE9, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright © 1986-2014 by Cisco Systems, Inc.
Compiled Tue 04-Mar-14 00:47 by prod_rel_team

 

Link to post
Share on other sites
l1ght

l1ght 377

Posted
Posted

 

 

(Тільки технічний персонал Cisco , які мають доступ до вихідного коду і докладних карт пам'яті повинен намагатися інтерпретувати файл дампу пам'яті)

день когда всё путаю

конечно carshinfo имел ввиду :/ 

Link to post
Share on other sites
l1ght

l1ght 377

Posted
Posted

откатись до 48 версии

12.2(55)SE8 аптайм месяцами

ospf/PBR/ip unnumbered + 500 vlans/ dchp relay/dhcp snooping/lacp

arp 1k+

 

так что думаю не софт виноват

Link to post
Share on other sites
artyom_bv

artyom_bv 0

Posted
Posted

Періодично перегружається cisco 3550, в чому може бути проблема?

 

sh ver:

Cisco IOS Software, C3550 Software (C3550-IPSERVICESK9-M), Version 12.2(55)SE9, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2014 by Cisco Systems, Inc.
Compiled Tue 04-Mar-14 00:47 by prod_rel_team
Image text-base: 0x00003000, data-base: 0x01608EB8

ROM: Bootstrap program is C3550 boot loader

termv_lan uptime is 37 minutes
System returned to ROM by error - Software Forced Crash Exception (0x0700)!, PC 0x513BC0
System restarted at 17:45:57 UTC Sat Feb 13 2016
System image file is "flash:c3550-ipservicesk9-mz.122-55.SE9/c3550-ipservicesk9-mz.122-55.SE9.bin"

використовується як термінатор vlan ubilling, нагрузка до 300мбіт

могу недорого продать, а то лежит без дела... правда, без блока питания (снял для других нужд)... если надо - в лс...

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Followers 2
Go to topic listing

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • olapchuk
      cisco snmp oid "interface vlan"
      By olapchuk
      Вечір добрий 
      потрібно підсказка чи це взагалі можливо зробити через snmp в ціско
      як влан створити, видалити і переімінувати розібрався через snmp, якщо комусь цікаво тут написано https://www.cisco.com/c/en/us/support/docs/ip/simple-network-management-protocol-snmp/45080-vlans.html, якщо треба приклади скину 
      але проблема в наступному, в ціско всі знають є таке штука яка interface vlan **id**
      тут потрібно саме це створити через snmp і задати пару параментрів, його взагалі можна створити через snmp!?
      interface Vlan3**
        no shutdown
        ip address 192.168.***.***/27
      подякував якщо хто тикне куди дивитись
    • Pavlo_110
      Продам маршрутизатори cisco asr 1004
      By Pavlo_110
      Продам маршрутизатори cisco asr 1004 в робочому стані. 2 шт. Ціна 5000 $ за 2 шт.. Пропозиції пишіть в особисті повідомдення. Продаємо по причині переходу на інший вендор.
    • JoeSnaxEve
      Продам cisco
      By JoeSnaxEve
      Cisco WS-C4948E - 2 шт. (По одному БЖ)
      Cisco WS-C4948-S - 1 шт.
      Cisco ASR1001 - 1 шт.
       
      Пропозиції цін надсилайте в приватні.
      Частина від виручки - на донат.
    • AvaloncheG
      Продам обладнання Cisco 2611/2811/2960/3750/5520/5540
      By AvaloncheG
      Продам:
       
      Cisco 2611XM+Serial NM-4A/S - 2000грн.
      Cisco 2811 (карта 64Mb) - 500грн.
       
      Cisco WS-C2960G-24TC-L - 2000грн.
      Cisco WS-C2960G-48TC-L - 3000грн.
      Cisco WS-C3750-48PS-S POE - 3000грн.
      Cisco WS-C3750V2-48PS-S POE - 3500грн.
      Cisco WS-3750X-24T (1 бж) - 3500грн.
       
      Cisco ASA 5520 SSM-10 - 2500грн.
      Cisco ASA 5540 SSM-40 - 4000грн.
       
      Cisco SB RV120W-E-G5 - 200грн.
       
      Київ.
      +380975649269
    • masha111
      Потрібна допомога завантаження файлів прошивок cisco
      By masha111
      Любий друже, тобі важливо завантажити файли маршрутизаторів, а це Cisco. Моя платима за наші товари в криптовалютах доларах. Людина повинна мати всю необхідну інформацію в місцевості. Це проблема з обслуговуванням на іноземних сайтах. Нам потрібна нам допомога. Будь ласка, дайте мені знати в обличчя, як розмовляти з моїм другом
×
×
  • Create New...