The Linux live CD or USB stick is not hot news. But, having the full installation running from a USB flash drive that acts like a hard drive is the difference.
You discover that your Junos EX or SRX device does not complete normal boot up. The image seems to be corrupted for some reason, such as a continuous power failure. If this occurs, don’t worry, you can get it back up within few minutes using the USB port. Get a USB flash drive. Copy the Junos image to the USB drive (without creating folders). Use FAT file format if the USB size is less than 2 GB. Use FAT32 if the USB size is greater than or equal to 4 GB.
The example below uses the file image junos-srxsme-10.4R1.9-domestic.tgz. Insert the flash into an EX/SRX USB port. Reboot the device. When Junos boots up, you will see the message: Press Space to abort autoboot Do nothing.
A little while later, you will see: Hit Enter to boot immediately, or space bar for command prompt. Press the space bar. You will be at loader mode; the prompt should be loader. If the prompt is , type boot to make it loader.
Now type the following command: loader install file:/// junos-srxsme-10.4R1.9-domestic. Expect to wait awhile for the code to download. Additionally, after the Junos OS boots, you may see messages relating to file system To upgrade your JUNOS: rootrequest system software add /tmp/usb/junos-jsr-10.0R3.10-export.tgz no-validate no-copy. Mikrotik Router OS CAPsMAN Configuration only bridge mode with external DHCP server and NAT service You can deploy CAPsMAN wireless controller on any Mikrotik RouterOS hardware (for instance Haplite series routers) 1st step is to check our RouterOS image version, it should include wiressless package (check SystemPackages). OS version on CAPsman controller should the same as in Access Point. You can upgrade the version manual.
Go to the SystemPackages, then simply drag and drop your previously downloaded imge. After I would recomend to reboot it from CLI / system reboot and then just run / system routerboard upgrade and again reboot it. Then we can check the version / sys rou print. 2nd step is to create bridge interface which should include our physycal interface or several interfaces, so we create bridging between our physycal interfaces or if it's only one interfaces then it will be put into bridge mode.
Let's check our interfaces: /interface print /interface bridge (this.
Well, it would seem that after a few days of tinkering and googling, my Google-fu FINALLY yielded the winning post. FROM: Re: Talking to RouterBoard via Serial Console won't work by brettg » Mon Jun 17, 2013 10:08 pm Many folks who are trying to connect to a serial terminal / console session may be trying to re-establish administrative control after making a mistake in their firewall rules. This happened to me a few days ago, and I struggled and struggled to get the serial cable/session going. For everyone in that boat, there is an easier answer: 1) Download and unzip 'Neighbour viewer for Windows' free from the Mikrotik web site. 2) Install it on a PC local to the router (not behind another router). 3) Get it to 'discover' your router, then press the button to initiate a terminal session (using its own built-in terminal that connects by MAC address,not by IP) 4) Log-in to the terminal session like you would any other SSH session.
Fix your firewall so that you can again connect by your method of choice. No serial cable required. Edited to Add: This information opened up the router enough to allow a LAN login for configuration via Winbox. #Router and internal network protection, no internal servers, LAN is friendly. Sounds like you may need to ensure your NAT policy's (port forwards) are configured properly. /ip firewall nat add chain=dstnat dst-address= protocol=tcp dst-port=443 action=dst-nat to-addresses= to-ports=443 If you are using the RB1100 as a firewall, make sure you are setting up firewall rules to accept new/established/related connections and deny the rest. This forum can give you some pointers: Use caution not to lock yourself out of the Mikrotik by stacking your rules incorrectly.
Are you sure you are using a null modem cable? Tera Term Settings: Serial Output: - Performing the Power-On Self Test (POST) - UART Channel Loopback Test.PASS Testing the System SDRAM.PASS Boot1 Checksum Test.PASS Boot2 Checksum Test.PASS Flash Image Validation Test.PASS BOOT Software Version 1.0.0.04 Built 08-Sep-2005 16:57:40:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::.:::::::::.::.
![Mikrotik Mikrotik](http://docshare.tips/img/20502/mikrotik-install-mikrotik-di-virtual-machine_5748447bb6d87fd5328b462d.jpg)
Linksys SmartSwitch SRW2048 based on 88E6218 with ARM946E-S. 64MByte SDRAM. I-Cache 8 KB. D-Cache 8 KB. Cache Enabled. Autoboot in 2 seconds - press RETURN or Esc.
To abort and enter prom. Preparing to decompress. 100% Decompressing SW from flash 100% OK Running from RAM. Running SW Ver. 1.2.2d Date 23-Feb-2009 Time 13:58:42.
HW version is 00.03.00 Base Mac address is: 00:1d:7e:84:90:43 Dram size is: 64M bytes Dram first block size is: 46080K bytes Dram first PTR is: 0x1300000 Flash size is: 16M 01-Jan-2000 01:01:07%CDB-I-LOADCONFIG: Loading startup configuration. Device configuration: Prestera based chassis - Linksys Slot 1 - SRW2048 HW Rev. 15.15 Tapi Version: v1.3.3.1 Core Version: v1.3.3.1 01-Jan-2000 01:01:41%INIT-I-InitCompleted: Initialization task is completed.
Well, it would seem that after a few days of tinkering and googling, my Google-fu FINALLY yielded the winning post. FROM: Re: Talking to RouterBoard via Serial Console won't work by brettg » Mon Jun 17, 2013 10:08 pm Many folks who are trying to connect to a serial terminal / console session may be trying to re-establish administrative control after making a mistake in their firewall rules.
This happened to me a few days ago, and I struggled and struggled to get the serial cable/session going. For everyone in that boat, there is an easier answer: 1) Download and unzip 'Neighbour viewer for Windows' free from the Mikrotik web site. 2) Install it on a PC local to the router (not behind another router). 3) Get it to 'discover' your router, then press the button to initiate a terminal session (using its own built-in terminal that connects by MAC address,not by IP) 4) Log-in to the terminal session like you would any other SSH session. Fix your firewall so that you can again connect by your method of choice. No serial cable required. Edited to Add: This information opened up the router enough to allow a LAN login for configuration via Winbox.
#Router and internal network protection, no internal servers, LAN is friendly.