Navigation
Back up to About Overview
[+] Expand All
[-] Collapse All
Symbols
A
- access privilege levels
- accounting
- applications
- description
- TACACS+, configuring
- admin permission
- admin-control permission
- all permission
- announcements at system login
- APIs (application programming interfaces)
- CORBA plug-in SPI
- CORBA remote API
- description
- SAE core API 1, 2
- application programming interfaces. See APIs
- architecture
- authentication 1, See also user accounts
- configuration example
- multiple methods
- RADIUS
- shared user accounts 1, 2
- TACACS+
- TACACS+, configuring
- TACACS+, configuring with C-Web interface
- TACACS+, configuring with SRC CLI
- template accounts
- authentication order
- configuring with C-Web interface
- configuring with SRC CLI 1, 2
- overview 1, 2
- removing authentication method
- removing authentication method with SRC CLI
B
C
- C Series Controller
- C Series Controllers
- C-Web interface
- committing a configuration
- configuration options
- configuring
- HTTP access 1, 2
- HTTPS access 1, 2
- logging properties
- copying an object
- deleting an object
- editing level
- elements
- getting Help
- icons
- layout
- loading configuration values
- logging out
- moving an object
- navigating
- overview 1, 2
- password, changing
- Policies, Services, and Subscribers
- renaming an object
- reverting a configuration
- starting
- updating configuration data
- username, changing
- C2000 Controller
- C3000 Controller
- C4000 Controller
- C5000 Controller
- clear permission
- cli
- client mode, NTP
- commands
- configuration statements
- configure permission
- control permission
- conventions
- customer support 1
- cweb-password
D
- date on system
- deployment scenarios
- DES (directory eventing system)
- differentiated QoS
- digital certificates. See security
- directory
- directory connection properties
- directory eventing system
- directory server
- documentation
- draft RFCs
- dynamic webpages
E
F
G
- Gigabit Ethernet interfaces, configuring IPv4
- Gigabit Ethernet interfaces, configuring IPv6
- GRE tunnel interfaces
- group interfaces, configuring 1
H
I
J
- Java Naming and Directory Interface. See JNDI
- java-heap-size, configuring
- JNDI (Java Naming and Directory Interface)
- Juniper Networks database
- adding Juniper Networks database to community
- changing modes
- community mode
- community mode configuration
- configuration example
- configuration statements
- configuring
- data recovery
- high availability
- loading sample data
- neighbors 1, 2
- overview 1, 2
- redundancy
- roles
- changing secondary to primary, SRC CLI
- overview 1, 2
- standalone mode
- verifying configuration
- Juniper-Allow-Commands attribute (RADIUS)
- Juniper-Allow-Configuration attribute (RADIUS)
- Juniper-Deny-Commands attribute (RADIUS)
- Juniper-Deny-Configuration attribute (RADIUS)
- Juniper-Local-User-Name attribute (RADIUS)
L
- LDAP (Lightweight Directory Access Protocol). See directory; directory server
- LDAP directory. See directory
- leases for licenses. See license server
- license
- license manager
- configuration statements
- configuring
- license server
- license usage
- Lightweight Directory Access Protocol. See LDAP
- load balancing
- local password authentication
- local properties
- logging, See also system log server
- login announcements, system
- login classes
- configuration
- configuration examples
- configuration prerequisites
- configuration statements
- configuration verification
- default classes
- idle timeout values
- options
- overview
- predefined
- privilege level options
- privilege levels
M
- maintenance permission
- manuals
- messages
- MII monitor
- configuring
- Monitoring Agent
- multicast
N
- NAS ID, configuring for SAE
- network
- network information collector. See NIC
- NIC (network information collector)
- notice icons
- NTP (Network Time Protocol)
- NTP,
O
- on-demand services 1, 2
- open interfaces
- operator login class
- operators, regular expression
- OSS integration
P
- passwords
- permissions
- policies
- Policies, Services, and Subscribers CLI. See SRC CLI
- Policies, Services, and Subscribers tasks. See C-Web interface
- policy management
- ports
- predefined login classes
- primary directory
- privilege levels 1
- product features 1, 2
R
- RADIUS
- RADIUS authentication. See authentication
- RADIUS authorization. See authentication
- read-only login class
- redundancy
- references
- regular expressions
- request license import file-name command
- reset permission
- residential portal
- resolving hostnames
- retrieving directory changes
- RFCs 1, 2, 3
- root account 1
- router running Junos OS
- router running JunosE Software
- routing permission
- routing-control permission
S
- SAE (service activation engine)
- configuring groups
- deleting default configurations
- SRC CLI 1, 2
- description 1, 2
- initial properties, overview
- starting
- stopping
- verifying status
- SAE (service activation engine), configuring initial properties
- SAE (service activation engine), configuring NAS ID
- SAE (service activation engine), configuring RADIUS address
- sample data
- secondary directory
- secret permission
- secret-control permission
- security
- digital certificates 1
- clearing certificates 1, 2
- clearing requests
- prerequisites
- requesting certificates 1, 2
- requesting certificates through SCEP
- viewing certificates
- security permission
- security-control permission
- server license. See license
- service activation engine. See SAE
- service permission
- service-control permission
- services
- shared user accounts
- shell permission
- SNMP agent
- access control, configuring on C Series Controllers
- community strings 1, 2
- named views
- SNMP groups
- VACM
- configuration statements 1, 2
- configuring
- description
- directory connection parameters, configuring
- Java Runtime Environment, configuring
- local properties, configuring
- logging, configuring
- monitoring
- named views, defining
- notification targets, configuring
- starting
- stopping
- system information, configuring
- trap history, configuring
- SNMP Agent
- snmp control permission
- snmp permission
- SNMP traps
- notification targets, configuring
- snmp-named-views-cli
- snmp-security-names-cli
- snmp-statements
- software standards
- SRC ACP (SRC Admission Control Plug-In)
- SRC CLI 1
- directory connections
- overview
- Policies, Services, and Subscribers CLI
- starting
- SRC components
- SRC software
- configuration prerequisites
- configuring
- creating, virtualized instance 1
- description
- features and benefits 1, 2
- financial advantages
- OSS integration
- recovering
- services
- snapshot on C Series Controller
- upgrading
- USB Storage Device
- virtualization
- virtualization, requirement
- SSH (secure shell)
- standards 1
- static host mapping
- static routes, configuring
- Steel-Belted Radius/SPE server 1, 2
- subscriber
- subscriber permission
- subscriber-control permission
- superuser login class
- support, technical See technical support
- symmetric active mode, NTP
- system authentication. See authentication
- system log server
- configuration prerequisites
- configuration statements
- message groups
- message severity levels
- messages
- messages, file
- messages, server
- messages, user notification
- overview
- system login
- system permission
- system-control permission
T
- TACACS+ authentication. See authentication
- tariff models
- technical support
- Telnet connection to remote host
- template authentication accounts
- text conventions defined
- third-party URLs
- tunnel interfaces
- tunnel interfaces, configuring
U
- UIDs
- unauthorized login class
- unresponsive directories
- usage data
- user accounts 1, See also login classes
- authentication
- configuring passwords
- configuring SSH authentication
- root password 1, 2
- authentication method and password
- configuration
- configuration verification 1, 2
- example
- overview 1, 2, 3
- shared
- user notification messages
V
W
- Web application server
- application deployment 1, 2
- channel stack
- configuration statements
- configuring the Web application server
- installing Web applications inside
- local properties
- multicast-address
- node-id
- overview
- removing Web applications from
- restarting
- shared cluster name
- shared cluster nodes
- shared cluster properties
- starting
- stopping
- viewing cluster history
- viewing cluster status
- viewing statistics
- Web Services Gateway
Download This Guide
Related Documentation
Creating a Virtualized SRC Instance
You can create a virtualized SRC instance by using the iso, qcow2, or vmdk image.
 | Note: We recommend you to create a virtualized SRC instance by using the qcow2 image. |
