We are working on setting up Auto Provisioning in our environment to speed up deployment time, but we will need to use different code versions for different switch models (7150 vs 7450, etc).My thinking is that we can modify the manifest.txt file and...
I went with plan B and it's working so far. Created a second Auto Provision vlan/DHCP scope for devices that will need a different firmware version. That way I could specify a different bootfile on the 2nd DHCP scope. No manifest file manipulation ne...
Sorry to wreck this train but I have used LRs configured temporarily at 1G speed while we wait for the distant end to be upgraded and capable of 10g:SSH@0XXX-RTR-G1#sh media | inc 1/2/2Port 1/2/2: Type : 10GE LR 10km ((SFP+))SSH@0XXX-RTR-G1#sh int ...
At this point I would look to simplify the situation and disable the lag on both ends. Make sure you can get communications working over a single link, and then get the lag configured after that
Static or dynamic depends on the other switch's capabilities. Dynamic is the better option. If it's another Ruckus, go dynamic for sure. Check to make sure that the LAG is active with "show lag". Both links should be in forwarding state.Otherwise, yo...
