Configuring Interfaces The main function of a switch is to relay frames from one data link to another. To relay the frames, the characteristics of the interfaces through which the frames are received and sent must be defined. The configured interfaces can be Fibre Channel interfaces, Gigabit Ethernet interfaces, the management interface (mgmt0), or VSAN interfaces.

Free Download and information on Sync-N-Link - Sync-N-Link for FCP is an auto-sync for Final Cut Pro that allows processing projects or bins of unsynchronized clips exported from Final Cut Pro to save your time or Synchronize after editing.

This chapter describes the basic interface configuration to get your switch up and running. It includes the following sections: • • • • • • See and for more information on configuring mgmt0 interfaces. See and for more information on configuring Gigabit Ethernet interfaces. Tip Before you begin configuring the switch, ensure that the modules in the chassis are functioning as designed. To verify the status of a module at any time, issue the show module command in EXEC mode (see the ). Fibre Channel Interfaces This section describes Fibre Channel interface characteristics, including (but not limited to) modes, frame encapsulation, states, SFPs, and speeds.

This section includes the following topics: • • • • • • • • • • • • • • • • • • • • • • Generation 1 Interfaces Configuration Guidelines The generation 1 interfaces configuration guidelines apply to the following hardware: • The 32-port, 2-Gbps or 1-Gbps switching module interfaces • The Cisco MDS 9140 and 9120 switch interfaces When configuring these host-optimized ports, the following port mode guidelines apply: • You can configure only the first port in each 4-port group (for example, the first port in ports 1-4, the fifth port in ports 5-8 and so on) as an E port. If the first port in the group is configured as an E port, the other three ports in each group (ports 2-4, 6-8 and so on) are not usable and remain shutdown. • If you execute the write erase command on a 32-port switching module, and then copy a saved configuration to the switch from a text file that contains the no system default switchport shutdown command, you need to copy the text file to the switch again for the E ports to come up without manual configuration. • If any of the other three ports are enabled, you cannot configure the first port as an E port. The other three ports continue to remain enabled. • The auto mode is not allowed in a 32-port switching module or the host-optimized ports in the Cisco 9100 Series (16 host-optimized ports in the Cisco MDS 9120 switch and 32 host-optimized ports in the Cisco MDS 9140 switch).

• The default port mode is Fx (Fx negotiates to F or FL) for 32-port switching modules. • The 32-port switching module does not support FICON. Note We recommend that you configure your E ports on a 16-port switching module. If you must configure an E port on a 32-port host-optimized switching module, the other three ports in that 4-port group cannot be used. Note In the Cisco MDS 9100 Series, the groups of ports that are located on the left and outlined in white are full line rate. The other ports are host-optimized.

Each group of 4 host-optimized ports have the same features as for the 32-port switching module. E Text Editor Serial Key here. About Interface Modes Each physical Fibre Channel interface in a switch may operate in one of several port modes: E port, F port, FL port, TL port, TE port, SD port, ST port, and B port (see ). Besides these modes, each interface may be configured in auto or Fx port modes. These two modes determine the port type during interface initialization.

Figure 13-1 Cisco MDS 9000 Family Switch Port Modes Note Interfaces are created in VSAN 1 by default. See Each interface has an associated administrative configuration and an operational status: • The administrative configuration does not change unless you modify it.

This configuration has various attributes that you can configure in administrative mode. • The operational status represents the current status of a specified attribute like the interface speed. This status cannot be changed and is read-only. Some values may not be valid when the interface is down (for example, the operational speed).

Note When a module is removed and replaced with the same type of module, the configuration is retained. If a different type of module is inserted, then the original configuration is no longer retained. Each interface is briefly described in the sections that follow. E Port In expansion port (E port) mode, an interface functions as a fabric expansion port. This port may be connected to another E port to create an Inter-Switch Link (ISL) between two switches.

E ports carry frames between switches for configuration and fabric management. They serve as a conduit between switches for frames destined to remote N ports and NL ports. E ports support class 2, class 3, and class F service. An E port connected to another switch may also be configured to form a PortChannel (see ). Note We recommend that you configure E ports on 16-port modules. If you must configure an E port on a 32-port oversubscribed module, then you can only use the first port in a group of four ports (for example, ports 1 through 4, 5 through 8, and so forth). The other three ports cannot be used.

F Port In fabric port (F port) mode, an interface functions as a fabric port. This port may be connected to a peripheral device (host or disk) operating as an N port. An F port can be attached to only one N port. F ports support class 2 and class 3 service. FL Port In fabric loop port (FL port) mode, an interface functions as a fabric loop port.

This port may be connected to one or more NL ports (including FL ports in other switches) to form a public arbitrated loop. Retinal Atlas Yannuzzi Free Download. If more than one FL port is detected on the arbitrated loop during initialization, only one FL port becomes operational and the other FL ports enter nonparticipating mode. FL ports support class 2 and class 3 service.

Note FL port mode is not supported on 4-port 10-Gbps switching module interfaces. NP Ports An NP port is a port on a device that is in NPV mode and connected to the core switch via an F port. NP ports behave like N ports except that in addition to providing N port behavior, they also function as proxies for multiple, physical N ports. For more details about NP ports and NPV, see TL Port In translative loop port (TL port) mode, an interface functions as a translative loop port. It may be connected to one or more private loop devices (NL ports).

