LAN failover

The only information I get on Cisco, it's that you can NOT use a crossover cable. The only possible connection type is a hub or switch. Can someone, please, tell me why not a crossover?

It is not a restriction as such. As some of you know, his works. The current design assumes that there is a switch/hub in the meantime, this shift can identify when an interface has failed and act accordingly.

For example, if the failover for the PIX_a lan interface has failed, then PIX - b can take more active, but cannot do so if they are connect

using crossover cable as PIX - b will see its interface was not as well. Most likely, the client will use a switch/hub

in the meantime to increase the distance between the 2 PIX when running on LAN fover.

Hope this helps,

Christophe

Tags: Cisco Security

Similar Questions

  • Active/active failover configuration LAN-based PIX / ASA

    Hi all

    I would like to ask, if there is a restriction of length between the two ASA5510 in a LAN failover? Should not be, or I'm wrong?

    Thank you

    Norbert

    Hello

    normal duration of 100 m Ethernet. Or you can use the switches between them. I do not have a direct link.

    Best regards, Celio

  • Help about LAN-based failover active / standby on pix 7.0

    Hello

    I wonder why my status active / standby faiover having to wait. And when I do sh failover state he failed on Hello not hear talk of companion to the standby state (see attachment)

    Failover on

    Status of cable: n/a - active LAN failover

    Unit of primary failover

    Failover LAN Interface: failover GigabitEthernet1 (top)

    Frequency of survey unit 1 seconds, 3 seconds hold time

    Interface frequency of survey 15 seconds

    1 political interface

    Watched 3 Interfaces maximum 250

    failover replication http

    Last failover to: 02:39:25 MYT on April 15, 2006

    This host: primary: enabled

    Activity time: 184985 (s)

    Interface inside (10.103.1.15): Normal (pending)

    Interface to the outside (210.187.51.2): Normal (pending)

    DMZ (210.187.51.81) of the interface: Normal (pending)

    Another host: secondary - ready Standby

    Activity time: 0 (s)

    Interface (0.0.0.0) inside: Normal (pending)

    Interface (0.0.0.0) outdoors: Normal (pending)

    Interface (0.0.0.0) dmz: Normal (pending)

    Failover stateful logical Update Statistics

    Link: failover GigabitEthernet1 (top)

    Stateful Obj xmit rcv rerr xerr

    101718 General 0 419 0

    sys cmd 419 0 419 0

    time 0 0 0 0

    RPC services 0 0 0 0

    Conn 74719 TCP 0 0 0

    Conn 21655 UDP 0 0 0

    ARP tbl 4928 0 0 0

    Xlate_Timeout 0 0 0 0

    VPN IKE upd 0 0 0 0

    VPN IPSEC upd 0 0 0 0

    VPN CTCP upd 0 0 0 0

    VPN SDI upd 0 0 0 0

    VPN DHCP upd 0 0 0 0

    Logical update queue information

    Heart Max Total

    Q: recv 0 2 419

    Xmit Q: 0 2 104936

    Is there something wrong with my setup?

    I use active LAN failover / standby.

    I am attached to my firewall configuration, failover, failover state sh sh and sh story of failover.

    looking at your configs... IP addresses for the rescue unit are missing... It should read something Central this:

    interface Ethernet0

    nameif outside

    IP 209.165.201.1 255.255.255.224 watch 209.165.201.2

  • ASA status interface failover: Normal (pending)

    I've been struggling with this, I have two ASA running 8.6 that show the interfaces being monitored as well.

    I'm under 9.2 on these and tell waiting interfaces. Also can I disable SPI monitored? I ask only the cause at the time where the IPS is a module of the SAA, if I had to restart, the units would be tipping. I don't know if it's the same now with the IPS is a software based inside the ASA running on a separate hard drive.

    ASA5515-01 # show failover
    Failover on
    Unit of primary failover
    Failover LAN interface: FAILOVER of GigabitEthernet0/5 (top)
    Frequency of survey unit 1 seconds, 15 seconds holding time
    Survey frequency interface 5 seconds, 25 seconds hold time
    1 political interface
    Watched 3 114 maximum Interfaces
    MAC address move Notification not defined interval
    Version: Our 9.2 (2) 4, Mate 4 9.2 (2)
    Last failover at: 03:55:44 CDT October 21, 2014
    This host: primary: enabled
    Activity time: 507514 (s)
    slot 0: ASA5515 rev hw/sw (1.0/9.2(2)4 State) (upward (Sys)
                      Interface to the outside (4.35.7.90): Normal (pending)
                      Interface inside (172.20.16.30): Normal (pending)
    Interface Mgmt (172.20.17.10): Normal (pending)
    Slot 1: IPS5515 rev hw/sw (N/A 7.1 (4) E4) State (to the top/to the top)
    IPS, 7.1 (4) E4, upward
    Another host: secondary - ready Standby
    Activity time: 0 (s)
    slot 0: ASA5515 rev hw/sw (1.0/9.2(2)4 State) (upward (Sys)
                      Interface (0.0.0.0) outdoors: Normal (pending)
    Interface (0.0.0.0) inside: Normal (pending)
    Interface (0.0.0.0) Mgmt: Normal (pending)
    Slot 1: IPS5515 rev hw/sw (N/A 7.1 (4) E4) State (to the top/to the top)
    IPS, 7.1 (4) E4, upward

    Failover stateful logical Update Statistics
    Relationship: unconfigured.

    ASA5515-01 # poster run | failover Inc.
    failover
    primary failover lan unit
    LAN failover FAILOVER GigabitEthernet0/5 interface
    failover interface ip FAILOVER 10.10.1.1 255.255.255.252 ensures 10.10.1.2
    ASA5515-01 # ping 10.10.1.2
    Type to abort escape sequence.
    Send 5, echoes ICMP 100 bytes to 10.10.1.2, time-out is 2 seconds:
    !!!!!
    Success rate is 100 percent (5/5), round-trip min/avg/max = ms 02/01/10
    # ASA5515-01

    ------------

    I read also not to use a design where a cable is directly connected to each unit, and instead each interface must connect on a downstream switch port so that the status of the link is still up to a firewall interface if the other firewall interface fails. Otherwise, the two units detects a link down condition and assume that their own interface is down. Never really thought about it in that sense. Anyone use a direct attached cable and have problems?

    Hello

    I rarely troubleshoot failover configurations so I am little rusty with associated with these problems.

    First thing that comes to mind is that configurations under interfaces has "standby" configured IP address? I wondered as the changeover seems to be configured and the link between the units is fine but the unit ready standby shows just 0.0.0.0 for each interface.

    -Jouni

  • "Move" failover to different / interface port

    Sorry if this is in the wrong place, we had if rarely to issues which were not covered otherwise I frequent this area.

    How is it difficult to change the interface used for active failover / standby? This is a pair of work, already configured with standby, but I need to move the cable crossed and tell them to use a different interface.
    Pair of ASA 5510, already put in place and work with failover, which was originally set on Ethernet port 0/3 by senior network administrator. It seems that its use of interfaces or ports he used things straight out of the examples on the web, including the interfaces used.
    The admin network senior retired last spring and left me "supported", gee, thanks.
    I need to make some changes and Ethernet port need for an important new project.
    The management interface 0/0 is unused and shut down. We manage by inside the interface from a specific inside subnet so do not need the interface dedicated management.
    I want to spend the shift IN management TO Ethernet 0/3 0/0

    * This is the current configuration:

    Output of the command: "sh run failover.

    failover
    primary failover lan unit
    failover failover lan interface Ethernet0/3
    failover failover Ethernet0/3 link
    failover interface ip failover 169.254.255.1 255.255.255.252 ensures 169.254.255.2

    * And it's the current 0/3 interface and management configuration:

    interface Ethernet0/3
    STATE/LAN failover Interface Description
    !
    interface Management0/0
    Speed 100
    full duplex
    Shutdown
    nameif management
    security-level 0
    no ip address
    OSPF cost 10

    I know that it can work on the management interface 0/0 because I see a lot of 'how to configure' as if the SAA is brand-new and several examples there indeed be setup on the management.

    I'm looking to find out how to take a pair of ASA is currently configured and has a functional work and all failover configuration simply "tilting move" to a different hole, or change the interfaces used for the 'heartbeat' somehow.

    I guess that's not difficult - but I also assume that there is a specific sequence of events that must occur in order to prevent the pair to enter the failover and switching of the main roles...
    For example - would have turned off or turn off the power switch and if so, how and on what ASA (frankly, I don't know how to access education secondary or standby if it needs to be done, suspended or on the rescue unit, because I never did that 'deep' a before config)
    CLI is very well - I'd be too comfortable in ASDM or cli.

    I really hope this makes sense - I have more than one convenience store and fixer than a designer or network engineer...
    And thank you very much - get this moved will release the interface I need and can really make a big bump in my list of project while the project manager is on vacation this week! I'd love to have done this and before his return.

    Oh, in case it is important as I said, it's running license and version shown here:

    Cisco Adaptive Security Appliance Software Version 4,0000 1
    Version 6.4 Device Manager (7)

    Updated Friday, June 14, 12 and 11:20 by manufacturers
    System image file is "disk0: / asa844-1 - k8.bin.
    The configuration file to the startup was "startup-config '.

    VRDSMFW1 141 days 4 hours
    failover cluster upwards of 141 days 4 hours

    Material: ASA5510, 1024 MB RAM, Pentium 4 Celeron 1600 MHz processor
    Internal ATA Compact Flash, 256 MB
    BIOS Flash M50FW080 @ 0xfff00000, 1024 KB

    Hardware encryption device: edge Cisco ASA - 55 x 0 Accelerator (revision 0 x 0)
    Start firmware: CN1000-MC-BOOT - 2.00
    SSL/IKE firmware: CNLite-MC-Smls-PLUS - 2.03
    Microcode IPSec:-CNlite-MC-IPSECm-HAND - 2.06
    Number of Accelerators: 1

    0: Ext: Ethernet0/0: the address is 0024.972b.e020, irq 9
    1: Ext: Ethernet0/1: the address is 0024.972b.e021, irq 9
    2: Ext: Ethernet0/2: the address is 0024.972b.e022, irq 9
    3: Ext: Ethernet0/3: the address is 0024.972b.e023, irq 9
    4: Ext: Management0/0: the address is 0024.972b.e01f, irq 11
    5: Int: not used: irq 11
    6: Int: not used: irq 5

    The devices allowed for this platform:
    The maximum physical Interfaces: unlimited perpetual
    VLAN maximum: 100 perpetual
    Guests of the Interior: perpetual unlimited
    Failover: Active/active perpetual
    VPN - A: enabled perpetual
    VPN-3DES-AES: activated perpetual
    Security contexts: 2 perpetual
    GTP/GPRS: Disabled perpetual
    AnyConnect Premium peers: 2 perpetual
    AnyConnect Essentials: 250 perpetual
    Counterparts in other VPNS: 250 perpetual
    Total VPN counterparts: 250 perpetual
    Shared license: disabled perpetual
    AnyConnect for Mobile: disabled perpetual
    AnyConnect Cisco VPN phone: disabled perpetual
    Assessment of Advanced endpoint: disabled perpetual
    Proxy UC phone sessions: 2 perpetual
    Proxy total UC sessions: 2 perpetual
    Botnet traffic filter: disabled perpetual
    Intercompany Media Engine: Disabled perpetual

    This platform includes an ASA 5510 Security Plus license.

    Cluster failover with license features of this platform:
    The maximum physical Interfaces: unlimited perpetual
    VLAN maximum: 100 perpetual
    Guests of the Interior: perpetual unlimited
    Failover: Active/active perpetual
    VPN - A: enabled perpetual
    VPN-3DES-AES: activated perpetual
    Security contexts: 4 perpetual
    GTP/GPRS: Disabled perpetual
    AnyConnect Premium peer: 4 perpetual
    AnyConnect Essentials: 250 perpetual
    Counterparts in other VPNS: 250 perpetual
    Total VPN counterparts: 250 perpetual
    Shared license: disabled perpetual
    AnyConnect for Mobile: disabled perpetual
    AnyConnect Cisco VPN phone: disabled perpetual
    Assessment of Advanced endpoint: disabled perpetual
    Proxy UC phone sessions: 4 perpetual
    Proxy total UC sessions: 4 perpetual
    Botnet traffic filter: disabled perpetual
    Intercompany Media Engine: Disabled perpetual

    This platform includes an ASA 5510 Security Plus license.

    Serial number: ABC12345678
    Running permanent activation key: eieioandapartridgeinapeartree
    Registry configuration is 0x1
    Last modified by me to 15:03:07.132 CDT MON Sep 15 2014 configuration

    Disconnect an interface monitored on your rescue unit that will ensure that it does not take as active. Then cut the failover link and modify its failover parameters. (You will need to first remove the nameif for M0/0).

    Then, make the changes on the primary unit similar free game active. Reconnect the failover link, confirm the synchronization of the units and finally reconnect the interface of production on the rescue unit.

  • PIX 515E failover

    I have a pair of PIX 515E (6.3) running in failover mode. They are currently connected to a single chassis base. We are upgrading our network with the heart, dual 6500's. Is there a way to connect each PIX to a separate kernel (1 PIX - Core1, PIX 2 - Core2) to allow a failure of the base?

    Core 1 and Core 2 will have a L2 link between them. If the current active PIX is connected to Core1 and Core 1 dies, this would not lead to support PIX failover. All LAN traffic would go through Core 2, but since he does not have an active path to the active PIX 1, traffic would drop. My reasoning is correct?

    Is there a way to connect the PIX to two cores running V6.3?

    Hello

    If you use the cable-based failover, you can change the basis of LAN failover.

    Read http://www.cisco.com/en/US/docs/security/pix/pix63/configuration/guide/failover.html#wp1024836

    I hope this helps.

    Best regards.

    Massimiliano.

  • PIX 515E failover restart problems

    Thursday, November 23, we went from the PIX cluster to version 7.1 (2) 6.2 (2) with the default memory (64 MB) in each PIX. The Active PIX then suffered what appeared to be leaking memory (attributed to process ARP Thread). This continued for a few days? with the result that we force reloaded the Active PIX every 8 hours to ensure the continuity of the service. Monday 27 after a reload? It has been noticed that the Active PIX leaked is more memory per process threads ARP? the same day, we went from the cluster PIX to 128 MB of memory. Then, we have had failovers active / standby every 2 hours? that seems to be attributed to missed? Hello? in the e-mail of failover? We decided then to configure LAN failover on the PIX cluster. In the process of activation of this secondary feature PIX (which was the current asset) crashed

    You have any explanation as to why these events took place.

    Hi Carlton,

    I can tell you that maybe the method you used to upgrade starts the chain of problems. I used for the migration of these products and I've never met before. In general I WINS configurations, program a service stop and I leave the unit of failover working alone while I do the upgrade of the unit the ex-active. After the upgrade, I had loaded the software configuration I saved before and made the customizations.

    For the PIX without restrictions, is real memory of 128 MB required. For the restricted permission, you can use the default of 64 MB.

    After that, you can place the active unit instead of the recovery. You improve the unit of failover so and connect again in active, already in production and restart the synchronization.

    For all my clients, it worked.

    It will be useful. If Yes, please rate.

    Kind regards

    Rafael Lanna

  • ASA 5540 Stateful failover routing errors

    Hello

    Having two 5540's configuration in a failover scenario. Make the LAN failover and failover state. * See attachment *.

    Failover LAN use 192.168.2.1 as active and 192.168.2.2 as before, with the subnet mask of 30. On both LAN failover use G0/2 and there is a crossover cable connecting them.

    The failover of the State uses 192.168.3.1 as active and 192.168.3.2 as before, with the subnet mask of 30. With "enable HTTP replication" checked in ASDM. On both devices State failover uses G0/3 and there is a crossover cable connecting them.

    The ASDM syslog connects errors every 10 seconds or so to say that:

    SOURCE IP ADDRESS: 192.168.3.1

    DESTINATION IP: 192.168.3.2

    Description:

    "Routing could not locate the next hop for igrp NP identity 192.168.3.1/0 in statefull:192.168.3.2/0".

    The ASA use static routes to meet the network, these roads, there are two, and both are in the 10.x.x.x network. No routing protocol is in use.

    I don't know why these errors are "spamming" my syslog and would like to get rid of them.

    Glad to hear that it works, that's the most important thing. I don't mean to preach, but Cisco does not recommend using ADJUSTABLE wires to fail on. Devices cannot always say that the captain should be and usually causes questions more than a simple link to the bottom.

  • PIX failover

    We have a PIX 515e failover bundle. In the documentation, I read that the PIX failover will restart even 12 hours min. This also occur in a failover design 'ordinary '?

    If the status of the lan failover interface connection is in place:

    * The only FO PIX will start and becomes automatically active if it fails to detect the primary UR PIX.

    * The device recharges itself all 24 hours, becomes automatically active whenever.

    If the lan failover interface link status is down:

    * The only FO PIX will start and are online but not become active.

    Active failover ordering must be run manually to the active unit.

    * The device recharges itself all 24 hours, requiring another manual failover active to make it active each time.

    This is precisely why we suggest to to connect with PIX failover through a switch instead of a crossover cable.

  • Add ASAv cluster in APIC: status remains as init

    Hello

    I tried to integrate a cluster ASAv the APIC, but could not make it work. The situation remains "init". However, when I add a standalone ASAv in APIC, integration seems to work very well. Could someone offer any idea why this is happening?

    I have attached an XML file that describes the error.

    Basically, what I did was the following:

    (1) put up my 2 VMs ASAv as active - standby with the following configuration:

    -Mgmt IP 10.88.88.201 for ASAv-Pri and 10.88.88.202 for ASAv-Sec

    -Failover LAN IP for ASAv-Pri 192.168.0.1 and 192.168.0.2 by ASAv-Sec

    (2) by virtue of one of the tenants, I added the cluster ASAv under L4 - L7 of devices, with the necessary interfaces configured. I also configured the interfaces required under settings, although I don't know if I did it correct. I have attached the configuration as xml for reference (you can remove the extension *.txt)

    Was it something I did wrong, or missed?

    Thanks for reading!

    It seems that your failover configuration is incomplete.  You must specify the failover_lan_interface under the LAN failover Interface folder.  The name used must match the interface_name (failover) you have specified in the Interface Configuration of failover.

    See the screenshot below for an example:

    Kind regards

    Zach

  • Help configuration AIP - SSM

    I have two questions about the AIP - SSM.

    (1) is the ACL in AIP - SSM has any type of relations to the ASA ACL?

    2) our four interfaces are all used. Is it possible to assign the SSM an IP address in the same subnet as the management interface?

    (3) should then the management interface serve as a gateway for the SSM?

    interface GigabitEthernet0/0

    nameif outside

    security-level 0

    IP address 65.x.x.1 255.255.255.0 watch 65.x.x.2

    !

    interface GigabitEthernet0/1

    nameif dmz

    security-level 50

    IP address 172.16.x.1 255.255.255.0 watch 172.16.x.2

    !

    interface GigabitEthernet0/2

    nameif inside

    security-level 100

    IP address 255.255.255.0 192.168.x.1 watch 192.168.x.2

    !

    interface GigabitEthernet0/3

    STATE/LAN failover Interface Description

    !

    interface Management0/0

    Speed 100

    full duplex

    nameif management

    security-level 100

    IP address 10.0.x.1 255.255.255.0 watch 10.0.x.2

    management only

    Here are the answers to your questions-

    (1) is the ACL in AIP - SSM has any type of relations to the ASA ACL?

    No of years) ACL on SSM is completely independent of the ACLs on the ASA.

    2) our four interfaces are all used. Is it possible to assign the SSM an IP address in the same subnet as the management interface?

    VNA) absolutely. You can assign the SSM management port IP address in the same subnet as your managemnet interface. In this way, all management traffic will remain independent of normal DATA traffic.

    (3) should then the management interface serve as a gateway for the SSM?

    VNA) you're right... :-)

    Hope that helps.

    Kind regards

    Maryse.

  • How do the management interface of configuration of an ethernet interface?

    We have an ASA 5540 requiring a LAN port for failover. And the left side of the interface available only the management port. How do the management interface of configuration of an ethernet interface?

    You can disable the mode of management only on this interface to make as regualr routable port and use for other purposes, including the purposes of failover LAN database.

    On the management interface - 5510 but applies generally to the management0/0, itself including 5540

    http://www.Cisco.com/en/us/docs/security/ASA/asa80/configuration/guide/intParam.html#wp1057800

    Basic LAN failover configuration

    http://www.Cisco.com/en/us/docs/security/ASA/asa80/configuration/guide/intParam.html#wp1057800

    Rgds

    -Jorge

  • VPN site-to-site between ASA 5505 and 2911

    Hi all

    I'm trying to setup VPN S2S. A.a.a.a of ip for the router 2911 office, remote office ASA 5505 8.4 (3) with ip b.b.b.b, but no luck.

    2911 config:

    !

    version 15.2

    horodateurs service debug datetime msec

    Log service timestamps datetime msec

    encryption password service

    !

    host name 2911

    !

    boot-start-marker

    Boot system flash c2900-universalk9-mz. Spa. 152 - 2.T.bin

    boot-end-marker

    !

    !

    Min-length 10 Security passwords

    logging buffered 51200 warnings

    !

    No aaa new-model

    !

    !

    min-threshold queue spd IPv6 62

    Max-threshold queue spd IPv6 63

    No ipv6 cef

    the 5 IP auth-proxy max-login-attempts

    max-login-attempts of the IP 5 admission

    !

    !

    !

    DHCP excluded-address IP 192.168.10.1 192.168.10.99

    DHCP excluded-address IP 192.168.22.1 192.168.22.99

    DHCP excluded-address IP 192.168.33.1 192.168.33.99

    DHCP excluded-address IP 192.168.44.1 192.168.44.99

    DHCP excluded-address IP 192.168.55.1 192.168.55.99

    192.168.10.240 IP dhcp excluded-address 192.168.10.254

    DHCP excluded-address IP 192.168.22.240 192.168.22.254

    DHCP excluded-address IP 192.168.33.240 192.168.33.254

    DHCP excluded-address IP 192.168.44.240 192.168.44.254

    DHCP excluded-address IP 192.168.55.240 192.168.55.254

    !

    desktop IP dhcp pool

    import all

    network 192.168.33.0 255.255.255.0

    router by default - 192.168.33.254

    192.168.10.10 DNS server 202.50.246.41 202.50.246.42

    local domain name

    -192.168.10.10 NetBIOS name server

    h-node NetBIOS node type

    !

    wi - fi IP dhcp pool

    import all

    network 192.168.44.0 255.255.255.0

    192.168.10.10 DNS server 202.50.246.41 202.50.246.42

    local domain name

    router by default - 192.168.44.254

    -192.168.10.10 NetBIOS name server

    h-node NetBIOS node type

    !

    DMZ IP dhcp pool

    import all

    network 192.168.55.0 255.255.255.0

    192.168.10.10 DNS server 202.50.246.41 202.50.246.42

    local domain name

    router by default - 192.168.55.254

    -192.168.10.10 NetBIOS name server

    h-node NetBIOS node type

    !

    IP dhcp pool voip

    import all

    network 192.168.22.0 255.255.255.0

    192.168.10.10 DNS server 202.50.246.41 202.50.246.42

    local domain name

    router by default - 192.168.22.254

    -192.168.10.10 NetBIOS name server

    h-node NetBIOS node type

    !

    IP dhcp pool servers

    import all

    network 192.168.10.0 255.255.255.0

    default router 192.168.10.254

    192.168.10.10 DNS server 202.50.246.41 202.50.246.42

    local domain name

    -192.168.10.10 NetBIOS name server

    h-node NetBIOS node type

    !

    !

    IP domain name of domain

    name-server IP 192.168.10.10

    IP cef

    connection-for block 180 tent 3-180

    Timeout 10

    VLAN ifdescr detail

    !

    Authenticated MultiLink bundle-name Panel

    !

    !

    Crypto pki token removal timeout default 0

    !

    Crypto pki trustpoint TP-self-signed-3956567439

    enrollment selfsigned

    name of the object cn = IOS - Self - signed - certificate - 3956567439

    revocation checking no

    rsakeypair TP-self-signed-3956567439

    !

    !

    TP-self-signed-3956567439 crypto pki certificate chain

    certificate self-signed 01 nvram:IOS - Self-Sig #1.cer

    license udi pid sn CISCO2911/K9

    !

    !

    the FULL_NET object-group network

    full range of the network Description

    192.168.10.0 255.255.255.0

    192.168.11.0 255.255.255.0

    192.168.22.0 255.255.255.0

    192.168.33.0 255.255.255.0

    192.168.44.0 255.255.255.0

    !

    object-group network limited

    description without servers and router network

    192.168.22.0 255.255.255.0

    192.168.33.0 255.255.255.0

    192.168.44.0 255.255.255.0

    !

    VTP version 2

    password username admin privilege 0 password 7

    !

    redundancy

    !

    !

    !

    !

    !

    no passive ftp ip

    !

    !

    crypto ISAKMP policy 10

    BA aes 256

    sha512 hash

    preshared authentication

    ISAKMP crypto key admin address b.b.b.b

    invalid-spi-recovery crypto ISAKMP

    !

    !

    Crypto ipsec transform-set esp - aes esp-sha-hmac SET

    !

    !

    !

    10 map ipsec-isakmp crypto map

    the value of b.b.b.b peer

    Set transform-set

    match address 160

    !

    !

    !

    !

    !

    Interface Port - Channel 1

    no ip address

    waiting-150 to

    !

    Interface Port - channel1.1

    encapsulation dot1Q 1 native

    IP 192.168.11.254 255.255.255.0

    IP nat inside

    IP virtual-reassembly in

    !

    Interface Port - channel1.10

    encapsulation dot1Q 10

    IP address 192.168.10.254 255.255.255.0

    IP nat inside

    IP virtual-reassembly in

    !

    Interface Port - channel1.22

    encapsulation dot1Q 22

    IP 192.168.22.254 255.255.255.0

    IP nat inside

    IP virtual-reassembly in

    !

    Interface Port - channel1.33

    encapsulation dot1Q 33

    IP 192.168.33.254 255.255.255.0

    IP nat inside

    IP virtual-reassembly in

    !

    Interface Port - channel1.44

    encapsulation dot1Q 44

    IP 192.168.44.254 255.255.255.0

    IP nat inside

    IP virtual-reassembly in

    !

    Interface Port - channel1.55

    encapsulation dot1Q 55

    IP 192.168.55.254 255.255.255.0

    IP nat inside

    IP virtual-reassembly in

    !

    the Embedded-Service-Engine0/0 interface

    no ip address

    Shutdown

    !

    interface GigabitEthernet0/0

    Description $ETH-LAN$$ETH-SW-LAUNCH$$INTF-INFO-GE $ 0/0

    no ip address

    Shutdown

    automatic duplex

    automatic speed

    !

    interface GigabitEthernet0/1

    no ip address

    automatic duplex

    automatic speed

    channel-group 1

    !

    interface GigabitEthernet0/2

    Description $ES_LAN$

    no ip address

    automatic duplex

    automatic speed

    channel-group 1

    !

    interface GigabitEthernet0/0/0

    IP address a.a.a.a 255.255.255.224

    NAT outside IP

    IP virtual-reassembly in

    automatic duplex

    automatic speed

    crypto map

    !

    IP forward-Protocol ND

    !

    no ip address of the http server

    23 class IP http access

    local IP http authentication

    IP http secure server

    IP http timeout policy slowed down 60 life 86400 request 10000

    !

    overload of IP nat inside source list NAT_INTERNET interface GigabitEthernet0/0/0

    IP nat inside source udp 500 interface GigabitEthernet0/0/0 500 a.a.a.a static

    IP route 0.0.0.0 0.0.0.0 xxx.xxx.xxx.xxx

    !

    NAT_INTERNET extended IP access list

    refuse the object-group ip FULL_NET 192.168.17.0 0.0.0.255

    refuse the object-group ip FULL_NET 192.168.1.0 0.0.0.255

    permit ip FULL_NET object-group everything

    !

    access-list 1 permit 192.168.44.100

    access-list 23 allow 192.168.10.7

    access-list 23 permit 192.168.44.0 0.0.0.255

    access-list 100 permit ip 192.168.10.0 0.0.0.255 192.168.17.0 0.0.0.255

    access-list 160 permit ip 192.168.10.0 0.0.0.255 192.168.17.0 0.0.0.255

    !

    !

    !

    control plan

    !

    !

    !

    Line con 0

    password password 7

    opening of session

    line to 0

    line 2

    no activation-character

    No exec

    preferred no transport

    transport of entry all

    transport output pad rlogin lapb - your MOP v120 udptn ssh telnet

    StopBits 1

    line vty 0 4

    access-class 23 in

    privilege level 15

    local connection

    entry ssh transport

    line vty 5 15

    access-class 23 in

    privilege level 15

    local connection

    entry ssh transport

    !

    Scheduler allocate 20000 1000

    !

    end

    The ASA config:

    : Saved : ASA Version 8.4(3) ! hostname C domain-name domain enable password password encrypted passwd passwd encrypted names ! interface Ethernet0/0 ! interface Ethernet0/1 shutdown ! interface Ethernet0/2 shutdown ! interface Ethernet0/3 shutdown ! interface Ethernet0/4 shutdown ! interface Ethernet0/5 switchport access vlan 100 ! interface Ethernet0/6 switchport trunk allowed vlan 2,6 switchport mode trunk ! interface Ethernet0/7 shutdown ! interface Vlan1 description INTERNET mac-address 1234.5678.0001 nameif WAN security-level 0 ip address b.b.b.b 255.255.255.248 standby c.c.c.c ospf cost 10 ! interface Vlan2 description OLD-PRIVATE mac-address 1234.5678.0102 nameif OLD-Private security-level 100 ip address 192.168.17.2 255.255.255.0 standby 192.168.17.3 ospf cost 10 ! interface Vlan6 description MANAGEMENT mac-address 1234.5678.0106 nameif Management security-level 100 ip address 192.168.1.2 255.255.255.0 standby 192.168.1.3 ospf cost 10 ! interface Vlan100 description LAN Failover Interface ! boot system disk0:/asa843-k8.bin ftp mode passive clock timezone NZST 12 clock summer-time NZDT recurring 1 Sun Oct 2:00 3 Sun Mar 2:00 dns domain-lookup WAN dns server-group DefaultDNS name-server 208.67.222.222 domain-name domain same-security-traffic permit intra-interface object network obj-192.168.17.0 subnet 192.168.17.0 255.255.255.0 object network obj-192.168.10.0 subnet 192.168.10.0 255.255.255.0 object network obj-192.168.2.0 subnet 192.168.2.0 255.255.255.0 object network obj-192.168.9.0 subnet 192.168.9.0 255.255.255.0 object network obj-192.168.33.0 subnet 192.168.33.0 255.255.255.0 object network obj-192.168.44.0 subnet 192.168.44.0 255.255.255.0 object network obj_any object network obj_any-01 object network NETWORK_OBJ_192.168.10.0_24 subnet 192.168.10.0 255.255.255.0 object network NETWORK_OBJ_192.168.17.0_24 subnet 192.168.17.0 255.255.255.0 object network subnet-00 subnet 0.0.0.0 0.0.0.0 object-group protocol TCPUDP protocol-object udp protocol-object tcp object-group service RDP tcp description RDP port-object eq 3389 object-group network DM_INLINE_NETWORK_1 network-object 192.168.17.0 255.255.255.0 network-object 192.168.10.0 255.255.255.0 network-object 192.168.33.0 255.255.255.0 network-object 192.168.44.0 255.255.255.0 object-group network DM_INLINE_NETWORK_2 network-object 192.168.10.0 255.255.255.0 network-object 192.168.33.0 255.255.255.0 network-object 192.168.44.0 255.255.255.0 object-group network subnet-17 network-object 192.168.17.0 255.255.255.0 object-group network subnet-2 network-object 192.168.2.0 255.255.255.0 object-group network subnet-9 network-object 192.168.9.0 255.255.255.0 object-group network subnet-10 network-object 192.168.10.0 255.255.255.0 access-list LAN_nat0_outbound extended permit ip 192.168.17.0 255.255.255.0 192.168.10.0 255.255.255.0 access-list LAN_nat0_outbound extended permit ip 192.168.17.0 255.255.255.0 192.168.9.0 255.255.255.0 access-list LAN_IP standard permit 192.168.17.0 255.255.255.0 access-list WAN_access_in extended permit ip any any log debugging access-list WAN_access_in extended permit tcp any object-group RDP any object-group RDP log debugging access-list WAN_access_in extended permit icmp x.x.x.x 255.255.255.248 192.168.10.0 255.255.255.0 access-list MANAGEMENT_access_in extended permit ip any any log debugging access-list OLD-PRIVATE_access_in extended permit ip any any log debugging access-list OLD-PRIVATE_access_in extended permit icmp any object-group DM_INLINE_NETWORK_1 access-list 101 extended permit tcp host 192.168.10.7 any eq 3389 log debugging access-list WAN_1_cryptomap extended permit ip 192.168.1.0 255.255.255.0 192.168.10.0 255.255.255.0 access-list WAN_1_cryptomap extended permit ip 192.168.17.0 255.255.255.0 192.168.9.0 255.255.255.0 access-list WAN_cryptomap_2 extended permit ip 192.168.1.0 255.255.255.0 192.168.10.0 255.255.255.0 access-list CiscoVPNClient_splitTunnelAcl standard permit 192.168.17.0 255.255.255.0 access-list LAN_access_in extended permit ip any any log debugging access-list WAN_nat0_outbound extended permit ip 192.168.17.0 255.255.255.0 192.168.10.0 255.255.255.0 access-list WAN_nat0_outbound extended permit ip 192.168.17.0 255.255.255.0 192.168.2.0 255.255.255.0 access-list WAN_nat0_outbound extended permit ip 192.168.17.0 255.255.255.0 192.168.9.0 255.255.255.0 access-list WAN_2_cryptomap extended permit ip 192.168.17.0 255.255.255.0 192.168.10.0 255.255.255.0 access-list WAN_2_cryptomap extended permit ip 192.168.17.0 255.255.255.0 192.168.9.0 255.255.255.0 access-list LAN_IP_inbound standard permit 192.168.10.0 255.255.255.0 access-list inside_nat0_outbound extended permit ip 192.168.10.0 255.255.255.0 192.168.17.0 255.255.255.0 access-list vpnusers_splitTunnelAcl extended permit ip 192.168.17.0 255.255.255.0 any access-list nonat-in extended permit ip 192.168.17.0 255.255.255.0 192.168.2.0 255.255.255.0 pager lines 24 logging enable logging buffer-size 52000 logging monitor informational logging trap informational logging asdm informational logging from-address syslog logging recipient-address admin level errors logging host OLD-Private 192.168.17.110 format emblem logging debug-trace logging permit-hostdown mtu WAN 1500 mtu OLD-Private 1500 mtu Management 1500 ip local pool VPN_Admin_IP 192.168.1.150-192.168.1.199 mask 255.255.255.0 ip local pool vpnclient 192.168.2.1-192.168.2.5 mask 255.255.255.0 failover failover lan unit primary failover lan interface failover Vlan100 failover polltime interface 15 holdtime 75 failover key ***** failover interface ip failover 192.168.100.1 255.255.255.0 standby 192.168.100.2 icmp unreachable rate-limit 1 burst-size 1 icmp permit 192.168.10.0 255.255.255.0 WAN icmp permit host x.x.x.x WAN icmp permit 192.168.17.0 255.255.255.0 WAN icmp permit host c.c.c.c WAN icmp permit host a.a.a.a WAN icmp deny any WAN icmp permit 192.168.10.0 255.255.255.0 OLD-Private icmp permit 192.168.17.0 255.255.255.0 OLD-Private icmp permit host a.a.a.a OLD-Private icmp permit host 192.168.10.0 Management icmp permit host 192.168.17.138 Management icmp permit 192.168.1.0 255.255.255.0 Management icmp permit host 192.168.1.26 Management icmp permit host a.a.a.a Management asdm image disk0:/asdm-647.bin no asdm history enable arp timeout 14400 nat (OLD-Private,any) source static subnet-17 subnet-17 destination static subnet-10 subnet-10 no-proxy-arp nat (OLD-Private,any) source static subnet-17 subnet-17 destination static subnet-2 subnet-2 no-proxy-arp nat (OLD-Private,any) source static subnet-17 subnet-17 destination static subnet-9 subnet-9 no-proxy-arp nat (Management,WAN) source static NETWORK_OBJ_192.168.17.0_24 NETWORK_OBJ_192.168.17.0_24 destination static NETWORK_OBJ_192.168.10.0_24 NETWORK_OBJ_192.168.10.0_24 no-proxy-arp route-lookup ! object network subnet-00 nat (OLD-Private,WAN) dynamic interface access-group WAN_access_in in interface WAN access-group OLD-PRIVATE_access_in in interface OLD-Private access-group MANAGEMENT_access_in in interface Management route WAN 0.0.0.0 0.0.0.0 x.x.x.x 1 timeout xlate 3:00:00 timeout pat-xlate 0:00:30 timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02 timeout sunrpc 0:10:00 h323 0:05:00 h225 1:00:00 mgcp 0:05:00 mgcp-pat 0:05:00 timeout sip 0:30:00 sip_media 0:02:00 sip-invite 0:03:00 sip-disconnect 0:02:00 timeout sip-provisional-media 0:02:00 uauth 0:05:00 absolute timeout tcp-proxy-reassembly 0:01:00 timeout floating-conn 0:00:00 dynamic-access-policy-record DfltAccessPolicy user-identity default-domain LOCAL aaa authentication ssh console LOCAL aaa local authentication attempts max-fail 10 http server enable http b.b.b.b 255.255.255.255 WAN http 0.0.0.0 0.0.0.0 WAN no snmp-server location no snmp-server contact snmp-server enable traps snmp authentication linkup linkdown coldstart service resetoutside crypto ipsec ikev1 transform-set OFFICE esp-aes esp-sha-hmac crypto map WAN_map 1 match address WAN_1_cryptomap crypto map WAN_map 1 set pfs crypto map WAN_map 65535 ipsec-isakmp dynamic SYSTEM_DEFAULT_CRYPTO_MAP crypto map Office 2 match address WAN_1_cryptomap crypto map Office 2 set peer a.a.a.a crypto map Office interface WAN crypto map MAP 10 set peer a.a.a.a crypto map MAP 10 set ikev1 transform-set OFFICE crypto ikev2 enable WAN crypto ikev1 enable WAN crypto ikev1 policy 10 authentication pre-share encryption 3des hash sha group 2 lifetime 86400 crypto ikev1 policy 30 authentication pre-share encryption des hash sha group 1 lifetime 86400 telnet timeout 5 ssh a.a.a.a 255.255.255.255 WAN ssh timeout 30 ssh version 2 console timeout 0 dhcpd auto_config OLD-Private ! threat-detection basic-threat threat-detection statistics host threat-detection statistics access-list threat-detection statistics tcp-intercept rate-interval 30 burst-rate 400 average-rate 200 ntp server 129.6.15.28 source WAN prefer webvpn group-policy DfltGrpPolicy attributes vpn-tunnel-protocol ikev1 ssl-client ssl-clientless group-policy admin internal group-policy admin attributes dns-server value 208.67.222.222 156.154.70.1 vpn-tunnel-protocol ikev1 group-policy GroupPolicy_a.a.a.a internal group-policy GroupPolicy_a.a.a.a attributes vpn-tunnel-protocol ikev1 ikev2 group-policy CiscoVPNClient internal group-policy CiscoVPNClient attributes vpn-idle-timeout 30 vpn-session-timeout none vpn-tunnel-protocol ikev1 l2tp-ipsec ssl-clientless split-tunnel-policy tunnelspecified split-tunnel-network-list value CiscoVPNClient_splitTunnelAcl username admin password password encrypted privilege 15 tunnel-group admin type remote-access tunnel-group admin general-attributes address-pool vpnclient authorization-server-group LOCAL default-group-policy admin tunnel-group a.a.a.a type ipsec-l2l tunnel-group a.a.a.a general-attributes default-group-policy GroupPolicy_a.a.a.a tunnel-group a.a.a.a ipsec-attributes ikev1 pre-shared-key ***** ikev2 remote-authentication pre-shared-key ***** ikev2 local-authentication pre-shared-key ***** tunnel-group CiscoVPNClient type remote-access tunnel-group CiscoVPNClient general-attributes address-pool vpnclient default-group-policy CiscoVPNClient tunnel-group CiscoVPNClient ipsec-attributes ikev1 pre-shared-key ***** ! class-map inspection_default match default-inspection-traffic ! ! policy-map type inspect dns preset_dns_map parameters   message-length maximum client auto   message-length maximum 512 policy-map global_policy class inspection_default   inspect dns preset_dns_map   inspect ftp   inspect h323 h225   inspect h323 ras   inspect rsh   inspect rtsp   inspect esmtp   inspect sqlnet   inspect skinny    inspect sunrpc   inspect xdmcp   inspect sip    inspect netbios   inspect tftp   inspect ip-options   inspect icmp ! service-policy global_policy global smtp-server 192.168.17.10 prompt hostname context no call-home reporting anonymous call-home contact-email-addr admin contact-name admin profile CiscoTAC-1   no active : end asdm image disk0:/asdm-647.bin asdm location c.c.c.c 255.255.255.255 WAN asdm location 192.168.17.2 255.255.255.255 WAN asdm location a.a.a.a 255.255.255.255 OLD-Private no asdm history enable

    ASA:

    # show crypto ipsec his

    There is no ipsec security associations

    # show crypto isakmp his

    There are no SAs IKEv1

    There are no SAs IKEv2

    2911:

    #show crypto ipsec his

    Interface: GigabitEthernet0/0/0

    Tag crypto map: map, addr a.a.a.a local

    protégé of the vrf: (none)

    local ident (addr, mask, prot, port): (192.168.10.0/255.255.255.0/0/0)

    Remote ident (addr, mask, prot, port): (192.168.17.0/255.255.255.0/0/0)

    current_peer b.b.b.b port 500

    LICENCE, flags is {origin_is_acl},

    #pkts program: encrypt 0, #pkts: 0, #pkts digest: 0

    #pkts decaps: 0, #pkts decrypt: 0, #pkts check: 0

    compressed #pkts: 0, unzipped #pkts: 0

    #pkts uncompressed: 0, #pkts compr. has failed: 0

    #pkts not unpacked: 0, #pkts decompress failed: 0

    Errors of #send 4, #recv errors 0

    local crypto endpt. : a.a.a.a, remote Start crypto. : b.b.b.b

    Path mtu 1500, mtu 1500 ip, ip mtu IDB GigabitEthernet0/0/0

    current outbound SPI: 0x0 (0)

    PFS (Y/N): N, Diffie-Hellman group: no

    SAS of the esp on arrival:

    -Other - arrival ah sas:

    -More-

    -More - CFP sas on arrival:

    -More-

    -More - outgoing esp sas:

    -More-

    -More - out ah sas:

    -More-

    -More - out CFP sas:

    Thanks for your time,

    Nick

    Please add

    map Office 2 set transform-set OFFICE ikev1 crypto

    If it is not helpful, please enable debug crypto ipsec 255 and paste here.
    

    HTH. Please rate if it was helpful. "Correct answer" will be also pleasant.

  • Configuration of the Interface under... Required main line?

    ASA5520: I'm trying to implement a subinterface for my 2 apart from the IPs (we have 2 pipes entering the data center). I just added a configuration with 2 secondary Interfaces because I didn't have enough ports with the help of g0/3 of our Interface failover (active / standby config). I was just wondering if I need to set up a trunk as to allow the communication? I have attached all ports on a switch and tried ping the secondary Interfaces of a server on the same subnet, but I can't ping interfaces. I have not implemented a main line and I was wondering if this would be the reason? I use a Dell 2724 switch so maybe that's the reason why it won't work? I could * really * use to help with this problem because I am at a loss... I added my current config to post so I hope this helps to clarify my situation and the installation program.

    See the ICM-asa01 (config) # executes

    : Saved

    :

    ASA Version 7.0 (4)

    !

    icm-xxxxx host name

    xxxxxxxx.com domain name

    !

    interface GigabitEthernet0/0

    No nameif

    security-level 0

    no ip address

    !

    interface GigabitEthernet0/0.1

    VLAN 10

    nameif Outside1

    security-level 0

    IP address 66.38.x.x 255.255.x.x Eve 66.38.x.x

    !

    interface GigabitEthernet0/0.2

    VLAN 20

    nameif Outside2

    security-level 0

    IP address 64.187.x.x 255.255.x.x Eve 64.187.x.x

    !

    interface GigabitEthernet0/1

    nameif DMZ

    security-level 100

    IP address 255.255.x.x 10.10.x.x ensures 10.10.x.x

    !

    interface GigabitEthernet0/2

    nameif private

    security-level 40

    IP address 255.255.x.x 192.168.x.x ensures 192.168.x.x

    !

    interface GigabitEthernet0/3

    STATE/LAN failover Interface Description

    !

    interface Management0/0

    STATE failover Interface Description

    No nameif

    security-level 100

    IP address 192.168.x.x 255.255.x.x

    !

    passive FTP mode

    clock timezone IS - 5

    clock to summer time EDT recurring

    pager lines 24

    Enable logging

    monitor debug logging

    asdm of logging of information

    MTU 1500 Outside1

    MTU 1500 Outside2

    MTU 1500 DMZ

    MTU 1500 private

    failover

    primary failover lan unit

    local failover FoInt GigabitEthernet0/3 network interface

    failover replication http

    link failover FoInt GigabitEthernet0/3

    failover interface ip FoInt 192.168.x.x 255.255.x.x Eve 192.168.x.x

    the interface of the monitor Outside1

    the interface of the monitor Outside2

    Thank you

    Chris

    Hi Chris,

    When you have created a sub-intf, it will automatically set the physical interface to use the trunk with dot1Q encap. No order of trunk/encap is required compared to spend. The rest must be supported by the switch, for example allowing to what vlan borrow and be associated with the respective subinterface.

    For example, if your Outside2 of Outside1 & is associated with the Vlan 10 and Vlan 20 respectively, the trunk of the switch (with dot1Q encap) must allow to these VLANS to pass through. Other than that, the configured IP subnet will determine how the traffic on the side switch vlan reach vlan firewall-side

    Rgds,

    AK

  • Interfaces (ASA 5520) cant ping

    Hello

    I recently implemented a configuration of active failover / standby with 2 secondary interfaces configured on my interface of g0/0 (g0/0.1 and g0/0.2) for some reason I can't an of these my ping test server (when the server is on the network and subnet to test the interface)? I'm not sure what continues... I've included a print out of my current configuration of the interface and failover. The test server is connected to a switch of 2724 Dell and the interfaces are in question.

    interface GigabitEthernet0/0

    No nameif

    security-level 0

    no ip address

    !

    interface GigabitEthernet0/0.1

    VLAN 10

    nameif Outside1

    security-level 0

    IP address 66.38.x.x 255.255.x.x Eve 66.38.x.x

    !

    interface GigabitEthernet0/0.2

    VLAN 20

    nameif Outside2

    security-level 0

    IP address 64.187.x.x 255.255.x.x Eve 64.187.x.x

    !

    interface GigabitEthernet0/1

    nameif DMZ

    security-level 100

    IP address 255.255.x.x 10.10.x.x ensures 10.10.x.x

    !

    interface GigabitEthernet0/2

    nameif private

    security-level 40

    IP address 255.255.x.x 192.168.x.x ensures 192.168.x.x

    !

    interface GigabitEthernet0/3

    STATE/LAN failover Interface Description

    !

    interface Management0/0

    STATE failover Interface Description

    No nameif

    security-level 100

    IP address 192.168.x.x 255.255.x.x

    !

    clock timezone IS - 5

    clock to summer time EDT recurring

    pager lines 24

    Enable logging

    monitor debug logging

    asdm of logging of information

    MTU 1500 Outside1

    MTU 1500 Outside2

    MTU 1500 DMZ

    MTU 1500 private

    failover

    primary failover lan unit

    local failover FoInt GigabitEthernet0/3 network interface

    failover replication http

    link failover FoInt GigabitEthernet0/3

    failover interface ip FoInt 192.168.x.x 255.255.x.x Eve 192.168.x.x

    the interface of the monitor Outside1

    the interface of the monitor Outside2

    Thank you

    Chris

    Hi Chris,

    Your config subinterface is fine, except that you will probably need to affect the level of safety that is different between them unless you have already planned for this.

    Normally, it is on the side of the switch that must be configured accordingly. The link of the trunk between the firewall and the switch use the encapsulation DOT1Q (IEEE). I don't know if he Dell support. Make sure that the trunk permits some Vlan you assigned to the firewall secondary interfaces.

    http://www.Cisco.com/en/us/products/ps6120/products_configuration_guide_chapter09186a008054c515.html#wp1051819

    To be able to ping to the interface, make sure that you allow the firewall to allow/permit icmp to hit the interface using the command "icmp", for example "icmp allow any Outside2."

    BTW, what is the gateway for your server? Is it subinterface ASA (function vlan) or IP VLAN on the switch?

    http://www.Cisco.com/en/us/partner/products/ps6120/products_command_reference_chapter09186a00805fba52.html#wp1615091

    Other, you must apply normal static ACL, NAT firewall and so on.

    Rgds,

    AK

