This one has flummoxed me in the past. The commands you're looking for relate to turning on the 8-Bit character set.
Now, this may still not allow the cellular modem to send the characters via SMS (I do not have a card to test this with), however this is the only command that I know of that may help you out.
Per the Configuring Operating Characteristics for Terminals guide from Cisco (specifically the section on Specifying an International Character Display):
The classic U.S. ASCII character set is limited to 7 bits (128
characters), which adequately represents most displays in the U.S.
Most defaults on the modem router work best on a 7-bit path. However,
international character sets and special symbol display can require an
8-bit wide path and other handling.
You can use a 7-bit character set (such as ASCII), or you can enable a
full 8-bit international character set (such as ISO 8859). This allows
special graphical and international characters for use in banners and
prompts, and adds special characters such as software flow control.
The commands to enable 8 bit character set are:
default-value special-character-bits 8
default-value exec-character-bits 8
To test, I tried to type æ into my lab router with the following results:
R-VOIPLAB#
R-VOIPLAB#>
Since I have the default 7-bit character lengths turned on, it interpreted the æ as angle brackets.
Now, I turned on 8 bit character sets and logged out of my session and back in (the logout is necessary to begin using the new terminal settings we just configured):
R-VOIPLAB#conf t
Enter configuration commands, one per line. End with CNTL/Z.
R-VOIPLAB(config)#default-value exec-character-bits 8
R-VOIPLAB(config)#default-value special-character-bits 8
R-VOIPLAB(config)#exit
R-VOIPLAB#exit
After logging back in:
R-VOIPLAB#
R-VOIPLAB#æ
R-VOIPLAB#æ, ø, å
Notes:
This testing was done with the following configuration, so your milage might vary with a different terminal emulator, different router, etc:
- Test computer: Mac OSX 10.9.2
- Terminal program: SecureCRT for Mac, Version 7.2.0
- Terminal emulation type: VT100
- Connection type: SSH
- Router: 2821
- IOS: 15.1(4)M6
The most common reason I've seen for alloc failures has been serious misconfiguration of the default route -- ip route 0.0.0.0 0.0.0.0 f0/0
will cause this because it's proxy-arp, and the ARP table will grow to an insane size.
A distant second place goes to dynamic routing protocols causing severe memory fragmentation.
We (and TAC) will need a lot more information to debug this. The first place I would suggest looking is the output of show memory failures alloc after failures are happening. (before rebooting)
Note: because memory is relatively cheap (when not bought from Cisco), I tend to load my routers with as much memory as they'll hold.
Best Answer
This can be configured using
VirtualBox
or usingQemu
. These are the steps required to setup JunOS on GNS3 using Qemu:Acquire an image of JUNOS. The image file should be with the extension
.img
Open GNS3 and go to
Edit
->Preferences
->Qemu
Make sure the settings in the
General Settings
section are correct. Below is a screenshot of what the Qemu settings should look like:Click on
Test Settings
to check if your settings are correctClick on the
JunOS
tab on the samePreferences
windowSample Settings for
JunOS
settings section:Click
Save
to save the JunOS image. Close the Preferences window by clickingApply
.Now you are able drag the Juniper Router from the left panel and drop them to the topology.
Note: If you want ta add multiple Juniper routers to your topology, you have to make multiple copies of the image acquired in step 1. Then from the GNS3 program right click on every Juniper router ->
Configure
-> In theJunOS Image:
setting, specify the path of a different image file for each instance.Helpful Links:
NiL - How to run JunOS inside of GNS3
Waleed Khan - JUNOS on GNS3 through Qemu