TL ports are specific to Cisco MDS 9000 Family switches and have similar properties as FL ports. TL ports enable communication between a private loop device and one of the following devices: • A device attached to any switch on the fabric • A device on a public loop anywhere in the fabric • A device on a different private loop anywhere in the fabric • A device on the same private loop TL ports support class 2 and class 3 services. Private loop devices refer to legacy devices that reside on arbitrated loops. These devices are not aware of a switch fabric because they only communicate with devices on the same physical loop (see the ). Tip We recommend configuring devices attached to TL ports in zones that have up to 64 zone members.

Note TL port mode is not supported on Generation 2 switching module interfaces. TE Port In trunking E port (TE port) mode, an interface functions as a trunking expansion port. It may be connected to another TE port to create an extended ISL (EISL) between two switches. TE ports are specific to Cisco MDS 9000 Family switches.

They expand the functionality of E ports to support the following: • VSAN trunking • Transport quality of service (QoS) parameters • Fibre Channel trace (fctrace) feature In TE port mode, all frames are transmitted in EISL frame format, which contains VSAN information. Interconnected switches use the VSAN ID to multiplex traffic from one or more VSANs across the same physical link. This feature is referred to as trunking in the Cisco MDS 9000 Family (see ). TE ports support class 2, class 3, and class F service. TF Port In trunking F port (TF port) mode, an interface functions as a trunking expansion port.

It may be connected to another trunked N port (TN port) or trunked NP port (TNP port) to create a link between a core switch and an NPV switch or an HBA to carry tagged frames. TF ports are specific to Cisco MDS 9000 Family switches. They expand the functionality of F ports to support VSAN trunking. In TF port mode, all frames are transmitted in EISL frame format, which contains VSAN information. Interconnected switches use the VSAN ID to multiplex traffic from one or more VSANs across the same physical link. This feature is referred to as trunking in the Cisco MDS 9000 Family (see ).

TF ports support class 2, class 3, and class F service. TNP Port In trunking NP port (TNP port) mode, an interface functions as a trunking expansion port. It may be connected to a trunked F port (TF port) to create a link to a core NPIV switch from an NPV switch to carry tagged frames. SD Port In SPAN destination port (SD port) mode, an interface functions as a switched port analyzer (SPAN). The SPAN feature is specific to switches in the Cisco MDS 9000 Family. It monitors network traffic that passes though a Fibre Channel interface. This monitoring is done using a standard Fibre Channel analyzer (or a similar switch probe) that is attached to an SD port.

SD ports do not receive frames, they merely transmit a copy of the source traffic. The SPAN feature is nonintrusive and does not affect switching of network traffic for any SPAN source ports (see ).

ST Port In the SPAN tunnel port (ST port) mode, an interface functions as an entry point port in the source switch for the RSPAN Fibre Channel tunnel. The ST port mode and the remote SPAN (RSPAN) feature are specific to switches in the Cisco MDS 9000 Family. When configured in ST port mode, the interface cannot be attached to any device, and thus cannot be used for normal Fibre Channel traffic (see the ). Note ST port mode is not supported on the Cisco MDS 9124 Fabric Switch, the Cisco Fabric Switch for HP c-Class BladeSystem, and the Cisco Fabric Switch for IBM BladeCenter. Fx Port Interfaces configured as Fx ports can operate in either F port or FL port mode. The Fx port mode is determined during interface initialization depending on the attached N port or NL port.

This administrative configuration disallows interfaces to operate in any other mode—for example, preventing an interface to connect to another switch. B Port While E ports typically interconnect Fibre Channel switches, some SAN extender devices, such as the Cisco PA-FC-1G Fibre Channel port adapter, implement a bridge port (B port) model to connect geographically dispersed fabrics. This model uses B ports as described in the T11 Standard FC-BB-2. Depicts a typical SAN extension over an IP network.

If an FCIP peer is a SAN extender device that only supports Fibre Channel B ports, you need to enable the B port mode for the FCIP link. When a B port is enabled, the E port functionality is also enabled and they coexist. If the B port is disabled, the E port functionality remains enabled (see ). Auto Mode Interfaces configured in auto mode can operate in one of the following modes: F port, FL port, E port, TE port, or TF port.

The port mode is determined during interface initialization. For example, if the interface is connected to a node (host or disk), it operates in F port or FL port mode depending on the N port or NL port mode. If the interface is attached to a third-party switch, it operates in E port mode.

If the interface is attached to another switch in the Cisco MDS 9000 Family, it may become operational in TE port mode (see ). TL ports and SD ports are not determined during initialization and are administratively configured. Note Fibre Channel interfaces on Storage Services Modules (SSMs) cannot be configured in auto mode. N Port Identifier Virtualization N port identifier virtualization (NPIV) provides a means to assign multiple FC IDs to a single N port. This feature allows multiple applications on the N port to use different identifiers and allows access control, zoning, and port security to be implemented at the application level. Shows an example application using NPIV. Figure 13-2 NPIV Example You must globally enable NPIV for all VSANs on the MDS switch to allow the NPIV-enabled applications to use multiple N port identifiers.

Note All of the N port identifiers are allocated in the same VSAN. About Interface States The interface state depends on the administrative configuration of the interface and the dynamic state of the physical link. Administrative States The administrative state refers to the administrative configuration of the interface as described in.

Table 13-1 Administrative States Administrative State Description Up Interface is enabled. Down Interface is disabled. If you administratively disable an interface by shutting down that interface, the physical link layer state change is ignored. Operational States The operational state indicates the current operational state of the interface as described in. Table 13-2 Operational States Operational State Description Up Interface is transmitting or receiving traffic as desired. To be in this state, an interface must be administratively up, the interface link layer state must be up, and the interface initialization must be completed. Down Interface cannot transmit or receive (data) traffic.