Maybe you are looking for

  • 9.2.1 and Apple pay

    Updated my 6s in 9.2.1 this morning.  Later in the day, I tried to use Apple pay to a place where he had previously worked at Marvel (Walgreens), and the loyalty and credit card failed.  After that, I have it turned off and restarted... but also noti

  • S20 Audio stutter / DPC latency... can't fix. Need help!

    Hello world I have recently (last week) bought a Lenovo S20 (Xeon W3520 with 6 GB memory upgrade). I mainly Use this workstation as a DAW for audio, check / change. Instead of preinstalled Windows XP (32-bit) and the Vista Business that comes with th

  • How can I removed the photos/videos to the iPad, but not delete icloud drive?  Need free space on the device, but can't.

    My iPad has a lot of videos/pictures on local memory.  I disappear off the coast because I see that they are in my photo database and iCloud drive.  When I try to delete them it asks it will remove them from all devices.  I just have to remove them f

  • Properties of the keyboard input language

    I have Windows 7 Ultimate and have added Korean via Windows Update.  I also added Korean as an input language, but when I display the properties of the keyboard, it shows the US English provision.  When I switch between them the Korean show language

  • Wi Di?

    Dear members Please forgive my ignorance, but I want to connect my new computer windows laptop 8.1, HP Pavilion 15-n281, on my Sony HD TV so that I can watch videos on the internet etc. on the TV. I used the 'Waves Q' link on my old system of windows