© 2007 apc-mge corporation. infrastruxure central 4.1

© 2007 APC-MGE corporation.

InfraStruXure Central 4.1


What Is InfraStruXure Central?

InfraStruXure Central is a comprehensive management and monitoring solution for APC, NetBotz, and Non-APC SNMP devices.

InfraStruXure Central enables centralized management of APC devices: Configuration (WallBotz and RackBotz Only) Monitoring Reporting Graphing/Trending Private Network Video Surveillance Long term data storage


ISX Central — Overview

Acts as a centralized repository for critical power, cooling, and environmental data, as well as camera image data.

Server-based — allows the user to access, control, and configure the NetBotz system through a Web interface

Rack-mountable 1 U (ISX Central Standard) or 2 U (ISX Central Enterprise)


ISX Central—Overview How ISX Central Servers Work

ISX Central

Console

Applet

ISX Central

Console

Application

http or h

ttps

http or https

ISX Central Standard or Enterprise

NetBotz 320/420/500 Devices


Current APC Management Platform Landscape

Light Integration

Different HardwareDifferent Consoles

InfraStruXure Central 4.1

• Graphing and trending• Surveillance• Data warehouse• Mass configuration• SSL encryption• Support of all APC

devicesCameras

Environmental

• Security NetBotz Cameras CCTV Cameras• Environmentals NetBotz Sensors Dry contact• Light third party

Third Party NCPI

NetBotz

APCPDU

APCCRACs

InfraStruXure Manager

APCUPS

• Deep Power ManagementAPC only

• Deep Cooling ManagementAPC only

• Data Center Build-out tools

APCRPDU


How do I Do BMS and RMS support today?

APC InfraStruXure Managerwith 25 node license key

APC InfraStruXure Central v4.1

The Bundle

AP9490 for both, Standard editionAP9495 for both, Enterprise edition

•This option available for customers who require RMS support, BMS support, Mass configuration or Mass firmware updates of

APC devices


InfraStruXure® Central 4.xKey Features

Connected Devices can be split into groups Dynamic Groups—based on discovery Static Groups—based on administrator selection

Three different views of connected Devices Map View—view appliances based on location maps Table View—shows detailed status of each appliance Alerts View —shows appliance alerts and conditions

Allows for mass configuration of NetBotz Devices

Ability to graph and report environmental conditions


InfraStruXure Central 4.1 Standard

• Both systems ship with Rapid rails to optimize installs into APC racks.• Customers will need to purchase Versa rails in order to mount in 3rd-party racks.

InfraStruXure Central Standard Edition Hardware:

- 1 U rack mount 1U form factor Single 2.8GHz Pentium 4 (64-bit) 2GB RAM Single, 250GB SATA HDD

- Dual 10/100/1000 Ethernet - Single Power Supply (345W @ 1177 BTU)

Includes license for 25 nodes (devices)

Maximum number of managed devices:

- 1025 maximum number of devices- 125 Botz in surveillance mode


InfraStruXure Central 4.1- Enterprise

InfraStruXure Central Enterprise Edition Hardware:

- 2U rack mount- Dual 3.0 GHz Xeon Processor (64 bit)- 4GB RAM- 1.2TB of storage in RAID 5 array (1TB

usable)- 5 SCSI drives (300GB each)

- 5 hot plug SCSI drives- Dual 10/100/1000 Ethernet - Dual hot-swappable Power Supplies

(700W @ 2388 BTU) Includes license for 25 nodes

(devices) Maximum number of managed

devices:

- 1025 maximum number of devices- 250 Botz in surveillance mode

The key differences between the Standard and Enterprise systems are:• Redundant disks• Redundant power• Larger disk space for more historical data


NetBotz Standard vs. NetBotz Enterprise

Feature Standard Enterprise

Pre-Loaded Appliance Yes Yes

Rack-Mount Design Yes Yes

Physical Size 1 U 2 U

Drive Types IDE SCSI

Available Storage 250 GB 1 TB

Hardware Based RAID No Yes

Processor Type Pentium 4 Xeon

RAM 1 GB 4 GB

Network Adapters (2) 10/100/1000 (2) 10/100/1000

Hot-Pluggable Drives No Yes

Redundant Power Supply No Yes

Hot-Swappable Power Supplies No Yes

Standard Appliances Licensed 25 25

Differences are highlighted in blue


InfraStruXure Central 4.x – Software Architecture

