Hello,
I´m using a pair of two C9500-48Y4C running as a SV-cluster.
We are currently running on 16.12.1 and want to connet a N9K-C93180YC-FX3 using QSFP-H40G-CU3M cable.
As i can see from the Optics Compatibility Martrix, it should be supported in 16...
Hi,I have successfully discovered, and uploaded some devices to the portal and generated a full inventory report.No serialnumbers or linecards are listed in the reports! Are there any known issues?We had the same problem on the old collector (2.1.8) ...
Hello,A Customer sent me a Firewall-Screenshot and asked me, why the Collector tries the unsecure protocol RSH to 192.168.0.1, which is not included in our scanning-ranges. Is there a reason for this? BR,Martin
Hello,We are using CSPC 2.8.1.8 and some of our Devices are running SNMPv2, others SNMPv3.Is it possible to run a Discovery with both (v2 and v3) @ the same time?When i start a discovery manually by using: Management/DiscoverDevices....Scan by IP-Ran...
I´m going to test it tomorrow.
We previously wanted to use 40Gig, but we had the 40/100 bidi which only goes 100 meters... so we had to step back to 10 gig.
Therefor I changed both links on the first box to 10 gig.
Afterwards i did the same on the se...
17.6.X needs a complete reboot of the Stackwise-Virtual cluster.
Thats, why i first want to try the ISSU to 16.12.8, and i think, the first thing, that the TAC-engineer will say is.... please make the upgrade to 16.12.8
Hu1/0/49, Hu1/0/50, Hu2/0/49, Hu2/0/50 are configured as uplink in a Port-Channel
Hu1/0/51, Hu1/0/52, Hu2/0/51, Hu2/0/52 is the Stackwise-Virtual-Ling
Hu1/0/49 NEXU_SW-Serv notconnect 1 auto auto unknownHu1/0/50 NEXU_SW-Serv connected trunk full 40G...
