It seems assigning a different rather than just a static address is what's fixing the issue.And if I statically assign the phone a different IP address, then all of a sudden now it can reach the internet and locally-hosted services again
Pin | Molex ATX fan wire color | Fan wire color | Purpose |
---|---|---|---|
1 | Black | Blue | Speed/Tach |
2 | Red | Red | 12VDC+ |
3 | Yellow | Black | 12VDC– |
SSH@switch-1(config-vif-10)#ip access-group "test_traffic" out
ERROR: ACL test_traffic has filters with "log" action. Output Access Lists cannot be configured.
You can get a cheap crimp tool and connectors from Aliexpress. Once you get the gist of it it's quicker than bothering yourself with solder joints and cutting wires. Search for "crimping JST kit", I believe the pitch in these is 2.0mm. @fohdeesha can probably confirm.Pinout (for ATX-style Molex connectors):
Pin Molex ATX fan wire color Fan wire color Purpose 1 Black Blue Speed/Tach 2 Red Red 12VDC+ 3 Yellow Black 12VDC–
Finally, I've attached a photo of a completed project for reference. I hope this helps all you fan modders out there! Cheers!
View attachment 38358
Fan 1 ok, speed (auto): 1<->[[2]]
Fan 2 ok, speed (auto): 1<->[[2]]
Fan 3 ok, speed (auto): 1<->[[2]]
The stack unit 1 chassis info:
Power supply 1 (AC - PoE) present, status ok
Power supply 2 not present
Power supply 3 not present
Fan 1 ok, speed (auto): [[1]]<->2
Fan 2 ok, speed (auto): [[1]]<->2
Fan 3 ok, speed (auto): [[1]]<->2
Fan controlled temperature:
Rule 1/2 (MGMT THERMAL PLANE): 60.7 deg-C
Rule 2/2 (AIR OUTLET NEAR PSU): 28.5 deg-C
Fan speed switching temperature thresholds:
Rule 1/2 (MGMT THERMAL PLANE):
Speed 1: NM<-----> 95 deg-C
Speed 2: 85<----->105 deg-C (shutdown)
Rule 2/2 (AIR OUTLET NEAR PSU):
Speed 1: NM<-----> 41 deg-C
Speed 2: 34<----->105 deg-C (shutdown)
Fan 1 Air Flow Direction: Front to Back
Fan 2 Air Flow Direction: Front to Back
Fan 3 Air Flow Direction: Front to Back
Slot 1 Current Temperature: 61.2 deg-C (Sensor 1), 28.5 deg-C (Sensor 2)
Slot 1 Current Temperature: 63.5 deg-C (Sensor 1), 56.0 deg-C (Sensor 2)
I'm not sure whether I'm on the S or R version of software. show runThere are multiple ways to do this, but since your eventual goal is to have the SFP provide routes to the Internet (which it will do over one or more VLANs), you don't want to use the layer 3 (router-only) method.
Which version of the ICX software are you running? Is it the 'S' (layer 2) or 'R' (layer 3) flavor? If it's 'R', are you currently using the ICX as a router, or are all of your ports and VLANs configured for layer 2 connectivity only?
You say the 'recommended' address for the SFP is 192.168.1.200, but what's critical to know is how the device will get its address. It will either be hardcoded in the device, or it will use BOOTP or DHCP to obtain an address (in which case there is no real need to use the 'recommended' address).
With the answers to all of those questions, it is possible to figure out a working configuration.
ver 08.0.95mT213
.I'm using a DFP-34X-2C2 and following the PON Madness guide. I currently have VLAN 1202 setup with all ports tagged and the only traffic on that vlan I see is from the router requesting a DHCP lease. When I do a tcpdump on the whole interface I still don't see other traffic from the GPON SFP. I also tried untagged ports.which SFP ONT? you'll most likely not want to do any IP addressing or routing on the icx itself. Just plug the SFP in, then on a computer on the same network (plugged into an ICX port that's on the same VLAN as the sfp+ port), and assign that computer the .200 address. the ICX shouldn't have an IP in that SFP+ vlan. Which leads me to - if you haven't, the sfp should be in its own isolated vlan, as it will be providing your internet feed. then you can connect that vlan to your routers WAN port, by either putting another icx port in that vlan, or trunking the vlan over something to your router. This is what I'm doing with my WAS-110 ONT in my icx6610
There is no software/firmware logic to change on these ICX models beside the model that supports fanless mode. Either add more cooling via some hackey method, run ac to where this is located, or buy a more energy efficient router/switch.snip....Fan speed 2 on complaint....snip
You'll need to show the full output of 'show version', that alone is not enough.I'm not sure whether I'm on the S or R version of software. show runver 08.0.95mT213
.
SSH@icx6450>show run
Current configuration:
!
ver 08.0.30uT313
!
stack unit 1
module 1 icx6450-48p-poe-port-management-module
module 2 icx6450-sfp-plus-4port-40g-module
!
!
!
!
vlan 1 name DEFAULT-VLAN by port
router-interface ve 1
!
vlan 5 name MGMT by port
tagged ethe 1/1/11 to 1/1/12 ethe 1/1/46 ethe 1/1/48
untagged ethe 1/1/2 to 1/1/4
router-interface ve 5
!
vlan 10 name Trusted by port
tagged ethe 1/1/11 to 1/1/12 ethe 1/1/46 ethe 1/1/48
untagged ethe 1/1/5 to 1/1/10 ethe 1/1/13 to 1/1/36 ethe 1/2/1 to 1/2/3
router-interface ve 10
!
vlan 20 name Lights by port
tagged ethe 1/1/11 to 1/1/12 ethe 1/1/46 ethe 1/1/48
untagged ethe 1/1/38 ethe 1/1/40
router-interface ve 20
!
vlan 30 name NVR by port
untagged ethe 1/1/37 ethe 1/1/39 ethe 1/1/41 ethe 1/1/43 ethe 1/1/45 ethe 1/1/4 7
router-interface ve 30
!
vlan 40 name IOT by port
tagged ethe 1/1/11 to 1/1/12 ethe 1/1/46 ethe 1/1/48
untagged ethe 1/1/42
router-interface ve 40
!
vlan 50 name Guest by port
tagged ethe 1/1/11 to 1/1/12 ethe 1/1/46 ethe 1/1/48
untagged ethe 1/1/44
router-interface ve 50
!
vlan 172 name Transit by port
untagged ethe 1/1/1 ethe 1/2/4
router-interface ve 172
!
!
!
!
!
optical-monitor
aaa authentication web-server default local
aaa authentication login default local
hostname icx6450
ip dhcp-client disable
ip route 0.0.0.0/0 172.16.1.1
!
no telnet server
username admin password .....
!
!
web-management https
!
!
!
interface ethernet 1/1/11
dual-mode 5
!
interface ethernet 1/1/12
dual-mode 5
!
interface ethernet 1/1/37
inline power
!
interface ethernet 1/1/38
inline power
!
interface ethernet 1/1/39
inline power
!
interface ethernet 1/1/40
inline power
!
interface ethernet 1/1/41
inline power
!
interface ethernet 1/1/42
inline power
!
interface ethernet 1/1/43
inline power
!
interface ethernet 1/1/44
inline power
!
interface ethernet 1/1/45
inline power
!
interface ethernet 1/1/46
dual-mode 5
inline power
!
interface ethernet 1/1/47
inline power
!
interface ethernet 1/1/48
dual-mode 5
inline power
!
interface ethernet 1/2/1
speed-duplex 1000-full-master
!
interface ve 5
ip address 10.10.5.1 255.255.255.0
!
interface ve 10
ip address 10.10.10.1 255.255.255.0
!
interface ve 20
ip address 10.10.20.1 255.255.255.0
!
interface ve 30
ip address 10.10.30.1 255.255.255.0
!
interface ve 40
ip address 10.10.40.1 255.255.255.0
!
interface ve 50
ip address 10.10.50.1 255.255.255.0
!
interface ve 172
ip address 172.16.1.2 255.255.255.252
!
!
!
!
!
!
!
!
!
end
You don't happen to have the desktop plugged into 1/2/4, do you?I have my desktop connected to one of the SFP+ ports using a Brocade optic and a fiber cable.
Any help would be appreciated. ThanksCode:SSH@icx6450>show run ... vlan 10 name Trusted by port tagged ethe 1/1/11 to 1/1/12 ethe 1/1/46 ethe 1/1/48 untagged ethe 1/1/5 to 1/1/10 ethe 1/1/13 to 1/1/36 ethe 1/2/1 to 1/2/3 router-interface ve 10 ! vlan 172 name Transit by port untagged ethe 1/1/1 ethe 1/2/4 router-interface ve 172 ! end
No, it's definitely plugged into 1/2/1. I actually tested plugging my laptop in 1/2/1 using a RJ45 SFP adapter and it is able to ping the desktop at 10.10.10.50, but is also doesn't get an IP from DHCP servers on the DCs and is unable to ping 10.10.5.1 or either of the DC VMs(10.10.5.2 & 10.10.5.3)You don't happen to have the desktop plugged into 1/2/4, do you?
It looks like you can plug the laptop into 1/1/5, manually assign 10.10.10.49/24, and ping the desktop at 10.10.10.50. This will demonstrate that modules 1 and 2 can pass traffic to each other.It seems like it's not routing from module 2 to module 1
Duh moment...eliminate variable to isolate the problem. Didn't think of that last night.It looks like you can plug the laptop into 1/1/5, manually assign 10.10.10.49/24, and ping the desktop at 10.10.10.50. This will demonstrate that modules 1 and 2 can pass traffic to each other.
You might also try running tcpdump at various points to determine where traffic is breaking down.
I'd also recommend the "show ip route" and "show ip cache" commands.