DLSW Ethernet Redundancy timers

Hi,
I am running DLSW Ethernet redundancy on 2 x 7204 VXR routers. The one acts as the master for the odd VLAN's and the other as the master for the even VLAN's. The 7204's connect to 2 x 6509 switches via ISL trunking.
The problem I have is that if I disable DLSw on one of the 7204's, it takes quite a long time for the worksession stations to re-establish their sessions.
Any help welcome..
Dean Young.
T-systems South Africa
[email protected]

Thanks. I did change the parameter, but it did not make any difference.
I am running PCOMMS 5.0.
What I found was the following:
I connect to the mainframe via 7204_1 and then disable DLSW on this router. It takes exactly 1minute and 25 seconds for my session to be re-established via the backup 7204.
I was wondering if there is a timer that will speed up this process. It seems as if the source and destination MAC binding has to be released and then setup via the backup 7204.
Regards
Dean

Similar Messages

DLSW Ethernet Redundancy Transparent Cache

I have corrupt entries in the ethernet redundancy transparent cache. These are causing problems establishing new sessions.
Can I clear the entries individually and how long does the cache take to time out?

Hi,
the "dlsw clear transparent circuit" was introduced with CSCdv16277, it is in ios 12.1(11.5) and higher, 12.2(6.4) and higher and it also rolled into 12.3.
Please note the "circuit" option is hidden. you can not see it with the ? asking for help in the parser.
in respect to the origin of the erroneous cache entries. They can be a bug on itself. But they also can be a result of a configuration not exactly like it should be.
I would advice to open a case with the tac and have the configurations sanity checked.
If this is something you can reproduce at will than we would certainly be very interested how you get into this state.
Dlsw ethernet redundancy was quite modified a bit in the last 2 years. Depending on what version of code you run you might need to go to a higher level to pick up all the current maintenance.
My personal few is a recent 12.2 image or even better a recent 12.3 image.
thanks...
Matthias

DLSW ethernet redundancy for multiple vlans

Can dlsw ethernet redundancy support mutliple vlans with the following configuration?
host dlsw router1 host dlsw router2
| |
local dlsw router 1 local dlsw router2
| |
ethernet switch1-------ethernet switch2
Ethernet switch1 and 2 are supporting multiple vlans and connected to local dlsw router1 and 2 through 802.1Q. SNA support is required for the vlans of ethernet switch1 and 2 .
We found that configuration of dlsw ethernet redundancy is not allowed on the 802.1Q sub-interface of the local dlsw router1 and 2. In this case, how can dlsw ethernet redundancy can be supported for SNA server attached to multiple vlans? Can you provide us some reference / sample for dlsw ethernet redundancy to support SNA servers attached to different vlans in a switch environment.
Thanks.

I think that I understand the problem. I am thinking the following:
dlsw local-peer peer-id 2.2.2.2 promiscuous
dlsw transparent switch-support
interface Ethernet0
mac-address 0000.3333.3333
dlsw transparent redundancy-enable 9999.9999.9999 master-priority 10
dlsw transparent map local-mac 0000.6666.0000 remote-mac 0200.eca2.0000 neighbor 0000.5555.5555
interface Ethernet1
mac-address 0000.4444.4444
dlsw transparent redundancy-enable 9999.9999.0001 master-priority 10
dlsw transparent map local-mac 0000.6666.0001 remote-mac 0200.eca2.0000 neighbor 0000.7777.7777
Of course, you need an ethernet interface per VLAN. If you need DLSw ER over dot1q interface, please contact the local Cisco Sales Rep or partner. You are not the first one to ask for it. Hope that there is a strong business case to initiate the new feature.

DLSW Ethernet Redundancy

Hi,
When configuring DLSW for ER using the global commands (transparent switch-support) and the interface commands (mac-address, transparent redundancy-enable and transparent map)
are the traditional DLSW ethernet commands (dlsw bridge-group) still necessary or not ?
If not why ? Does the ER implicit contains this commands ?
Thnx
Omar

No, the traditional bridge commands are not applicable. In fact, once you enable DLSW ER, you will not be able to enable the traditional bridge-group commands. The ER takes care of receiving the packets into the DLSW process.

DLSW Ethernet Redundancy - Master/Slave preemptive

I am wondering if there is a way to control the behavior of the master dlsw router if it fails and circuits are established on the slave dlsw router. The lab testing I have done shows that once the master dlsw router is back online, the circuits teardown from the slave dlsw router and re-establish on the master dlsw router.
Is there a way to control this behavior so that additional LLC disruptions are avoided when the master router comes online?

