D-Link wirless Controller

DWS-3160-24PC

System

Size

• 19-inch Sandard Rack-Mount Width, 1U Height

Network Interfaces

• 20 10/100/1000Base-T
• 4 Combo 10/100/1000Base-T/SFP

Console Port

• RJ45 RS-232

MAC Address Table

• 16K

Maximum Power Consumption

• 467 W (full POE load)

Performance

Switching Capacity

• 48 Gbps

Maximum Forwarding Rate

• 35.71 Million Packets per Second

Forwarding Method

• Store and Forward

Packet Buffer Memory

• Up to 256 static MAC entries
• Enable/disable auto-learning of MAC addresses

802.3af Power over Ethernet

• 15.4 W Per Port
• 370 W Total Power Budget
• 740 W Total Power Budget With RPS

Number of VLANs per Device

• 4K

Static Routes

• 512

Jumbo Frames

• 13K

Physical

MTBF

• 282,541 hours

Acoustic

• Below 30 °C (86 °F)< 39.8 dB
• Over 30 °C (86 °F):< 51.8 dB

Heat Dissipation

• With 370 W PoE load: 1593.5 BTU/hr

Dimensions

• 440 x 310 x 44 mm (17.32 x 12.20 x 1.73 inches)

Redundant Power Supply

• DPS-700

Weight (without optional module)

• 5.24 kg (11.55 pounds)

Operating Temperature

• 0 to 50 °C (32 to °F)

Storage Temperature

• -40 to 70 °C ( to 158 °F)

Operating Humidity

• 10% to 90% RH

Storage Humidity

• 5% to 90% RH

EMI Certifications

• FCC Class A
• CE
• ICES-003
• C-Tick
• VCCI

Safety

• UL/cUL
• CB

Software Specifications

Management

• Manages up to 48 Unified Access Points per switch, up to 192 APs per cluster
• Switch Cluster for Single IP Management
• SSH
• SSL
• SNMP v1, 2c, 3
• sFlow
• Dual Image Support
• Web GUI
• Command Line Interface

AP Management

• AP Auto-Discovery
• Remote AP Reboot
• AP Monitoring: List Managed AP, Rogue AP, Authentication Failed AP
• Client Monitoring: List clients associated with each Managed AP
• Ad-hoc Client Monitoring
• AP Authentication Supporting Local Database and External RADIUS Server
• Centralized RF/Security Policy Management
• Automatic AP RF Channel Adjustment
• Automatic AP Transmit Output Power Adjustment
• Centralized Firmware Upgrade

Managed Unified Access Points

• DWL-3600AP
• DWL-6600AP
• DWL-8600AP

Roaming

• Fast Roaming
• Intra-Switch/Inter-Switch Roaming
• Intra-Subnet/Inter-Subnet Roaming

Access Control & Bandwidth Management

• Up to 32 SSID per AP (16 SSID per frequency band)
• AP Load Balancing based on the number of users or AP utilization
• Flexible Mapping Schemes

L2 Features

• IGMP Snooping
• MLD Snooping
• 802.1D/w/s Spanning Tree
• 802.3ad Link Aggregation
• 802.1ab LLDP
• Port Mirroring (One-to-One and Many-to-One)
• Jumbo Frame Size: Up to 13 KB

L3 Features

• IPv4/v6 Static Route
• Routing Table Size: 512 Static Routes
• VRRP
• ARP Proxy

LAN Security

• RADIUS Authentication Management Access
• TACACS+ Authentication for Management Access
• SSH & SSL Support
• MAC Filtering
• 802.1X Port-based Access Control & Guest VLAN
• Denial of Service Protection
• Dynamic ARP Inspection
• Protected Port
• Broadcast Storm Control
• Access Control List

MIB

• 1213 MIB II
• 1493 Bridge MIB
• 1907 SNMP v2 MIB
• 1215 Trap Convention MIB
• 2233 Interface Group MIB
• D-Link Private MIB
• LLDP MIB
• Power-Ethernet MIB

LAN Flow Control

