DLSW - Transparent Bridging via FE Subinterfaces?

Hi. I have a 7206 router connected with FE to a Catalyst 6509, via 802.1Q trunking. Two VLANs. The router supports DLSW to remote sites, and the switch transports SNA traffic to the router with transparent bridging through one of the FE subinterfaces.
What I'd like to do is establish DLSW peering between the router and another device on the local LAN -- in other words, also through the FE interface connected to the 6509. I don't have another physical FE interface on the router. Two questions:
1) Is there any reason I would run into difficulty setting up another VLAN on the switch and another FE subinterface in the router, and using the new VLAN/subinterface for DLSW, while keeping the other subinterface configured to use transparent bridging?
2) In that configuration, might there be any issue transporting SNA into and out of the router via the one FE subinterface configured with a bridge group and the other FE subinterface being used for the DLSW path? That is, I will need the router to decapsulate the SNA coming in via DSLW on one subinterface, and bridge it out the other subinterface, and vice-versa.
Thanks for any guidance.

I'm not sure how well I managed to explain the scenario in the previous post. An attempt to clarify:
VLAN1 -\ FE.Subinterface1
[6509] VLAN2 --> <=-802.1Q-=> FE.Subinterface2 [7206]
VLAN3 -/ FE.Subinterface3
6509
VLAN 1: bridge group 1
VLAN 2: bridge group 1
VLAN 3: L2-only VLAN (no definition in the MSFC). Used only to transport DLSW (and other IP) traffic to and from a router also running DLSW to FE.Subinterface3 on the 7206 through the 802.1Q trunk.
7206
FE.Subinterface1: bridge-group 1
FE.Subinterface2: bridge-group 1 (blocked by STP)
FE.Subinterface3: not in a bridge group. The interface through which the 7206 communicates with an internal router running DLSW (transporting SNA for a device directly connected to that internal router).
Traffic path
SNA must travel between the device the 7206 is DLSW peering with through FE.Subinterface3, and a device (a mainframe OSA Express interface) the 7206's SNA traffic can reach via transparent bridging through FE.Subinterface1.
The "steps": the 7206 uses FE.Subinterface3 to receive DLSW TCP/IP-encapsulated SNA traffic from the other DLSW router. The SNA traffic gets decapsulated in the 7206, and is bridged to the mainframe OSA Express interface via FE.Subinterface1. And of course the reverse, from the mainframe, transparently bridged into the 7206 through FE.Subinterface1 and sent via DLSW through FE.Subinterface3.
Do-able? Thanks!

Similar Messages

Is it possible for SA540 to work in transparent bridge mode?

