ASAv telnet consol error
Moderator: mike
-
- Posts: 7
- Joined: Mon Mar 20, 2017 12:05 pm
ASAv telnet consol error
I am getting error when i use telnet console for ASAv, but vnc works fine, i used telnet console for ASAv in unetlab. please help me.. telnet session is more flexible than vnc session.
Error info:
loader: Platform type set to default
Platform ASAv
loader: Platform type set to default
IO memory blocks requested from bigphys 32bit: 87680
Error info:
loader: Platform type set to default
Platform ASAv
loader: Platform type set to default
IO memory blocks requested from bigphys 32bit: 87680
-
- Posts: 409
- Joined: Sun Mar 19, 2017 10:27 pm
Re: ASAv telnet consol error
Himithu wrote: ↑Mon Mar 20, 2017 12:19 pmI am getting error when i use telnet console for ASAv, but vnc works fine, i used telnet console for ASAv in unetlab. please help me.. telnet session is more flexible than vnc session.
Error info:
loader: Platform type set to default
Platform ASAv
loader: Platform type set to default
IO memory blocks requested from bigphys 32bit: 87680
Stop the ASAv node, Edit the ASAv node and select console type Telnet, it should work.
R!
-
- Posts: 7
- Joined: Mon Mar 20, 2017 12:05 pm
Re: ASAv telnet consol error
when i select console type Telnet i got error, when i select vnc it works..
Error info:
loader: Platform type set to default
Platform ASAv
loader: Platform type set to default
IO memory blocks requested from bigphys 32bit: 87680
Top
Error info:
loader: Platform type set to default
Platform ASAv
loader: Platform type set to default
IO memory blocks requested from bigphys 32bit: 87680
Top
-
- Posts: 5083
- Joined: Wed Mar 15, 2017 4:44 pm
- Location: London
- Contact:
Re: ASAv telnet consol error
Under our how to section is given how to setup ASAv Telnet console sir. Check in our web site please
-
- Posts: 6
- Joined: Sun Mar 19, 2017 5:17 pm
Re: ASAv telnet consol error
Hi,
I am also having the same issue with the console. I followed the directions as stated in the "How to" section as you can see below. However, when I start a ASAv node and "telnet" into the node I only see the "loader: Platform type set to default" messages. But if I VNC into the ASAv node I see the ASAv has booted. What else am I missing? Thank you
root@eve-ng:/opt/unetlab/addons/qemu/asav-941-200# guestfish -a virtioa.qcow2
Welcome to guestfish, the guest filesystem shell for
editing virtual machine filesystems and disk images.
Type: 'help' for help on commands
'man' to read the manual
'quit' to quit the shell
><fs> run
100% [#############################################################################################] --:--
><fs> mount /dev/sda1 /
><fs> touch /use_ttyS0
><fs> unmount /
><fs> exit
root@eve-ng:/opt/unetlab/addons/qemu/asav-941-200# /opt/unetlab/wrappers/unl_wrapper -a fixpermissions
I am also having the same issue with the console. I followed the directions as stated in the "How to" section as you can see below. However, when I start a ASAv node and "telnet" into the node I only see the "loader: Platform type set to default" messages. But if I VNC into the ASAv node I see the ASAv has booted. What else am I missing? Thank you
root@eve-ng:/opt/unetlab/addons/qemu/asav-941-200# guestfish -a virtioa.qcow2
Welcome to guestfish, the guest filesystem shell for
editing virtual machine filesystems and disk images.
Type: 'help' for help on commands
'man' to read the manual
'quit' to quit the shell
><fs> run
100% [#############################################################################################] --:--
><fs> mount /dev/sda1 /
><fs> touch /use_ttyS0
><fs> unmount /
><fs> exit
root@eve-ng:/opt/unetlab/addons/qemu/asav-941-200# /opt/unetlab/wrappers/unl_wrapper -a fixpermissions
-
- Posts: 5083
- Joined: Wed Mar 15, 2017 4:44 pm
- Location: London
- Contact:
Re: ASAv telnet consol error
Use newer ASAv 971, it has diff hdd setup inside and match aour new HowTo steps
-
- Posts: 7
- Joined: Mon Mar 20, 2017 12:05 pm
Re: ASAv telnet consol error
I use ASAv 951-200.qcow2, telnet works with this image on unetlab, but after upgrade to EVE-ng, we have this issue..
-
- Posts: 5083
- Joined: Wed Mar 15, 2017 4:44 pm
- Location: London
- Contact:
-
- Posts: 2
- Joined: Wed Mar 29, 2017 12:17 pm
Re: ASAv telnet consol error
Assuming that "ASAv 951-200.qcow2" is actually :
asav-951-200.qcow
Make sure there are no spaces in the filename please
Upload the downloaded image to the EVE root directory using for example FileZilla or WinSCP
SSH to the EVE-NG VM using the IP Address (whatever it may be)
Username : root
Password : eve
Create the folder for HDD image and move it:
-------------------------------------------------------------------------------------------
mkdir -p /opt/unetlab/addons/qemu/asav-951-200
mv /asav951-200.qcow2 /opt/unetlab/addons/qemu/asav-951-200/virtioa.qcow2
==================
Install the following
--------------------------
apt-get install libguestfs-tools
*** answer yes
y
======================================================
Run following commands to enable telnet access instead of vnc
--------------------------------------------------------------------------------
cd /opt/unetlab/addons/qemu/asav-951-200/
guestfish -a virtioa.qcow2
run
mount /dev/sda2 /
touch /use_ttyS0
umount /
exit
!
cd\
!
/opt/unetlab/wrappers/unl_wrapper -a fixpermissions
You should now be able to go into the EVE-NG web interface, add the ASAv image and then connect using telnet.
I actually use SecureCRT and have created saved sessions to the VM IP and then to the ports that is generally used, makes it much easier
asav-951-200.qcow
Make sure there are no spaces in the filename please
Upload the downloaded image to the EVE root directory using for example FileZilla or WinSCP
SSH to the EVE-NG VM using the IP Address (whatever it may be)
Username : root
Password : eve
Create the folder for HDD image and move it:
-------------------------------------------------------------------------------------------
mkdir -p /opt/unetlab/addons/qemu/asav-951-200
mv /asav951-200.qcow2 /opt/unetlab/addons/qemu/asav-951-200/virtioa.qcow2
==================
Install the following
--------------------------
apt-get install libguestfs-tools
*** answer yes
y
======================================================
Run following commands to enable telnet access instead of vnc
--------------------------------------------------------------------------------
cd /opt/unetlab/addons/qemu/asav-951-200/
guestfish -a virtioa.qcow2
run
mount /dev/sda2 /
touch /use_ttyS0
umount /
exit
!
cd\
!
/opt/unetlab/wrappers/unl_wrapper -a fixpermissions
You should now be able to go into the EVE-NG web interface, add the ASAv image and then connect using telnet.
I actually use SecureCRT and have created saved sessions to the VM IP and then to the ports that is generally used, makes it much easier
-
- Posts: 5083
- Joined: Wed Mar 15, 2017 4:44 pm
- Location: London
- Contact: