Chatee ahora con Soporte
Chat con el soporte

DR Series Software 4.0 - Command Line Reference Guide

Introduction to the DR Series System Command Line Reference Guide Introducing the DR Series system Managing the DR Series system
Alerts Commands Authenticate Commands Network
Network Command Usage network --show network --delete network --restart network --setdhcp network --setstatic_ip [--bondif <bondN>] [--nwif <ethN>] --ip <IPv4/IPv6 address not already in use> --netmask <netmask> [--gateway <IPv4/IPv6 address>] network --create_bond network --create_eth network --add_member network --setdns [--suffix <dns suffix>] [--primary <IPv4/IPv6 address>] [--secondary <IPv4/IPv6 address>] network --setbonding --bondif <bondN> [--mode <ALB | 802.3ad>] [--mtu <supported MTU range 512 - 9000>] network --update network --factory_reset network --host network --route network --nslookup --destination <ip address | hostname> network --traceroute --destination <ip address | hostname> network --ping --destination <ip address | hostname> [--tries <number>] [--size <number>] [--interface <bondN | ethN>] network --blink network --enable network --disable network --troubleshoot [--links] [--gateway] [--ntp] [--dns] [--active_domain] [--nis] [--clients] [--port_mapper] [--network_config] [--show_active <NFS|CIFS|OST|RDS|NDMP|ISCSI|FC>] [--interface <bondN | ethN>] network --troubleshoot --gateway --interface <bondN | ethN> network --troubleshoot [--show_active <NFS| CIFS|OST|NDMP|ISCSI|RDS>] network --tcpdump [--port <nfs | windows | replication | ost | rds>] [--pkt_size <128 - 32768>] [--file_size <0 - 100>] [--stop] [--host <ip address list>] [--interface <bondN | ethN>] network --tcpdump [--pkt_size <128 - 32768>] network --tcpdump [--file_size <0 - 100>] network --tcpdump [--host <ip address list>] network --tcpdump [--port <nfs | windows | replication | ost | rds>] network --iperf_client --server <ip address | hostname> [--port <number>] [--window_size <num bytes [KB/MB]>] [--interval <num seconds>] [--time <num seconds>] network --iperf_server [--port <number>] [--window_size <num bytes [KB/MB>] network --help
OST RDA Stats Storage Group commands System
System Command Usage system --show [--config] system --show [--hardware] system --show [--storage] [--type <boot | internal | external>] [--service_tag <service tag>] system --show [--storage] system --show [--license] [--verbose] system --show [--ntp] system --show [--version] system --show [--timezones [Region]] system --show [--upgradefile] system --show [--upgradehistory] system --show [--marker] system --show [--replication_traffic] system --show [--opdup_traffic] system --show [--backup_traffic] system --show [--mgmt_traffic] system --init system --init --secure_erase <1–pass/3-passes/7-passes> system --reboot system --shutdown system --upgrade system --license [--validate] [--add] system --setname --name <node_name> system --setdate [--date <date>] [--timezone <Region/Zone>] system --setntp [--add <server name>] system --setntp [--delete <server name>] system --setntp [--enable] system --setntp [--disable] system --setntp [--adjust_time] system --setlogin system --telnet [--enable | --disable] system --datacheck --enable system --datacheck --disable system --datacheck --throttle system --marker [--enable] [--disable] system --verify_on_read [--enable] [--disable] system --add_storage --enclosure <service tag> system --storage [--set_usage_alert <70% - 90%>] system --storage [--blink] [--type <internal | external>] [--service_tag <service tag>] [--disk <slot num>] system --storage [--unblink] [--type <internal | external>] [--service_tag <service tag>] [--disk <slot num> system --mgmt_traffic system --backup_traffic system --replication_traffic system --opdup_traffic system --support_agent --register system --support_agent --unregister system --support_agent --stats system --support_agent --status system --help
User Virtual Machine
Maintaining the DR Series System
Diagnostics Maintenance
Maintenance Command Usage maintenance --filesystem [--start_scan [verify_data | verify_rda_metadata | verify_metadata] [--storage_group <name>] maintenance --filesystem [--stop_scan] maintenance --filesystem [--scan_status] maintenance --filesystem [--scan_report [verbose]] maintenance --filesystem [--repair_status [verbose]] maintenance --filesystem [--repair_history [verbose]] maintenance --filesystem [--scan_restart [verify_data | verify_rda_metadata | verify_metadata]] maintenance --filesystem [--repair_now] maintenance --filesystem [--reclaim_space] maintenance --filesystem [--stop_reclaim_space] maintenance --filesystem [--clear_quarantine] maintenance --filesystem --show_throughput maintenance --configuration [--backup] maintenance --configuration [--restore] maintenance --configuration [--reinit_dictionary] maintenance --configuration [--reset_web_certificate] maintenance --hardware [--reinit_nvram] maintenance --hardware [--restore_hw_db] maintenance --hardware [--motherboard_replaced] maintenance --disk [--make_standby [slot num]] [--type <internal | external-<num> | service tag>] --clear_foreign] maintenance --remote_access [--show] maintenance --remote_access [--enable] maintenance --remote_access [--racreset] maintenance --remote_access [--static_ip] [--ip <IPv4/IPv6 address>] [--netmask <netmask>] [--gateway <IPv4/IPv6 address>] [--device <lom1|lom2|lom3|lom4>] maintenance --remote access [--disable] maintenance --vdisk --check_consistency --type <boot|internal|external> [--service_tag <service tag>] maintenance --help
Managing DR Series System Storage Operations
System Storage Operation Commands Connection Container VTL NDMP iSCSI FC Replication Seed Schedule
Data Integrity Checking Additional Linux Commands

network --setbonding --bondif <bondN> [--mode <ALB | 802.3ad>] [--mtu <supported MTU range 512 - 9000>]

Syntax

network --bondif bond1 --setbonding --mode ALB --mtu 1750

Result

Bond device operation successful. Please run 'network --restart' for the changes to take effect.
Note: ALB load balancing does not balance the load properly when the backup servers are on a remote subnet. This is because ALB uses the address resolution protocol (ARP) and ARP updates are subnet-specific. Because of this, ARP broadcasts and updates are not sent across the router. Instead, all traffic is sent to the first interface in the bond. To resolve this ARP-specific issue, make sure that the data source systems reside on the same subnet as the DR Series system.
Note: When setting or changing the MTU value, make sure to verify that the Ethernet network switch is capable of supporting an MTU size that is equal to or larger than the value being set. Any mismatch in MTU values between the clients, the Ethernet network switch, and the DR Series system will make it inoperable. The relationship of jumbo frames to MTU is discussed in this topic.
Note: When using the DR Series system CLI --setbonding and --mtu commands, a warning dialog displays with the following message:
Incorrectly setting the MTU size will cause the DR4000 to not respond. You will 
need to log in to the system console and use the network --setbonding --bondif bond0 --mtu 1500 command 
to resolve the issue. Please verify that the switch is enabled and capable of supporting an MTU size 
that is equal to or larger than the value being set. Do you want to continue (yes/no) ?
CAUTION:
If the existing bonding setting is changed, the connection to the DR Series system may be lost unless you are sure that the DR Series system can accept this bonding type.

In computer networking, jumbo frames are Ethernet frames with more than 1500 bytes of payload (but in some cases, jumbo frames can carry up to 9000 bytes of payload).

Many Gigabit Ethernet switches and Gigabit Ethernet network interface cards support jumbo frames. Some Fast Ethernet switches and Fast Ethernet network interface cards (NICs) also support jumbo frames.

Some computer manufacturers use 9000 bytes as the conventional limit for jumbo frame sizes. Internet Protocol (IP) subnetworks require that all hosts in a subnet have an identical MTU.

Consequently, interfaces that use a standard frame size and those that use a jumbo frame size should not be in the same subnet. To reduce the chance of interoperability issues, NICs capable of jumbo frames require special configurations to use jumbo frames. For more information, contact your Technical Support representative for assistance.

To verify that the destination system can support a specific frame size you want to attempt, use the following DR Series system CLI commands and specify the frame size in bytes using the following command as an example:
network --ping --destination <ip address> --size <number of bytes>

network --update

Syntax

 network --update [--bondif <bondN>]
                 [--nwif <ethN>]
                 [--mode < ALB | 802.3ad>]
                 [--name < DNS name >]
                 [--mtu  <Supported MTU range 512 - 9000>]


        --bondif   Bond interface to update.
        --nwif     Eth interface to update.
        --mode     Bonding mode to use.
        --name     DNS name for the interface.
        --mtu      Ethernet MTU to use (valid range is 512 - 9000).

For example, to update bond1 to use a different MTU parameter, run the command: network --update --bondif bond1 --mtu 5000

Result

WARNING: Incorrectly setting the MTU size will cause the DR appliance to not respond.

Please verify that the switch is enabled and capable of supporting an MTU size that is equal to or larger than the value being set.

Do you want to continue (yes/no) [n]? y

Interface update successful.

network --factory_reset

Syntax

network --factory_reset [--auto_bonding_speed <1G|10G>]

          --auto_bonding_speed    The speed of the device (1G or 10G) 
                                  to bond on restart.

Result

WARNING: This will reset network configuration to factory settings and
will require a system reboot. Existing configuration will be lost.

Do you want to continue (yes/no) [n]?yes
Reboot the system using the command 'system --reboot' to complete the network factory reset.

network --host

Syntax

network --host [--add] [--ip <IPv4/IPv6 address>] [--name <host name>]
               [--delete] [--ip <IPv4/IPv6 address>] [--name <host name>]

        --add      Add local host.
        --delete   Delete local host.
        --ip       Host IP address to manage.
        --name     Host name (FQDN or alias) to manage.
Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación