> Ethernet Port Configuration Mode Commands
> The Ethernet Port Configuration Mode is used to create and manage Ethernet ports and their bindings between contexts.
> bind interface
> Configures an association (binds) between a virtual IP interface, an SS7 or Frame Relay link to a specific context.
> Product
> All
> Privilege
> Security Administrator, Administrator
> Syntax
> [ no ] bind interface interface_name context_name
> no
> Indicates the virtual interface specified is to be unbound from the context.
> interface_name
> Specifies the name of the virtual interface to be bound to the context. interface_name must be from 1 to 79 alphanumeric characters.
> context_name
> Specifies the name of the context to be bound to the virtual port. context_name must refer to a previously configured context.
> Usage
> Bind an interface to a context to allow the context to provide service.
> Example
> bind interface sampleVirtual sampleContext
> no bind interface sampleVirtual sampleContext
> default
> Restores the port’s default speed and communication mode.
> Product
> All
> Privilege
> Security Administrator, Administrator
> Syntax
> default { medium | preferred slot | threshold { value } }
> medium
> Restores the default values for the medium options as follows:

> • | SPIO and fast ethernet line cards: auto

> • | Gigabit ethernet line card: auto

> preferred slot
> Sets the port for non-revertive operation for port redundancy auto-recovery; requiring an administrative user to manually issue a port switch to command to return service to the original port.
> threshold { value }
> Restores the specified port-level threshold parameter to its default value(s). The possible values are:

> • | high-activity: High port activity threshold settings

> • | monitoring: Threshold monitoring configuration settings

> • | rx-utilization: Receive port utilization threshold settings

> • | tx-utilization: Transmit port utilization threshold settings