I don't think there is a way to control this behavior

DLSw - MSFC - Redundancy

Do all the same rules apply when doing Dlsw redundancy with backup msfc's? For example, do I need the following types of commands:
dlsw transparent redundancy-enable xxxx master-priority x
and
dlsw transparent map local-mac xxxx remote-mac xxxx neighbor xxxx
and
dlsw transparent switch-support

Yes.
You may want to look into Single Router Mode (SRM) at http://www.cisco.com/univercd/cc/td/doc/product/lan/cat6000/sw_6_3/confg_gd/redund.htm for your MSFC redundancy. You lose MSFC load balancing but simplify the configuration greatly since you don't need to use HSRP or DLSw Transparent Redundancy.
hope this helps
tim

Eth. T/R DLSw w/ Redundancy

I have an ethernet segment and a Token Ring segment.
I have 2 routers connecting to both the Ethernet and the Token Ring. Both routers have a serial interface. I'm attempting to have dlsw redundancy for both Ethernet and Token Ring.
I noticed that when I 'Ping' from Ethernet to T/R, I get duplicate responses. I've been forced to disable redundancy for DLSw on the Token Ring. Is there any reason this might happen?
Any help will be greatly appreciated.

You may have a routing or bridging loop. It's difficult to troubleshoot on this type of message board. I'd suggest you open a case with the TAC and request some design help and configuration review. That way you can describe your specific situation and include diagrams of your network.

DLSw redundancy problem

| |
****** ******** | |
* *--CPA1--*7206-1*--| ******** |
*IBM * ******** |--*7206-3*--|
* * | ******** |
*HOST* | |
* * ******** |--******** |
* *--CPA2--*7206-2*--| *7206-4*--|
****** ******** | ******** |
| |
7206-1 and 7206-2 manage the the connection to the IBM host with a CPA card eich other.
7206-3 and 7206-4 manage the connection between the central site and the remotes sites via frame-relay network, they are border peer and DLSw load balancing coded. also manage the connection between a LAN of the central site and with bridge-group to reach an IBM HOST via 7206-1 and 7206-2.
The following is the configurations:
7206-3:
dlsw local-peer peer-id 3.3.3.3 group 3 border keepalive 0 promiscuous
dlsw load-balance round-robin
dlsw remote-peer 0 tcp 1.1.1.1 timeout 90
dlsw remote-peer 0 tcp 2.2.2.2 timeout 90
dlsw cache-ignore-netbios-datagram
dlsw bridge-group 1
7206-4:
dlsw local-peer peer-id 4.4.4.4 group 3 border keepalive 0 promiscuous
dlsw load-balance round-robin
dlsw remote-peer 0 tcp 1.1.1.1 timeout 90
dlsw remote-peer 0 tcp 2.2.2.2 timeout 90
dlsw cache-ignore-netbios-datagram
dlsw bridge-group 1
The probleme is:
In the central site, i see a slowness in the connection, and it is random, sometime a connction is very fast, other time it is very slow, and it can take up to 1,5 minute to connect.
After all that, i coded a dlsw redundancy in the 7206-3 and 7206-4 FastEthernets, the problem still exist in the LAN, and it cause a trouble in some remotes sites connected with frame-relay, that loose a connection to HOST.
Thank You for your help.

1. To make load balancing work you will have to add the following commands:
dlsw timer explorer-wait-time ...
source-bridge ring-group ...
Ring-group number must be the same on 7206-3 & 7206-4 - it prevents unnecessary explorer flooding.
2. If bridge-group 1 on 7206-3 & 7206-4 shares the same Ethernet domain you must use DLSw+ Ethernet Redundancy feature.
3. Border peers in the same group must be in full-mesh and all members in the group must peers with all border peers in this group. On 7206-3 & 7206-4 you will have to add the following commands:
(7206-3)# dlsw remote-peer 0 tcp 4.4.4.4 ...
(7206-4)# dlsw remote-peer 0 tcp 3.3.3.3 ...

DLSw question

Dear all,
Could anyone help me to clarify the following point on DLSw redundancy?
Is it true if DLSw redundancy (or recover) are transparent to user if the end stations lie on a token ring network ? On the other hand if the end stations lie on the ethernet LAN, the DLSw can re-established itself but it is not transparent to user. Can I make such a conclusion ?
thanks

