Jump to content

Search the Community

Showing results for tags 'problem'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • ANNOUNCEMENTS
    • ANNOUNCEMENTS
  • CERTIFICATION - - - - - NO REQUESTS IN THESE FORUMS - - - - -
    • CISCO SYSTEMS
    • COMPTIA
    • LINUX
    • MICROSOFT
    • ORACLE
    • PROJECT MANAGEMENT
    • SECURITY CERTIFICATIONS
    • SUN MICROSYSTEMS
    • WIRELESS
    • OTHER CERTIFICATIONS
  • CISCO TECHNICAL SECTION
    • CISCO LABS
    • GNS3
    • NETWORK INFRASTRUCTURE
    • SECURITY
    • WIRELESS
    • SERVICE PROVIDERS
    • COLLABORATION, VOICE AND VIDEO
    • DATA CENTER
    • SMALL BUSINESS
  • MICROSOFT TECHNICAL SECTION
  • OTHER TECHNICAL SECTION
  • TRAINING OFFERS & REQUESTS
  • CERTCOLLECTION MALL
  • GENERAL FORUMS
  • COMMUNITY CENTER

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 4 results

  1. Hi there, i have a problem with Routing on ASA 5505 (the image is: Cisco Adaptive Security Appliance Software Version 8.2(2), with Base licence: Licensed features for this platform: Maximum Physical Interfaces: 8 VLANs: 3, DMZ Restricted). Here is a brief explanation of the topology: ASA Interface Ethernet 0/0 nameif outside switchport access vlan 11 ASA Inteface VLAN 11: description Outside Interface for Internet IP: A.A.A.2/30 <- DC endpoint Upstream IP: A.A.A.1/30 There is a Cisco Switch connected to one of ASA Ethernet ports, forming Public/DMZ VLAN (ID 500) segment. ASA Interface Ethernet 0/2 nameif public switchport access vlan 500 ASA Inteface VLAN 500: description Public/DMZ VLAN IP: B.B.B.1/26 Cisco 3750 Interface VLAN 500: IP: B.B.B.2/26, - default gateway: B.B.B.1, - IP Routing enabled on Switch. From the Cisco Switch I can access the Internet with Source IP: B.B.B.2. Now I have asked from DC additional subnet: C.C.C.0/26 and they have it routed correctly towards the ASA Outside interface IP: A.A.A.2. I have created additional Public2 VLAN on the Switch with IP address of: C.C.C.1/26. It's going to serve as default gateway because of the ASA 3 VLAN limitation with Base licence. On the ASA 5505 i've added the route to this Public2 VLAN: #route public C.C.C.0 255.255.255.192 B.B.B.2 1 Now the problem is that from the Switch with Source IP: C.C.C.1 i can ping ASA 5505 Public VLAN IP: B.B.B.1 so the routing between subnets B.B.B.0/26 and C.C.C.0/26 is working OK on both the ASA 5505 and the Switch. But I can't access the Internet from the Switch with Source IP: C.C.C.1.
  2. Hello, Am having some issues with the configuration. Help please.. 1. In Section 2.5, it says "Ensure that any prefix originated in any of these main site will not get advertise back to same site via redundant gateway." I think there are two variants for the lab, VRF and Non-VRF, how to achieve this requirement in the VRF one and Non-VRF one. Should we use Route-tap and distribute list? 2. Secondly, my HSRP is not working good. SW3 is in Active mode and SW4 Standby and SW4 eventually become Active if SW3 is down BUT am not being able to ping the Virtual IP address from the Standby Switch. The Virtual IP address, which is also the default gateway of PC 101, cannot be ping the PC too. As the PC cannot even ping it's gateway, all the test where PC 101 is involved in fails. SW 3 can ping SW4 vlan 100 and vice-versa. The DHCP is working fine. The L2 Interface are as follows: SW5 >> SW3 >> SW4 >> SW6 If anybody can help, please provide the config too. Best, xxcciexx
  3. Dear All: Please note that i am using IOU web and it is working fine for INE Vol1 K7 K6 K2 K4 and MPLS MSDP MSDPV2 and TS503 but when i import a new TS504 there is not devices or configuration also i tried to import the INE VOl2 same problem no devices found i am just wondering if the IOU web accept only number of devices or configuration so i will try to delete any of the old thanks
  4. Hello everyone, I recently obtained couple of Cisco 9971 IP Phones and two of them are marked as "Prototype". They has different markings on the back and both has firmwares that ends with "dev". I am running CUCM 10.5.1.11900-13. Phones are running ok, can register to CUCM, but when they tries to upgrade firmware log looks like this: <x-cisco-alarm> <Alarm Name="DeviceImageDownloadFailure"> <ParameterList> <String name="DeviceName">REMOVED</String> <String name="IPAddress">192.168.0.151</String> <Enum name="Method">3</Enum> <Enum name="FailureReason">3</Enum> <String name="Active">sip9971.9-3-1-16dev</String> <String name="Inactive">sip9971.9-2-3-27dev</String> <String name="FailedLoadId">sip9971.9-4-1-9</String> <String name="Server">192.168.0.100</String> </ParameterList> </Alarm> </x-cisco-alarm> and: 7816 NOT 04:08:14.100301 dgetimage(32253)-GETIMG [GI32253] authenticating: /tmp/sip9971.9-4-1-9.loads 1 0 0 0 sip9971.9-4-1-9.loads 7817 NOT 04:08:14.115100 dgetimage(32253)-RCLNT_SCK_FD: Clnt sock fd [12] bound to [/tmp/secClnt_GI32253] 7818 WRN 04:08:14.118139 dgetimage(32253)-RCLNT_TO_REQUEST: Requested timeout [600] (> normal max [120]) 7819 NOT 04:08:14.124616 SECD: -verifyImg: filename:/tmp/sip9971.9-4-1-9.loads, opCode:1 ,keyType:0, fileType:0, expectedFileName:sip9971.9-4-1-9.loads fileLen:0 7820 NOT 04:08:14.124753 SECD: -verifyImg: verify with primary key 7821 NOT 04:08:14.124843 SECD: -parseHdr(): start of pad ('T' 0x0d) at TLV 14 7822 NOT 04:08:14.124923 SECD: -parseHdr(): hdr ver 1.1 (knows upto 2.0) 7823 NOT 04:08:14.124999 SECD: -parseHdr(): skipping 2 trail bytes (pad and/or unknown TLVs) 7824 ERR 04:08:14.125073 SECD: -verifySignedFile(): RSA decr of sig failed 7825 ERR 04:08:14.125144 SECD: -verifyImg: *** verify with primary key failed *** 7826 NOT 04:08:14.125215 SECD: -verifyImg: verify with secondary key 7827 NOT 04:08:14.125288 SECD: -parseHdr(): start of pad ('T' 0x0d) at TLV 14 7828 NOT 04:08:14.125359 SECD: -parseHdr(): hdr ver 1.1 (knows upto 2.0) 7829 NOT 04:08:14.125433 SECD: -parseHdr(): skipping 2 trail bytes (pad and/or unknown TLVs) 7830 ERR 04:08:14.125504 SECD: -verifySignedFile(): RSA decr of sig failed 7831 ERR 04:08:14.125710 SECD: -verifyImg:** verify with secondary key failed ** 7832 ERR 04:08:14.125829 SECD: -SFA_SGN_VFY_F_4: sgn verify file failed [/tmp/sip9971.9-4-1-9.loads], errclass [8], errcode [15] [signature failed] 7833 ERR 04:08:14.125917 SECD: -SFA_VFY_F_2: Verify[] FAILED, [/tmp/sip9971.9-4-1-9.loads] 7834 NOT 04:08:14.126257 dgetimage(32253)-RCLNT_CLOSE_SOCK: Closing clnt sock fd [12] 7835 NOT 04:08:14.126551 dgetimage(32253)-RCLNT_RM_SCK_PATH: Removing clnt sock path [/tmp/secClnt_GI32253] and closing [12] 7836 NOT 04:08:14.126804 dgetimage(32253)-GETIMG-DEBUG auth astat return [13] 7837 NOT 04:08:14.127294 img-pfs-&&&done dd_get_image_ replies 269 7838 ERR 04:08:14.127509 img-pfs-LOAD6 [offset:-269] downdload image file failure. 7839 NOT 04:08:14.127979 dgetimage(32253)-DDGETIMG.RESULT [authentication error] 7840 ERR 04:08:14.129134 downd-SOCKET accept errno=4 "Interrupted system call" 7841 NOT 04:08:15.127874 img-pfs-closing child 0 7842 NOT 04:08:15.128102 img-pfs-Child 0 already closed 7843 NOT 04:08:15.128291 img-pfs-closing child 1 7844 NOT 04:08:15.128472 img-pfs-Child 1 already closed 7845 CRT 04:08:15.128825 img-pfs-EXITING... 7846 NOT 04:08:15.128923 ========================================== 7847 NOT 04:08:15.128993 image-[err:269] IMAGE <<<FAIL>>>. 7848 NOT 04:08:15.129048 authentication error 7849 NOT 04:08:15.129132 ========================================== 7850 NOT 04:08:15.240891 imgpfs: -ebr-active = 9-3-1-16dev 7851 NOT 04:08:15.246857 imgpfs: -Active = 2 7852 NOT 04:08:15.343915 imgpfs: -ebr_a [81] sip9971.9-2-3-27dev.loads 7853 NOT 04:08:15.440418 imgpfs: -ebr_b [80] sip9971.9-3-1-16dev.loads 7854 NOT 04:08:15.472158 img-pfs-Post-Image Archive of Logs 7855 NOT 04:08:18.141989 dimg(32181)-IMAGE.actualserver [192.168.0.100] So, my question is: What is going on in there and how to update to newer firmware. I dont understand why all other phones can update and these two prototypes cant. I hope someone will be able to help THANKS P.S.: Nice about this phones is the fact, that telnet is enabled and you can connect to them via port 22 and see this: MontaVista® Linux® Professional Edition Blackfoot (0702518) Linux/armv6l 2.6.18_pro500 (none) login: Welcome to MontaVista® Linux® Professional Edition Blackfoot (0702518). Cisco IP Phone 9971 9-3-1-16 you can then root to the phone and work there.
×
×
  • Create New...