> Usage
> Restores port-level parameters to their default values.
> Example
> default medium
> description
> Sets the port descriptive text.
> Product
> All
> Privilege
> Security Administrator, Administrator
> Syntax
> description text
> no description
> no
> Clears the description for the port.
> text
> Specifies the descriptive text to use. text must be 1 to 79 alphanumeric characters with no spaces or a quoted string using printable characters.
> Usage
> The description should provide useful information on the port’s primary function, services, end users, etc.
> Example
> description samplePortDescriptiveText
> description “This is a sample description”
> end
> Exits the port configuration mode and returns to the Exec mode.
> Product
> All
> Privilege
> Security Administrator, Administrator
> Syntax
> end
> Usage
> Change the mode back to the Exec mode.
> exit
> Exits the port configuration mode and returns to the global configuration mode.
> Product
> All
> Privilege
> Security Administrator, Administrator
> Syntax
> exit
> Usage
> Return to the global configuration mode.
> flow-control
> Enables and disables flow control on the Quad Gig-E line card (QGLC).
> Product
> PDSN, SGSN, GGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> [ no ] flow-control
> no flow-control
> Disables flow control on the specified port
> Usage
> Flow control is enabled by default on the QGLC and can be disabled using the no command on a per-port basis. This command does not work on the Fast Ethernet Line Card (FELC), Gigabit Ethernet Line Card (GELC/GLC2) or 10 GigE Line Card (XGLC) which do not support flow control.
> Example
> After flow control has been disabled, use the following command to enable flow control:
> flow-control
> ingress-mode
> Labels this port as an ingress port.
> Product
> IPSG
> Privilege
> Security Administrator, Administrator
> Syntax
> [ no ] ingress-mode
> no
> Disables ingress port tag.
> Usage
> Use this command to label this port in order for the session manager to recognize the interface from which IP data packets are being received. This command should be used in single context configurations. In single context configurations, the ingress port can only be identified if labeled.
> link-aggregation
> Used to aggregate ports on a Quad Gig-E line card (QGLC) or 10 Gig-E line card (XGLC) and set related parameters in accordance IEEE 802.3ad.
> Product
> WiMAX, PDSN, HA, FA, GGSN, SGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> link-aggregation { distribution { block | random | rotate | simple } | lacp { active | passive } [ rate { auto | fast | slow } ] [ timeout { long | short } ] | master { global group group_number | group group_number | local group group_number } | member { global group group_number | group group_number | local group group_number } | redundancy { standard | switched } [ hold-time sec ] [ preferred slot { card_number | none } ] | toggle-link }
> no link-aggregation [ toggle-link ]
> default link-aggregation { distribution | lacp | redundancy | toggle-link }
> distribution { block | random | rotate | simple }
> Configures link aggregation distribution and controls how a Link Aggregation Group (LAG) hash map is generated. This method is required for Equal Cost Multi-Path (ECMP) routing over LAG. Set this option on the master port for use with the whole group. The following list defines the distribution options (assuming port index 0,1,2,3 were selected.
> block: Blocks of the same port index (Example: 0000111122223333)
> random: Based on pseudo random number
> rotate: Repetition of rotated port index (Example: 0123123023013012…)
> simple: Repetition of all selected port indexes (Example: 0123012301230123…)
> lacp { active | passive }
> Configures the Link Aggregation Control Protocol (LACP). Set this option on the master port for use with the whole group.
> active mode sends out LACP packets periodically. (Default)
> passive mode only responds to LACP packets received.
> rate { auto | fast | slow }
> Configures the rate at which the LACP sends packets.
> auto: rate is controlled by the peer
> fast: 1 seconds
> slow: 30 seconds (Default)
> timeout { long | short }
> Configures LACP timeout events. Set this option on the master port for use with the whole group.
> long: Set LACP to long timeout
> short: Set LACP to short timeout
> master { global group group_number | group group_number | local group group_number }
> This command creates the Master port for the aggregated group.
> global: Set group global across slots.
> group group_number: Set link aggregation group number. group_number must be an integer between 1 and 1023.
> local: Set group local within same slot.
> member { global group group_number | group group_number | local group group_number }
> This command makes the port a member of the aggregated group.
> global: Set group global across slots.
> group group_number: Set link aggregation group number. group_number must be an integer between 1 and 1023.
> local: Set group local within same slot.
> redundancy { standard | switched } [ hold-time sec ] [ preferred slot { card_number | none } ]
> Connects top and bottom QGLCs and side-by-side XGLCs to different switches. The master port must be set to make this effective for the group.
> standard: Treats all cards in the group as one group. (Default)
> switched: Assumes cards are connected to different switches.
> hold-time sec: Sets the amount of time to hold, in seconds, before switching between cards. Applies to standard and switched modes. sec must be an integer from 0 to 3600. Default: 10
> preferred slot: Specifies revertive/non-revertive preference including preferred slot for standard LAG for two switches. Applies to standard and switched modes.
> slot: Specifies which slot to prefer for revertive mode (or none).
> card_number: Specifies a card number and must be an integer between 1 and 48.
> none: Specifies no preferred slot.
> toggle-link
> Set to toggle link on port switch.
> default
> Restores the default values.
> no
> This command deletes the Ethernet port from any group it might be in. If the port was the Master of a group, the whole group would be deleted.
> Usage
> Configure from one to four ports on a QGLC (vertical aggregation) or the single port on XGLCs (horizontal aggregation) to be in an aggregation group on the chassis that links to an aggregation group on a remote switch. Very large files can be downloaded across all ports in a group, which makes for a faster download when compared to serial downloads over a single link. For additional information, refer to the System Administration Guide.
> Example
> The following example configures the port to be the Master for Group 2:
> link aggregation master group 2
> media
> Configures the port interface type.
> Product
> All
> Privilege
> Security Administrator, Administrator
> Syntax
> media { rj45 | sfp }
> rj45 | sfp
> rj45: sets the physical interface to copper RJ-45 connectors.
> sfp: sets the physical interface connection to optical Small Form Factor (SFP) gigabit via an SFP transceiver.
> Usage
> Set the media option when the physical cabling interface is changed.
> Example
> The following commands are entered one-at-a-time to set the physical interface to RJ-45 and SFP:
> media rj45
> media sfp
> medium
> Configures the port speed and communication mode.
> Product
> All
> Privilege
> Security Administrator, Administrator
> Syntax
> medium { auto | speed { 10 | 100 | 1000 | 10000 } duplex { full | half } }
> auto | speed { 10 | 100 | 1000 | 10000 } duplex { full | half }
> Default: auto
> Optionally sets the speed of the interface and the communication mode.
> auto: configures the interface to auto negotiate the interface speed.
> speed { 10 | 100 | 1000 | 10000 }: specifies the speed to use at all times.
> duplex { full | half }: sets the communication mode of the interface to either full or half duplex.
> Important: Ethernet networking rules dictate that if a device whose interface is configured to auto-negotiate is communicating with a device that is manually configured to support full duplex, the first device will negotiate to the manually configured speed of the second device but will only communicate in half duplex mode.
> Usage
> Set the medium options when the physical interface changes.
> Example
> The following configures the port’s speed and communication mode to be auto negotiated.
> medium auto
> The following command configures the port’s interface speed to gigabit with full duplex communication.
> medium speed 1000 duplex full
> preferred slot
> Assigns revertive or non-revertive control to port redundancy auto-recovery.
> Default: non-revertive operation
> Product
> PDSN, FA, HA, SGSN, GGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> [ no ] preferred slot slot#
> no
> Disables revertive, or auto-recovery, operation for selected port.
> slot#
> Identifies the physical chassis slot where the line card or SPIO card is installed.
> Usage
> This command enables or disables revertive port redundancy, wherein after a port failover, when the original port is restored to service (such as link up) the system will return service to that port automatically.
> Disabled, which is the default setting, causes non-revertive operation; requiring an administrative user to manually issue a port switch to command to return service to the original port.
> This command must be issued on a per port basis, allowing you to configure specific ports to be used on individual LCs or SPIO cards. For example, ports 1 through 4 could be configured as “preferred” on the LC in slot 17 while ports 5 through 8 are “preferred” on the LC in slot 33. In this scenario, both LCs would be in an Active operational state while still providing LC and port redundancy for the other.
> Important: This command is not supported on all platforms.
> Example
> preferred slot 17
> shutdown
> Terminates all processes supporting the port or blocks the shutting down of the port. Conversely, the port is enabled with the use of the no keyword.
> Product
> All
> Privilege
> Security Administrator, Administrator
> Syntax
> [ no ] shutdown
> no
> Enables the port. When omitted the card is shutdown (removed from service).
> Usage
> Shut down a port prior to re-cabling and/or other maintenance activities.
> This command is necessary to bring a port into service by enabling it via the no keyword.
> Example
> Use the following command to disable the port:
> shutdown
> Use the following command to enable the port for service:
> no shutdown
> snmp trap link-status
> Enables/disables the generation of an SNMP trap for link status changes.
> Product
> All
> Privilege
> Security Administrator, Administrator
> Syntax
> [ no ] snmp trap link-status
> no
> Disables the sending of traps for link status changes.
> Usage
> Enable link status change traps when a monitoring facility can use the information or if there are trouble shooting activities are in progress.
> Example
> Use the following command to disable sending of traps:
> no snmp trap link-status
> srp virtual-mac-address
> Configures the Standby Router Protocol (SRP) virtual MAC address for the port.
> Product
> All
> Privilege
> Security Administrator, Administrator
> Syntax
> srp virtual-mac-address MAC_Address
> no srp virtual-mac-address
> no
> Disables the SRP virtual MAC addressing for Ethernet ports. The block of virtual MAC addresses is not saved.
> Usage
> The SRP virtual MAC address is applied to the port when the chassis is in SRP ACTIVE state. The default is no srp virtual-mac-address.
> Important: This command is not supported on all platforms.
> Example
> Use the following command to enable the SRP’s virtual MAC addressing:
> srp virtual-mac-address MAC_Address
> threshold high-activity
> Configures thresholds for high port activity for the port.
> Product
> All
> Privilege
> Security Administrator, Administrator
> Syntax
> threshold high-activity high_thresh [ clear low_thresh ]
> high_thresh
> Default: 50
> The high threshold high port activity percentage that must be met or exceeded within the polling interval to generate an alert or alarm.
> high_thresh can be configured to any integer value between 0 and 100.
> clear
> Allows the configuration of the low threshold.
> low_thresh
> Default: 50
> The low threshold high port activity percentage that maintains a previously generated alarm condition. If the activity percentage falls below the low threshold within the polling interval, a clear alarm will be generated.
> low_thresh can be configured to any integer value between 0 and 100.
> Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.
> Usage
> High port activity thresholds generate alerts or alarms based on the utilization percentage of each configured port during the specified polling interval. This threshold is configured on a per-port basis.
> Alerts or alarms are triggered for high port activity based on the following rules:

> • | Enter condition: Actual percent utilization of a port is greater than High Threshold

> • | Clear condition: Actual percent utilization of a port is less than Low Threshold

> If a trigger condition occurs within the polling interval, the alert or alarm will not be generated until the end of the polling interval.
> Refer to the threshold poll command in the Global Configuration Mode Commands chapter of this reference to configure the polling interval and the threshold monitoring command in this chapter to enable thresholding for this value.
> Example
> The following command configures a high port utilization threshold percent of 70 and a low threshold percent of 50 for a system using the Alarm thresholding model:
> threshold high-activity 70 clear 50
> threshold monitoring
> Enables thresholding for port-level values.
> Product
> All
> Privilege
> Security Administrator, Administrator
> Syntax
> [ no ] threshold monitoring
> no
> Disables threshold monitoring for port-level values. This is the default setting.
> Usage
> Thresholding on the system is used to monitor the system for conditions that could potentially cause errors or outage. Typically, these conditions are temporary (such as high-activity) and are quickly resolved. However, continuous or large numbers of these error conditions within a specific time interval may be indicative of larger, more severe issues. Thresholding helps identify potentially severe conditions so that immediate action can be taken to minimize and/or avoid system downtime.
> Thresholding reports conditions using one of the following mechanisms:

> • | SNMP traps: SNMP traps have been created that indicate the condition (high threshold crossing and/or clear) of each of the monitored values. Complete descriptions and other information pertaining to these traps is located in the starentMIB(8164).starentTraps(2) section of the SNMP MIB Reference.

> The generation of specific traps can be enabled or disabled on the system allowing you to view only those traps that are most important to you.

> • | Logs: The system provides a facility called threshold for which active and event logs can be generated. As with other system facilities, logs are generated Log messages pertaining to the condition of a monitored value are generated with a severity level of WARNING.

> • | Alarm System: High threshold alarms generated within the specified polling interval are considered “outstanding” until a the condition no longer exists and/or a condition clear alarm is generated.

> “Outstanding” alarms are reported to through the system’s alarm subsystem and are viewable through the system’s CLI.
> The following table indicates the reporting mechanisms supported by each of the above models.
> Thresholding Reporting Mechanisms by Model

> Model | SNMP Traps | Logs | Alarm System
> Alert | X | X |
> Alarm | X | X | X

> ‌
> This command enables thresholding for port-level values. Refer to the threshold high-activity, threshold rx-utilization, and threshold tx-utilization commands in this chapter for information on configuring these values. In addition refer to the threshold poll command in the Global Configuration Mode Commands chapter of this reference for information on configuring the polling interval over which these values are monitored.
> threshold rx-utilization
> Configures thresholds for receive port utilization.
> Product
> All
> Privilege
> Security Administrator, Administrator
> Syntax
> threshold rx-utilization high_thresh [ clear low_thresh ]
> high_thresh
> Default: 80
> The high threshold receive port utilization percentage that must be met or exceeded within the polling interval to generate an alert or alarm.
> The percentage can be configured to any integer value between 0 and 100.
> clear
> Allows the configuration of the low threshold.
> low_thresh
> Default: 80
> The low threshold receive port utilization percentage that maintains a previously generated alarm condition. If the utilization percentage falls below the low threshold within the polling interval, a Clear Alarm will be generated.
> The percentage can be configured to any integer value between 0 and 100.
> Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.
> Usage
> Receive port utilization thresholds generate alerts or alarms based on the utilization percentage of each configured port in relation to data received during the specified polling interval. This threshold is configured on a per-port basis.
> Important: Ports configured for half-duplex do not differentiate between data received and data transmitted. Therefore, to avoid redundant alarms, it is recommended that only the receive or transmit utilization threshold be configured.
> Alerts or alarms are triggered for receive port utilization based on the following rules:

> • | Enter condition: Actual percent utilization of a port for received data is greater than High Threshold

> • | Clear condition: Actual percent utilization of a port for received data is less than Low Threshold

> If a trigger condition occurs within the polling interval, the alert or alarm will not be generated until the end of the polling interval.
> Refer to the threshold poll command in the Global Configuration Mode Commands chapter of this reference to configure the polling interval and the threshold monitoring command in this chapter to enable thresholding for this value.
> Example
> The following command configures a receive port high utilization threshold percent of 70 and a low threshold percent of 50 for an system using the Alarm thresholding model:
> threshold rx-utilization 70 clear 50
> threshold tx-utilization
> Configures thresholds for transmit port utilization.
> Product
> All
> Privilege
> Security Administrator, Administrator
> Syntax
> threshold tx-utilization high_thresh [ clear low_thresh ]
> high_thresh
> Default: 80
> The high threshold transmit port utilization percentage that must be met or exceeded within the polling interval to generate an alert or alarm.
> The percentage can be configured to any integer value between 0 and 100.
> clear
> Allows the configuration of the low threshold.
> low_thresh
> Default: 80
> The low threshold transmit port utilization percentage that maintains a previously generated alarm condition. If the utilization percentage falls below the low threshold within the polling interval, a clear alarm will be generated.
> The percentage can be configured to any integer value between 0 and 100.
> Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.
> Usage
> Transmit port utilization thresholds generate alerts or alarms based on the utilization percentage of each configured port in relation to data transmitted during the specified polling interval. This threshold is configured on a per-port basis.
> Important: Ports configured for half-duplex do not differentiate between data received and data transmitted. Therefore, to avoid redundant alarms, it is recommended that only the receive or transmit utilization threshold be configured.
> Alerts or alarms are triggered for transmit port utilization based on the following rules:

> • | Enter condition: Actual percent utilization of a port for transmit data is greater than High Threshold

> • | Clear condition: Actual percent utilization of a port for transmit data is less than Low Threshold

> If a trigger condition occurs within the polling interval, the alert or alarm will not be generated until the end of the polling interval.
> Refer to the threshold poll command in the Global Configuration Mode Commands chapter of this reference to configure the polling interval and the threshold monitoring command in this chapter to enable thresholding for this value.
> Example
> The following command configures a transmit port high utilization threshold percent of 70 and a low threshold of 50 for an system using the Alarm thresholding model:
> threshold tx-utilization 70 clear 50
> vlan
> Creates/deletes a VLAN tag and enters VLAN configuration mode.
> Product
> All
> Privilege
> Security Administrator, Administrator
> Syntax
> vlan tag [ inline-process ] [ subscriber-vlan ] [ -noconfirm ]
> no vlan tag
> no
> Deletes the VLAN with the specified tag.
> tag
> A tag that you specify to identify the VLAN. The tag must be unique and not used by any other VLANs on any other ports in the system. tag must be an integer from 1 through 4095.
> inline-process
> Do not use this keyword. This is a restricted keyword. It sets this VLAN for special processing for packets received from an external inline server.
> subscriber-vlan
> Designates the VLAN type as a subscriber VLAN. This keyword must be specified if the VLAN is to be associated with specific subscribers. Refer to the ip vlan command in the Subscriber Configuration Mode chapter of this reference for additional information on Subscriber-VLAN associations.
> Important: To maintain optimal performance, this keyword should not be specified for VLANs that are not to be associated with subscribers.
> -noconfirm
> Indicates that the command is to execute without any additional prompt and confirmation from the user.
> Usage
> Virtual LANs (VLANs) provide greater flexibility in the configuration and use of contexts and services.
> They are configured as “tags” on a per-port basis and allow more complex configurations to be implemented. The VLAN tag allows a single physical port to be bound to multiple logical interfaces that can be configured in different contexts. Therefore, each Ethernet port can be viewed as containing many logical ports when VLAN tags are employed.
> Important: VLANs are supported in conjunction with ports on the Ethernet 10/100 and Ethernet 1000 line cards, as well as on the four-port Quad Gig-E Line Card (QGLC) and the single port 10 GigE Line Card (XGLC). (VLAN tagging is not supported for SPIO ports.) The system supports the configuration of VLANs as follows:
> Important: Ethernet 1000 Line Card/QGLC: 1024 VLANs per card. QGLC supports 511 VLANs per port.
> Important: Ethernet 10/100 Line Card: Maximum of 256 VLANs per port and a maximum of 1016 VLANs per Line Card. (VLANs on all the ports of a single 10/100 Line Card can not add up to more than 1016.)
> Important: In order to change the type (using/removing the subscriber-vlan keyword) for VLANs that are already configured, the VLAN must first be deleted and then reconfigured as desired.
> Example
> The following example creates a VLAN and assign it the tag of 100:
> vlan 100

Cisco Systems Inc.
Tel: 408-526-4000
Fax: 408-527-0883