|
Enables auto-negotiating on a gigabit interface in accordance with the flow control specification 802.3x. Both sides of the circuit need to be configured with this feature.
EXAMPLE:
ServerIron(config)# int e 1 ServerIron(config-if-1)# auto-gig
Syntax: [no] auto-gig
Possible values: on or off
Default value: disabled
Specifies the maximum number of broadcast packets the device can forward each second. By default the device sends broadcasts and all other traffic at wire speed and is limited only by the capacities of the hardware. However, if other devices in the network cannot handle unlimited broadcast traffic, this command allows you to relieve those devices by throttling the broadcasts at the Foundry device.
NOTE: The broadcast limit does not affect multicast or unicast traffic. However, you can use the
multicast limit and
unknown-unicast limit commands to control these types of traffic. See "multicast limit" and "unknown-unicast limit" .
EXAMPLE:
ServerIron(config)# int e 6 ServerIron(config-if-6)# broadcast limit 30000
Syntax: broadcast limit <num>
Possible values: 0 – 4294967295
Default value: N/A
Applies the port to a TCS cache group. The port’s membership in a cache group allows client traffic received on the port to be redirected to the cache servers in the cache group.
EXAMPLE:
ServerIron(config)# int e 6 ServerIron(config-if-6)# cache-group 1
Syntax: cache-group 1
Possible values: 1
Default value: 1
Clears statistics or clears entries from a cache or table. See the descriptions for the individual clear commands in "Privileged EXEC Commands" .
This parameter assigns a defined DHCP gateway list to a specific interface on a Foundry switch. DHCP gateway lists must be defined at the Global Level and the DHCP Assist feature enabled to support assignment of this feature on switches.
NOTE: This feature is not supported on Foundry routers.
NOTE: For more details on this command and the DHCP Assist feature, see the Foundry Switch and Router Installation and Basic Configuration Guide.
EXAMPLE:
To assign a defined DHCP gateway list (1) to interface 2/5, enter the following:
ServerIron(config)# int e 2 ServerIron(config-if-2)# dhcp-gateway-list 1
Syntax: dhcp-gateway-list <number>
Possible values: N/A
Default value: N/A
Disables a specific port.
EXAMPLE:
ServerIron(config)# interface e 1 ServerIron(config-if-1)# disable
Syntax: disable
Possible values: N/A
Default value: N/A
Enables a specific port. All ports are enabled at initial startup. This command is only necessary if a port has been disabled, as all ports are by default enabled at system startup.
EXAMPLE:
ServerIron(config)# interface e 1 ServerIron(config-if-1)# enable
Syntax: enable
Possible values: N/A
Default value: All ports are enabled at system startup.
Moves activity to the privileged level from any level of the CLI with the exception of the User level.
EXAMPLE:
To move to the privileged level, enter the following:
ServerIron(config-if-5)# end ServerIron#
Syntax: end
Possible values: N/A
Default value: N/A
Moves activity up one level from the current level of the CLI. This command is available at all levels.
EXAMPLE:
To move from the interface level, back to the global level, enter the following:
ServerIron(config-if-4)# exit ServerIron(config)#
Syntax: exit
Possible values: N/A
Default value: N/A
Allows you to turn flow control (802.3x) for full-duplex ports on or off (no). Flow control is configured on, by default.
EXAMPLE:
To turn the feature off, enter the following:
ServerIron(config)# int e5 ServerIron(config-if-5)# no flow control
To turn the feature on after being turned off, enter the following:
ServerIron(config-if-5)# flow-control
Syntax: [no] flow-control
Possible values: N/A
Default value: on
Assigns a port to a firewall group.
EXAMPLE:
To assign port 5 to firewall group 2:
ServerIron(config)# int e 5 ServerIron(config-if-5)# fw-group 2
Syntax: fw-group 2
Possible values: 2
Default value: All ports are assigned to firewall group 2 by default.
Overrides the global default setting for Gigabit negotiation mode. You can configure the Gigabit negotiation mode for a port to be one of the following:
- Default – The port uses the negotiation mode that was set at the global level.
- Negotiate-full-auto – The port first tries to perform a handshake with the other port to exchange capability information. If the other port does not respond to the handshake attempt, the port uses the manually configured configuration information (or the defaults if an administrator has not set the information). This is the default for Chassis devices (including the TurboIron/8).
- Auto-Gigabit – The port tries to perform a handshake with the other port to exchange capability information. This is still the default for Stackable devices.
- Negotiation-off – The port does not try to perform a handshake. Instead, the port uses configuration information manually configured by an administrator.
See the “Configuring Basic features” chapter of the Foundry Switch and Router Installation and Basic Configuration Guide for more information.
NOTE: This command does not apply to Stackable devices. To change the negotiation mode for a Stackable Gigabit Ethernet port, use the
[no] auto-gig command at the Interface level. See "auto-gig" .
EXAMPLE:
To override the global setting and set the negotiation mode to auto-Gigabit for ports 4/1 – 4/4, enter the following commands:
ServerIron(config)# int ethernet 4/1 to 4/4 ServerIron(config-mif-4/1-4/4)# gig-default auto-gig
Syntax: gig-default neg-full-auto | auto-gig | neg-off
Possible values: see above
Default value: neg-full-auto
Applies an ACL to an interface.
EXAMPLE:
To configure a standard ACL and apply it to outgoing traffic on port 1, enter the following commands.
ServerIron(config)# access-list 1 deny host 209.157.22.26 log ServerIron(config)# access-list 1 deny 209.157.29.12 log ServerIron(config)# access-list 1 deny host IPHost1 log ServerIron(config)# access-list 1 permit any ServerIron(config)# int eth 1 ServerIron(config-if-1)# ip access-group 1 out ServerIron(config)# write memory
The commands in this example configure an ACL to deny packets from three source IP addresses from being forwarded on port 1. The last ACL entry in this ACL permits all packets that are not explicitly denied by the first three ACL entries.
Syntax: [no] ip access-group <num> in | out
The <num> parameter is the access list number and can be from 1 – 99.
EXAMPLE:
To apply an ACL to a subset of ports within a virtual interface, enter commands such as the following:
ServerIron(config)# vlan 10 name IP-subnet-vlan ServerIron(config-vlan-10)# untag ethernet 1/1 to 2/12 ServerIron(config-vlan-10)# router-interface ve 1 ServerIron(config-vlan-10)# exit ServerIron(config)# access-list 1 deny host 209.157.22.26 log ServerIron(config)# access-list 1 deny 209.157.29.12 log ServerIron(config)# access-list 1 deny host IPHost1 log ServerIron(config)# access-list 1 permit any ServerIron(config)# interface ve 1 ServerIron(config-vif-1)# ip access-group 1 in ethernet 1/1 ethernet 1/3 ethernet 2/1 to 2/4
The commands in this example configure port-based VLAN 10, add ports 1/1 – 2/12 to the VLAN, and add virtual routing interface 1 to the VLAN. The commands following the VLAN configuration commands configure ACL 1. Finally, the last two commands apply ACL 1 to a subset of the ports associated with virtual interface 1.
Syntax: [no] ip access-group <num> in ethernet <portnum> [<portnum>...] to <portnum>
Possible values: see above
Default value: N/A
Configures an IP interface for use with IP forwarding. You must configure the IP interface on a virtual routing interface. You cannot configure the interface on a physical port. See "router-interface" .
NOTE: This command applies only to Layer 3 IP interfaces for use with IP forwarding. To configure the ServerIron’s management IP address, see "ip address" .
EXAMPLE:
To add an IP interface, enter commands such as the following:
ServerIron(config)# interface ve 1 ServerIron(config-vif-1)# ip address 10.10.10.1 255.255.255.0
The interface ve 1 command changes the CLI to the configuration level for virtual routing interface 1. The ip address command adds an IP interface.
Syntax: [no] ip address | nat-address | standby-address <ip-addr> <ip-mask>
or
Syntax: [no] ip address | nat-address | standby-address <ip-addr>/<mask-bits>
The address | nat-address | standby-address parameter identifies the type of IP interface you are adding.
- The address parameter adds a standard IP interface. This option is applicable in most cases.
- The nat-address parameter applies to active-standby configurations. This parameter configures a shared IP interface for use with SLB source NAT. Enter the same command with the same IP address on each of the ServerIrons in the active-standby configuration. The address is active only on one ServerIron (the ServerIron that is currently active) at a time.
NOTE: SLB source NAT is different from standard Network Address Translation (NAT).
- The standby-address parameter applies to active-standby configurations and allows both ServerIrons to share the same router interface. One of the ServerIrons actively supports the interface while the other ServerIron provides failover for the interface if the first ServerIron becomes unavailable. Real servers can use the shared interface as their default gateway. Enter the same command with the same IP address on each of the ServerIrons in the active-standby configuration. The address is active only on one ServerIron (the ServerIron that is currently active) at a time.
The <ip-addr> parameter specifies the IP address.
The <ip-mask> parameter specifies a class-based (or “Classical”) IP sub-net mask.
The <mask-bits> parameter specifies the number of significant bits in a Classless Interdomain Routing (CIDR) sub-net mask.
You can use either format to configure the interface. For example, both the following commands are valid and produce the same result:
- ip address 10.10.10.1 255.255.255.0
- ip address 10.10.10.1/24
Possible values: See above
Default value: N/A
NOTE: This command applies to stackable ServerIron devices only.
Causes the Foundry device to drop ICMP packets when excessive numbers are encountered, as is the case when the device is the victim of a Smurf attack. This command allows you to set threshold values for ICMP packets targeted at the router and drop them when the thresholds are exceeded.
EXAMPLE:
In the following example, if the number of ICMP packets received per second exceeds 5,000, the excess packets are dropped. If the number of ICMP packets received per second exceeds 10,000, the device drops all ICMP packets for the next 300 seconds (five minutes).
ServerIron(config-if-e100-1)# ip icmp burst-normal 5000 burst-max 10000 lockup 300
Syntax: ip icmp burst-normal <value> burst-max <value> lockup <seconds>
The
burst-normal value can be from 1 – 100000.
The
burst-max value can be from 1 – 100000.
The
lockup value can be from 1 – 10000.
The number of incoming ICMP packets per second are measured and compared to the threshold values as follows:
- If the number of ICMP packets exceeds the
burst-normal value, the excess ICMP packets are dropped.
- If the number of ICMP packets exceeds the
burst-max value,
all ICMP packets are dropped for the number of seconds specified by the
lockup value. When the lockup period expires, the packet counter is reset and measurement is restarted.
Possible values: The
burst-normal and
burst-max values can be between 1 – 100000 packets. The
burst-normal value must be smaller than the
burst-max value. The
lockup value can be between 1 – 10000 seconds.
Default value: N/A
Applies Transaction Rate Limiting for ICMP traffic to an interface.
EXAMPLE:
ServerIron(config)# interface ethernet 1/1 ServerIron(config-if-1/1)# ip icmp trans-rate
Syntax: [no] ip icmp trans-rate
Possible values: N/A
Default value: N/A
Applies Transaction Rate Limiting for TCP traffic to a port on an interface.
EXAMPLE:
ServerIron(config)# interface ethernet 1/1 ServerIron(config-if-1/1)# ip tcp trans-rate 80
Syntax: ip tcp trans-rate <ports>
Possible values: The <ports> parameter specifies one or more TCP ports to monitor. You can monitor up to 4 ports.
Default value: N/A
Applies Transaction Rate Limiting for UDP traffic to a port on an interface.
EXAMPLE:
ServerIron(config)# interface ethernet 1/1 ServerIron(config-if-1/1)# ip udp trans-rate 80
Syntax: ip udp trans-rate <ports>
Possible values: The <ports> parameter specifies one or more UDP ports to monitor. You can monitor up to 4 ports.
Default value: N/A
Disables disable Internet Group Membership Protocol (IGMP) queries from being sent or received on the port.
EXAMPLE:
To disable IGMP queries on an interface, enter commands such as the following:
ServerIron(config)# int e5 ServerIron(config-if-5)# ip-multicast-disable
To re-enable the IGMP queries on the interface, enter the following command:
ServerIron(config-if-5)# no ip-multicast-disable
Syntax: [no] ip-multicast-disable
Possible values: N/A
Default value: IGMP queries are enabled.
Locally enables TCS or firewall load balancing on the interface. Use this command if you did not enable TCS or firewall load balancing globally. See "ip policy" .
NOTE: You must use the ip policy command to configure the policy before using the ip-policy command. See "ip policy" .
NOTE: This command does not configure permit and deny filters. To configure this type of filter, see "ip filter..." .
See the following for more information:
- The "Configuring Transparent Cache Switching" chapter of the Foundry ServerIron Installation and Configuration Guide
- The Foundry ServerIron Firewall Load Balancing Guide
EXAMPLE:
To enable transparent cache switching of HTTP traffic for port 18 only, as opposed to globally on all of the ports, enter the following commands:
ServerIron(config)# ip policy 2 cache tcp 80 local ServerIron(config)# int e 18 ServerIron(config-if-18)# ip-policy 2
EXAMPLE:
To enable firewall load balancing on port 9, enter the following commands:
ServerIron(config)# ip policy 3 fw tcp 0 local ServerIron(config)# ip policy 4 fw udp 0 local ServerIron(config)# int e 9 ServerIron(config-if-9)# ip-policy 3 ServerIron(config-if-9)# ip-policy 4
Syntax: ip policy <index> cache | fw | high | normal tcp | udp <tcp/udp-portnum> global | local
Syntax: ip-policy <index>
NOTE: When enabling firewall load balancing, you must specify "0" for the <tcp/udp-portnum> parameter of the ip policy command. This value allows all ports of the specified type (TCP or UDP).
Possible values: See above
Default value: N/A
Enables the Routing Information Protocol (RIP) version on a virtual routing interface.
NOTE: This command applies only to IP forwarding (Layer 3 IP).
EXAMPLE:
ServerIron(config-rip-router)# interface ve 1 ServerIron(config-vif-1)# ip rip v1-only
This command changes the CLI to the configuration level for virtual routing interface 1 and enables RIP version 1 on the interface. You must specify the version.
Syntax: [no] ip rip v1-only | v1-compatible-v2 | v2-only
Possible values: See above
Default value: Disabled; no version specified
Enables the ServerIron to learn RIP default routes.
NOTE: This command applies only to IP forwarding (Layer 3 IP).
EXAMPLE:
ServerIron(config)# interface ve 1 ServerIron(config-vif-1)# ip rip learn-default
Syntax: [no] ip rip learn-default
Possible values: N/A
Default value: Disabled
Changes the method of loop prevention that RIP uses.
NOTE: This command applies only to IP forwarding (Layer 3 IP).
RIP can use one of the following loop-prevention methods:
- Split horizon – The ServerIron does not advertise a route on the same interface as the one on which the ServerIron learned the route.
- Poison reverse – The ServerIron assigns a cost of 16 (“infinite” or “unreachable”) to a route before advertising it on the same interface as the one on which the ServerIron learned the route. This is the default.
NOTE: These methods are in addition to RIP’s maximum valid route cost of 15.
EXAMPLE:
To enable split horizon, enter commands such as the following:
ServerIron(config)# interface ve 1 ServerIron(config-vif-1)# no ip rip poison-reverse
Syntax: [no] ip rip poison-reverse
Possible values: See above
Default value: Poison reverse
NOTE: This command applies to stackable ServerIron devices only.
Causes the Foundry device to drop TCP SYN packets when excessive numbers are encountered, as is the case when the device is the victim of a TCP SYN attack. This command allows you to set threshold values for TCP SYN packets targeted at the router and drop them when the thresholds are exceeded.
EXAMPLE:
In the following example, if the number of TCP SYN packets received per second exceeds 10, the excess packets are dropped. If the number of TCP SYN packets received per second exceeds 100, the device drops all TCP SYN packets for the next 300 seconds (five minutes).
ServerIron(config)# int e 1 ServerIron(config-if-e100-1)# ip tcp burst-normal 10 burst-max 100 lockup 300
Syntax: ip tcp burst-normal <value> burst-max <value> lockup <seconds>
The
burst-normal value can be from 1 – 100000.
The
burst-max value can be from 1 – 100000.
The
lockup value can be from 1 – 10000.
The number of incoming TCP SYN packets per second are measured and compared to the threshold values as follows:
- If the number of TCP SYN packets exceeds the
burst-normal value, the excess TCP SYN packets are dropped.
- If the number of TCP SYN packets exceeds the
burst-max value,
all TCP SYN packets are dropped for the number of seconds specified by the
lockup value. When the lockup period expires, the packet counter is reset and measurement is restarted.
Possible values: The
burst-normal and
burst-max values can be between 1 – 100000 packets. The
burst-normal value must be smaller than the
burst-max value. The
lockup value can be between 1 – 10000 seconds.
Default value: N/A
Enables the SYN-Guard feature on individual ports on ServerIron Chassis devices. This feature can be applied to inbound SYN requests (for Web site traffic) and/or outbound SYN requests (for ISP and institution outgoing traffic).
EXAMPLE:
To use the SYN-Guard feature for inbound SYN requests on interface 3/1:
ServerIron(config)# interface e 3/1 ServerIron(config-if-3/1)# ip tcp syn-proxy in
Syntax: ip tcp syn-proxy in | out
When applied to inbound SYN requests, the SYN-Guard feature can be used with all ServerIron features, including TCS, FWLB, and SLB. However, when applied to outbound SYN requests, the SYN-Guard feature is the only process that can act on the packet.
Possible values: N/A
Default value: N/A
This command allows you to modify the inter-packet gap (delay) between packets on a 10Mbps Ethernet segment. By default, the delay between packets will be 12 bytes or 9.6 microseconds.
Use this command only to adjust the inter-packet gap to match older adapters that do not meet the default IPG requirements for Ethernet.
In determining the value to enter in the CLI command, note that one byte equals.8 microseconds for packets on a 10Mbps segment, so the following equation can be used:
IPG10 = 9.6 microseconds + (value *.8), where value is the number of bytes by which you want to increase the inter-packet gap.
EXAMPLE:
To increase the delay between packets by 3.2 microseconds, enter the port to be modified and then enter the value of 4 (4*.8 =3.2 microseconds).
ServerIron(config)# int e 4 ServerIron(config-if-4)# ipg10 4
Syntax: ipg10 <value>
Possible values: 0 – 100 bytes
Default value: 12 bytes or ipg10 0
NOTE: Entering the value of 0 within the ipg10, ipg100, and ipg1000 commands restore the inter-packet gap (IPG) to the default of 12 bytes.
This command allows you to modify the inter-packet gap (delay) between packets on a 100Mbps Ethernet segment on a port-by-port basis. By default, the delay between packets will be 12 bytes or 0.96 microseconds.
Use this command only to adjust the inter-packet gap to match that of older adapters that do not meet the default IPG requirements for Fast Ethernet.
In determining the value to enter in the CLI command, note that one byte equals.08 microseconds for packets on a 100Mbps segment, so the following equation can be used:
IPG100 = 0.96 microseconds + (value *.08), where value is the number of bytes by which you want to increase the inter-packet gap.
EXAMPLE:
To increase the delay between packets by 3.2 microseconds, enter the port to be modified and then enter the value of 40(40*.08 =3.2 microseconds)
ServerIron(config)# int e 3 ServerIron(config-if-3)# ipg100 40
Syntax: ipg100 <value>
Possible values: 0 – 100
Default value: 12 bytes or ipg100 0
This command allows you to modify the inter-packet gap (delay) between packets on a 1000Mbps Gigabit Ethernet segment on a port-by-port basis. By default, the delay between packets will be 12 bytes or.096 microseconds.
Use this command only to adjust the inter-packet gap to match that of older adapters that do not meet the default IPG requirements for Gigabit Ethernet.
In determining the value to enter in the CLI command, note that one byte equals.008 microseconds for packets on a 1000Mbps segment, so the following equation can be used:
IPG1000 =.096 microseconds + (value *.008), where value is the number of bytes by which you want to increase the inter-packet gap.
EXAMPLE:
To increase the delay between packets by.32 microseconds, first enter the port to be modified and then enter the value of 40(40*.008 =.32 microseconds)
ServerIron(config)# int e 3 ServerIron(config-if-3)# ipg1000 40
Syntax: ipg1000 <value>
Possible values: 1 – 100
Default value: 12 bytes or ipg1000 0
Applies a group of MAC filters to an interface. You can configure one filter group on each interface.
NOTE: You must define the filters at the global CONFIG level using the
mac filter command (see "mac filter" ) before you can apply them in a filter group.
NOTE: The filters must be applied as a group. For example, if you want to apply four filters to an interface, they must all appear on the same command line.
NOTE: You cannot add or remove individual filters in the group. To add or remove a filter on an interface, apply the filter group again containing all the filters you want to apply to the port.
NOTE: If you apply a filter group to a port that already has a filter group applied, the older filter group is replaced by the new filter group.
EXAMPLE:
To apply MAC filters 1, 2, 3, and 1024 to interface 6, enter the following command:
ServerIron(config)# int e 6 ServerIron(config-if-6)# mac filter-group 1 2 3 1024
Syntax: mac-filter-group <filter-list>
Possible values: 1 – 1024
Default value: N/A
This allows you to select a port to be diagnosed by a designated mirror port. You can configure incoming, outgoing or both incoming and outgoing traffic to be monitored on the port.
EXAMPLE:
To monitor both incoming and outgoing traffic on interface 5:
ServerIron(config)# interface e5 ServerIron(config-if-5)# monitor both
Syntax: monitor input | output | both
Possible values: N/A
Default value: Disabled
Specifies the maximum number of multicast packets the device can forward each second. By default the device sends multicasts and all other traffic at wire speed and is limited only by the capacities of the hardware. However, if other devices in the network cannot handle unlimited multicast traffic, this command allows you to relieve those devices by throttling the multicasts at the Foundry device.
NOTE: The multicast limit does not affect broadcast or unicast traffic. However, you can use the
broadcast limit and
unknown-unicast limit commands to control these types of traffic. See "broadcast limit" and "unknown-unicast limit" .
EXAMPLE:
ServerIron(config)# interface e5 ServerIron(config-if-5)# multicast limit 30000
Syntax: multicast limit <num>
Possible values: 0 – 4294967295
Default value: N/A
Overrides the default negotiation mode for a Gigabit port on Chassis devices. When you invoke this command, the port does not try to perform a handshake. Instead, the port uses configuration information manually configured by an administrator.
EXAMPLE:
To change the negotiation mode for the port to negotiation-off:
ServerIron(config)# int e3 ServerIron(config-if-3)# neg-off
Syntax: neg-off
Possible values: N/A
Default value: N/A
This command disables other commands. To disable a command, place the word
no before the command.
If a port on a ServerIron is to be attached to a Bay Networks 28000 switch, enter this command at the Interface Level as shown below.
This command helps the ServerIron to adjust to interoperability requirements of the 28000.
EXAMPLE:
ServerIron(config)# int e3 ServerIron(config-if-3)# phy-mode 28k
Syntax: phy-mode 28k
Possible values: 28k
Default value: Option is turned off.
Assignment of a name to an interface provides additional identification for a segment on the network.
EXAMPLE:
ServerIron(config)# interface e 1 ServerIron(config-if-1)# port-name marketing-funk
Syntax: port-name <text>
Possible values: N/A
Default value: N/A
Statically enables support for Cisco Systems’ Per VLAN Spanning Tree (PVST).
PVST/PVST+ support is automatically enabled on a port if the port receives a BPDU in PVST/PVST+ format. However, you can statically enable PVST/PVST+ support on a port if desired. In this case, the support is enabled immediately and support for Foundry tagged BPDUs is disabled at the same time.
NOTE: When PVST/PVST+ support is enabled on a port, support for Foundry BPDUs is disabled.
For more information, see the "Configuring Spanning Tree Protocol (STP) and IronSpan" chapter in the Foundry Switch and Router Installation and Basic Configuration Guide.
EXAMPLE:
To enable PVST/PVST+ support on a port, enter commands such as the following:
ServerIron(config)# interface ethernet 1/1 ServerIron(config-if-1/1)# pvst-mode
Syntax: [no] pvst-mode
NOTE: If you disable PVST/PVST+ support, the software still automatically enables PVST/PVST+ support if the port receives an STP BPDU with PVST/PVST+ format.
Possible values: N/A
Default value: Enabled automatically when a PVST/PVST+ BPDU is received on the port
Sets the Quality-of-Service (QoS) priority level for a port, VLAN, static MAC address, or Layer 4 session. You can select the normal queue or the high-priority queue. All traffic is in the normal queue by default. When you allocate a port, VLAN, static MAC address, or Layer 4 session to the high-priority queue, all traffic queued up for that item is processed before any traffic in the normal queue for the same item is processed.
QoS applies to outbound traffic only.
EXAMPLE:
To allocate port 6 traffic to the high-priority queue, enter the following command:
ServerIron(config)# interface e 6 ServerIron(config-if-6)# qos-priority high
Syntax: qos-priority normal | high
Possible values: normal or high
Default value: normal
This command returns you from any level of the CLI to the User EXEC mode.
EXAMPLE:
ServerIron(config-if-6)# quit ServerIron>
Syntax: quit
Possible values: N/A
Default value: N/A
Displays the real and virtual server configuration information on a remote site ServerIron in the GSLB ServerIron’s CLI. The command also displays the session and CPU information used by the GSLB policy. You can view detailed configuration information and statistics for the site ServerIron, from the GSLB ServerIron’s management console. For more information, see the "Configuring Global Server Load Balancing" chapter in the Foundry ServerIron Installation and Configuration Guide.
Displays a variety of configuration and statistical information about the ServerIron. To see a description of the show commands, see "Show Commands" .
Spanning tree can be disabled or enabled on an interface basis.
EXAMPLE:
To disable spanning tree on physical port 4 of a system with no VLANs operating, enter the following:
ServerIron(config)# interface ethernet 4 ServerIron(config-if-4) no spanning-tree
EXAMPLE:
To disable spanning tree on physical port 4 of a system within VLAN 2, enter the following:
ServerIron(config)# vlan 2 ServerIron(config-vlan-2) no spanning-tree
Syntax: spanning-tree
Possible values: N/A
Default value: Disabled
Modifies port speed and duplex. It defines the speed and duplex mode for a 10BaseT and 100BaseTx ports.
Gigabit (1000BaseSx and 1000BaseLx) and 100BaseFx ports operate at a fixed speed and mode (full-duplex) and cannot be modified.
EXAMPLE:
ServerIron(config)# interface e8 ServerIron(config-if-8)# speed-duplex 10-full
Syntax: speed-duplex <value>
Possible values: 10-full, 10-half, 100-full, 100-half, auto
Default value: 10/100 autosense
Specifies the maximum number of unknown-unicast packets the device can forward each second. By default the device sends unknown unicasts and all other traffic at wire speed and is limited only by the capacities of the hardware. However, if other devices in the network cannot handle unlimited unknown-unicast traffic, this command allows you to relieve those devices by throttling the unknown unicasts at the Foundry device.
NOTE: The unknown-unicast limit does not affect broadcast or multicast traffic. However, you can use the
broadcast limit and
multicast limit commands to control these types of traffic. See "broadcast limit" and "multicast limit" .
EXAMPLE:
ServerIron(config)# interface e8 ServerIron(config-if-8)# unknown-unicast limit 30000
Syntax: unknown-unicast limit <num>
Possible values: 0 – 4294967295
Default value: N/A
Saves the running-time configuration into the startup-config file.
EXAMPLE:
ServerIron(config-if-8)# write memory
Syntax: write memory
Possible values: N/A
Default value: N/A
Displays the running-configuration of the ServerIron on the terminal screen.
EXAMPLE:
ServerIron(config-if-8)# write terminal
Syntax: write terminal
Possible values: N/A
Default value: N/A
|