Library Version 1.10

Library Version 1.06


HP OneView 1.10 Library

NAME

New-HPOVLogicalInterconnectGroup

SYNOPSIS

Create new Logical Interconnect Group.

SYNTAX

New-HPOVLogicalInterconnectGroup -Name <String> -Bays <Hashtable> [-enableIgmpSnooping <Boolean>] [-igmpIdleTimeoutInterval <Int32>] [-enableFastMacCacheFailover <Boolean>] [-macRefreshInterval <Int32>] [-enableNetworkLoopProtection <Boolean>] [-SNMP <Hashtable>] [<CommonParameters>]

New-HPOVLogicalInterconnectGroup [[-Name] <String>] [[-Bays] <Hashtable>] [[-enableIgmpSnooping] <Boolean>] [[-igmpIdleTimeoutInterval] <Int32>] [[-enableFastMacCacheFailover] <Boolean>] [[-macRefreshInterval] <Int32>] [[-enableNetworkLoopProtection] <Boolean>] [[-SNMP] <Hashtable>] -Import <Object> [<CommonParameters>]

DESCRIPTION

This cmdlet provides the ability to create a Logical Interconnect Group. Bays 1 and 2 are required, and need to be identical.

PARAMETERS

-Name [<String>]
Required. The Logical Interconnect Group Name
Aliases None
Required? false
Position? 1
Default value <none>
Accept pipeline input? false
Accept wildcard characters?    false
-Bays [<Hashtable>]
Required. A [System.Collections.Hashtable] value of each Interconnect Bay. Accepted values are:
  • FlexFabric - HP VC FlexFabric 10Gb/24-Port Module
  • Flex10 - HP VC Flex-10 Enet Module
  • Flex1010D - HP VC Flex-10/10D Module
  • Flex2040f8 - HP VC FlexFabric-20/40 F8 Module
  • VCFC20 - HP VC 8Gb 20-Port FC Module
  • VCFC24 - HP VC 8Gb 24-Port FC Module
  • FEX - Cisco Fabric Extender for HP BladeSystem

E.g. @{1 = "Flex10";2 = "Flex10";3 = "FlexFabric";4 = "Flexfabric";5 = "";6 = "";7 = "";8 = "";}

Aliases None
Required? false
Position? 2
Default value <none>
Accept pipeline input? false
Accept wildcard characters?    false
-enableIgmpSnooping [<Boolean>]

Optional. The IGMP snooping feature allows interconnects to monitor the IGMP IP multicast membership activities and configure hardware Layer 2 switching behavior of multicast traffic to optimize network resource usage. Currently, only IGMP v1 and v2 (RFC 2236) are supported.

Default value: Disabled

Aliases None
Required? false
Position? 3
Default value False
Accept pipeline input? false
Accept wildcard characters?    false
-igmpIdleTimeoutInterval [<Int32>]

Optional. The Group Membership Interval value, as specified by the IGMP v2 specification (RFC 2236). For optimum network resource usage, set the timeout interval to match your network's multicast router settings.

Data type: Numeric; unit of measure is seconds

Default value: 260

Required: Yes, if IGMP snooping is enabled

Aliases None
Required? false
Position? 4
Default value 260
Accept pipeline input? false
Accept wildcard characters?    false
-enableFastMacCacheFailover [<Boolean>]

Optional. When an uplink that was in standby mode becomes active, it can take several minutes for external Ethernet interconnects to recognize that the server blades can now be reached on this newly active connection.

Enabling Fast MAC Cache Failover causes Ethernet packets to be transmitted on the newly active connection, which enables the external Ethernet interconnects to identify the new connection (and update their MAC caches).

The transmission sequence is repeated a few times at the MAC refresh interval and completes in about 1 minute.

Default value: Enabled

Aliases None
Required? false
Position? 5
Default value True
Accept pipeline input? false
Accept wildcard characters?    false
-macRefreshInterval [<Int32>]

Optional. The time interval at which MAC caches are refreshed

Data type: Numeric; unit of measure is seconds

Default value: 5

Aliases None
Required? false
Position? 6
Default value 5
Accept pipeline input? false
Accept wildcard characters?    false
-enableNetworkLoopProtection [<Boolean>]

Optional. Enables or disables network loop and pause flood protection.

Pause flood protection:

