Class: Ansible::Ruby::Modules::Netapp_e_iscsi_interface

Inherits:
Base show all
Defined in:
lib/ansible/ruby/modules/generated/storage/netapp/netapp_e_iscsi_interface.rb

Overview

Configure settings of an E-Series iSCSI interface

Instance Method Summary collapse

Methods inherited from Base

#ansible_name, #to_h

Methods inherited from Ansible::Ruby::Models::Base

attr_option, attr_options, attribute, fix_inclusion, #initialize, remove_existing_validations, #to_h, validates

Constructor Details

This class inherits a constructor from Ansible::Ruby::Models::Base

Instance Method Details

#address ⇒ String?

Returns The IPv4 address to assign to the interface.,Should be specified in xx.xx.xx.xx form.,Mutually exclusive with I(config_method=dhcp).

Returns:

  • (String, nil) —

    The IPv4 address to assign to the interface.,Should be specified in xx.xx.xx.xx form.,Mutually exclusive with I(config_method=dhcp)



24
 
# File 'lib/ansible/ruby/modules/generated/storage/netapp/netapp_e_iscsi_interface.rb', line 24

attribute :address

#config_method ⇒ :dhcp, ...

Returns The configuration method type to use for this interface.,dhcp is mutually exclusive with I(address), I(subnet_mask), and I(gateway).

Returns:

  • (:dhcp, :static, nil) —

    The configuration method type to use for this interface.,dhcp is mutually exclusive with I(address), I(subnet_mask), and I(gateway).



36
 
# File 'lib/ansible/ruby/modules/generated/storage/netapp/netapp_e_iscsi_interface.rb', line 36

attribute :config_method

#controller ⇒ :A, :B

Returns The controller that owns the port you want to configure.,Controller names are presented alphabetically, with the first controller as A, the second as B, and so on.,Current hardware models have either 1 or 2 available controllers, but that is not a guaranteed hard limitation and could change in the future.

Returns:

  • (:A, :B) —

    The controller that owns the port you want to configure.,Controller names are presented alphabetically, with the first controller as A, the second as B, and so on.,Current hardware models have either 1 or 2 available controllers, but that is not a guaranteed hard limitation and could change in the future.



12
 
# File 'lib/ansible/ruby/modules/generated/storage/netapp/netapp_e_iscsi_interface.rb', line 12

attribute :controller

#gateway ⇒ String?

Returns The IPv4 gateway address to utilize for the interface.,Should be specified in xx.xx.xx.xx form.,Mutually exclusive with I(config_method=dhcp).

Returns:

  • (String, nil) —

    The IPv4 gateway address to utilize for the interface.,Should be specified in xx.xx.xx.xx form.,Mutually exclusive with I(config_method=dhcp)



32
 
# File 'lib/ansible/ruby/modules/generated/storage/netapp/netapp_e_iscsi_interface.rb', line 32

attribute :gateway

#log_path ⇒ Object?

Returns A local path to a file to be used for debug logging.

Returns:

  • (Object, nil) —

    A local path to a file to be used for debug logging



44
 
# File 'lib/ansible/ruby/modules/generated/storage/netapp/netapp_e_iscsi_interface.rb', line 44

attribute :log_path

#mtu ⇒ Integer?

Returns The maximum transmission units (MTU), in bytes.,This allows you to configure a larger value for the MTU, in order to enable jumbo frames (any value > 1500).,Generally, it is necessary to have your host, switches, and other components not only support jumbo frames, but also have it configured properly. Therefore, unless you know what you’re doing, it’s best to leave this at the default.

Returns:

  • (Integer, nil) —

    The maximum transmission units (MTU), in bytes.,This allows you to configure a larger value for the MTU, in order to enable jumbo frames (any value > 1500).,Generally, it is necessary to have your host, switches, and other components not only support jumbo frames, but also have it configured properly. Therefore, unless you know what you’re doing, it’s best to leave this at the default.



40
 
# File 'lib/ansible/ruby/modules/generated/storage/netapp/netapp_e_iscsi_interface.rb', line 40

attribute :mtu

#name ⇒ String

Returns The channel of the port to modify the configuration of.,The list of choices is not necessarily comprehensive. It depends on the number of ports that are available in the system.,The numerical value represents the number of the channel (typically from left to right on the HIC), beginning with a value of 1.

Returns:

  • (String) —

    The channel of the port to modify the configuration of.,The list of choices is not necessarily comprehensive. It depends on the number of ports that are available in the system.,The numerical value represents the number of the channel (typically from left to right on the HIC), beginning with a value of 1.



16
 
# File 'lib/ansible/ruby/modules/generated/storage/netapp/netapp_e_iscsi_interface.rb', line 16

attribute :name

#state ⇒ :enabled, ...

Returns When enabled, the provided configuration will be utilized.,When disabled, the IPv4 configuration will be cleared and IPv4 connectivity disabled.

Returns:

  • (:enabled, :disabled, nil) —

    When enabled, the provided configuration will be utilized.,When disabled, the IPv4 configuration will be cleared and IPv4 connectivity disabled.



20
 
# File 'lib/ansible/ruby/modules/generated/storage/netapp/netapp_e_iscsi_interface.rb', line 20

attribute :state

#subnet_mask ⇒ String?

Returns The subnet mask to utilize for the interface.,Should be specified in xx.xx.xx.xx form.,Mutually exclusive with I(config_method=dhcp).

Returns:

  • (String, nil) —

    The subnet mask to utilize for the interface.,Should be specified in xx.xx.xx.xx form.,Mutually exclusive with I(config_method=dhcp)



28
 
# File 'lib/ansible/ruby/modules/generated/storage/netapp/netapp_e_iscsi_interface.rb', line 28

attribute :subnet_mask