Connecting a managed Cisco switch to a smart Netgear switch via fiber

[bquade]

I'm racking my brain about what the issue could be. Very basic configurations, one vlan, the link lights are up on the fiber connection but there is no activity. Below is the Cisco config and the Netgear has the default configurations on it.

version 12.1

no service pad

service timestamps debug uptime

service timestamps log uptime

no service password-encryption

!

hostname NewBldg

!

enable secret 5 $1$MD5t$bylDlzLn0TWDZRMt5Y1Ck.

enable password ***

!

ip subnet-zero

!

vtp mode transparent

!

spanning-tree mode pvst

no spanning-tree optimize bpdu transmission

spanning-tree extend system-id

!

!

!

!

interface FastEthernet0/1

switchport mode access

spanning-tree portfast

!

interface FastEthernet0/2

switchport mode access

spanning-tree portfast

!

interface FastEthernet0/3

switchport mode access

spanning-tree portfast

!

interface FastEthernet0/4

switchport mode access

spanning-tree portfast

!

interface FastEthernet0/5

switchport mode access

spanning-tree portfast

!

interface FastEthernet0/6

switchport mode access

spanning-tree portfast

!

interface FastEthernet0/7

switchport mode access

spanning-tree portfast

!

interface FastEthernet0/8

switchport mode access

spanning-tree portfast

!

interface FastEthernet0/9

switchport mode access

spanning-tree portfast

!

interface GigabitEthernet0/1

switchport mode trunk

!

interface Vlan1

ip address 192.168.1.6 255.255.255.0

no ip route-cache

!

ip default-gateway 192.168.1.1

ip http server

!

line con 0

password ***

login

line vty 0 4

password ***

login

line vty 5 15

password ***

login

!

!

end

 

[bill001g]

There is nothing wrong with the config not sure why you have a trunk port unless you are going to run multiple vlans.

 

[bquade]

There is nothing wrong with the config not sure why you have a trunk port unless you are going to run multiple vlans.

I had it set up as an access port, however when it wasn't working I decided to go ahead and try to configure it as a trunk port... this all leads me to believe that it's something with the Netgear switch, but there are no configurations that could cause it to not communicate.

 

[bill001g]

If you do not need the trunk then just leave it a access port. The vlan numbers mean nothing when you run it all as access port. It pretty much runs as a stupid unmanaged switch with that configuration