InfraStruXure Central Software Architecture: All data (sensors and images)

stored in file system data repository

Postgres SQL used to store topology data and headers/pointers to info in the data repository

All communications to the appliances flows through the Apache/Tomcat software stacks via port 80 or port 443 (Ports are configurable)

InfraStruXure Central periodically polls all devices and retrieves current sensor readings and stores the information in data repository

InfraStruXure Central monitors all Devices for online/offline states

APC Devices are configured to send (via HTTP Post) alerts to InfraStruXure Central

Linux OS (64 Bit)(Based on 2.6 Kernel)

Apache WebServer

Postgres SQLDatabase

Tomcat(Java Servlet Server)

InfraStruXure CentralJava Applications (Servlets)

OpenSSL

Open Source NetBotz Source

File System DataRepository

(local or remote)

Spring Framework(Java)


Communication Modes—Overview

LAN Mode Default mode when appliances are added to ISX Central in a normal LAN/network environment

Bi-directional communication—ISX Central can initiate communications to appliances and vice versa

Post-Only Mode Special mode initiated by the appliance if there is a firewall between the appliance and the ISX Central and only the ISX Central has a public IP Address

Uni-directional communication—only NetBotz Appliances can initiate communication to ISX Central


InfraStruXure Central – Post Only Mode

Corporate Network

InfraStruXure Central

InternetIntranet

Remote Network

NetBotzDevice


InfraStruXure Central – Node Licensing

Device Licensing: A node = IP address Cameras no longer count as a node Ships with 25 nodes, can be expanded to 1025 25, 100, 500, and 1000 node keys SNMP, IPMI and DCAL (APC proprietary protocol) devices

that are directly managed by InfraStruXureC now count as nodes

NetBotz appliances with Advanced Device Crawlers (monitoring up to 48 devices) count as one node on InfraStruXure


InfraStruXure Central – Node Licensing

InfraStruXure Central – Node Licensing 25 nodes ships on ISX Central Standard and Enterprise Additional Node Licenses scalability of up to 1025

devices- 25 Node License AP9525 - 100 Node License AP95100- 500 Node License AP95500- 1000 Node License AP951000


InfraStruXure Central – Performance & Planning

Maximum Appliances per InfraStruXure Central The following are the maximum number of recommended devices

for InfraStruXure Central Standard and Enterprise.

These maximum configurations can only be achieved in optimized low load environments.

APC and Non-APC SNMP Devices

NetBotz Surveillance Devices

InfraStruXure Central Standard

1025 125

InfraStruXure Central Enterprise

1025 250

Note: The throughput difference between Standard and Enterprise is quite different. If Surveillance is going to be used, APC highly recommends InfraStruXure Central Enterprise.



FPS = frames per second

Resolution = camera resolution or picture size

Appliance Alerting = a notification from a NetBotz appliance that a threshold was breeched may include text, possibly pictures, possibly audio

Surveillance Clips = pictures sent to InfraStruXure Central as a result of detected motion.

Surveillance clips do NOT generate alerts.

Surveillance clips record video (and audio) until the motion stops (recorded at the InfraStruXure Central only).

Pictures Per Alert = defines the number of pictures captures per alert



InfraStruXure Central performance is greatly affected by the following factors: Network throughput (10Mb vs 100Mb, vs 1Gb) Number of appliances managed by InfraStruXure Central Camera Frame Rate Camera Resolution Alerting Frequency Alerting Overlap Pictures per Alert Surveillance Activity Surveillance Overlap Number of active consoles



For the NetBotz version 2 appliances, APC recommends the following camera capture settings for alerting and/or surveillance: Option 1:

- Resolution = 640 x 480- Frames per Second = 1 or 2

Option 2:- Resolution = 320 x 240- Frames per Second = 4 or 5

For alerting capture, NetBotz recommends not capturing more than 25 seconds of video per alert. If more than 25 seconds of video is required, then it may be more appropriate to

utilize surveillance instead of camera motion or door switch alerts.

Optimize what initiates camera motion and surveillance activity by properly configuring camera masking, sensitivity, and area of motion. Essentially tuning the camera to only capture video when something “interesting” is

happening.

Audio recording does not affect InfraStruXure Central to a large degree, but it does place an additional load on the appliance so only enable when necessary.


InfraStruXure Central Data Polling Data Polling Overview for Managed and Monitored Devices InfraStruXure Central polls each device periodically to gather sensor readings (default is 10

minutes).