Hi,
no, this statement is not true.
From an end systems perspective the recovery is always disruptive. No matter if you are on a tokenring or on a ethernet lan.
That means:
DLSw is about llc2 sessions at layer2. If your lan attached end system has a llc2 session with a cisco dlsw router and i.e. that router fails, the llc2 session with the end system will fail aswell.
After the end system has realized that the llc2 session is gone it cleans up its local connections and then tries to reestablish the llc2 connection. If another dlsw router is available, who can reach the requested remote host, than this connection will come up again. That means the end user sna session goes down and comes back up again.
The same is true if you are talking about dlsw+ ethernet redundancy.
There is more in the details/differences between ethernet and tokenring lan segments. I.e. on a tokenring you have a rif in each packet which can be used for loop control.
On ethernet you almost always have ethernet switches, where a cam table of a ethernet switch in any vlan for any mac address can only point to exactly one port on the switch.
If you have two dlsw routers connected that can reach the same remote host those two routers will both send frames with the same host mac address into the same switch on two different ports. This is where dlsw ethernet redundancy feature comes into play.
thanks...
Matthias

Design question about SNASw, DLSW and VDLC

Hello,
I have a question about Ethernet redundancy in an APPN environment.
Let's have an example with 3 routers running SNASw that are on the SAME LAN (no vlans) as the Mainframe's OSA (one OSA only). APPN is configured on the Mainframe.
Using DLSw+, all downstream PUs are connected to the 3 routers. Can I define in the VDLC interface of each router the SAME MAC address, and this MAC address be the destination MAC of the downstream PUs?

Hi,
yes, headend routers are the ones in front of the OSA/mainframe.
If you replace a tokenring with ethernet in the data center/headend, than the snasw dlsw solution is almost perfect for you. If you use hpr/ip to connect upstream to the host you are all set.
In that case you dont advertise any mac addresses on the local ethernet between the snasw/dlsw routers and the osa since it is hpr/ip. Basicaly ip routing only.
From the clients perspective, they dont really know that there is a change since you replicate the old tokenring mac address as vdlc mac address/snasw port and the end systems still connect to them like they did before.
In respect to dlsw ethernet redundancy we have to be a bit carefull not to mix the scenarios.
Dlsw ethernet redundancy is designed for the branch. Not the data center.
If you use dlsw ethernet redundancy with ethernet switches, and in almost all cases today ethernet means ethernet switches, you configure a mac address mapping between artificiall local mac addresses and your real remote mac address of the host.
On each router you configure a unique local mac address. Than you point half of your end systems dmac to the local mac address configured on router1 and the other half to the local mac address configured on router2. That way you achive load balancing.
The two routers exchange their mapping and in case router1 looses the connection to router2, router1 will activate the mapping it learned from router2 aswell and then take over those circuits additional.
If you decide that you configure on router1 the local mac address equal to the remote mac address, because you have a large number of clients and can not simply change the damc's on all of them, than you need to configure a "dummy" mapping on router2 and router1 will get all the circuits in this example. router2 would be purely for redundancy in case router1 goes down.
If you think about this than it is clear why dlsw ethernet redundancy is designed for the branch. In the branch we map local to remote mac addresses and the remote mac addresses are the hosts. Typically there are only a limited number of host mac addresses to map.
If you turn this around and put dlsw ethernet redundancy on the host end than you have to map all clients. If you have only one or two clients this is certainly doable. But if you have a large nuber of clients this is simply not manageable.
thanks...
Matthias

DLSw+ Eth. Redundancy

Can you give me an example of a 'Multicast MAC Address' other than 9999.9999.9999?
I'm not exactly sure how to determine Multicast
MAC Addresses.
Thank You.

A layer 2 multicast MAC address in Ethernet 802.3 format means that bit 0 (the least significant bit) of the first octet is set on to indicate a multicast frame. A layer 2 multicast MAC address in Token Ring 802.5 format means that the most significant bit of the first octet is on. So long as you use a layer 2 multicast MAC address for the dlsw transparent redundancy-enable configuration command DLSw+ ER will work fine. MAC address 9999.9999.9999 is normally used since the MAC address would be same in both cannonical and non-connonical format (ie., bitswapped).

DLSW drop sporadically

