I've run into an interesting problem in building out connectivity in our Global Collections. We have TWO SpectroSERVERS with models on them in a DSS environment at the local site. One has the VC AIM host modeled and all the Virtual Hosts on it. I've added the Access layer Switches to that server that service the ESX hardware and that connectivity is looking OK. We add the the VM servers and vSwitches Spectrum uses to reflect the ESX vSwitch to the global collection. We also add the Phy (Access) switch to show which Access switch is serving which VM. Lets call this "landscape a".
The Access layer devices also service Physical server devices on the other lansdcape (lets call it "landcape b") so I have them modeled there, but I also have Distro, Core and DMZ devices on that landscape as well. All of that resolves together nicely on that landscape. That said I am trying to do this: In Global Collection "FOO" connect Dev A (Access Switch) from Landscape A to Dev B (Distro Switch) on Landscape B, but Dev B is on Landscape B is already resolved to the correct (10 Gig port) on Landscape B. Anybody run into this issue? There is a "proxy" setting that I am using on Dev A on Land A since I don't want the alarm on that device from that landscape (landscape a). Bottom line I need to represent the connectivity in the Global Collection for mostly "lay folk" and not truly functional, so I could probably just connect the Access dev from Land A to the Distro device on Land B in the GC via number of different ways, but none seem optimal. Anybody faced this before? -- Robert K. Borowicz Austin, Texas --- To unsubscribe from spectrum, send email to [email protected] with the body: unsubscribe spectrum [email protected]
