Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 
New Member

bad port type: port mode access(1)


I have got a Cisco 3845 with 2 HWIC WITH 4 PORTS one on slot 0 and another on slot 2

All interfaces on the first card slot 0 fa0/0/0 - 3 are configured on different vlans and are working fine.

on Slot 2, a modem from ISP is connected to fa0/2/1 and is configured on vlan 2

int fa0/2/1

sw a vlan 2

int vlan 2 is properly configured.

Int fa0/2/1 is up, however int vlan 2 is down.

THe vlan 2 exists in sh vlan-switch.

When I checked the spanning-tree on vlan 2

it says port 22/ fa0/2/1 is bad port type: port mode access(1)

What could be the problem?



New Member

Re: bad port type: port mode access(1)


I guess you don't have more than 15 VLANs?

(AFAIK the HWIC cards support only up to 15 VLANS)


Could you check if the port connected to the modem came up properly, maybe the ISP modem

needs some special duplex/speed configuration?



New Member

bad port type: port mode access(1)

I am got 5 vlans.

h vlan-switch

VLAN Name                             Status    Ports

---- -------------------------------- --------- -------------------------------

1    default                          active    Fa0/0/0, Fa0/2/0, Fa0/2/1

                                                Fa0/2/2, Fa0/2/3

2    VLAN0002                         active    Fa0/0/1

3    VLAN0003                         active    Fa0/0/2

4    VLAN0004                         active    Fa0/0/3

1002 fddi-default                     act/unsup

1003 token-ring-default               act/unsup

1004 fddinet-default                  act/unsup

1005 trnet-default                    act/unsup

VLAN Type  SAID       MTU   Parent RingNo BridgeNo Stp  BrdgMode Trans1 Trans2

---- ----- ---------- ----- ------ ------ -------- ---- -------- ------ ------

1    enet  100001     1500  -      -      -        -    -        1002   1003

2    enet  100002     1500  -      -      -        -    -        0      0  

3    enet  100003     1500  -      -      -        -    -        0      0  

4    enet  100004     1500  -      -      -        -    -        0      0  

1002 fddi  101002     1500  -      -      -        -    -        1      1003

1003 tr    101003     1500  1005   0      -        -    srb      1      1002

1004 fdnet 101004     1500  -      -      1        ibm  -        0      0  

1005 trnet 101005     1500  -      -      1        ibm  -        0      0

New Member

Re: bad port type: port mode access(1)


could you also post some interface information:

show int fa0/2/1


show int fa0/2/1 switchport

I just want to make sure that the port 0/2/1 is up and running (btw. is this the only port in VLAN 2?)



New Member

bad port type: port mode access(1)


i have the following problem

*Jan 12 11:49:42.899 BI: %SPANTREE-7-RECV_1Q_NON_TRUNK: Received 802.1Q BPDU on non trunk FastEthernet0/0/1 VLAN2.

*Jan 12 11:49:42.899 BI: %SPANTREE-7-BLOCK_PORT_TYPE: Blocking FastEthernet0/0/1 on VLAN2. Inconsistent port type

Here are the details

#sh int fa0/0/1 switchport

Name: Fa0/0/1

Switchport: Enabled

Administrative Mode: static access

Operational Mode: static access

Administrative Trunking Encapsulation: dot1q

Operational Trunking Encapsulation: native

Negotiation of Trunking: Disabled

Access Mode VLAN: 2 (VLAN0002)

Trunking Native Mode VLAN: 1 (default)

Trunking VLANs Enabled: ALL

Trunking VLANs Active: 2

Protected: false

Priority for untagged frames: 0

Override vlan tag priority: FALSE

Voice VLAN: none

Appliance trust: none

#sh int fa0/0/1

FastEthernet0/0/1 is up, line protocol is up

  Hardware is Fast Ethernet, address is c84c.7542.c872 (bia c84c.7542.c872)

  Description: Connexion Internet Spidernet

  MTU 1500 bytes, BW 1000 Kbit/sec, DLY 100 usec,

     reliability 255/255, txload 1/255, rxload 72/255

  Encapsulation ARPA, loopback not set

  Keepalive set (10 sec)

  Half-duplex, 10Mb/s

  ARP type: ARPA, ARP Timeout 04:00:00

  Last input 00:00:00, output never, output hang never

  Last clearing of "show interface" counters never

  Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0

  Queueing strategy: fifo

  Output queue: 0/40 (size/max)

  5 minute input rate 283000 bits/sec, 127 packets/sec

  5 minute output rate 0 bits/sec, 0 packets/sec

     343976 packets input, 89874579 bytes, 0 no buffer

     Received 249153 broadcasts, 0 runts, 0 giants, 0 throttles

     23 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored

     0 input packets with dribble condition detected

     1871 packets output, 116955 bytes, 0 underruns

     10 output errors, 33 collisions, 3 interface resets

     12713 unknown protocol drops

     0 babbles, 0 late collision, 25 deferred

     0 lost carrier, 0 no carrier

     0 output buffer failures, 0 output buffers swapped out

I have changed the vlan 2 onto fa0/0/1 now, and there are no additional interfaces on the vlan 2.

New Member

Re: bad port type: port mode access(1)


okay, let's see what we have:

You have configured the port fa0/0/1 statically to access mode. The log messages

say that you are receiving 802.1Q BPDU on this port.

So it seems that your ISP modem sends tagged frames, that is the port at the modem is

probably configured as a trunk port.

Your switch disables the port due to the configuration missmatch, acces-port on one side

trunk-port on the other.

You could try to configure your interface fa0/0/1 as a trunk port just to check if I'm right:

switchport mode trunk



New Member

bad port type: port mode access(1)


You are right, I have tested the ISP modem with my laptop so he must be trunking with native vlan 1..

VLAN 1 is already in use.

So i cannot configure the port as a trunk.

Cisco Employee

bad port type: port mode access(1)

Hi Ashley,

If you cannot make it a trunk port, then why dont you apply a bpdufilter on that interface and check if the connection comes up. Under the interface give the command "spanning-tree bpdufilter enable" - i think this must be the command.

It would drop those bpdu packets sent by ISP, and the connection would stay up when bpdu filter is configured.

Let us know if it helped.




Re: bad port type: port mode access(1)

  If you are running 2 4 port hwic switchcards make sure you have them setup correctly. I believe if you have more than 1 switchcard  you must tie them together using 1 port off each switchcard so that it looks like 1 switch otherwise you will have issues.  Just something to check to make sure this was done.  Make sure your switchcards have been stacked.

Configuring Stacking

Stacking is the connection of two switch modules resident in the same  chassis so that they behave as a single switch. When a chassis is  populated with two switch modules, the user must configure both of them  to operate in stacked mode. This is done by selecting one port from each  switch module and configuring it to be a stacking partner. The user  must then connect with a cable the stacking partners from each switch  module to physically stack the switch modules. Any one port in a switch  module can be designated as the stacking partner for that switch module.

Beginning in privileged EXEC mode, follow these steps to configure a  pair of ports on two different switch modules as stacking partners.


1. interface fastethernet interface-id

2. no shutdown

3. switchport stacking-partner interface FastEthernet partner-interface-id

4. exit

5. interface fastethernet partner-interface-id

6. no shutdown

7. end



Step 1 

Router(config)#interface fastethernet 

Selects the interface to configure.

Step 2 

Router(config-if)#no shutdown

Activates the interface. (Required only if you shut down the interface.)

Step 3 

stacking-partner interface FastEthernet 

Selects and configures the stacking partner port.

Step 4 


Exits interface configuration mode.

Step 5 

Router(config)#interface fastethernet 

Selects the stacking partner interface.

Step 6 

Router(config-if)#no shutdown

Activates the stacking partner interface.

Step 7 


Exits configuration mode.

Note Both stacking partner ports must have their speed and duplex parameters set to auto.

CreatePlease to create content