I have encountered today a very strange situation: I connected a 7940 phone to my desk switch (it's a lousy Surecom switch, with no VLANs or other stuff) and that switch is connected to another switch - and from there, to the company's routing infrastructure (also to a CallManager). I mention that my laptop is connected to the same Surecom switch as the phone.
The weird thing is that after phone starts, it respons to ping from my laptop, and it responds to 3-4 ping packets sourced from a router (that lies somewhere in the company network, but has direct connection, through switches, with the phone). After those 3-4 replies, phone no longer replies to pings sourced from the router, but only replies to pings coming from my laptop. I put the phone in another ports on the switch - same happened. I connected the phone to the upstream switch - same happened.
I really don't understand why the phone stops replying to pings (this is also a sign that no other packets from phone to router or CM are passing through).
Might be because the IP phones have been designed to only reply to an echo every 10ms, in order to withstand Denial of Service (DoS) attacks. A Cisco IOS gateway sends echos more frequently so one out of two will timeout. This is not the case for a PC since the time between two echos is greater than 10ms.
It is not the problem that the router sends faster ICMP requests and some of them are lost and some of them aren't, because the situation is that no ICMP replies get back to the router after the first 3-4. Pings from router towards my laptop are working fine.
I also attached another IP Phone (a 7905), having an IP similar to 7940's, and this one is working "by the book": replies to all ICMP pings with no loss.
I read Narayan's link, but those statements have nothing to do with my case. If you read it thoroughly, I said that the 7940 phone STOPS replying ICMPs after 3-4 replies, arrived in order. And it never replies to any ICMP ever, until I take out the ethernet cable from the switch and plug it back. After that, the situation repeats.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.