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 Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
problem in UCM Registration for more that 11 elements(MGC and MC32S)
- Thread starter ntima1
- Start date
Stand alone configuration? If you have anything else loaded on the server you could hose your UCM and get severe latency with connection and authenticating to the UCM.
11 elements is pushing it. I think the top end is 12 elements, so you are pushing it to the limits.
Cut it down and unregister some of the elements. Right now there is no fix for any number of elements registered.
Hope this helps, but we are facing the same issue, but we are looking at NRS loaded on the same server and about 30 elements, but Avaya swears this will work.
11 elements is pushing it. I think the top end is 12 elements, so you are pushing it to the limits.
Cut it down and unregister some of the elements. Right now there is no fix for any number of elements registered.
Hope this helps, but we are facing the same issue, but we are looking at NRS loaded on the same server and about 30 elements, but Avaya swears this will work.
We have dedicated primary and secondary UCM/NRS Servers loaded on HP COTS Servers. There are over 50 elements registered and 10 plus SIP Endpoints. We have no latency issues at all.
The dedicated servers were part of our design for NRS when we orginally layed out a 5.5 upgrade. Once we upgraded to 6.0 and added UCM it was decided to share the servers.
This is sized to add several more endpoints and elements.
If you are using the CPPM processors instead of COTS that could be the issue. I hear there is a replacement for the CPPM either coming soon or already released.
The dedicated servers were part of our design for NRS when we orginally layed out a 5.5 upgrade. Once we upgraded to 6.0 and added UCM it was decided to share the servers.
This is sized to add several more endpoints and elements.
If you are using the CPPM processors instead of COTS that could be the issue. I hear there is a replacement for the CPPM either coming soon or already released.
- Thread starter
- #4
hii thanks for your infor..
but i have problem in node SYNC amd getting fail(cannot connect to server) but during installation.i was regestering one by one the elements and i do not have this problem..
are u facing sync-ing issue with big number of elements..
Pleae advise...
but i have problem in node SYNC amd getting fail(cannot connect to server) but during installation.i was regestering one by one the elements and i do not have this problem..
are u facing sync-ing issue with big number of elements..
Pleae advise...
No syncing issues except the follower Signaling Server wouldn't sync. Like I answered in your other thread. Had to deploy Element Manager to it and then do a sync on the follower in order to get my node synced. This happened at more than one site.
MC32 at all of the sites we did 6.0 have always synced perfectly first try.
MC32 at all of the sites we did 6.0 have always synced perfectly first try.
- Thread starter
- #6
- Status
Similar threads
- Locked
- Question
- Locked
- Question