09-25-2004 10:21 AM - edited 03-13-2019 06:27 AM
Hi
I'm doing a new phone deployment with call mgr 4.0. I have a bunch a phones that will not boot up. After trying to load the sep file for some 5 minutes, they stop and the display says "protocol application invalid".
Has anyone seen this ? Could these be sip phones?
thanks
Rob
09-25-2004 08:14 PM
A search on the Cisco website shows:
http://www.cisco.com/en/US/products/sw/voicesw/ps4967/products_upgrade_guides09186a008022a968.html
Cisco 7940 and 7960 IP Phones Firmware Upgrade Matrix
Common Error Messages
Protocol Application Invalid
This error message means that the application image cannot be loaded into flash memory or that the image does not exist in flash memory. This can happen for the following reasons:
The zip package was not unzipped in the root TFTP directory.
Files were copied to the TFTP server instead of using the zip package.
The universal application loader was unable to load a new application image into flash memory (image authentication failure, nonexistent image, TFTP errors, and so forth).
Another hit showed similar results:
http://www.cisco.com/en/US/tech/tk652/tk701/technologies_tech_note09186a0080094584.shtml#issue3a
09-28-2004 05:49 PM
Problem turns out to be some sort of bug with the phone tftp'g its config through the trunk port. The phone ports were configured with aux vlan 80 and could not load the config.
workaround is to remove the aux vlan and put the port into vlan 80. After the phone gets its config file, put the port back into aux vlan 80. Once the phone has its config it works normally in the aux vlan.
TAC did not mention any bug when they tried to resolve this so I'm not sure if its documented. I've sent this to my TAC engineer.
12-15-2004 11:21 AM
Here is the bug ID CSCef75275. However, I do not see it as fixed in version 7.1.1.
12-15-2004 01:46 PM
our bug turned out to be the 6548 module - bug CSCeb67650.
Packets destined out the WS-X6548-GE-TX or the WS-X6148-GE-TX that are less than 64 bytes will be dropped. This can occur when a device forwards a packet that is 60 bytes and the 4 byte dot1q tag is to added to create a valid 64 byte packet. When the tag is removed the packet is 60 bytes. If the destination is out a port on the WS-X6548-GE-TX or the WS-X6148-GE-TX it will be dropped by the linecard.
Additionally, if packets are received on an interface that does not have a minimum MTU of 64 bytes (e.g. ATM,POS) and are destined out the WS-X6548-GE-TX or the WS-X6148-GE-TX it will be dropped by the linecard.
needed to swap the module with a newer rev module
Rob
04-30-2005 12:32 PM
Rob,
Why did you have to swap the module and not use newer software with fixes?
I am having this problem at customer with 6148-GE-TX on 8.1(2) code which is 1 rev newer then bugfix was resolved mayybe from reading the bug release.
The hardware rev of the 6148 is 2.0 and firmware rev is 7.2(1). The MSFC is also at a earlier IOS release then bug fix but do we need MSFC on newer for this?
Thanks for posting this info. This may be the magic bullet I need to convince them to upgrade their switches/MSFCs. But wondering why you needed a newer revision module...
thanks.
04-30-2005 12:59 PM
the bug was fixed in a later firmware version and so I had to replace the module with the later version to fix the problem
Rob
04-30-2005 02:20 PM
That was for the 6548. Hmm.
Did TAC know the buggy firmware versions? Debating on upgrading first and see what happens or see what TAC has to say.
Our problem is that phoneload TFTP upgrades to newer/other versions fail when port is configured as dot1q trunk or has aux vlan set. If it is a plain access port in voice vlan the upgrade/downgrade to other image works.
Besides the TFTP issue, all other traffic appears to work fine.
05-01-2005 07:01 AM
check bug CSCeb67650 on cisco's web site. It will describe the details
05-01-2005 09:58 AM
I have checked the bug. The versions fixed in don't state if it is CatOS or actually hardware firmware versions which would need replacement of module.
Thats what I was trying to clarify with you, since you swapped out the module. The bug notes don't mention replacing hardware at all.
05-01-2005 01:01 PM
this is the link to the field notice:
05-01-2005 07:31 PM
Thank you! We have serial #s in that range.
03-17-2005 11:47 AM
The is happening to me too. I havnet figured how to correct it. If you find out please let me know.
Chris
03-17-2005 04:57 PM
CSCef75275 is resolved in the 7.1.1 load however it has been defered. You should load the 7.1.2 and it resolves the deferd issues in 7.1.1.
Also you may need to do the work around of setting the access v-lan to the voice vlan and removing trunking one last time. But the problem should be gone after that.
Mike
04-27-2005 07:52 PM
Adding option 66 to the voice vlan dhcp scope and putting in the tftp address for the string value fixes this as well.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide