From: Marcus Jensen (marcus@pobox.com)
Date: Thu Aug 07 2003 - 10:16:19 GMT-3
Tomas
The answer provided for lab 36 is not wrong, but it is misleading. There are
two different questions in that lab. I am only referring to the one where
the command 'sw mode trunk' is NOT used.
Version 1:
interface FastEthernet0/11
switchport access vlan 102
switchport voice vlan 101
switchport trunk encapsulation dot1q <----This command is unnecessary.
switchport priority extend cos 0
no ip address
mls qos cos 1
mls qos cos override
spanning-tree portfast
You can verify this command is unnessary by using 'sw trunk encap isl' here
instead. 7960s only support dot1q so you might think the phone will break
with encap ISL, but it will continue to work. In access or dynamic mode,
voice vlan uses dot1q and overrides trunk encap command. When I changed to
static trunk mode with ISL encap, then my 7960s and call manager finally
failed. See a post I made about 3 weeks ago for more details.
Marcus
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Tomasz Szymanski
Sent: Thursday, August 07, 2003 7:10 PM
To: ccielab@groupstudy.com
Subject: Connecting IP Phone 7960 to CAt3550
Hi group,
Studying IPexperts lab 36 I found two solutions for connecting Cisco IP
Phone to cat. Can you explain me the differences and when the
configurations should be used?
Version 1:
interface FastEthernet0/11
switchport access vlan 102
switchport voice vlan 101
switchport trunk encapsulation dot1q
switchport priority extend cos 0
no ip address
mls qos cos 1
mls qos cos override
spanning-tree portfast
Version2
interface FastEthernet0/12
switchport trunk encapsulation dot1q
switchport trunk native vlan 202
switchport mode trunk
switchport voice vlan 201
no ip address
spanning-tree portfast
This archive was generated by hypermail 2.1.4 : Tue Sep 02 2003 - 18:53:54 GMT-3