Brett,
the error message is making you aware of the fact that a certain frame is due to be forwarded onto a ring number it already has an entry for in its rif.
However in certain situations this is also seen in working environments due to the inner working of the cisco source bridging code.
Are you sure that there is no duplicate source-bridge path? If yes, ignore the message.
If the error message is only seen when you use source-bridge spanning to forward single route explorers on the tokenring than you can do the following. Assuming we are talking about sna in this example:
dlsw allroute-sna
in this case dlsw will forward explorers outbound towards the tokenring as allroute explorers for sna on a tokenring interface. The default is as single-route explorer.
However inbound into the router it is purely dependend on what the end system does. If the end system, the client, starts with a single route explorer you still need source-bridge spanning on the interface, otherwise dlsw will not see the frame.
How does the setup physcially look like?
Is your client on the tokenring or on the ethernet interface attached to dlsw?
I understand from your description that the client is behind R2, so when you issue a show dlsw reachability
can you see the client?
debug dlsw reach verbose
should give you an idea if the client tries to start a session and with what dmac.
Is dlsw trying to start a circuit? I.e. in what state is the circuit if there is one?
show dlsw circuit history detail can give you some more ideas what happened, if the router tries to start a circuit and it is not successfull. However you need to know a great deal of dlsw to fully understand that output.
A sniffer on the tokenring will certainly show if the client tries to start a session and with what dmac.
There are lots of possibilities why this might not work, so it is most likely the best to open a case with the tac and work the issue till conclusion.
thanks...
Matthias