• 802.3x Standard in Full Duplex Mode
• Back Pressure in Half Duplex Mode
• Head-of-Line Blocking Prevention

QoS (Quality of Service)

• Voice VLAN
• Wireless Multimedia (WMM)
• 802.1p Priority Queues
• CoS-based QoS
• Per-Flow Bandwidth Control
• Per-Port Traffic Shaping
• Minimum Bandwidth Guarantee

VLAN

• 802.1Q VLAN Tagging
• 802.1V
• Subnet-based VLAN
• MAC-based VLAN
• GVRP
• Double VLAN
• Voice VLAN

WLAN Security

• WPA Personal/Enterprise
• WPA2 Personal/Enterprise
• 64/128/152-bit WEP Data Encryption
• MAC Authentication
• Station Isolation
• Wireless Station and AP Monitoring based on RF Channel, MAC Address, SSID, Time
• Rogue AP and Client Detection & Mitigation
• Captive Portal
• Security Profile
• 802.1X Support
• Guest VLAN

Ordering Information
DWS-3160-24PC

• Unified Wireless Gigabit 24 Port PoE L2+ Switch with 12 AP license

DWS-3160-24TC

• Unified Wireless Gigabit 24 Port L2+ Switch with 12 AP license

DPS-700

• D-Link Redundant Power Supply 589 watts, 1+1 PoE budget

DPS-200

• D-Link Redundant Power Supply 60 watts, 1+1 PoE budget

DWL-8600AP

• Unified Concurrent Dual-band Access Point 802.11a/b/g/n

DWL-6600AP

• Unified Concurrent Dual-band Access Point 802.11a/b/g/n

DWL-3600AP

• Unified Access Point 802.11b/g/n

DWS-3160-24TC-AP12-LIC

• DWS-3160AP-24TC Upgrade License for 12 APs

DWS-3160-24TC-AP24-LIC

• DWS-3160AP-24TC Upgrade License for 24 APs

DWS-3160-24PC-AP12-LIC

• DWS-3160AP-24PC Upgrade License for 12 APs

DWS-3160-24PC-AP24-LIC

• DWS-3160AP-24PC Upgrade License for 24 APs

AMP cable

Twisted Pair Cable

Category 6 UTP Cable

Meets or exceeds TIA/EIA-568-B Category 6 and ISO Class E 11801:2002 specifications Performance characterized to 600 MHz 3dB NEXT performance above Category 6 standards Independently verified by Intertek ETL/SEMKO testing services Intertek ETL/SEMKO Listed cUS (CMR/CMP) Exceeds all requirements for Gigabit Ethernet (IEEE 802.3ab) Lead-free jacketing 23 AWG, solid conductors

Category 6A F/UTP (ScTP) Cable

Meets or exceeds TIA/EIA-568-B.2-10 Augmented Category 6 and ISO 11801 Edition 2.1 Class EA specifications UL Listed cUS (CMR/CMP) Independently verified by Intertek ETL/SEMKO testing services Exceeds all requirements for Gigabit Ethernet (IEEE 802.3ab) Exceeds all requirements for IEEE 802.3an, 10 Gigabit Ethernet 23 AWG, solid conductors Lead-free (no heavy metals) Category 6e UTP Cable Meets or exceeds TIA/EIA-568-B Category 6 and ISO 11801:2002 Class E specifications Performance characterized to 600 MHz 8 dB NEXT performance above Category 6 Intertek ETL SEMKO Listed cUS (CMR/CMP) Independently verified by Intertek ETL SEMKO testing services Exceeds all requirements for Gigabit Ethernet (IEEE 802.3ab) Lead-free jacketing 23 AWG, solid conductors     

CISCO

Cisco UCS, Nexus, NetApp – FCoE End to End Config

I am sick of cables.  One of the most recent vSphere hosts I deployed had ELEVEN Gigabit Ethernet cables attached to it…and I actually have one that has Fourteen!  So, one of my goals when looking at deploying UCS was a setup that utilized 10gb Ethernet and FCoE everywhere. 

