01-05-2024 11:48 AM
Hello,
My first post in these forums, apologies if this is better placed in a different subsection.
My company deploys C1000s and C9300Ls in AV installations to handle multicast AVoIP traffic. In order to keep that traffic off of our corporate network we isolate it using a mini-router that's inside the Crestron control processors that we use. The 'LAN' side connects to our corporate network and the 'Control Subnet' side connects to our AVoIP switches.
These Crestron control processors allow for port-forwarding so that we can access the web GUIs of devices. For C9300L switches I have had no problem accessing their web GUIs via something like http://172.26.100.100:4254, which maps to 192.168.1.254:80. For the C1000 switches however I just can't get it to work. The initial config that I do via the CLI is essentially the same as the C9300L (enable http server, specify local login, set IP/mask on the VLAN SVI etc).
There is just something about these C1000 switches that doesn't allow for a connection to the web GUI via a forwarded port. Any suggestions on what I can try?
Thanks in advance,
Mark
01-05-2024 12:28 PM - edited 01-05-2024 12:31 PM
When you say that it doesn't allow for connection, will it not establish a TCP session at all? You can check by telneting to the mapped port, or running the following in powershell test-netconnection -p {port} {IP address}.
01-09-2024 10:03 AM
Yes that's right, I ran that powershell command and TCP fails. It is however successful for other devices on the subnet on different mapped port numbers. I said in my original post that I have never had an issue with 9300Ls, but I actually did run in to an issue with one recently. The common denominator seems to be the routing device, in this case a Crestron CP3N or CP4N. Maybe the C1000, C9300Ls don't like how the Crestron device is handling the connection?! The cases in which I have gotten it to work was using a different Crestron device that is AlmaLinux based (VC4), hence why I think the CP3N/CP4N is to blame. I might put a Wireshark tap in line and see if anything is getting to the C1000/C9300Ls. Open to any other suggestions! Thanks.
01-09-2024 05:30 PM
you need to post come configuration bit, also as you mentioned run some packet capture and debug logs to understand what went wrong ?
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide