It is common in the medium buisness to use a large chassis switch (or a pair of them) for both Layer 3 inter-VLAN routing and also Layer 2 port aggregation. For example, a 6513 with 200 hundered triple-speed ports for servers and desktops and also intervlan routing for 30 VLANs.
How does MARS deal with this? Is it a Layer 2 device as in "Cisco Switch-IOS 12.2" or is it a Layer 3 device "Cisco IOS 12.2"? Does it matter? (I always run native mode so there is not a seperate interface for the MSFC3).
Whatever it is, you will have to enable syslog on the MSFC and bundle it with the MARS. the logging level you set, gives whatever info you require.. MARS will collate all these info and give you an event correlation report.... Is this OK?
As far as I know, you'll have to add the MSFC3 device and configuring like Raj says. Then, you can add the Layer 2 Cisco switch as a "Cisco Switch-IOS 12.2" and you'll see there's an option for "Add Available Module". Look for the MSFC3 device created previously and add it.
Anyway, it's correct what Raj is saying. Don't worry too much because MARS will correlate the events.
I understand how MARS correlates messages. MARS also needs to understand the topology of the network at Layer2 and at Layer3. The switch is both a Layer2 device and a Layer3 device.
In native IOS mode, a 6500 switch and the onboard MSFC are managed with one interface. You can not add the "switch" into MARS as one device and the MSFC as a second device. They are the same interface, the same device.
You can not add an MSFC as a module. The only options are FWSM and IDSM.
So the question remains: Do I add this switch into MARS as a "Cisco Switch-IOS 12.2" or a "Cisco IOS 12.2"? Will it matter with regards to Layer2 and Layer3 topology calculation?
DocumentationCode download linksGoalRequirementLimitationsSupported ISR and UCS-E ModelSupported ISRG2 and UCS-E Blades:Supported ISR4K and UCS-E Blades:Step by Step ConfigurationConfigure one of the connectivity options to access the Cisco IMC from the n...
Firepower Threat Defense (NGFWv) on UCS E-series - Transparent Mode in HA
DocumentationCode download linksGoalRequirementLimitationsSupported ISR and UCS-E ModelSupported ISRG2 and UCS-E Blades:Supported ISR4K and UCS-E Blades:Step by Step ConfigurationCo...
I am currently unable to specify "crypto keyring" command when configuring VPN connection on my cisco 2901 router.
The following licenses have been activated on my router :