Hi all,
I've been considering to use a Cisco SA540 in an industrial project; please consider Scenario 1 and 2 files attached (bear with me - I'm an engineer, not an artist).
All networks mentioned in both scenarios are regular and well known Ethernet TCP/IP networks. The Corporate Network and Automation Network (including the DMZ) are in different subnets. The Corporate Network is the biggest one, similar to any company's corporate network you all know. The Automation Network exists for the purpose of operating and maintaining the industry process; it's smaller but highly critical. Only specific staff (automation staff and dedicated operators) have access to it. Although many devices and networks in the Automation Network are industry specific - not so well known, a small segment of it is plain Ethernet TCP/IP, as I've already stated. The Automation Network has a DMZ, where we lay servers that provide industry process information for the Corporate Network.
Scenario 2 may look at a first glance the best option, since it's simpler, doesn't require another router and benefits from Cisco SA540 support for both a LAN and a DMZ. The problem with Scenario 2 is the following:
Since both networks are maintained by different teams under different management, TI staff would have absolute control over the Cisco SA540. This way automation staff could not grant that the Automation Network is really protected from the Corporate Network.
TI staff may even demand for another device to interface with the Automation Network - which is not Cisco SA540, since they rule everything that lives in the Corporate Network. In this case, I have my hands tied!
Scenario 1 solves the above problems. Since automation would have absolute control over the Cisco SA540, they could grant security for the Automation Network (except for DMZ, but that's the reason why it is called a DMZ!). TI staff could ask for any router they prefer to interface with the DMZ, I would never mind about it.
Considering the above, I will probably be forced to adopt Scenario 1 instead of Scenario 2. So here comes my question: is it possible for Cisco SA540 to work with the same subnet for both WAN and LAN interfaces (in Scenario 1, no DMZ interface is required)? In other words, is it possible for Cisco SA540 to work in transparent bridge mode? I've been through all of the Cisco SA540 Administration Manual and as far as I could understand, routing is not an option - it is demanding.
Although I understand I could adopt Scenario 1 and still have different subnets for DMZ and the rest of the Automation Network by connecting the DMZ to the WAN interface and the rest of the Automation Network to the LAN interface in the Cisco SA540, I believe it's not worth the effort. The Automation Network is so small and we do all we can to keep it as simple as possible.

Adriano, there is a RV042G, which supports the gig ports and a 800 mbps nat throughput. Here is the datasheet
http://www.cisco.com/en/US/prod/collateral/routers/ps10907/ps9923/ps12262/data_sheet_c78-706724.html
If you are using a DSL connection, the SRP527/547 models may be an alternative. These models support the RFC 1483 Bridges EOA Please note the SRP547 should be 10/100/1000. Also note the SRP521/541 are Fast Ethernet units and they do differ from the SRP527/547. The main selling point of these devices are the FXS/FXO ports. So this may also be a bit of an "unfocused" solution. But it's worth throwing the idea out there!
Here is the admin guide;
http://www.cisco.com/en/US/docs/voice_ip_comm/unified_communications/srp540_series/administration/srp500_AG_2567701.pdf
Here is the datasheet;
http://www.cisco.com/en/US/prod/collateral/voicesw/ps6790/gatecont/ps10500/data_sheet_c78-550705.pdf

Viewing XMP Metadata in Adobe Bridge via Adobe Drive Connector

Hi there,
I've been trying to view remote file XMP metadata in Adobe bridge via our adobe drive connector. I've added the READ_XMP_METADATA capablitiy, and I've seen the DataType.XMP has been requested. but I'm not sure how to display the metadata on the Adobe bridge metadata panel. since the metadata is embeded in the file, when i browse the file in local drive, the metadata shows fine, but when it's on our remote server, some how bridge doesn't extract the info and display it. I can see the metadata when I browse the remote file in windows explorer adobe drive. and we do download the file to local to a temp copy, browse the temp copy in bridge also showing the metadata, The only thing not working is browsing the remote file in bridge via adobe drive connector.
Please advise what should be done, in the programmer's guide, it says for each item, request that the server return the XMP data for that asset. How should I do that? If the XMP is embeded in the file, why would I need to request for it, would it be automatically extracted from the file?
Thanks,
Katherine

Hi there,
I've been trying to view remote file XMP metadata in Adobe bridge via our adobe drive connector. I've added the READ_XMP_METADATA capablitiy, and I've seen the DataType.XMP has been requested. but I'm not sure how to display the metadata on the Adobe bridge metadata panel. since the metadata is embeded in the file, when i browse the file in local drive, the metadata shows fine, but when it's on our remote server, some how bridge doesn't extract the info and display it. I can see the metadata when I browse the remote file in windows explorer adobe drive. and we do download the file to local to a temp copy, browse the temp copy in bridge also showing the metadata, The only thing not working is browsing the remote file in bridge via adobe drive connector.
Please advise what should be done, in the programmer's guide, it says for each item, request that the server return the XMP data for that asset. How should I do that? If the XMP is embeded in the file, why would I need to request for it, would it be automatically extracted from the file?
Thanks,
Katherine

RV320 transparent bridge issues

I've tried to use a Small Business RV320 to setup a transparent bridge, for someone not wanting to divide a subnet. It's acting very buggy. This is my first time with an RV router, and without CLI, I'm finding it hard to troubleshot. I have the bridge going between WAN1 and the LAN. The MAC table seems to be built by the WAN side only.
Is there any version of show mac-address-table for the RV routers? Any method of customize bridging operations?
Secondly, the WAN is hooked to a hub, which is hooked to a polling server. The server keeps the MAC table updated. Oddly, the WAN port seems to absorb all packets in the subnet, causing no communication between the poller and polled machines on the WAN-side hub.
The router's GUI has a transparent bridge setting, but I don't exactly know what it's setting up. Anyone with RV router advice?
Thanks!

Hello,
Have you tried the settings as listed in the admin guide:
Transparent Bridge (IPv4)
Choose this option if you are using this router to connect two network segments.
Only one WAN interface can be set as transparent bridge.
• Specify WAN IP Address—External IP address that your ISP assigned to
your account.
• Subnet Mask—Subnet mask specified by your ISP.
• Default Gateway Address—IP address of the default gateway.
• DNS Server 1 and DNS Server 2—IP addresses of the DNS servers.
Optionally, you can enter a second DNS server. The first available DNS
server is used.
• Internal LAN IP Range—Internal LAN IP range that is bridged. The WAN
and LAN of transparent bridge must be on the same subnet.
• MTU—Maximum transmission unit (MTU) size. Select Auto to set the size
automatically. Otherwise, to set the MTU size manually, select Manual and
enter the MTU size. (The size in bytes of the largest protocol data unit that
the layer can pass.)

Transparent Bridging

HI
I am trying to configure transparent bridging over E1 network but not working. Pls refer Scenario in attachment and reply.
Regards
Maninder

Maninder
We could give you better answers if you would supply more detail about what you have put into your configuration. But assuming that you really do want to do transparent bridging (and not something like Integrated Routing and Bridging) then I have these suggestions for you.
- configure a bridge group.
- assign the bridge group to the Ethernet interfaces of both routers and to the E1 interfaces of both routers.
- turn off ip routing (no ip routing - this is the step that most people miss in trying to do this).
HTH
Rick

Transparent bridging & Multilink PPP

Is it possible to run Multilink PPP on 2 T1s while also doing transparent bridging?
If so, Do I need to put bridge-group 1 on my multilink interface?
thx

It is not clear what the original problem was or what was the solution. And I am not clear what problem you are trying to solve that leads to the question of bridging over the multi link.
If we knew more about your situation we might be able to give better advice. But I would suggest that the answer will turn out to be something close to this:
- if you want to route IP over the multilink and to bridge some other traffic that might be possible.
- if you want to bridge IP over the multilink then you can not have an IP address configured on the multilink. To bridge IP over the multilink you might need to do something like configure Integrated Routing and Bridging. In IRB you configure a virtual interface BVI and put the IP address on the BVI. then you put a bridge group on the multilink which points to the BVI. It is ugly and I would not recommend it, but I think that it might work.
HTH
Rick

Routers connected via serial subinterfaces(for non VPN internet service in a mpls network)

I have conected two cisco 7200 routes via one serial interface.
I am going to create two subinterfaces in each of them assign them IP address and connect them via (two BGP neighborship)
the fact is that they cannot even ping eachother though they are directly connected .
1. interfaces are no shut
2.L2 protocol is HDLS on both sides
3.the IPs are in the same subnets .
the question is how to connect two routers with serial sub-interfaces.?
this is my config on both routers , only the IPs are different:
int ser 1/0
no shut
encapsulation hdlc
clock rate 64000
int ser 1/0.1
subif)#ip add a.b.c.d x.x.x.x

