It would be nice to see within a topology map, which links are virtual eg. based on Layer 3 IP Information and which are real phyiscal links.
Also it would be nice to switch off viewing of virtual links dynamically by user within the GUI.
This feature could be fundamental to show Spectrum maturity about network monitoring.
Thanks for posting the idea for CA Spectrum. You feedback is valuable to us.
While we see significant number of votes on this idea I would appreciate if we could get further help on this. We seek clarification on Virtual Links and there usage. What Business Problem would this solve?
Thanks,
Nagesh
Great idea, thanks for posting
Is there any news on this idea? It's been under review for quite a long time now, and with 99 votes it's clearly something lots of people would like to see.
Dear Spectrum Community Members,
Sorry for late response on this. The reason it took long because this is kind of complicated with the current design and the impact is also high. Having said that I just don't want to shoot down this idea. There are lot of scenarios needs to be considered and lot of questions need to be answered.
The challenge is how an OC identifies a virtual link? Which links are considered to be virtual links? Can we consider ports of type (iftype =153) - propVirtual & ifType=135 - Vlan are virtual ports? How about connectivity b/w VMs(are pingables/SNMP reachable) to Physical switch?
I want to be transparent with the members here and this may take some more time for review and to take decision.
Meanwhile additional inputs from the members is appreciated.
Thanks,
Nagesh
In my environment, for example, a physical WAN connection connects to a physical port. Maybe Gi1/0/1 on a switch. But if the subinterface on the router, say, Te0/0/5.1234 goes down, we cannot route across that interface.
So a hypothetical between Site and DC.
The virtual path: Site-R1_GigabitEthernet0/0/1.1234 <-> DC-R1_TenGigabitEthernet0/0/5.1234
The physical path:
Site-R1_GigabitEthernet0/0/1 <-> Site-6509_GigabitEthernet1/1
(WA_Link Model): Site-6509_GigabitEthernet1/24 <-> DC-6509_GigabitEthernet1/24
DC-6509_TenGigabitEthernet2/5 <-> DC-R1_TenGigabitEthernet0/0/5
Today, I have a WA_Link model that connects the physical ports on Gi1/24 of each 6509. And I have the router <-> 6509 links setup as WA_Link models that I refer to as "WAN Aggregation Link".
I have GigabitEthernet0/0/1.1234 at the site to Te0/0/5.1234 at the DC modeled as yet another WAN link with the "Virtual Link" designation somewhere in the desription.
I also have IP SLAs at the WAN edge that are modeled as "WAN Circuit Availability" services which, combined with all of the above, roll up, eventually, into a single "Site <-> DC WAN" Service.
It's not the prettiest solution, but it works. I'd love to see this somehow differentiated.
Perhaps add an attribute such as IsVirtualLink which can be set to True based on policy manager?
For each link which has this set to true, differentiate based on color or visual pattern. This way a person can decide which attributes constitute a virtual link for their environment.
CA can later decide if there is some absolute mixture of attributes which define a virtual link for all vendors.
I checked if propVirtual was a good fit for our Cisco 1000V, it included the portgroups but not the Vethernets. Since Vethernets are what connect to the virtual machines, I'd imagine it's a miss.
My customers would like to hide the links between WLAN-APs and the WLCs. ... if this feature could help me to do so. Would be great.
We would like to see that feature too because we have many questions about something like this from our customers.The idea is very old. Will this be implemented by any chance?
Nice Idea.
Topology is one of the important factor of Spectrum.If Spectrum is able to highlight physical and virtual link,it will be a added advantage.