For managed and monitored devices all historical sensor readings and current sensor readings are returned since the last poll request.

Only reading changes are returned. For example if humidity has been holding steady at 42% for the past 15 minutes and the InfraStruXure Central is polling every 15 minutes; then no sensor information is returned and no new data is stored in the InfraStruXure Central database.

Therefore amount of data returned per appliance is completely variable. If the environment your devices are located in static, then very little data will be returned. If the environment your devices are located in is dynamic, then more data will be returned.

Each data point that changes results in 50 bytes of data being sent and stored in the repository

Tests indicate that version 2 appliances in a typical office setting have about 1900 changes per day to their various standard sensors.

These 1900 changes per day equate to about 94 KB of data per day (or 3MB per month) per device.



Alert Throughput (Standard & Enterprise) The maximum number of alerts a InfraStruXure Central can

handle is variable depending on the contents of the alerts. Text alerts Picture alerts (picture qty, size of pictures, etc.)

InfraStruXure Central can handle a maximum of 150 alerts per minute sustained (9000 alerts per hour) Assuming the alerts are picture alerts containing 15 pictures captured at

640x480 resolution

Note: An alert is about 400bytes of text data plus pictures, audio and graphs.



Surveillance Throughput for InfraStruXure Central Local Storage

InfraStruXure Central can sustain a maximum of incoming surveillance frames (Regardless of resolution and SSL; Assumes Gigabit connection and local repository): InfraStruXure Central Standard Max frame rate = 250 FPS InfraStruXure Central Enterprise Max frame rate = 500 FPS

The max FPS can be divided among as many or as few NetBotz cameras (not appliances).

InfraStruXure Central Standard Example: 62 cameras at 640x480 at 4 frames per second. 125 cameras at 640x480 at 2 frame per second

InfraStruXure Central Enterprise Example: 125 cameras at 640x480 at 4 frames per second. 250 cameras at 640x480 at 2 frame per second


InfraStruXure 4.1 Distributed Architecture


NAS

NAS*

V1 Pod sharing with a NetBotz 500*


Dual posts fordisaster recovery*

* BotzWare 2.6 needed for 420 NAS support, dual surveillance posts, and V1 pod sharing

Java console(v 1.5.0_06) NAS

NAS


ISX Central – Possible IP Connections

ISX-CConsole

HTTP or HTTPS

SNMPManager

SNMP

HTTP or HTTPS NetBotzAppliance

SMTPEmail Svr

DNSDNS Svr

NFSNAS/SAN

CIFSNAS/SAN

NetBotzAppliance

HTTP or HTTPS


Data Repository And Types NAS: Network Attached Storage examples:

File server, NAS appliance, etc.

NAS Storage uses the following protocols most commonly: CIFS:

- CIFS: Common Internet File System, this protocol is the successor to SMB. CIFS implements all of SMB’s features with more stringent security, fault tolerance, and increased performance.

- CIFS are commonly used to connect Windows PC’s and Windows to UNIX/Linux servers/clients.

NFS:- Network File System, similar to SMB & CIFS, NFS is another protocol that enables

the file system on a remote system to be accessible on the local system.- NFS is more common in the UNIX world allowing UNIX/Linux servers to share

files/folders more easily.

WarningLocal NAS must have gigabyte connection. NFS is 50% slower than CIFS


Hardware Level Examples for Distributed Storage

Different levels of NAS Hardware

Hardware examples for Basic NAS - Desktop class hardware- Entry Level Server- IDE / SATA Drives

Hardware Examples For Premium NAS- Medium to high end servers- Containing SCSI / Fiber Drives

NetBotz recommends premium NAS for solutions involving surveillance


InfraStruXure Central – Performance & Planning NAS

Surveillance Throughput for InfraStruXure Central With NAS Storage

InfraStruXure Central standard can sustain a maximum of incoming surveillance frames when using NAS storage Local 250FPS NFS Basic 125FPS NFS Premium 200FPS CIFS Basic 125FPS CIFS Premium 350FPS

InfraStruXure Central Enterprise can sustain a maximum of incoming surveillance frames when using NAS storage Local 500FPS NFS Basic 125FPS NFS Premium 275FPS CIFS Basic 125FPS CIFS Premium 500FPS

Note: Assumes gigabyte connection from InfraStruXure Central to NAS



Day Week Month 3Months

6Months

1 Year 2 Years 3 Years