Setup
6509 (IOS 12.1(13)E6) running standard DLSW ( i.e. non ethernet redundancy)over FastEthernet to 7513 (12.1(14)) connected to Mainframe over CIP2/IBM Channel.
1.
Our PC running LU6.2 over ethernet connected to the 6509 spordic loose thier connection due to the DLSW peer drops. (on the DLSW peer there is max 100 circuits)
2.
The 6509 have orther DSLW peers that run to other routers that are unaffected by the dropping peer.
3.
Likewise the 7513 that is the peer for the dropping DLSW connection has other peers that are unaffected.
4.
On a DLSW debug I see that the drop is caused due to failed DLSW keepalives.
5. As I found the CSCdw58350 I would appreciate some details how to determine if its the CSCdw58350 thats causing my problems ?? Or any other suggestions for the cause - thanks.
Regards
Gert Schaarup

Thanks
1. I will go for the IOS upgrade, but do I need to upgrade both ends of the dlsw peer ? (i.e. the 7513 with the CIP and the 6500 with the LU6.2 workstations)
2. After we moved some of the LU6.2 client to Token Ring (i.e. direct SNA to the host) the dlsw peer seems to stay up but we still see that dlsw circuits gets disconnected and shortly after reconnect without direct loss of LU6.2 data.
3. I do see some few half flow op and reset (like Half: 6/2 Reset 1/0) but could you please comment following output (taken 4 and 9 July when the peer is up, as the peer hasnt gone done since we moved some of the load) to see if these confirm that it is the bug that is the problem. - Thanks
07:54:01.231 PDT Fri Jul 4 2003
At the 7513 end:
CIP-Slot4#llc stat all
Maximum connections = 1200
Highest connections = 169
Current connections = 59
Connections rejected = 0
Connect requests = 5615
Connect responses = 0
Connect confirms = 5615
Connect indications = 0
Disconnect confirms = 207
Disconnect indications = 5128
Flow off terminated conn = 0
Session timeouts = 99
FRMRs sent = 1
FRMRs received = 1
SABMEs sent = 5632
SABMEs received = 0
DISCs sent = 542
DISCs received = 5027
UAs sent = 5027
UAs received = 5811
DMs sent = 0
DMs received = 10
IDLE connections = 0
Connection thresheld = 1200
Frames transmitted = 130903182
Transmit completes = 130903182
Frames received = 124105764
Flow offs sent = 43844
Flow ons sent = 43810
Flows (on/off) cancel = 180
Flow offs received = 0
Flow ons received = 0
CCB indications sent = 92883
CCB indications freed = 92883
Unexpected events = 36
Ack Timer Missed = 0
Frames ignored = 4
Data requests = 101195500
Data requests freed = 101193980
Aggregate data req qlen = 0
Maximum data req qlen = 0
Data indications = 87183015
Data indications freed = 87183015
Aggregate data ind qlen = -1457917659
Maximum data ind qlen = 87183015
Polls sent = 152722
Finals sent = 18591962
Polls rcvd = 18625036
Finals rcvd = 158403
RR polls sent = 152722
RNR polls sent = 0
REJ_polls sent = 0
RRs sent = 29607348
RRs received = 36878480
RNRs sent = 80011
RNR received = 27452
REJs sent = 1487
REJs received = 4178
Bad PDUs received = 0
Bad N(r)s received = 5
Bad N(s)s received = 1747
Out-of-seq N(s)s received = 38
Acknowledgements delayed = 81673676
Iframes transmitted = 101203134
Iframes retransmitted = 9115
Retries = 7507
Local busy entered = 96226
Local busy exited = 96226
Remote busy entered = 9737
Remote busy exited = 9429
Unexpec Ack = 0
Adapter registered = 4
SAPs registered = 1
CEPs registered = 59
Msgs to entity mgr = 31
Msgs to PSAP = 58712
Msgs to PCEP = 101206483
Msgs to DLU = 87346909
Invalid handles = 0
SAPs activated = 8
Deactivate SAP requests = 5
Deactivate SAP confirms = 5
SAPs reset by user = 2
SAPs reset by network = 0
SAP deact/reset completed = 7
SAPs deact/reset w/ CCBs = 2
SAPs frame drops = 0
Hash buckets used = 3439
Hash table collisions = 2181
Hash table lookups = 124174704
Hash table caparisons = 198849566
Hash table lookups failed = 58305
Longest collistion chain = 19
Receive erroneous frame = 0
DMA write operations = 130999946
DMA write completions = 130999946
DMA write errors = 0
DMA write waits = 0
DMA read notifications = 124534436
DMA read operations = 124534436
DMA read completions = 124534435
DMA read errors = 0
DMA reads discarded = 0
DMA reads discarded small = 0
DMA read chains freed = 0
Frames exceed MAX frameSZ = 0
Timer ticks (100ms) = 222075154
Timeouts = 6502680
Timers started = 275098246
Timers stopped = 268595506
T1 timers expired = 7607
Idle timers expired = 91521
T2 timers expired = 6403552
Longest timeout chain = 58
P/F timer started = 163700
P/F timer stopped = 158403
Ack timer started = 66234646
Ack timer stopped = 58411329
Busy timer started = 13354
Idle timer started = 145383718
T2 timer started = 63301341
T2 timer stopped = 63301340
Reject timer started = 1487
Reject timer stopped = 1589
LLC Stack locked = 363336715
LLC Stack delayed events = 101
LLC stack pending events = 0
LLC stack most pndng evnts= 1
LLC stack not locked.
15:17:44.199 PDT Wed Jul 9 2003
At the 7513 end:
CIP-Slot4#llc stat all
Maximum connections = 1200
Highest connections = 169
Current connections = 69
Connections rejected = 0
Connect requests = 10778
Connect responses = 0
Connect confirms = 10778
Connect indications = 0
Disconnect confirms = 301
Disconnect indications = 10216
Flow off terminated conn = 0
Session timeouts = 118
FRMRs sent = 1
FRMRs received = 1
SABMEs sent = 10815
SABMEs received = 0
DISCs sent = 628
DISCs received = 10096
UAs sent = 10096
UAs received = 11037
DMs sent = 0
DMs received = 12
IDLE connections = 0
Connection thresheld = 1200
Frames transmitted = 153147701
Transmit completes = 153147701
Frames received = 146574711
Flow offs sent = 52506
Flow ons sent = 52472
Flows (on/off) cancel = 198
Flow offs received = 0
Flow ons received = 0
CCB indications sent = 115314
CCB indications freed = 115314
Unexpected events = 103
Ack Timer Missed = 0
Frames ignored = 4
Data requests = 119159228
Data requests freed = 119157594
Aggregate data req qlen = 0
Maximum data req qlen = 0
Data indications = 102290655
Data indications freed = 102290655
Aggregate data ind qlen = -2074303823
Maximum data ind qlen = 102290655
Polls sent = 182235
Finals sent = 21206449
Polls rcvd = 21242583
Finals rcvd = 193195
RR polls sent = 182235
RNR polls sent = 0
REJ_polls sent = 0
RRs sent = 33862716
RRs received = 44225534
RNRs sent = 93378
RNR received = 30175
REJs sent = 2075
REJs received = 4686
Bad PDUs received = 0
Bad N(r)s received = 5
Bad N(s)s received = 2441
Out-of-seq N(s)s received = 69
Acknowledgements delayed = 95797452
Iframes transmitted = 119167992
Iframes retransmitted = 10275
Retries = 7696
Local busy entered = 108966
Local busy exited = 108966
Remote busy entered = 11023
Remote busy exited = 10715
Unexpec Ack = 0
Adapter registered = 4
SAPs registered = 1
CEPs registered = 69
Msgs to entity mgr = 35
Msgs to PSAP = 85729
Msgs to PCEP = 119180620
Msgs to DLU = 102514497
Invalid handles = 0
SAPs activated = 9
Deactivate SAP requests = 6
Deactivate SAP confirms = 6
SAPs reset by user = 2
SAPs reset by network = 0
SAP deact/reset completed = 8
SAPs deact/reset w/ CCBs = 2
SAPs frame drops = 0
Hash buckets used = 8529
Hash table collisions = 2283
Hash table lookups = 146676148
Hash table caparisons = 224807587
Hash table lookups failed = 80517
Longest collistion chain = 19
Receive erroneous frame = 0
DMA write operations = 153281642
DMA write completions = 153281642
DMA write errors = 0
DMA write waits = 0
DMA read notifications = 147050284
DMA read operations = 147050284
DMA read completions = 147050284
DMA read errors = 0
DMA reads discarded = 0
DMA reads discarded small = 0
DMA read chains freed = 0
Frames exceed MAX frameSZ = 0
Timer ticks (100ms) = 226558498
Timeouts = 7361429
Timers started = 324359028
Timers stopped = 316997530
T1 timers expired = 7815
Idle timers expired = 109334
T2 timers expired = 7244280
Longest timeout chain = 58
P/F timer started = 203551
P/F timer stopped = 193195
Ack timer started = 78970086
Ack timer stopped = 68892536
Busy timer started = 14376
Idle timer started = 170688653
T2 timer started = 74480287
T2 timer stopped = 74480287
Reject timer started = 2075
Reject timer stopped = 2229
LLC Stack locked = 426985053
LLC Stack delayed events = 120
LLC stack pending events = 0
LLC stack most pndng evnts= 1
LLC stack not locked.

