Packet Tracer - can't assign IP address to switch fastethernet 0/1
SurferdudeHB
Member Posts: 199 ■■■□□□□□□□
in CCNA & CCENT
can someone tell me what I'm doing wrong here. Why can't assign the IP address to interface fastethernet 0/1
THis is for a 2950-24 switch in Packet Tracer
switch01(config)#interface vlan 1
switch01(config-if)#ip address 192.168.1.5 255.255.255.0
switch01(config-if)#no shutdown
switch01(config-if)#
%LINK-5-CHANGED: Interface Vlan1, changed state to up
switch01(config-if)#interface fast 0/1
switch01(config-if)#ip address 192.168.1.1 255.255.255.0
^
% Invalid input detected at '^' marker.
THis is for a 2950-24 switch in Packet Tracer
switch01(config)#interface vlan 1
switch01(config-if)#ip address 192.168.1.5 255.255.255.0
switch01(config-if)#no shutdown
switch01(config-if)#
%LINK-5-CHANGED: Interface Vlan1, changed state to up
switch01(config-if)#interface fast 0/1
switch01(config-if)#ip address 192.168.1.1 255.255.255.0
^
% Invalid input detected at '^' marker.
Comments
-
mikeybinec Member Posts: 484 ■■■□□□□□□□SurferdudeHB wrote: »can someone tell me what I'm doing wrong here. Why can't assign the IP address to interface fastethernet 0/1
THis is for a 2950-24 switch in Packet Tracer
switch01(config)#interface vlan 1
switch01(config-if)#ip address 192.168.1.5 255.255.255.0
switch01(config-if)#no shutdown
switch01(config-if)#
%LINK-5-CHANGED: Interface Vlan1, changed state to up
switch01(config-if)#interface fast 0/1
switch01(config-if)#ip address 192.168.1.1 255.255.255.0
^
% Invalid input detected at '^' marker.
You cant' assign an IP address to a Layer 2 switchport.. Maybe you're thinking router?Cisco NetAcad Cuyamaca College
A.S. LAN Management 2010 Grossmont College
B.S. I.T. Management 2013 National University -
OfWolfAndMan Member Posts: 923 ■■■■□□□□□□You can do it if it's a chassis switch (4006, 6509) by typing in no switchport, but you won't find that in packet tracer. Routers and L2 switches serve two completely different purposes:study:Reading: Lab Books, Ansible Documentation, Python Cookbook 2018 Goals: More Ansible/Python work for Automation, IPSpace Automation Course [X], Build Jenkins Framework for Network Automation []
-
binaryhat Member Posts: 129Think:
Switch = Layer 2 = MAC Address
Router = Layer 3 = IP Address
However a switch can be assigned an administrative IP Address via a vlan interface.Currently working on:
ICND1 - TBD
Book: CCENT/CCNA ICND1 100-101 Official Cert Guide
Equipment: Packet Tracer, GNS3
Supplement Material: Youtube, Google, Boson ExamSim-Max, CBTNuggets -
OfWolfAndMan Member Posts: 923 ■■■■□□□□□□Think:
Switch = Layer 2 = MAC Address
Router = Layer 3 = IP Address
However a switch can be assigned an administrative IP Address via a vlan interface.
Correct. This is primarily for remote management. One of the biggest things between a L2 and L3 switch is that on L2 switches, you have to configure subinterfaces on an attached router for intervlan routing. On a L3 switch, you can use SVIs to define the address pool for each VLAN (After enabling IP routing) so then you don't even need a router to route them between vlans.:study:Reading: Lab Books, Ansible Documentation, Python Cookbook 2018 Goals: More Ansible/Python work for Automation, IPSpace Automation Course [X], Build Jenkins Framework for Network Automation []