Really sounds like you may have a bad board out of the box…few comments below
-
If you can swap the 1100 back in and the FCS goes away, then i would agree cabling is prob not it
-
This is true only on copper (and you can set 100M Full on each side just for testing) SFP ports can be hard coded to 1000/Full as well.
Examples here:
[admin@IPA-LAB-CCR1009-01] > interface ethernet monitor 1
name: ether2
status: link-ok
auto-negotiation: disabled
rate: 100Mbps
full-duplex: yes
tx-flow-control: no
rx-flow-control: no
[admin@IPA-LAB-CCR1009-01] > interface ethernet monitor 9
name: sfp1
status: link-ok
auto-negotiation: disabled
rate: 1Gbps
full-duplex: yes
tx-flow-control: no
rx-flow-control: no
sfp-module-present: yes
sfp-rx-lose: no
sfp-tx-fault: no
sfp-connector-type: LC
sfp-link-length-9um: 20000m
sfp-vendor-name: Mikrotik
sfp-vendor-part-number: S-31DLC20D
sfp-vendor-serial: MT40813H3283
sfp-manufacturing-date: 14-08-13
sfp-wavelength: 1310nm
sfp-rx-power: -7dBm
- In our lab we have a CCR1009 connected to MikroTik, Cisco and HP network equipment on copper and fiber without issue…unfortunately you probably got a bad CCR.
There was a batch of bad CCR1009s early on and it’s possible you got one that’s been on the shelf for a while as all the new CCR1009s shipping seem to be pretty solid.
http://forum.mikrotik.com/t/is-there-something-wrong-with-ccr1009-8g-1s-1s/80075/1