Upgrading Tandberg E20 TE2.1.0 to TE4.1.1. Phone is in both Data & Voice VLANS

[stepnharp]

I have upgraded a Tandberg E20 TE2.1.0 to TE4.1.1 (no encryption) Phone is now showing up in both Data & Voice/Video VLANS. 

It appears that the Data and Voice traffic is being properly handled, due to the fact that when I SHUTDOWN the voice/video VLAN no calls can be sent or received. 

Q:  Do I need to worry about why the Tandberg phone is now showing up in both Data & Voice/Video VLANS?

Thanks, Scott

[Danny De Ridder]

Hello,

the normal process would be to have the video/voice into the VLAN. Data traffic would flow when one has a PC connected to the E20 at the same time.

Can you access the E20 via root and execute some commands ?

ssh to the E20 with admin password and set the root password [here cisco used as example]

[EX90-PDIHD:~] $ tsh

Welcome to EX90_PDIHD

TANDBERG Codec Release TE7.0.0 PreAlpha (TEST SW, te-6.0.0-alpha6-3782-gf93604e)

SW Release Date: 2012-10-02, 15:45, m

OK

systemtools rootsettings on cisco

OK

Then reconnect using root and log the output to a file to capture all the data.

sweet-brew-7:/home/dderidde # ssh root@144.254.12.202

Password:

[EX90-PDIHD:~]

[EX90-PDIHD:~] $ ip add

1: lo: mtu 16436 qdisc noqueue state UNKNOWN

    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

    inet 127.0.0.1/8 scope host lo

    inet6 ::1/128 scope host

       valid_lft forever preferred_lft forever

2: eth0: mtu 1500 qdisc htb state UP qlen 1000

    link/ether 00:50:60:04:e8:72 brd ff:ff:ff:ff:ff:ff

    inet 144.254.12.202/25 scope global eth0

    inet6 fe80::250:60ff:fe04:e872/64 scope link

       valid_lft forever preferred_lft forever

3: eth1: mtu 1500 qdisc pfifo_fast state UP qlen 1000

    link/ether 00:e0:0c:00:8c:02 brd ff:ff:ff:ff:ff:ff

    inet 169.254.0.1/24 brd 169.254.0.255 scope global eth1

    inet6 fe80::2e0:cff:fe00:8c02/64 scope link

       valid_lft forever preferred_lft forever

4: dummy0: mtu 1500 qdisc noop state DOWN

    link/ether ce:5a:8b:41:21:dd brd ff:ff:ff:ff:ff:ff

5: sit0: mtu 1480 qdisc noop state DOWN

    link/sit 0.0.0.0 brd 0.0.0.0

6: eth1.4090@eth1: mtu 1500 qdisc noqueue state UP

    link/ether 00:e0:0c:00:8c:02 brd ff:ff:ff:ff:ff:ff

    inet 169.254.1.1/24 brd 169.254.1.255 scope global eth1.4090

    inet6 fe80::2e0:cff:fe00:8c02/64 scope link

       valid_lft forever preferred_lft forever

[EX90-PDIHD:~] $

[EX90-PDIHD:~] $ cat /var/log/console

Creating tmp files with hw config information

Checking if base file system is mounted... Not mounted.  Mounting...

Mounting base filesystem as yaffs2 from device /dev/mtdblock1

OK.

Mounting /devel... OK.

Mounting /extra... OK.

[EX90-PDIHD:~] $

[EX90-PDIHD:~] $ cat /var/log/messages.log | grep dhclient

Oct  3 05:06:32 (none) dhclient: Bound to *:546

Oct  3 05:06:33 (none) dhclient: RCV: Reply message on eth0 from fe80::21a:30ff:fec8:7800.

Oct  3 05:06:36 (none) dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67

Oct  3 05:06:36 (none) dhclient: DHCPACK from 144.254.12.130

Oct  3 05:06:37 (none) dhclient: bound to 144.254.12.202 -- renewal in 86504 seconds.

[EX90-PDIHD:~] $

[stepnharp]

FYI, I will be out of the office until Saturday, I will reply back at that time. Thanks for your time.

Danny,

I have not been able to login as admin or root. The release notes state that no password is set.

Any Suggestion on how to login? I am using BitVise SSH Client 4.5

Thanks for your time, Scott

[Alok Jaiswal]

Hi Scott,

I don't understand exactly when you say you see endpoint in both the vlans.

however i believe on the switch end you have confiugred the "auxilary" vlan. that is configured the DATA and VOICE/VIDEO vlan voth.

this is for segregating the traffic and the data traffic passing through your E-20 will be via the data vlan.

and hence when you remove the other vlan from the switch or shutdown the voice/video vlan the call stops working.

Cheers

Alok

[stepnharp]

Alok,

Please see below the E20 is shown in 2 different VLANs.

Native (Data) VLAN = 100

Auxiliary (Voice) VLAN = 11

interface GigabitEthernet0/2

switchport access vlan 100

switchport mode access

switchport voice vlan 11

spanning-tree portfast

#sh mac address-table

         Mac Address Table

-------------------------------------------

Vlan   Mac Address       Type       Ports

11   0050.6004.2451   DYNAMIC     Gi0/2 // Tandberg E20

100   0050.6004.2451   DYNAMIC     Gi0/2

100   1803.73e3.083c   DYNAMIC     Gi0/2 // Workstation connected to E20

Thanks for your time, Scott

[Danny De Ridder · Accepted solution]

Hello,

I think what happens is that when the unit boots up, DHCP tries to get IP address in the native VLAN 100. After CDP discovers there's a voice VLAN, the endpoint will request DHCP address on VLAN 11. So you see MAC twice  :

#sh mac address-table

         Mac Address Table

-------------------------------------------

Vlan   Mac Address       Type       Ports

11    0050.6004.2451   DYNAMIC     Gi0/2 // Tandberg E20

100   0050.6004.2451   DYNAMIC     Gi0/2

If you would clear the MAC address table, the entry for 100 will disappear [I hope].

The other entry for the connected PC is normal.

#sh mac address-table

         Mac Address Table

-------------------------------------------

Vlan   Mac Address       Type       Ports

100   1803.73e3.083c   DYNAMIC     Gi0/2 // Workstation connected to E20

We have a ddts where we would not get proper address in case of CDP automatic : CSCtx84402.

Should get fixed in TC6 release.

Danny.

[stepnharp]

Danny,

I have done a "clear mac address-table dynamic" on the switch, with the same result as before. 

I have installed 8 E20 (TE 4.1.1) on Cisco 3560 switches, all of the phones show up on VLAN 100 and 11.

Vlan   Mac Address       Type       Ports

11   0050.6004.2451   DYNAMIC     Gi0/2 // Tandberg E20

100   0050.6004.2451   DYNAMIC     Gi0/2

Having the E20 on VLAN 100 does not seem to cause any problems for the phone or workstation, so I am going to call it good.  Boss likes the new phones, therefore I like it...

Thanks for your effort.

Scott