Trunking Interface is operational in TE or TF mode. Reason Codes Reason codes are dependent on the operational state of the interface as described in. Table 13-3 Reason Codes for Interface States Administrative Configuration Operational Status Reason Code Up Up None. Down Down Administratively down—If you administratively configure an interface as down, you disable the interface. No traffic is received or transmitted. Note Only some of the reason codes are listed in. If the administrative state is up and the operational state is down, the reason code differs based on the nonoperational reason code as described in.

Table 13-4 Reason Codes for Nonoperational States Reason Code (long version) Description Applicable Modes Link failure or not connected The physical layer link is not operational. All SFP not present The small form-factor pluggable (SFP) hardware is not plugged in. Initializing The physical layer link is operational and the protocol initialization is in progress. Reconfigure fabric in progress The fabric is currently being reconfigured. Offline The Cisco NX-OS software waits for the specified R_A_TOV time before retrying initialization.

Inactive The interface VSAN is deleted or is in a suspended state. To make the interface operational, assign that port to a configured and active VSAN. Hardware failure A hardware failure is detected. Error disabled Error conditions require administrative attention.

Interfaces may be error-disabled for various reasons. For example: • Configuration failure. • Incompatible buffer-to-buffer credit configuration. To make the interface operational, you must first fix the error conditions causing this state; and next, administratively shut down or enable the interface. FC redirect failure A port is isolated because a Fibre Channel redirect is unable to program routes.

No port activation license available A port is not active because it does not have a port license. SDM failure A port is isolated because SDM is unable to program routes. Isolation due to ELP failure The port negotiation failed. Only E ports and TE ports Isolation due to ESC failure The port negotiation failed. Isolation due to domain overlap The Fibre Channel domains (fcdomain) overlap. Isolation due to domain ID assignment failure The assigned domain ID is not valid.

Isolation due to the other side of the link E port isolated The E port at the other end of the link is isolated. Isolation due to invalid fabric reconfiguration The port is isolated due to fabric reconfiguration. Isolation due to domain manager disabled The fcdomain feature is disabled. Isolation due to zone merge failure The zone merge operation failed.

Isolation due to VSAN mismatch The VSANs at both ends of an ISL are different. Nonparticipating FL ports cannot participate in loop operations.

It may happen if more than one FL port exists in the same loop, in which case all but one FL port in that loop automatically enters nonparticipating mode. Only FL ports and TL ports PortChannel administratively down The interfaces belonging to the PortChannel are down. Only PortChannel interfaces Suspended due to incompatible speed The interfaces belonging to the PortChannel have incompatible speeds. Suspended due to incompatible mode The interfaces belonging to the PortChannel have incompatible modes. Suspended due to incompatible remote switch WWN An improper connection is detected. All interfaces in a PortChannel must be connected to the same pair of switches.

Configuring Fibre Channel Interfaces To configure a Fibre Channel interface, follow these steps: Command Purpose Step 1 switch# config t Enters configuration mode. Step 2 switch(config)# interface fc1/1 switch(config-if)# Selects a Fibre Channel interface and enters interface configuration submode.

Note When a Fibre Channel interface is configured, it is automatically assigned a unique world wide name (WWN). If the interface’s operational state is up, it is also assigned a Fibre Channel ID (FC ID). To configure a range of interfaces, follow these steps: Command Purpose Step 1 switch# config t Enters configuration mode. Step 2 switch(config)# interface fc1/1 - 4, fc2/1 - 3 switch(config-if)# Selects the range of Fibre Channel interfaces and enters interface configuration submode3.

Note In this command, provide a space before and after the comma. For the Cisco Fabric Switch for HP c-Class BladeSystem and the Cisco Fabric Switch for IBM BladeCenter, you can configure a range of interfaces among internal ports or external ports, but you cannot mix both interface types within the same range. For example, “bay 1-10, bay 12” or “ext 0, ext 15-18” are valid ranges, but “bay 1-5, ext 15-17” is not. Graceful Shutdown Interfaces on a port are shut down by default (unless you modified the initial configuration).

The Cisco NX-OS software implicitly performs a graceful shutdown in response to either of the following actions for interfaces operating in the E port mode: • If you shut down an interface. • If a Cisco NX-OS software application executes a port shutdown as part of its function. A graceful shutdown ensures that no frames are lost when the interface is shutting down. When a shutdown is triggered either by you or the Cisco NX-OS software, the switches connected to the shutdown link coordinate with each other to ensure that all frames in the ports are safely sent through the link before shutting down. This enhancement reduces the chance of frame loss. A graceful shutdown is not possible in the following situations: • If you physically remove the port from the switch. • If in-order-delivery (IOD) is enabled (see ).

• If the Min_LS_interval interval is higher than 10 seconds (see). Note This feature is only triggered if both switches at either end of this E port interface are MDS switches and are running Cisco SAN-OS Release 2.0(1b) or later, or MDS NX-OS Release 4.1(1a) or later.

Setting the Interface Administrative State To gracefully shut down an interface, follow these steps: Command Purpose Step 1 switch# config t Enters configuration mode. Step 2 switch(config)# interface fc1/1 Selects a Fibre Channel interface and enters interface configuration submode. Step 3 switch(config-if)# shutdown Gracefully shuts down the interface and administratively disables traffic flow (default). To enable traffic flow, follow these steps: Command Purpose Step 1 switch# config t Enters configuration mode.

