1 / 70

Deploying IPv6 in Enterprise UC Networks

Deploying IPv6 in Enterprise UC Networks. Florence Boucher TSE UC. Contents. IPv6 and UC networks summary IPv6 Addressing and Cisco devices DHCP and DNS for IPv6 IPv6 Deployment options IPv6 UC features IPv6 New Configuration Parameters CUCM Device Configuration and media handling

cecily
Download Presentation

Deploying IPv6 in Enterprise UC Networks

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Deploying IPv6 in Enterprise UC Networks Florence Boucher TSE UC

  2. Contents • IPv6 and UC networks summary • IPv6 Addressing and Cisco devices • DHCP and DNS for IPv6 • IPv6 Deployment options • IPv6 UC features • IPv6 New Configuration Parameters • CUCM Device Configuration and media handling • Other IPv6 UC Design Considerations • IPv6 UC Deployment Guidelines • Summary

  3. IPv6 for UC Networks Summary

  4. v4 v6 v4 v6 v4 v6 IPv4 and IPv6 – Icons and Terminology IPv4 Only Device communicates with and understands IPv4 addresses only IPv6 Only Device communicates with and understands IPv6 addresses only Dual Stack – IPv4 and IPv6 Device communicates with and understands both IPv4 and IPv6 addresses IPv6 Aware Device communicates with IPv4 addresses, but can receive and understand IPv6 addresses embedded in Application PDUs – Typically used by applications which use IPv4 to transport IPv6 information

  5. v4 v4 v4 v4 v6 v6 v6 v6 v4 v4 v4 v4 v4 v6 v6 v6 v4 v4 v6 v6 IPv4 and IPv6 for UC support - Summary • CUCM 7.1(2) Linux OS only • Cisco IP Phones Newer Cisco IP Phones running SCCP only • Gateways SIP Gateways ( ISR 28XX & 38XX, AS5400 ) VG224 SCCP Analogue Gateway SCCP FXS ports on ISR 28XX & 38XX routers IOS MTPs for IPv4 - IPv6 RTP Media conversion • CUCM SIP Trunks • Applications CUCM : CTI, AXL/SOAP, SNMP - IPv6 aware

  6. IPv6 Addressing and Cisco devices

  7. IPv6 – CUCM Addressing • CUCM can support : • One Link Local Address • One Unique Local Address or • One Global Address • ( and an IPv4 address )

  8. CUCM : configure IPv6 with CLI • Configure IPv6 with CLI • set network ipv6 service enable • Set a static IPv6 server address : • set network ipv6static_address <addr> <mask> • Reload the server • Utils system shutdown • Show the IPv6 configuration • show network ipv6 settings EFT DoD Release

  9. IPv6 – IP Phone Addressing • IP Phones can support : • One Link Local Address • Multiple Unique Local Addresses • Multiple Global Addresses • ( and an IPv4 address ) • IP Phones can support a combination of up to 20 Addresses (Global or Unique Local) • The IP Phone will use one IPv6 address (Global or Unique Local) for CUCM signaling and media. • IP Phone Address selection priority : 1) If configured, use the address that has been manually configured via the Phone’s UI 2) If an address has not been manually configured, use DHCPv6 to assign an address  3) If neither a DHCPv6, nor a manually configured address is available, and Auto Configuration (SLAAC) is enabled for the Phone (CUCM default = On) -  The phone will use SLAAC to create an IPv6 address. Router RA “O” bit should be set. • A Link Local address will never be sent to CUCM as a signaling and media address • If the phone has both Unique Local and Global addresses, the Global Addresses take precedence over Unique Local Addresses. • If multiple Unique Local or multiple Global addresses exist - the first address configured will be used as the signaling and media address sent to CUCM

  10. IPv6 – IOS Addressing • IOS devices can support : • One Link Local Address • Multiple Unique Local Addresses • Multiple Global Addresses • ( and multiple IPv4 addresses ) • Per Interface • Routers use Link Local Addresses for Routing protocols and the Address Selection Algorithm (RFC 3484) for applications running on routers ( Telnet, SSH etc ) • e.g. For responses to devices - Routers will use the same Network Prefix as the device initiating communications

  11. DHCP and DNS for IPv6

  12. IP Phone – IPv6 Address allocation options • IPv4 Address Configuration Options • Manual Configuration via Phone User Interface • DHCPv4 • IPv6 Address Configuration Options • Manual Configuration via Phone User Interface • DHCPv6 • Auto Configuration • Phones require a minimum of an IP address and TFTP server address • Cisco Network Registrar supports : • IPv4 DHCP and DNS • IPv6 DHCPv6 and DNSv6 • Dynamic DNS Updates, Vendor Option Classes • IOS DHCPv6 server support with vendor options

  13. IP Phone – IPv6 Address allocation – DHCPv6 Methods • Devices use Multicast to find DHCPv6 servers • IOS DHCP Relay is supported • Stateful DHCPv6 (RFC 3315) • DHCP server provides Network address and optionally : • Host ID - Host ID can also be generated by host using EUI-64 • Other Information – e.g. DNS Server address, TFTP Server Address • Note Default Router address is not a required option with IPv6 - Multicast is used instead to discover Routers on the Link • Stateless DHCPv6 (RFC 3736) • DHCP server only provides Other Information – e.g. DNSv6 Server address, TFTP Server address • DHCPv6 Prefix Delegation (RFC 3633) • Primarily used by Service Providers to automatically assign a Network Prefix to a customer’s site – Allows the delegation of prefixes from a delegating router to requesting routers.

  14. Reply DHCPv6 Server IP Phone DHCPv6 Client Request Advertise Solicit RA with “O” and /or “M” bit set IPv6 – DHCP Operation Stateless DHCP When a router sends an RA with the ‘O’ bit set, but does not set the ‘M’ bit, the client can use Stateless Address Auto-configuration (SLAAC) to obtain its IPv6 address, and use DHCPv6 for obtaining additional information. (e.g. TFTP Server address, DNS server address). This mechanism is known as Stateless DHCPv6, because the DHCPv6 server does not need to keep track of the client address bindings. Stateful DHCP When a router sends an RA with the ‘M’ bit set, this indicates that clients should use DHCP to obtain Addresses. Note - When the M bit is set, the setting of the O bit is irrelevant, since the DHCP server will also return “Other” configuration information together with addresses. This mechanism is known as Stateful DHCPv6, because the DHCPv6 server does keep track of the client address bindings.

  15. IP Phone – IPv6 Address allocation – SLAAC Stateless Address Auto-Configuration (SLAAC) - RFC 2462 • Configurable for IPv6 enabled Phones • CUCM Default - Auto Configuration = On • On power up phone sends a Router Solicitation (RS) message requesting Address configuration information • Router responds and periodically sends a Router Advertisement (RA) • RA can contain one or more Network Prefixes • Network Prefix and EUI-64 Host ID used to create interface address • RA also contains O and M bits : • O bit = 1 • Indicates that the Phones should use the advertised Network Prefix(es) to auto-configure its address, but should also request Other information from the DHCP server e.g. TFTP server address, DNS server address • M bit =1 • Indicates that the Phone should use DHCP for stateful address assignment

  16. Configuring the RA with the O-bit and the M-bit • For configuring the M-bit in the RA of the router : • ipv6 nd managed-config-flag • For configuring the O-bit in the RA of the router : • ipv6 nd other-config-flag

  17. CUCM Configuration for DHCP IPv6 • Enable IPv6 with auto conf OFF for phones (in entreprise parameters) • Off—The phone obtains its IPv6 address and TFTP server address from the DHCPv6 server. • Tip Ensure that the M (Managed address configuration) bit/ flag is also set in the router assignment on the router, which indicates that the phone should use DHCP for all addressing information. • On—The phone uses the IPv6 Network ID that is advertised in the Router Advertisements (RAs) to autoconfigure its IPv6 address. • Tip To indicate to the phone that it needs to use the DHCPv6 server to obtain other information, ensure that the O bit is set in the router assignment on the router.

  18. DHCP v6 configuration options

  19. DHCP stateful IPv6 CLI configuration example 1(CUCM config : autoconf OFF, Router :Bit M set ) Global config ! ipv6 unicast-routing ! ipv6 dhcp pool IPv6 address prefix 2001:1::/64 link-address 2001:1::/64 vendor-specific 9 suboption 1 address 2001:1::21C:C4FF:FE3A:1128 Interface Config ! interface Vlan1 ip address 172.30.0.254 255.255.255.0 ipv6 address 2001:1::1/64 ipv6 enable ipv6 nd managed-config-flag ipv6 dhcp server IPv6 Address configuration Cisco TFTP Set the M (Managed address configuration) bit/ flag Indicates that the Phone should use DHCP for stateful address assignment

  20. IPv6 Settings of the phoneexample 1

  21. Sh ipv6 int VLAN 1 (bit M set)example 1 Vlan1 is up, line protocol is up IPv6 is enabled, link-local address is FE80::222:BEFF:FE94:74C0 No Virtual link-local address(es): Global unicast address(es): 2001:1::1, subnet is 2001:1::/64 Joined group address(es): FF02::1 FF02::2 FF02::1:2 FF02::1:FF00:1 FF02::1:FF94:74C0 FF05::1:3 MTU is 1500 bytes ICMP error messages limited to one every 100 milliseconds ICMP redirects are enabled ICMP unreachables are sent ND DAD is enabled, number of DAD attempts: 1 ND reachable time is 30000 milliseconds (using 24019) ND advertised reachable time is 0 (unspecified) ND advertised retransmit interval is 0 (unspecified) ND router advertisements are sent every 200 seconds ND router advertisements live for 1800 seconds ND advertised default router preference is Medium Hosts use DHCP to obtain routable addresses.

  22. .Apr 24 13:49:20.558: ICMPv6-ND: Received RS on Vlan1 from FE80::221:A0FF:FE84:6FB6 .Apr 24 13:49:20.558: ICMPv6-ND: Sending solicited RA on Vlan1 .Apr 24 13:49:20.558: ICMPv6-ND: Request to send RA for FE80::222:BEFF:FE94:74C0 .Apr 24 13:49:20.558: ICMPv6-ND: Sending RA from FE80::222:BEFF:FE94:74C0 to FF02::1 on Vlan1 .Apr 24 13:49:20.558: ICMPv6-ND: Managed address configuration .Apr 24 13:49:20.558: ICMPv6-ND: MTU = 1500 .Apr 24 13:49:20.558: ICMPv6-ND: prefix = 2001:1::/64 onlink a Debug IPv6 ndexample 1

  23. Debug DHCPv6example 1 1/4 .Apr 23 16:43:14.032: IPv6 DHCP: Received SOLICIT from FE80::221:A0FF:FE84:6FB6 on Vlan1 .Apr 23 16:43:14.032: IPv6 DHCP: detailed packet contents .Apr 23 16:43:14.032: src FE80::221:A0FF:FE84:6FB6 (Vlan1) .Apr 23 16:43:14.032: dst FF02::1:2 .Apr 23 16:43:14.032: type SOLICIT(1), xid 16838 .Apr 23 16:43:14.032: option CLIENTID(1), len 10 .Apr 23 16:43:14.032: 000300010021A0846FB6 .Apr 23 16:43:14.032: option IA-NA(3), len 40 .Apr 23 16:43:14.032: IAID 0x00000001, T1 0, T2 0 .Apr 23 16:43:14.032: option IAADDR(5), len 24 .Apr 23 16:43:14.032: IPv6 address 2001:1::854F:9498:B198:802A .Apr 23 16:43:14.032: preferred 0, valid 0 .Apr 23 16:43:14.032: option ELAPSED-TIME(8), len 2 .Apr 23 16:43:14.032: elapsed-time 0 .Apr 23 16:43:14.032: option ORO(6), len 6 .Apr 23 16:43:14.032: DNS-SERVERS,DOMAIN-LIST,VENDOR-OPTS Apr 23 16:43:14.032: IPv6 DHCP: Using interface pool IPv6 .Apr 23 16:43:14.032: IPv6 DHCP: Looking up pool 2001:1::/64 entry with username '000300010021A0846FB600000001' .Apr 23 16:43:14.032: IPv6 DHCP: Poolentry for user found .Apr 23 16:43:14.032: IPv6 DHCP: Found address 2001:1::854F:9498:B198:802A in binding for FE80::221:A0FF:FE84:6FB6, IAID 00000001 .Apr 23 16:43:14.032: IPv6 DHCP: Updating binding address entry for address 2001:1::854F:9498:B198:802A .Apr 23 16:43:14.032: IPv6 DHCP: Setting timer on 2001:1::854F:9498:B198:802A for 60 seconds From IP Phone to DHCP Server DHCP Server

  24. Debug DHCPv6example 1 2/4 .Apr 23 16:43:14.032: IPv6 DHCP: Sending ADVERTISE to FE80::221:A0FF:FE84:6FB6 on Vlan1 .Apr 23 16:43:14.032: IPv6 DHCP: detailed packet contents .Apr 23 16:43:14.032: src FE80::222:BEFF:FE94:74C0 .Apr 23 16:43:14.032: dst FE80::221:A0FF:FE84:6FB6 (Vlan1) .Apr 23 16:43:14.032: type ADVERTISE(2), xid 16838 .Apr 23 16:43:14.032: option SERVERID(2), len 10 .Apr 23 16:43:14.032: 000300010022BE947480 .Apr 23 16:43:14.032: option CLIENTID(1), len 10 .Apr 23 16:43:14.032: 000300010021A0846FB6 .Apr 23 16:43:14.032: option IA-NA(3), len 40 .Apr 23 16:43:14.032: IAID 0x00000001, T1 43200, T2 69120 .Apr 23 16:43:14.032: option IAADDR(5), len 24 .Apr 23 16:43:14.032: IPv6 address 2001:1::854F:9498:B198:802A .Apr 23 16:43:14.032: preferred 86400, valid 172800 .Apr 23 16:43:14.032: option VENDOR-OPTS(17), len 24 .Apr 23 16:43:14.032: Enterprise-ID: 9 .Apr 23 16:43:14.032: Suboption 1, length 16 .Apr 23 16:43:14.032: Data: 2001000100000000021CC4FFFE3A1128 From DHCP Server to IP Phone Cisco TFTP

  25. Debug DHCPv6 example 1 3/4 .Apr 23 16:43:15.148: IPv6 DHCP: Received REQUEST from FE80::221:A0FF:FE84:6FB6 on Vlan1 .Apr 23 16:43:15.148: IPv6 DHCP: detailed packet contents .Apr 23 16:43:15.148: src FE80::221:A0FF:FE84:6FB6 (Vlan1) .Apr 23 16:43:15.148: dst FF02::1:2 .Apr 23 16:43:15.148: type REQUEST(3), xid 10113 .Apr 23 16:43:15.148: option CLIENTID(1), len 10 .Apr 23 16:43:15.148: 000300010021A0846FB6 .Apr 23 16:43:15.148: option SERVERID(2), len 10 .Apr 23 16:43:15.157: 000300010022BE947480 .Apr 23 16:43:15.157: option IA-NA(3), len 40 .Apr 23 16:43:15.157: IAID 0x00000001, T1 0, T2 0 .Apr 23 16:43:15.157: option IAADDR(5), len 24 .Apr 23 16:43:15.157: IPv6 address 2001:1::854F:9498:B198:802A .Apr 23 16:43:15.157: preferred 86400, valid 172800 .Apr 23 16:43:15.157: option ELAPSED-TIME(8), len 2 .Apr 23 16:43:15.157: elapsed-time 0 .Apr 23 16:43:15.157: option ORO(6), len 6 .Apr 23 16:43:15.157: DNS-SERVERS,DOMAIN-LIST,VENDOR-OPTS .Apr 23 16:43:15.157: IPv6 DHCP: Using interface pool IPv6 .Apr 23 16:43:15.157: IPv6 DHCP: Looking up pool 2001:1::/64 entry with username '000300010021A0846FB600000001' .Apr 23 16:43:15.157: IPv6 DHCP: Poolentry for user found .Apr 23 16:43:15.157: IPv6 DHCP: Found address 2001:1::854F:9498:B198:802A in binding for FE80::221:A0FF:FE84:6FB6, IAID 00000001 .Apr 23 16:43:15.157: IPv6 DHCP: Updating binding address entry for address 2001:1::854F:9498:B198:802A .Apr 23 16:43:15.157: IPv6 DHCP: Setting timer on 2001:1::854F:9498:B198:802A for 172800 seconds From IP Phone to DHCP Server DHCP Server

  26. Debug DHCPv6example 1 4/4 .Apr 23 16:43:15.157: IPv6 DHCP: Sending REPLY to FE80::221:A0FF:FE84:6FB6 on Vlan1 .Apr 23 16:43:15.157: IPv6 DHCP: detailed packet contents .Apr 23 16:43:15.157: src FE80::222:BEFF:FE94:74C0 .Apr 23 16:43:15.157: dst FE80::221:A0FF:FE84:6FB6 (Vlan1) .Apr 23 16:43:15.157: type REPLY(7), xid 10113 .Apr 23 16:43:15.157: option SERVERID(2), len 10 .Apr 23 16:43:15.157: 000300010022BE947480 .Apr 23 16:43:15.157: option CLIENTID(1), len 10 .Apr 23 16:43:15.157: 000300010021A0846FB6 .Apr 23 16:43:15.157: option IA-NA(3), len 40 .Apr 23 16:43:15.157: IAID 0x00000001, T1 43200, T2 69120 .Apr 23 16:43:15.157: option IAADDR(5), len 24 .Apr 23 16:43:15.157: IPv6 address 2001:1::854F:9498:B198:802A .Apr 23 16:43:15.157: preferred 86400, valid 172800 .Apr 23 16:43:15.157: option VENDOR-OPTS(17), len 24 .Apr 23 16:43:15.157: Enterprise-ID: 9 .Apr 23 16:43:15.157: Suboption 1, length 16 .Apr 23 16:43:15.157: Data: 2001000100000000021CC4FFFE3A1128 From DHCP Server to IP Phone Cisco TFTP

  27. Sh ipv6 dhcp briefexample 1 Client: FE80::221:A0FF:FE84:6FB6 (Vlan1) DUID: 000300010021A0846FB6 IA NA: IA ID 0x00000001, T1 43200, T2 69120 Address: 2001:1::854F:9498:B198:802A preferred lifetime 86400, valid lifetime 172800 expires at Apr 25 2009 04:43 PM (172668 seconds)

  28. DHCP statelessIPv6 CLI configuration example 2CUCM conf : autoconf ON, Router config Bit O set Global config ! ipv6 unicast-routing ! ipv6 dhcp pool IPv6 address prefix 2001:1::/64 link-address 2001:1::/64 vendor-specific 9 suboption 1 address 2001:1::21C:C4FF:FE3A:1128 interface Vlan1 ip address 172.30.0.254 255.255.255.0 ipv6 address 2001:1::1/64 ipv6 enable ipv6 nd other-config-flag ipv6 dhcp server IPv6 Cisco TFTP If the O bit is set in the router’s RAs - The Phone will use SLAAC to acquire its IP address and use the DHCP server to acquire Other information e.g. the TFTP server address, DNS server address (This is known as Stateless DHCP).

  29. Sh run int vlan 1 (bit O set)example 2 interface Vlan1 ip address 172.30.0.254 255.255.255.0 ipv6 address 2001:1::1/64 ipv6 enable ipv6 nd other-config-flag ipv6 dhcp server IPv6

  30. Vlan1 is up, line protocol is up IPv6 is enabled, link-local address is FE80::222:BEFF:FE94:74C0 No Virtual link-local address(es): Global unicast address(es): 2001:1::1, subnet is 2001:1::/64 Joined group address(es): FF02::1 FF02::2 FF02::1:2 FF02::1:FF00:1 FF02::1:FF94:74C0 FF05::1:3 MTU is 1500 bytes ICMP error messages limited to one every 100 milliseconds ICMP redirects are enabled ICMP unreachables are sent ND DAD is enabled, number of DAD attempts: 1 ND reachable time is 30000 milliseconds (using 25896) ND advertised reachable time is 0 (unspecified) ND advertised retransmit interval is 0 (unspecified) ND router advertisements are sent every 200 seconds ND router advertisements live for 1800 seconds ND advertised default router preference is Medium Hosts use stateless autoconfig for addresses. Hosts use DHCP to obtain other configuration. Sh ipv6 int vlan 1 (bit O set)example 2

  31. .Apr 24 14:35:44.165: ICMPv6-ND: Received RS on Vlan1 from FE80::221:A0FF:FE84:6FB6 .Apr 24 14:35:44.165: ICMPv6-ND: Sending solicited RA on Vlan1 .Apr 24 14:35:44.165: ICMPv6-ND: Request to send RA for FE80::222:BEFF:FE94:74C0 .Apr 24 14:35:44.165: ICMPv6-ND: Sending RA from FE80::222:BEFF:FE94:74C0 to FF02::1 on Vlan1 .Apr 24 14:35:44.165: ICMPv6-ND: Other stateful configuration .Apr 24 14:35:44.165: ICMPv6-ND: MTU = 1500 .Apr 24 14:35:44.165: ICMPv6-ND: prefix = 2001:1::/64 onlink autoconfig .Apr 24 14:35:44.165: ICMPv6-ND: 2592000/604800 (valid/preferred) Debug ipv6 nd (Bit O set)example 2

  32. IPv4 IPv6 A record: www.abc.test. A 192.168.30.1 AAAA record: www.abc.test AAAA 2001:db8:C18:1::2 Hostname to IP Address Resolution PTR record: 2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.1.0.0.0.8.1.c.0. 8.b.d.0.1.0.0.2.ip6.arpa PTR www.abc.test. IP Address to Hostname Resolution PTR record: 1.30.168.192.in-addr.arpa. PTR www.abc.test. IPv6 – DNS • CUCM uses DNS Name to Address Resolution for three purposes : • If DNS names are used to define CUCM servers (not recommended) • If SIP Route Patterns use DNS names to define destinations • If SIP Trunks use DNS names to define Trunk destinations • The principle for DNS is the same as IPv4 but : • The nomenclature is different • AAAA instead of A records • DNS name to address queries can return multiple IPv6 addresses (and an IPv4 address)

  33. IPv6 Deployment Options

  34. General IPv6 Deployment Guidelines • Almost all IPv6 deployments will run a combination of IPv4 and IPv6 • Although not recommended IP Phones can be configured as IPv6 Only (with functionality limitations) • Other IPv6 devices ( e.g. routers, switches ) require some IPv4 configuration • LAN and WAN environments also need to be considered when deploying IPv6 • In almost all cases…… Dual Stack deployments offer the best approach when introducing IPv6 into any network environment - As both IPv4 devices and Dual Stack v4/v6 devices can interoperate and disruption to the existing network is minimal. • In the following sections we will focus on IPv6 deployments for UC. We will touch upon the Campus and WAN environments, but mainly to reference existing design guidance for IPv6 deployment

  35. IPv6 UC Features

  36. v4 v6 v4 v6 v4 v6 IPv4 and IPv6 – Icons & Terminology IPv4 Only Device communicates with and understands IPv4 addresses only IPv6 Only Device communicates with and understands IPv6 addresses only Dual Stack – IPv4 and IPv6 Device communicates with and understands both IPv4 and IPv6 addresses IPv6 Aware Device communicates with IPv4 addresses, but can receive and understand IPv6 addresses embedded in Application PDUs – Typically used by applications which use IPv4 to transport IPv6 information

  37. v4 v4 v4 v4 v6 v6 v6 v6 v4 v4 v4 v4 v4 v6 v6 v6 v4 v4 v6 v6 IPv4 and IPv6 for UC support - Summary • CUCM 7.1(2) Linux OS only • Cisco IP Phones Newer Cisco IP Phones running SCCP only • Gateways SIP Gateways ( ISR 28XX & 38XX, AS5400 ) VG224 SCCP Analogue Gateway SCCP FXS ports on ISR 28XX & 38XX routers IOS MTPs for IPv4 - IPv6 RTP Media conversion • CUCM SIP Trunks • Applications CUCM : CTI, AXL/SOAP, SNMP - IPv6 aware

  38. IPv6 New Configuration Parameters

  39. CUCM SIP Trunks CUCM H323 & ICT Trunks v4 v4 v4 v4 v4 v4 v4 v4 v4 v4 v4 v4 v4 v4 v4 v4 v4 v4 v6 v6 v6 v6 v6 v6 v6 SCCPISR Analogue Ports SRST SIP ISR Gateways Soft Phones CUCME VG224 Analogue Gateways WiFi IP Phones MGCP Gateways All SIP based Phones Newer SCCP based Phones H323 Gateways Older SCCP based Phones IPv6 capable UC Devices - Summary IPv4 Only IPv4/IPv6 Video Conf. Endpoints CUVA

  40. IPv6 – CUCM Configurations options • Server platform IPv6 address configuration • CUCM IPv6 Server Address Configuration • CUCM IPv6 Cluster wide Configuration • IPv6 Device Specific parameters • Common Device Configuration • SIP Trunk Configuration

  41. MCS Server Ethernet Port IPv6 address Configuration To allow IPv6 based call processing – IPv6 must first be enabled throughout the cluster. This involves two steps: 1) Configuring IPv6 via the OS CLI, or CUCM OS GUI on each server in the cluster (below) 2) Configuring IPv6 via the CUCM GUI Server Configuration Server OS Admin CLI commands : To enable IPv6 : “set network ipv6 service enable” To set a static IPv6 server address : "set network ipv6 static_address <addr> <mask>" Using the DHCPv6 client is not recommended. To view IPv6 address settings : “show network ipv6 settings”

  42. CUCM Server - IPv6 Address Configuration ICCS TFTP TFTP For the CUCM service Configure an IPv6 address or name If a name is used, DNSv6 is required This name / IPv6 address is used by the TFTP server in the configuration files that are sent to devices. The address is used by these devices for CUCM registration.

  43. CUCM Enterprise Parameters for IPv6 Enable IPv6 Cluster-wide via CUCM GUI Configure Cluster-wide : IP Addressing Mode Preference for Media IP Addressing Mode Preference forSignalling Allow Auto-Configuration for Phones (SLAAC) Signalling Preference and Phone Auto Configuration settings are also configurable at the device level – Device setting takes precedence

  44. IPv6 – CUCM Common Device Configuration SIP Trunks The Common Device Configuration is a configuration template that can be applied to Phones and Trunks. For IPv6 capable devices the following values can be configured : IP Addressing Mode: IPv4 Only - Phone uses one IPv4 address only IPv6 Only - Phone uses one IPv6 address only IPv4 and IP6 - Phone uses one IPv4 address and one IPv6 address IP Addressing Mode Preference for Signalling: IPv4 only IPv6 only System Default Allow Auto Configuration For Phones : On Off Default

  45. CUCM device configuration and media handling for IPV6

  46. IPv4 Signalling IPv6 Signalling IPv4 Media v4 v4 v6 v4 v4 v6 v6 IPv6 Media IPv6 – CUCM Phone Signaling & Addressing Options Only SCCP based Phones support IPv6 : 7906G, 7911G 7931G 7941G, 7941GE 7942G, 7945G 7961G, 7961GE 7962G, 7965G 7970G, 7971G-GE 7975G v4 v6 IP Addressing Mode: (For Media and Signalling) Phone uses one IPv4 address only Phone uses one IPv6 address only Phone uses one IPv4 address and one IPv6 address IP Addressing Mode Preference for Signalling IPv4 only/ IPv6 only/ System Default Allow Auto-Configuration for Phones - On/ Off/ Default

  47. IPv4 Signalling IPv6 Signalling v4 v4 v4 v6 v6 v4 v4 v4 v4 v4 v4 v4 v6 v6 v6 v6 v6 v6 v6 IPv4 Media IPv6 Media MTP MTP IPv6 – CUCM Phone Signaling and Media Options For IP Addressing Mode mis-matches between Phones -CUCM inserts an MTP for IPv4   IPv6 conversion IPv6 is supported by the following SCCP based Phones : 7906G, 7911G 7931G 7941G, 7941GE 7942G, 7945G 7961G, 7961GE 7962G, 7965G 7970G, 7971G-GE 7975G Dual Stack Phones use the Cluster-wide “IP Addressing mode for Media Preference” to select addressing mode (IPv4 or IPv6)for media between phones.

  48. v4 v4 v4 v4 v4 v6 v6 v6 Video Voice Cluster-wide Addressing Mode Preference for Media value = IPv6 IPv6 and video calls CUCM does not support IPv6 for video media Video Phones such as the Cisco 7985 do not support IPv6 For IPv6 capable Phones using CUVA for video : - The voice stream can be IPv4 or IPv6 - The video stream is always IPv4

  49. v4 v4 v4 v4 v4 TFTP HTTP IPv6 – CUCM Phones - Other Signaling Options 1/3 Phones use IP to interact with other CUCM services and network based services : Phone IP addresses are sent to access switches in CDP/ LLDP Phones use IP to contact their TFTP server Phones use HTTP for Phones Services, Extension Mobility, Directory Look Ups etc TFTP For IPv4 only CUCM and Phone deployments IPv4 is used in CDP/LLDP and for TFTP and HTTP services PUB CDP/LLDP

  50. v4 v4 v4 v4 v4 v4 v4 v4 v4 v6 v6 v6 v6 TFTP HTTP IPv6 – CUCM Phones - Other Signaling Options 2/3 Phones use IP to interact with other CUCM services and network based services : Phone IP addresses are sent to access switches in CDP/ LLDP Phones use IP to contact their TFTP server Phones use HTTP for Phones Services, Extension Mobility, Directory Look Ups etc TFTP For IPv4 only CUCM and Phone deployments IPv4 is used in CDP/LLDP and for TFTP and HTTP services For Dual Stack CUCM and Phone deployments IPv4 and IPv6 addresses are transported in CDP/LLDPTFTP can use IPv4 and/or IPv6 HTTP services use IPv4 only PUB CDP/LLDP

More Related