Year: 2016

So yesterday I’ve been configuring a two-member Virtual Chassis on Juniper EX4600. I’ve been following the guide but the configuration wouldn’t save when issuing commit or commit synchronize commands with the following error:

Member’s information missing from provisioning database

Turns out, when adding members to VC

user@switch# set member 0 serial-number abc123 role routing-engine
user@switch# set member 1 serial-number def456 role routing-engine

serial numbers must be entered with UPPER CASE letters. I wish this was mentioned in the guide or at least the guide didn’t use lowercase letters in the examples. It could’ve saved me a lot of time 🙁

So I needed to upgrade the IOS XE on the customer’s ASR 1002 and after copying the image from USB to Flash, I issued a standard command

boot system flash asr1000rp1-advipservicesk9.03.16.03.S.155-3.S3-ext.bin

After reloading the router I get this error:

boot: unsupported boot device "asr1000rp1-advipservicesk9.03.16.03.S.155-3.S3-ext.bin"
autoboot: boot failed, restarting…

First Google search result showed that I missed ‘bootflash:‘ before the name of the IOS image and the correct command should be

boot system flash bootflash:asr1000rp1-advipservicesk9.03.16.03.S.155-3.S3-ext.bin

Definitely need to remember this!

Finally got my hands on BE6000S. An interesting little machine and worked great for the small project. One thing to keep in mind though, if you decide to change the default IP addresses, it’s better to rebuild the BVI.

BE6000S is a blade server installed in bigger ISR routers.