Well, it’s almost end to end.  It’s actually not possible to do FCoE end to end today, and you might read about the need for “FCoE Multi Hop”.  FCoE is as it is described, an implementation of Fibre Channel over Ethernet.  How it works is you basically establish an Ethernet infrastructure, and the FC (which is really just standard FC) runs over “Virtual FC” ports.  In order for this to be done completely end to end you need N_port Virtualization support on all devices in the chain.  This support exists today on the latest code for the Nexus switches, but not on the code for the UCS Fabric Interconnects (although I am told it is coming soon).  My temporary solution was to order my Fabric Interconnects with the expansion module that has Four 10gb Ethernet ports and Four 4gb Fibre Channel ports.

There are several models you can plug into the expansion slot on the FI’s but I chose this one for the following reasons:

·  It has more than enough FC ports for my immediate needs, and the extra 10gb ports mean it will continue to be useful when the FI software is updated to allow NPV.

·  Ports on addon modules include “Free Port Licenses”, so I will be able to add another couple of UCS Chassis down the road without paying the ridiculous port licence costs (the one thing about UCS I don’t like).

For now, this is what I’m describing.  Blue lines are 10gb Ethernet, Green are traditional Fibre Channel:

Hardware Breakdown

The config described below consists of the following hardware:

·  1 UCS Blade Chassis (Cisco 5108)

·  2 UCS Fabric Interconnects (Cisco 6120XP w/ 4x10GB & 4x4GB FC Expansion Module)

·  2 Cisco Nexus 5548UP Switches (with Layer3 Daughtercard)

·  1 NetApp 3210 Filer (with Dual Controllers)

What about VPC on the switches?

VPC is a great thing.  It lets you create a port-channel between a device and two separate switches, but from the device’s point of view the connections are going to the same device.  Lose a switch, nothing goes down.  We have the Nexus Switches connected in a VPC Peer Link (not shown in the diagram above).  The only challenge here is that a properly built Fibre Channel design calls for two completely separate fabrics; this is taken into account in the configs below.

Fabric Interconnect <-> Nexus (Ethernet) Config:

I have two 10gb links between each Fabric Interconnect and it’s corresponding Nexus Switch (no cross connections).  These are port-channelled in the traditional way to keep service in the event of port, transceiver, or cable loss.
On the UCS Side it’s easy to establish the port channel.  For each Fabric (A and B) just right click on Port Channels under the LAN tab and select Create Port Channel.  Give it a name and select your uplink ports.  When done, the UCS interface will look similar to the below:

On the Nexus side, the following configs are in place on both switches:

Pretty simple stuff.  When done, do a “show port-channel summary” command from both switches and you should see them up as so:
201   Po201(SU)   Eth      LACP      Eth1/17(P)   Eth1/18(P)

Fabric Interconnect <-> Nexus (Fibre Channel) Config:

On the UCS Side, you don’t actually have to do anything for the actual FC Uplinks.  UCS considers any traditional FC port an FC Uplink.  What you DO have to do is define your VSAN’s for those uplinks.  Although much of our Ethernet infrastructure is designed to allow packets to flow in multiple paths, with FC the mentality is you define 2 exact paths and if there is a failure somewhere along one of them, the whole path is just down (and therefore packets should be transmitted along the other path).  We do this in our FCoE setup by defining a different VSAN for Fabric A and Fabric B.  Since in this example the SAN is a NetApp 3210, I used VSAN3210 for Fabric A and VSAN3211 for Fabric B.
In your UCS Console, under the SAN Tab, open up SAN Cloud, then Fabric A.  Right click on VSANs and define VSAN3210 as shown:

Notice you have to define an FCoE VLAN as well?  We’ll get to that in a bit.  You can make this a different number if you want but it’s much easier to work with if you keep the numbers the same.  Make very sure that Default Zoning is set to Disabled, and that the fabric is set to Fabric A.
Now repeat this for Fabric B; using the number 3211 instead of 3210, and making sure to select the Fabric B radio button.