Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

ATA Config

Status
Not open for further replies.

TheCardMan

IS-IT--Management
Jun 18, 2002
428
US
I have several ATA's running in different sites. On some I only use the first port of the 2 ports. I get errors in the event application log for all the secondary ports that are not configured. How do I stop these errors from clogging the logs? The error is as follows:

Error: DeviceTransientConnection - Transient connection attempt.

Connecting Port: 2000

Device name [Optional].: ATA157FCACDAA01

Device IP address.: 1.2.3.4

Device type. [Optional]: 12

Reason Code [Optional].: 1

App ID: Cisco CallManager

Cluster ID: PUB1-Cluster

Node ID: 5.4.3.2

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..
 
You have to disable the 2nd port if you are not using it or it continues to try and register and fails and logs an error which will build up.I have seen the procedure on Cisco's web site but couldn't find it for you.
 
Thanks, I may have found the Doc on Cisco's site.

 
Second option is to build the second port in CCM but not to put a Dn on it. The second port will register and stop the transient device attempts.
 
Thanks, another good option. I ended up going into the ata via: http:<ata ip>\dev and changed the value of EPID1 or SID1 from (.) to (0). EPID0/SID0 is Port 1 and EPID1/SID1 is Port 2, (.) is enabled and (0) is disable.

 
The second option is perfect for sites with VG224's etc. If the port is registered then no gateway reset is required by adding a DN. In a production environment, those resets may be few and far between on 24 and 48 port gear...
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top