Users Guide
Setting Up F5 BIGIP VNF Package | Configuring Virtualization
826 OMNM 6.5.3 User Guide
3
Run the f5vmconfig.sh script, which logs into the target VM using the F5 vendor’s default ssh
v2 user credentials and applies the following commands to the VM as well as saves the
running configuration to be permanent.
f5vmconfig.sh -i <
Management IP Address
> [-m <
MTU
>]
Where:
• -i is the target F5 BIGIP device management IP address (required)
• -m is the MTU integer value (optional)
The Dorado Software LAN environment requires that MTU value of 1400 be assigned
to the mgmt (eth0) port. Omit or change to a different valid MTU value based upon
your specific network environment requirements.
• -h is the help message
For example:
f5vmconfig.sh -i 10.122.15.44 -m 1400
4
Reboot the VM for the MTU change to take affect by logging into the Linux shell using the
ssh
command and issuing the
reboot
command.
The ssh connectivity is lost, until the VM reboots and completely starts up again.
5
Manually log into the VM using the
ssh
command.
6
Verify that the MTU setting was applied or retained properly:
# ifconfig eth0
config eth0 Link encap:Ethernet HWaddr FA:16:3E:9E:E7:4D
inet addr:172.85.0.5 Bcast:172.85.0.255 Mask:255.255.255.0
inet6 addr: fe80::f816:3eff:fe9e:e74d/64 Scope:Link
UP BROADCAST RUNNING ALLMULTI MULTICAST
MTU:1400
Metric:1
RX packets:817 errors:0 dropped:0 overruns:0 frame:0
TX packets:843 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:167119 (163.2 KiB) TX bytes:148788 (145.3 KiB)
7
Verify that the
mtu
setting of
1400
for the
eth0
interface command was appended to the /
config/startup file by running the following command.
config # cat /config/startup
#
# NOTE:
# This file will be installed in /config/startup and it will
# be called by /etc/rc.local.
#
# - /config/startup is for customer config additions and
# will be saved in UCS and synced by tmsh run sys sync-sys-files
#
# - /etc/rc.local should *not* be used by customers and
# can/will be changed by F5
#
ifconfig eth0 mtu 1400
8
Make sure that the SNMP allowed-addresses tmsh cli setting of
ALL
was persisted after
reboot: