From: Roger Schotsal (schotsal@xxxxxxxxxxx)
Date: Wed Mar 13 2002 - 03:15:48 GMT-3
When configuring DLSW - what is the correct configuration to protect the
ethernet segment (mtu 1500) from token frames (mtu 4472) ? Do you need to
configure 'lf' on the remote peer statement on the token side ? or is a 'lf'
statement on the local peer statement of the ethernet side sufficient?
r1
source-bridge ring-group 3333
dlsw local-peer peer-id 204.100.100.17
dlsw port-list 1 TokenRing0/0
dlsw remote-peer 1 tcp 150.10.10.1 lf 1500
r2
dlsw local-peer peer-id 150.10.10.1 lf 1500
dlsw port-list 1 Ethernet0
dlsw remote-peer 1 tcp 204.100.100.17
dlsw bridge-group 1
OR
r1
source-bridge ring-group 3333
dlsw local-peer peer-id 204.100.100.17
dlsw port-list 1 TokenRing0/0
dlsw remote-peer 1 tcp 150.10.10.1
r2
dlsw local-peer peer-id 150.10.10.1 lf 1500
dlsw port-list 1 Ethernet0
dlsw remote-peer 1 tcp 204.100.100.17
dlsw bridge-group 1
I cannot find any dlsw show commands that show me the capability is
exchanged in any way so my guess is that you have to configure it on both
sides. That is the configuration is not part of the capability exchange.
Seems like something a proctor could get pickey about. I'd appreciate any
comments omn this.
Thanx,
roger
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:57:03 GMT-3