Carrier I-VU Server Recovery and Setup
This guide covers recovering and accessing legacy Carrier i-Vu servers when documentation is unavailable.
Understanding I-VU Server Architecture
Carrier i-Vu is built on Tridium Niagara AX or N4 framework. The server types include:
| Model | Platform | Typical Use |
|---|
| i-Vu Pro | Niagara AX/N4 | Enterprise server |
| i-Vu Link | Niagara AX | Building-level controller |
| i-Vu Open | Niagara N4 | Open protocol server |
| CCN Router | Proprietary | Legacy Carrier Comfort Network bridge |
Initial Assessment
Physical Inspection
- Check model label - Usually on bottom or back panel
- Identify ports - Ethernet, USB, serial, CCN bus
- Note LED status - Power, network activity, fault indicators
- Check for CompactFlash slot - Configuration may be stored on CF card
Power Requirements
- Most i-Vu devices use 24VAC (same as JACE controllers)
- Some rack-mount servers use standard 120VAC
- Verify power requirements before connecting
Network Access
Default Network Settings
Try these common default configurations:
| Setting | Default Value |
|---|
| IP Address | 192.168.1.100 or DHCP |
| Subnet Mask | 255.255.255.0 |
| HTTP Port | 80 or 443 |
| Platform Port | 4911 (Niagara) |
Connection Methods
Method 1: Direct Ethernet
- Connect laptop directly to server Ethernet port
- Set laptop to static IP in same subnet (e.g., 192.168.1.50)
- Open browser to https://192.168.1.100
- Try common default credentials (see below)
Method 2: Network Scan
- Connect server to same network as your laptop
- Use network scanning tool (Advanced IP Scanner, Angry IP Scanner)
- Look for devices with ports 80, 443, or 4911 open
- Niagara devices often show "Niagara" in HTTP banner
Method 3: Serial Console (if equipped)
- Connect via RS-232 serial cable
- Use terminal emulator (PuTTY, Tera Term)
- Settings: 115200 baud, 8N1
- May provide command-line access to network config
Default Credentials
Try these common factory defaults:
| Username | Password | Notes |
|---|
| admin | admin | Most common |
| admin | password | |
| admin | carrier | Carrier default |
| tridium | tridium | Niagara default |
| installer | installer | |
| guest | guest | Limited access |
Note: If credentials have been changed and are unknown, you may need to contact Carrier technical support or perform a factory reset (which may erase configuration).
Accessing Configuration
Web Interface
- Navigate to https://[IP_ADDRESS]
- Accept any certificate warnings (self-signed certs are common)
- Log in with credentials
- Navigate to Config > Station to view current setup
Workbench Access
- Open Niagara Workbench (matching version - AX or N4)
- File > Open > Open Platform
- Enter IP address and port 4911
- Log in with platform credentials
- Open the station from the platform
Database Backup
Once accessed, immediately create a backup:
- In Workbench: File > Backup
- Save .dist file to secure location
- Also export any graphics and schedules separately
Common Issues
Server Won't Boot
- Check power LED - solid green indicates power OK
- Try different power supply (24VAC transformers can fail)
- Listen for HDD/fan activity
- CompactFlash cards can corrupt - try removing and reseating
No Network Connectivity
- Verify Ethernet link LED on server and switch
- Try different cable
- Connect directly (eliminate switch issues)
- Check if network port is disabled in software
Forgotten Credentials
Options in order of preference:
- Contact Carrier technical support with device serial number
- Check with the installing contractor (credentials may be documented)
- Factory reset (WARNING: loses all configuration)
- Attempt password recovery via Tridium if you have the platform license
Evaluating Usability
Worth Recovering If:
- Hardware passes POST and boots normally
- Niagara license is valid (check license expiration)
- Contains programming for existing equipment
- Newer firmware can be applied
Consider Replacement If:
- Running Niagara AX 3.5 or older (security vulnerabilities)
- License has expired and can't be transferred
- Hardware is unreliable (repeated failures)
- Integration requirements exceed device capabilities
Next Steps After Recovery
- Document everything - Credentials, IP addresses, point counts
- Update firmware - If significantly outdated
- Review security - Change default passwords, disable unused services
- Create backups - Station backup, graphics export, database dump
- Evaluate migration - May be time to move to newer platform