Hello Gabriel,
Instead of using the HDLC, use frame-relay encap. Make one side as DCE. Use same DLCI on both sides.
R4#sh run int se2/0
Building configuration...
Current configuration : 96 bytes
interface Serial2/0
no ip address
encapsulation frame-relay
frame-relay intf-type dce
end
R4#sh run int se2/0.1
Building configuration...
Current configuration : 113 bytes
interface Serial2/0.1 point-to-point
ip address 1.1.1.1 255.255.255.0
frame-relay interface-dlci 100
end
R4#ping 1.1.1.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 1.1.1.1, timeout is 2 seconds:
Success rate is 100 percent (5/5), round-trip min/avg/max = 40/40/44 ms
R4#ping 1.1.1.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 1.1.1.2, timeout is 2 seconds:
Success rate is 100 percent (5/5), round-trip min/avg/max = 20/22/32 ms
R4#sh run | i swit
frame-relay switching
R4#
R5#sh run int se2/0
Building configuration...
Current configuration : 69 bytes
interface Serial2/0
no ip address
encapsulation frame-relay
end
R5#sh run int se2/0.1
Building configuration...
Current configuration : 113 bytes
interface Serial2/0.1 point-to-point
ip address 1.1.1.2 255.255.255.0
frame-relay interface-dlci 100
end
R5#ping 1.1.1.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 1.1.1.1, timeout is 2 seconds:
Success rate is 100 percent (5/5), round-trip min/avg/max = 20/21/24 ms
R5#ping 1.1.1.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 1.1.1.2, timeout is 2 seconds:
Success rate is 100 percent (5/5), round-trip min/avg/max = 36/40/44 ms
R5#
Hope this helps.
Regards,
Imran

Sync/Async bridge via JMS with FAULT messages

Hello all, 
I set up a sync/async bridge scenario with using of JMS communication channel (SAP - JMSReceiverCC - JMSServer and application - JMSSenderCC - SAP). The normal communication works fine. 
But what we can not solve is the Fault Message handling. If there is a application error behind the JMS, a fault message is generated instead of proper application response and sent back to XI. Without any additional setup of JMS Sender CC the processing of the message ends with "MAPPING - EXCEPTION_DURING_EXECUTE", because normal "response mapping" is executed instead of "fault message mapping". This is correct behavior without any discussion. 
[SAPhelp|http://help.sap.com/saphelp_nw70/helpdata/en/45/202845de34072ce10000000a155369/frameset.htm] says that there are 2 module parameters to be set : fault, faultNamespace. The description is rather vague, so let's see, what the "NotifyResponseBean" does, when parameters fault/faultNamespace are filled: 
<pre>if(fault != null && faultNamespace != null)
if(faultNamespace.equals("http://sap.com/xi/XI/System"))
 ((XIMessage)message1).setMessageClass(MessageClass.SYSTEM_ERROR);
 ((XIMessage)message1).setError(fault, "no additional information");
} else
 ((XIMessage)message1).setMessageClass(MessageClass.APPLICATION_ERROR);
 ErrorInfo errorinfo = message1.createErrorInfo();
 errorinfo.setAttribute("ApplicationFaultInterface", fault);
 errorinfo.setAttribute("ApplicationFaultInterfaceNamespace", faultNamespace);
 errorinfo.setAttribute("ErrorCode", fault);
 errorinfo.setAttribute("AdditionalErrorText", "no additional information");
 message1.setErrorInfo(errorinfo);
} else
((XIMessage)message1).setMessageClass(MessageClass.APPLICATION_RESPONSE);
}</pre> 
The code is pretty straight forward so one could assume, that it's the name and namespace of inbound synchronnous message interface what is supposed to be filled in the values of each parameter. And from that kind of information SAP XI can evolve how to handle the response, actually the fault. 
Unfortunatelly the real situation is different - every time the fault message is generated and sent back to XI, the response is correctly corelated with the request message, "WaitResponseBean" and "NotifyResponseBean" are finished correctly and the processing crashes in messaging class on following exception: 
java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:592) at
com.sap.aii.messaging.mo.MessageContext.setAttribute(MessageContext.java:140) at
com.sap.aii.adapter.xi.ms.XIMessage.updateHeaders(XIMessage.java:4244) at
com.sap.aii.adapter.xi.ms.XIMessage.getTransportHeaders(XIMessage.java:570) at
com.sap.aii.af.ra.ms.impl.ServerConnectionImpl.request(ServerConnectionImpl.java:212) at
com.sap.aii.af.ra.ms.impl.core.transport.http.MessagingServlet.doPost(MessagingServlet.java:337) at ...
 
Is there anyone, who can put more light on JMS sync/async bridge fault handling ???
 
Thank you ... 
Regards
Tomas

Hello again,
I proceed in investigation little more, but the main problem has not been solved. I found that the problem is not even in WaitResponseBean (placed in JMCReceiverCC). This bean is woken up properly on base of proper CorrelationID. See the log:
2009-10-15 11:00:33 Success WRB: entering WaitResponseBean
2009-10-15 11:00:33 Success WRB: retrieving the message for f1ea1fc0-b96d-11de-9b68-00144f4acd86 ...
2009-10-15 11:00:46 Success WRB: retrieved the message: ApplicationError
2009-10-15 11:00:46 Success WRB: leaving WaitResponseBean
I think, that the problem is somewhere within main messaging functionality. I suppose that on base of exception message:
com.sap.aii.messaging.mo.MessageContext.setAttribute(MessageContext.java:140) at
which is generated.
Any ideas or comments ?
Thank you in advance.
Regards
Tomas

Opening JPG from Bridge via ACR in PS causes ACR to run twice.

Using PSCS3 and Bridge CS3, with both set to prefer ACR when opening JPG files. Sometimes when opening a file from within Bridge with PSCS3, ACR runs twice. The image can be opened in PS and then ACR opens again with another copy of the JPG. Cancelling the ACR window closes it.
Anyone else get ACR running twice on the one JPG?
Thanks.
Stew.

The most common reason for patch to fail is the absence of folder "AdobePatchFiles" folder or it's content from location "C:\Program Files (x86)\Adobe\Adobe\AdobePatchFiles" and it's counterpart location in Mac.
If this folder or its contents are missing then the patch cannot be applied , the only way to resolve this is to Reinstall the product and then apply patch again.
Now there can be two cases :
1) Was this folder removed manually or some other action caused this removal of folder( May be some script or Defragmentation or anything). In this case please reinstall product and apply patch again.
2) If the folder and its contents are intact but still patcher failed, then please follow the following steps:
     a) Create ribs3debug file without any extension inside %temp% directory of your system
     b) Run Patcher again
     c) If it fails , send the log files that are generated inside C:\Program Files (x86)\Common Files\Adobe\Installers
Hope it clears some of the facts around failure. If there are any underlying issues then we all hope to resolve them as soon as we have more information.
Regards
Anshum

7246 CMTS transparent bridging?

Hi,
I have a question.
How can I solve my problem on the picture?
Is it possible that the default GW is the internet router and the CMTS is acting as a bridge?

I hope this will help.
http://www.cisco.com/en/US/tech/tk86/tk804/technologies_q_and_a_item09186a00800a4ae5.shtml#qa4

ASA - Transparent Bridging and BVI

Does the BVI have to be on the same subnet as the nodes on the Inside interface?
We'd like to place the ASA between two routers with a /29 in between them and put the BVI on the same subnet.
The servers would be behind one of the routers (L3 switch) on a different subnet.
Looking through the docs, the ASA seem to be placed between the the servers and its default gateway, and acts as a front end to the servers.
Servers -- Cat3750 -- ASA -- Router

Looked further into the release notes and now, leads to more confusion ...
"Each bridge group requires a management IP address. The ASA uses this IP address as the source address for packets originating from the bridge group. The management IP address must be on the same subnet as the connected network."
http://www.cisco.com/en/US/docs/security/asa/asa90/configuration/guide/intro_fw.html
My understanding is that the BVI does the following?
- used for management
- must be on the same subnet as the Inside Hosts
- as acts a front-end to the hosts to respond to ARP, etc

Guest WLAN and VLAN out of 2811 w WLC module

Using a WLC 2006 or 4000 series, there is
no problem getting the traffic on a "guest WLAN" connected to a wired VLAN.
But, how to do that when one is using
a 2811 with a WLC module?
Now the "guest WLAN" connects internally
to the 2811 "interface wlan-controller 1/0" as a VLAN on a subinterface. I do not want the default GW for that VLAN within the 2811. Instead I just want to get it out at layer 2. Transparent bridging between a subinterface "int wlan-controller1/0.x" and "int fastethernet0/1.x" failed. Any ideas?

Try these links:
http://www.cisco.com/en/US/tech/tk722/tk809/technologies_configuration_example09186a008070ba8f.shtml
http://www.cisco.com/en/US/tech/tk722/tk809/technologies_configuration_example09186a008073c723.shtml

Bridging FWSM VLAN via IDSM

I have briged the FWSM VLANs ( named DMZ,DMZ-BRIDGE) via the IDSM. However, on the 'show failover' on FWSM the server VLAN shows as 'No Link/Unknown'. Is it because there is no IP assigned. Is it the right status/configuration. Do I need to assign an IP to the bridged VLAN. Please assist.
This host: Primary - Active
Interface DMZ-BRIDGE (0.0.0.0): No Link (Not-Monitored)
Other host: Secondary - Standby Ready
Interface DMZ-BRIDGE (0.0.0.0): Unknown (Not-Monitored)

