I just went through the event viewer on my CallManager 4.1 machine, not
because anythings wrong, but because its 10pm and im still at work.

And I found THOUSANDS of messages.  Here is the background,
cimgroup801grand is a 2801 connected with a p2p t1, and all the devices
connected to it work great. I have about 6x 7960s and they are all fine.
Its setup as a gateway, since it has a VIC2-2FXO in it for 911 calling.
The lines haven't been installed, so 911 calling is not turned on yet.
Is that why I am getting this error message every 30 seconds? Or is it
something else?



Event Type:       Error

Event Source:    cisco CallManager

Event Category: None

Event ID:           3

Date:                12/28/2005

Time:                10:15:15 PM

User:                N/A

Computer:         CIMGROUPCCM01

Description:

Error: DeviceTransientConnection - Transient connection attempt.

Connecting Port: 2427

Device name [Optional].: *@cimgroup801grand.cimgroup.com

Device IP address.: 10.60.1.129

Device type. [Optional]: 254

Reason Code [Optional].: 2

App ID: cisco CallManager

Cluster ID: StandAloneCluster

Node ID: 10.96.3.11

Explanation: A connection was established and immediately dropped before
completing registration. Incomplete registration may indicate a device
is rehoming in the middle of registration. The alarm could also indicate
a device misconfiguration, database error, or an illegal/unknown device
trying to attempt a connection.

Recommended Action: No action is required if this event was issued as a
result of a normal device rehome..




 ****************************************
**************
This email may contain trade secrets and/or other information that is
proprietary and/or confidential. Use of this by anyone other than the
intended recipient(s) is prohibited and may be unlawful. If you are not
the intended recipient, delete the e-mail and notify us immediately.
 ****************************************
**************

Attachment:
This has been downloaded 0 time(s).

[ Post a follow-up to this message ]

The reason code of 2 means no entry in database (port
not configured yet in ccm). Is this particular port
(endpoint) configured in call manager yet or
unconfigured?

Usually from my experiences, if you see transient
connection on one server another server in the cluster
will have a device unregistered event log error with
more details as to port, etc trying to register. CCM
detailed traces will also have this info.

I'm betting that since you're still working on getting
the 911 lines installed these ports may not be
configured yet on the CCM gateway page and thus the
router is constantly trying to register them to CCM.
You can shutdown the voice ports on the router - or
simply configure the ports on the call manager side
but not assign a DN, etc to them. This way they show
registered on CCM side and later you can come back and
finish configuring them with specifics. This will also
save on resources because the router/gateway is no
longer constantly trying to register and the server
doesn't have to constantly try to process the
registration request and put entries in the event log.
It will also get rid of that error in event log ...
which will make troubleshooting real issues easier
since you won't have a bunch of noise in the logs to
sift through.

--- IT <it@cimgroup.com> wrote:

> I just went through the event viewer on my
> CallManager 4.1 machine, not
> because anythings wrong, but because its 10pm and im
> still at work.
>
> And I found THOUSANDS of messages.  Here is the
> background,
> cimgroup801grand is a 2801 connected with a p2p t1,
> and all the devices
> connected to it work great. I have about 6x 7960s
> and they are all fine.
> Its setup as a gateway, since it has a VIC2-2FXO in
> it for 911 calling.
> The lines haven't been installed, so 911 calling is
> not turned on yet.
> Is that why I am getting this error message every 30
> seconds? Or is it
> something else?
>
>
>
> Event Type:       Error
>
> Event Source:    cisco CallManager
>
> Event Category: None
>
> Event ID:           3
>
> Date:                12/28/2005
>
> Time:                10:15:15 PM
>
> User:                N/A
>
> Computer:         CIMGROUPCCM01
>
> Description:
>
> Error: DeviceTransientConnection - Transient
> connection attempt.
>
>   Connecting Port: 2427
>
>   Device name [Optional].:
> *@cimgroup801grand.cimgroup.com
>
>   Device IP address.: 10.60.1.129
>
>   Device type. [Optional]: 254
>
>   Reason Code [Optional].: 2
>
>   App ID: cisco CallManager
>
>   Cluster ID: StandAloneCluster
>
>   Node ID: 10.96.3.11
>
> Explanation: A connection was established and
> immediately dropped before
> completing registration. Incomplete registration may
> indicate a device
> is rehoming in the middle of registration. The alarm
> could also indicate
> a device misconfiguration, database error, or an
> illegal/unknown device
> trying to attempt a connection.
>
> Recommended Action: No action is required if this
> event was issued as a
> result of a normal device rehome..
>
>
>
>
>
 ****************************************
**************
> This email may contain trade secrets and/or other
> information that is
> proprietary and/or confidential. Use of this by
> anyone other than the
> intended recipient(s) is prohibited and may be
> unlawful. If you are not
> the intended recipient, delete the e-mail and notify
> us immediately.
>
 ****************************************
**************
>
>
> 
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>





__________________________________
Yahoo! for Good - Make a difference this year.
http://brand.yahoo.com/cybergivingweek2005/

[ Post a follow-up to this message ]