Enabling IP Communication

Copyright 2008 Juniper Networks, Inc.

Proprietary and Confidential

www.juniper.net

Enabling IP Communication Agenda

Power over Ethernet (PoE)

Voice VLAN

LLDP

LLDP-MED

Copyright 2008 Juniper Networks, Inc.

Proprietary and Confidential

www.juniper.net

Enabling IP Communication Agenda

Power over Ethernet (PoE)

Voice VLAN

LLDP

LLDP-MED

Copyright 2008 Juniper Networks, Inc.

Proprietary and Confidential

www.juniper.net

Understanding Power over Ethernet (PoE)

Power over Ethernet (IEEE 802.3af) is the ability
to deliver regulated -48V DC power over a
standard copper Ethernet network cable

Power is utilized by connected devices for
operation

Copyright 2008 Juniper Networks, Inc.

Proprietary and Confidential

www.juniper.net

Components of Power over Ethernet (PoE)

Two primary components of a PoE deployment:
Power sourcing equipment (PSE) such as a EX 3200
or 4200 series switch

Powered device (PD) that accepts and utilizes

delivered power

Copyright 2008 Juniper Networks, Inc.

Proprietary and Confidential

www.juniper.net

802.3af Power over Ethernet

IEEE 802.3af has an optional power classification
feature and should be a minimum requirement for
any PoE deployment

LAN switch (PSE) budgets require power based
upon the class of attached devices

Significantly reduces power capacity
requirements
With power classification: Switch identifies power
needs and reserves power based upon class
Without power classification: Unclassified devices
treated as default (class 0) with full 15.4W power
budgeted per port
Copyright 2008 Juniper Networks, Inc.

Proprietary and Confidential

www.juniper.net

802.3af Power over Ethernet (PoE) Class

Number and Corresponding Max Power
Class Number

0 (default)

Copyright 2008 Juniper Networks, Inc.

Max Power at output port of PSE

15.4 watts reserved
(actual device requirement can be much less)

4 watts

7 watts

15.4 watts

Future Expansion

Proprietary and Confidential

www.juniper.net

Understanding PoE Power Management

Types

Static Mode
The power deducted from total power pool is the
maximum power specified by the user for that
interface. This mode ensures that the maximum power
specified by the user for that interface is always
reserved

Dynamic Mode (Roadmap)

The power budgeted from total power pool for each
port is the actual power consumed at that port

Class Mode (Roadmap)

The power budgeted for each port from the total power
pool is the maximum power of the class of PD
connected to that port

Copyright 2008 Juniper Networks, Inc.

Proprietary and Confidential

www.juniper.net

Understanding PoE Total Power Pool

There are 3 different power
supply capacities: 320, 600,
930W

Any power supply can be
installed on any Stand-alone
or Virtual-Chassis switch
model. However, installing
higher capacity power supply
will not increase the number
of PoE supported on the
switch
For example, installing 930W
power supply on 24-port
partial PoE switch will not
increase the number of PoE
ports to 24
Copyright 2008 Juniper Networks, Inc.

Power Supply
Capacity

320W

600W

930W

Proprietary and Confidential

Switch
Consumption

Power Budget
for PoE Pool

190W

130W
(8 PoE Ports
at 15.4W
each)

190W

410W
(24 PoE Ports
at 15.4W
each)

190W

740W
(48 PoE Ports
at 15.4W
each)

www.juniper.net

Scenario 1 Smaller Capacity Power Supply

with Full PoE Switch

In case of power supply deficiency such as
having 320W power supply on a 24-port switch
with full PoE support, the first 8 ports that are
connected to PD will be provided with power

The first 8 ports refer to ports 0 through 7

Copyright 2008 Juniper Networks, Inc.

Proprietary and Confidential

www.juniper.net

10

Scenario 2 Redundant Power supplies

with different capacities

In case where redundant power supplies are
installed on a switch where capacities are not
equal to each other, the switch will budget the
total power pool based on more conservative
capacity power supply
For example, there are two power supplies installed on a
switch: 320W and 930W
In this case, total PoE pool available for ports are based on
320W (130W for pool, 8 PoE ports) rather than 930W
This is done to prevent power loss on already powered ports
in case of power supply failure or hot-swap
Dual power supplies cannot be combined into a single pool
equal to the sum of the two
Copyright 2008 Juniper Networks, Inc.

Proprietary and Confidential

www.juniper.net

11

Scenario 3 Power Pool Reduction

In case where all power available is used up and switch
experiences reduction of power, user can configure PoE port
priority which PoE ports should be provided with power while
disabling power on others until enough power is available to
remaining PoE ports
Priority is either low (default) or high
In case of power pool reduction, switch will start eliminating power
to low priority ports then high priority ports until there are enough
PoE power available in pool

When PoE ports are at same priority, port with higher interface
number will be eliminated with power before lower one
For example, when there are ge-0/0/5 and ge-0/0/9 with same
priority, switch will eliminate power to ge-0/0/9 before ge-0/0/5

Copyright 2008 Juniper Networks, Inc.

Proprietary and Confidential

www.juniper.net

12

Enabling IP Communication Agenda

Power over Ethernet (PoE)

Voice VLAN

LLDP

LLDP-MED

Copyright 2008 Juniper Networks, Inc.

Proprietary and Confidential

www.juniper.net

13

Understanding Voice VLAN

In order to reduce switch port count, common enterprise VOIP edge

deployment consists of a pair of IP phone and end-host machine
connected in tandem that are attached to the same switch port

Good VOIP solution requires separation of voice and data traffic in
the network
Sound quality of an IP phone call can deteriorate when large bursts of
data traffic creates network congestion that leads to packet loss or delay
Its desirable to provide higher end-to-end SLAs to voice traffic due to its
susceptibility to jitter, delay and packet loss