Step 2 switch(config)# interface fc1/1 Selects a Fibre Channel interface and enters interface configuration submode. Step 3 switch(config-if)# no shutdown Enables traffic flow to administratively allow traffic when the no prefix is used (provided the operational state is up). Configuring Interface Modes To configure the interface mode, follow these steps: Command Purpose Step 1 switch# config t Enters configuration mode. Step 2 switch(config)# interface fc1/1 switch(config-if)# Selects a Fibre Channel interface and enters interface configuration submode. Step 3 switch(config-if)# switchport mode F switch(config-if)# Configures the administrative mode of the port.

You can set the operational state to auto, E, F, FL, Fx, TL, NP, or SD port mode. Note Fx ports refers to an F port or an FL port (host connection only), but not E ports. Switch(config-if)# switchport mode auto switch(config-if)# Configures the interface mode to auto-negotiate an E, F, FL, or TE port mode (not TL or SD port modes) of operation. Note TL ports and SD ports cannot be configured automatically.

They must be administratively configured. Note You cannot configure Fibre Channel interfaces on SSMs in auto mode. Configuring System Default Port Mode F The system default switchport mode F command sets the administrative mode of all Fibre Channel ports to mode F, while avoiding traffic disruption caused by the formation of unwanted inter-switch links (ISLs). This command is part of the setup utility that runs during bootup after a write erase or reload.

It can also be executed from the command line in configuration mode. This command changes the configuration of the following ports to administrative mode F: • All ports that are down and that are not out-of-service. • All F ports that are up, whose operational mode is F, and whose administrative mode is not F. This command does not affect the configuration of the following ports: • All user-configured ports, even if they are down. • All non-F ports that are up; however, if non-F ports are down, this command changes the administrative mode of those ports.

Shows the command in the setup utility, and shows the command from the command line. Example 13-1 Setup Utility Configure default switchport mode F (yes/no) [n]: y Example 13-2 Command Line switch(config)# system default switchport mode F Note To ensure that ports that are part of ISLs do not get changed to port mode F, configure the ports in port mode E, rather than in Auto mode. Note When the command is executed from the command line, switch operation remains graceful. No ports are flapped.

To sets the administrative mode of Fibre Channel ports to mode F in the CLI, follow these steps: Command Purpose Step 1 switch# config t Enters configuration mode. Step 2 switch(config)# system default switchport mode F Sets the administrative mode of Fibre Channel ports to mode F (if applicable). Switch(config)# no system default switchport mode F Sets the administrative mode of Fibre Channel ports to the default (unless user configured). Note For detailed information about the switch setup utility see Configuring Port Speeds By default, the port administrative speed for an interface is automatically calculated by the switch. Caution Changing the port administrative speed is a disruptive operation. To configure the port speed of the interface, follow these steps: Command Purpose Step 1 switch# config t Enters configuration mode.

Step 2 switch(config)# interface fc 1/1 Selects the mgmt0 interface and enters interface configuration mode. Step 3 switch(config-if)# switchport speed 1000 Configures the port speed of the interface to 1000 Mbps. The number indicates the speed in megabits per second (Mbps). You can set the speed to 1000 (for 1-Gbps interfaces), 2000 (for 2-Gbps interfaces), 4000 (for 4-Gbps interfaces), 8000 (for 8-Gbps interfaces), or auto (default). Switch(config-if)# no switchport speed Reverts the factory default ( auto) administrative speed of the interface. For internal ports on the Cisco Fabric Switch for HP c_Class BladeSystem and Cisco Fabric Switch for IBM BladeCenter, a port speed of 1 Gbps is not supported. Auto-negotiation is supported between 2 Gbps and 4 Gbps only.

Also, if the BladeCenter is a T chassis, then port speeds are fixed at 2 Gbps and auto-negotiation is not enabled. Autosensing Autosensing speed is enabled on all 4-Gbps and 8-Gbps switching module interfaces by default. This configuration enables the interfaces to operate at speeds of 1 Gbps, 2 Gbps, or 4 Gbps on the 4-Gbps switching modules, and 8-Gbps on the 8-Gbps switching modules. When autosensing is enabled for an interface operating in dedicated rate mode, 4-Gbps of bandwidth is reserved, even if the port negotiates at an operating speed of 1-Gbps or 2-Gbps. To avoid wasting unused bandwidth on 48-port and 24-port 4-Gbps and 8-Gbps Fibre Channel switching modules, you can specify that only 2 Gbps of required bandwidth be reserved, not the default of 4 Gbps or 8-Gbps. This feature shares the unused bandwidth within the port group provided that it does not exceed the rate limit configuration for the port. You can also use this feature for shared rate ports that are configured for autosensing.

Tip When migrating a host that supports up to 2-Gbps traffic (that is, not 4-Gbps with autosensing capabilities) to the 4-Gbps switching modules, use autosensing with a maximum bandwidth of 2-Gbps. When migrating a host that supports up to 4-Gbps traffic (that is, not 8-Gbps with autosensing capabilities) to the 8-Gbps switching modules, use autosensing with a maximum bandwidth of 4-Gbps. Specifying a Port Owner Using the port owner feature, you can specify the owner of a port and the purpose for which a port is used so that the other administrators are informed. To specify or remove the port owner, follow these steps: Command Purpose Step 1 switch# config t Enters configuration mode.

Step 2 switch(config)# interface fc1/1 Selects the port interface. Step 3 switch(config)# switchport owner description The description can include name of the owner and the purpose for which the port is used. The description can be up to 80 characters long.

