NetApp Cluster mode ADP disk assignment.
storage disk show -container-type spare
storage disk show -partition-ownership
cn1234::> storage disk assign -owner cn1234-01 -disk 0b.00.9
cn1234::>
cn1234::> system node run -node cn1234-01
cn1234-01>
cn1234-01> disk assign 0b.00.9P1
cn1234-01> disk assign 0b.00.9P2
cn1234::> system node run -node cnaxvp3401-02
cn1234-02> disk assign 0b.00.14P1
cn1234-02> disk assign 0b.00.14P2
from console.
cnaabcd1::> system node environment sensors show -name "Bat Present"|"Bat Volt"
Node Sensor State Value/Units Crit-Low Warn-Low Warn-Hi Crit-Hi
---- --------------------- ------ ----------- -------- -------- ------- -------
cnaabcd-01
Bat Present normal
PRESENT
Bat Volt normal
8100 mV 5500 5600 8500 8600
cnaabcd-02
Bat Present normal
PRESENT
Bat Volt normal
8100 mV 5500 5600 8500 8600
4 entries were displayed.
from SP mode :
system battery show.
VMAX Lun migrate from one pool to another pool
symmigrate -sid 123 -name migration4 -f tdev3 -tgt_pool -pool F15_R5_01_1B validate -nop
symmigrate -sid 123 -name migration4 -f tdev3 -tgt_pool -pool F15_R5_01_1B establish -v
symmigrate -sid 123 -name migration4 query
symmigrate -sid 123 -name migration4 terminate
tdev2 and tdev4 is file where i have to save ldev which need to migrate.
symmigrate -sid 123 -name migration5 -f tdev4 -tgt_pool -pool F15_R5_01_1B validate -nop
symmigrate -sid 123 -name migration5 -f tdev4 -tgt_pool -pool F15_R5_01_1B establish -v
symmigrate -sid 123 -name migration5 query
symmigrate -sid 123 -name migration5 terminate
#*************************************************************************************************************
# Script Name : VMPoweredOff30DaysAgo.ps1
# Purpose : Get the report of VMS Powered Off 30 Days ago
#
#*************************************************************************************************************
#
#If(!(Get-PSSnapin | Where {$_.Name -Eq "VMware.VimAutomation.Core"}))
#{
#Add-PSSnapin VMware.VimAutomation.Core
#}
$VCServer = Read-Host 'Enter VC Server name'
$vcUSERNAME = Read-Host 'Enter user name'
$vcPassword = Read-Host 'Enter password' -AsSecureString
$vccredential = New-Object System.Management.Automation.PSCredential ($vcusername, $vcPassword)
$LogFile = "VMPoweredOff_" + (Get-Date -UFormat "%d-%b-%Y-%H-%M") + ".csv"
Write-Host "Connecting to $VCServer..." -Foregroundcolor "Yellow" -NoNewLine
$connection = Connect-VIServer -Server $VCServer -Cred $vccredential -ErrorAction SilentlyContinue -WarningAction 0 | Out-Null
$Global:Report = @()
If($? -Eq $True)
{
Write-Host "Connected" -Foregroundcolor "Green"
$PoweredOffAge = (Get-Date).AddDays(-30)
$Output = @{}
$PoweredOffvms = Get-VM | where {$_.PowerState -eq "PoweredOff"}
$EventsLog = Get-VIEvent -Entity $PoweredOffvms -Finish $PoweredOffAge -MaxSamples ([int]::MaxValue) | where{$_.FullFormattedMessage -like "*is powered off"}
If($EventsLog)
{
$EventsLog | %{ if($Output[$_.Vm.Name] -lt $_.CreatedTime)
{
$Output[$_.Vm.Name] = $_.CreatedTime
}
}
}
$Result = $Output.getEnumerator() | select @{N="VM";E={$_.Key}},@{N="Powered Off Date";E={$_.Value}}
If($Result)
{
$Result | Export-Csv -NoTypeInformation $LogFile
}
Else
{
"NO VM's Powered off last 30 Days"
}
}
Else
{
Write-Host "Error in Connecting to $VIServer; Try Again with correct user name & password!" -Foregroundcolor "Red"
}
If($? -Eq $True)
{
#write-output $Output
$confirmation = Read-Host 'Check VM list csv file and confirm to Delete Vm Deletion-Yes/No'
if ($confirmation -eq "Yes"){
$vmlist = Get-Content -Path "C:\RY\ansible lab\Powershell_lab\vmdelete30days.txt"
Remove-VM -VM $vmlist -DeletePermanently -Confirm:$True
}
}
#Disconnect-VIServer * -Confirm:$false
#
#
Follow the below mentioned steps to configure Dynamic inventory update on Ansible Tower.
Selecting this credential type enables synchronization of inventory with VMware vCenter.
The automation controller uses the following environment variables for VMware vCenter credentials and are fields prompted in the user interface:
VMware credentials have the following inputs that are required:
vCenter Host: The vCenter hostname or IP address to connect to.
Username: The username to use to connect to vCenter.
Password: The password to use to connect to vCenter.
To configure a VMWare-sourced inventory, select VMware vCenter from the Source field.
The Create Source window expands with the required Credential field. Choose from an existing VMware Credential. For more information, refer to Credentials.
You can optionally specify the verbosity, host filter, enabled variable/value, and update options as described in the main procedure for adding a source.
Use the Source Variables field to override variables used by the vmware_inventory inventory plugin. Enter variables using either JSON or YAML syntax. Use the radio button to toggle between the two. For a detailed description of these variables, view the vmware_inventory inventory plugin.
Starting with Ansible 2.9, VMWare properties have changed from lower case to camelCase. The controller provides aliases for the top-level keys, but lower case keys in nested properties have been discontinued. For a list of valid and supported properties starting with Ansible 2.9, refer to virtual machine attributes in the VMware dynamic inventory plugin.
below is github link for the same.
https://github.com/area51coder/ansible_group_issues
---
hosts: localhost
gather_facts: no
tasks:
- name: collect VMs in specific folder
vmware_vm_facts:
validate_certs: False
hostname: "{{ vcenter_hostname }}"
username: "{{ vcenter_username }}"
password: "{{ vcenter_passwd }}"
# folder: "{{ vcenter_folder }}"
delegate_to: localhost
register: vm_info
- name: print VM info
debug:
msg: "{{ item['guest_name'] }}"
with_items: "{{ vm_info.virtual_machines }}"
- name: Show virtual machines guest_name in job log
ansible.builtin.debug:
msg: "{{ item['guest_name'] }}"
with_items: "{{ vm_info.virtual_machines }}"
- name: Print virtual machines guest_name in output file
ansible.builtin.copy: # should really use template here
content: |
Virtual Machine Names
{% for vm in vm_info.virtual_machines %}
- {{ vm['guest_name'] }}
{% endfor %}
dest: /etc/ansible/reports/virtual_machine_names.txt
NetApp
SnapMirror Synchronous and Asynchronous
When the replication is synchronous, the source host sends a
write request to the source storage system, which is the source of the
replication. Then, the source storage system sends a replication request, and
it also sends the write to the destination storage system.
The target destination storage sends an acknowledgement back
to the source storage, and the source storage sends the acknowledgement back to
the client. With synchronous replication, the data is written to the source and
target storages before an acknowledgement is sent back to the client.
Therefore, you can't have too much delay in the data being written to both
locations.
When you use asynchronous replication, the source host sends
in a write request to its source storage system, and the source storage system
immediately returns an acknowledgement to the client.
Then, based on a predetermined schedule that you decide, for
example, once every 10 minutes, the source sends all of the data written to it
in the previous 10 minutes to the target storage. The target storage then sends
an acknowledgement back to the source storage system.
The asynchronous replication breaks it down into two
separate operations. With synchronous, the write goes to both the source and
the target storage before the acknowledgement returns. With asynchronous
replication, the write comes into the source storage and immediately sends the
acknowledgement back to the client.
Later on, on the schedule in a separate operation, all of
the writes will be written to the target storage, and the target storage will
return an acknowledgement.
With asynchronous replication, the source storage sends an
acknowledgement immediately back to the client host system, so there's no time
and distance limitation. The application will not time out in the source
because the acknowledgement is sent back immediately.
NetApp Cluster Mode.
What are lifs and types of lifs :
NetApp Logical Interfaces are where our IP addresses (or
WWPNs for Fibre Channel and FCoE) live in NetApp ONTAP systems. Having the
IP address applied at the Logical Interface level gives us more
flexibility than would be possible if it was applied to a physical port. It
allows for the use of Interface
Groups and VLANs, and for IP addresses to migrate between different physical
ports in case of failure or maintenance.
Multiple LIF's can be placed on the same port, interface
group, or VLAN. LIF's can move to other nodes non-disruptively. We can migrate
a LIF to another port as an administrator or it could move to a different port
because of a failure.
Each individual LIF is owned by and dedicated to a single SVM
There are a few different types of NetApp Logical
Interfaces:
Node Management LIF - Each node has one LIF which an
administrator can connect to for node management. The LIF never leaves
that node.
Cluster Management LIF - Each cluster also has a LIF which
an administrator can connect to manage the entire cluster. The cluster
management LIF can move between different nodes.
Cluster LIF - Two or more cluster LIF's exist per node,
they are homed on the cluster interconnect physical ports. This is used for
traffic between nodes in the cluster.
Data LIF - Our data LIF's serve client access over our
NAS and SAN protocols.
Intercluster LIF - for SnapMirror and/or SnapVault
replication we have inter-cluster LIF's which must be created on each node.
How to run Ansible playbook on vmware vcenter
So we have below mentioned vcenter ip
192.168.29.195
first we will create host Inventory for vecenter ip on Ansible
Tower as per below mentioned snapshot.
Now we will create a project
to collect inventory report of vcenter
I already have playbook ready
and saved in server path :
Credential I have mentioned
in playbook itself., you can add it in survey also. Or use secret.yml file.
/var/lib/awx/projects/vcenter
Now we will create a template
to execute job, and will selecte the below mentioned yml file from tower to
execute.
You can also use below github
link to use playbook.
https://github.com/area51coder/vmwareinventory
reports will get generate and
save on given location in playbook in html format.
In an
environment with a vCenter Server Appliance (VCSA) 6.5.x, 6.7.x or vCenter
Server 7.0.x, you experience these symptoms:
·
The vmware-vpxd service fails to start.
·
Logging in to
the vSphere Client fails with the error:
HTTP Status 400 – Bad Request Message BadRequest,
Signing certificate is not valid
To
resolve the Signing certificate is not valid error:
1.
Download the
attached fixsts.sh script from this
article and upload to the impacted PSC or vCenter Server with Embedded PSC
to the /tmp folder.
2.
If the
connection to upload to the vCenter by the SCP client is rejected, run this
from an SSH session to the vCenter:
# chsh -s /bin/bash
3.
Connect to the
PSC or vCenter Server with an SSH session if you have not already per Step 2.
4.
Navigate to
the /tmp directory:
# cd /tmp
5.
make the
file executable:
# chmod +x fixsts.sh
6.
Run the
script:
# ./fixsts.sh
7.
Restart
services on all vCenters and/or PSCs in your SSO domain by using below
commands:
8.
# service-control --stop --all &&
service-control --start --all
Note: Restart of services will fail if there are other expired
certificates like Machine SSL or Solution User. Proceed with the next step to
identify and replace expired certificates.
The
following one-liner can determine other expired certificates for the vCenter
Server Appliance:
·
for i in $(/usr/lib/vmware-vmafd/bin/vecs-cli store
list); do echo STORE $i; sudo /usr/lib/vmware-vmafd/bin/vecs-cli entry list
--store $i --text | egrep "Alias|Not After"; done
if above does not work.
run below command from vcenter shell mode.
/usr/lib/vmware-vmca/bin/certificate-manager
choose 8 and reset all certificate.
Resetting root password in vCenter Server Appliance 6.5 / 6.7 / 7.x
How to identify disk number or ID in NetApp filer.
Disk Naming
Let's also cover the naming convention for our disks. The
controllers will be reading and writing data to those individual disks, so it
needs a way to identify them individually. The naming convention is:
stack_id.shelf_id.bay_number
For example, this was in stack ID 1, the shelf ID is
0, and the bay here is 23. When we're in the system manager or the command line
viewing information there and see information about that disk, that disk would
be identified as 1.0.23. Obviously, the bay next door would be 1.0.22.
Unfortunately it depends on your Data ONTAP version. With
Data ONTAP 8.2.x (and earlier) drive names have different formats, depending on
the connection type (FC-AL / SAS). Each drive has a universal unique identifier
(UUID) that is a unique number from all other drives in your cluster.
Each disk is named wit their node name at the beginning. For
example node1:0b.1.20 (node1 – nodename, 0 –
slot, b – port, 1 – shelfID, 20 –
bay).
In other words for SAS drives the name
convention is <node>:<slot><port>.<shelfID>.<bay>
For SAS in multi-disk shelf the name
convention is: <node>:<slot><port>.<shelfID>.<bay>L<position> –
<position> is either 1, or 2 – in this shelf type two disks are inside a
single bay.
For FC-AL name convention is: <node>:<slot><port>.<loopID>
First we will install NetApp
Simulator for our lab, as I dont want you to perform tasks on production if you
are new Storage Team.
use below link to download
simulator. :
there are many type of file for
simulator like, you can install ova on vmware workstation or vmware ESX.
I am using vmware ESX file
here.
https://mysupport.netapp.com/site/tools/tool-eula/simulate-ontap/download
Download ova file, guide pdf, and
license files.
Login to your esx server, select
Deploy OVF Template
follow the guid or below steps to complete the installation. Thanks.
You can display information about the routing configuration for each SVM on your cluster. This can help you diagnose routing problems involving connectivity issues between client applications or services and a LIF on a node in the cluster.
Symptoms
How to Interpret the Brocade porterrshow output
What do the porterrshow counters mean?
Interprets and explains the porterrshow output (port errors) of Brocade SAN switches and possible causes of the errors.
For action to be taken when counters increase see the copy of the KB article
Connectrix: How to troubleshoot Fibre Channel node to switch port or SFP communication problems by means of elimination?
below in the notes section of this KB.
/fabos/cliexec/porterrshow:
frames enc crc crc too too bad enc disc link loss loss frjt fbsy c3timeout pcs uncor
tx rx in err g_eof shrt long eof out c3 fail sync sig tx rx err err
0: 575.2m 2.1g 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0
1: 576.7m 2.1g 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0
2: 611.3m 2.1g 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0
3: 613.6m 2.1g 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0
This command displays an error summary for all ports.
One output line is displayed per port, and shows error counters in ones, thousands (the number is followed by k), or millions (the number is followed by m)..
Cause
NA
Resolution
frames tx
Frames transmitted: The number of frames transmitted by the port. This number is a statistic that provides a baseline for the error counters.
frames rx
Frames received: The number of frames transmitted by the port. This number is a statistic that provides a baseline for the error counters.
enc in
Encoding errors inside frames: (RX). The number of 8b/10b encoding errors that have occurred inside frame boundaries. This counter is generally a zero value, although occasional errors may occur on a normal link and give a nonzero result. Minimum compliance with the link-bit error rate specification on a link continuously receiving frames would allow approximately one error every 20 minutes for 1 Gb/s. Reinitialization and reboots of associated Nx-port can also cause these errors. These errors are in the sum for the LLI errors.
crc err
Frames with Cyclic Redundancy Check errors: (RX) The number of frames that have failed a Cyclic Redundancy Check. The Cyclic Redundancy Check (CRC) is a four-byte field that shall immediately follow the Data Field and shall be used to verify the data integrity of the frame header and Data Field. SOF (= Start-Of-Frame) and EOF (= End-Of-Frame) delimiters shall not be included in the CRC verification. The CRC field shall be calculated on the Frame header and Data Field prior to encoding for transmission and after decoding upon reception. The CRC field shall be aligned on a word boundary. For the purpose of CRC computation, the bit of the word-aligned four-byte field that corresponds to the first bit transmitted is the highest order bit. Frames that fail a CRC are noted but not modified and the destination device is responsible for rejecting and/or re-requesting the frame. Statistically, enc out errors alone imply cable problems, the enc out and crc err in combination implies GBIC/SFP problems. These errors are in the sum for the LLI errors
crc g_eof
CRC with good EOF (End Of Frame) recieved. (Rx). When a CRC with a good EOF is detected the switch will increment the crc g_eof counter, it will tag the frame so no other port will count this CRC frame and forward the frame on.
This allows CRC frame with good EOF to be quickly traced to the originating port.
too short
The "too short" counter is an error statistics counter which is incremented whenever a frame, bounded by an SOF (Start of Frame) and EOF (End of Frame), is received and the number of words between the SOF and EOF is less than 7 words (6 words header plus 1 word CRC), i.e., 38 bytes (not 48) including the SOF and EOF. This could be caused by the transmitter, or an unreliable link. Data frame size is a variable from 0 to 2112. These errors are in the sum for the LLI errors
too long
Frames longer than maximum: The number of frames that are longer than the maximum frame size (36 bytes + data frame size). Data frame size is a variable from 0 to 2112. These errors are in the sum for the LLI errors. FC frames are 2148 byes maximum. If an EOF is corrupted or data generation is incorrect a too long error is generated.
bad eof
Frames with bad end-of-frame delimiters: The end-of-frame (EOF) delimiter is an ordered set that immediately follows the CRC. After a loss-of-synchronization error continuous-mode alignment allows the receiver to reestablish word alignment at any point in the incoming bit stream while the receiver is Operational. Such realignment is likely (but not guaranteed) to result in Code Violations and subsequent loss of Synchronization. Under certain conditions, it may be possible to realign an incoming bit stream without loss of Synchronization. If such a realignment occurs within a received frame, detection of the resulting error condition is dependent upon higher-level function (e.g., invalid CRC, missing EOF Delimiter).
The EOF delimiter shall designate the end of the frame content and shall be followed by idles. There are three categories of EOF delimiters. One category of delimiter shall indicate that the frame is valid from the senders perspective and potentially valid from the receivers perspective. The second category shall indicate that the frame content is valid. This category shall only be used by an F-Port which receives a complete frame and decodes it before forwarding that frame on to another destination. The third category shall indicate the frame content is corrupted and the frame was truncated during transmission. The third category shall be used by both N-Ports and F-Ports to indicate an internal malfunction, such as a transmitter failure, which does not allow the entire frame to be transmitted normally. These errors are in the sum for the LLI errors.
enc out
8bit/10bit encoding errors occurred in words (ordered sets) outside the FC frame. Words outside of frames are encoded, if this encoding is corrupted or an error is detected enc out is generated.
Encoding error outside of frames: The number of 8b/10b encoding errors that have occurred outside frames boundaries. This counter may become a nonzero value during link initialization but indicates a problem if it increments faster than the link-bit error rate allows (approximately once every 20 minutes for 1 Gb/s). This is usually caused by corrupted primitive sequences, that is: LIP f7,f7.
NOTE: loss sig, loss sync and enc out errors are expected every time a user brings the port down and up by rebooting a host, power cycles a storage sub-system, disconnects/reconnects a cable or invoke the portDisable/portEnable command. Also important is the fact, that these errors are also increasing, while a 2GBit switch negotiates the connection speed to its connected device - keep this in mind. Statistically, enc out errors alone imply cable problems, the enc out and crc err in combination implies SFP problems. These errors are in the sum for the LLI errors.
disc c3
Number of Class 3 discared frames (Rx). Counter includes the sum of the following C3 discard counters reported by portstatshow command:
er_rx_c3_timeout, er_tx_c2_timeout, er_c2_dest_unreach, and er_other_disc
Discard class 3 errors could be generated by switch when devices send frames without FLOGI'ing first or with an invalid destination. This error is just reporting that such a discard occurred.
Class 3 frames can be discarded due to timeouts or invalid or unreachable destinations. This counter increment during normal operation. It can also be used to show the effect of port congestion, means good frames from consecutive S-ID's and D-ID's not being directly routed port to port, but instead an exception frame is routed through the internal port (that normally should not happen with a port to port routing on the ASIC, but it does when the D-ID port suffers a buffer full condition and cannot accept any more frames). Also, if the destination is blocked due to high ISL workload (means that is: a long time with BB Credit Buffer = 0), that can cause buffer full conditions, therefore the S-ID port may (in extreme circumstances) meet a timeout condition and therefore the disc c3 counter will increase. These errors are in the sum for the LLI errors.
Some further information: A port can only receive one frame at a time (outside of xWDM connections it is not possible to shine 2 light pulses down an optical cable at the same time). Therefore if two light sources try to share a port they have to use an arbitration algorithm where one light source goes through and the second waits for it is turn. When the first source has completed, the second source is allowed to go. This means that the sources can only run at 50% utilization (or equal busy and ready times). If the source is capable of streaming data at the speed of the D-ID (which a lot of HBA's are these days) any attempt by another similarly fast HBA will result in a 50% performance decrease.
er_unreachable are discards logged because the destination could not be reached or due to offline/online of devices on the destination.
er_other_disc are actual discards which do not fall into either of the other defined discard frame categories. According Brocade they are insignificant and have no impact on performance.
link fail
Link failures (LF1 or LF2 states): The number of times the port achieved Link fail1 and/or Link fail 2 states. Received (Rx). If a Port remains in the LR Receive State for a period of time greater than a timeout period (R_T_TOV), a Link Reset Protocol Timeout shall be detected which results in a Link Failure condition (enter the NOS Transmit State).
The link failure also indicates that loss of signal or loss of sync lasting longer than the R_T_TOV value was detected while not in the Offline state
loss sync
Loss of synchronization: The number of times synchronization was lost. Synchronization failures on either bit or Transmission-Word boundaries are not separately identifiable and cause loss-of synchronization errors.
Note: "loss sig", "loss sync" and "enc out" errors are expected every time a user brings the port down and up (by rebooting a host, power cycles a storage sub-system, disconnects/reconnects a cable or invoke the portDisable/portEnable command (loss sig = Loss of signal: The number of times the signal was lost. When a loss-of-signal condition is recognized by an operational receiver, the Loss-Of-Synchronization state shall be entered (if the receiver is not presently in that state). The receiver shall remain in this state until one of the following conditions occur: The loss-of-signal condition is corrected and synchronization is regained - or - the receiver is reset.
Note: "loss sig", "loss sync" and "enc out" errors are expected every time a user brings the port down and up (by rebooting a host, power cycles a storage sub-system, disconnects/reconnects a cable or invoke the portDisable/portEnable command.
loss sig
Number of times a Loss of Signal was received, occurs when a signal is transmitted but none is being received on the same port.
frjt
Frames rejected with F_RJT: The number of Fabric Port Reject Frames. These indicate that the delivery of a frame is being denied. Some reasons for issuing an F_RJT include: Class not supported; invalid header field(s); and N-Port unavailable.
fbsy
If fabric can't deliver a class 2 frame within E_D_TOV frame will be discarded and a F_BSY returned. (Tx) Frames busied with F_BSY: Fabric Port Busy Frame. This frame is issued by the Fabric to indicate that a particular cannot be delivered because the Fabric or the destination N-Port is busy.
c3-timeout tx
The number of transmit class 3 frames discarded at the transmission port due to timeout (platform- and port-specific).
c3-timeout rx
The number of receive class 3 frames received at this port and discarded at the transmission port due to timeout (platform- and port-specific).
pcs err
The number of Physical Coding Sublayer (PCS) block errors. This counter records encoding violations on 10 Gbps or 16 Gbps ports.
In the porterrshow ER_PCS_BLK counter, this is applicable only on platforms that support 10 Gbps or 16 Gbps ports (6505/6510/6520/DCX-8510) and it was introduced with Condor3 ASIC, the GEN5 Platform. This counter is equivalent with enc_out for 8Gb/4Gb link and it's used only for 10GB and 16Gb speed.
The 10Gb and 16Gb links use 64B/66B encoding instead of 8B/10B for data transmission and "pcs err" (=er_pcs_blk) counter records encoding violations on 10 Gbps or 16 Gbps ports detected during decoding.
uncor err
The number of uncorrectable forward error corrections (FEC).
Command | Description |
auditCfg | Configures the audit message log. |
auditDump | Displays or clears the audit log. |
errClear | Clears all error log messages for all switch instances on this control processor (CP). |
errDelimiterSet | Sets the error log start and end delimiter for messages pushed to the console. |
errDump | Displays the entire error log, without page breaks. Use the -r option to show the messages in reverse order, from newest to oldest. |
errFilterSet | Sets an error severity filter for the system console. |
errModuleShow | Displays all defined error log modules. |
errShow | Displays the entire error log, with page breaks. Use the -r option to show the messages in reverse order, from newest to oldest. |
pdShow | Displays the contents of the panic dump and core dump files. |
portErrShow | Displays the port error summary. |
portLogClear | Clears the port log. If the port log is disabled, this command enables it. |
portLogDisable | Disables the port log facility. |
portLogDump | Displays the port log, without page breaks. |
portLogDumpPort | Displays the port log of the specified port, without page breaks. |
portLogEnable | Enables the port log facility. |
portLogEventShow | Displays which port log events are currently being reported. |
portLoginShow | Displays port logins. |
portLogPdisc | Sets or clears the debug pdisc_flag. |
portLogReset | Enables the port log facility. |
portLogResize | Resizes the port log to the specified number of entries. |
portLogShow | Displays the port log, with page breaks. |
portLogShowPort | Displays the port log of the specified port, with page breaks. |
portLogTypeDisable | Prevents an event from being reported in the port log. Port log events are described by the portLogEventShow command. |
portLogTypeEnable | Configures an event to be reported in the port log. Port log events are described by the portLogEventShow command. |
rasAdmin | Used to enable or disable logging for selected messages or modules, to change the default severity level for a specified message, to display configured RASLog message settings, and to enable or disable quiet time. |
rasMan | Displays message documentation on the switch. |
setVerbose | Sets the verbose level of a particular module within the Fabric OS. |
Command | Description |
snmpConfig | Manages the SNMP agent configuration. |
supportFfdc | Enables and disables FFDC. |
supportFtp | Sets, clears, or displays support FTP parameters or a time interval to check the FTP server. |
supportSave | Collects RASLog, trace files, and supportShow (active CP only) information for the local CP and then transfers the files to an FTP server. The operation can take several minutes. |
supportShow | Issues a list of diagnostic and error display commands. This output is used by your switch service provider to diagnose and correct problems with the switch. The output from this command is very long. Refer to the following related commands: supportShowCfgShow —Displays the groups of commands enabled for display by the supportShow command. supportShowCfgEnable —Enables a group of commands to be displayed under the supportShow command. supportShowCfgDisable —Disables a group of commands under the supportShow command. |
syslogadmin --set - facility | Changes the syslogd facility. |
syslogadmin --set - ip | Adds an IP address as a recipient of system messages. |
syslogadmin -- remove -ip | Removes an IP address as a recipient of system messages. |
syslogadmin --show - ip | Displays the currently configured IP addresses that are recipients of system messages. |
traceDump | Displays, initiates, or removes a Fabric OS module trace dump. |
