Nimble is the only CRM that creates auto-enriched contact profiles from anywhere on the web. Simply hover over any name and the Nimble Prospector browser extension will deliver actionable contact information, business insights, and interaction history to cut your time spent on data entry in half. Learn how to capture leads in 3 clicks. The serial number is found on the back or bottom of your HPE product, and will be in a format such as USE646N6FJ, 2UA73310K5 or CNU6080B8C.
Since Nimble Storage introduced Fibre Channel, I’m sure that many of our customers and prospects want to use their new FC array.
In this post, I will cover how to setup your new FC array and indicate what has changed in the setup manager as well as in the WebUI of the array.
All Fibre Channel arrays will be shipped with the Nimble OS version 2.2.2.0 as it is the first OS which supports FC.
Once you have unpacked your new array, racked and cabled it, power it on. For the initial setup, you will need the Nimble Setup Manager on your local machine. The Nimble Setup Manager is part of the Nimble Windows Toolkit and can be downloaded from InfoSight. If you do not have an InfoSight login yet, please register as a new user.
Note: You will need your array serial number to register successfully.
After you started the Nimble Setup Manager, it will find your storage array and ask you to accept the EULA.
Next, you will be asked if you want to add this array to an existing group or set it up as a standalone array.
In this setup, we decided to not join an existing group. Specify the array & group name and some additional management settings and hit next.
In the next screen you have to specify your subnet labels. Since this is a Fibre Channel array, you do not need to specify a data subnet. However, we have chosen to create a data subnet dedicated for replication.
Finally, we can see our actual FC ports and as you hover over each single FC port, you can see the operational speed.
By the way, don’t forget to set your diagnostic IPs. Those come in handy if you ever have to engage Support.
The next screen should look familiar again as it is the same for every Nimble Storage array. Specify the domain name and your DNS server.
Also, this screen should look familiar. Nothing has changed here. Specify your time zone and a NTP server.
This is the final step for the initial setup. Make sure to setup an unauthorized SMTP relay on your mail server for your new array.
Also, please check the box for Send event data to Nimble Storage Support. A lot of Nimble’s case automation and pro-active wellness relies on email alerts.
If you think you don’t need email alerts and all this pro-active wellness stuff, watch this video and see what you’ll miss out on. I highly recommend enabling those alerts!
Additionally, make sure Autosupport is enabled and works. Autosupport data is also playing a big role in Nimble’s pro-active wellness & InfoSight.
Once you are done, hit Finish and your array is ready for some action.
Go to Manage -> Arrays and select your array name. It will open this part of the WebUI and you can see your Ethernet and FC ports as well as the usual details.
Heading over to Administration -> Network Configuration. Select the active configuration and select the Interfaces-Tab. Here, you can see all your FC port including their WWPNs and the WWNN.
For the guys new to FC, WWPN = World Wide Port Name & WWNN = World Wide Node Name.
Additional to the new Interfaces-Tab, Nimble Storage also changed the Initiator Group UI in order to accommodate FC Initiators/WWPNs.
All images have been provided by Rich Fenton, one of Nimble’s Sales Engineer from UK.
This tutorial explains how to use the example application blehciincluded in the NimBLE stack to talk to the Mynewt NimBLE controller viathe Host Controller Interface. You may build the Mynewt image using alaptop running any OS of your choice - Mac, Linux, or Windows.
The host used in this specific example is the BlueZ Bluetooth stack.Since BlueZ is a Bluetooth stack for Linux kernel-based family ofoperating system, the tutorial expects a computer running Linux OS andwith BlueZ installed to talk to the board with the Mynewt image.
Ensure that you meet the following prerequisites before continuing withone of the tutorials.
Have Internet connectivity to fetch remote Mynewt components.
Have a board with BLE radio that is supported by Mynewt. We will usean nRF52 Dev board in this tutorial.
Have a USB TTL Serial Cable that supports hardware flow control suchas ones found athttp://www.ftdichip.com/Products/Cables/USBTTLSerial.htm to establisha serial USB connection between the board and the laptop.
Install the newt tool and toolchains (See BasicSetup).
Install a BLE host such as BlueZ on a Linux machine to talk to thenRF52 board running Mynewt. Use
sudoapt-getinstallblueztoinstall it on your Linux machine.
Use the newt tool to create a new project directory containing askeletal Mynewt framework. Change into the newly created directory.
You will create two targets - one for the bootloader, the other for theapplication. Then you will add the definitions for them. Note that youare using the example app blehci for the application target. Set thebsp to nordic_pca10040.
NOTE: The preview version, nRF52PDK, is no longer supported. If youdo not see PCA100040 on the top of your board, you have a previewversion of the board and will need to upgrade your developer boardbefore continuing.
Check that the targets are defined correctly.
Then build the two targets.
Generate a signed application image for the myble2 target. Theversion number is arbitrary.
Make sure the USB connector is in place and the power LED on the boardis lit. Use the Power ON/OFF switch to reset the board after loading theimage.
Load the bootloader:
Load the application image:
Attach a serial port to your board by connecting the USB TTL SerialCable. This should create /dev/ttyUSB0 (or similar) on your machine.
Note Certain Linux OS versions have been observed to detect thenrf52 board as a mass storage device and the console access doesn’t workproperly. In that case try powering the nrf52 board from your monitor orsomething other than your Linux computer/laptop when you set up theserial port for HCI communication.
btmon is a BlueZ test tool to display all HCI commands and events ina human readable format. Start the btmon tool in a terminal window.
In a different terminal, attach the blehci device to the BlueZ daemon(substitute the correct /dev filename for ttyUSB0).
The baud rate used to connect to the controller may be changed byoverriding the default value of 1000000 in thenet/nimble/transport/uart/syscfg.yml. Settings in the serialtransport syscfg.yml file can be overridden by a higher prioritypackage such as the application. So, for example, you may set theBLE_HCI_UART_BAUD to a different value inapps/blehci/syscfg.yml.
If there is no CTS/RTS lines present in the test environment, flowcontrol should be turned off. This can be done with -N option forbtattach. Note: -N option came with BlueZ ver 5.44.Also, modify the value of BLE_HCI_UART_FLOW_CTRL in thenimble/transport/uart/syscfg.yml to HAL_UART_FLOW_CTL_NONE.
In a third terminal, start btmgmt. This tool allows you to send commandsto the blehci controller. Use the index number that shows up when youbtattach in the previous step.
Set your device address (you can substitute any static random addresshere).
Initialize the controller.
Find Nimble Storage Serial Number
Begin scanning.