Switch(config)# no switchport owner Removes (default) the port owner description. Note The port guard and port owner features are available for all ports irrespective of the operational mode. To display the owner description specified for a port, use the following commands: switch# show running interface fc module-number / interface-number switch# show port internal info interface fc module-number / interface-number Configuring Port Guard Using the port guard feature, you can restrict the number of error reports and bring a malfunctioning port to down state dynamically. The link failure can be caused by the following reasons: • General link failure. • Link failure due to loss of signal (LOS) or not operational (NOS). • High bit error rate.

• Too many interrupts. • Cable is disconnected.

• BB_credit buffers overflow. • Hardware recoverable errors. • The connected device rebooted (F ports only). • The connected linecard rebooted (ISL only). The port guard feature is intended for use in environments where the system and application environment does not adapt quickly and efficiently to a port going down and back up, or to a port rapidly cycling up and down, which can happen in some failure modes.

For example, if a system takes five seconds to stabilize after a port goes down, but the port is going up and down once a second, this might ultimately cause a more severe failure in the fabric. The port guard feature gives the SAN administrator the ability to prevent this issue from occurring in environments that are vulnerable to these problems. The port can be configured to stay down after the first failure, or after specified number of failures in specified time period. This allows the SAN administrator to intervene and control the recovery, avoiding any problems caused by the cycling. To enable or disable the port guard for a port, follow these steps: Command Purpose Step 1 switch# config t Enters configuration mode. Step 2 switch(config)# interface fc1/1 Selects the port interface.

Step 3 switch(config)# errdisable detect cause link-down Brings the port to down state if the link flaps once. Switch(config)# errdisable detect cause link-down [num-times number duration seconds ] Brings the port to down state if the link flaps for the number of instances within the specified seconds. Switch(config)# no errdisable detect cause link-down Removes (default) the port guard configuration for the interface. The link resumes flapping and sending error reports normally.

Note Even if the link does not flap due to failure of the link, and port guard is not enabled, the port goes into a down state if too many invalid FLOGI requests are received from the same host. Use the shut and the no shut commands consecutively to bring up the link.

This example shows how to configure port guard to bring a port to down state if the link flaps 5 times within 30 seconds: Switch# config t Switch (config)# interface fc1/1 Switch (config-if)# errdisable detect cause link-down num-times 5 duration 30 Verifying Port Guard Configuration To verify the port guard configuration, run the show running-config interface command in the EXEC mode. Switch# show running-config interface fc2/1!Command: show running-config interface fc2/1!Time: Tue May 26 10: version 6.2(1) interface fc2/1 switchport mode F switchport trunk mode off errdisable detect cause link-down errdisable detect cause bit-errors errdisable detect cause sync-loss errdisable detect cause link-reset errdisable detect cause credit-loss no shutdown Configuring Port Monitor Port monitor helps to monitor the performance and the status of ports and generate alerts when problems occur. You can configure the thresholds for various counters and trigger an event when the values cross the threshold settings. This section includes the following topics: • • • • • Enabling Port Monitor To enable port monitor, follow these steps: Command Purpose Step 1 switch# config t Enters configuration mode. Step 2 switch(config)# port-monitor enable Enables (default) port monitoring. Switch(config)# no port-monitor enable Disables port monitoring. Configuring Port Monitor Policy To configure a port monitor policy, follow these steps: Command Purpose Step 1 switch# config t Enters configuration mode.

Step 2 switch(config)# port-monitor name policyname Specifies the policy name and enters the port monitoring policy configuration mode. Switch(config)# no port-monitor name policyname Removes the policy. Step 3 switch(config-port-monitor)# port-type access-port Applies the policy to the access ports. Switch(config-port-monitor)# port-type trunks Applies the policy to the trunk ports. Switch(config-port-monitor)# port-type all Applies the policy to all ports. Step 4 switch(config-port-monitor)# counter invalid-crc poll-interval seconds delta rising-threshold percentage1 event event-id falling-threshold percentage2 event event-id Specifies the delta invalid CRC poll interval in seconds, the thresholds in percentage, and the event IDs of events to be triggered.

Switch(config-port-monitor)# counter invalid-words poll-interval seconds delta rising-threshold percentage1 event event-id falling-threshold percentage2 event event-id Specifies the delta invalid words poll interval in seconds, the thresholds in percentage, and the event IDs of events to be triggered. Switch(config-port-monitor)# counter link-loss poll-interval seconds delta rising-threshold percentage1 event event-id falling-threshold percentage2 event event-id Specifies the delta link loss poll interval in seconds, the thresholds in percentage, and the event IDs of events to be triggered. Switch(config-port-monitor)# counter protocol-error poll-interval seconds delta rising-threshold percentage1 event event-id falling-threshold percentage2 event event-id Specifies the delta protocol error poll interval in seconds, the thresholds in percentage, and the event IDs of events to be triggered. Switch(config-port-monitor)# counter rx-performance poll-interval seconds delta rising-threshold percentage1 event event-id falling-threshold percentage2 event event-id Specifies the delta Rx counter poll interval in seconds and thresholds in percentage. Switch(config-port-monitor)# counter signal-loss poll-interval seconds delta rising-threshold percentage1 event event-id falling-threshold percentage2 event event-id Specifies the delta signal loss poll interval in seconds, the thresholds in percentage, and the event IDs of events to be triggered. Switch(config-port-monitor)# counter state-change poll-interval seconds delta rising-threshold percentage1 event event-id falling-threshold percentage2 event event-id Specifies the delta state change poll interval in seconds, the thresholds in percentage, and the event IDs of events to be triggered. Switch(config-port-monitor)# counter sync-loss poll-interval seconds delta rising-threshold percentage1 event event-id falling-threshold percentage2 event event-id Specifies the delta sync loss poll interval in seconds, the thresholds in percentage, and the event IDs of events to be triggered.

