Cisco Acano X-series
Cisco Meeting Server Release 2.0 : Scalable and Resilient Meeting Server Deployments
25
should support 2 simultaneous recordings per physical core, so a maximum of 8 simultaneous
recordings.
recordings.
To purchase recording license keys, you will need the following information:
n
number of simultaneous recordings,
n
MAC address of interface A on the servers hosting the Call Bridges.
You can purchase recording license keys through Cisco’s ecommerce tool.
2.11 Diagnostics and troubleshooting
In addition to using a Syslog server it is also possible to enable additional SIP tracing using the
Logs > Detailed tracing page in the Web Admin Interface. These logs may be useful when
investigating call setup failure issues for SIP endpoints and should be disabled at all other times.
To prevent the verbose logging being enabled for longer than necessary, it automatically shuts
off after a choice of 1 minute, 10 minutes, 30 minutes or 24 hours. Refer to the Meeting Server
Support FAQs on the Cisco website for more troubleshooting information.
Logs > Detailed tracing page in the Web Admin Interface. These logs may be useful when
investigating call setup failure issues for SIP endpoints and should be disabled at all other times.
To prevent the verbose logging being enabled for longer than necessary, it automatically shuts
off after a choice of 1 minute, 10 minutes, 30 minutes or 24 hours. Refer to the Meeting Server
Support FAQs on the Cisco website for more troubleshooting information.
Diagnostics for failed login attempts include:
n
the IP address of the far end included in event log messages relating to logins
n
audit messages generated for unsuccessful logins (minus the user name) and log in session
timeouts. They are also generated for successful logins.
timeouts. They are also generated for successful logins.
2.12 General points about scalability and resilience
For scalability and resilience the Meeting Server can be deployed with:
n
Multiple combined servers (virtualized servers, Acano X-series servers or a combination). The
location of these servers will depend on your requirements, possibly one at each point of
presence—although this is not a requirement
location of these servers will depend on your requirements, possibly one at each point of
presence—although this is not a requirement
When scaling to a large deployment, it is not necessary (and not always recommended) to
have every component enabled on every instance: this is discussed more fully later.
have every component enabled on every instance: this is discussed more fully later.
n
Multiple Edge and/or Core servers (virtualized servers, Acano X-series servers or a
combination). The location of these Edge and Core servers will depend on your
requirements, possibly co-locating Core and Edge servers in the same data center—although
this is not a requirement
combination). The location of these Edge and Core servers will depend on your
requirements, possibly co-locating Core and Edge servers in the same data center—although
this is not a requirement
n
In a large split deployment it is not necessary, or even desirable, to have the same number of
Edge and Core servers. For example, one Call Bridge can manage multiple Web Bridges;
those Web Bridges can be reachable externally with a single DNS name resolving to
potentially multiple separate units
Edge and Core servers. For example, one Call Bridge can manage multiple Web Bridges;
those Web Bridges can be reachable externally with a single DNS name resolving to
potentially multiple separate units
2 General concepts for deployment