If that's at me, I expected there is some kind of non-interactive shortcut command for that.What's your expectation of how it should work?
printf 'enable\nconf t\ninterface e 2/1/2\nno inline power\ninline power' | ssh switchwould do the trick. No need for anything else. I couldn't figure this out at first because no ; or && supported in shell.
@CED6688 - I am trying to do this on a 7250 and have no idea how to set it up. I have pfsense running frr bgp and a kubernetes cluster that cant reach it via metallb. Any pointers how to set this up?When I drop this to a 6450, I've decided to just do router-on-a-stick with a Mikrotik RB4011, which on its single SFP+ port can route 10gb/s on that one port (I've tested it) and supports BGP. I'll then have it redistribute the routes via OSPF to the rest of the network, which the 6450 will manage. All of my nodes have a separate interface to my storage VLAN, so that won't hit the Mikrotik, so the Mikrotik will really only be routing traffic that enters/leaves the cluster...and 10gb/s should be plenty enough for this for me.
Here is what I did. Maybe is helpful for you.Hello together
I've been trying to access my 7250 via console for 2 days now and I'm getting desperate. I have a Cisco DB9 cable which I have converted according to the following instructions.
Unfortunately the putty session does not respond. After that I found this article and tried it too, without success.
I also searched the internet for the original Brocade cable, but it is not available anywhere.
Should I assume that the 7250 mini-usb port is broken?
What else can I try?
View attachment 20548
Thanks @LodeRunner. See below:Output of "sh int br" and "sh run" would help. You can post them here in code tags wrapped in spoiler tags to make them collapse.
Off hand, subnet mismatch, VLAN tag vs untag issue (or port not part of the VLAN that has the VE with assigned IP), no default route, or a port in ERR-DISABLE state come to mind.
This was exactly what I needed! The cable now works. Thanks for the support.Hi S!rius,
I had to make the same sort of cable for mine, and can perhaps shed some light. First off, unless your Cisco cable uses different colors than mine, those are not the right pins. Here's the mapping I've used (successfully):
Green (Cisco) -> White (USB)
Yellow (Cisco) -> Blue (USB) (orange on the Cisco end should also work; both are grounds)
Red (Cisco) -> Green (USB)
Edit: My USB wire colors were different than what I found online and may be different than yours, so you might want to ignore this part of mine.
The important thing is that on the Cisco side, the middle two wires (pins 4 & 5) are ground. Then to each side of those (pins 3 and 6) are transmit and receive. Not sure offhand which is which, but on my cable they are green and red.
You can test your Putty setup by temporarily connecting pins 3 and 6 of the Cisco cable (ignoring the USB side). With that in place, anything you type in Putty should come right back and display on the screen.
If that doesn't work, you've got a problem on the Putty/serial port/Cisco cable side. If it does work, it's probably just a matter of getting the correct wires connected to the USB cable.
Hope that helps a bit.
@LodeRunner@Phlesh So to be clear, your home subnet (everything on your network) is 192.168.255.0/24? Because if your home network is really 192.168.0.0/24 or anything else really, then that's your problem. Otherwise, that config is as barebones as it gets and it should work. Is the one port that's connected going to your workstation or another switch? If it's another switch, how is the port on the far end configured (tagged or untagged)?
Hmm, maybe some new information here.@LodeRunner
I have a Ubiquiti USG (soon to be put to pasture) that has multiple VLAN's on it already. The default VLAN is the subnet as shown, yes (*.255/24). I have already verified I can ping from, say, my laptop on one of the other VLAN's in the network to devices in this *.255 subnet, so there should be no firewall issues at play here.
The port is connecting to another switch (which, again, is a Ubiquiti switch soon to be retired). That port is configured with a profile that sets "All" VLAN's to be tagged, or so it seems to me. I spent hours on this last night trying to determine whether that's indeed the case, and it seems to be. But I'm not sure how I can inspect frames, etc. to be able to debug it further.
You are missing a default route on the switch. It doesn't know where it has to forward traffic to that doesn't belong to its L2 segment.However, I can't ping any device in the other VLAN's. So, there is something still either wrong with tagging or there's a firewall rule I don't understand, I think?