Switch(config-port-monitor)# counter tx-performance poll-interval seconds delta rising-threshold percentage1 event event-id falling-threshold percentage2 event event-id Specifies the delta Tx counter poll interval in seconds and thresholds in percentage. Switch(config-port-monitor)# no counter sync-loss Reverts to the default policy for sync loss performance counter values.

Switch(config-port-monitor)# no counter tx-performance Reverts to the default policy for Tx performance counter values. Step 5 switch(config-port-monitor)# monitor counter rx-performance Turns on Rx performance monitoring. Switch(config-port-monitor)# monitor counter tx-performance Turns on Tx performance monitoring. Switch(config-port-monitor)# no monitor counter tx-performance Turns off Tx performance monitoring. Switch(config-port-monitor)# no monitor counter sync-loss Turns off monitoring sync loss. Switch(config-port-monitor)# no monitor counter state-change Turns off monitoring state change. Default Policy The default policy has the following threshold values: Counter Threshold Type Interval (Seconds)% Rising Threshold Event% Falling Threshold Event Link Loss Delta 60 5 4 1 4 Sync Loss Delta 60 5 4 1 4 Protocol Error Delta 60 1 4 0 4 Signal Loss Delta 60 5 4 1 4 Invalid Words Delta 60 1 4 0 4 Invalid CRCs Delta 60 5 4 1 4 RX Performance Delta 648 4 524288000 4 TX Performance Delta 648 4 524288000 4 Activating a Port Monitor Policy To activate a port monitor policy, follow these steps: Command Purpose Step 1 switch# config t Enters configuration mode.

Step 2 switch(config)# port-monitor activate policyname Activates the specified port monitor policy. Switch(config)# port-monitor activate Activates the default port monitor policy. Switch(config)# no port-monitor activate policyname Deactivates the specified port monitoring policy.

Hi Peter, Ridiculous doesn't even get close. Last week we were in Denmark setting up a new FCP X shared storage workflow for 30 simultaneous users at a major television production company.

International broadcasters such as BBC, TF1 and others have purchased thousands of FCP X installs for their worldwide news and sports programming. Just a few days ago Sam Mestman posted on different groups that they were looking for a large number of experienced FCP X editors for their major clients in LA. And this is only the tip of the iceberg. In their official sales statements Apple announced that the number of FCP X licenses purchased last year had already exceeded the total purchases of classic FCP licenses over seven years. If you really want to know how well FCP X is doing, just read the user stories at FCP.co. It's high time for the haters and bashers to shut up and accept reality if they don't want to sound like complete idiots anymore.

I wish I could tell you more but: you ain't seen nothing yet (-: Best wishes, Ronny. I can understand why a 3rd party app developer said this. FCP X is used by many more consumers than professionals. That's why the sales numbers of FCP X are so good and that's also the reason why the sales of add-on packages for FCP X (like plugins) are down compared to the sales for FCP (or is this only me?!?):-) For 3rd party developers it is a different story. I am myself a plugin developer of the first hour for Final Cut Pro (1!!). Legacy FCP was mainly used by professionals (and bootlegging consumers).

Those who buy a $1000 NLE package don't care about $299 for a plugin package. A consumer who pays $299 for FCP X thinks twice, if not even 3 times about a $99 plugin purchase.

I highly doubt that Apple will discontinue FCP X. Their plan worked out.

FCP X sells pretty good. And for Apple it doesn't matter if they make a sale of $299 to a professional or a consumer.

-- Christoph Vonrhein []. I threw in my towel and began to learn x and PP at same time. Pp learning curve not steep at all. Keep on getting jobs, which is a blessing so cutting on legacy. Jobs slow down in two weeks so will go back to tutorials on both pp and X.

The cat who i did speak to had pretty good track record as developer and tons of success, that is why i just did not think he was starting a rumor but was based on some veracity. Seems from your guys inside intel that his instincts are totally absurd and and crazy. Glad i asked, now more compelled to continue to learn x Thanks. Hi Peter, I don't live in Ronny's world of corporate NLE work, I deal with individuals one at a time.

Over the past year I have had, almost on a weekly basis, people writing me saying that they are moving from FCP 7 or PP or Avid back to Apple and FCP X. They say that they are glad to have made the switch back. True, many FCP legacy users who are now using Avid or PP will probably stay there but more and more first timers are running FCP X. More Universities, Colleges and High schools are starting to teach FCP X and so it is growing a new user base.

And the numbers are large. Just last week I received an email from someone with whom I have been corresponding with about FCP for the past year. He said that he was glad that he finally listened to me and dnl the FCP X free demo, worked with it, bought the retail version and had just cut a complex project. He was coming back from PP and said that he could not be happier with X.

He said that it is 'so powerful'. From where I sit, it looks like the FCP X user base is growing at a rapid rate. I know many people who use X on a daily basis and make their living with it. It is their tool of choice. If you have worked with FCP X, and taken the time to learn the program you'll understand why it is gaining traction in the NLE world. Don't listen to those 'nay-sayers' spend some time with X and decide for yourself.

Hi Ken, As an editor who has been using Final Cut Pro since vers.2 in 2001 right up through 7, I was reluctant to try X. I did try it in early 2013 and couldn't get my head around it. Finally, in November, 2014, I gave it another shot.

