1 / 36

D-Link Switches Management Features and Examples New 10G Stacking Technology for DGS-3400/3600

D-Link Switches Management Features and Examples New 10G Stacking Technology for DGS-3400/3600. James Chu , Sep. 2007. Stacking Technology Advantage. Manage the entire stack as a single high-performance device. Single SNMP image for entire stack simplifies SNMP applications.

inga
Download Presentation

D-Link Switches Management Features and Examples New 10G Stacking Technology for DGS-3400/3600

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. D-Link Switches Management Features and Examples New 10G Stacking Technology for DGS-3400/3600 James Chu, Sep. 2007

  2. Stacking Technology Advantage • Manage the entire stack as a single high-performance device. • Single SNMP image for entire stack simplifies SNMP applications. • Shared learning and management information between the switches of the stack. • The stacking capability, hot swap of stack switches, offers reliability and scalability for network to grow with business.

  3. New 10G Stacking Features • 2 Types of Stacking Topology : • Duplex Chain : 1 primary master + 1 backup master + 10 slaves • (Max. stacking number 12 units in a stack) • Duplex Ring : 1 master + 1 backup master +10 slaves • (Max. stacking number 12 units in a stack) • (No star topology in DGS-3400/3600 series) • Very High Port Density (stacking 12 units) • up to 288~576GE + 12 10GE (if stacking DGS-3427/3627) ports • DGS-3426  24 * 12 = 288 12 10G ports * 12 • DGS-3450  48 * 12 = 576 • (Comparison: 168~384 GE ports in xStack) • DGS-3324SRi  24 * 7 = 168 (star topoloy) • DXS-3350SR  48 * 8 = 384 (Ring topology) • Very High Bandwidth Switch Engine • Chain/Ring: 40 Gbps share bandwidth • 10G * 2 (upstream/downstream) * 2 ports / per device • Full Redundant Support • AutoRecover on any point of failure (Ring topology) • AutoRestore when the same device re-join • Backup master activates without whole stack rebooting (new for DGS-3400/3600)

  4. DGS-3400/3600 Stacking Topology

  5. XStack DGS-3400 series • DGS-3400 is the first series for D-Link next generation 10G stackable Switch including 3 models: DGS-3426 [ 24G+ 4 combo SFP + 2 10G slots ] DGS-3427 [ 24G+ 4 combo SFP + 3 10G slots ] DGS-3450 [ 48G+ 4 combo SFP + 2 10G slots ] DGS-3612 [ 12 SFP+ 4G combo + no stacking slots ] Support 2 modules DEM-410CX [1-port 10GBase-CX4 10G copper module] DEM-410X [1-port 10G module to work with 10G transceiver DEM421/422XT]

  6. Stacking Ports (10G ports) DGS-3426 DGS-3426 : port 25 (SIO 1), 26 (SIO 2) DGS-3427/3627 DGS-3427/3627 : port 26 (SIO 1), 27 (SIO 2), 25 for 10G only. DGS-3450/3650 DGS-3450/3650 : port 49 (SIO 1), 50 (SIO 2)

  7. 10GE Stacking modules 1/2 Using Fiber cable Using CX4 cable

  8. 10GE Stacking modules 2/2 • To establish long distance stacking by DEM-410X

  9. DGS-3400/3600 Stacking Technology 1/3 1. Very Hi-Ports Density : (Compared with xStack chart below) DGS-3400/3600 xStack(DGS-3324SRi, DGS-3324SR, DXS-3326GSR,DXS-3350SE) 2. Hot swappable at all device • Device could join to or remove from the ring anytime.

  10. DGS-3400/3600 Stacking Technology 2/3 Fully utilize the Ring bandwidth by Shortest Path Switching This feature, Shortest Path Switching, can be applied to Unicast only and is designed to achieve full utilization of bandwidth in a Duplex-Ring stacking topology by forwarding packets through the shortest path between devices. ex: From node 2 to node 9 path has two choices. Node 2  3  4  …… node 9 (totally, pass 7 nodes) Node 2  1  12 …… node 9 (totally, pass 5 nodes)  adopt shortest path

  11. DGS-3400/3600 Stacking Technology 3/3 • The traffic in the ring runs on the super high way. It will not be influenced by local traffic ! • X-Bar architecture enable this capability !! Traffic in the Ring X-Bar The Traffic in the Ring will not be influenced by the local traffic. SW Local Traffic

  12. Master Election 1/3 • After stacking topology is stable, every device saves other device’s discovery information (ex: priority, MAC address) in self tempstacking topology database. • It will judge whether the switch itself should become primary master according to priority(default is 32)and MAC addresscomparison. • According this mechanism, stacked switch will be responsible to determine which device is backup master in remain devices according to priority and MAC address. • Then all devices’ box ID will be assigned (ex: master = 1 in auto mode). This topology information will be sent to other devices. Alldevices will know self role and box ID. • Root up SW  Elect Master SW  Elect backup Master  Assign Box ID

  13. Master Election 2/3

  14. Master Election 3/3

  15. Backup Master Election 1/3 Backup Master is the backup of primary master. If primary master is down, backup master must swap to be the primary master role immediately to make whole stacking work continue. After primary master being determined the backup master would be decided according remain devices’ priority and MAC address. Rules are the same as the process of primary master election. After backup master being determined and Box ID assigned, stacking topology database will be updated and notify other devices. All devices will have same stacking topology database.

  16. Backup Master Election 2/3

  17. Backup Master Election 3/3

  18. Box ID Assign 1/6 All in AUTO Mode If all switches configure Box ID as “AUTO” , primary master (with Box ID “1” after master elected) will assign Box ID to each device by stacking ID assignment rule automatically.

  19. Box ID Assign 2/6 The following diagram depicts AUTO assigning rule for both topologies:

  20. Box ID Assign 3/6 • All in STATIC Mode • When all devices are set as STATIC mode, the assignment of Box IDs will follow user’s configuration. • Any device with new BOX ID, different from the previous setting, will return to default configuration. • If confliction of BOX ID (more than one device have the same BOX ID) is detected during the stack discovery process, the device will enter stand-alone mode. Also the system will promptly display an error message about conflictive BOX ID to remind you change BOX ID of the device to eliminate the confliction. • SW master/backup master doesn’t relative Box ID. • (ex: Master SW’ Box ID could be 3, not 1)

  21. Box ID Assign 4/6 AUTO and STATIC Mixed Mode Under AUTO and STATIC mixed mode: Step 1. primary master will collect all BOX ID information first Step 2. check whether BOX ID confliction occurs or not. Step 3. If no confliction is detected, primary master will first assign BOX IDs for those devices configured with STATIC mode enabled, and then assign the others BOX IDs for devices configured with AUTO mode enabled. See also the following flowchart.

  22. Box ID Assign 5/6

  23. Box ID Assign 6/6

  24. Topology Change 1/7 • Stacking protocol can discover topology change and synchronize immediately to form a new stacking topology. There are four typical types of topology change: • Hot Insert (put a new SW into stacking topology) • Hot Remove (remove a new SW into stacking topology) • Chain to Ring (establish a connection to be Ring topology) • Ring to Chain (establish a connection to be Chain topology)

  25. Topology Change 2/7 Hot Insert Adding one or multiple devices to a stable stacking topology, the new device will enter slave or backup master state of the stacking topology.

  26. Topology Change 3/7 Hot Remove Removing one or multiple devices from a stable stacking topology, each device in the current stacking topology will clear information about this leaving device

  27. Topology Change 4/7 Primary Master fails Backup master, designated as a backup of primary master, can immediately auto-exchange and operate as primary master when master switch is broken. Besides, the new primary master will use same IP Address as the old primary master in order to abate influence to the network. The box_id of backup master will remain the same as it used to be and will not change to “1”. Backup Master become a Primary Master with Box ID 2 

  28. Topology Change 5/7 Primary Master fails

  29. Topology Change 6/7 Chain to Ring Stacking topology change from chain to ring is simple: no need to change devices’ states.

  30. Topology Change 7/7 Ring to Chain Similar to Chain to Ring topology change, all devices’ states are not necessary to be renewed when stacking topology is changed from Ring to Chain.

  31. Other DGS-3400/3600 stacking features • 1. Support mirror across units in a stack • 2. Support trunking across units in a stack • 3. Auto Fail-Over mechanism in Ring architecture while stacking master fails, the whole stack will not reboot and the backup master will take over.

  32. Cross-Mirroring PC1 SW IP : 192.168.0.50 Port 1:13 1 Port 2:1 stacking 2 PC2 192.168.0.250 Test Steps 1.PC2 continuously ping SW 2.Use PC1 to monitor port 2:1Configurationconfig mirror port 1:13 add source ports 2:1 both enable mirror Result We can successfully monitor port 2:1 from port 1:13

  33. Cross-Trunking PC1 Port 1 Port 9,11 A Stand alone 1:9 1 Stacking 2:11 2 Port 2:2 PC2 Configuration #DGS-3426(stand alone) config link_aggregation algorithm mac_source create link_aggregation group_id 1 type lacp config link_aggregation group_id 1 master_port 9 ports 9,11 state enable #DGS-3426(stacking) config link_aggregation algorithm mac_source create link_aggregation group_id 1 type lacp config link_aggregation group_id 1 master_port 1:9 ports 1:9,2:11 state enable config lacp_port 1:9,2:11 mode active

  34. DGS-3400/3600 Stacking Demo

  35. Demo: Auto Fail-over Auto Fail-Over mechanism in Ring architecture while stacking master fail, the whole stack shouldn't reboot and the backup master will take over. There are two scenarios. 1.Backup master take over immediately if master’s power is down or link to master fails. 2.It will take about 54/120(DGS-3400/3600) seconds for backup master to take over if the primary master is in exception mode and can not communicate with other devices.

  36. Thank You !

More Related