Configure vJunosEvolved-BX on KVM
Read this topic to understand the connections and configurations of the vJunosEvolved-BX instances deployment on KVM
Connect to vJunosEvolved-BX
Telnet to the serial console number specified in the XML file to connect to vJunosEvolved-BX. See details provided in the example below:
# telnet localhost 8610 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. root@:~ # cli root>
Configure vJunosEvolved-BX Channelization Interfaces
The vJunosEvolved-BX configurations are the same as the hardware configurations in Junos Evolved-BX CLI.
If channelization of WAN interfaces is required, then boot argument “channelized=yes” must be specified in the XML configuration and the interfaces speed should be configured at Junos Evolved-BX CLI. Only 4x100G channelization is supported with total of 144 channelized interfaces.
Sample configuration shown below:
Run the set interfaces et-0/0/0 speed 100g number-of-sub-ports 4 command.
[edit] # set interfaces et-0/0/0 speed 100g number-of-sub-ports 4 > show interfaces terse Interface Admin Link Proto Local Remote et-0/0/0:0 up up et-0/0/0:0. 16386 up up inet multiservice et-0/0/0:1 up up et-0/0/0:1.16386 up up multiservice et-0/0/0:2 up up et-0/0/0:2.16386 up up multiservice et-0/0/0:3 up up et-0/0/0:3.16386 up up multiservice
You can specify the number of sub ports under a WAN interface to channelize. The default number of non-channelized ports is 36 (et-0/0/0 to et-0/0/35), but you can channelize each interface with 4 subports at 100G speed. You must have this Junos Evolved-BX CLI configuration when channelized option is set to "yes" in the XML. Otherwise, traffic won’t pass through. Table to show vBX’s mapping with channelized WAN ports.
WAN Port |
BX0 or BX1 |
Supported Port Speed |
---|---|---|
et-0/0/0:0-3 to et-0/0/8:0-3 |
BX1 |
4x100G |
et-0/0/9:0-3 to et-0/0/26:0-3 |
BX0 |
4x100G |
et-0/0/27:0-3 to et-0/0/35:0-3 |
BX1 |
4x100G |
Configure the vBX Chips
By default, both BX is running, and all the 36 interfaces are visible at show interfaces terse.
If there is a need to power off BX’s then following command is useful.
Chassis Configuration to power off vBX0
[edit]
user@host# set chassis fpc 0 pfe 0 power off
user@host#set chassis fpc 0 pfe 1 power off
user@host# commit
Chassis Configuration to power off vBX1
[edit]
user@host# set chassis fpc 0 pfe 2 power off
user@host##set chassis fpc 0 pfe 3 power off
user@host# commit
Configure the Media MTU
You can configure the media maximum transmission unit (MTU) in the range 288 through 16000. MTU values outside the above mentioned range are rejected.
You must configure the MTU by including the MTU statement at the [edit interface interface-name] hierarchy level.
Configure the MTU.
[edit] user@host# set interface et-0/0/0 mtu <mtu>
The maximum supported MTU value is 16000 bytes.
For example:
[edit] user@host# set interface et-0/0/0 mtu 16000