1 94KB .6MB 2.8MB 8.3MB 16.6MB 33.1MB 66.2MB 99.4MB

10 .9MB 6.4MB 27.6MB 82.8MB 165.6MB 331.2MB 662.4MB 993.6MB

15 1.4MB 9.7MB 41.1MB 124.2MB 248.4MB 496.8MB 993.6MB 1.5GB

25 2.3MB 16.1MB 69.0MB 207.0MB 414.0MB 828.0MB 1.6GB 2.4GB

50 4.6MB 32.2MB 138.0MB 414.0MB 828.0MB 1.6GB 3.2GB 4.9GB

100 9.2MB 64.4MB 276.0MB 828.0MB 1.6GB 3.2GB 6.5GB 9.7GB

150 13.8MB 96.6MB 414.0MB 1.2GB 2.4GB 4.9GB 9.7GB 14.6GB



500 46.0MB 322.0MB 1.3GB 4.0GB 8.1GB 16.2GB 32.3GB 48.5GB

Disk Space Consumption for Sensor Reading Data Only



Disk-space Consumption for Alerts and Sensor Data Assumptions:

Version 2 Appliances 3 text alerts per day per appliance 3 picture alerts per day per appliance (15 640x480 pictures, no audio)

Number ofAppliances Day Week Month

3Months

6Months 1 Year 2 Years 3 Years

1 2.3MB 16.3MB 70.1MB 210.2MB 420.4MB 840.7MB 1.6GB 2.5GB


15 35.0MB 245.2MB 1050.9MB 3.1GB 6.2GB 12.3GB 24.6GB 36.9MB

25 58.4MB 408.7GB 1.7GB 5.1GB 10.3GB 20.5GB 41.1GB 61.6GB

50 116.8MB 817.4MB 3.4GB 10.3GB 20.5GB 41.1GB 82.1GB 123.2GB





500 1.1GB 8.0GB 34.2GB 102.6GB 205.3GB 410.5GB 821.0GB 1231.5GB



#

Cams

1

Day

1

Week

1

Mnth

2

Mnth

3

Mnth

4

Mnth

5

Mnth

6

Mnth

7

Mnth

8

Mnth

9

Mnth

10

Mnth

11

Mnth

12

Mnth

1 0.4 2.5 9.8 19.6 29.4 39.2 49.0 58.8 68.6 78.4 88.2 98.1 107.9 117.7

10 3.5 24.5 98.1 196.1 294.2 392.2 490.3 588.3 686.4 784.4 882.5 980.5 1078 1176

15 5.3 36.8 147.1 294.2 441.2 588.3 735.4 882.5 1029 1176 1323 1470 1617 1765

25 8.8 61.3 245.1 490.3 735.4 980.5 1225 1470 1715 1961 2206 2451 2696 2941

50 17.5 122.6 490.3 980.5 1470 1961 2451 2941 3431 3922 4412 4902 5392 5883

100 35.0 245.1 980.5 1961 2941 3922 4902 5883 6863 7844 8824 9805

Surveillance Disk Space Consumption (GB)

Assumptions:• Version 2 appliances • Low Activity Scenario (1 hour of video recording per day)• 640x480 at 2 FPS• No Audio



Total Disk-space Consumption The amount of disk space consumed per year is an

aggregate of the following: Polled data (sensor readings) Alert data (including pictures and audio)

- 400 bytes of text data- plus pictures data if applicable- plus audio data if applicable

Surveillance data (pictures and audio)- Picture data- plus audio data if applicable



Multiple InfraStruXure Centrals Obviously if there are more NetBotz appliances than a single

InfraStruXure Central can manage, then multiple InfraStruXure Central systems will have to be deployed.


Console Views—Overview Map View



Hierarchy of groups—shows groups within groups

Groups



Roll-Over Help—shows details of the appliance



Right click on the device to view status.

Data sets available for easy navigation



Double-clicking appliance shows advanced view


Console Views—Overview Table View

View selected group in table format Reorder table by columns Configure which columns are shown


Console Views—Overview Table View

Double-clicking appliance shows advanced view


Console Views—Overview Alerts View

Summary of alerts from appliance based on date View details of each alert Listen to audio (if applicable) Unresolved alerts have red background Ability to delete multiple alerts at once


Console Views—Overview Alerts View—Detailed View

Details of alert with graphs and pictures


Console Views—Overview Graph and Report View

Graph internal and external sensor readings Graph same type sensors on same graph


