03-17-2011 12:16 PM
I want to find out if you connect 2 ISL links between Core switches, but have not purchased trunking would both links pass traffic? We have set up this configuration and it appears that only one link is passing traffic. Additionally we made sure to use adjacent fiber ports on each of the switches.
We are looking at purchasing trunking with some new core switches in the next month or so.
Does anyone know how we can remove what appears to be a ghost connection (from the port we moved the fiber cable from) in DCFM. It still shows the port as grayed out when using the connection properties in DCFM and of course the link on the map show in an error condition. Are switch reboots required to clear this error?
Thanks for any help.
03-17-2011 12:57 PM
1) ISL links must work without any trunking license (they establish two independant links between switches). Trunking license is used only to make trunks - connections consisting of several links, making the fabric able to loose some of these links without recalculating fabric routing tables.
2) To get rid of the grayed out link, you must "confirm" the changes in the fabric through DCFM interface. No switch reboots are required.
03-17-2011 01:02 PM
There is no need for a trunking license both links should pass traffic if it is setup correctly.
I would recommend to login to the switchs via SSH session and check the ports on the CLI.
If you need further help please provide some more information like switch type, FOS code level
and the out put of the commands,
of the affected ports which are not working.
Do not reboot the SAN switch.
I hope this helps,
03-17-2011 01:04 PM
Trunking combined two or more physical ISL in to a single logical link and trunking is licensed feature. So as per my understanding you will not be able to use two ISL' s as a trunk.
Regarding the port - You can run portdisable / portenable command and see if port is coming online.
You can run porttest command as well and porttestshow command to see the result of this command.
Run errdump command to get more information about the port state.
03-17-2011 01:36 PM
I have attached a spreadsheet with the requested information. I've really only given you one side of the switch network, but the other side looks identical. Included in the spreadsheet are the switch types and firmware specification. Let me know if you have any questions.
I guess I should tell you we are using the DCFM Performance Graphs to show utilzation on the links. Nothing shows up on the newly created ISL links.
03-17-2011 11:51 PM
I assume that no traffic is passed through the link due to the fact how you have connected the devices to the SAN switch.
This cabling and your configured routing policy will affect which ISL will be used.If you will enable trunking both links will be used.
If you connect some server to odd and some to even port numbers this should cause the switch to use both links.
I hope this helps.
05-09-2011 03:28 AM
"2) To get rid of the grayed out link, you must "confirm" the changes in the fabric through DCFM interface. No switch reboots are required."
How do you "confirm" ?
05-09-2011 03:41 AM
'Confirm' is in the right-click menu and is actually called Monitor > Accept Changes.
Why would you want to interconnect core switches in the first place? In a classic Core-Edge design interconnecting core switches is neither recommended nor useful because data traffic will never be routed via a longer path (Edge-Core-Core-Edge).