In most of the data centers IDSM could be a bottleneck due to its 600Mbps(Promiscuous) & 500Mbps(inline) limitation.
If its placed inline and has no capacity to process new packets then like any other inline device it will start dropping packets.
In your case you need to know the throughput needed between segments.
If you are not sure then dont use IDSM in inline mode.
In promiscouous mode, using VACL you can define traffic to be examined by Sensor using ACLs.
Although IPS exist at the WAN/Internet Layer, its still desirable to have IPS/IDS at service layer to protect resources from getting compromised.
When we say bridging vlans using IDSM then we mean IDSM in inline mode. In case of ACE if you want to use IDSM inline then you will bridge server vlan interface of ACE & Actual Server Vlans.
Vlan X (client vlan) ACE (Server Vlan)Vlan Y IDSM (Real Server Vlan) Vlan Z
In the above example you will bridge vlan Y & Z.Since you are bridging the two vlans, Same IP address space will be used in the two Vlans.
Syed

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.

DLSW ER+ at the central site

The network topology that I have is two MSFCs and two external routers at central site and two MSFCs and two external routers at the remote site.
DLSW is activated on the external routers. In regards to DLSW+ ER at the central site, only one translational or transparent bridge can be active at a time. Manual intervention is required to cause a router to take over for the other router. Is there any other way to have some means of dlsw redundancy (w/o manual intervention) at the central site (for ethernet environment only)?
Second, DLSW ER+ cannot be deployed easily at the central site, since you need a lot of dlsw mapping. On the other hand, you also need local SNA PUs to be able and reach the CIP (both located at the central site) but reside on a different broadcast domain. Any ideas?
Thanks

Hi,
on the central side, host end, there are a couple of things you can do.
The potential solutions mentioned below are in the order that cisco would prefer.
1.
The most clean thing to do is to upgrade and configure the mainframe for appn and allow hpr/ip between the host end router and the host.
You will need to run dlsw/vdlc/snasw in the host end routers to be able to do this.
It also requires that you have ip connectivity to the mainframe.
If you do this than the mac address, the remote devices connect to, is configured as a snasw vdlc port in the routers. Both of them are active all the time, the remotes will learn the remote mac address over both peers and as such you have automatic, non manual intervention, redundancy, loadbalancing. The mac addresses in this case only exist in the central router. Nowhere else. The remote device does not know anything about this change.
Each of the head end dlsw/vdlc/snasw routers will have at least one hpr/ip uplink to the host. This is routed ip traffic into the mainframe.
In that case you can also define the physical ethernets as snasw ports, do hsrp on it and configure a hsrp mac address, this mac address would then be used as dmac for local clients connecting to the host.
2.
If for some reason you can not do the appn/snasw configuration you still have some options.
If you are using cisco cip's with csna today than you most likely have on path into the mainframe today for each mac address.
You can configure multiple vlans between the dlsw router and the cip router, i.e. dot1q trunk, and on the cip router you can configure multiple virtual ring groups and more than one csna path statement into the host. At the end you attach each vlan to one of the channel path, configure srtlb for each vlan into a unique vring, and then configure a different adapter number on each of the internal tokenring lans with the same mac address.
On the dlsw router you can configure multiple bridge groups into dlsw and each of those bridge groups goes to a different vlan. If you do this with two dlsw routers going to the same cip router you then end up with two channel access's and one vlan on each of the dlsw routers. If you do it to two cip routers you need 4 vlans. Just make sure that you dont bridge the vlans together.
The remotes learn than the remote mac address over both peers and your redundancy is established.
For the local clients this solution has the draw back that you need to pick a vlan where to connect them. There is no automatic redundancy, like hsrp in the first example, for those.
3.
You can enable both dlsw routers towards a single bridge-group and apply a mac address filter inbound to the bridge group only allowing the mac address/es of the hosts as source mac address.
That way you kill the potential loop on the head end. You will also need to put on as much restrictive filtering as possible to only allow the traffic that is wanted.
thanks...
Matthias

DLSW - Transparent Bridging via FE Subinterfaces?

Similar Messages

Maybe you are looking for