Console Views—Overview Graph and Report View (cont.)

Zoom into graph Save graph as .jpeg or .bmp file or export data as text file


Console Views—Overview Graph and Report View (cont.)

Reports (table format) on all sensors, applications, and alerts Export report data as a text file


InfraStruXure® Central 4.x Surveillance

Add-On Application for ISX Central

Allows the user to license specific cameras in “surveillance mode”

Allows user to view multiple cameras simultaneously in the live camera view

Captures video for as long as motion occurs

All captured video is only stored in ISX Central and NOT store in the individual Appliances


InfraStruXure® Central 4.x Surveillance

Camera Motion Standard with Standalone

Appliances and ISX Central

Only captures video for a finite amount of time/frames once motion is detected

Does not capture again until motion stops and then is detected again

Surveillance Add-On Application for ISX

Central only Captures video for as long as

motion occurs Navigation of historical clips Simultaneous viewing of

multiple cameras

• Camera Motion vs. Surveillance


Questions?

Q U E S T I O N S ?


InfraStruXure® Central 4.xInstallation – Initial Network

Configuration


Installation—InfraStruXure® Central 4.x Applications

Place the ISX Central Installer CD-Rom in the drive of the system used to configure and manage the ISX Central (customer’s system) Windows systems—the ISX Central Installer will start

automatically Linux or Solaris systems—run install.bin from the sub-

directory on the CD


Installation—NetBotz Applications

The InstallAnywhere window appears indicating that the software is preparing to install


Installation—ISX Central Applications

The Welcome screen appears—select “Next” to continue


Installation—ISX Central Applications

The Important note screen appears to exit all ISX central application. Click “Next” to continue



The License Agreement window appears Click “I Accept the terms of the License Agreement” Click “Next”



The Choose Install Set window appears Choose “Typical” to install the Serial Configuration Utility

and ISX Central Control Console Application Click “Next” to continue



The Choose Install Folder window appears prompts you to choose an installation location Click “Next” to continue



The Pre-Installation Summary window appears confirming the installation information Click “Install” to continue



The Installation window appears indicating the progress of the installation



The Install Complete window appears Click “Done” to finish the installation and close the ISX

Central Installer


Installation—Initial Network Configuration

Initial Network Configuration Complete before physical installation, by performing the

following procedure:

1. Ensure that the power cord and the Ethernet cord of the ISX Central are connected

2. Connect one end of a null modem cable to the ISX Central and the other end to your laptop computer

Null modem cableISX Central

(Enterprise version shown) Laptop computer



Initial Network Configuration (cont.)3. Start the NetBotz Serial Configuration Utility

• (Start Programs ISX Central Help and Tools ISX Central Serial Configuration Utility)



Initial Network Configuration (cont.)4. When the ISX Central has finished starting up

select the “Next” button to continue. Note: The device may take up to 2 minutes to fully start up.



Initial Network Configuration (cont.)5. The serial configuration will search for NetBotz

appliances attached to your computer through the serial port

Select “Next”

Select appropriate port/appliance



Initial Network Configuration (cont.)

6. You will be prompted for a password in the Root Password window—enter the default password “apc” and select OK



Initial Network Configuration (cont.)7. Select the radio button for “Configure using

these settings” and enter the IP Address, Subnet Mask, and Default Gateway for the device



Initial Network Configuration (cont.)8. Configure the DNS information for the device

by completing the information under “DNS Settings”

9. Select “Next” to continue



Initial Network Configuration (cont.)

10. Enter ISX Central hostname and Click “OK” to continue.



Initial Network Configuration (cont.)11. Shutdown ISX Central to save network

settings.



Initial Network Configuration (cont.)11. The final screen displays the configured

network settings — select “Back” to make any changes to the information or “Finish” to exit the utility


Using LDAP With ISXC


What is LDAP? Lightweight Directory Access Protocol

Active Directory is an Implementation of LDAP

LDAP servers manage users, user groups, resource access, and in some cases name resolution.


Why Use LDAP with ISXC? Users do not need to memorize additional

passwords

Administrators do not have to maintain user accounts on ISXC

Password policy is based on company standard.


Before You Begin Customer must have a LDAP search account

Customer must know the hostname of the LDAP server

Customer must know the search base of the users and user groups they wish to have login access


Steps To “Bind” ISXC to LDAP

Provide search user account and search base so that ISXC can access the LDAP server

