Transcript Auto Provisioning

Synergi Nortel Telefoni & Data
Asko Hotakainen
Senior Sales Engineer
Why did the World Converge Around IP/Ethernet?
• Effective – Ethernet and IP did the job as well as any
alternative technology at the time
• Simple – Ethernet was much simpler than the alternative
technologies. This lead to less complex networks, which in
turn drove down costs, fueled growth and increased the
pace of innovation.
• Cost – A plethora of vendors and wide ranging standards
drove choice and reduced interoperability issues. This
drove commoditization, further fueling innovation as
organizations looked to find and edge and further reduce
costs.
2
Standard LAN designs
Common Designs
Common Capabilities
Common Components
5500 Edge
Uniform Strategy
Uniform Applications
Uniform Benefits
4500 Edge
2500 Edge
5500 SMLT Core
Small
8300 SMLT Core
8600 SMLT Core
Medium
Large
3
Common Key Benefits
Workstation
IP Phone
WLAN Access Points
IP Phone
Resilient Stackable
edge for flexibility in
delivering required
edge connectivity
10/100 or Gig
access ports with
PoE, access
control and auto
configuration
Multi-homed
interconnects use
standard link
aggregation for
performance,
resilience and
interoperability
Choice of 100-FX, 1G
& 10G interconnect
options to deliver the
required bandwidth
Core Switch Clustering
with SMLT delivers subsecond fail-over and is
fully load-balanced to
provide best possible
application performance
Laptop PC
Application
Server
WAN Router
Telephony Server
Dual-homed Servers
& WAN Routers
ensure availability of
critical services
4
Auto Provisioning
Deploying IP Telephony
How do I put all this together
Ethernet Edge
Switches
Voice
Data
and make it work ?
Core
IP Phones
Video
VLANs
Voice VLAN
& QoS
Quality
of
Service
5
Auto Provisioning
Putting the Pieces Together
802.1AB
• Uses Link Layer Discovery Protocol (LLDP)
• Exchanges capabilities/information of connected devices
• Builds topology of connected devices
• Can be used for configuration of network devices
• Discovery of Ethernet
Switch and IP Phone
• Topology of Ethernet
Switch and IP Phone
• Configuration of IP
Phone
Auto Detect Auto Config (ADAC)
• Nortel Ethernet Switch feature
• Discovers IP phones connected to it
• Automatically configures Voice VLAN and QoS
• Works in conjunction with 802.1AB
Configuration of Ethernet
Switch
DHCP/TFTP
• Provides basic IP configuration information to IP phone
• Configuration options for call server, VLAN, etc.
• VLAN auto discovery via DHCP site specific option
Configuration of IP
Phone
6
802.1AB
Overview
• The IEEE 802.1AB Link Layer Discovery Protocol (May 2005)
defines a standard way for Ethernet devices to advertise information about
themselves to their network neighbors and store information they discover
from other devices
Router
Switch
LLDP
LLDP
Network
Management
Station
IP Phone
MIB
MIB
• The devices store information in local MIB databases accessible via SNMP
• A network management system retrieves the data stored by each device
and builds a network topology map
7
802.1AB
Overview
• The information fields in each frame are contained in a Link
Layer Discovery Protocol Data Unit (LLDPDU) as a sequence of short,
variable-length, information elements known as TLVs that each
include type, length, and value fields
• Each LLDPDU includes four mandatory TLVs plus optional TLVs –
Optional TLVs may be inserted in any order
Core TLV’s
Organizational TLV’s
MED TLV’s
• Chassis ID
• Port ID
• Time to Live
• Port Description
• System Name
• System Description
• System Capabilities
• Management Address
• End of LLDPDU
• Port VLAN ID
• Port & Protocol VLAN ID
• VLAN Name
• Protocol Identity
• MAC/PHY Config Status
• Power via MDI
• Link Aggregation
• Maximum Frame Size
• LLDP/MED Capabilities
• Network Policy
• Location Identification
• Extended Power via MDI
• Inventory (HW, FW, SW,
Serial Number,
Manufacturer Name,
Model Name, Asset ID)
8
IP Phone Voice VLAN Configuration
LLDP VLAN Name
• LLDP VLAN Name (802.1) used to configure the Voice VLAN on
the IP Phone
• Voice VLAN must be configured on Ethernet switch
• Ethernet switch is configured to provide Voice VLAN ID to the IP
phone via 802.1tx TLV VLAN Name
• IP phone “knows” to listen for Voice VLAN via LLDP
LLDP
190
Phone Configures
itself to use
VLAN ID 190 and
continues with
it’s configuration
process (DHCP)
LLDP
with
VLAN
ID 190
Voice VLAN ID = 190
9
ERS4500 v5.2
802.1AB Enhancements
• 802.1AB MED support
• Current 802.1AB discovery is via system TLV IP Phone bit
• Enable full MED exchange with IP Handset to specify VLAN
and QoS
• 802.1AB Location TLV
• Support location based TLV, essential for E911 support
ERS2500 v4.2
ERS4500 v5.2
10
Auto Detect Auto Config
(ADAC)
11
ADAC – Auto Detection Auto Configuration
Overview
• Enables Nortel Ethernet Switches to automatically detect and configure
ports for use with IP phones
• Auto Detection of IP phones can be accomplished one of two ways
• MAC address of the IP Phone
• 802.1AB LLDP
• Auto Configuration of the Ethernet switch can include:
• Voice VLAN for the IP phone
• QoS marking of all voice packets entering the Ethernet switch
• The auto configuration of the Ethernet switch is dynamic and requires no
user intervention
• ADAC can be used in conjunction with 802.1x EAP
• ADAC can be used for connections that have an IP phone and PC
connected to a single port
12
Auto Configuration
QoS on ERS 5500
• Auto Configuration of QoS
• Two policies (each w/ one classifier) are used depending on operating
mode and port type
• All IP Traffic Filter
• A policy with a classifier to filter all IPv4 traffic and remark it with DSCP 0x2E and
802.1p priority to 0x06
• This policy is installed on Telephony ports in Untagged mode and on Call Server port
• Tagged Voice Traffic Filter
• A policy with a classifier to filter the traffic tagged with the Voice VLAN and remark it
with DSCP 0x2E and 802.1p priority to 0x06
• This policy is installed on Telephony ports in Tagged mode and on the Uplink ports
• The QoS filters are created internally and automatically and therefore cannot be
seen or modified when managing the switch
13
ERS4500 v5.2
NT-on-NT QoS Support
• Provide a new capability to enable Nortel application prioritisation on Nortel
switching platforms
• Recognises Nortel application specific DSCP marking of IP packets and
provides priority on these applications into appropriate queues
Traffic Type
VoIP Data (Premium)
VoIP Signaling (Platinum)
Video (Platinum)
Streaming (Gold)
NT
DSCP
0x2F (47)
0x29 (41)
0x23 (35)
0x1B (27)
CoS Drop
Precedence
6
Low
5
Low
5
Low
4
Low
Standard
DSCP
0x2E (EF)
0x28 (CS5)
0x22 (AF41)
0x1A (AF31)
• CLI Command Examples:
To enable the nt-on-nt mode
4548GT(config)#qos agent nt mixed
To disable the nt-on-nt mode
4528GT(config)#qos agent nt disable
New on ERS4500 v5.2
14
Nortel Automatic QoS (NAQ) Support
ERS 5500 v6.1
• Supports prioritizing traffic marked with recognized Nortel
DSCP values
• Pure and Mixed modes
• Pure: update 802.1p, leave DSCP unchanged
• Mixed: update 802.1p, remark DSCP to equivalent “standard”
value
• NAQ filters augment Trusted/Untrusted/Unrestricted QoS
interface processing support
• Enabled/disabled through QoS Agent
NAQ Enable: qos agent nt-mode [pure | mixed]
NAQ Disable: qos agent nt-mode disable
15
Nortel Automatic QoS (NAQ) Support
Traffic Type
QoS Classification
Nortel Automatic
QoS DSCP
CoS
Standard
DSCP
VoIP
Premium – EF
0x2F (47)
6
0x2E
VoIP Signaling
Platinum – CS5
0x29 (41)
5
0x28
Video Conf
Platinum – AF41
0x23 (35)
5
0x22
Streaming
Gold – AF31
0x1B (27)
4
0x1A
16
CS1000 Configuration for Auto QoS
17
Autoprovisioning
TFTP based ”no touch” install of IP phones
Auto Provisioning
• Possible to configure via Auto Provisioning
• All options from Network Configuration menu, as per Expanded
DHCP Options
• Contrast, brightness and backlight from Display menu
• Node and TN
• Auto VLAN is still used to provide Voice VLAN ID via DHCP
• Intent is to add Auto Provisioning capability for Voice VLAN ID
subsequently
• Alternatively use LLDP to provide VLAN information
• Supported on 11x0, 12x0 and 2007 only
• Not supported on 2001 / 2002 / 2004 sets – and no intent to add
support for same
19
19
Auto Provisioning Hierarchy
• Since multiple modes of configuration information now exist, a
hierarchy must be employed for configuration information
• Hierarchy as follows in order of precedence
• Manual Configuration
** DHCP could be used to provide
• Prov Server – device specific
the provisioning server info, at
which point the set would then
• Prov Server – zone specific
query the provisioning server for
the relevant files. Nortel options
• Prov Server – model/type specific
(S1, S2 etc.) would not need to be
• TFTP – system specific
added to the DHCP scope and
would anyway be overwritten by
• LLDP-Med
the auto provisioning process.
• DHCP (Nortel-i2004-B) **
• DHCP (Nortel-i2004-A) **
• UNIStim(for some specific device / network paramaters only)
• Last value received
• Factory default
20
20
Auto Provisioning
• Each phone can be configured via a combination of
different files from the provisioning server
• Phone boots and attaches to the network (runs through
802.1x, 802.1ab, DHCP as applicable)
• Receives the provisioning server address via DHCP Option
66 (or via manual configuration)
• System level, zone level, phone type level and device level
files can be on provisioning server – one, some or all of these
• Provisioning server is supplied by customer or channel
partner, i.e. not part of the Nortel solution
• User will not be required to enter any information
• Assuming an entry exists for the user’s MAC address in one
of the files above
21
21
Provisioning Files
• System level file SYSTEM.PRV
• System specific provisioning information
• “file” parameter indicates which other files (if any) are to be
downloaded via TFTP – line below indicates phone type (t),
device (d) and zone (z) files should all be pulled via TFTP
file=tdz;
• Model level file TTTT.PRV
• Phone type specific provisioning information
• For example – to turn on/off Bluetooth on all 1140E sets
• TTTT replaced by phone model, e.g. 1140e.prv
• 1110,1120E,1140E,1150E,2007,1210,1220,1230 as valid
options
22
22
Provisioning Files
• Zone level file ZZZZZ.PRV
• Zone specific provisioning information, where ZZZZZ is the
one to eight character Zone ID
• Zone ID can be set manually, via DHCP or via “zone”
parameter in SYSTEM.PRV
• Device level file XXXXXXXXXXXXXXXX.PRV
• Device specific provisioning information, where XX… is the
MAC address of the device
• Can also “mix and match” – e.g. can have a number of
MAC address / node / TN mappings in the system level file
for example, rather than multiple device level files
23
23
Provisioning Files
• The files used depend on the level of granularity required
by the customer
• Customer might only have a SYSTEM.PRV file and
include some generic information therein (e.g. enable
LLDP for all devices), along with all MAC / node / TN
mapping …
• Customer might have a SYSTEM.PRV file, an1140E.PRV
file to enable Bluetooth, a zone based file to modify
contrast for an area with very bright lighting, as well as
individual DEVICE.PRV files per set
• Changing some parameters (e.g. LLDP) automatically
causes a reset of the IP set when it downloads the
updated value
24
24
Provisioning Files
• Below is an example of the MAC / node / TN mapping in a
SYSTEM.PRV file
• The first line defines the relevant Call Server IP address
• The second line is the registration information for one
particular set, which contains MAC address, Call Server
type (only CS1K supported at this time), S1 (valid values
of S1 or S2 or S1S2), Node ID and TN
s1ip=47.165.164.32;
reg= 001365FEF3E2 CS1K S1 21 96-0-4-5;
25
25
Autoprovisioning config file example
s1ip=47.11.62.20;
/* Primary server IP address */
p1=4100;
/* Primary server port number */
a1=1;
/* Primary server action code */
r1=10;
/* Primary server retry count */
s2ip=47.11.62.21;
/* Secondary server IP address */
p2=4100;
/* Secondary server port number */
a2=1;
/* Secondary server action code */
r2=10;
/* Secondary server retry count */
xip=47.11.62.147;
/* XAS server IP address */
xp=5000;
/* XAS server port number */
xa=g;
/* XAS server action code */
unid=Main-tower;
/* Unique network identification */
menulock=p;
/* Menu lock mode */
26