With the help of Larry Jordan's fantastic and very methodical tutorials, it began to sink in. Ronny is so correct when he says that you have to let go of the format of editing that you've become used to in Legacy. Once I got the hang of it, I found using X liberating. I'm still learning but I've found that with X, there is so much more I can do in terms of graphic effects work. I'm just finishing a job with a lot of green screen scenes and the keying feature in X is far beyond what I had in 7. X also works beautifully with CoreMelt's Mocha Slice which I highly recommend.

Using it in X, I was able to easily remove cables and rigs in the green screen work. In fairness, I have to say that I did try PP first.

Although I found the transition from FCP 7 quite painless, PP as a whole seemed clunky and awkward compared to 7. However, I did appreciate its connectivity to AfterEffects and Photoshop and the audio program, Audition, is terrific. So is Adobe Media Encoder which comes with them in the CC package. So after using the trial version of PP, I was almost ready to go with it. Then I gave FCP X a second chance and here I am.

I also have to say that the Adobe subscription plan was a deal breaker for me. I really didn't like the idea of my credit card being dinged every month in perpetuity. And, that Ken, is my 2 cents. It does seem the whole effects style plugin market has been shifting as FCPX grows. One can certainly speculate but some of the notable things are: NoiseIndustries going from FCPX centric to supporting Adobe products as well. Although there are still FCPX exclusive plugins. RedGiant creating Universe, a number of free plugins included (like NoiseIndustries) but adding FCPX support for several of the higher end plugins like KnollLightFactory and ToonIt.

Related to RedGiant is CrumplePop, which had been FCPX exclusive, adding some of their plugins to Universe and, therefore, supporting other NLEs. GenArts killing SaphireEdge, while not FCPX exclusive, was their only product that supported FCPX amongst others. CoreMelt, which is FCPX exclusive, starting to bring their plugins to the App Store.

I'd 'heard' that BorisFX hand't been encouraged by BCC sales to FCPX users although their merger with ImagineerSystems (which is key to CoreMelt's SliceX, TrackX) should make things interesting. It would seem some of the patterns are: Big plugin makers entice with lots of free plugins as part of a bigger paid group. FCPX plugin makers are expanding beyond that NLE. CoreMelt, rather than adding other NLEs moves to the App Store. I don't doubt the huge amount of free plugins both from the bigger companies and from those small altruistic types are forcing changes in business models.

Craig Seeman Wrote: ------------------------------------------------------- >It does seem the whole effects style plugin market has been shifting as FCPX grows. >One can certainly speculate but some of the notable things are: >>NoiseIndustries going from FCPX centric to supporting Adobe products as well. Although there >are still FCPX exclusive plugins. >>RedGiant creating Universe, a number of free plugins included (like NoiseIndustries) but adding >FCPX support for several of the higher end plugins like KnollLightFactory and ToonIt. >>Related to RedGiant is CrumplePop, which had been FCPX exclusive, adding some of their plugins to >Universe and, therefore, supporting other NLEs. >>GenArts killing SaphireEdge, while not FCPX exclusive, was their only product that supported >FCPX amongst others.

>>CoreMelt, which is FCPX exclusive, starting to bring their plugins to the App Store. >>I'd 'heard' that BorisFX hand't been encouraged by BCC sales to FCPX users although their merger with >ImagineerSystems (which is key to CoreMelt's SliceX, TrackX) should make things interesting. >>It would seem some of the patterns are: >Big plugin makers entice with lots of free plugins as part of a bigger paid group. >FCPX plugin makers are expanding beyond that NLE. >CoreMelt, rather than adding other NLEs moves to the App Store. >>I don't doubt the huge amount of free plugins both from the bigger companies and from those small >altruistic types are forcing changes in business models. You forgot to mention me, CHV!

(balling) JK;-) There are a bunch of legacy FCP plugin developers that completely vanished for several reasons. Some were writing plugins using only the internal FX-Script language. FX-Script didn't involve a lot of programming knowledge. Everybody was basically able to write plugins.

FCP X / Motion 5 however only understand FxPlug plugins. That's hardcore C++.

FCP X can't handle FX-Script plugins, which is why these developers either needed to completely redevelop their plugins with the necessity to learn C++ (if they never did that before) or vanish. I have jumped on the FCP X train and redeveloped my plugins for it.

New ones are in the making as we speak. -- Christoph Vonrhein [].

Craig Seeman Wrote: ------------------------------------------------------- >I hand't mentioned you because I was hoping you'd add that info:) Apology accepted.:-) (JK!!) >You had expressed concern about declining sales. Some declining sales don't scare me away just like that.

I am still selling plugins for legacy FCP 7. The interesting part is that currently my sales are about 50/50 between the long dead legacy FCP 7 and the well alive current FCP X. Taking into account that FCP X now outsold FCP 7 I can only come to the conclusion that most FCP X sales are coming from non-professional users. There are many factors for the declining sales. More and a different breed of competition, a different set of FCP (X) users and the major price drop of FCP ($1000 >$299). This makes a $95 plugin package suddenly look soooooo expensive.

Especially to home users. >You seem to be one of the few brave FCPX only plugin developers remaining. Most of the other legacy FCP only developers are gone. Joe Maller, Artmetic, 'Too Much Too Soon', the other guy from Germany (forgot his name).

>Looking forward to see what you have cooking up. Salt, pepper and some C++ code. >Would the App Store be viable for you? I didn't look into that so far.

Apple takes a huge cut (30%). That's somehow holding me back. But then again, it's another sales platform that could bring in some business. Another thing is the copy protection.

I have developed an individual Serial Number system, where each user gets his own Serial Number that is locked to the users computer. Leaked Serial Numbers are worthless to anyone else. In the AppStore I have to rely on Apple's DRM which has already been compromised. That's a huge bootleg problem. So, I don't know if I will do it. -- Christoph Vonrhein []. I agree, Peter.

