Failover setup on RV016

Is it possible to have this setup on RV016?
WAN1: VOIP traffic (either by port or IP) + failover for WAN 2
WAN2: all other traffic + failover for WAN1
WAN3: failover for WAN1 & WAN2 with connection on demand
Thanks.

Has anyone else figured this out? I'm getting it on every machine I upgrade and I have about 18 more to go and would like to fix it.
These are brand new iMac's shipped with Mountain Lion. I turn them on and the third screen asks if you want to transfer items from a backup or another Mac. I choose another Mac. Then use Migration Assistant on the users old machine (running Snow Leopard 10.6.8) and then let it transfer all of their files.
At just about the end of the transfer the new Mac pops up this error and waits until an action is taken. I've tried every password it could have been on the previous users machine to no avial. The only option appears to be hitting cancel and movi ng on but I'd like to know what is breaking when this happens becase the machines exhibit a strange spinning wheel hang when logging in afterwards?
Here's a screen shot of the new iMac and the problem:
Thanks!

Similar Messages

  • Help needed in ASA 5540 Cluster/Failover setup

    Hello expert,
                        Currently we have two asa in our Datacenter setup as a Active/Standby failover setup and tested ie failover is working,(if one FW goes down), but what if a the uplink switches/links or backend switches go down, how does the active fw knows to failover ?
    Current setup
              |                                        |
        ___|___                              __|___
    ---| SW 1 |------------------------ | Sw2   |     
              |                                        |
        ___|___                              __|___
    ---| FW 1 |------------------------ | FW-2 |     
              |                                        |
        ___|___                              __|___
    ---| SW 1 |------------------------ | Sw2   |     
    In the above figure, FW1 is active and I have powerd off the uplink  SW1, but the FW2 did not take over, and the same for backend switches, So how do I configure my FW's so that any of the uplink or back end switches go down, the Active should give its role to standby to forward the traffice from a different switch ie sw2 in case sw1 goes down.
    Or Is there any mechanisim where I can monitor the interfaces ie uplinks or back end links etc ?
    Your help is appreciated.
    Regards

    It seems that you have LAN link directly connected between the boxes, so the unit will determine that Primary/Active has interfaces that are inactive and failover. You should read:
    http://www.cisco.com/en/US/products/hw/vpndevc/ps2030/products_configuration_example09186a00807dac5f.shtml
    This link gives you the failover triggers and failover actions.

  • Redundancy and Failover setup for 2 MPLS link with 2 different countries

    Hi Sir/Madam,
    We have 2 MPLS link and both links are active (from COUNTRY A to COUNTRY B) and we also have 2 partners who are located in COUNTRY B with same building but with different offices and each partner will be using each MPLS link.  For example, PARTNER A will use the 1st MPLS link and PARTNER B will use the 2nd MPLS link and we want to have a failover setup (please see sample design below).  What is the best solution for COUNTRY A and B to have a full redundancy and failover setup/network?
    Any recommendation and sample configuration will be a big help for me.   Your feedback is highly appreciated.
    Thank you in advance.
    Best regards,
    Marvin

    Disclaimer
    The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
    Liability Disclaimer
    In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
    Posting
    MPLS links, eh.  You mean your MPLS facing ports have actual MPLS labels?  Or do you mean your WAN links are running across a MPLS network, but the handoff isn't MPLS?
    Country A's two routers are your company's devices?  Do you have interior connectivity between them?
    Country B's two routers - do they or can they have interior connectivity?
    What routing protocols are being used (and where)?

  • ORACLE8 OPS 환경에서 FAILOVER SETUP 방법(TRANSPARENT APPLICATION FAILOVER)

    제품 : ORACLE SERVER
    작성날짜 : 2004-08-13
    ORACLE8 OPS 환경에서 FAILOVER SETUP 방법
    ========================================
    SCOPE
    Standard Edition 에서는 Real Application Clusters 기능이 10g(10.1.0) 이상 부터 지원이 됩니다.
    Explanation
    oracle 7 ops (sqlnet v2.3.x 이상)에서는 fail로 인한 failover 지원이 manual
    하게 reconnect를 하도록 하여 지원이 되었다. <bulletin 11033 참고>
    이는 sql*net기능을 사용하여 connection time failover 기능을 사용하는 경우이다.
    하지만, oracle 8 이상 에서는 automatic reconnection이 가능하게 되었다.
    즉, run-time failover가 가능하다.
    이는 일단 connection이 이루어진 후에 발생하는 모든 failover는
    Transparent Application Failover 코드에 의해 처리된다.
    다음은 Oracle 8 TAF(Transparent Application Failover) setup 방법이다.
    tnsnames.ora file에 다음의 parameter를 지정하여 가능하다.
    1. failover_mode : run time 시에 failover가 가능하게 한다.
    2. TYPE (Required) : failover 후의 operation을 지정한다.
    SESSION - failover 발생 시 새로운 session이 다른 instance에
    reconnection되며 이전 session에서의 모든 uncommit된
    작업은 rollback 된다.
    select도 이어서 진행되지 못한다.
    SELECT - failover 발생 시 새로운 session이 다른 instance에
    reconnection되며 이 때 long query나 복잡한 query 등의
    작업 수행 시 작업이 이어서 진행된다.
    단, dml 작업은 rollback된다.
    NONE - This is the default. No automatic failover
    3. METHOD : 어떻게 failover할지를 지정한다.
    BASIC - failover 발생 시에 backup instance(server)로 다시 접속한다.
    PRECONNECT - primary instance와 backup instance 두 개에 모두
    connection 맺어 놓은 후 failover 시에 backup
    instance를 통해 service한다.
    ***< 중요 > 현재 PRECONNECT는 최소한 8.0.5는 되어야 하며
    BASIC은 8.0.6이나 8.1.5에서만 가능하다.
    4. BACKUP : failover 시 접속할 instance의 정보를 기술한다.
    tnsnames.ora의 alias name을 기술한다.
    Example
    다음은 tnsnames.ora file의 example이다.
    < example 1 >
    =========================================================================
    node1.WORLD =
    (DESCRIPTION_LIST =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(Host = node1)(Port = 1521))
    (CONNECT_DATA = (SID = SID1)
    (FAILOVER_MODE = (BACKUP = node2)
    (TYPE = SELECT )
    (METHOD = PRECONNECT))
    node2.WORLD =
    (DESCRIPTION_LIST =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(Host = node2)(Port = 1521))
    (CONNECT_DATA = (SID = SID2)
    (FAILOVER_MODE = (BACKUP = node1)
    (TYPE = SELECT )
    (METHOD = PRECONNECT))
    ========================================================================
    < test 1 >
    1) 각 node의 instance를 start한다.
    2) 각 node의 listener를 구동한다.
    node1% lsnrctl start lsnr_node1
    node2% lsnrctl start lsnr_node2
    3) node1에서 다음의 작업을 한다.
    sqlplus scott/tiger@node1
    SQL> select count(*) from emp;
    COUNT(*)
    14
    4) Node1에서 instance를 shutdown abort한다.
    5) 3번의 session에서 select를 다시 한다.
    SQL> select count(*) from emp;
    ERROR at line 1:
    ORA-25404: lost instance
    다시 select한다.
    SQL> select count(*) from emp;
    COUNT(*)
    14
    Data가 node2 instance를 통해 제대로 select되며 이는 failover가 정상적으로
    작동됨을 알 수 있다.
    < example 2 >
    다음은 TAF(Transparent Application Failover) 기능에 SQL*NET의
    connection time failover 기능을 추가한 경우이다.
    ========================================================================
    node1.WORLD =
    (DESCRIPTION_LIST =
    (DESCRIPTION = (ADDRESS = (PROTOCOL= TCP)(Host= node1)(Port= 1521))
    (CONNECT_DATA =(SID = SID1)(SERVER=SHARED)
    (FAILOVER_MODE = (BACKUP = node2)(TYPE=SESSION)(METHOD=PRECONNECT))))
    (DESCRIPTION =(ADDRESS = (PROTOCOL= TCP)(Host= node2)(Port= 1521))
    (CONNECT_DATA =(SID = SID2)(SERVER=SHARED)
    (FAILOVER_MODE = (BACKUP = node1)(TYPE=SELECT)(METHOD=PRECONNECT))))
    node2.WORLD =
    (DESCRIPTION_LIST =
    (DESCRIPTION =(ADDRESS = (PROTOCOL= TCP)(Host= node2)(Port= 1521))
    (CONNECT_DATA =(SID = SID2)(SERVER=SHARED)
    (FAILOVER_MODE = (BACKUP = node1)(TYPE=SESSION)(METHOD=PRECONNECT))))
    (DESCRIPTION = (ADDRESS = (PROTOCOL= TCP)(Host= node1)(Port= 1521))
    (CONNECT_DATA = (SID = SID1)(SERVER=SHARED)
    (FAILOVER_MODE = (BACKUP = node2)(TYPE=SELECT)(METHOD=PRECONNECT))))
    =======================================================================
    < test 2 >
    1) 각 node의 instance를 start한다.
    2) 각 node의 listener를 구동한다.
    node1% lsnrctl start lsnr_node1
    node2% lsnrctl start lsnr_node2
    3) node1에서 다음의 작업을 한다.
    sqlplus scott/tiger@node1
    SQL> select count(*) from emp;
    COUNT(*)
    14
    4) Node1에서 instance를 shutdown abort한다.
    5) 3번의 session에서 select를 다시 한다.
    ORA-25404 error조차 없이 select된다.
    SQL> select count(*) from emp;
    COUNT(*)
    14
    Data가 node2 instance를 통해 제대로 select되며 이는 failover가 정상적
    으로 작동됨을 알 수 있다.
    (참고 1) dedicated 방식의 경우는 shared 대신에 dedicated를 기술한다.
    물론 initSID.ora의 mts를 기술하지 않고 tnsnames.ora의 server option을 쓰지
    않으면 default로 dedicated 방식을 쓴다.
    (참고 2) example 1을 사용할 경우 session 종료 후 재접속 시 자동 failover가
    되지는 않는다.
    Reference Documents
    oracle8 parallel server concepts & administration manual

    Hi,
    Many Thanks for your inputs. I created 2 non default listeners LISTENER_ORCL1 and LISTENER_ORCL2 on each node respectively.
    I was able to set LISTENER_ORCL as remote listener. But for some reason, the local_listener does not get set. The statement is executed successfully but no changes in the parameters and TAF setup does not work. I initially had the default port number of 1521 for the listener but then changed it to 1522 (to test if it had something to do with default port no) but still no success.
    SQL> show parameters listener
    NAME TYPE VALUE
    local_listener string
    mts_listener_address string
    mts_multiple_listeners boolean FALSE
    remote_listener                  string         LISTENER_ORCL
    SQL> alter system set local_listener='LISTENER_ORCL1' SCOPE=BOTH SID='ORCL1';
    System altered.
    SQL> alter system set local_listener='LISTENER_ORCL2' SCOPE=BOTH SID='ORCL2';
    System altered.
    SQL> show parameters listener
    NAME TYPE VALUE
    local_listener string
    mts_listener_address string
    mts_multiple_listeners boolean FALSE
    remote_listener string LISTENER_ORCL
    Help Plssssssssssss!!!!!!!!

  • New ASA 5515x failover setup

    Just an architecture setup question. We have purchased two 5515x ASA firewalls. I will be setting them up in a stateful failover setup. I know this sounds like a basic question but here goes. I am thinking we should get the first one working on my network and then install the failover ASA once the first one is working properly....? Any thoughts?

    Hi,
    Yes, you can just configure the single ASA first with the configurations and after its configurations are finished install the Secondary unit.
    Naturally while you are configuring the Primary unit you should already setup the interfaces with a "standby" IP address under the interface configuration.
    After you have setup the Primary ASA and made sure that for each of its interfaces/subinterfaces you have a L2 connection through the connecting networking devices to the Secondary ASAs corresponding interfaces/subinterfaces, then you are ready to install the Secondary ASA to the network.
    What you could do on the Secondary ASA is that you remove its default factory configuration and then configure "no shutdown" on each physical interface that you are going to use. Then you could configure the required Failover configurations using the multiple different "failover" configuration commands. (You wont need to configure the actual physical port separately, just need to enable it with "no shutdown", the "failover" commands should handle the rest) After the physical interfaces are configured up and the "failover" commands are set up on the Secondary ASA (and naturally the Primary ASA) then you could basically save the configuration on the Secondary ASA, power down the Secondary ASA, connect it to the network and boot it up. It should then sync the configuration from the Primary ASA after it has booted up and noticed the Active unit (Primary ASA) through the Failover link. So you should not really need to configure the Secondary ASA a lot since it syncs majority of the configurations from the Primary ASA. Naturally the above "failover" configurations are required so the Failover link can be formed for the sync.
    I have had to do this a couple of times lately because of broken down ASAs in Failover pairs. Naturally I would suggest that you take backups of the Primary ASAs configurations before you start setting up the Failover environment so that incase of some error in the setup you still have the configuration. Some people have mentioned the other unit wiping the others configuration but it has not happened to me atleast.
    Hope this helps and that I made any sense :)
    - Jouni

  • Simple SQL Mirror Failover Setup?

    Hello,
    I would think this would be very simple however I can't find a single Adobe document with any information about it!
    In ColdFusion 10 under the Data Sources / SQL Server there is a Connection String box...
    From my hours of Google Searching it SEEMS like all you have to do is add: AlternateServers=(X.X.X.X:1433) to that box and SQL Mirroring failover should work and be automatic...is this correct?
    If anyone has any documentation or experience with this I would greatly appreciate your input...it doesn't seem like this should be all that complicated...or unique...but all the info I find on this is either really old or not really pertaining to this simple setup.
    FYI SQL Servers are Microsoft SQL 2008 R2 (I think SP2).
    Thanks!

    Seriously? Nothing? Bump!

  • Virtual box failover setup possible or no

    Dear All,
    i have three VDI servers and 4th Virtualbox server where 2500 storage is directly connected. it is connected using fibre channel.
    i have created zfs pool on this server after mounting LUN on it. and it is working fine now.
    but there is currently only one server. i want to use one idle server in VDI setup and make another virtual box server to make failover possible. i will make this new server as virtual box server and connect it to same 2500 storage. ( there is no additional storage)
    now how virtualbox failover is possible?
    since on current virtualbox server, there is LUN mounted and configured as zfs pool. if i mount the same LUN in second server. and if one server is down, will it take another virtual box server where same LUN is mounted.
    or i have to create two LUNs in storage and mount one LUN in one server and another on second virtualbox server and do manual replication?
    then there will be manual replication everytime or script to execute for replication.
    Kindlly guide.
    thank you,
    parker

    I think you are combining two possible failover scenarios into one by having the VB host and the storage host as the same physical entity. Having the storage host mount a Fibre Channel LUN doesn't really matter because VB uses iscsi to mount the desktop volume so VDI would not be mounting FC luns. If you have two VB hosts and one fails, the remaining host will have the iscsi volumes mounted and the VMs would be restarted on that hosts, assuming the storage host is independent of the VB hosts.
    In your scenario if a VB host failed, the storage on that host would as well, so the desktop volumes would be inaccessible. If you needed failover with another VB host you would need another volume mounted and configured as a seconded storage host. Then, if using cloning, the desktop would be spread across the two storage hosts. If you lost a VB host you would only lose half your storage (subsequently half your desktops), if there was enough space, the rest could be recloned.

  • Failover setup between ASA5510-AIP10SP-K9 and ASA5510-SEC-BUN-K9

    Not sure if we can setup Active/standby failover between ASA5510-AIP10SP-K9 and ASA5510-SEC-BUN-K9 at all?
    If anyone could advice please, that would be grateful. Thanks a lot

    You would need the module on both appliances to setup failover.
    Regards
    Farrukh

  • Need to add a new segment on a live ASA5520 with a failover setup running

    Hi ,
    how do I add a new segment on my ASA5520 that is currently on a lan based active/standby failover. ?
    Will it trigger the failover if I add another interface and will be just as simple as unshutting a normal interface and adding an IP with the same configuration as the other interfaces for failover .
    all of my existing segment has a redundant switch and for the new segment that I will be creating is just a straight forward with only 1 switch on the segment.
    fw-inside-1# show run int
    interface GigabitEthernet0/0
    description OUTSIDE Interface_1
    no nameif
    no security-level
    no ip address
    interface GigabitEthernet0/1
    description APPS Interface_1
    no nameif
    no security-level
    no ip address
    interface GigabitEthernet0/2
    description DB Interface_1
    no nameif
    no security-level
    no ip address
    interface GigabitEthernet0/3
    description LAN/STATE Failover Interface
    interface Management0/0
    shutdown
    nameif management
    security-level 100
    no ip address
    management-only
    interface GigabitEthernet1/0
    description OUTSIDE Interface_2
    no nameif
    no security-level
    no ip address
    interface GigabitEthernet1/1
    description APPS Interface_2
    no nameif
    no security-level
    no ip address
    interface GigabitEthernet1/2
    description DB Interface_2
    no nameif
    no security-level
    no ip address
    interface GigabitEthernet1/3           <<<<<<<<<<<<<<<<<< I will use this interface for the new segment.
    shutdown
    no nameif
    no security-level
    no ip address
    interface Redundant1
    member-interface GigabitEthernet0/0
    member-interface GigabitEthernet1/0
    nameif outside
    security-level 0
    ip address 10.50.5.10 255.255.255.0 standby 10.50.5.11
    interface Redundant2
    member-interface GigabitEthernet0/1
    member-interface GigabitEthernet1/1
    nameif apps
    security-level 80
    ip address 172.16.1.1 255.255.255.0 standby 172.16.1.2
    interface Redundant3
    member-interface GigabitEthernet0/2
    member-interface GigabitEthernet1/2
    nameif db
    security-level 90
    ip address 172.16.4.1 255.255.255.0 standby 172.16.4.2
    fw-inside-1#
    fw-inside-1# show run fail
    failover
    failover lan unit primary
    failover lan interface Failover GigabitEthernet0/3
    failover polltime unit 5 holdtime 15
    failover link Failover GigabitEthernet0/3
    failover interface ip Failover 10.0.0.1 255.255.255.252
    fw-inside-1#
    Since I will not be having a redundant switch on the new segment I will use the below config
    interface GigabitEthernet1/3    
      no shut
      nameif
      security-level 75
      ip address 172.16.3.1 255.255.255.0 standby 172.16.3.2
    Then I will connect cables..
    Please let me know if you have any suggestions or links.
    Regards

    You should first configure your interface, then cable both units and after that no shut it on the ASA. Additionally you can remove your new interface from failover-monitoring as a precaution if somerhing goes wrong.
    Sent from Cisco Technical Support iPad App

  • Physical Standby DB - failover setup

    Can you please help me with the following questions:
    1. XELUSP1 is Production database, XELUSS1 is physical standby database for XELUSP1. During XELUSP1 crash, we brought up XELUSS1 as primary database manually. Post XELUSP1 is back to primary, Can we use XELUSS1 as standby database as it was?
    2. What are the steps to be done in order to make XELUSS1 as primary during failover scenario from XELUSP1?
    3.What is the impact in client/server environment in 1st case? How it can be fixed?

    Hi,
    1.No, u can't use it again in case of failover but this thing is possible in switchover mode.
    2.diff commands for diff oracle version.tell me on which version u want to perform it.
    3.littile downtime when role of server becomes changing.
    Thanks
    Kuljeet

  • Failover setup help

              I have a sun V880 box and an IIS proxy. The goal is to set up a failover only scenario
              with no load balancing (more licenses and minimal load of applications).
              Is there a way to set up failover with this configuration without load balancing
              ? when you set up a cluster with weblogic, isnt it load balancing with built in
              fail over ?
              I can build a cluster with 2 managed servers and put one of the managed servers
              in a warm standby mode. IIS proxy will assume the secondary is down and will always
              direct the requests to the primary. I can put in a JMS script that will check
              the heart beat of the running server and if it fails it will resume the standby
              server.
              Ideas and comments are appreciated.
              regards.
              arjun.
              

    Router 1:
    interface Serial0/0/0.1 ip routing ! Points at the interface that needs to be Prioritized
    interface FastEthernet0/0
    description interface to LAN
    ip address x.x.x.x 255.255.255.0
    standby 1 ip <Gateway> ! Virtual IP (IP Virtual)
    standby 1 priority 105 ! Higher Priority = Primary Router
    standby 1 preempt ! Enables the router with the highest priority to
    ! immediately become the active router
    standby 1 track 1 ! WAN SUBINTERFACE
    Router bgp <ASN>
    network <Gateway> mask 255.255.255.0 ! Broadcasts Gateway out the WAN through BGP
    Router 2:
    track 1 interface Serial0/0/0.1 ip routing ! Points at the interface that needs to be
    ! Prioritized
    interface FastEthernet0/0
    description interface to LAN
    ip address x.x.x.x 255.255.255.0
    standby 1 ip <Gateway> ! Virtual IP
    standby 1 priority 100 ! Lower Priority = Backup Router
    standby 1 preempt ! Enables the router with the highest priority to
    ! immediately become the active router
    standby 1 track 1 ! WAN SUBINTERFACE
    Router bgp <ASN>
    network <Gateway> mask 255.255.255.0 ! Broadcasts Gateway out the WAN through BGP
    By doing the following to my 2 router is that enough? to have the automatic failover if ISP A went down routing will go thur R2?
    when ISP A is up routing will go back to R1

  • Direct Connect OSPF and BGP AWS failover setup

    Hi,
    We recently installed AWS Direct Connect which was successful but now we are looking at the best way to  automatically fail over if our Direct Connect fails to route via our back VPN.
    The setup
    Cisco 6500 distributes routes via OSPF internally to all production environments with one area set.
    A second Cisco 2901 was installed to support the AWS Direct Connect which uses BGP with a single ASN. This router is connected to the Cisco 6500 and now within the OSPF area.  Static routes exist to the Cisco 2901 currently which unless we physically detach from the network fail over wont work.
    What we want to achieve
    The Cisco 2901 Direct Connect to be the default AWS route until we have a link issue or alike and dynamically fail over to our VPN via the firewall to AWS.  What we are confused is do we advertise these BGP routes within OSPF or should we setup BGP on the Cisco 6500? 
    I appreciate your time.

    Hi,
    We recently installed AWS Direct Connect which was successful but now we are looking at the best way to  automatically fail over if our Direct Connect fails to route via our back VPN.
    The setup
    Cisco 6500 distributes routes via OSPF internally to all production environments with one area set.
    A second Cisco 2901 was installed to support the AWS Direct Connect which uses BGP with a single ASN. This router is connected to the Cisco 6500 and now within the OSPF area.  Static routes exist to the Cisco 2901 currently which unless we physically detach from the network fail over wont work.
    What we want to achieve
    The Cisco 2901 Direct Connect to be the default AWS route until we have a link issue or alike and dynamically fail over to our VPN via the firewall to AWS.  What we are confused is do we advertise these BGP routes within OSPF or should we setup BGP on the Cisco 6500? 
    I appreciate your time.

  • UCCX 8.5.1 Failover setup error

    Hi All,
    just installed a HA UCX 8.5.1 SU3 server and added to existing server to create a cluster.  The install completed OK and all services are activated.  The last message after 1st logon on 2nd node said the server was added to the cluster and gave the following message:
    Infomational Message If you have configured CM Telephony Call Control Groups on your Primary(First) Node, update the Port Groups to create the corresponding ports for this node.
    We already have Call control groups as the UCCX has been live for several years.  I logon to the primary and navigate to the port groups, selecting a port group.  I chose the drop down and select the 2nd node I have just added and click go.  I then click update but get an error that states failed to update user in CM.  This is the same error I get within each of the port groups I have tried this on.
    The user that was setup in UCCX first node was UCCXAdministrator and I made sure to enter these case sensitively.  However when I check CUCM or UCCX user management pages I can't find this user listed.  However I can logon to UCCX with this account.  Any suggestions on how to get the port groups setup on the new 2nd node.
    thanks in advance
    David

    Hi David,
    The account UCCXAdministrator which you said you can log into UCCX with, but couldn't find in CUCM.  The fact that you can log into UCCX with it, tells me that it's a CUCM End User account, so be sure to search End Users and not Application Users for it.  With that said, since you can login with it, this account probably is not that important in your troubleshooting.
    The account which you need to find is a CUCM Application User account, which should have AXL rights.  Since you can log into UCCX at all, I would say that this account is setup correctly as well.  That's because UCCX authenticates via CUCM's AXL API, and unless it wasn't setup and working properly, you wouldn't be able to login to UCCX.
    You mentioned that you went into the CCG, chose the second server from the drop down, clicked Go, then clicked Update.  But, you never mentioned if you actually configured anything first.  Did you?  Did you create the second port group for the second node before you clicked Update?  Or did you simply click Go, then click Update?
    Also, since the error happened while in AppAdmin, then the logs you want to collect and review at the Application Administration logs in RTMT.  They may or may not give you more clues as to what's happening.
    Anthony Holloway
    Please use the star ratings to help drive great content to the top of searches.

  • Weblogic failover setup

    Hi,
    We have a weblogic cluster environment with node1 running Admin server and also one of the cluster node running managed servers.
    Node2 is another node in the cluster running another managed server.
    While at run time if the node1 goes down node2 can pickup the user request without any problem.
    In a situation where both the nodes are down and node1 [which contains admin server also] fails to come up, how do I bring up the node2 which doesn't have the admin server component.
    Is there any way I can move the admin server from node1 to node3 which runs only the admin server component.
    That way node2 can come up by using the node3 admin server.
    Please suggest.

    You ccan use msi mode (managed server indepenedence) to some degree to solve this
    Admin server is required only during startup of managed . MSI can help remove this dependency although you would lose "admin capability " till you actually bring the admin server up
    However this should be fine in an emergency situation
    You can also run the admin on a separate node if required
    8.1 link for MSI is here http://download.oracle.com/docs/cd/E13222_01/wls/docs81/adminguide/failures.html#1126322

  • ASA Failover when Firewalls are at different sites - help

    I am implementing a solution for a customer whereby they have two Cisco ASA 5520X firewalls. They wish for the firewalls to be in an Active-Standby state.
    This not only means that if one firewall dies, the other will take over. It also means that any configuration changes made on the primary are copied to the backup.
    The only catch is, both firewalls are at different sites. There is no layer 2 WAN link running between the sites. They are seperated by both the internet cloud on one side and their internal company MPLS cloud on the other.
    The diagram, that I have taken from my GNS3 simulation and modified slightly, shows the setup. All of the IP addresses (and AS numbers) are made up. Any reflection on real world IPs is unintentional and just a coincidence.
    The diagram is probably too overcrowded with IP information than is needed in this question - but the basic idea is the following:
    1. Under normal conditions traffic will flow to the internet from the remote MPLS site and leave via the firewall (PAT) at site1 - however note the public range of 23.23.23.0/24 is configured at both Site-1 and Site-2 - so at the moment the internet cloud is prefering Site-1 to reach that range.
    2. If the internet link fron INT-PRI at Site-1 fails, remote MPLS traffic destined for the internet will be forwarded out to the internet at Site-2.
    3. If the two MPLS links to Site-1 fail, INT-PRI will stop advertising the public range to the internet PE routers and traffic from the remote MPLS router destined for the internet will go out via Site-2.
    I have the tracking and dynamic routing failover setup between the sites all configured and worked out (I can provide the details of how INT-PRI tracks a sponge address in the MPLS cloud to determine whether or not it advertises the public range to the internet etc etc if you want, but on this question I want to focus on the firewalls).
    Currently the customer has resigned to having to do manual copying between the firewalls every time a change is made (i.e. there is no dynamic failover configured and the Site-2 firewall is just a clone that is kept up to date by their change management team).
    Is there a smart way to set up an Active-Standby configuration between these distant sites? Or at the very least dynamically copy the configuraiton to the backup everytime a change is made? My first though would be some kind of EEM or TCL script but I'm not that experienced with either. Alternatively, if there is smart was to get the two firewalls talking over Layer 2 it might be a better way forward.
    Thanks in advance. Apologies for this question being too wordy.

    You could used Ethernet over MPLS (EoMPLS) or Virtual Private Lan Services (VPLS), though if I remember correctly this is limited to certain platforms and IOS versions.
    Here is a design guide you could have a read through on the options
    http://www.cisco.com/c/en/us/products/collateral/data-center-virtualization/data-center-interconnect/white_paper_c11_493718.html#wp9000079
    EoMPLS configuration guide:
    http://www.cisco.com/c/en/us/td/docs/wireless/asr_901/Configuration/Guide/config_guide/eompls.html
    VPLS configuration guide:
    http://www.cisco.com/c/en/us/td/docs/optical/cpt/r9_5/configuration/guide/cpt95_configuration/cpt95_configuration_chapter_011000.html
    Please remember to rate and select a correct answer

Maybe you are looking for