MXclusters, Redundancy, XRS12, EPA3

1. MXclusters, Redundancy, XRS12, EPA3 Yang Guo Manager of Business Development for Asia Pacific

2. MXcluster — What is it? • Software feature for MX250 • standard function in version 2.2 at no charge • Enables true single system for up to 1000 users • solutions equivalent to “MX500”, “MX750”, “MX1000” • single Admin UI and database • all features of single MX250 extended to cluster • Transparent to administrator and user • single IP address • Supports N+1 redundancy

3. MXcluster One site, up to 1000 users MX250s must be co-located Cluster depends on all MX250s operating Cluster controlled by single Admin UI Redundancy is supported Foreign login has no meaning Single IP address MXgroup 32 sites, up to 8000 users MX250s at separate sites Group can operate with any one site removed Each group member controlled by separately No redundancy Foreign login required moving between sites Separate IP address for each MX250 MXcluster — Differences with MXgroup

4. MXcluster — Who needs it? • Have 250–1000 users at one site • all functions of MX250 retained • Want automatic redundancy • for MX250 failure • Want 60+ voice channels from MX system • gain additional 60 channels with each MX250 box • Want to scale MX system to over 8000 users • add MXcluster system to an MXgroup • 32 members maximum within an MXgroup

5. MXcluster — Capacities • Single MXcluster (no MXgroup) • 1000 users • 240 voice channels • Multiple MXclusters (in an MXgroup) • 32,000 users

6. MXcluster — Enabling on Admin UI • Similar to MXgroup • create MXcluster ID • add each MX250 box • One MX250 is designated as master • its IP address becomes the IP address of cluster • IP addresses of other members are “lost” • Add info of each box to a cluster • each MX250 still requires two internal IP addresses • need to make sure the internal IP does not conflict with each other

7. Licensing • Capacity of cluster equals sum of licenses • Licenses can be on any MX250 in cluster • Allows a user to bring together MX250 without loss of capacity

8. Configuration of Redundancy • Requires MX250 • no special hardware • Requires Redundancy license • installed on any one of the MX250s in cluster • Requires XRS12 • metallic switch to route PSTN circuits • Configuration all done through Admin UI master

9. MXcluster — 4:1 Redundancy (simple)

10. MXcluster — 4:1 Redundancy (2 Ethernet) Spanning Tree Protocol

11. MXcluster — 2:1 Redundancy

12. XRS12 — What is it? • Physical relay switch • Provides redundancy switching for CO circuits • Switches PCM, analog, or BRI circuits • 10 circuits to MX250s • 8 circuits to PSTN • Controlled over Ethernet • 19” rack, 1RU high • Runs Linux internally • Two LEDs: Power and Status

13. EPA3 — Ethernet Power Adapter • Small box • black or bone • Three Ethernet ports • one to network, two to peripherals • internal switch at full line rate • Network port takes Power over Ethernet • industry standard IEEE 802.3af • Cisco proprietary inline power • Outputs power to drive one peripheral • Five LEDs

14. EPA3

15. Power Input and Output • Power in can be from: • Power over Ethernet • dc power in from wall adapter • Power out is selectable • 5 V or 12 V • switch selectable underneath box • DC power in is 2.5 mm connector • DC power out is flying lead with 2.5 mm plug

16. Uses of EPA3 • Using EPA3 with ZIP 2 provides: • Power over Ethernet • second Ethernet port for PC • ability to draw power from Cisco switches with proprietary inline power • Use as standalone box for other IP devices • provides about 10 W • cameras • WiFi adapters