WS-X6066-SLB-K9-S Redundancy

Hello;
In our topology we try to use two csm-s module on different 6509 chasis. In our network we use hsrp configuration, so csm-s module's running as active-passive.
According to cisco documents, we couldnt be able to pass clients vlan on load balancer configuration between two chasis trunks port. Also according to same documents we configured fault tolerance vlan on 6500 switches.
But for server ethernet redundancy we configured teaming ethernet interface on the servers and finalized on different 6500 switches. So when the ethernet port on active backbone is plug off, because of trunk port vlan restiriction , we couldnt reach servers behind load balancer.
We want to know if there is another solution for this csm-s configuration. Could we use active-active envionment ?
Must we exclude client vlans on load balancer configuration on trunks port between two 6500 chasis ?
Best regards
Umut.

Hi,
Here is a basic configuration for SSL Termination with a CSM-S
vlan 112 client
ip address 10.198.16.78 255.255.255.192
gateway 10.198.16.77
natpool HTTPS 10.198.16.106 10.198.16.106 netmask 255.255.255.192
vserver TEST
virtual 10.198.16.124 tcp https
serverfarm SSL
persistent rebalance
inservice
serverfarm SSL
no nat server
no nat client
real 10.198.16.79 local
inservice
ssl-proxy vlan 112
ipaddr 10.198.16.79 255.255.255.192
gateway 10.198.16.78
admin
ssl-proxy service test
virtual ipaddr 10.198.16.124 protocol tcp port 443 secondary
server ipaddr 10.198.16.116 protocol tcp port 80
certificate rsa general-purpose trustpoint Digi-Int
inservice
vserver TEST2
virtual 10.198.16.116 tcp www
serverfarm TEST
persistent rebalance
inservice
serverfarm TEST
nat server
nat client HTTPS
real 10.198.16.92
inservice