Just never, ever believe anyone who says FCP X is going to be discontinued or that Apple does not care about professionals. Those people simply don't have a clue. I get so many questions from individual pros who are switching to FCP X and from big companies who are adding it to their current setups now that I would say quite the opposite is happening. I think by the end of this year you will see that today we haven't even touched the surface of what FCP X will become. Best wishes, Ronny.

Ronny, Hope all is well. Curious if you had a ballpark price on the 30 simultaneous users at a major television production company you mentioned. I have a crew of 10 videographers who edit projects on individual drives. (More to come in the future) We also have a photography department that is working on developing a shared system. And rough estimates are coming in for $25 grand plus. I just know if it will run as smooth for video. Backing up is one thing, editing with AVC files in real time can definitely tie up a system.

I would love a centrally located storage system with iMacs branching from them. Any pointers in the right direction would be great.:) Best, Jason. Hey Jason, A shared system for photography work is far less performant than a professional video server. The system we set up at Metronome Productions (a division of Shine International) is a classic SAN that has been configured by one of the world's most respected video system engineers.

Actually it's not that big, just 96 TB central storage to start with, but it can be extended to 1 PetaByte. At this time 10 stations (maxed out 27 inch iMacs) are connected to the system over a 10 GigE switch for simultaneous editing (300 MB/s constant read on each client which equals approximately 16 layers of native XDCAM HD 422 50i on each client), while 24 other users can connect to it anywhere in the building over 1 GigE for previews, rough cuts and whatnot (journalists, producers, production team). The system is configured as RAID 6, which gives double redundancy. This means that even when two drives fail at the same time you still can continue to edit without any data loss while the system restores itself. For that reason you don't need a 'hot' (nearline) backup system, which is very expensive.

Scheduled backups are made over Chronosync via a MacMini that acts as a server for a bunch of Pegasus Thunderbolt enclosures that are connected as JBOD. During our stress tests we worked with 5 editors simultaneously on the same 1-hour multicam clip with 7 native MXF XDCAM 422 angles, each with 8 channels of uncompressed audio. We got near to zero latency and FCP X responded extremely fast, as if we were working with a fast attached Promise Thunderbolt RAID. This system runs on OSX Server and NFS and it is works exclusively with FCP X. The total price for the setup is under 40K, including 18 enterprise-class drives and ten 10GigE to Thunderbolt 2 interfaces (which together cost 10K by themselves).

I have asked quotations from different companies that offer 'all-in-one' shared storage solutions. All prices were much (and I mean much) higher than this classic SAN. You should know that no two shared storage systems are the same. I have seen many people who have lost lots of time and money trying to set up such a thing themselves without getting any decent speeds. The hardware actually is the less difficult part.

A detailed workflow assessment to determine exactly what you need and (most important) what you don't need, plus the assistance of a video SAN expert to remotely configure and optimize the system for your specific needs, are far more important than picking the right hardware. If you ever consider setting up a professional shared storage network for FCP X video editing I will be happy to help you work out the details. Just drop me an e-mail: ronnycourtens(at)mac(dot(com).

Best wishes, Ronny. That sounds totally bad ass Ronny! Our company has grown tremendously over the last 9 years in the wedding industry in Michigan. And I can see this as a sound investment. When we are ready to afford to go this route.we also just bought a 4000 sq ft building to house all of our photography and videography post productions. I will be sure contact you.

On a side note I can see what you're saying about having a SAN expert to help configure and optimize the system. For what I'm hearing I don't have full confidence in this individual for various reasons. I'm glad you mentioned the outline of the system. I can relate to my staff and see if it's close to what they're setting up.

Thanks again Ronny! Peter, A topic is never silly. You asked a valid question based on misinformation you got from someone who seems to be frustrated because he has missed the boat with FCP X. I agree with Christopher that the success of FCP X is also due to the fact that Apple has made its professional NLE affordable for a much larger user base (I hate the word amateurs).

But this does not mean in any way that it is used less in professional workflows, at least that is my hands-on experience. IMO the reasons why third-party effects developers each seem to sell less products to FCP X users are: 1.

FCP X already has a good number of quality effects, titles and generators included with the app. Since the introduction of X there has been a growing supply of free template effects created in Motion 5. The offer of low-priced but high-quality quality third-party effects for FCP X has never been so vast, which makes the competition in this market fierce. I do see a rapidly growing and profitable market for developers who create specialized plugins that add to the functionality of FCP X: Sync-N-Link X, ShotNotes X, Producer's Best Friend (film production); SliceX/Mocha (motion tracking); mObject (3D animation); X2Pro, 7toX, EDLX (format exchange); ClipExporter (media exchange); LUT Utility, Color Finale (advanced color correction) and so on. Many of these packages cost nearly the same price or more than FCP X itself and yet their developers seem to be very satisfied with the sales as they continuously offer updates to their products. It also shows that FCP X is quite successful in professional workflows.

That's why I have no fear whatsoever that Apple would even consider discontinuing this application, as a matter of fact I am absolutely sure of the opposite. Best wishes, Ronny.

Jason, I will be glad to offer you free advice with regard to your current shared storage plans. You or your team are welcome to send me the information you have and we will give you our objective opinion on what we think about it. I don't have any financial gains in any of this, I just hate to see people waste good money on systems or workflows that don't work as expected and then blame their software for the mistakes others have made (-: So just drop me an e-mail and I will be happy to help you. Best wishes, Ronny.