it may or may not boot, or you may discover it only has 4 mb flash and 32 mb ram, which isn't longer supported by openwrt.
even if it boots it'll probably not be 100% functional.
Thanks for the response, the spec sheet suggest it has 4 Gb of NANA and 2GB of ram.
Is there any cisco router equivalent that support openwrt? hopefully the instructions are similar - i'm willing to brick this device if it doesn't work out so i don't mind taking the risks here.
only cisco product afaik are 'meraki' but arguably they don't really qualify...
get serial and knock yourself out... if you are lucky at best you are probably looking at xmodem/kermit/jtagging a custom uboot... and that's just the beginning...
Yeah these devices are part of their Viptela SD-WAN lineup. When they acquired Viptela, they inherited their device lineup but quickly pivoted all development into their ISR series.
So i have this device that is pretty useless for me (requires a paid -expensive - monthly membership fee for the service), so i thought i can try to convert it to my home router using openwrt.
I have console access, I just have no idea where to start.
? - alias for 'help'
askenv - get environment variables from stdin
base - print or set address offset
base64 - print or set address offset
bdinfo - print Board Info structure
bootelf - Boot from an ELF image in memory
bootm - boot application image from memory
bootoct - Boot from an Octeon Executive ELF image in memory
bootoctelf - Boot a generic ELF image in memory. NOTE: This command does not
support simple executive applications, use bootoct for those.
bootoctlinux- Boot from a linux ELF image in memory
bootp - boot image via network using BOOTP/TFTP protocol
bootvx - Boot vxWorks from an ELF image
bunzip - uncompress a bzip2 compressed memory region
cdp - Perform CDP network configuration
cmp - memory compare
cmp64 - memory compare
coninfo - print console devices and information
cp - memory copy
cp64 - memory copy
cpld_rd - cpld_rd 8 bit word from cpld
cpld_wr - cpld_wr 8 bit word from cpld
crc32 - checksum calculation
date - get/set/reset date & time
dhcp - boot image via network using DHCP/TFTP protocol
dns - lookup the IP of a hostname
echo - echo args to console
editenv - edit environment variable
eeprom - EEPROM sub-system
env - environment handling commands
exit - exit script
ext2load - load binary file from a Ext2 filesystem
ext2ls - list files in a directory (default /)
ext4load - load binary file from a Ext4 filesystem
ext4ls - list files in a directory (default /)
false - do nothing, unsuccessfully
fatinfo - print information about filesystem
fatload - load binary file from a dos filesystem
fatls - list files in a directory (default /)
fatwrite - write file into a dos filesystem
fdt - flattened device tree utility commands
flush_dcache- Flushes and invalidates the data cache
flush_l2c - Flushes the L2 cache
freeprint - Print list of free bootmem blocks
go - start application at address 'addr'
gpio - input/set/clear/toggle gpio pins
grepenv - search environment variables
help - print command description/usage
i2c - I2C sub-system
imxtract - extract a part of a multi-image
inv_icache - Invalidates the instruction cache
itest - return true/false on integer compare
loadb - load binary file over serial line (kermit mode)
loads - load S-Record file over serial line
loady - load binary file over serial line (ymodem mode)
loop - infinite loop on address range
loop64 - infinite loop on address range
md - memory display
md5sum - compute MD5 message digest
md64 - memory display
mdio - MDIO utility commands
meminfo - display memory information
mii - MII utility commands
mm - memory modify (auto-incrementing address)
mm64 - memory modify (auto-incrementing address)
mmc - MMC sub system
mmcinfo - display MMC info
mw - memory write (fill)
mw64 - memory write (fill)
namedalloc - Allocate a named bootmem block
namedfree - Free a named bootmem block
namedprint - Print list of named bootmem blocks
nfs - boot image via network using NFS protocol
nm - memory modify (constant address)
nm64 - memory modify (constant address)
octbootbus - print boot bus parameters
octreginfo - print register information
pci - list and access PCI Configuration Space
ping - send ICMP ECHO_REQUEST to network host
printenv - print environment variables
qlm - Octeon QLM debug function (dangerous - remove from final product)
read64 - read 64 bit word from 64 bit address (deprecated)
read64b - read 8 bit word from 64 bit address (deprecated)
read64l - read 32 bit word from 64 bit address (deprecated)
read64s - read 16 bit word from 64 bit address (deprecated)
reset - Perform RESET of the CPU
run - run commands in an environment variable
saveenv - save environment variables to persistent storage
saves - save S-Record file over serial line
setenv - set environment variables
setexpr - set environment variable as the result of eval expression
sf - SPI flash sub-system
sha1sum - compute SHA1 message digest
showvar - print local hushshell variables
sleep - delay execution for some time
source - run script from memory
sspi - SPI utility command
strings - display strings
test - minimal test like /bin/sh
tftp - alias for tftpboot command (deprecated)
tftpboot - boot image via network using TFTP protocol
tftpput - TFTP put command, for uploading files to a server
tftpsrv - act as a TFTP server and boot the first received file
time - run commands and summarize execution time
tlv_eeprom - EEPROM data parsing
true - do nothing, successfully
unlzma - uncompress a lzma compressed memory region
unzip - unzip a memory region
usb - USB sub-system
usbboot - boot from USB device
version - print monitor, compiler and linker version
write64 - write 64 bit word to 64 bit address (deprecated)
write64b - write 8 bit word to 64 bit address (deprecated)
write64l - write 32 bit word to 64 bit address (deprecated)
write64s - write 16 bit word to 64 bit address (deprecated)
Thanks, now this is where I start getting into uncharted territories.
Do i simply go to the latest snapshot, download the Itus img and try t o load it i believe it's here
or do i need to build/compile it myself? (which may be a bit more complicated for me but i can give ite a shot following the development guides).
Alternatively, how can i test it without replacing the current firmware (is there a possibility of dualboot) or how can i save my current firmware if things go awry.
i'm in Montreal Quebec, EST timezone.
Although I can setup the environment, i don't seem to have network connection - the lights don't even turn on leading me to believe that the ports are disabled when i interrupt the bootloader.
I enabled the tftpserver on my host machine, name the file router.bin
on the client (router), I type tftpboot router.bin but i doesn't connect, i tried all the ports.
Ok, i turned off my firewall and tried again, still no go.
it seems to also cycle through the different interfaces so i let it run until it cycled through all of them;
=>tftpboot router.bin
Using octeth2 device
TFTP from server 192.168.1.231; our IP address is 192.168.1.230
Filename 'router.bin'.
Load address: 0x20000000
Loading: T T T T T T T T T T
Retry count exceeded; starting again
Using octeth3 device
TFTP from server 192.168.1.231; our IP address is 192.168.1.230
Filename 'router.bin'.
Load address: 0x20000000
Loading: T T T T T T T T T T
Retry count exceeded; starting again
Using octrgmii0 device
TFTP from server 192.168.1.231; our IP address is 192.168.1.230
Filename 'router.bin'.
Load address: 0x20000000
Loading: T T T T T T T T T T
Retry count exceeded; starting again
Using octeth0 device
TFTP from server 192.168.1.231; our IP address is 192.168.1.230
Filename 'router.bin'.
Load address: 0x20000000
Loading: T T T T T T T T T T
Retry count exceeded; starting again
Using octeth1 device
TFTP from server 192.168.1.231; our IP address is 192.168.1.230
Filename 'router.bin'.
Load address: 0x20000000
Loading: T T T T T T T T T T
I also tried the tftp request from a different machine to ensure the server is working;
c:\>tftp -i 192.168.1.231 get router.bin
Transfer successful: 17948592 bytes in 1 second(s), 17948592 bytes/s
Fire up wireshark or tcpdump, and check if you can see any incoming traffic on the device hosting the TFTPd.
You could also try the tftpsrv command, and send the image from your client.
If it fails, you can still explore the USB commands, nfs and load*.
EDIT: if there's a reset button, you could try using it, and watch the console.
if you're lucky, it'll start some kind of default recovery, whatever it might be.
I have acquired a vEdge 100b and a vEdge 1000. The vEdge 1000 is very interesting as it has a Quad Core CN6130 at 1GHz and 4GB ECC RAM in a SODIMM and 8 SFP ports. I have sent email to external-opensource-requests@cisco.com requesting the appropriate source code. Their Open Source page indicates that source for U-Boot 2013.07 and kernel 3.10.62 are included in the source provided.