Failover to deprecated interface
Hi,
I have a 2 node cluster (SC 3.2) with Link based IPMP. Ive configured a very basic Resource Group with a LogicalHostname and simple Apache start script to test failover.
I have 2 interfaces (ce0 and ce4) with the management IP on ce0, my problem is that when I start the logicalhostname resource it is created on ce4, this also occurs when I failover the resource group to the failover node.
I have cut/pasted some information below and any input would be gratefully received - please note I have had to remove the 1st 2 octets as our security requires.. any more output required please let me know....
On another note, I created a dependency of apache-test to testip-res so what is the best command to view the actual dependency please..??.. VCS is a simple hares ...
root@server1 # ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
ce0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet xx.xx.69.224 netmask ffffff80 broadcast xx.xx.69.255
groupname man_ipmp
ether 0:14:4f:7c:c5:1c
ce3: flags=1008843<UP,BROADCAST,RUNNING,MULTICAST,PRIVATE,IPv4> mtu 1500 index 5
inet xx.xx.0.130 netmask ffffff80 broadcast xx.xx.0.255
ether 0:14:4f:43:67:5
ce4: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3
inet 0.0.0.0 netmask ff000000 broadcast 0.255.255.255
groupname man_ipmp
ether 0:14:4f:43:67:6
ce4:1: flags=1040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4> mtu 1500 index 3
inet xx.xx.69.225 netmask ffffff80 broadcast xx.xx.69.255
ce7: flags=1008843<UP,BROADCAST,RUNNING,MULTICAST,PRIVATE,IPv4> mtu 1500 index 4
inet xx.xx.1.2 netmask ffffff80 broadcast xx.xx.1.127
ether 0:14:4f:43:79:21
clprivnet0: flags=1009843<UP,BROADCAST,RUNNING,MULTICAST,MULTI_BCAST,PRIVATE,IPv4> mtu 1500 index 6
inet xx.xx.4.2 netmask fffffe00 broadcast xx.xx.5.255
ether 0:0:0:0:0:2
root@server1 # cat /etc/hostname.ce0
server1 group man_ipmp up
root@server1 # cat /etc/hostname.ce4
group man_ipmp up
root@server1 # cat /etc/hosts
# Internet host table
127.0.0.1 localhost
xx.xx.69.224 server1 loghost
xx.xx.69.227 server2
# Logical IP for SunCluster test
xx.xx.69.225 test-ip
root@server1 # clrg show
Resource Groups and Resources ===
Resource Group: sterg
RG_description: <NULL>
RG_mode: Failover
RG_state: Managed
Failback: False
Nodelist: server1 server2
--- Resources for Group sterg ---
Resource: testip-res
Type: SUNW.LogicalHostname:2
Type_version: 2
Group: sterg
R_description:
Resource_project_name: default
Enabled{server2}: True
Enabled{server1}: True
Monitored{server2}: True
Monitored{server1}: True
Resource: apache-res
Type: SUNW.gds:6
Type_version: 6
Group: sterg
R_description:
Resource_project_name: default
Enabled{server2}: True
Enabled{server1}: True
Monitored{server2}: True
Monitored{server1}: True
I've checked with my networking colleagues and this is what is expected. The logical host should end up on the NIC with the least number of logical IP addresses plumb.
Is it actually causing any problem? If so, could you post back and I can take it up with my colleagues.
The commands to show resource dependency would be:
clrs show -v <resource_name> | grep -i depend
For resource groups you can get dependencies and affinities using:
clrg show -v <rg_name> | egrep -e "affinity|depend"
Tim
---
Similar Messages
-
Deprecated interfaces and methods
We have a weblogic time service that utilize a lot of
deprecated interfaces and methods such as
ScheduledTriggerDef, TimeServicesDef etc. Although the time
service runs in the WLS 7, it is a big concern to me
that it uses so many deprecated interfaces or methods.
I am just wondering how I can replace them with non-deprecated onesMark,
I have a question about the API.
From the documentation and the API docs it is not clear how to schedule
a callback to be called just once ASAP.
We use the deprecated Timer service to execute long running operations
on the Weblogic thread pool and want the operation to execute only once
and start as soon as there is a thread available.
It is not clear what will happen in case a task is scheduled to be
executed only once and the time for that execution has passed ( 5 ms ago).
I'd appreciate the clarification.
Thanks,
Dejan
Mark Griffith wrote:
It will run because it is only deprecated. You should at some point
"rewrite", but the rewrite is not that big of a deal. There maybe some
slight differences in timers, since we moved to jmx interfacs, but the
scemantics should be very very close.
Attached is an example that will run in the 8.1 sample environment.
cd to $WLS_HOME
(On my box it is /bea/wls81/weblogic81/)
cd samples/domains/examples/
setExamplesEnv.sh
cd ../../server/examples/src/examples
../examples/src/examples 201$ pwd
C:/bea/wls81/weblogic81/samples/server/examples/src/examples
cp jmxTimerEar.zip .
jar xvf jmxTimerEar.zip
cd jmxTimerEar
ant
And it should build for you.
Cheers
mbg
"Eric Sundberg" <[email protected]> wrote in message
news:[email protected]..
We have a weblogic time service that utilize a lot of
deprecated interfaces and methods such as
ScheduledTriggerDef, TimeServicesDef etc. Although the time
service runs in the WLS 7, it is a big concern to me
that it uses so many deprecated interfaces or methods.
I am just wondering how I can replace them with non-deprecated ones -
ASA-5505 failover, cant choose interface
Hi
I am trying to configure two ASA-5505 as a failover pair.
Software 8.2.5 and ASDM 6.4.5.206
Using the wizard i get to step3 .. then nothing happenes.
Trying direct in asdm but the only interface i can choose is "--None Unnamed-"
How do i get any further ?
/PerSolved this by configuring the failocer interface by cli
-
Need to "move" failover to different interface/port
Sorry if this is the wrong area, we have so seldom had questions that were not otherwise handled I don't frequent this area.
How difficult is it to change the interface used for active/standby failover? It's a working, already configured pair with standby, but I need to move the crossover cable and tell them to use a different interface.
ASA 5510 pair, already set up and working with failover that was originally configured on Ethernet port 0/3 by the senior network admin. It appears that from his use of interfaces or ports he used things straight out of examples on the web, including the interfaces used.
The senior network admin retired last spring and left me "in charge", gee, thanks.
I need to make some changes and need an Ethernet port for a new important project.
The Management 0/0 interface is unused and shutdown. We manage via inside interface from a specific subnet inside so don't need the dedicated management interface.
I want to move failover FROM Ethernet 0/3 TO Management 0/0
*This is the current setup:
Result of the command: "sh run failover"
failover
failover lan unit primary
failover lan interface failover Ethernet0/3
failover link failover Ethernet0/3
failover interface ip failover 169.254.255.1 255.255.255.252 standby 169.254.255.2
*And this is the current interface configuration for 0/3 and Management:
interface Ethernet0/3
description LAN/STATE Failover Interface
interface Management0/0
speed 100
duplex full
shutdown
nameif management
security-level 0
no ip address
ospf cost 10
I know it can run on the Management 0/0 interface because I see a lot of "how to configure" as if the ASA is brand new and several examples out there indeed show it being setup on Management.
I'm looking for how to take an ASA pair that is currently configured and has a working functional failover configuration and simply "move failover" to a different hole or change the interfaces used for the "heartbeat" as it were.
I assume it's not hard - but I also assume there's a specific sequence of events that must take place to prevent the pair from going into failover and switching lead roles...........
For example - would I shut off or turn off failover, and if so how, and on which ASA (frankly, I'm not sure how to access the secondary or standby if this must be done from or on the standby unit as I've never done that "deep" a config before)
CLI is fine - I'd be just as comfortable in either ASDM or cli.
I sure hope this makes sense - I'm more of a troubleshooter and fixer than a designer or network engineer....
And many many thanks - getting this moved will free up the interface I need and can really make a big dent in my project list while the supervisor is on vacation this week! I'd love to have this done and working before his return.
Oh, in case it does matter as I've been told, this is the Currently running license and versions shown here:
Cisco Adaptive Security Appliance Software Version 8.4(4)1
Device Manager Version 6.4(7)
Compiled on Thu 14-Jun-12 11:20 by builders
System image file is "disk0:/asa844-1-k8.bin"
Config file at boot was "startup-config"
VRDSMFW1 up 141 days 4 hours
failover cluster up 141 days 4 hours
Hardware: ASA5510, 1024 MB RAM, CPU Pentium 4 Celeron 1600 MHz
Internal ATA Compact Flash, 256MB
BIOS Flash M50FW080 @ 0xfff00000, 1024KB
Encryption hardware device : Cisco ASA-55x0 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.06
Number of accelerators: 1
0: Ext: Ethernet0/0 : address is 0024.972b.e020, irq 9
1: Ext: Ethernet0/1 : address is 0024.972b.e021, irq 9
2: Ext: Ethernet0/2 : address is 0024.972b.e022, irq 9
3: Ext: Ethernet0/3 : address is 0024.972b.e023, irq 9
4: Ext: Management0/0 : address is 0024.972b.e01f, 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 : 100 perpetual
Inside Hosts : Unlimited perpetual
Failover : Active/Active perpetual
VPN-DES : Enabled perpetual
VPN-3DES-AES : Enabled perpetual
Security Contexts : 2 perpetual
GTP/GPRS : Disabled perpetual
AnyConnect Premium Peers : 2 perpetual
AnyConnect Essentials : 250 perpetual
Other VPN Peers : 250 perpetual
Total VPN Peers : 250 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
This platform has an ASA 5510 Security Plus license.
Failover cluster licensed features for this platform:
Maximum Physical Interfaces : Unlimited perpetual
Maximum VLANs : 100 perpetual
Inside Hosts : Unlimited perpetual
Failover : Active/Active perpetual
VPN-DES : Enabled perpetual
VPN-3DES-AES : Enabled perpetual
Security Contexts : 4 perpetual
GTP/GPRS : Disabled perpetual
AnyConnect Premium Peers : 4 perpetual
AnyConnect Essentials : 250 perpetual
Other VPN Peers : 250 perpetual
Total VPN Peers : 250 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 : 4 perpetual
Total UC Proxy Sessions : 4 perpetual
Botnet Traffic Filter : Disabled perpetual
Intercompany Media Engine : Disabled perpetual
This platform has an ASA 5510 Security Plus license.
Serial Number: ABC12345678
Running Permanent Activation Key: eieioandapartridgeinapeartree
Configuration register is 0x1
Configuration last modified by me at 15:03:07.132 CDT Mon Sep 15 2014If there was a "smack-self-on-forehead" icon here I'd use it now.
Of course, totally logical - if you disconnect a monitored connection on the standby it's not about to take over as primary because it's had a failure and can't do the job, forcing the primary or active to remain that way. There's the key that would allow all other changes.
Since the settings or config lines are in place already, then if I'm correct it's a matter of then just modifying what's there, and of course removing the name of the Management interface (no nameif) and making sure it's not shut down (no shutdown), etc.
You are a handy person to have around. Thanks.
By the way, *thanks to prior answers received here* and reading responses to others who had questions I can say I've set a record for this agency and done what no one else had been able to do - I've taken a troublesome LAN-to-LAN connection and made it trouble-free with a solid connection that is just 7.5 hours away from being up 90 days with no interruption, no collapse of any SA and improved performance. I have 2 others out of our 34 that aren't too far behind that. The boss has recognized this after seeing his monthly up-time reports.
Once I get this done failover change made I will be setting up a "DMZ" of sorts and trying out my hand at telling the 5510s to forward specific traffic aimed at a specific public IP address to a specific server. (But that's another topic............) -
My ASA5540 8.2.4(4) can not monitor and failover on certain interfaces
the story is
we configure the
monitor interface inside
monitor interface outside
monitor interface partner
and save configue
but when i show run monitor-interface
the configure do not show the 3 montitor interfaces, it only show other monitor interfaces,which can failover , but not the above 3 interfaces, however they are all showed interface monitor in the ASDM configure
here is the show version
==================================
Cisco Adaptive Security Appliance Software Version 8.2(4)4
Device Manager Version 6.4(5)
Compiled on Thu 03-Mar-11 17:18 by builders
System image file is "disk0:/asa824-4-k8.bin"
Config file at boot was "startup-config"
dcm-lidc-fw1 up 9 days 18 hours
failover cluster up 16 days 20 hours
Hardware: ASA5540, 2048 MB RAM, CPU Pentium 4 2000 MHz
Internal ATA Compact Flash, 256MB
BIOS Flash Firmware Hub @ 0xffe00000, 1024KB
Encryption hardware device : Cisco ASA-55x0 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.05
0: Ext: GigabitEthernet0/0 : address is 30e4.db7b.6f82, irq 9
1: Ext: GigabitEthernet0/1 : address is 30e4.db7b.6f83, irq 9
2: Ext: GigabitEthernet0/2 : address is 30e4.db7b.6f84, irq 9
3: Ext: GigabitEthernet0/3 : address is 30e4.db7b.6f85, irq 9
4: Ext: Management0/0 : address is 30e4.db7b.6f86, irq 11
5: Int: Internal-Data0/0 : address is 0000.0001.0002, irq 11
6: Int: Not used : irq 5
7: Ext: GigabitEthernet1/0 : address is 30e4.db02.1f96, irq 255
8: Ext: GigabitEthernet1/1 : address is 30e4.db02.1f97, irq 255
9: Ext: GigabitEthernet1/2 : address is 30e4.db02.1f98, irq 255
10: Ext: GigabitEthernet1/3 : address is 30e4.db02.1f99, irq 255
11: Int: Internal-Data1/0 : address is 0000.0003.0002, irq 255
Licensed features for this platform:
Maximum Physical Interfaces : Unlimited
Maximum VLANs : 200
Inside Hosts : Unlimited
Failover : Active/Active
VPN-DES : Enabled
VPN-3DES-AES : Enabled
Security Contexts : 2
GTP/GPRS : Disabled
SSL VPN Peers : 2
Total VPN Peers : 5000
Shared License : Disabled
AnyConnect for Mobile : Disabled
AnyConnect for Cisco VPN Phone : Disabled
AnyConnect Essentials : Enabled
Advanced Endpoint Assessment : Disabled
UC Phone Proxy Sessions : 2
Total UC Proxy Sessions : 2
Botnet Traffic Filter : Disabled
This platform has an ASA 5540 VPN Premium license.
==========here is the show monitor interface, it does not show outside/inside/partner====================
-fw1# sh run monitor-interface
monitor-interface app
monitor-interface dmz
monitor-interface data
monitor-interface dev-app
monitor-interface dev-data
no monitor-interface management
-fw1#
-fw1(config)# sh run all | in monitor
banner motd * This is a private and monitored system. *
monitor-interface app
monitor-interface dmz
monitor-interface data
monitor-interface dev-app
monitor-interface dev-data
no monitor-interface management
===============failover test =============
- unplug the outside interface cable on primary , led go off, but failover does not happen-
- upplug the cable on inside, or parner , it still do not failover
- only unplug the cable on other monitor interface , it failover.
=======clear config monitor-interface, and enter monitor-interface command for all the interface, re test, again, same result=======fw1# sh failover
Failover On
Failover unit Secondary
Failover LAN Interface: failover GigabitEthernet1/3 (up)
Unit Poll frequency 1 seconds, holdtime 15 seconds
Interface Poll frequency 5 seconds, holdtime 25 seconds
Interface Policy 1
Monitored Interfaces 8 of 210 maximum
Version: Ours 8.2(4)4, Mate 8.2(4)4
Last Failover at: 15:44:00 EST Nov 24 2011
This host: Secondary - Standby Ready
Active time: 767625 (sec)
slot 0: ASA5540 hw/sw rev (2.0/8.2(4)4) status (Up Sys)
Interface outside (209.202.65.132): Normal
Interface inside (10.100.161.2): Normal
Interface app (10.100.171.2): Normal
Interface dmz (10.100.172.2): Normal
Interface data (10.100.173.2): Normal
Interface dev-app (10.100.174.2): Normal
Interface dev-data (10.100.175.2): Normal
Interface management (10.7.4.9): Failed (Not-Monitored)
Interface partner (10.100.160.14): Normal
slot 1: ASA-SSM-4GE hw/sw rev (1.0/1.0(0)10) status (Up)
Other host: Primary - Active
Active time: 77823 (sec)
slot 0: ASA5540 hw/sw rev (2.0/8.2(4)4) status (Up Sys)
Interface outside (209.202.65.131): Normal
Interface inside (10.100.161.1): Normal
Interface app (10.100.171.1): Normal
Interface dmz (10.100.172.1): Normal
Interface data (10.100.173.1): Normal
Interface dev-app (10.100.174.1): Normal
Interface dev-data (10.100.175.1): Normal
Interface management (10.7.4.8): Normal (Not-Monitored)
Interface partner (10.100.160.13): Normal
slot 1: ASA-SSM-4GE hw/sw rev (1.0/1.0(0)10) status (Up)
Stateful Failover Logical Update Statistics
Link : failover GigabitEthernet1/3 (up)
Stateful Obj xmit xerr rcv rerr
General 1001073 0 443701 25
sys cmd 194284 0 194283 0
up time 0 0 0 0
RPC services 0 0 0 0
TCP conn 262196 0 45389 2
UDP conn 342196 0 47480 3
ARP tbl 202397 0 156529 20
Xlate_Timeout 0 0 0 0
IPv6 ND tbl 0 0 0 0
VPN IKE upd 0 0 10 0 -
Controller Failover - Clients and Interfaces
We have 2 x 4404 controllers.
It is layer 3 LWAPP. They are in different buildings on different subnets.
They have different AP Manager and Management Interfaces.
They are in the same mobility gourp.
We have some AP's connecting to one controller and others to the second one. AP Failback works fine.
We are using AP Group VLAN's and this seems fine too.
All is working well.
Now - if one controller fails, the AP's failover to the other controller.
No what happens the clients?
They have IP addresses on a VLAN. This VLAN is available on the other Core switch.
Does this VLAN need to be available on the Wireless Controller also?
What needs to be done to keep the all important clients alive in this instance??
Appreciate any feedback.Hi There
We have the same setup at one of our clients and you do definitely need all the WLAN VLANS to be present on both controllers (only different IP Addresses for each VLAN) for the failover and L3 roaming for that matter to work properly. Using remember that in the Mobility Group each WLC needs to be added to the other's Mobility Group for it to function correctly.
If all this is done correctly then it should be fine.
HTH
Steven
Please rate helpful posts. -
If weblogic.jdbc.common.OracleBlob is deprecated then what interface should replace
it?Thanks for you reply, however we are not using the Oracle Thin client. Shouldn't
that be a problem? More specifically, the code looks like this:
java.sql.Clob content = result.getClob(DESCRIPTION);
java.io.Writer osss =
((weblogic.jdbc.common.OracleClob) content).getCharacterOutputStream();
osss.write(getFullDescription());
The code, of course, still seems to work fine, but we get a deprecation warning
on the OracleClob interface. Should the OracleThinClob still work, or do you have
any other information you could provide me? Thanks.
"Slava Imeshev" <[email protected]> wrote:
"Keith Gauntt" <[email protected]> wrote in message news:3fb28831$[email protected]..
If weblogic.jdbc.common.OracleBlob is deprecated then what interfaceshould replace
it?weblogic.jdbc.vendor.oracle.OracleThinBlob
In 8.1 you can cast Blobs directly to Oracle interfaces.
Slava -
Link outage in Etherchannel causes interface down and failover Secondary Faild
Hi,
I have configured port-channel Firewall ASA5515-X and stacking switch WS-3750X. Also firewall configured as failover mode. Problem is that my active firewall connected switch port show green and working but standby firewall connected switch port shows orange color. When i inpute show failover command on firewall, secondary is faild. Please assist. Here is the below show command.
mdbl-int-fw-01# sho port-channel 10
Ports: 2 Maxports = 16
Port-channels: 1 Max Port-channels = 48
Protocol: LACP/ active
Minimum Links: 1
Maximum Bundle: 8
Load balance: src-dst-ip
mdbl-int-fw-01# sho interface port-channel 10
Interface Port-channel10 "inside", is up, line protocol is up
Hardware is EtherChannel/LACP, BW 2000 Mbps, DLY 10 usec
Auto-Duplex(Full-duplex), Auto-Speed(1000 Mbps)
Input flow control is unsupported, output flow control is off
Description: *** Connected to CORE-SW ***
MAC address 4c00.821d.511f, MTU 1500
IP address 10.98.8.97, subnet mask 255.255.255.248
Traffic Statistics for "inside":
56859 packets input, 3419130 bytes
148709 packets output, 16063580 bytes
56858 packets dropped
1 minute input rate 0 pkts/sec, 46 bytes/sec
1 minute output rate 2 pkts/sec, 216 bytes/sec
1 minute drop rate, 0 pkts/sec
5 minute input rate 0 pkts/sec, 46 bytes/sec
5 minute output rate 2 pkts/sec, 216 bytes/sec
5 minute drop rate, 0 pkts/sec
Members in this channel:
Active: Gi0/1 Gi0/2
mdbl-int-fw-01# sho port
mdbl-int-fw-01# sho port-channel sum
mdbl-int-fw-01# sho port-channel summary
Flags: D - down P - bundled in port-channel
I - stand-alone s - suspended
H - Hot-standby (LACP only)
U - in use N - not in use, no aggregation/nameif
M - not in use, no aggregation due to minimum links not met
w - waiting to be aggregated
Number of channel-groups in use: 1
Group Port-channel Protocol Ports
------+-------------+-----------+-----------------------------------------------
10 Po10(U) LACP Gi0/1(P) Gi0/2(P)
mdbl-int-fw-01#
mdbl-int-fw-01# sho port-channel ?
<1-48> Channel group number
brief Brief information
detail Detail information
port Port information
protocol protocol enabled
summary One-line summary per channel-group
| Output modifiers
<cr>
mdbl-int-fw-01# sho port-channel bri
mdbl-int-fw-01# sho port-channel brief
Channel-group listing:
Group: 10
Ports: 2 Maxports = 16
Port-channels: 1 Max Port-channels = 48
Protocol: LACP/ active
Minimum Links: 1
Maximum Bundle: 8
Load balance: src-dst-ip
mdbl-int-fw-01# sho port-channel ?
<1-48> Channel group number
brief Brief information
detail Detail information
port Port information
protocol protocol enabled
summary One-line summary per channel-group
| Output modifiers
<cr>
mdbl-int-fw-01# sho port-channel pro
mdbl-int-fw-01# sho port-channel protocol
Channel-group listing:
Group: 10
Protocol: LACP
mdbl-int-fw-01# sho port-channel ?
<1-48> Channel group number
brief Brief information
detail Detail information
port Port information
protocol protocol enabled
summary One-line summary per channel-group
| Output modifiers
<cr>
mdbl-int-fw-01# sho port-channel det
mdbl-int-fw-01# sho port-channel detail
Channel-group listing:
Group: 10
Ports: 2 Maxports = 16
Port-channels: 1 Max Port-channels = 48
Protocol: LACP/ active
Minimum Links: 1
Maximum Bundle: 8
Load balance: src-dst-ip
Ports in the group:
Port: Gi0/1
Port state = bndl
Channel group = 10 Mode = LACP/ active
Port-channel = Po10
Flags: S - Device is sending Slow LACPDUs F - Device is sending fast LACPDUs.
A - Device is in active mode. P - Device is in passive mode.
Local information:
LACP port Admin Oper Port Port
Port Flags State Priority Key Key Number State
Gi0/1 SA bndl 32768 0xa 0xa 0x2 0x3d
Partner's information:
Partner Partner LACP Partner Partner Partner Partner Partner
Port Flags State Port Priority Admin Key Oper Key Port Number Port State
Gi0/1 SA bndl 32768 0x0 0xa 0x118 0x3d
Port: Gi0/2
Port state = bndl
Channel group = 10 Mode = LACP/ active
Port-channel = Po10
Flags: S - Device is sending Slow LACPDUs F - Device is sending fast LACPDUs.
A - Device is in active mode. P - Device is in passive mode.
Local information:
LACP port Admin Oper Port Port
Port Flags State Priority Key Key Number State
Gi0/2 SA bndl 32768 0xa 0xa 0x3 0x3d
Partner's information:
Partner Partner LACP Partner Partner Partner Partner Partner
Port Flags State Port Priority Admin Key Oper Key Port Number Port State
Gi0/2 SA bndl 32768 0x0 0xa 0x119 0x3d
mdbl-int-fw-01#
mdbl-int-fw-01#
mdbl-int-fw-01#
mdbl-int-fw-01#
mdbl-int-fw-01# sho port-channel ?
<1-48> Channel group number
brief Brief information
detail Detail information
port Port information
protocol protocol enabled
summary One-line summary per channel-group
| Output modifiers
<cr>
mdbl-int-fw-01# sho fail
mdbl-int-fw-01# sho failover st
mdbl-int-fw-01# sho failover state
State Last Failure Reason Date/Time
This host - Primary
Active None
Other host - Secondary
Failed Ifc Failure 22:03:03 UTC Jan 8 2014
outside: No Link
dmz: No Link
mgt: No Link
inside: No Link
====Configuration State===
Sync Done
====Communication State===
Mac set
mdbl-int-fw-01#
mdbl-int-fw-01#
mdbl-int-fw-01#
mdbl-int-fw-01# sho failover
Failover On
Failover unit Primary
Failover LAN Interface: failover GigabitEthernet0/3 (up)
Unit Poll frequency 200 milliseconds, holdtime 800 milliseconds
Interface Poll frequency 500 milliseconds, holdtime 5 seconds
Interface Policy 1
Monitored Interfaces 4 of 114 maximum
failover replication http
Version: Ours 8.6(1)2, Mate 8.6(1)2
Last Failover at: 02:16:48 UTC Jan 8 2014
This host: Primary - Active
Active time: 74479 (sec)
slot 0: ASA5515 hw/sw rev (1.0/8.6(1)2) status (Up Sys)
Interface outside (118.179.139.4): No Link (Waiting)
Interface dmz (10.98.56.3): No Link (Waiting)
Interface mgt (10.10.11.1): Unknown (Waiting)
Interface inside (10.98.8.97): Normal (Waiting)
slot 1: IPS5515 hw/sw rev (N/A/7.1(4)E4) status (Up/Up)
IPS, 7.1(4)E4, Up
Other host: Secondary - Failed
Active time: 0 (sec)
slot 0: ASA5515 hw/sw rev (1.0/8.6(1)2) status (Up Sys)
Interface outside (118.179.139.6): No Link (Waiting)
Interface dmz (10.98.56.2): No Link (Waiting)
Interface mgt (0.0.0.0): No Link (Waiting)
Interface inside (10.98.8.98): No Link (Waiting)
slot 1: IPS5515 hw/sw rev (N/A/7.1(4)E4) status (Up/Up)
IPS, 7.1(4)E4, Up
Stateful Failover Logical Update Statistics
Link : failover GigabitEthernet0/3 (up)
Stateful Obj xmit xerr rcv rerr
General 12665 0 9929 0
sys cmd 9929 0 9929 0
up time 0 0 0 0
RPC services 0 0 0 0
TCP conn 0 0 0 0
UDP conn 0 0 0 0
ARP tbl 2735 0 0 0
Xlate_Timeout 0 0 0 0
IPv6 ND tbl 0 0 0 0
VPN IKEv1 SA 0 0 0 0
VPN IKEv1 P2 0 0 0 0
VPN IKEv2 SA 0 0 0 0
VPN IKEv2 P2 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
SIP Session 0 0 0 0
Route Session 0 0 0 0
User-Identity 1 0 0 0
Logical Update Queue Information
Cur Max Total
Recv Q: 0 7 9930
Xmit Q: 0 30 99581
mdbl-int-fw-01#
mdbl-int-fw-01#
mdbl-int-fw-01# sho failover state
State Last Failure Reason Date/Time
This host - Primary
Active None
Other host - Secondary
Failed Ifc Failure 22:03:03 UTC Jan 8 2014
outside: No Link
dmz: No Link
mgt: No Link
inside: No Link
====Configuration State===
Sync Done
====Communication State===
Mac set
mdbl-int-fw-01# sho failover ?
descriptor Show failover interface descriptors. Two numbers are shown for
each interface. When exchanging information regarding a
particular interface, this unit uses the first number in messages
it sends to its peer. And it expects the second number in
messages it receives from its peer. For trouble shooting, collect
the show output from both units and verify that the numbers
match.
exec Show failover command execution information
history Show failover switching history
interface Show failover command interface information
state Show failover internal state information
statistics Show failover command interface statistics information
| Output modifiers
<cr>
mdbl-int-fw-01# sho failover inter
mdbl-int-fw-01# sho failover interface
interface failover GigabitEthernet0/3
System IP Address: 10.98.8.89 255.255.255.248
My IP Address : 10.98.8.89
Other IP Address : 10.98.8.90
mdbl-int-fw-01# sho failover stati
mdbl-int-fw-01# sho failover statistics
tx:995725
rx:980617
mdbl-int-fw-01# sho failover hi
mdbl-int-fw-01# sho failover history
==========================================================================
From State To State Reason
==========================================================================
02:16:40 UTC Jan 8 2014
Not Detected Negotiation No Error
02:16:48 UTC Jan 8 2014
Negotiation Just Active No Active unit found
02:16:48 UTC Jan 8 2014
Just Active Active Drain No Active unit found
02:16:48 UTC Jan 8 2014
Active Drain Active Applying Config No Active unit found
02:16:48 UTC Jan 8 2014
Active Applying Config Active Config Applied No Active unit found
02:16:48 UTC Jan 8 2014
Active Config Applied Active No Active unit found
==========================================================================
mdbl-int-fw-01# sho failover
Failover On
Failover unit Primary
Failover LAN Interface: failover GigabitEthernet0/3 (up)
Unit Poll frequency 200 milliseconds, holdtime 800 milliseconds
Interface Poll frequency 500 milliseconds, holdtime 5 seconds
Interface Policy 1
Monitored Interfaces 4 of 114 maximum
failover replication http
Version: Ours 8.6(1)2, Mate 8.6(1)2
Last Failover at: 02:16:48 UTC Jan 8 2014
This host: Primary - Active
Active time: 74554 (sec)
slot 0: ASA5515 hw/sw rev (1.0/8.6(1)2) status (Up Sys)
Interface outside (118.179.139.4): No Link (Waiting)
Interface dmz (10.98.56.3): No Link (Waiting)
Interface mgt (10.10.11.1): Unknown (Waiting)
Interface inside (10.98.8.97): Normal (Waiting)
slot 1: IPS5515 hw/sw rev (N/A/7.1(4)E4) status (Up/Up)
IPS, 7.1(4)E4, Up
Other host: Secondary - Failed
Active time: 0 (sec)
slot 0: ASA5515 hw/sw rev (1.0/8.6(1)2) status (Up Sys)
Interface outside (118.179.139.6): No Link (Waiting)
Interface dmz (10.98.56.2): No Link (Waiting)
Interface mgt (0.0.0.0): No Link (Waiting)
Interface inside (10.98.8.98): No Link (Waiting)
slot 1: IPS5515 hw/sw rev (N/A/7.1(4)E4) status (Up/Up)
IPS, 7.1(4)E4, Up
Stateful Failover Logical Update Statistics
Link : failover GigabitEthernet0/3 (up)
Stateful Obj xmit xerr rcv rerr
General 12676 0 9938 0
sys cmd 9938 0 9938 0
up time 0 0 0 0
RPC services 0 0 0 0
TCP conn 0 0 0 0
UDP conn 0 0 0 0
ARP tbl 2737 0 0 0
Xlate_Timeout 0 0 0 0
IPv6 ND tbl 0 0 0 0
VPN IKEv1 SA 0 0 0 0
VPN IKEv1 P2 0 0 0 0
VPN IKEv2 SA 0 0 0 0
VPN IKEv2 P2 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
SIP Session 0 0 0 0
Route Session 0 0 0 0
User-Identity 1 0 0 0
Logical Update Queue Information
Cur Max Total
Recv Q: 0 7 9940
Xmit Q: 0 30 99677Hi Ganesan,
I am proposing a design like this. You can have the STP in pvst mode and have a different priority set for the core switch to make it core a as root bridge. There is nothing wrong with your design you have made you core switch which will be physically down to your firewall... but in real it comes on the top of your firewall as well... But spanning tree conf should be done properly to achieve this... I have proposed my design which is pretty simple but easy for troubleshoot....
You can have your firewalls connected to core switch on the down and can directly connected to router on outside... always core a -->py fw--rtra will be the primary path... if anything goes wrong then secondary line will come in to picture....
make sure that your hsrp will have high priority to ur core a vlan conf for the access switches.....
Please do rate for the helpful posts.
By
Karthik -
UCS Virtual Interface Card 1280 failover
Hi,
I'm facing some issues with failover and Cisco UCS Virtual Interface Card 1280.
I found some information regarding M81KR:
Cisco UCS M81KR has fabric failover
The Cisco UCS M81KR offers fabric failover, which enables interface failover at a physical level without involving the OS or hypervisor or certification overhead.
http://www.cisco.com/en/US/prod/collateral/ps10265/ps10276/solution_overview_c22-555987_ps10280_Product_Solution_Overview.html
b) Both uplinks of one FI fail or FI fails : In this case the corresponding server links will be shut since there is no uplink available on an FI. The FI will propagate link-down status to the adapter. Once adapter link-down status occurs, it is the responsibility of the operating system to re-pin traffic to the remaining NIC/HBA. The exception here is with Palo adapter (M71KR and M81KR) which supports fabric failover.
https://supportforums.cisco.com/docs/DOC-18525
But I didn't found about Cisco UCS Virtual Interface Card 1280.
Cisco UCS Virtual Interface Card 1280 is newer than M81KR, anybody knows if 1280 has the same feature? is it possible the failover even if the Fabric Interconnect fails?
Thanks,Hi Mauricio,
The VIC 1280 has fabric failover as well, from the spec sheet:
Network architecture
Provides a redundant path to the fabric interconnect using hardware-based fabric failover
http://www.cisco.com/en/US/prod/collateral/ps10277/ps11551/data_sheet_c78-677682.html -
[SOLVED] Cannot bring wifi interface up
Hello,
A bit of a newbie here...
I've just installed archlinux on a laptop and I'm trying to get it to use a static IP on the wireless (already suceeded to get it working with a static IP on the wired network) via WEP to an access point that doesn't broadcast its ESSID.
I have set up a netctl profile which runs at boot time. Said profile seems to run correctly and I even get an IP address for the wireless. However, it doesn't seem to bring the wifi interface up and typing "ip link set <INTERFACE> up" as root seems to have no effect. I have already installed the firmware for the card and I'm not successful in getting a connection.
This is the output of the commands I've tried so far:
# ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: wlp2s3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN qlen 1000
link/ether 00:12:f0:02:47:bd brd ff:ff:ff:ff:ff:ff
inet 192.168.1.6/26 brd 192.168.1.63 scope global wlp2s3
valid_lft forever preferred_lft forever
3: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
link/ether 00:11:43:4b:d6:ec brd ff:ff:ff:ff:ff:ff
inet 192.168.1.5/26 brd 192.168.1.63 scope global enp2s0
valid_lft forever preferred_lft forever
inet6 fe80::211:43ff:fe4b:d6ec/64 scope link
valid_lft forever preferred_lft forever
# iw dev
phy#0
Interface wlp2s3
ifindex 2
wdev 0x1
addr 00:12:f0:02:47:bd
type managed
# iw dev wlp2s3 link
Not connected.
# ip link set wlp2s3 up
<this command doesn't produce any output>
# ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: wlp2s3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN qlen 1000
link/ether 00:12:f0:02:47:bd brd ff:ff:ff:ff:ff:ff
inet 192.168.1.6/26 brd 192.168.1.63 scope global wlp2s3
valid_lft forever preferred_lft forever
3: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
link/ether 00:11:43:4b:d6:ec brd ff:ff:ff:ff:ff:ff
inet 192.168.1.5/26 brd 192.168.1.63 scope global enp2s0
valid_lft forever preferred_lft forever
inet6 fe80::211:43ff:fe4b:d6ec/64 scope link
valid_lft forever preferred_lft forever
# iw dev
phy#0
Interface wlp2s3
ifindex 2
wdev 0x1
addr 00:12:f0:02:47:bd
type managed
# iw dev wlp2s3 link
Not connected.
# lspci -k
02:03.0 Network controller: Intel Corporation PRO/Wireless 2200BG [Calexico2] Network Connection (rev 05)
Subsystem: Intel Corporation Dell Latitude D600
Kernel driver in use: ipw2200
Kernel modules: ipw2200
# dmesg | grep ipw2200
[ 6.606394] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.2kmprq
[ 6.606401] ipw2200: Copyright(c) 2003-2006 Intel Corporation
[ 6.608009] ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
[ 6.854658] ipw2200: Detected geography ZZD (13 802.11bg channels, 0 802.11a channels)
# rfkill list
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
As a reference, here you have the netctl profile I created:
Description='WEP encrypted wireless connection'
Interface=wlp2s3
Connection=wireless
Security=wep
ESSID='MYNETWORKNAME'
# Prepend \" to hexadecimal keys
Key=\"01234567890ABCDEF012345678
IP=static
Address=('192.168.1.6/26')
Gateway='192.168.1.XXX'
DNS=('XXX.XXX.XXX.XXX' 'YYY.YYY.YYY.YYY')
SkipNoCarrier=yes
# Uncomment this if your ssid is hidden
Hidden=yes
# Uncomment if you are using an ad-hoc connection
#AdHoc=yes
Thanks in advance for your help/advice!!
Last edited by AMaudio (2013-11-09 21:08:35)Thanks for the pointers, Strike0. The wired-wireless failover scenario does look quite interesting. So I'd like to explore that option more extensively. I attempted to create a master bond/failover connection via netctl with two slaves: one for the wired connection and another one for the wireless connection. For the wired connection I used a netctl profile and for the wireless connection I used a systemd service manually setting up the wireless connection, somewhat following the wiki pages you refer to.
All three services start up correctly, but when I unplug the ethernet cable, the wireless network doesn't take over. It seems that it's not really connected.
Here's the details of my configuration:
The master failover (bond) netctl profile:
# cat /etc/netctl/failover
Description='A wired connection with failover to wireless'
Interface='bond0'
Connection=bond
BindsToInterfaces=('enp2s0' 'wlp2s3')
IP=static
Address="192.168.1.5/26"
Gateway='192.168.1.1'
DNS=('XXX.XXX.XXX.XXX' 'YYY.YYY.YYY.YYY')
SkipNoCarrier='no'
The failover wired netctl profile:
# cat /etc/netctl/failover_wired
Description='Failover wired network'
Interface=enp2s0
Connection=ethernet
IP=no
SkipNoCarrier=yes
## For IPv6 autoconfiguration
#IP6=stateless
## For IPv6 static address configuration
#IP6=static
#Address6=('1234:5678:9abc:def::1/64' '1234:3456::123/96')
#Routes6=('abcd::1234')
#Gateway6='1234:0:123::abcd'
The systemd service for the wireless network:
# cat /etc/systemd/system/network-wireless\@.service
[Unit]
Description=Wireless network connectivity (%i)
Wants=network.target
Before=network.target
BindsTo=sys-subsystem-net-devices-%i.device
After=sys-subsystem-net-devices-%i.device
[Service]
Type=oneshot
RemainAfterExit=yes
#EnvironmentFile=/etc/conf.d/network-wireless@%i
ExecStart=/usr/bin/ip link set dev %i up
ExecStart=/usr/bin/iwconfig wlp2s3 essid MYNETWORKNAME
ExecStart=/usr/bin/iwconfig wlp2s3 key 0123456789ABCDEF
#ExecStart=/usr/bin/ip addr add ${address}/${netmask} broadcast ${broadcast} dev %i
#ExecStart=/usr/bin/ip route add default via ${gateway}
#ExecStop=/usr/bin/ip addr flush dev %i
ExecStop=/usr/bin/ip link set dev %i down
[Install]
WantedBy=multi-user.target
After rebooting the machine, I see that all three profile/services started successfully:
# netctl status failover
[email protected] - A wired connection with failover to wireless
Loaded: loaded (/etc/systemd/system/[email protected]; enabled)
Active: active (exited) since Sat 2013-11-09 13:59:27 GMT; 34min ago
Docs: man:netctl.profile(5)
Process: 165 ExecStart=/usr/lib/network/network start %I (code=exited, status=0/SUCCESS)
Main PID: 165 (code=exited, status=0/SUCCESS)
Nov 09 13:59:24 mycomputer systemd[1]: Starting A wired connection with failover to wireless...
Nov 09 13:59:27 mycomputer network[165]: Starting network profile 'failover'...
Nov 09 13:59:27 mycomputer network[165]: RTNETLINK answers: File exists
Nov 09 13:59:27 mycomputer systemd[1]: Started A wired connection with failover to wireless.
Nov 09 13:59:28 mycomputer systemd[1]: Started A wired connection with failover to wireless.
# netctl status failover_wired
netctl@failover_wired.service - Failover wired network
Loaded: loaded (/etc/systemd/system/netctl@failover_wired.service; enabled)
Active: active (exited) since Sat 2013-11-09 13:59:27 GMT; 34min ago
Docs: man:netctl.profile(5)
Process: 163 ExecStart=/usr/lib/network/network start %I (code=exited, status=0/SUCCESS)
Main PID: 163 (code=exited, status=0/SUCCESS)
Nov 09 13:59:24 mycomputer systemd[1]: Starting Failover wired network...
Nov 09 13:59:27 mycomputer systemd[1]: Started Failover wired network.
Nov 09 13:59:28 mycomputer systemd[1]: Started Failover wired network.
# systemctl status [email protected]
[email protected] - Wireless network connectivity (wlp2s3)
Loaded: loaded (/etc/systemd/system/[email protected]; enabled)
Active: active (exited) since Sat 2013-11-09 13:59:25 GMT; 36min ago
Process: 177 ExecStart=/usr/bin/iwconfig wlp2s3 key 12345667890ABCDEF (code=exited, status=0/SUCCESS)
Process: 175 ExecStart=/usr/bin/iwconfig wlp2s3 essid MYNETWORKNAME (code=exited, status=0/SUCCESS)
Process: 164 ExecStart=/usr/bin/ip link set dev %i up (code=exited, status=0/SUCCESS)
Main PID: 177 (code=exited, status=0/SUCCESS)
Nov 09 13:59:24 mycomputer systemd[1]: Starting Wireless network connectivity (wlp2s3)...
Nov 09 13:59:27 mycomputer systemd[1]: Started Wireless network connectivity (wlp2s3).
This is the output from ip addr show, which as far as I can tell, it's all correct:
# ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp2s0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP qlen 1000
link/ether 00:11:43:4b:d6:ec brd ff:ff:ff:ff:ff:ff
3: wlp2s3: <NO-CARRIER,BROADCAST,MULTICAST,SLAVE,UP> mtu 1500 qdisc pfifo_fast master bond0 state DOWN qlen 1000
link/ether 00:11:43:4b:d6:ec brd ff:ff:ff:ff:ff:ff
4: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
link/ether 00:11:43:4b:d6:ec brd ff:ff:ff:ff:ff:ff
inet 192.168.1.5/26 brd 192.168.1.63 scope global bond0
valid_lft forever preferred_lft forever
inet6 fe80::211:43ff:fe4b:d6ec/64 scope link
valid_lft forever preferred_lft forever
And here's the output from iwconfig. Notice that it says "Access point: not-associated"
# iwconfig
wlp2s3 IEEE 802.11bg ESSID:"MYNETWORKNAME"
Mode:Managed Channel:0 Access Point: Not-Associated
Bit Rate:0 kb/s Tx-Power=20 dBm Sensitivity=8/0
Retry limit:7 RTS thr:off Fragment thr:off
Encryption key:900A-0B0D-4B57-C007-1F5D-5C63-79 Security mode:open
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
lo no wireless extensions.
enp2s0 no wireless extensions.
bond0 no wireless extensions. -
Integration Repository Interfaces - Documentation??
I'm looking for an on-line source for the integration respository interfaces - similar to the now deprecated Interface Repository (IFR)(http://ifr.sap.com).
In particular, I'm looking for the WSDL/XML and Java Proxy interfaces for the following BAPIs.
- BAPI_CUSTOMER_GETDETAIL or BAPI_CUSTOMER_GETDETAIL1
- BAPI_CUSTOMER_CHANGEFROMDATA
- BAPI_SALESORDER_GETSTATUS
- BAPI_SALESORDER_CHANGE
Does anybody know if those interfaces are available online anyplace?
Thanks,
MarkGregor,
Thanks. That is what I was looking for. Unfortunately, it seems to be password protected.
I'm trying to view the StandardSalesOrderChangeRequestResponse service here -> https://www.sdn.sap.com/irj/sdn/esapreviewsystem and when I select "Inbound Interface WSDL" or "Inbound Interface Documentation", I get hit with a logon screen.
Ny SDN username/pwd doesn't work. Is there a guest username/pwd that can be used?
-- Mark -
Logical host states deprecated
Why does my logical host show deprecated when looking at 'ifconfig -a' output.
I snoop the logical host and it seems to be recieving the traffic it's supposed to recieve.
I read somewhere that this may mean that the public network interface is not to be used, all traffic must go
through the logical host.
Any ideas???That's normally used with IPMP for interfaces that do the monitoring of the link.
# man ifconfig
deprecated
Marks the logical interface as deprecated. An address
associated with a deprecated interface will not be used
as source address for outbound packets unless either
there are no other addresses available on the interface
or the application has bound to this address explicitly.
The status display shows DEPRECATED as part of flags.
See INTERFACE FLAGS for information on the flags
supported by ifconfig.--
Darren -
Active/Standby And failover link configuration mode
Hi everyone,
When config failover link of ASA in Active Standby mode.
When we config failover int say gi0/1
config t
int gi0/1
failover lan int gi0/1
Need to confirm we do this from interface config mode only or we can do this from global config also ????????
Whe we assign IP to this int we do that from global config mode ????
Regards
Mahesh
Message was edited by: mahesh parmar
Message was edited by: mahesh parmarHi,
Actually the ASA lets you insert a lot of command what ever mode you are under.
In the output you posted is a very important thing to notice
configure mode commands/options:
WORD Specify the interface name
As you can see, the output lists only one option and before that it mentions that this is a "configure mode" command
So even if you entered the command under the interface configuration mode, it would still be entered as a global/configure command mode.
Take the following thing for example
I want to check what configuration options I have with the command "failover"
So I enter the following to my ASA
ASA(config)# failover ?
configure mode commands/options:
interface Configure the IP address to be used for failover and/or
stateful update information
interface-policy Set the policy for failover due to interface failures
key Configure the failover shared secret or key
lan Specify the unit as primary or secondary or configure the
interface and vlan to be used for failover communication
mac Specify the virtual mac address for a dynamic interface
polltime Configure failover poll interval
timeout Specify the failover reconnect timeout value for
asymmetrically routed sessions
exec mode commands/options:
active Make this system to be the active unit of the failover pair
exec Execute command on the designated unit
reload-standby Force standby unit to reboot
reset Force a unit or failover group to an unfailed state
As you can see, the ASA tells us that there are different additional command parameters after the "failover" command that can be used. Some of them can be used either in Exec or Configuration mode.
- Jouni -
Cisco call manager Network Failover Configuration
Hi all,
I have a cisco call manager 6.0.
The server is configured and is functioning very well.
Only today I realized that the server MCS has two NIC and there is the possibility to configure a networ failover by cli interface.
Now the question are:
is it possible to configure this function now without problem?
if yes what are the ordered steps to follow?
Thanks all.Hi
you can use EtherChannel, 2 phisical ports as 1 logical -
Hello,
On an ASA 5520 active, standby pair, what will result if the failover link or interface goes down or fails. Will both devices become active?
If yes, how to prevent this. We want it in such a way that if such a situation happens, there should be only Active and the other one should be standby.
Thanks in advance!If ASA units connected with cross over then no failover will take place.
if using LAN based failover then you will end up with Active-Active and traffic will fail.
Thanks
Ajay
Maybe you are looking for
-
I'm looking for a way I can set my Mac up so that there are two modes - one for when I'm at work, or at home, and one for when I am out and about / working remotely. The modes would be: A: the screensaver does not come on for 20-30 minutes, and when
-
I lost my seriel number for PS Elements 11 following computer crash. Os is W7 Peter Jones Aug 27, 2014 5:36 AM Hi, I lost my serial number for PS Elements 11 following computer crash. Os is W7. I have the cd installation disc but there is no seria
-
TS4062 Syncing with a new network/router
I am having trouble on syncing on a new WIFI network. I moved and I have a new router with a new network name. Since that I cannot sync over wifi. On syncing options on the ipod says that I will be able to sync via wifi when "old network" is availabl
-
could someone please provide a sample code of how to upload a text "|" delimited file into SAP internal structure? i used GUI_upload with field_separator but didn't work. many thanks.
-
I will have an AirPort Extreme 5th gen in a few days.....
I will have an AirPort Extreme 5th gen in a few days. I have an older model and when playing with settings, I found out that my Epson wireless printer can only see 2.4 ghz 802.11n networks..... but I want to use the 5Ghz wireless.....is there anyway