Ethernet switch interfaces use pause frame based flow control mechanisms to control data flow. When a pause frame is received on a flow control enabled interface, the transmit operation is stopped for the pause duration specified in the pause frame. All other frames destined for this interface are queued up. If another pause frame is received before the previous pause timer expires, the pause timer is refreshed to the new pause duration value. If a steady stream of pause frames is received for extended periods of time, the transmit queue for that interface continues to grow until all queuing resources are exhausted. This condition severely impacts the switch operation on other interfaces. In addition, all protocol operations on the switch are impacted because of the inability to transmit protocol frames. Both port pause and priority-based pause frames can cause the same resource exhaustion condition.

VC interconnects provide the ability to monitor server downlink ports for pause flood conditions and take protective action by disabling the port. The default polling interval is 10 seconds and is not customer configurable. The SNMP agent supports trap generation when a pause flood condition is detected or cleared.

This feature operates at the physical port level. When a pause flood condition is detected on a Flex-10 physical port, all Flex-10 logical ports associated with physical ports are disabled. When the pause flood protection feature is enabled, this feature detects pause flood conditions on server downlink ports and disables the port. The port remains disabled until an administrative action is taken. The administrative action involves the following steps:

  1. Resolve the issue with the NIC on the server causing the continuous pause generation. This might include updating the NIC firmware and device drivers. Rebooting the server might not clear the pause flood condition if the cause of the pause flood condition is in the NIC firmware. In this case, the server must be completely disconnected from the power source to reset the NIC firmware.
  2. Re-enable the disabled ports on the VC interconnect modules.

Network loop protection:

The loop protection feature enables detection of loops on downlink ports, which can be Flex-10 logical ports or physical ports. The feature applies when Device Control Channel (DCC) protocol is running on the Flex-10 port. If DCC is not available, the feature applies to the physical downlink port.

Network loop protection uses two methods to detect loops:

  1. It periodically injects a special probe frame into the VC domain and monitors downlink ports for the looped back probe frame. If this special probe frame is detected on downlink ports, the port is considered to cause the loop condition.
  2. It monitors and intercepts common loop detection frames used in other switches. In network environments where the upstream switches send loop detection frames, the VC interconnects must ensure that any downlink loops do not cause these frames to be sent back to the uplink ports. Even though the probe frames ensure loops are detected, there is a small time window depending on the probe frame transmission interval in which the loop detection frames from the external switch might loop through down link ports and reach uplink ports. By intercepting the external loop detection frames on downlinks, the possibility of triggering loop protection on the upstream switch is eliminated. When network loop protection is enabled, VC interconnects intercept loop detection frames from various switch vendors, such as Cisco and HP Networking.

When the network loop protection feature is enabled, any probe frame or other supported loop detection frame received on a downlink port is considered to be causing the network loop, and the port is disabled immediately until an administrative action is taken. The administrative action involves resolving the loop condition and clearing the loop protection error condition. The loop detected status on a port can be cleared by un-assigning all networks from the profile connect corresponding to the port in the loop detected state.

The SNMP agent supports trap generation when a loop condition is detected or cleared.

Default value: Enabled

Aliases None
Required? false
Position? 7
Default value True
Accept pipeline input? false
Accept wildcard characters?    false
-SNMP [<Hashtable>]

Optional. SNMP Settings in a nested hashtable format.

Accepted properties (Property names and values are CasEsEnsitVE)

readCommunity <String>
Enabled <Bool>
systemContact <String>
snmpAccess <Array> (value: array of IP's with subnet mask bit or subnet address; e.g. for host: 192.168.1.1/32, Subnet 192.168.1.0/24)
trapDestinations <Array>
	|- trapDestination <String> (value: IP or FQDN of host)
	|- communityString <String>
	|- trapFormat <String> (value: "SNMPv1" or "SNMPv2")
	|- trapSeverities <Array> (filter values: "Critical", "Major", "Minor", "Warning", "Normal", "Info", "Unknown")
	|- enetTrapCategories <Array> (filter values: "PortStatus", "PortThresolds", "Other")
	|- fcTrapCategories <Array> (filter values: "PortStatus", "Other")
	|- vcmTrapCategories <Array> (filter values: "Legacy")

Example:

$SNMP = @{readCommunity = "MyTr@p1"; enabled=$True; systemContact = "Network Admin"; snmpAccess = @("192.168.1.2/32","10.1.1.0/24");trapDestinations = @(@{trapDestination="myhost.local";communityString="MyTr@p2";trapFormat="snmpv1";trapSeverities=@("critical", "major", "minor", "warning", "normal", "info", "unknown");fcTrapCategories=@("PortStatus", "Other")},@{trapDestination="192.168.1.10";communityString="N3tw0rkTrap";trapFormat="snmpv1";trapSeverities=@("critical", "major", "minor", "warning", "normal", "info", "unknown");fcTrapCategories=@("Port status", "Other")})}

Aliases None
Required? false
Position? 8
Default value <none>
Accept pipeline input? false
Accept wildcard characters?    false
-Import <Object>
Import JSON file to create LIG.
Aliases None
Required? true
Position? named
Default value <none>
Accept pipeline input? false
Accept wildcard characters?    false

<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, ErrorVariable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216).

