Installation and Start-Up
After you have completed the hardware installation procedures outlined in the the relevant Hardware Installation Guide, you are ready to establish a connection to your Oracle Communications Session Border Controller. Then you can load the software image you want to use and establish basic operating parameters.
Hardware Installation Process
Installing the Oracle Communications Session Border Controller hardware in a rack requires the following process.
Connecting to Your Oracle Communications Session Border Controller
You can connect to your Oracle Communications Session Border Controller either through a direct console connection, or by creating a remote SSH session. Both of these access methods provide you with the full range of configuration, monitoring, and management options.
Note:
By default, SSH and SFTP connections to your Oracle Communications Session Border Controller are enabled.Create a Console Connection
Using a serial connection, you can connect your laptop or PC directly to the Acme Packet hardware. If you use a laptop, you must take appropriate steps to ensure grounding.
One end of the cable plugs into your terminal, and the other end plugs into the RJ-45 Console port on the NIU (or management ports area on the Acme Packet 6300).
To make a console connection to your hardware:
SSH Remote Connections
For increased security, you can connect to the Oracle Communications Session Border Controller using SSH.
The Oracle Communications Session Border Controller supports five concurrent SSH and SFTP sessions. Only one SSH session may be in configuration mode at a time.
To SSH to your Oracle Communications Session Border Controller, you need to know the IP address of its administrative interface (wancom0/eth0). The wancom0/eth0 IP address of your Oracle Communications Session Border Controller is found by checking the inet on ethernet value in the boot parameters or visible from the front panel display.
You can manage incoming SSH connections from the ACLI:
- SSH service is enabled by default.
- To set a time-out due to inactivity, use the telnet-timeout parameter in the system configuration. You can set the number of seconds that elapse before the SSH connection is terminated. The default for this field is 0, which means that no time-out is being enforced.
- To view the users who are currently logged into the system, use the ACLI show users command. You can see the ID, timestamp, connection source, and privilege level for active connections.
- From Superuser mode in the ACLI, you can terminate the connections of other users in order to free up connections. Use the kill user command with the corresponding connection ID.
- If you reboot your Oracle Communications Session Border Controller from a SSH session, you lose IP access and therefore your connection.
There are two ways to use SSH to connect to the Oracle Communications Session Border Controller. Either connect via SSH without specifying users and SSH user passwords, or initiate the SSH connection using custom SSH credentials.
Accessing the System Via User and Admin Accounts
You may access the Oracle Communications Session Border Controller via SSH connection without specifying users and SSH user passwords.
- Open your SSH client (with an open source client, etc.).
- At the prompt in the SSH client, type the
ssh command, a Space, the IPv4 address of your
Oracle Communications Session Border Controller, and then press Enter.
The SSH client prompts you for a password before connecting to the Oracle Communications Session Border Controller. Enter the Oracle Communications Session Border Controller’s User mode password. After it is authenticated, an SSH session is initiated and you can continue with tasks in User mode or enable Superuser mode.
Accessing the System Using Custom SSH Credentials
You may initiated an SSH connection using custom SSH credentials.
- In the ACLI at the Superuser prompt, type the ssh-password and press Enter.
- Enter the name of the user you are creating.
- Enter a password for the user when prompted.
Note:
Passwords do not appear on your screen.ORACLE# ssh-password SSH username [saved]: MJones Enter new password: 95X-SD Enter new password again: 95X-SD
Once you have configured ssh-password, the SSH login accepts the configured username and password, as well as the default SSH/SFTP usernames, user and admin.
- Configure your SSH client to connect to your
Oracle Communications Session Border Controller’s management IPv4 address using the username you just created. For example:
ssh -l MJones 10.0.1.57
- Enter the SSH password you configured in the ACLI.
MJones@10.0.2.54 password: 95X-SD
- Enter your User password to work in User mode on the Oracle Communications Session Border Controller. Enable Superuser mode and enter your password to work in Superuser mode.
Import Private SSH Key to Derive New SSH Host Keys
The Oracle Communications Session Border Controller supports importing externally generated SSH keys to replace the internally generated SSH host keys. Because the OCSBC derives the public key from the private key, only the externally generated private key needs to be imported. The OCSBC uses these keys when it functions as an SSH server. The OCSBC supports RSA or DSA key lengths of 1024, 2048, 3072, or 4096 bits.
Import a Private SSH Key for the OCSBC as an SFTP Client
As an alternative to relying on the SSH keys generated by the Oracle Communications Session Border Controller, customers may import externally generated SSH keys for any configured public-key element. Because the OCSBC derives the public key from the private key, only the private key needs to be imported, and any previously generated keys for this public-key element will be overwritten. The OCSBC uses these keys when it functions as an SFTP client.
Configure SSH Ciphers
The ssh-config configuration element controls which ciphers the Oracle Communications Session Border Controller offers during SSH session negotiation.
Each command takes an argument which is either a single word or a
comma-separated list within double quotes. Type
?
to
see the available algorithms for this release.
System Boot
When your Oracle Communications Session Border Controller boots, the following information about the tasks and settings for the system appear in your terminal window.
- System boot parameters
- From what location the software image is being loaded: an external device or internal flash memory
- Requisite tasks that the system is starting
- Log information: established levels and where logs are being sent
- Any errors that might occur during the loading process
After the loading process is complete, the ACLI login prompt appears.