Ip Phone Boot Up Process 476g2e
This document was ed by and they confirmed that they have the permission to share it. If you are author or own the copyright of this book, please report to us by using this report form. Report 3b7i
Overview 3e4r5l
& View Ip Phone Boot Up Process as PDF for free.
More details w3441
- Words: 1,963
- Pages: 8
IP Phone Boot up Process | Unified Communications Applications | Cisco Community | 5971 | 104191
Cisco Community
Search Home/ Collaboration, Voice and Video/ Unified Communications Applications
Search Unified Communications Applications Cisco Community Cisco.com
Language:
IP Phone Boot up Process
English
Us
Follow Us
Document
Help
Tue, 10/27/2015 - 23:54
Community Directory
shalushar 3 years ago
Expert Corner Table of Contents [hide]
Introduction Voice Vlan Concepts VLAN Trunking/Tagging
Community Corner Solutions Community Resources Cisco
VLAN Configuration Understanding the Cisco IP Phone Boot Process IP Phone Network Configuration File Not Found - Cisco IP Phone 7940 boot up error Related Links
Introduction This document describes the boot up process of IP phone and Voice VLAN concepts.
Voice Vlan Concepts When VLANs were introduced a number of years ago, the concept was so radical and beneficial that it was immediately adopted into the industry. Nowadays, it is rare to find any reasonably sized network that is not using VLANs in some way. VLANs allow you to break up switched environments into multiple broadcast domains. Here is the basic summary of a VLAN: A VLAN = A Broadcast Domain = An IP Subnet
https://forums.cisco.com/document/104191/ip-phone-boot-process[11/3/2015 9:31:06 AM]
IP Phone Boot up Process | Unified Communications Applications | Cisco Community | 5971 | 104191
VLAN Trunking/Tagging
If a member of VLAN A sends a broadcast message, it goes to all VLAN A ports on both switches. The same holds true for VLAN B. To accommodate this, the connection between the switches must carry traffic for multiple VLANs. This type of port is known as a trunk port. Trunk ports are often called tagged ports because the switches send frames between each other with a VLAN "tag" in place. It illustrates the following process: 1. HostA (in VLAN A) wants to send data to HostD (also in VLAN A). HostA transmits the data to SwitchA. 2. SwitchA receives the data and realizes that HostD is available through the FastEthernet 0/24 port (because
HostD's MAC address has been learned on this port). Because FastEthernet 0/24 is configured as a trunk port, SwitchA puts the VLAN A tag in the IP header and sends the frame to SwitchB. 3. SwitchB processes the VLAN A tag because the FastEthernet 0/24 port is configured as a trunk. Before sending
the frame to HostD, the VLAN A tag is removed from the header. 4. The tagless frame is sent to HostD.
Using this process, the PC never knows what VLAN it belongs to. The VLAN tag is applied when the incoming frame crosses a trunk port. The VLAN tag is removed when exiting the port to the destination PC. Always keep in mind that VLANs are a switching concept; the PCs never participate in the VLAN tagging process. VLANs are not a Cisco-only technology. Just about all managed switch vendors VLANs. In order for VLANs
https://forums.cisco.com/document/104191/ip-phone-boot-process[11/3/2015 9:31:06 AM]
IP Phone Boot up Process | Unified Communications Applications | Cisco Community | 5971 | 104191
to operate in a mixed-vendor environment, a common trunking or "tagging" language must exist between them. This language is known as 802.1Q. All vendors design their switches to recognize and understand the 802.1Q tag, which is what allows us to trunk between switches in any environment.
Understanding Voice VLANs It is a common and recommended practice to separate voice and data traffic by using VLANs. Separating voice and data traffic using VLANs provides a solid security boundary, preventing data applications from reaching the voice traffic. It also gives you a simpler method to deploy QoS, prioritizing the voice traffic over the data. One initial difficulty you can encounter when separating voice and data traffic is the fact that PCs are often connected to the network using the Ethernet port on the back of a Cisco IP Phone. Because you can assign a switchport to only a single VLAN, it initially seems impossible to separate voice and data traffic. That is, until you see that Cisco IP Phones 802.1Q tagging. The switch built into Cisco IP Phones has much of the same hardware that exists inside of a full Cisco switch. The incoming switchport is able to receive and send 802.1Q tagged packets. This gives you the capability to establish a type of trunk connection between the Cisco switch and IP phone.
You might call the connection between the switch and IP phone a "mini-trunk" because a typical trunk es a large number of VLANs (if not all VLANs). In this case, the IP phone tags its own packets with the correct voice VLAN (VLAN 25). Because the switch receives this traffic on a port ing tagged packets (our mini-trunk), the switch can read the tag and place the data in the correct VLAN. The data packets through the IP phone and into the switch untagged. The switch assigns these untagged packets to whatever VLAN you have configured on the switchport for data traffic. NOTE: Traditionally, a switchport on a Cisco switch that receives tagged packets is referred to as a trunk port. However,
https://forums.cisco.com/document/104191/ip-phone-boot-process[11/3/2015 9:31:06 AM]
IP Phone Boot up Process | Unified Communications Applications | Cisco Community | 5971 | 104191
when you configure a switchport to connect to a Cisco IP Phone, you configure it as an access port (for the untagged data from the PC) while ing tagged traffic from the IP phone. So, think of these ports as "access ports ing tagged voice VLAN traffic."
VLAN Confguration Configuring a Cisco switch to Voice VLANs is a fairly simple process. First, you create VLANs to the switch switch#conf t Enter configuration commands, one per line. End with CNTL/Z. switch(config)#vlan 25 switch(config-vlan)#name VOICE switch(config-vlan)#vlan 50 switch(config-vlan)#name DATA switch(config-vlan)#end switch#show vlan brief
VLAN Name Status Ports ---- -------------------------------- --------- ------------------------------1 default active 9 brat active 25 VOICE active 50 DATA active Sure enough, VLANs 25 (VOICE) and 50 (DATA) now appear as valid VLANs on the switch. Now that the VLANs exist, you can assign the ports attaching to Cisco IP Phones (with PCs connected to the IP Phone) to the VLANs. Switch#configure terminal Switch(config)#interface range fa0/2 - 24 Switch(config-if-range)#switchport mode access Switch(config-if-range)#spanning-tree portfast Switch(config-if-range)#switchport access vlan 50 Switch(config-if-range)#switchport voice vlan 25 Switch(config-if-range)#no shutdown Switch(config-if-range)#end
NOTE:When connecting Cisco IP Phones to a switch, you should also enable portfast (using spanning-tree portfast,), because the IP phones boot quickly and request a DH assigned address before a typical port with spanning-tree enabled would go active. Also, keep in mind that port Fa0/1 does not appear in the above figure output because it is
https://forums.cisco.com/document/104191/ip-phone-boot-process[11/3/2015 9:31:06 AM]
IP Phone Boot up Process | Unified Communications Applications | Cisco Community | 5971 | 104191
configured as a trunk port (ports 2–24 are not considered trunks by Cisco IOS). The ports are now configured to a voice VLAN of 25 and a data VLAN of 50. This syntax is a newer form of configuration for IP Phone connections. In the "old days," you would configure the interface as a trunk port because the switch was establishing a trunking relationship between it and the IP phone. This was less secure because a hacker could remove the IP phone from the switchport and attach their own device (another managed switch or PC) and perform a VLAN-hopping attack. The more modern syntax configures the port as a "quasi-access port," because an attached PC will be able to access only VLAN 50. Only an attached Cisco IP Phone will be able to access the voice VLAN 25. NOTE:Keep in mind that Cisco IP phones will be able to receive this voice VLAN configuration from the switch via CDP. After it receives the voice VLAN number, the IP Phone begins tagging its own packets.
Understanding the Cisco IP Phone Boot Process Here is the Cisco IP Phone boot process, start to finish: The Cisco IP Phone connects to an Ethernet switchport. If the IP phone and switch PoE, the IP phone receives power through either Cisco-proprietary PoE or 802.3af PoE. On Phone: Mute, Headset, Speaker Buttons Are Illuminated As the Cisco IP Phone powers on, the Cisco switch delivers voice VLAN information to the IP phone using CDP as a delivery mechanism. The Cisco IP Phone now knows what VLAN it should use. Phone displays:“Configuring VLAN” The Cisco IP Phone sends a DH request asking for an IP address on its voice VLAN. Phone displays: “Configuring IP”(DNS is optional) The DH server responds with an IP address offer. When the Cisco IP Phone accepts the offer, it receives all the DH options that go along with the DH request. DH options include items such as default gateway, DNS server information, domain name information, and so on. In the case of Cisco IP Phones, a unique DH option is included, known as Option 150. This option directs the IP phone to a TFTP server. After the Cisco IP Phone has the IP address of the TFTP server, it s the TFTP server and s its configuration file. The Cisco IP Phone attempts to the first call processing server (the primary server) listed in its configuration file to . If this fails, the IP phone moves to the next server in the configuration file. This process continues until the IP phone s successfully or the list of call processing agents is exhausted.
IP Phone Network Confguration This video talks about the basics of Network configuration for your IP Phone to get your phone ready to work with Cisco Unified communications Manager
https://forums.cisco.com/document/104191/ip-phone-boot-process[11/3/2015 9:31:06 AM]
IP Phone Boot up Process | Unified Communications Applications | Cisco Community | 5971 | 104191
Video: IP Phone Network Configuration
File Not Found - Cisco IP Phone 7940 boot up error In order to resolve this issue restart the TFTP server.
Related Links IP Phones TFTP IP Phone fails to boot IP Phone, SC & SIP Phone Registration Process with CUCM IP Phone Boot up Process
Overall Rating: 5 (4 ratings)
Comments
or to post comments
Collapse all
Recent replies first
Sebastian Fernandez about a year ago
This is amazing document.. meaty information.. nicely documented.
or to post comments
sansehga 4 months ago
Good document.
or to post comments
mfwilkinson 7 days ago
https://forums.cisco.com/document/104191/ip-phone-boot-process[11/3/2015 9:31:06 AM]
IP Phone Boot up Process | Unified Communications Applications | Cisco Community | 5971 | 104191
+1
or to post comments
Actions or to take actions
This Document Posted June 21, 2012 at 9:59 PM Updated October 27, 2015 at 11:54 PM By shalushar Stats: Comments: Views: Shares:
3 25674 29
Overall Rating: Contributors:
5 3
Tags: up, ip, ip_phone, phone, process
Follow
Shortcut
Abuse
PDF
Related Content Show --Any Any
Apply Apply N7K Changing Logging Severity for Link Events Bilal Nawaz
74 views
CUP Cisco up x text conference manager service doesn't started Sergey Svishenko
61 views
Setting up my Cisco Router (WRVS4400N) smokieskim
178 views
Cisco ASA 5505 Site to Site VPN gordonpcollins
270 views
BLF call pick up group [email protected]
396 views
Trending Topics: UCA https://forums.cisco.com/document/104191/ip-phone-boot-process[11/3/2015 9:31:06 AM]
-
IP Phone Boot up Process | Unified Communications Applications | Cisco Community | 5971 | 104191
Unified communications manager Cisco call manager CUCM
Information For
News & Alerts
About Cisco
Small Business
Newsroom
s
Investor Relations
Midsize Business
Blogs
Documentation
Corporate Social Responsibility
Executives
Field Notices
Home
Security Advisories
Service Provider
Industries s Cisco
Environmental Sustainability
Communities
Tomorrow Starts Here Developer Network
Technology Trends
Career Opportunities
Learning Network
Cloud
Community
IPv6
Programs Cisco Designated VIP Program
Video Portal
Mobility
Cisco Powerered
Open Network Environment
Financing Options
Trustworthy Systems
& Conditions
Privacy Statement
Cookie Policy
https://forums.cisco.com/document/104191/ip-phone-boot-process[11/3/2015 9:31:06 AM]
Trademarks of Cisco Systems, Inc.
Cisco Community
Search Home/ Collaboration, Voice and Video/ Unified Communications Applications
Search Unified Communications Applications Cisco Community Cisco.com
Language:
IP Phone Boot up Process
English
Us
Follow Us
Document
Help
Tue, 10/27/2015 - 23:54
Community Directory
shalushar 3 years ago
Expert Corner Table of Contents [hide]
Introduction Voice Vlan Concepts VLAN Trunking/Tagging
Community Corner Solutions Community Resources Cisco
VLAN Configuration Understanding the Cisco IP Phone Boot Process IP Phone Network Configuration File Not Found - Cisco IP Phone 7940 boot up error Related Links
Introduction This document describes the boot up process of IP phone and Voice VLAN concepts.
Voice Vlan Concepts When VLANs were introduced a number of years ago, the concept was so radical and beneficial that it was immediately adopted into the industry. Nowadays, it is rare to find any reasonably sized network that is not using VLANs in some way. VLANs allow you to break up switched environments into multiple broadcast domains. Here is the basic summary of a VLAN: A VLAN = A Broadcast Domain = An IP Subnet
https://forums.cisco.com/document/104191/ip-phone-boot-process[11/3/2015 9:31:06 AM]
IP Phone Boot up Process | Unified Communications Applications | Cisco Community | 5971 | 104191
VLAN Trunking/Tagging
If a member of VLAN A sends a broadcast message, it goes to all VLAN A ports on both switches. The same holds true for VLAN B. To accommodate this, the connection between the switches must carry traffic for multiple VLANs. This type of port is known as a trunk port. Trunk ports are often called tagged ports because the switches send frames between each other with a VLAN "tag" in place. It illustrates the following process: 1. HostA (in VLAN A) wants to send data to HostD (also in VLAN A). HostA transmits the data to SwitchA. 2. SwitchA receives the data and realizes that HostD is available through the FastEthernet 0/24 port (because
HostD's MAC address has been learned on this port). Because FastEthernet 0/24 is configured as a trunk port, SwitchA puts the VLAN A tag in the IP header and sends the frame to SwitchB. 3. SwitchB processes the VLAN A tag because the FastEthernet 0/24 port is configured as a trunk. Before sending
the frame to HostD, the VLAN A tag is removed from the header. 4. The tagless frame is sent to HostD.
Using this process, the PC never knows what VLAN it belongs to. The VLAN tag is applied when the incoming frame crosses a trunk port. The VLAN tag is removed when exiting the port to the destination PC. Always keep in mind that VLANs are a switching concept; the PCs never participate in the VLAN tagging process. VLANs are not a Cisco-only technology. Just about all managed switch vendors VLANs. In order for VLANs
https://forums.cisco.com/document/104191/ip-phone-boot-process[11/3/2015 9:31:06 AM]
IP Phone Boot up Process | Unified Communications Applications | Cisco Community | 5971 | 104191
to operate in a mixed-vendor environment, a common trunking or "tagging" language must exist between them. This language is known as 802.1Q. All vendors design their switches to recognize and understand the 802.1Q tag, which is what allows us to trunk between switches in any environment.
Understanding Voice VLANs It is a common and recommended practice to separate voice and data traffic by using VLANs. Separating voice and data traffic using VLANs provides a solid security boundary, preventing data applications from reaching the voice traffic. It also gives you a simpler method to deploy QoS, prioritizing the voice traffic over the data. One initial difficulty you can encounter when separating voice and data traffic is the fact that PCs are often connected to the network using the Ethernet port on the back of a Cisco IP Phone. Because you can assign a switchport to only a single VLAN, it initially seems impossible to separate voice and data traffic. That is, until you see that Cisco IP Phones 802.1Q tagging. The switch built into Cisco IP Phones has much of the same hardware that exists inside of a full Cisco switch. The incoming switchport is able to receive and send 802.1Q tagged packets. This gives you the capability to establish a type of trunk connection between the Cisco switch and IP phone.
You might call the connection between the switch and IP phone a "mini-trunk" because a typical trunk es a large number of VLANs (if not all VLANs). In this case, the IP phone tags its own packets with the correct voice VLAN (VLAN 25). Because the switch receives this traffic on a port ing tagged packets (our mini-trunk), the switch can read the tag and place the data in the correct VLAN. The data packets through the IP phone and into the switch untagged. The switch assigns these untagged packets to whatever VLAN you have configured on the switchport for data traffic. NOTE: Traditionally, a switchport on a Cisco switch that receives tagged packets is referred to as a trunk port. However,
https://forums.cisco.com/document/104191/ip-phone-boot-process[11/3/2015 9:31:06 AM]
IP Phone Boot up Process | Unified Communications Applications | Cisco Community | 5971 | 104191
when you configure a switchport to connect to a Cisco IP Phone, you configure it as an access port (for the untagged data from the PC) while ing tagged traffic from the IP phone. So, think of these ports as "access ports ing tagged voice VLAN traffic."
VLAN Confguration Configuring a Cisco switch to Voice VLANs is a fairly simple process. First, you create VLANs to the switch switch#conf t Enter configuration commands, one per line. End with CNTL/Z. switch(config)#vlan 25 switch(config-vlan)#name VOICE switch(config-vlan)#vlan 50 switch(config-vlan)#name DATA switch(config-vlan)#end switch#show vlan brief
VLAN Name Status Ports ---- -------------------------------- --------- ------------------------------1 default active 9 brat active 25 VOICE active 50 DATA active Sure enough, VLANs 25 (VOICE) and 50 (DATA) now appear as valid VLANs on the switch. Now that the VLANs exist, you can assign the ports attaching to Cisco IP Phones (with PCs connected to the IP Phone) to the VLANs. Switch#configure terminal Switch(config)#interface range fa0/2 - 24 Switch(config-if-range)#switchport mode access Switch(config-if-range)#spanning-tree portfast Switch(config-if-range)#switchport access vlan 50 Switch(config-if-range)#switchport voice vlan 25 Switch(config-if-range)#no shutdown Switch(config-if-range)#end
NOTE:When connecting Cisco IP Phones to a switch, you should also enable portfast (using spanning-tree portfast,), because the IP phones boot quickly and request a DH assigned address before a typical port with spanning-tree enabled would go active. Also, keep in mind that port Fa0/1 does not appear in the above figure output because it is
https://forums.cisco.com/document/104191/ip-phone-boot-process[11/3/2015 9:31:06 AM]
IP Phone Boot up Process | Unified Communications Applications | Cisco Community | 5971 | 104191
configured as a trunk port (ports 2–24 are not considered trunks by Cisco IOS). The ports are now configured to a voice VLAN of 25 and a data VLAN of 50. This syntax is a newer form of configuration for IP Phone connections. In the "old days," you would configure the interface as a trunk port because the switch was establishing a trunking relationship between it and the IP phone. This was less secure because a hacker could remove the IP phone from the switchport and attach their own device (another managed switch or PC) and perform a VLAN-hopping attack. The more modern syntax configures the port as a "quasi-access port," because an attached PC will be able to access only VLAN 50. Only an attached Cisco IP Phone will be able to access the voice VLAN 25. NOTE:Keep in mind that Cisco IP phones will be able to receive this voice VLAN configuration from the switch via CDP. After it receives the voice VLAN number, the IP Phone begins tagging its own packets.
Understanding the Cisco IP Phone Boot Process Here is the Cisco IP Phone boot process, start to finish: The Cisco IP Phone connects to an Ethernet switchport. If the IP phone and switch PoE, the IP phone receives power through either Cisco-proprietary PoE or 802.3af PoE. On Phone: Mute, Headset, Speaker Buttons Are Illuminated As the Cisco IP Phone powers on, the Cisco switch delivers voice VLAN information to the IP phone using CDP as a delivery mechanism. The Cisco IP Phone now knows what VLAN it should use. Phone displays:“Configuring VLAN” The Cisco IP Phone sends a DH request asking for an IP address on its voice VLAN. Phone displays: “Configuring IP”(DNS is optional) The DH server responds with an IP address offer. When the Cisco IP Phone accepts the offer, it receives all the DH options that go along with the DH request. DH options include items such as default gateway, DNS server information, domain name information, and so on. In the case of Cisco IP Phones, a unique DH option is included, known as Option 150. This option directs the IP phone to a TFTP server. After the Cisco IP Phone has the IP address of the TFTP server, it s the TFTP server and s its configuration file. The Cisco IP Phone attempts to the first call processing server (the primary server) listed in its configuration file to . If this fails, the IP phone moves to the next server in the configuration file. This process continues until the IP phone s successfully or the list of call processing agents is exhausted.
IP Phone Network Confguration This video talks about the basics of Network configuration for your IP Phone to get your phone ready to work with Cisco Unified communications Manager
https://forums.cisco.com/document/104191/ip-phone-boot-process[11/3/2015 9:31:06 AM]
IP Phone Boot up Process | Unified Communications Applications | Cisco Community | 5971 | 104191
Video: IP Phone Network Configuration
File Not Found - Cisco IP Phone 7940 boot up error In order to resolve this issue restart the TFTP server.
Related Links IP Phones TFTP IP Phone fails to boot IP Phone, SC & SIP Phone Registration Process with CUCM IP Phone Boot up Process
Overall Rating: 5 (4 ratings)
Comments
or to post comments
Collapse all
Recent replies first
Sebastian Fernandez about a year ago
This is amazing document.. meaty information.. nicely documented.
or to post comments
sansehga 4 months ago
Good document.
or to post comments
mfwilkinson 7 days ago
https://forums.cisco.com/document/104191/ip-phone-boot-process[11/3/2015 9:31:06 AM]
IP Phone Boot up Process | Unified Communications Applications | Cisco Community | 5971 | 104191
+1
or to post comments
Actions or to take actions
This Document Posted June 21, 2012 at 9:59 PM Updated October 27, 2015 at 11:54 PM By shalushar Stats: Comments: Views: Shares:
3 25674 29
Overall Rating: Contributors:
5 3
Tags: up, ip, ip_phone, phone, process
Follow
Shortcut
Abuse
Related Content Show --Any Any
Apply Apply N7K Changing Logging Severity for Link Events Bilal Nawaz
74 views
CUP Cisco up x text conference manager service doesn't started Sergey Svishenko
61 views
Setting up my Cisco Router (WRVS4400N) smokieskim
178 views
Cisco ASA 5505 Site to Site VPN gordonpcollins
270 views
BLF call pick up group [email protected]
396 views
Trending Topics: UCA https://forums.cisco.com/document/104191/ip-phone-boot-process[11/3/2015 9:31:06 AM]
-
IP Phone Boot up Process | Unified Communications Applications | Cisco Community | 5971 | 104191
Unified communications manager Cisco call manager CUCM
Information For
News & Alerts
About Cisco
Small Business
Newsroom
s
Investor Relations
Midsize Business
Blogs
Documentation
Corporate Social Responsibility
Executives
Field Notices
Home
Security Advisories
Service Provider
Industries s Cisco
Environmental Sustainability
Communities
Tomorrow Starts Here Developer Network
Technology Trends
Career Opportunities
Learning Network
Cloud
Community
IPv6
Programs Cisco Designated VIP Program
Video Portal
Mobility
Cisco Powerered
Open Network Environment
Financing Options
Trustworthy Systems
& Conditions
Privacy Statement
Cookie Policy
https://forums.cisco.com/document/104191/ip-phone-boot-process[11/3/2015 9:31:06 AM]
Trademarks of Cisco Systems, Inc.
Related Documents 3m3m1z
Ip Phone Boot Up Process 476g2e
November 2019 80
Vista Boot Process 171y5e
March 2023 0
Aix Boot Process 70q1i
December 2019 27
Boot Process In Rhel7 314n2j
June 2022 0
Esx Boot Process 4k1n16
October 2019 36
November 2019 53
More Documents from "Dustin" 6d3t1
Como Desbloquear Archivos Protegidos De Pdf 23163q
December 2022 0
Statics And Mechanics Of Materials 5th Edition Hibbeler Solutions Manual 5l2n2
October 2019 315
D1d 1u4i5i
November 2020 0
Como Cambiar Tu Vida En 30 Dias Gratis Pdf 43j6g
December 2019 110
Existence Rollo May Pdf 6q3p1x
December 2019 334