INPUTS

System.Collections.Hashtable

Hashtable containing Interconnect Bay layout and associated interconnect module.

OUTPUTS

System.ObjectSystem.Management.Automation.PSCustomObject

Logical Interconnect Group creation async task

RELATED LINKS

EXAMPLES

-------------------------- EXAMPLE 1 -------------------------- 

PS C:\> $SNMP = @{readCommunity = "MyTr@p1"; enabled=$True; systemContact = "Network Admin"; snmpAccess = @("192.168.1.2/32","10.1.1.0/24");trapDestinations = @(@{trapDestination="myhost.local";communityString="MyTr@p2";trapFormat="snmpv1";trapSeverities=@("critical", "major", "minor", "warning", "normal", "info", "unknown");fcTrapCategories=@("PortStatus", "Other")})}
PS C:\> $Bays = @{1 = "FlexFabric";2 = "FlexFabric"}
PS C:\> New-HPOVLogicalInterconnectGroup "FlexFabric Production 1" -bays $Bays -snmp $SNMP
   
Create a Logical Interconnect Group with VC FlexFabric modules in Bays 1 and 2, and SNMP Settings
-------------------------- EXAMPLE 2 -------------------------- 

PS C:\> New-HPOVLogicalInterconnectGroup -LIGName "Flex10/10D and FlexFabric Production 1" -bays @{1 = "Flex1010D";2 = "Flex1010D";3 = "FlexFabric";4 = "FlexFabric"} -enableIgmpSnooping $True -igmpIdleTimeoutInterval 300 -LoopProtect $True
  
Create a Logical Interconnect Group with VC Flex10/10D in Bays 1 and 2, FlexFabric modules in Bays 3 and 4, Enable IGMP Snooping, IGMP Idle timeout and LoopProtect
-------------------------- EXAMPLE 3 -------------------------- 

PS C:\> New-HPOVLogicalInterconnectGroup -import c:\dir\mylig.json
   
Create a Logical Interconnect Group by using a JSON formatted input file.

HP OneView 1.06 Library

NAME

New-HPOVLogicalInterconnectGroup

SYNOPSIS

Create new Logical Interconnect Group.

SYNTAX

New-HPOVLogicalInterconnectGroup -Name <String> -Bays <Hashtable> [-enableIgmpSnooping <Boolean>] [-igmpIdleTimeoutInterval <Int32>] [-enableFastMacCacheFailover <Boolean>] [-macRefreshInterval <Int32>] [-enableNetworkLoopProtection <Boolean>] [-SNMP <Hashtable>] [<CommonParameters>]
New-HPOVLogicalInterconnectGroup [[-Name] <String>] [[-Bays] <Hashtable>] [[-enableIgmpSnooping] <Boolean>] [[-igmpIdleTimeoutInterval] <Int32>] [[-enableFastMacCacheFailover] <Boolean>] [[-macRefreshInterval] <Int32>] [[-enableNetworkLoopProtection] <Boolean>] [[-SNMP] <Hashtable>] -Import <Object> [<CommonParameters>]

DESCRIPTION

This cmdlet provides the ability to create a Logical Interconnect Group. Bays 1 and 2 are required, and need to be identical.

PARAMETERS

-Name <String>
Required. The Logical Interconnect Group Name
Required? false
Position? 1
Default value <none>
Accept pipeline input? false
Accept wildcard characters? false

-Bays <Hashtable>
Required. A Hashtable value of each Interconnect Bay. Valid values are FlexFabric, Flex10, Flex1010D only.
E.g. @{1 = "Flex10";2 = "Flex10";3 = "FlexFabric";4 = "Flexfabric";5 = "";6 = "";7 = "";8 = "";}
Required? false
Position? 2
Default value <none>
Accept pipeline input? false
Accept wildcard characters? false