- Creating a Virtualized SRC Instance Using qcow2 Image
- Creating a Virtualized SRC Instance Using iso Image
- Creating a Virtualized SRC Instance Using the vmdk Image
Creating a Virtualized SRC Instance Using qcow2 Image
To create a virtualized SRC instance on the KVM hypervisor by using the qcow2 image:
- Download the qcow2.gz image from https://www.juniper.net/support/downloads/?p=src#sw and place it on the host operating system.
- Unzip the image on the host operating system.
gunzip name.qcow2.gz - Download the SDK+AppSupport+Demos+Samples.tar.gz file from https://www.juniper.net/support/downloads/?p=src#sw and place it on the host operating system.
- Untar the file to use the create_vm.py script for creating
a virtualized SRC instance.
tar –xzvf SDK+AppSupport+Demos+Samples.tar.gz - Execute the create_vm.py script from the path where the
SDK+AppSupport+Demos+Samples.tar.gz is extracted.
#$cd <sdk_root_folder>/SDK/vSRC/#$./create_vm.pyNote: The create_vm.py script is not supported for VMware virtual machine creation. To create a virtualized SRC instance on VMware hypervisor, use the iso or vmdk image.
The script requests various details for creating the virtualized SRC instance.
- Enter the requested details. The details requested by
the script are:
- Name for the virtualized SRC instance
- Number of CPUs to be allocated for the virtualized SRC instance
- Memory (in megabytes) to be allocated for the virtualized SRC instance
- Network configuration details:
- Number of interfaces to be configured
- Media access control (MAC) address for each interface. You can enter MAC address or allow the script to create the MAC address automatically.
- Networking mode for each interface. The supported modes
are:
- Direct host device mapping with bridge mode—Use this mode if multiple network interfaces have to be shared with a host device (for example, eth0). This mode is ideal for hosting multiple virtualized SRC instances with multiple interfaces. This is the default mode.
- Direct host device mapping with passthrough mode—In this mode, one-to-one mapping is done between the host device network interface and virtualized SRC instance’s network interface. You can use this mode when only one virtualized SRC instance is hosted in the server.
- Shared bridge mapping (bridge has to be manually configured)—In this mode, you have to manually configure the bridge and provide the shared bridge name as an input. This mode provides flexibility to have more complex networking.
- Path of the qcow2 image file
The script creates an xml file with the name of the virtualized SRC instance and creates the virtualized SRC instance by using the virsh command. The xml file contains one serial console configuration and one vnc console configuration.
Note: You must have the virsh management tool in the host operating system for the script to successfully create the virtualized SRC instance.
- Log in to the virtualized SRC instance through any hypervisor management tool and set up the initial configuration for the SRC software. For information about the initial configuration, see your C Series Controller Hardware Guide.
Creating a Virtualized SRC Instance Using iso Image
To create a virtualized SRC instance on VMware and KVM hypervisors by using the iso image:
- Download the iso image from https://www.juniper.net/support/downloads/?p=src#sw and place it in the host operating system.
- Start installing the iso image in the virtual machine
by using the hypervisor management tool (such as virt-manager, virsh, VMware vSphere client, and VMware Workstation
Player). The virtual machine boots from the iso image
and prints the following message:
Welcome to SRC PE Software Installation. WARNING: This system recovery software replaces all data and software on the system disk image. As a result, any data, including data previously in the snapshot partition, is lost. After you run the system installation software, the virtual image contains the SRC software, including the SRC operating system, but no configuration data. To continue, press <TAB> and choose the installation type. To enable serial console enter following after choosing the Installation type : “console=tty0 console=tty50, 9600 To cancel this operation, power off the system and remove the iso image. boot: AUTO Manual rescue boot:
- At the boot prompt, type the installation option.
- If the typed option is AUTO, the disk space is partitioned
automatically and the packages are installed. The following hard disk
partition scheme is used:
- /—8.5 GB
- /var—50 percent of remaining hard disk space
- 50 percent of remaining hard disk space can be used for storing snapshots
- If the typed option is Manual, you can define the partition
scheme and other general settings (such as language) through the displayed
dialog boxes to install the SRC software.
Note: You cannot create snapshot or restore snapshot with custom partition scheme. We recommend you to use the virsh snapshot-create command on KVM hypervisor and use the Snapshot option in the VMware Workstation Pro or VMware ESXi hypervisor to maintain snapshots of disk image.
- If the typed option is AUTO, the disk space is partitioned
automatically and the packages are installed. The following hard disk
partition scheme is used:
- After the successful installation, reboot the virtual machine.
- After the virtual machine reboots, set up the initial configuration. For information about the initial configuration, see your C Series Controller Hardware Guide.
Creating a Virtualized SRC Instance Using the vmdk Image
Virtual Machine Disk (vmdk) is a file format that describes containers for virtual hard disk drives to be used in VMware virtual machines. The vmdk image shipped with the SRC software is of the monolithicSparse type, and the image has been tested with monolithicSparse and monolithicFlat types. If you are using VMware ESXi, either the iso image or the vmdk image of monolithicFlat type must be used. To convert the monolithicSparse type to the MonolithicFlat type, use the qemu-img convert -f vmdk vmdk-file-name-MonolithicSparse -O vmdk output-file-name -o subformat={ monolithicFlat } command. To use this command, you must have the qemu-img tool installed in your system.
| Note: The SRC software installation is currently supported and tested over the VMware Workstation 12 Player, VMware Workstation 12 Pro, and VMware ESXi 5.5.0. |
To create a virtualized SRC instance on VMware hypervisor by using the vmdk image:
- Download the vmdk image from https://www.juniper.net/support/downloads/?p=src#sw and place it in the host operating system.
- Using VMware
vSphere client or VMware workstation player, create a new virtual
machine with custom configurations (RAM, CPU, network, and so on).
Provide the path of the downloaded vmdk image in the Virtual Disk
section.
Note: The following settings have been tested by Juniper Networks:
- Network Connection—Bridged Networking
- I/O Controller Type—LSI Logic
- Virtual Disk Type—SCSI
- OS—CentOS (64-bit)
- Power on the virtual machine to start the SRC software.
- After the virtual machine boots, set up the initial configuration.
For information about the initial configuration, see your C Series Controller Hardware Guide.
Note: You cannot create snapshot or restore snapshot with custom partition scheme. We recommend you to use the Snapshot option in the VMware Workstation Pro or VMware ESXi to maintain snapshots of disk image.
The virtual machine gets paused while creating snapshots. We recommend you to disable the Juniper Networks database (jdb component) and components involved in service activities during snapshot creation.
