Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
With FTP it works fine using this "Path" with embedded username+password - but with SFTP the NXOS ignores the password and asks interactively.
Any idea how to make this work on NXOS without interactive prompting for the password?
...there is no "file...
https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst9500/software/release/17-17/configuration_guide/int_hw/b_1717_int_and_hw_9500_cg/configuring_interface_characteristics.html#speed-limitation-for-c9500x-60l4d
"Each set of adjacent SFP ports ...
Hi all,
the Catalyst 8570-G2 is obviously not an option since using 2x100G-Ports locks down all low-speed-interfaces.
Any idea to provide those interfaces in one device?
...adding a Cat8455-G2 seems to be a TCO-nightmare...Edit: Catalyst 8500-20X6C i...
Obviously - the C8570-G2 is the way to go.
But the docs are inconsistent:* FAQ und Datasheet state "240G Interface Limit" - so 2x100G plus 1x40G or 4x10G seem to be possible* FAQ https://www.cisco.com/c/en/us/products/collateral/networking/sdwan-rout...
HI all,
I wonder where I can find "NXOS"-logs of fabric-interconnects at intersight level.
Cisco LIve Session "BRKDCN-2086" mentions access to fabric-interconnects......using ssh!!!...this of course requires access to local infrastructure => breaking...
Thank you for your reply, I've read the document you posted before and skipped it as solution...
And wanted to reply: "yes - but how to handle this if there is a Windows-based SFTP-Service? I'd need to create (for 100 Nexus'-Switches) 100 Windows Use...
great thank you - that was too easy, of course - when not using any 100G-Interface, up to 260G are real.
...not what I wanted to hear, of course - but good, that all three documents are technically correct.
CSCwq55757 is not in the release notes - but according to Bug-Search-Tool https://bst.cisco.com/bugsearch/bug/CSCwq55757 5.0.0.46 is affected and 5.0.0.48 is fixed.