Will or can DLSW talk SNA over DIX/EthernetII?

Hi. I have a device that can talk SNA only over the DIX/Ethernet2 frame format. For this reason, it cannot communicate via Ethernet transparent bridging with our mainframe OSA Express, which requires SNA to ride the 802.3/802.2 Ethernet frame format.
My intention has been to try to resolve this by configuring DLSW (Ethernet-to-Ethernet) between two routers placed between these non-communicating devices. The hope is that DLSW will use the required 802.3 frame format to communicate on one side with the mainframe (which of course does work) and use the DIX Ethernet frame format to communicate on the other side (separate router) with the device that requires SNA to use DIX.
There is a command for this purpose, source-bridge enable-80d5, but I don't know if that command has any effect Ethernet-to-Ethernet, transparent bridging only. Without it, over Ethernet, is DLSW "smart enough" to use the frame format required by the end host?
Thank you.

source-bridge enable-80d5 is local significant. It does not know the interface type of the remote dlsw router. In other words, the router with source-bridge enable-80d5 configured (say Router_a) understands DIX frames. The Router_a converts the DIX frames into information required by DLSw SSP protocol (i.e. SSAP, DSAP, MAC addresses and so on). Router_a has no idea how the remote DLSw router use the information.
Similarly, Router_a converts a DLSw frame into DIX frames. The remote DLSw router has no idea that Router_a is using DIX frame format.

SNA Load Balancing

Hello:
i have a issue about load balancing adn redundance in Routers working with SNA DLsw.
in one router i have a master and the other is slave.
MASTER:
dlsw transparent redundancy-enable 9999.9999.9999 master-priority 10
SLAVE:
dlsw transparent redundancy-enable 9999.9999.9999
If i want to make redundance in the master, do i have to put the redundancy-enable command in the second port? for example
MASTER:
int e0
dlsw transparent redundancy-enable 9999.9999.9999 master-priority 10
int e1
dlsw transparent redundancy-enable 9999.9999.9999 master-priority 10
is this configuration right, does anybody knows something about this?
Regards

Answer to my question: http://ieoc.com/forums/p/26385/218976.aspx#218976

DLSW Ethernet Redundancy timers

Similar Messages

Maybe you are looking for