+1 I've not seen any differences with ours either. I expect you could probably take the 3560 config and just paste it in and not get any errors. You should be fine if you're comfortable with IOS.
-Christopher On 12/11/14, 8:54 AM, "Stephen Fulton" <[email protected]> wrote: >The 4500X is hardly different from a Catalyst in terms of >configuration. IOS-XE looks very much like IOS, so much so I really >haven't noticed any cosmetic differences. So, if you can configure a >C3560 you can do so on a 4500X. > >-- Stephen > >On 12/10/2014 4:34 PM, Bob Fronk wrote: >> Hello group. >> >> I have a very short window to teach myself how to configure a Cisco >>4500x. Although I am no expert, I am familiar enough with other >>Catalyst switches to satisfy our networking needs. However, I have not >>touched a 4500x before. >> >> The goal is to (as soon as possible) take numerous C3560 switches with >>10G Single mode interfaces that cascade from one to the other, to the >>other, to the other, to connect our various locations across our campus. >> Some of the C3560 switches have only the 1G interface, while the newer >>ones have 10G. The issue is bottlenecks in the cascade. My hope is to >>use the 4500X as the "hub" and all other campus switches would connect >>to it. There may be a few 1G interfaces as well. All ports would >>trunk the 5 Vlans on this campus. >> >> All I am hoping for is a sanitized sample to help me learn. >> >> I am starting on this document today, but as I said, my timeline is >>extremely short and any help would be appreciated.- >>https://supportforums.cisco.com/document/124626/virtual-switching-system- >>vss-configuration-cisco-4500-series-switches >> >> Thanks - >> >> Bob >> . >> >> *Note: We have a new email address domain. Please add @dhec.com to your >>whitelists and update your contat lists* This email and any attached >>files are confidential and intended solely for the intended >>recipient(s). If you are not the named recipient you should not read, >>distribute, copy or alter this email. Any views or opinions expressed in >>this email are those of the author and do not represent those of the >>Davis H. Elliot Company. Warning: Although precautions have been taken >>to make sure no viruses are present in this email, the company cannot >>accept responsibility for any loss or damage that arise from the use of >>this email or attachments. {dhe*} >> _______________________________________________ >> cisco-nsp mailing list [email protected] >> https://puck.nether.net/mailman/listinfo/cisco-nsp >> archive at http://puck.nether.net/pipermail/cisco-nsp/ > >_______________________________________________ >cisco-nsp mailing list [email protected] >https://puck.nether.net/mailman/listinfo/cisco-nsp >archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
