|
Classes
FinalExam
Troubleshooting
edit SideBar
|
Class07
Class07 as slideshow
VLANs and QoS
Domains
- collision domain
- bounded by L2 device, like a switch
- broadcast domain
- bounded by L3 device, like a router
Areas
- WAN
- "other" side of the router
- LAN
- VLAN
- LAN without geographical constraints (assuming this is technically possible)
802.1Q
Layer 2 header, Ethernet
- maximum 1518 bytes total
- destination MAC address
- source MAC address
- frame type
- payload
Layer 2 header, 802.1Q
- 4 bytes larger, maximum 1522 bytes total
- 2 octets for Tagged Protocol Identifier, 0x8100
- 3 bits for priority, 802.1p
- 1 bit for Canonical Format Indicator
- 12 bits for VLAN ID, 802.1Q
Layer 2 header, 802.1Q
- 12 bits: VLAN IDs range from 1 to 4094
- 1 is DEFAULT
- 0 and 4095 are not allowed
802.1p priority
- priority
- immediate
- flash
- flash override
- critical
- internetwork control
- network control
More About 802.1p
For more on 802.1p, I like Bringing Prioritization Services to Ethernet, then maybe Directing Your Network Traffic and Implementing Prioritization for IP Networks if you want to read more. It's really a pretty painless introduction to 802.1p.
VLAN Facts of Life
- 802.1Q adds 4 bytes to Ethernet packets between the Layer 2 (Ethernet) header and the Layer 3 leader, increasing the maximum packet size from 1518 to 1522 bytes; 3 bits are for the 802.1p Ethernet class of service and 12 bits are for the 802.1Q VLAN ID.
- A VLAN, by definition, provides broadcast containment. Broadcasts (Windows browser elections, Bonjour) are contained within the VLAN.
VLAN Facts of Life
- Your IP address determines your IP subnet (of course). Your IP subnet uniquely determines your 802.1Q VLAN. Each VLAN can have several subnets, but each subnet has one and only one VLAN. If the VLAN on your switch port doesn't match your IP address subnet, you can't communicate on the network (except at Layer 2, but the user reports no network connectivity).
- For traffic to travel between VLANs, it must go to the router port defined for that VLAN (your gateway). In the simplest case, it then goes through the routing engine and out the router port for the destination VLAN. (It could also go from the routing engine on one router to the routing engine on another router, and then out the router port for the destination VLAN.) Each router knows what subnets match the VLANs it manages, and it knows what router to send packets for the VLANs it doesn't manage.
QoS
- a short walk from VLANs to QoS
- quality
- Quality of Service for packet networks is the assurance that certain special packets will encounter fewer problems on the network than all other packets.
- QoS processing may delay all packets, up to 10x latency
- at most 10% of packets can be special
- QoS must be end-to-end
- flip side: policing, or dropping packets
- CoS
QoS Categories
- number of priorities
- OSI layer
- hard (absolute) or soft (relative)
- static (management) or dynamic (signaling)
- bandwidth broker or policy server
- bandwidth control, prioritization, and/or traffic control
- network engineering or traffic engineering
- active (oversubscription) or proactive (overprovisioning)
- let's fill in this chart as we go!
Simple QoS
- more bandwidth
- very common, but requires money
- brute force, or enlightened overprovisioning?
- switch queuing
QoS: IP ToS
- ToS octet
- 3 bits for IP precedence
- 4 bits for DTR˘ (least Delay, most Throughput, most Reliability, least ˘o$t: pick one)
- 1 bit zero/unused
QoS: 802.1p
- 8 levels, like ToS
- what's different?
QoS: 802.1p priorities
- priority
- immediate
- flash
- flash override
- critical
- internetwork control
- network control
QoS: DiffServ
- reuse ToS octet as DiffServ Code Point
- Class Selector, also like ToS
- Per-Hop Behavior
- 3 PHBs and 5 services out of 64 values!
QoS: DiffServ
- Assured Forwarding
- low drop probability
- medium drop probability
- high drop probability
- Expedited (explicit) Forwarding
- don't forget, Best Effort is a type of QoS (PHB)
Best Practices for DSCP
- CS, class selector: re-use the
xxx000 values from IP precedence
- don't rewrite existing "standards"
- AF, assured forwarding: classes 1 through 4, drop probabilities 1 through 3
- EF, explicit forwarding
Best Practices for DSCP
| DSCP | Binary value | Decimal value |
| Default | 000000 | 0 |
| CS1 | 001000 | 8 |
| AF11 | 001010 | 10 |
| AF12 | 001100 | 12 |
| AF13 | 001110 | 14 |
| CS2 | 010000 | 16 |
| AF21 | 010010 | 18 |
| AF22 | 010100 | 20 |
| AF23 | 010110 | 22 |
| CS3 | 011000 | 24 |
| AF31 | 011010 | 26 |
| AF32 | 011100 | 28 |
| AF33 | 011110 | 30 |
| CS4 | 100000 | 32 |
| AF41 | 100010 | 34 |
| AF42 | 100100 | 36 |
| AF43 | 100110 | 38 |
| CS5 | 101000 | 40 |
| EF | 101110 | 46 |
| CS6 | 110000 | 48 |
| CS7 | 111000 | 56 |
QoS: IntServ
- uses a central router for admission control
- explicit reservation with RSVP, out of band signaling
- not used
QoS: SBS
WAN
- what happens on another network?
- what happens with another network administrator?
MPLS
MPLS separates packet forwarding from packet routing
- DTR
- EOS
- MPLS' TTL
- other terms
- Label-Switched Paths
- Label Distribution Protocol
QoS Comparison
| Name | Number of Levels | OSI Layer | Hard or Soft | Static or Dynamic | Bandwidth Broker or Policy Server | Functional Types | Engineering | Active or Proactive |
| more bandwidth | 1 | 1 | Soft, Relative | Static, Management | none ($) | Bandwidth Control | Network Engineering | Proactive, Overprovisioning |
| traffic shaping (like Packeteer) | 1 | 1 | Soft, Relative | Static, Management | Policy Server | Traffic Control | Traffic Engineering | Active, Oversubscription |
| SBS | 2 | 1 | Soft, Relative | Static, Management | none ($) | Prioritization | Network Engineering | Proactive, Overprovisioning |
| 802.1p | 8 | 2 | Soft, Relative | Static, Management | Policy Server | Bandwidth Control, Prioritization | Per-Device (Network) Engineering | Active, Oversubscription |
| switch queues | 8 | 2 | Soft, Relative | Static, Management | Policy Server | Prioritization | Per-Device Engineering | Active, Oversubscription |
| ToS | 8 | 3 | Soft, Relative | Static, Management | none (per-device) | Prioritization | Per-Device Engineering | Active, Oversubscription |
| DiffServ | 64 | 3 | Soft, Relative | Static, Management | Policy Server | Bandwidth Control, Prioritization | Per-Device Engineering | Active, Oversubscription |
| IntServ | 256 | 3 | Hard, Absolute | Dynamic, Signaling | Bandwidth Broker | Bandwidth Control, Prioritization | Per-Device Engineering | Active, Oversubscription |
When to use QoS
- scope
- external: identify issue, work with ISP
- internal: identify, fix
- time
- latency: find, upgrade
- jitter: find, then upgrade or shape traffic
- congestion
- always: add bandwidth
- critical times: prioritize traffic
- sometimes: plan for upgrade
Where to use QoS
edge switches run at about 0.2% CPU utilization
- policing: as close to edge as possible
drop before congestion
expedite where congestion is more likely thanks to aggregation
Which QoS is Best?
- least intrusive
- most effective
- 802.1p (expedited, not policed)
- most managable
QoS Selector
QoS flowchart
QoS and Network Management
- Where does QoS fit in with Network Management?
- Are they different subjects?
VLAN Reminders
- Your IP address determines your IP subnet (of course). Your IP subnet uniquely determines your 802.1Q VLAN. Each VLAN can have several subnets, but each subnet has one and only one VLAN. If the VLAN on your switch port doesn't match your IP address subnet, you can't communicate on the network (except at Layer 2, but the user reports no network connectivity).
- 802.1Q adds 4 bytes to Ethernet packets between the Layer 2 (Ethernet) header and the Layer 3 leader, increasing the maximum packet size from 1518 to 1522 bytes; 3 bits are for the 802.1p Ethernet class of service and 12 bits are for the 802.1Q VLAN ID.
VLAN Reminders
- A VLAN, by definition, provides broadcast containment. Broadcasts (Windows browser elections, Bonjour) are contained within the VLAN.
- For traffic to travel between VLANs, it must go to the router port defined for that VLAN (your gateway). In the simplest case, it then goes through the routing engine and out the router port for the destination VLAN. (It could also go from the routing engine on one router to the routing engine on another router, and then out the router port for the destination VLAN.) Each router knows what subnets match the VLANs it manages, and it knows what router to send packets for the VLANs it doesn't manage.
Example: DHCP
- remember that a user port has one and only one VLAN
- remember that your IP address (and netmask) → your IP subnet → your VLAN
- The end-user implications for this are that if you are a mobile computer user and take your laptop to/from one location to another on campus, you must be registered for and configured to use campus DHCP service. You should also be aware of the fact that, when you do go from one building to another, you must either do a complete shutdown or an "ipconfig /release", followed by an "ipconfig /renew" in order to get a new DHCP lease that's appropriate for the routed domain to which you've moved.
Light Reading
Reading
Homework
|