we are setting up our first ATT metro ethernet connection. I have a Cisco 2960S at the remote site and I placed a Cisco 2960 on the Host site to test and had no issues. When I moved the Host site to our Nexus 7000, I can not get a link.. both sides are set as trunks,
anything special about why it will not come up when connected to the 7K?
I feel the fiber cable is correct, it works when I plug into a 2960, I also have a case open with ATT to see if there are any special setup to connect to the 7K. Not sure what configuration I should use for the VTP you mentioned.
You shouldn't need to configure any VTP command. If one side of the interface is configured with trunk (nexus in your case) and the other side is configured with nonegotiate (2960) the trunk should come up.
Can you configure both side as an access switch and test? If successful, this will tell us that there is something wrong with trunk negotiation.
Each side of the circuit connects to a device at ATT. The 2960 switch connects and shows a connected state on it's interface. The 7K side show a disconnected state. I think the issue is a capability issue between the ATT device and the 7K. I just don't have many options on the 7K port to set now.
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...