STARTUP CONFIG IS NOT PRESENT FULL
STARTUP CONFIG IS NOT PRESENT PC

STARTUP CONFIG IS NOT PRESENT PC

The switch works fine when connected to the network using one of the 10Gb ports, but when I connect to another same switch with the network connectivity using one of the 40Gb ports with a QSFP to QSFP Active cable my PC connected to it is not getting network connectivity. Below is a session when I tried to copy from USB. We are replace old non-Brocade switches with these 6740Ts some will be in a logical VCS cluster. If the above does not work, please provide the output of the command being done.

Then, the changes should take affect right away. If you want to copy the config to your VDX, you can do it from, USB, FTP, SCP, etc to running. URL syntax for IPv4 copy startup-config to USB. URL syntax for IPv4 URL syntax for IPv6 copy startup-config to TFTP server. URL syntax for IPv4 URL syntax for IPv6 copy startup-config to SFTP server. URL syntax for IPv4 URL syntax for IPv6 copy startup-config to SCP server. path syntax flash://ДЇtp:// copy startup-config to FTP server. vcs3_rb1# copy startup-config ?ДЇlash:// copy startup-config to local flash. Notice вЂcopy start runвЂ™ is not available. With logical chassis mode, copying the starting config to running is not available as all configuration changes made are applied and automatically saved. I suspect you are running logical chassis mode. How can I replace the running-config file with startiup-config file? When I tried to copy startup-config to running-config I get error message, вЂњstartup-configвЂќ is NOT valid source URL.

STARTUP CONFIG IS NOT PRESENT FULL

This should have updated your VDX config on the fly, did you see the changes prior to reboot? Can you provide the full syntax?ДЄfter reboot I checked the running-config and itвЂ™s not showing the changes from copying off USB drive, but the startup-config shows what I have copied from USB drive.

Then I put the USB drive onto a new switch,В copied USB://myconfig running-config and rebooted switch (reload system). I then edited the running-config file by changing the chassis-name and IP address of Interface Management. Are you replacing a failed 6740T with a new 6740T?.Are the VDX in a logical VCS cluster? If so, how many VDX are in the cluster?.Please tell us a bit about how your VDX are setup:

Startup config is not present