Section 6: DLSw (6 Points)

Section 6: DLSw+ (6 Points)

• Configure DLSw+ with TCP encapsulation between R6-R4 and R6-R5. R4 should only be able to connect to R6 VLAN2 and R5 to VLAN5.

If you configured straightforward peering between each of the routers, they would have full connectivity to each VLAN on R6. This question requires bridge-lists to separate the DLSw connectivity for the two peers to each VLAN connected to R6. If you have configured this correctly as shown in Example 3-70 through Example 3-72, you have scored 2 points.

Example 3-70. R4 Initial DLSw+ Configuration

 dlsw local-peer peer-id 10.4.4.4 dlsw remote-peer 0 tcp 10.6.6.6 dlsw bridge-group 1 ! interface FastEthernet0/0  bridge-group 1 ! bridge 1 protocol ieee 

Example 3-71. R5 Initial DLSw+ Configuration

 dlsw local-peer peer-id 10.5.5.5 dlsw remote-peer 0 tcp 10.6.6.6 dlsw bridge-group 1 ! interface FastEthernet0/0  bridge-group 1 ! bridge 1 protocol ieee 

Example 3-72. R6 Initial DLSw+ Configuration

 dlsw local-peer peer-id 10.6.6.6 dlsw bgroup-list 1 bgroups 1 dlsw bgroup-list 2 bgroups 2 dlsw remote-peer 2 tcp 10.5.5.5 dlsw remote-peer 1 tcp 10.4.4.4 dlsw bridge-group 1 dlsw bridge-group 2 ! interface FastEthernet0/0  bridge-group 1 ! interface FastEthernet4/0  bridge-group 2 ! bridge 1 protocol ieee bridge 2 protocol ieee 

• If the DLSw+ connection from R4-R6 fails, allow R4 to connect to VLAN2 via R1. If the primary connection to R6 is restored, only keep the new connection to VLAN2 active for 60 seconds.

You are now required to configure a backup peer from R4 to R1. If the primary peer to R6 fails on R4, the backup peer will be used. To keep the backup peer active when the primary peering to R6 is re-established, you will need to use the linger option. Remember that linger is expressed in minutes and not seconds and that R1 will require a promiscuous statement to peer with R4 in addition to the basic DLSw+ configuration. If you have configured this correctly as shown in Example 3-73 and Example 3-74, you have scored 2 points.

Example 3-73. R4 DLSw+ Backup Configuration

 dlsw remote-peer 0 tcp 10.1.1.1 backup-peer 10.6.6.6 linger 1 

Example 3-74. R1 DLSw+ Backup Configuration

 dlsw local-peer peer-id 10.1.1.1 promiscuous dlsw bridge-group 1 ! interface FastEthernet0/0  bridge-group 1 ! bridge 1 protocol ieee 

• R4 and R5 should show reachability of NetBIOS name ccie advertised from R6. This is the only NetBIOS name of which R6 should have visibility.

You need to configure DLSw+ NetBIOS reachability in the form of an icanreach statement on R6. Because this is the only NetBIOS name that R6 can reach, you should include the dlsw icanreach netbios-exclusive command. If you have configured this correctly as shown in Example 3-75, you have scored 2 points. Example 3-76 shows the DLSw+ capabilities on R4 and R5 with the cached NetBIOS name.

Example 3-75. R6 NetBIOS Configuration

 dlsw icanreach netbios-exclusive dlsw icanreach netbios-name ccie???? 

NOTE

To enter a ? within the command line without bringing up the help function, you need to enter ^v (Shift+6, then v) first.

Example 3-76. R4 and R5 DLSw+ Capabilities

 R4#sh dlsw capabilities DLSw: Capabilities for peer 10.6.6.6(2065)   vendor id (OUI)          : '00C' (cisco)   version number           : 2   release number           : 0   init pacing window       : 20   unsupported saps         : none   num of tcp sessions      : 1   loop prevent support     : no   icanreach mac-exclusive  : no   icanreach netbios-excl.  : yes   reachable mac addresses  : none   reachable netbios names  : ccie????   V2 multicast capable     : yes   DLSw multicast address   : none   cisco version number     : 1   peer group number        : 0   peer cluster support     : no   border peer capable      : no   peer cost                : 3   biu-segment configured   : no   UDP Unicast support      : yes   Fast-switched HPR supp. : no   NetBIOS Namecache length : 15   local-ack configured     : yes   priority configured      : no   cisco RSVP support      : no   configured ip address    : 10.6.6.6   peer type                : conf   version string           : Cisco Internetwork Operating System Software IOS (tm) 7200 Software (C7200-JS-M), Version 12.2(16), RELEASE SOFTWARE (fc3) Copyright  1986-2003 by cisco Systems, Inc. Compiled Thu 06-Mar-03 21:37 by pwade ________________________________________________________________ R5#sh dlsw capabilities DLSw: Capabilities for peer 10.6.6.6(2065)   vendor id (OUI)          : '00C' (cisco)   version number           : 2   release number           : 0   init pacing window       : 20   unsupported saps         : none   num of tcp sessions      : 1   loop prevent support     : no   icanreach mac-exclusive  : no   icanreach netbios-excl.  : yes   reachable mac addresses  : none   reachable netbios names  : ccie????   V2 multicast capable     : yes   DLSw multicast address   : none   cisco version number     : 1   peer group number        : 0   peer cluster support     : no   border peer capable      : no   peer cost                : 3   biu-segment configured   : no   UDP Unicast support      : yes   Fast-switched HPR supp. : no   NetBIOS Namecache length : 15   local-ack configured     : yes   priority configured      : no   cisco RSVP support      : no   configured ip address    : 10.6.6.6   peer type                : conf   version string           : Cisco Internetwork Operating System Software IOS (tm) 7200 Software (C7200-JS-M), Version 12.2(16), RELEASE SOFTWARE (fc3) Copyright  1986-2003 by cisco Systems, Inc. Compiled Thu 06-Mar-03 21:37 by pwade