Explore the LDAP tree adding user groups and users as needed through the provided ISXC interface

Assign LDAP users and groups device group access on ISXC


Adding an LDAP Server to ISXC


Configuring the Bind


The Bind User The Bind User DN must be explicitly typed out in

perfect syntax.

The bind user DN MUST HAVE permission to search the search base with the users and groups that ISXC will user

Experience shows that people rarely input the right syntax the first time.


Bind DN Syntax Example Bind User DN: cn=John Smith, ou=AMS, dc=defaultcorp,

dc=com (cn) stands for Canonical Name: It is the long name for the user and

sometimes a built in container group in active directory (ou) stands for organizational unit: Most Directories created by

users in active directory are organizational units (dc) stands for domain component: Normally this is used to

specify the domain portion of the BIND DN. In active directory it is required, while in other LDAP implantations it can be optional.

Commas must be escaped with \ The bind DN starts with the canonical name of the user , then the

organizational unit if applicable, and finally with the domain components if needed.

On Active Directory a container “folder” does not have the little are work in the folder icon, while a Organizational Unit Does


Is it an OU or a CN?


Determining the BIND DN The BIND DN is NOT the

login name

2003.aus-lab.netbotz.com is the DC portion

Users would normally be the OU, but on Active directory it is a CN as it is a built in container. (See previous slide)

“directory search” is the user name or canonical name (CN)


Final Bind DN cn=directory search, cn=Users, dc=2003, dc=aus-

lab, dc=netbotz, dc=com


Search Base The search base specifies the top level folder of ISXC’s

LDAP access.

ALL USERS and USER GROUPS that ISXC authenticates with must be in the search base.

If a user is a member of a Group that is in the search base, but the user is not in the search base, login will be denied.

Users and User Groups within the search base will not be allowed to login to ISXC unless they are explicitly added later in the configuration.

Being in the search base only allows an ISXC administrator to add the user or group, it does not grant automatic access.


Active Directory Search Base In this example the administrator chooses to allow login only from

users/groups in the AMS Organizational Unit Search base is : ou=AMS , ou=Corp, dc=2003, dc=aus-lab, dc=netbotz,

dc=com


Complete Configuration


Adding Users and Groups When the bind is successful Users and Groups

can be added through the GUI tool

On the User/Group Configuration screen, only ISXC Admin privileges can be given. All other privileges must be added per device group

You must click on a folder in the left pain for users and groups to appear in the center.

Users and Groups are displayed by their Canonical name, not by login.


User/Group Browser


Granting Per Device Group Permissions to LDAP Users


LDAP Behavior When Directory Server is Down, users cannot log in LDAP users cannot change their password (Through ISXC) Users will login with their login IDs, not their canonical names LDAP users can be added and deleted from ISXC without

interrupting current connections If a LDAP ID has the same username as an ISXC local ID, then the

ISXC local ID is preferred. A local administration account must remain on ISXC (ISXC will not

let you delete this local account) ISXC NEVER modifies any data within the directory server, and

does not process any permissions data other than group membership and account id/password authentication

Official tested support for Open LDAP and Active Directory only, but L3 will attempt to make any LDAP compliant system work.


Trouble Shooting The most common problem with LDAP is a syntax

error in the Bind DN. Make sure that the BIND DN has the bind user’s

canonical name and not their login id Make sure that if the bind user is in an OU, that ou is

specified and if it is in a container that cn is specified. Make sure commas are escaped out with \ (you can

escape a \ with \\) Sometimes DNS and DCs are not the same especially in

companies that have migrated from legacy X.500 implementations


Trouble Shooting The Second most common problem with LDAP is

lack of permission on the search user. If strange error messages appear try a normal LDAP user

account, just to test to see if it is a permissions problem Try an admin level account if that doesn’t work.


Trouble Shooting If a customer has more than 50,000 users or

groups in a singe OU and their client is crashing in the LDAP browser. There is a known issue about handling a massive amount

of users and groups in the same OU. The client runs out of memory as we limit memory usage to 256MB

The solution is to increase the amount of RAM the client can use. In c:\programs\(ISXC version) there is a file called “InfraStruXure Central Console.lax”

Edit the line in this file that displays lax.nl.java.option.java.heap.size.max=268435456to displaylax.nl.java.option.java.heap.size.max=536870912

Restart Client


Questions?

Q U E S T I O N S ?

© 2007 apc-mge corporation. infrastruxure central 4.1

Documents