7.8.1.0 - Force10 Networks

Figure 208 shows how the show config command displays an example of a Layer 3 interface.
Figure 208 show config Command Example of a Layer 3 Interface
Force10(conf-if)#show config
!
interface GigabitEthernet 1/5
ip address 10.10.10.1 /24
no shutdown
Force10(conf-if)#
If an interface is in the incorrect layer mode for a given command, an error message is displayed to the
user. For example, in Figure 209, the command ip address triggered an error message because the
interface is in Layer 2 mode and the ip address command is a Layer 3 command only.
Figure 209 Error Message When Trying to Add an IP Address to Layer 2 Interface
Force10(conf-if)#show config
!
interface GigabitEthernet 1/2
no ip address
switchport
no shutdown
Force10(conf-if)#ip address 10.10.1.1 /24
% Error: Port is in Layer 2 mode Gi 1/2.
Force10(conf-if)#
Error message
To determine the configuration of an interface, you can use the show config command in INTERFACE
mode or the various show interface commands in EXEC mode.
Physical Interfaces
The Management Ethernet interface, is a single RJ-45 Fast Ethernet port on the Route Processor Module
(RPM) of the C-Series and E-Series, and provides dedicated management access to the system. The
S-Series systems supported by FTOS do not have this dedicated management interface, but you can use
any Ethernet port configured with an IP address and route.
Line card interfaces support Layer 2 and Layer 3 traffic over the 10/100/1000, Gigabit, and 10-Gigabit
Ethernet interfaces. SONET interfaces with PPP encapsulation support Layer 3 traffic. These interfaces
(except SONET interfaces with PPP encapsulation) can also become part of virtual interfaces such as
VLANs or port channels.
For more information on VLANs, see Bulk Configuration on page 365 and for more information on port
channels, see Port Channel Interfaces on page 354.
FTOS Behavior: S-Series systems use a single MAC address for all physical interfaces while
E-Series and C-Series use a unique MAC address for each physical interface, though this results in no
functional difference between these platforms.
346 Interfaces