-enableIgmpSnooping <Boolean>
Aliases [-IGMPSnoop]
Optional. The IGMP snooping feature allows interconnects to monitor the IGMP IP multicast membership activities and configure hardware Layer 2 switching behavior of multicast traffic to optimize network resource usage. Currently, only IGMP v1 and v2 (RFC 2236) are supported.
Required? false
Position? 3
Default value Disabled
Accept pipeline input? false
Accept wildcard characters? false

-igmpIdleTimeoutInterval <Int32>
Aliases [-IGMPIdle]
Optional. The Group Membership Interval value, as specified by the IGMP v2 specification (RFC 2236).
For optimum network resource usage, set the timeout interval to match your network's multicast router settings.
Data type: Numeric; unit of measure is seconds
Default value: 260
Required: Yes, if IGMP snooping is enabled
Required? false
Position? 4
Default value 260
Accept pipeline input? false
Accept wildcard characters? false

-enableFastMacCacheFailover <Boolean>
Aliases [-FastMAC]
Optional. When an uplink that was in standby mode becomes active, it can take several minutes for external Ethernet interconnects to recognize that the server blades can now be reached on this newly active connection.
Enabling Fast MAC Cache Failover causes Ethernet packets to be transmitted on the newly active connection, which enables the external Ethernet interconnects to identify the new connection (and update their MAC caches). The transmission sequence is repeated a few times at the MAC refresh interval and completes in about 1 minute.
Required? false
Position? 5
Default value True
Accept pipeline input? false
Accept wildcard characters? false

-macRefreshInterval <Int32>
Aliases [-FastMACRefresh]
Optional. The time interval at which MAC caches are refreshed; unit of measure is seconds
Required? false
Position? 6
Default value 5
Accept pipeline input? false
Accept wildcard characters? false

-enableNetworkLoopProtection <Boolean>
Aliases [-LoopProtect]
Optional. Enables or disables network loop and pause flood protection.
Pause flood protection:
Ethernet switch interfaces use pause frame based flow control mechanisms to control data flow. When a pause frame is received on a flow control enabled interface, the transmit operation is stopped for the pause duration specified in the pause frame. All other frames destined for this interface are queued up. If another pause frame is received before the previous pause timer expires, the pause timer is refreshed to the new pause duration value. If a steady stream of pause frames is received for extended periods of time, the transmit queue for that interface continues to grow until all queuing resources are exhausted. This condition severely impacts the switch operation on other interfaces. In addition, all protocol operations on the switch are impacted because of the inability to transmit protocol frames. Both port pause and priority-based pause frames can cause the same resource exhaustion condition.
VC interconnects provide the ability to monitor server downlink ports for pause flood conditions and take protective action by disabling the port. The default polling interval is 10 seconds and is not customer configurable. The SNMP agent supports trap generation when a pause flood condition is detected or cleared.
This feature operates at the physical port level. When a pause flood condition is detected on a Flex-10 physical port, all Flex-10 logical ports associated with physical ports are disabled. When the pause flood protection feature is enabled, this feature detects pause flood conditions on server downlink ports and disables the port. The port remains disabled until an administrative action is taken. The administrative action involves the following steps:
  1. Resolve the issue with the NIC on the server causing the continuous pause generation. This might include updating the NIC firmware and device drivers. Rebooting the server might not clear the pause flood condition if the cause of the pause flood condition is in the NIC firmware. In this case, the server must be completely disconnected from the power source to reset the NIC firmware.
  2. Re-enable the disabled ports on the VC interconnect modules.
Network loop protection:
The loop protection feature enables detection of loops on downlink ports, which can be Flex-10 logical ports or physical ports. The feature applies when Device Control Channel (DCC) protocol is running on the Flex-10 port. If DCC is not available, the feature applies to the physical downlink port.
Network loop protection uses two methods to detect loops:
  1. It periodically injects a special probe frame into the VC domain and monitors downlink ports for the looped back probe frame. If this special probe frame is detected on downlink ports, the port is considered to cause the loop condition.
  2. It monitors and intercepts common loop detection frames used in other switches. In network environments where the upstream switches send loop detection frames, the VC interconnects must ensure that any downlink loops do not cause these frames to be sent back to the uplink ports. Even though the probe frames ensure loops are detected, there is a small time window depending on the probe frame transmission interval in which the loop detection frames from the external switch might loop through down link ports and reach uplink ports. By intercepting the external loop detection frames on downlinks, the possibility of triggering loop protection on the upstream switch is eliminated. When network loop protection is enabled, VC interconnects intercept loop detection frames from various switch vendors, such as Cisco and HP Networking.
