Cisco Nexus 7000 Series NX-OS System Management Command Reference
B Commands
Downloads: This chapterpdf (PDF - 214.0KB) The complete bookPDF (PDF - 12.71MB) | Feedback

B Commands

Table Of Contents

B Commands

blink

bloggerd log-dump

bloggerd log-transfer

bloggerd parse log-buffer


B Commands


This chapter describes the Cisco NX-OS system management commands that begin with the letter B.

blink

To blink the LED on the system, use the blink command. To restore the default LED state, use the no form of this command.


Note Beginning with Cisco NX-OS Release 4.1(2), the blink command is not available in Cisco NX-OS software. Use the locator-led command for this function.


blink {chassis | fan f-number | module slot | powersupply ps-number | xbar x-number}

no blink {chassis | fan f-number | module slot | powersupply ps-number | xbar x-number}

Syntax Description

chassis

Blinks the chassis LED.

fan f-number

Blinks the LED that represents the configured fan number. The range depends on the platform. Use ? to see the range.

module slot

Blinks the module LED. The range depends on the platform. Use ? to see the range.

powersupply ps-number

Blinks the power supply LED. The range depends on the platform. Use ? to see the range.

xbar x-number

Blinks the xbar module LED. The range depends on the platform. Use ? to see the range.


Defaults

None

Command Modes

Any command mode

Supported User Roles

network-admin
network-operator
vdc-admin
vdc-operator

Command History

Release
Modification

4.0(1)

This command was introduced.


Usage Guidelines

Use the blink command to flash the LED on a component in the system. You can use this blinking LED to identify the component to an administrator in the data center.

This command does not require a license.

Examples

This example blinks the LED for module 4:

switch# blink module 4
 
   

Related Commands

Command
Description

show locator-led status

Displays the status of locator LEDs on the system.


bloggerd log-dump

To enable threshold-based log dumps on a per application, per virtual device context (VDC), per module, or on a switch-wide basis, use the bloggerd log-dump command. To disable threshold-based log dumps, use the no form of this command.

bloggerd log-dump {all | module module-number sap sap-number [vdc vdc-number | vdc-all] | sap sap-number [vdc vdc-number | vdc-all]}

no bloggerd log-dump {all | module module-number sap sap-number [vdc vdc-number | vdc-all] | sap sap-number [vdc vdc-number | vdc-all]}

Syntax Description

all

Enables a log dump for all services across all modules on the device.

module module-number

Enables a log dump for the specific module. The range for the module number argument is from1 to 18.

sap sap-number

Enables a log dump for a specific Service Access Point (SAP). The range for the sap-number argument is from 0 to 65536. A value of 0 enables a log dump of all SAPs.

vdc vdc-number

(Optional) Enables a log dump for the specific VDC. The range for the vdc-number argument is from 1 to 5.

vdc-all

(Optional) Enables a log dump for the SAP on all VDCs on the device.


Defaults

A threshold-based log dump is enabled for the default VDC.

Command Modes

Any command mode

Supported User Roles

network-admin
network-operator
vdc-admin
vdc-operator

Command History

Release
Modification

6.2(2)

This command was introduced.


Usage Guidelines

You can use the bloggerd log-dump command to prevent application logs from rolling over and becoming lost. You can enable threshold-based log dumps on a per application, per VDC, per module, or on a switch-wide basis to ensure that application logs are saved into files just before a rollover.

Once the logs are dumped, you can configure them to be transferred to a more persistent location (either an external log server or to the active supervisor module's logflash device) using the bloggerd log transfer command. All collected logs are in binary format and must be parsed into ASCII format using DeBlogger.


Note We recommend that you use BloggerD only with TAC supervision.


This command does not require a license.

Examples

This example shows how to enable threshold-based log dumps on a device-wide basis:

switch(config)# bloggerd log-dump all
Sending Enable Request to Bloggerd
Bloggerd Log Dump Successfuly enabled
 
   

Related Commands

Command
Description

bloggerd log-transfer

Enables the transfer of application logs.

bloggerd parse log-buffer

Parses the log buffers using DeBlogger.


bloggerd log-transfer

To enable the transfer of application logs to an external log server or a logflash device, use the bloggerd log-transfer command. To disable the transfer of application logs, use the no form of this command.

bloggerd log-transfer {ip-address tftp-path-name | logflash}

no bloggerd log-transfer

Syntax Description

ip-address

IP address of the logging server.

tftp-path-name

Name of the TFTP server path.

logflash

Enables all log files to be transferred to to the active supervisor module's logflash device.


Defaults

None

Command Modes

Global configuration mode (config)

Supported User Roles

network-admin
network-operator
vdc-admin
vdc-operator

Command History

Release
Modification

6.2(2)

This command was introduced.


Usage Guidelines

The bloggerd log-transfer command allows you to configure the transfer of application logs to a more persistent location (either an external log server or to the active supervisor module's logflash device). All collected logs are in binary format and must be parsed into ASCII format using DeBlogger.


Note We recommend that you use BloggerD only with TAC supervision.


This command does not require a license.

Examples

This example shows how to enable a log dump and transfer of log files on the device:

switch(config)# bloggerd log-dump all
Sending Enable Request to Bloggerd
Bloggerd Log Dump Successfuly enabled
switch(config)# bloggerd log-transfer 10.10.10.1 /cisco_blogger/

Related Commands

Command
Description

bloggerd log-dump

Enables threshold-based log dumps.

bloggerd parse log-buffer

Parses the log buffers using DeBlogger.


bloggerd parse log-buffer

To parse the log buffers from binary format to ASCII format using DeBlogger, use the bloggerd parse log-buffer command.

bloggerd parse log-buffer {directory directory-path | file file-name}

Syntax Description

directory directory-path

Specifies the directory path of file to be parsed by DeBlogger.

file file-name

Specifies the filename of file to be parsed by DeBlogger.


Defaults

A threshold-based log dump is enabled for the default VDC.

Command Modes

Global configuration mode (config)

Supported User Roles

network-admin
network-operator
vdc-admin
vdc-operator

Command History

Release
Modification

6.2(2)

This command was introduced.


Usage Guidelines

DeBlogger is an external parsing framework that converts binary data into ASCII format by linking with the necessary application libraries. You can use the bloggerd parse log-buffer command to parse logs from binary to ASCII format.


Note We recommend that you use BloggerD only with TAC supervision.


This command does not require a license.

Examples

This example shows how to parse binary logs to ASCII format on the device:

switch# bloggerd parse log-buffer directory /tmp/blogger/
Parsing file: /tmp/blogger//module-5_vdc-1_spm_binary_sdwrap_app_uuid_404_inst_1
_type_0_06_15_2013_00:42:56
***************************************************************
===========================================================
META DATA:
===========================================================
Log Data Type: SDWRAP_LOG_DATA_TYPE_EVENT_HISTORY
Module Number: 5
VDC ID: 1
APP UUID: 0
Buffer UUID: 404
Buffer Instance: 1
 
   

Related Commands

Command
Description

bloggerd log-dump

Enables threshold-based log dumps.

bloggerd log-transfer

Enables the transfer of application logs.