The voice VLAN feature enables access ports to accept both

untagged (data) and tagged (voice) traffic from directly connected IP
phones and separate these traffic into different VLANs (namely data
VLAN and Voice VLAN)
Copyright 2008 Juniper Networks, Inc.

Proprietary and Confidential

www.juniper.net

14

Voice VLAN Guidelines

Before voice VLAN enabled, it is recommend that
CoS is enabled on the switch

Voice VLAN should be configured on switch access
ports

LLDP-MED can be used by the switch port to instruct
the attached IP phones which Voice VLAN ID and
802.1p value to use

Copyright 2008 Juniper Networks, Inc.

Proprietary and Confidential

www.juniper.net

15

Enabling IP Communication Agenda

Power over Ethernet (PoE)

Voice VLAN

LLDP

LLDP-MED

Copyright 2008 Juniper Networks, Inc.

Proprietary and Confidential

www.juniper.net

16

Understanding LLDP

Link Layer Discovery Protocol (IEEE 802.1AB)
is a Layer 2 protocol that allows network devices
to advertise their identity and capabilities on the LAN

When LLDP is enabled on a device, it is called an
LLDP agent
LLDP exchanges occur between LLDP agents

Simple one-way neighbor discovery protocol with

periodic transmissions of LLDPDU

LLDP frames are constrained to a local link

Copyright 2008 Juniper Networks, Inc.

Proprietary and Confidential

www.juniper.net

17

Understanding LLDP LLDPDU Updates

LLDP periodic updates restricted to 1 per second
(default is 30 sec, recommended minimum is 2 sec)

One-way advertisements only: no REQ or ACK

Anytime a local value changes, LLDP sends a frame
(triggered update)
Update conforms to 1 per second limit

LLDP itself is stateless

LLDP has no authentication

Copyright 2008 Juniper Networks, Inc.

Proprietary and Confidential

www.juniper.net

18

Enabling IP Communication Agenda

Power over Ethernet (PoE)

Voice VLAN

LLDP

LLDP-MED

Copyright 2008 Juniper Networks, Inc.

Proprietary and Confidential

www.juniper.net

19

Understanding LLDP-MED

LLDP-MED (media endpoint devices) is an extension
to LLDP developed by TIA (ANSI/TIA-1057) to
support interoperability between VoIP endpoint
devices and other networking end-devices

LLDP-MED is focused mainly on discovery running
between network devices and end-points such as
IP phones

Copyright 2008 Juniper Networks, Inc.

Proprietary and Confidential

www.juniper.net

20

Usage of LLDP-MED

Network policy discovery: Lets end-points and
switches advertise their VLAN IDs (e.g. voice VLAN),
priority and DSCP; switch can instruct end-devices
to modify their settings to match switch requirements

PoE management: Lets endpoint devices advertise

PoE level and priority they require; also lets PSEs
(e.g. PoE-capable switches) advertise power
offerings
Copyright 2008 Juniper Networks, Inc.

Proprietary and Confidential

www.juniper.net

21

Usage of LLDP-MED (cont.)

Inventory management discovery
Information such as vendor, model, firmware and
serial number of end-point devices is stored on
switch and is accessible to network management
system for inventory reporting

End-point location discovery
Switch gets end-devices exact location; uses this
information to communicate with public safety
answering point and also for emergency call services

* Note: Inventory Management Discovery and End-point Location Discovery are roadmap items.
Copyright 2008 Juniper Networks, Inc.

Proprietary and Confidential

www.juniper.net

22

Understanding Interaction
Between LLDP and LLDP-MED

LL
DP
-M
ED

LL
DP
-M
ED

2. LLDP-MED frame
sent by neighbor

LL
DP

All mandatory LLDP TLVs will be advertised in

LLDPDUs as soon as LLDP is enabled

All optional LLDP and LLDP-MED TLVs are also
enabled by default (can be disabled explicitly)

LLDP-MED TLVs will be sent only after detecting a
MED device

1. Interface will start

advertising Base LLDP
TLVs (non-LLDP-MED)

3. Agent will toggle

to LLDP-MED

Copyright 2008 Juniper Networks, Inc.

Proprietary and Confidential

www.juniper.net

23

LLDP/LLDP-MED and 802.1X

LLDP-MED and 802.1X provide robust and
secure solutions
LLDP frames will be advertised and processed only
when a secure port enters authenticated state
When 802.1X is enabled, LLDP frames will not be
transmitted or received until port is authenticated
An IP phone and PC connected to a port can be
authenticated separately (multiple supplicant mode)
and can receive different VLAN assignments and
policies for data and voice

Copyright 2008 Juniper Networks, Inc.

Proprietary and Confidential

www.juniper.net

24

LLDP / LLDP-MED Walk-through

How does it work?
SNMP
Information

ge-0/0/0

Gateway

xxxx

ge-0/0/1

IP phone

xxxx

ge-0/0/2

PC

xxxx

ge-0/0/3

Switch

xxxx

Management
Application
Im
IP Ph a
one

I
sw m a
itc
h

IP Im
Ph a
on
e

Im
Ga a
te Vo
w a IP
y

Im a

Copyright 2008 Juniper Networks, Inc.

SNMP
Im a

Im
switca
h

Im
switca
h

I
sw m a
itc
h

Device

I
sw m a
itc
h

Port

PC

Im a
switch

Port

Device

Information

ge-0/0/0

Switch

xxxx

ge-0/0/1

IP phone

xxxx

ge-0/0/2

PC/Server

xxxx

ge-0/0/3

PC/Server

xxxx

PC

Proprietary and Confidential

www.juniper.net

25

Copyright 2008 Juniper Networks, Inc.

Proprietary and Confidential

www.juniper.net

26