When the network loop protection feature is enabled, any probe frame or other supported loop detection frame received on a downlink port is considered to be causing the network loop, and the port is disabled immediately until an administrative action is taken. The administrative action involves resolving the loop condition and clearing the loop protection error condition. The loop detected status on a port can be cleared by un-assigning all networks from the profile connect corresponding to the port in the loop detected state.
The SNMP agent supports trap generation when a loop condition is detected or cleared.
Required? false
Position? 7
Default value True
Accept pipeline input? false
Accept wildcard characters? false

-SNMP <Hashtable>
Optional. SNMP Settings in a nested hashtable format.
Accepted properties (Property names and values are CasEsEnsitiVE)
  • readCommunity <String>
  • Enabled <Bool>
  • systemContact <String>
  • snmpAccess <Array> (value: array of IP's with subnet mask bit or subnet address; e.g. for host: 192.168.1.1/32, Subnet 192.168.1.0/24)
  • trapDestinations <Array>:
    • trapDestination <String> (value: IP or FQDN of host)
    • communityString <String>
    • trapFormat <String> (value: "SNMPv1" or "SNMPv2")
    • trapSeverities <Array> (filter values: "Critical", "Major", "Minor", "Warning", "Normal", "Info", "Unknown")
    • enetTrapCategories <Array> (filter values: "PortStatus", "PortThresolds", "Other")
    • fcTrapCategories <Array> (filter values: "PortStatus", "Other")
    • vcmTrapCategories <Array> (filter values: "Legacy")
E.g. $SNMP = @{readCommunity = "MyTr@p1"; enabled=$True; systemContact = "Network Admin"; snmpAccess = @("192.168.1.2/32","10.1.1.0/24");trapDestinations = @({trapDestination="myhost.local";communityString="MyTr@p2";trapFormat="snmpv1";trapSeverities=@("critical", "major", "minor", "warning", "normal", "info", "unknown");fcTrapCategories=@("PortStatus","Other")},@{trapDestination="192.168.1.10";communityString="N3tw0rkTrap";trapFormat="snmpv1";trapSeverities=@("critical", "major", "minor", "warning", "normal", "info", "unknown");fcTrapCategories=@("Port status", "Other")})}
Required? false
Position? 8
Default value <none>
Accept pipeline input? false
Accept wildcard characters? false

-Import <Object>
Import JSON file to create LIG.
Required? true
Position? named
Default value <none>
Accept pipeline input? false
Accept wildcard characters? false

<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, ErrorVariable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more information, see about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216).

INPUTS

System.Collections.Hashtable
Interconnect Bay layout.

OUTPUTS

System.Management.Automation.PSCustomObject
Logical Interconnect Group async task

RELATED LINKS

EXAMPLES

-------------------------- EXAMPLE 1 --------------------------

PS C:\> $SNMP = @{readCommunity = "MyTr@p1"; enabled=$True; systemContact = "Network Admin"; snmpAccess = @("192.168.1.2/32","10.1.1.0/24");trapDestinations =@({trapDestination="myhost.local";communityString="MyTr@p2";trapFormat="snmpv1";trapSeverities=@("critical", "major", "minor", "warning", "normal", "info", "unknown");fcTrapCategories=@("PortStatus", "Other")})}
PS C:\> $Bays = @{1 = "FlexFabric";2 = "FlexFabric"}
PS C:\> New-HPOVLogicalInterconnectGroup "FlexFabric Production 1" -bays $Bays -snmp $SNMP
Create a Logical Interconnect Group with VC FlexFabric modules in Bays 1 and 2, and SNMP Settings

-------------------------- EXAMPLE 2 --------------------------

PS C:\> New-HPOVLogicalInterconnectGroup -LIGName "Flex10/10D and FlexFabric Production 1" -bays @{1 = "Flex1010D";2 = "Flex1010D";3 = "FlexFabric";4 ="FlexFabric"} -enableIgmpSnooping $True -igmpIdleTimeoutInterval 300 -LoopProtect $True
Create a Logical Interconnect Group with VC Flex10/10D in Bays 1 and 2, FlexFabric modules in Bays 3 and 4, Enable IGMP Snooping, IGMP Idle timeout and LoopProtect

-------------------------- EXAMPLE 3 --------------------------

PS C:\> New-HPOVLogicalInterconnectGroup -import c:\dir\mylig.json
Create a Logical Interconnect Group by using a JSON formatted input file.

Last edited Aug 20, 2014 at 7:10 PM by chrislynchhp, version 8