What is the reasoning for two separate view rules for IP Switches?

[crystalrforbes]

In an effort to uncover an inexplicable view rule in our CMDB, I found when looking at our IP Switch CIs that I was unable to right click on the CI to change the "view" of the CI from Default view to Compliance view.

According to our Developer there are two separate Out-of-Box (OOB) view rules for viewing IP switches in the CMDB:

        Switch, Plain

        Switch, with Routing

Why are IP switches separated with different CI views? Is there a specific infrastructure reason why I might not want to have consistent user interface for all IP Switch CIs in our CMDB?

I'm really working to increase user adoption and participation in maintaining our ServiceNow Configuration data. And as a result I'm trying to address all odd quirks, bugs, or possible inconsistencies in the user interface.

Is there some really smart reason I should be aware of to explain this inconsistency? Or, is this simply an OOB error that we could modify our instance to only have a SINGLE view for all records in the IP switch class? (Normally I am a huge advocate of "Keep It Simple Silly" and try to maintain OOB settings unless there is a specific business reason for changing something, but in this case OOB seems to be more complicated than just a single IP switch view.)

All advice is welcome and very much appreciated!

[VivekSattanatha]

Hi Crystal,

The View will differentiate Layer 2 and layer 3 network switches. In normal Switch view, you can see only switching related components. Since Layer 3 switches can do routing, Switch with routing view will show switching as well as routing related information in the related list.

To recognize layer 3 switch, Instead of going with the model number this view was easy for me to identify. If you are using Discovery I suggest you can keep the view as it is.

Regards,

Vivek

Based on the impact hit like, helpful or correct