BGP in Dual Homing setup not failing over correctly
Hi all,
we have dual homed BGP connections to our sister company network but the failover testing is failing.
If i shutdown the WAN interface on the primary router, after about 5 minutes, everything converges and fails over fine.
But, if i shut the LAN interface down on the primary router, we never regain connectivity to the sister network.
Our two ASR's have an iBGP relationship and I can see that after a certain amount of time, the BGP routes with a next hop of the primary router get flushed from BGP and the prefferred exit path is through the secondary router. This bit works OK, but i believe that the return traffic is still attempting to return over the primary link...
To add to this, we have two inline firewalls on each link which are only performing IPS, no packet filtering.
Any pointers would be great.
thanks
Mario
Hi John,
right... please look at the output below which is the partial BGP table during a link failure...
10.128.0.0/9 is the problematic summary that still keeps getting advertised out when we do not want it to during a failure....
now there are prefixes in the BGP table which fall within that large summary address space. But I am sure that they are all routes that are being advertised to us from the eBGP peer...
*> 10.128.0.0/9 0.0.0.0 32768 i
s> 10.128.56.16/32 172.17.17.241 150 0 2856 64619 i
s> 10.128.56.140/32 172.17.17.241 150 0 2856 64619 i
s> 10.160.0.0/21 172.17.17.241 150 0 2856 64611 i
s> 10.160.14.0/24 172.17.17.241 150 0 2856 64611 i
s> 10.160.16.0/24 172.17.17.241 150 0 2856 64611 i
s> 10.200.16.8/30 172.17.17.241 150 0 2856 65008 ?
s> 10.200.16.12/30 172.17.17.241 150 0 2856 65006 ?
s> 10.255.245.0/24 172.17.17.241 150 0 2856 64548 ?
s> 10.255.253.4/32 172.17.17.241 150 0 2856 64548 ?
s> 10.255.253.10/32 172.17.17.241 150 0 2856 64548 ?
s> 10.255.255.8/30 172.17.17.241 150 0 2856 6670 ?
s> 10.255.255.10/32 172.17.17.241 150 0 2856 ?
s> 10.255.255.12/30 172.17.17.241 150 0 2856 6670 ?
s> 10.255.255.14/32 172.17.17.241 150 0 2856 ?
i would not expect summary addresses to still be advertised if the specific prefixes are coming from eBGP... am i wrong?
thanks for everything so far...
Mario De Rosa
Similar Messages
-
Weblogic not failing over correctly
Hi,
I've got two weblogic servers in a cluster recieving requests from a
weblogic proxy server. To demonstrate and test failover I've written
three servlets: Login, Logout, and Test2. They perform session
tracking ie. Login creates a session, Test2 tests it and Logout kills
the session. The failover is very inconsistent at best. Shutting down
one of the servers in the cluster causes the other one to failover OK
but turning it back on and shutting down the second one doesn't work.
Also the Test2 servlet doesn't see the session when it is loaded for the
first time. Reloading causes it to work properly. Why?
Could you look through these weblogic.properties files and see if they
are configured correctly? One is from the cluster servers and the other
is from the proxy server.
These are in the weblogic root directory. I don't have any properties
files in the cluster - wide or server specific directories. I am not
using a shared file system.
I am using weblogic 5.1 sp1 on NT and jdk1.2.2.
Thank you
Timur M.
[weblogic.properties]
[weblogic.properties]
The mistakes I found so far are the following.
You have to register HttpClusterServlet to proxy all the servlet/jsp requests to weblogic
cluster.
** PROXY PROPERTIES **
weblogic.httpd.register.cluster=weblogic.servlet.internal.HttpClusterServlet
weblogic.httpd.initArgs.cluster=defaultServers=jer:7001|tmaltaric:7001
weblogic.httpd.defaultServlet=cluster
** WEBLOGIC SERVER PROPERTIES **
weblogic.httpd.register.Login=Login
weblogic.httpd.register.Logout=Logout
blah blah blah
Hope this helps.
- Prasad
Timur Maltaric wrote:
> Hi,
>
> I've got two weblogic servers in a cluster recieving requests from a
> weblogic proxy server. To demonstrate and test failover I've written
> three servlets: Login, Logout, and Test2. They perform session
> tracking ie. Login creates a session, Test2 tests it and Logout kills
> the session. The failover is very inconsistent at best. Shutting down
> one of the servers in the cluster causes the other one to failover OK
> but turning it back on and shutting down the second one doesn't work.
> Also the Test2 servlet doesn't see the session when it is loaded for the
> first time. Reloading causes it to work properly. Why?
>
> Could you look through these weblogic.properties files and see if they
> are configured correctly? One is from the cluster servers and the other
> is from the proxy server.
>
> These are in the weblogic root directory. I don't have any properties
> files in the cluster - wide or server specific directories. I am not
> using a shared file system.
> I am using weblogic 5.1 sp1 on NT and jdk1.2.2.
>
> Thank you
> Timur M.
>
> ------------------------------------------------------------------------
> Name: weblogic.properties
> weblogic.properties Type: application/x-unknown-content-type-properties_auto_file
> Encoding: base64
>
> Name: weblogic.properties
> weblogic.properties Type: application/x-unknown-content-type-properties_auto_file
> Encoding: base64
Cheers
- Prasad
-
NIC not failing Over in Cluster
Hi there...I have configured 2 Node cluster with SoFS role...for VM Cluster and HA using Windows Server 2012 Data Center. Current set up is Host Server has 3 NICS (2 with Default Gateway setup (192.x.x.x), 3 NIC is for heartbeat 10.X.X.X). Configured CSV
(can also see the shortcut in the C:\). Planning to setup few VMs pointing to the disk in the 2 separate storage servers (1 NIC in 192.x.x.x) and also have 2 NIC in 10.x.x.x network. I am able to install VM and point the disk to the share in the cluster volume
1.
I have created 2 VM Switch for 2 separate Host server (using Hyper-V manager). When I test the functionality by taking Node 2, I can see the Disk Owner node is changing to Node 1, but the VM NIC 2 is not failing over automatically to VM NIC 1 (but I can
see the VM NIC 1 is showing up un-selected in the VM Settings). when I go to the VM Settings > Network Adapter, I get error -
An Error occurred for resource VM "VM Name". select the "information details" action to view events for this resource. The network adapter is configures to a switch which no longer exists or a resource
pool that has been deleted or renamed (with configuration error in "Virtual Switch" drop down menu).
Can you please let me know any resolution to fix this issue...Hoping to hear from you.
VTHi,
From your description “My another thing I would like to test is...I also would like to bring a disk down (right now, I have 2 disk - CSV and one Quorum disk) for that 2 node
cluster. I was testing by bringing a csv disk down, the VM didnt failover” Are you trying to test the failover cluster now? If so, please refer the following related KB:
Test the Failover of a Clustered Service or Application
http://technet.microsoft.com/en-us/library/cc754577.aspx
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place. -
VIP is not failed over to surviving nodes in oracle 11.2.0.2 grid infra
Hi ,
It is a 8 node 11.2.0.2 grid infra.
While pulling both cables from public nic the VIP is not failed over to surviving nodes in 2 nodes but remainng nodes VIP is failed over to surviving node in the same cluster. Please help me on this.
If we will remove the power from these servers VIP is failed over to surviving nodes
Public nic's are in bonding.
grdoradr105:/apps/grid/grdhome/sh:+ASM5> ./crsstat.sh |grep -i vip |grep -i 101
ora.grdoradr101.vip ONLINE OFFLINE
grdoradr101:/apps/grid/grdhome:+ASM1> cat /proc/net/bonding/bond0
Ethernet Channel Bonding Driver: v3.4.0-1 (October 7, 2008)
Bonding Mode: fault-tolerance (active-backup)
Primary Slave: None
Currently Active Slave: eth0
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0
Slave Interface: eth0
MII Status: up
Speed: 100 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 84:2b:2b:51:3f:1e
Slave Interface: eth1
MII Status: up
Speed: 100 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 84:2b:2b:51:3f:20
Thanks
BalaPlease check below MOS note for this issue.
1276737.1
HTH
Edited by: krishan on Jul 28, 2011 2:49 AM -
Thin Client connection not failing over
I'm using the following thin client connection and the sessions do not failover. Test with SQLPLUS and the sessions do fail over. One difference I see between the two different connections is the thin connection has NONE for the failover_method and failover_type but the SQLPLUS connection show BASIC for failover_method and SELECT for failover_type.
Is there any issues with the thin client the version is 10.2.0.3
jdbc:oracle:thin:@(description=(address_list=(load_balance=YES)(address=(protocol=tcp)(host=crpu306-vip.wm.com)(port=1521))(address=(protocol=tcp)(host=crpu307-vip.wm.com)(port=1521)))(connect_data=(service_name=ocsqat02)(failover_mode=(type=select)(method=basic)(DELAY=5)(RETRIES=180))))You have to use (FAILOVER=on) as well on jdbc url.
http://download.oracle.com/docs/cd/B19306_01/network.102/b14212/advcfg.htm#sthref1292
Example: TAF with Connect-Time Failover and Client Load Balancing
Implement TAF with connect-time failover and client load balancing for multiple addresses. In the following example, Oracle Net connects randomly to one of the protocol addresses on sales1-server or sales2-server. If the instance fails after the connection, the TAF application fails over to the other node's listener, reserving any SELECT statements in progress.sales.us.acme.com=
(DESCRIPTION=
*(LOAD_BALANCE=on)*
*(FAILOVER=on)*
(ADDRESS=
(PROTOCOL=tcp)
(HOST=sales1-server)
(PORT=1521))
(ADDRESS=
(PROTOCOL=tcp)
(HOST=sales2-server)
(PORT=1521))
(CONNECT_DATA=
(SERVICE_NAME=sales.us.acme.com)
*(FAILOVER_MODE=*
*(TYPE=select)*
*(METHOD=basic))))*
Example: TAF Retrying a Connection
TAF also provides the ability to automatically retry connecting if the first connection attempt fails with the RETRIES and DELAY parameters. In the following example, Oracle Net tries to reconnect to the listener on sales1-server. If the failover connection fails, Oracle Net waits 15 seconds before trying to reconnect again. Oracle Net attempts to reconnect up to 20 times.sales.us.acme.com=
(DESCRIPTION=
(ADDRESS=
(PROTOCOL=tcp)
(HOST=sales1-server)
(PORT=1521))
(CONNECT_DATA=
(SERVICE_NAME=sales.us.acme.com)
*(FAILOVER_MODE=*
*(TYPE=select)*
*(METHOD=basic)*
*(RETRIES=20)*
*(DELAY=15))))* -
Stateful bean not failing over
I have a cluster of two servers and a Admin server. Both servers are running NT
4 sp6 and WLS6 sp1.
When I stop one of the servers, the client does n't automatically failover to
the other server, instead it fails unable to contact server that has failed.
My bean is configured to have its home clusterable and is a stateful bean. My
client holds onto the remote interface, and makes calls through this. If Server
B fails then it should automatically fail over to server A.
I have tested my multicast address and all seems to be working fine between servers,
my stateless bean work well, load balancing between servers nicely.
Does anybody have any ideas, regarding what could be causing the stateful bean
remote interface not to be providing failover info.
Also is it true that you can have only one JMS destination queue/topic per cluster..The
JMS cluster targeting doesn't work at the moment, so you need to deploy to individual
servers?
Thanks
Did you enable stateful session bean replication in the
weblogic-ejb-jar.xml?
-- Rob
Wayne Highland wrote:
>
> I have a cluster of two servers and a Admin server. Both servers are running NT
> 4 sp6 and WLS6 sp1.
> When I stop one of the servers, the client does n't automatically failover to
> the other server, instead it fails unable to contact server that has failed.
>
> My bean is configured to have its home clusterable and is a stateful bean. My
> client holds onto the remote interface, and makes calls through this. If Server
> B fails then it should automatically fail over to server A.
>
> I have tested my multicast address and all seems to be working fine between servers,
> my stateless bean work well, load balancing between servers nicely.
>
> Does anybody have any ideas, regarding what could be causing the stateful bean
> remote interface not to be providing failover info.
>
> Also is it true that you can have only one JMS destination queue/topic per cluster..The
> JMS cluster targeting doesn't work at the moment, so you need to deploy to individual
> servers?
>
> Thanks
Coming Soon: Building J2EE Applications & BEA WebLogic Server
by Michael Girdley, Rob Woollen, and Sandra Emerson
http://learnweblogic.com
-
GSLB Zone-Based DNS Payment Gw - Config Active-Active: Not Failing Over
Hello All:
Currently having a bit of a problem, have exhausted all resources and brain power dwindling.
Brief:
Two geographically diverse sites. Different AS's, different front ends. Migrated from one site with two CSS 11506's to two sites with one 11506 each.
Flow of connection is as follows:
Client --> FW Public Destination NAT --> CSS Private content VIP/destination NAT --> server/service --> CSS Source VIP/NAT --> FW Public Source NAT --> client.
Using Load Balancers as DNS servers, authoritative for zones due to the requirement for second level Domain DNS load balancing (i.e xxxx.com, AND FQDNs http://www.xxxx.com). Thus, CSS is configured to respond as authoritative for xxxx.com, http://www.xxxx.com, postxx.xxxx.com, tmx.xxxx.com, etc..., but of course cannot do MX records, so is also configured with dns-forwarders which consequently were the original DNS servers for the domains. Those DNS servers have had their zone files changed to reflect that the new DNS servers are in fact the CSS'. Domain records (i.e. NS records in the zone file), and the records at the registrar (i.e. tucows, which I believe resells .com, .net and .org for netsol) have been changed to reflect the same. That part of the equation has already been tested and is true to DNS Workings. The reason for the forwarders is of course for things such as non load balanced Domain Names, as well as MX records, etc...
Due to design, which unfortunately cannot be changed, dns-record configuration uses kal-ap, example:
dns-record a http://www.xxxx.com 0 111.222.333.444 multiple kal-ap 10.xx.1.xx 254 sticky-enabled weightedrr 10
So, to explain so we're absolutely clear:
- 111.222.333.444 is the public address returned to the client.
- multiple is configured so we return both site addresses for redundancy (unless I'm misunderstanding that configuration option)
- kal-ap and the 10.xx.1.xx address because due to the configuration we have no other way of knowing the content rule/service is down and to stop advertising the address for said server/rule
- sticky-enabled because we don't want to lose a payment and have it go through twice or something crazy like that
- weighterr 10 (and on the other side weightedrr 1) because we want to keep most of the traffic on the site that is closer to where the bulk of the clients are
So, now, the problem becomes, that the clients (i.e. something like an interac machine, RFID tags...) need to be able to fail over almost instantly to either of the sites should one lose connectivity and/or servers/services. However, this does not happen. The CSS changes it's advertisement, and this has been confirmed by running "nslookups/digs" directly against the CSSs... however, the client does not recognize this and ends up returning a "DNS Error/Page not found".
Thinking this may have something to do with the "sticky-enabled" and/or the fact that DNS doesn't necessarily react very well to a TTL of "0".
Any thoughts... comments... suggestions... experiences???
Much appreciated in advance for any responses!!!
Oh... should probably add:
nslookups to some DNS servers consistently - ALWAYS the same ones - take 3 lookups before getting a reply. Other DNS servers are instant....
Cheers,
Ben Shellrude
Sr. Network Analyst
MTS AllStream IncHi Ben,
if I got your posting right the CSSes are doing their job and do advertise the correct IP for a DNS-query right?
If some of your clients are having a problem this might be related to DNS-caching. Some clients are caching the DNS-response and do not do a refresh until they fail or this timeout is gone.
Even worse if the request fails you sometimes have to reset the clients DNS-demon so that they are requesting IP-addresses from scratch. I had this issue with some Unixboxes. If I remeber it corretly you can configure the DNS behaviour for unix boxes and can forbidd them to cache DNS responsed.
Kind Regards,
joerg -
Why DML not failed over in TAF??
Hi,
I have an OLTP application running on 2 node 10gR2 RAC(10.2.0.3) on AIX 5.3L ML 8. I have configured TAF here for SESSION failover.I would like to know two things from you all:
1) Though each instance is able to read other instnace's undo tablespace data and redolog, then allso why TAF is not able failover the DML transactions?
2) As of now is there any way to failover the DML other than cathing the error thrown back to application and re-executing the query?Is it possible in the 11gR1?
I am gratefull to you all if you are sparing your valuable time to answer this.
Thanks and Regards,
Vijay ShankerRe: Failover DML on RAC
The reason is transaction processing and its implications.
Imagine that you updated a row, then waited idly, then some other session wanted that same row and waited for you to either rollback or commit.
You failed.
Automatically, Oracle will rollback your transaction and release all your locks.
What should the other session do: wait to see that maybe you have TAF or FCF and will reconnect and rerun your uncommitted DML, or should it proceed with its own work?
Failed session rollback currently happens regardless of whether you or anybody else have TAF, FCF, or even whether you have RAC.
But in order for you to be able to replay your DML safely after reconnect, that transaction rollback had to be prevented, and your new failed over session should magically re-attach to the failed session's transaction.
Maybe some day Oracle will implement something like that, but it's not easy, and Oracle leaves it up to the application to decide what to do (TAF-specific error codes).
On the other hand, replaying selects is fairly easy: re-executing the query (with scn as of the originally failed cursor to ensure read-consistency) and re-fetching up to the point of last fetch. -
Problems with Oracle FailSafe - Primary node not failing over the DB to the
I am using 11.1.0.7 on Windows 64 bit OS, two nodes clustered at OS level. The Cluster is working fine at Windows level and the shared drive fails over. However, the database does not failover when the primary node is shutdown or restarted.
The Oracle software is on local drive on each box. The Oracle DB files and Logs are on shared drive.Is the database listed in your cluster group that you are failing over?
-
Http cluster servlet not failing over when no answer received from server
I am using weblogic 510 sp9. I have a weblogic server proxying all requests to
a weblogic cluster using the httpclusterservlet.
When I kill the weblogic process servicing my request, I see the next request
get failed over to the secondary server and all my session information has been
replicated. In short I see the behavior I expect.
r.troon
However, when I either disconnect the primary server from the network or just
switch this server off, I just get a message back
to the browser - "unable to connect to servers".
I don't really understand why the behaviour should be different . I would expect
both to failover in the same manner. Does the cluster servlet only handle tcp
reset failures?
Has anybody else experience this or have any ideas.
Thanks
I think I might have found the answer......
The AD objects for the clusters had been moved from the Computers OU into a newly created OU. I'm suspecting that the cluster node computer objects didn't have perms to the cluster object within that OU and that was causing the issue. I know I've seen cluster
object issues before when moving to a new OU.
All has started working again for the moment so I now just need to investigate what permissions I need on the new OU so that I can move the cluster object in. -
Hi All
Im preparing a lab and I have 2 ASA 5520's. I have configured them for failover so the Primarys config will replicate over to the Secondary. They are connected via a 3560 switch. the switch ports are configured as access ports on vlan 1. Spanning-tree portfast is enabled
Firewall (Primary)
Cisco Adaptive Security Appliance Software Version 9.1(1)
Device Manager Version 7.1(2)
Compiled on Wed 28-Nov-12 10:38 by builders
System image file is "disk0:/asa911-k8.bin"
Config file at boot was "startup-config"
DEO-FW-01 up 5 hours 1 min
failover cluster up 5 hours 1 min
Hardware: ASA5520, 2048 MB RAM, CPU Pentium 4 Celeron 2000 MHz,
Internal ATA Compact Flash, 256MB
BIOS Flash M50FW080 @ 0xfff00000, 1024KB
Encryption hardware device : Cisco ASA-55xx on-board accelerator (revision 0x0)
Boot microcode : CN1000-MC-BOOT-2.00
SSL/IKE microcode : CNLite-MC-SSLm-PLUS-2.03
IPSec microcode : CNlite-MC-IPSECm-MAIN-2.08
Number of accelerators: 1
0: Ext: GigabitEthernet0/0 : address is 001e.f762.bc44, irq 9
1: Ext: GigabitEthernet0/1 : address is 001e.f762.bc45, irq 9
2: Ext: GigabitEthernet0/2 : address is 001e.f762.bc46, irq 9
3: Ext: GigabitEthernet0/3 : address is 001e.f762.bc47, irq 9
4: Ext: Management0/0 : address is 001e.f762.bc43, irq 11
5: Int: Not used : irq 11
6: Int: Not used : irq 5
Licensed features for this platform:
Maximum Physical Interfaces : Unlimited perpetual
Maximum VLANs : 150 perpetual
Inside Hosts : Unlimited perpetual
Failover : Active/Active perpetual
Encryption-DES : Enabled perpetual
Encryption-3DES-AES : Enabled perpetual
Security Contexts : 2 perpetual
GTP/GPRS : Disabled perpetual
AnyConnect Premium Peers : 2 perpetual
AnyConnect Essentials : Disabled perpetual
Other VPN Peers : 750 perpetual
Total VPN Peers : 750 perpetual
Shared License : Disabled perpetual
AnyConnect for Mobile : Disabled perpetual
AnyConnect for Cisco VPN Phone : Disabled perpetual
Advanced Endpoint Assessment : Disabled perpetual
UC Phone Proxy Sessions : 2 perpetual
Total UC Proxy Sessions : 2 perpetual
Botnet Traffic Filter : Disabled perpetual
Intercompany Media Engine : Disabled perpetual
Cluster : Disabled perpetual
This platform has an ASA 5520 VPN Plus license.
Here is the failover config
failover
failover lan unit primary
failover lan interface SFO GigabitEthernet0/3
failover replication http
failover link SFO GigabitEthernet0/3
failover interface ip SFO 10.10.16.25 255.255.255.248 standby 10.10.16.26
Here is the Show failover output
Failover On
Failover unit Primary
Failover LAN Interface: SFO GigabitEthernet0/3 (Failed - No Switchover)
Unit Poll frequency 1 seconds, holdtime 15 seconds
Interface Poll frequency 5 seconds, holdtime 25 seconds
Interface Policy 1
Monitored Interfaces 3 of 160 maximum
failover replication http
Version: Ours 9.1(1), Mate Unknown
Last Failover at: 12:53:27 UTC Mar 14 2013
This host: Primary - Active
Active time: 18059 (sec)
slot 0: ASA5520 hw/sw rev (2.0/9.1(1)) status (Up Sys)
Interface inside (10.10.16.1): No Link (Waiting)
Interface corporate_network_traffic (10.10.16.21): Unknown (Waiting)
Interface outside (193.158.46.130): Unknown (Waiting)
slot 1: empty
Other host: Secondary - Not Detected
Active time: 0 (sec)
Interface inside (10.10.16.2): Unknown (Waiting)
Interface corporate_network_traffic (10.10.16.22): Unknown (Waiting)
Interface outside (193.158.46.131): Unknown (Waiting)
Stateful Failover Logical Update Statistics
Link : SFO GigabitEthernet0/3 (Failed)
Here is the output for the secondary firewall
Cisco Adaptive Security Appliance Software Version 9.1(1)
Device Manager Version 6.2(5)
Compiled on Wed 28-Nov-12 10:38 by builders
System image file is "disk0:/asa911-k8.bin"
Config file at boot was "startup-config"
ciscoasa up 1 hour 1 min
failover cluster up 1 hour 1 min
Hardware: ASA5520, 2048 MB RAM, CPU Pentium 4 Celeron 2000 MHz,
Internal ATA Compact Flash, 256MB
BIOS Flash M50FW080 @ 0xfff00000, 1024KB
Encryption hardware device : Cisco ASA-55xx on-board accelerator (revision 0x0)
Boot microcode : CN1000-MC-BOOT-2.00
SSL/IKE microcode : CNLite-MC-SSLm-PLUS-2.03
IPSec microcode : CNlite-MC-IPSECm-MAIN-2.08
Number of accelerators: 1
0: Ext: GigabitEthernet0/0 : address is 0023.0477.12e4, irq 9
1: Ext: GigabitEthernet0/1 : address is 0023.0477.12e5, irq 9
2: Ext: GigabitEthernet0/2 : address is 0023.0477.12e6, irq 9
3: Ext: GigabitEthernet0/3 : address is 0023.0477.12e7, irq 9
4: Ext: Management0/0 : address is 0023.0477.12e3, irq 11
5: Int: Not used : irq 11
6: Int: Not used : irq 5
Licensed features for this platform:
Maximum Physical Interfaces : Unlimited perpetual
Maximum VLANs : 150 perpetual
Inside Hosts : Unlimited perpetual
Failover : Active/Active perpetual
Encryption-DES : Enabled perpetual
Encryption-3DES-AES : Enabled perpetual
Security Contexts : 2 perpetual
GTP/GPRS : Disabled perpetual
AnyConnect Premium Peers : 2 perpetual
AnyConnect Essentials : Disabled perpetual
Other VPN Peers : 750 perpetual
Total VPN Peers : 750 perpetual
Shared License : Disabled perpetual
AnyConnect for Mobile : Disabled perpetual
AnyConnect for Cisco VPN Phone : Disabled perpetual
Advanced Endpoint Assessment : Disabled perpetual
UC Phone Proxy Sessions : 2 perpetual
Total UC Proxy Sessions : 2 perpetual
Botnet Traffic Filter : Disabled perpetual
Intercompany Media Engine : Disabled perpetual
Cluster : Disabled perpetual
This platform has an ASA 5520 VPN Plus license.
Here is the failover config
failover
failover lan unit secondary
failover lan interface SFO GigabitEthernet0/3
failover replication http
failover link SFO GigabitEthernet0/3
failover interface ip SFO 10.10.16.26 255.255.255.248 standby 10.10.16.25
Here is the Show failover output
failover
failover lan unit secondary
failover lan interface SFO GigabitEthernet0/3
failover replication http
failover link SFO GigabitEthernet0/3
failover interface ip SFO 10.10.16.26 255.255.255.248 standby 10.10.16.25
Failover On
Failover unit Secondary
Failover LAN Interface: SFO GigabitEthernet0/3 (up)
Unit Poll frequency 1 seconds, holdtime 15 seconds
Interface Poll frequency 5 seconds, holdtime 25 seconds
Interface Policy 1
Monitored Interfaces 0 of 160 maximum
failover replication http
Version: Ours 9.1(1), Mate Unknown
Last Failover at: 12:58:31 UTC Mar 14 2013
This host: Secondary - Active
Active time: 3630 (sec)
slot 0: ASA5520 hw/sw rev (2.0/9.1(1)) status (Up Sys)
slot 1: empty
Other host: Primary - Not Detected
Active time: 0 (sec)
Stateful Failover Logical Update Statistics
Link : SFO GigabitEthernet0/3 (up)
interface g0/3 on both are up via the No shutdown command. However I get the following error No Active mate detected
please could someone help.
Many thanksHello James,
You have configured the IPs on the interfaces incorrectly.
Let me point it out
failover
failover lan unit primary
failover lan interface SFO GigabitEthernet0/3
failover replication http
failover link SFO GigabitEthernet0/3
failover interface ip SFO 10.10.16.25 255.255.255.248 standby 10.10.16.26
You are telling the Primary device use IP address 10.10.16.25 and the secondary firewall will be 10.10.26.26
Now let's see the configuration on the Secondary Unit?
failover
failover lan unit secondary
failover lan interface SFO GigabitEthernet0/3
failover replication http
failover link SFO GigabitEthernet0/3
failover interface ip SFO 10.10.16.26 255.255.255.248 standby 10.10.16.25
On the secondary you are saying the primary IP will be 10.10.16.26 and the secondary will be 10.10.16.25
You have it backwards and based on the output I would say you configured it on all of the interfaces like that
So please change it and make it the same on all of the interfaces so both devices know the same thing ( which IP they should use when they are primary and secondary, this HAVE to match )
Hope that I could help
Julio Carvajal -
2 node Sun Cluster 3.2, resource groups not failing over.
Hello,
I am currently running two v490s connected to a 6540 Sun Storagetek array. After attempting to install the latest OS patches the cluster seems nearly destroyed. I backed out the patches and right now only one node can process the resource groups properly. The other node will appear to take over the Veritas disk groups but will not mount them automatically. I have been working on this for over a month and have learned alot and fixed alot of other issues that came up, but the cluster is just not working properly. Here is some output.
bash-3.00# clresourcegroup switch -n coins01 DataWatch-rg
clresourcegroup: (C776397) Request failed because node coins01 is not a potential primary for resource group DataWatch-rg. Ensure that when a zone is intended, it is explicitly specified by using the node:zonename format.
bash-3.00# clresourcegroup switch -z zcoins01 -n coins01 DataWatch-rg
clresourcegroup: (C298182) Cannot use node coins01:zcoins01 because it is not currently in the cluster membership.
clresourcegroup: (C916474) Request failed because none of the specified nodes are usable.
bash-3.00# clresource status
=== Cluster Resources ===
Resource Name Node Name State Status Message
ftp-rs coins01:zftp01 Offline Offline
coins02:zftp01 Offline Offline - LogicalHostname offline.
xprcoins coins01:zcoins01 Offline Offline
coins02:zcoins01 Offline Offline - LogicalHostname offline.
xprcoins-rs coins01:zcoins01 Offline Offline
coins02:zcoins01 Offline Offline - LogicalHostname offline.
DataWatch-hasp-rs coins01:zcoins01 Offline Offline
coins02:zcoins01 Offline Offline
BDSarchive-res coins01:zcoins01 Offline Offline
coins02:zcoins01 Offline Offline
I am really at a loss here. Any help appreciated.
ThanksMy advice is to open a service call, provided you have a service contract with Oracle. There is much more information required to understand that specific configuration and to analyse the various log files. This is beyond what can be done in this forum.
From your description I can guess that you want to failover a resource group between non-global zones. And it looks like the zone coins01:zcoins01 is reported to not be in cluster membership.
Obviously node coins01 needs to be a cluster member. If it is reported as online and has joined the cluster, then you need to verify if the zone zcoins01 is really properly up and running.
Specifically you need to verify that it reached the multi-user milestone and all cluster related SMF services are running correctly (ie. verify "svcs -x" in the non-global zone).
You mention Veritas diskgroups. Note that VxVM diskgroups are handled in the global cluster level (ie. in the global zone). The VxVM diskgroup is not imported for a non-global zone. However, with SUNW.HAStoragePlus you can ensure that file systems on top of VxVM diskgroups can be mounted into a non-global zone. But again, more information would be required to see how you configued things and why they don't work as you expect it.
Regards
Thorsten -
2012 R2 iSCSI CSV not failing over when storage NICs disabled (no redirected access)
We have a couple of simple two node Hyper-V clusters. They are fresh installs with 2012R2 (running on Cisco UCS blades).
They are configured with dedicated NIC for Management, 2x dedicated NICs for storage (using MPIO and NetApp DSM) and then a trunk for VM traffic with virtual adapters for CSV, Live Migration and Heartbeat. Binding orders all set and priorities.
With storage, we have a 1GB Quorum disk and then a temporary 500GB CSV.
All is healthy and happy, I can move VMs around, move the CSV around, fail hosts etc and all works fine.
HOWEVER..... If I disable BOTH of the iSCSI NICs on one of the host (the host that currently owns the CSV), then all hell breaks out. I would have expected that the CSV would go into redirected mode and use the connection from the other node? The CSV disappears
from FCM temporarily, then comes back and goes red (Offline). It doesn't even try to failover to the other node. If I manually move it over to the other node then the CSV comes straight back online.
Watching in Disk Manager on both nodes I can see on the effected host that the volumes do not disappear once it looses the iSCSI connection. I'm pretty sure that with the iSCSI disconnected (iscsicpl showing "reconnecting" state) that those disks
should disappear? But perhaps that is my problem here.
Is the expected behavior or does it sound wrong? If so, any ideas?
Also - I've noticed that in FCM, my cluster networks all go to a state of showing a red question mark over them with the exception of the management NIC. It feels like the cluster is having a fit and failing to communicate properly once I disable the iSCSI
NICs.
Any input greatly appreciated!I think I might have found the answer......
The AD objects for the clusters had been moved from the Computers OU into a newly created OU. I'm suspecting that the cluster node computer objects didn't have perms to the cluster object within that OU and that was causing the issue. I know I've seen cluster
object issues before when moving to a new OU.
All has started working again for the moment so I now just need to investigate what permissions I need on the new OU so that I can move the cluster object in. -
Network Load Balancing not failing over properly
I have 2 MS 2012 servers setup in a NLB unicast configuration, with 2 NICs each on the same subnet. When I take down the second server (and only the second server) the FQDN goes offline. Below are the ipconfigs for each server. Any help
would be greatly appreciated!
Ethernet adapter Data NIC 192.168.220.172:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) I350 Gigabit Network
#4
Physical Address. . . . . . . . . : 6C-3B-E5-B2-48-60
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.220.172(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.220.1
DNS Servers . . . . . . . . . . . : 192.168.220.100
192.168.200.10
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter Cluster NIC:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom BCM57810 NetXtreme II
DIS VBD Client) #67
Physical Address. . . . . . . . . : 02-BF-C0-A8-DC-AA
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.220.171(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IPv4 Address. . . . . . . . . . . : 192.168.220.170(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.220.1
DNS Servers . . . . . . . . . . . : 192.168.220.100
192.168.200.10
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter Data NIC 192.168.220.174:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : HP FlexFabric 10Gb 2-port 533FLR-
r #54
Physical Address. . . . . . . . . : A0-D3-C1-F6-96-08
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.220.174(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.220.1
DNS Servers . . . . . . . . . . . : 192.168.220.100
192.168.200.10
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter Cluster NIC:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : HP NC523SFP 10Gb 2-port Server Ad
Physical Address. . . . . . . . . : 02-BF-C0-A8-DC-AA
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.220.173(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IPv4 Address. . . . . . . . . . . : 192.168.220.170(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.220.1
DNS Servers . . . . . . . . . . . : 192.168.220.100
192.168.200.10
NetBIOS over Tcpip. . . . . . . . : EnabledHi MS DEF,
A second network adapter is required to provide peer-to-peer communication between cluster hosts. Please isolate your heartbeat network. With unicast when cluster is connected
to a switch, incoming packets are sent to all the ports on the switch, which can cause switch flooding, please confirm you have setup your switch correct, you can refer the following Cisco Switch related unicast configuration.
The Cisco switch unicast related information:
How to configure Microsoft Network Load Balancing on two switches
https://supportforums.cisco.com/discussion/11918276/how-configure-microsoft-network-load-balancing-two-switches
More information:
Selecting the Unicast or Multicast Method of Distributing Incoming Requests
http://technet.microsoft.com/en-us/library/cc782694(v=ws.10).aspx
An Optimal Network Load Balancing (NLB) Configuration
http://blogs.technet.com/b/clint_huffman/archive/2007/10/08/an-optimal-network-load-balancing-nlb-configuration.aspx
Selecting the Unicast or Multicast Method of Distributing Incoming Requests
http://technet.microsoft.com/en-us/library/cc782694(v=ws.10).aspx
I’m glad to be of help to you!
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place. -
GetConnection on clustered DS not failing over as documentation indicates
Hi,
(Weblogic 7 SP2 )
I have a Connection pool and datasource both targeted to a cluster.
The cluster is working as a cluster, HTTP session failover is working
for instance, as is context failover. However, ds.getConnection() does
not failover to another DS when the machine hosting the ds is down. I
don't expect connection failover, I just expect DS failover as indicated
by the docs.
The JDBC documentation indicates that the datasource is cluster aware
(see the quotes below). However, I do not observe this value.
I have a client connecting to the cluster using the cluster address.
If I lookup the the datasource, then in a loop do
Connection ccc = ds.getConnection();
ccc.close();
Thread.sleep(500);
(with exception handling omittted)
Then I expect that when the server to which the ds is connected (the
server on which it was looked up, which is determined by the context
which I used to look it up, which is determined by round robin) goes
down, that the getConnection() will failover to another machine.
That is, I expected getconnection() to return a connection from another
pool to which the datasource was targetted. This does not happen.
Instead I get a connection error:
weblogic.rmi.extensions.RemoteRuntimeException: Unexpected Exception
- with nested exception:
[java.rmi.ConnectException: Could not establish a connection with
-4447598948888936840S:10.0.10.10:[7001,7001,7002,7002,7001,7002,-1]:10.0.10.10:7001,10.0.10.14:7001:my2:ServerA,
java.rmi.ConnectException: Destination unreachable; nested exception is:
java.net.ConnectException: Connection refused: connect; No available
router to destination]
The datasource is after all a cluster-aware stub?
What is the intended behaviour?
Thanks,
Q
"Clustered JDBC eases the reconnection process: the cluster-aware nature
of WebLogic data sources in external client applications allow a client
to request another connection from them if the server instance that was
hosting the previous connection fails."
"External Clients Connections?External clients that require a database
connection perform a JNDI lookup and obtain a replica-aware stub for the
data source. The stub for the data source contains a list of the server
instances that host the data source?which should be all of the Managed
Servers in the cluster. Replica-aware stubs contain load balancing logic
for distributing the load among host server instances."This is a bug in WL 7 (& 8).
"QQuatro" <[email protected]> wrote in message
news:[email protected]...
Hi,
(Weblogic 7 SP2 )
I have a Connection pool and datasource both targeted to a cluster.
The cluster is working as a cluster, HTTP session failover is working
for instance, as is context failover. However, ds.getConnection() does
not failover to another DS when the machine hosting the ds is down. I
don't expect connection failover, I just expect DS failover as indicated
by the docs.
The JDBC documentation indicates that the datasource is cluster aware
(see the quotes below). However, I do not observe this value.
I have a client connecting to the cluster using the cluster address.
If I lookup the the datasource, then in a loop do
Connection ccc = ds.getConnection();
ccc.close();
Thread.sleep(500);
(with exception handling omittted)
Then I expect that when the server to which the ds is connected (the
server on which it was looked up, which is determined by the context
which I used to look it up, which is determined by round robin) goes
down, that the getConnection() will failover to another machine.
That is, I expected getconnection() to return a connection from another
pool to which the datasource was targetted. This does not happen.
Instead I get a connection error:
weblogic.rmi.extensions.RemoteRuntimeException: Unexpected Exception
- with nested exception:
[java.rmi.ConnectException: Could not establish a connection with
-4447598948888936840S:10.0.10.10:[7001,7001,7002,7002,7001,7002,-1]:10.0.10.10:7001,10.0.10.14:7001:my2:ServerA,
java.rmi.ConnectException: Destination unreachable; nested exception is:
java.net.ConnectException: Connection refused: connect; No available
router to destination]
The datasource is after all a cluster-aware stub?
What is the intended behaviour?
Thanks,
Q
"Clustered JDBC eases the reconnection process: the cluster-aware nature
of WebLogic data sources in external client applications allow a client
to request another connection from them if the server instance that was
hosting the previous connection fails."
"External Clients Connections—External clients that require a database
connection perform a JNDI lookup and obtain a replica-aware stub for the
data source. The stub for the data source contains a list of the server
instances that host the data source—which should be all of the Managed
Servers in the cluster. Replica-aware stubs contain load balancing logic
for distributing the load among host server instances."
Maybe you are looking for
-
I was on my son's school website and I was looking to click the link to his teachers personal web-page. When I did, many, many "untitled" new tabs kept opening in the same screen. In fact it did not stop until I restarted my computer. When I tried to
-
How to call a BPEL process from Oracle Apps Java Concurrent program
Hello, I need to trigger a BPEL process from Oracle Apps. Can anybody tell me how to do that? I have two triggering option-- 1. On button click from a Form 6i screen 2. Using Java Concurrent program. Thanks in advance. Debkanta
-
Cannot embed pdfs in Word doc which are PDF Version 1.3 (Acrobat 4.x) [This is associated with Adobe Reader 9]. Getting 'program not installed' error. Pdfs with other versions are okay: Tested successfully with Adobe Pro 9 (Version 1.5 (Acrobat 6.x))
-
How to define new derivation rules in FM module
Can somebody help me define a new derivation rule which is user specific in FM module. I want to map muliple Fund Centers to a single Cost center and also map many commitment items to a single GL. Thanks shivaji
-
Set measure to NULL for dates in the future
Hi all I am trying to set the values of a measure to NULL in case the date is in the future. I have a time dimension and fact table. What I have so fat is the following: IIF([Date].[CalendarDetailed].CURRENTMEMBER.Name < format(now(), "yyyy-MM-dd"),