So I hit a big snag... Heat! Everything but a laptop, and the parts needed to get Internet running are off right now, as I let the room cool back down. My office doesn't have enough HVAC for the equipment in here. On first glance, it was easy to point the finger at the two new switches that I was bringing on-line, but once I started doing measurements, I realized the largest issue was the second FreeNAS system, the new switches just pushed me over the tipping point. I can't run this much heat load in this room. I can probably get away with moving the new FreeNAS system into my wife's office, as her office is an open-air room with plenty of open ceiling space to flow the heat out, and there is a much larger cooling register in there... My wife just complained that the house is too warm, and I see the house is 3 degrees warmer that it should be, based on the thermostat setting. So clearly my over-heat problem is more complex than turning on two large switches, but I'm not going to be able to go much father for the moment.
After having the freenas systems off for a few hours, the room is cooled off again...
But with regard to bringing up the network itself, the management port ever came up, it is set to use DHCP by default, and that failed to do anything.
(FASTPATH Routing) #show serviceport
Interface Status............................... Up
IP Address..................................... 0.0.0.0
Subnet Mask.................................... 0.0.0.0
Default Gateway................................ 0.0.0.0
Configured IPv4 Protocol....................... DHCP
Burned In MAC Address.......................... 08:9E:01:17:96:8C
I think I saw some talk about that earlier in the thread...
But the trunking from my netgear switch to the Cisco and to the 6M is all functional, and the "home" vlan IP on the 6m is pingable, so in general I had no problems getting the 6m running. I can telnet into the IP on the vlan port, so clearly I don't /need/ the management port. My telnet is passing through every bit of my network stack... Wireless router, to the firewall switch, to the netgear switch to the Cisco to the 6m...
I have not configured snmp yet, nor ssh, so I can't say the management configuration is done by a long shot, but that is all secondary. I also need to go tweak the idle timeouts on my terminal sessions, it is constantly logging me off... but that is pretty normal.
But the bottom line is I hit no real snags. everything "just worked". When things "just work" I feel like I didn't learn anything. It was a bit more simple than configuring a Cisco, but not by much. The command line is different from the Cisco, but close enough that it all felt pretty easy. The context help was more useful than the manuals. The manuals mostly didn't have the right commands for the things I was looking up, so the context help was the main source of documentation I found to be useful.
I'm not doing any multicast here at home, so the temptation to dig into that isn't very strong. At the office I have multicast configured for IPTV head-end simulation, but I have no nead for streaming multicast at home... All of my home IPTV is from Plex, Directv, or o0ne of the many OTT video sources, and all of that is unicast.
After having the freenas systems off for a few hours, the room is cooled off again...
But with regard to bringing up the network itself, the management port ever came up, it is set to use DHCP by default, and that failed to do anything.
(FASTPATH Routing) #show serviceport
Interface Status............................... Up
IP Address..................................... 0.0.0.0
Subnet Mask.................................... 0.0.0.0
Default Gateway................................ 0.0.0.0
Configured IPv4 Protocol....................... DHCP
Burned In MAC Address.......................... 08:9E:01:17:96:8C
I think I saw some talk about that earlier in the thread...
But the trunking from my netgear switch to the Cisco and to the 6M is all functional, and the "home" vlan IP on the 6m is pingable, so in general I had no problems getting the 6m running. I can telnet into the IP on the vlan port, so clearly I don't /need/ the management port. My telnet is passing through every bit of my network stack... Wireless router, to the firewall switch, to the netgear switch to the Cisco to the 6m...
I have not configured snmp yet, nor ssh, so I can't say the management configuration is done by a long shot, but that is all secondary. I also need to go tweak the idle timeouts on my terminal sessions, it is constantly logging me off... but that is pretty normal.
But the bottom line is I hit no real snags. everything "just worked". When things "just work" I feel like I didn't learn anything. It was a bit more simple than configuring a Cisco, but not by much. The command line is different from the Cisco, but close enough that it all felt pretty easy. The context help was more useful than the manuals. The manuals mostly didn't have the right commands for the things I was looking up, so the context help was the main source of documentation I found to be useful.
I'm not doing any multicast here at home, so the temptation to dig into that isn't very strong. At the office I have multicast configured for IPTV head-end simulation, but I have no nead for streaming multicast at home... All of my home IPTV is from Plex, Directv, or o0ne of the many OTT video sources, and all of that is unicast.