Cisco Cat3750 Stack details

I've got some 3750 stacks around the place and have run some reports off them but the problem is things like serial number and mac address is only displays the master switch details.

 Is there anyway of creating a report that will show the details of all the switches in the stack?

 Thanks

That's an excellent question, and something I've been wondering myself. It's actually one of the reasons why I haven't purchased Cirrus yet, as I have over 100 Catalyst 3750 stacks and as you can imagine inventory is very important. Ciscoworks does a wonderful job of keeping my 3750 stack inventory, even if it is an over priced bloated piece of ****

 If this can't be done this is going to cause us all sorts of problems as we're looking at moving our 6509 Chassis over to VSS later this year, which will basically give us the same result as a 3750 stack.

 i think you could easily write a script that would do that

 -------------------------------------------

sho ver

session # (replace # with switch number in the stack)

 sho ver

exit

 session # 

sho ver 

exit

-----------------------------------------------

 just repeat this for how ever many switches are in each stack

i used sho ver for example but this would work for most anything i would think 

probably not perfect but it should get the job done

 the tricky part is knowing which one is master.  i try to setup the priorities so that switch 1 is always master.  sometimes i forget and sometimes it just isnt the case though.  session always has to be run from the master, thus the need for the exit after each session. 

hope this helps . . .

Looking around Cirrus, the switches with serial numbers are listed in the Physical Entities section of the Inventory.

One manual way it to place the various stack serial number information into snmp-server chassis-id " string".  This is one tedious problem.

There was a non-standard report that was mocked together.  It's not the best but may help out. I'll try to remember to post it.

Regards

P.S.
This issue is one the few remaining reasons we still have CiscoWorks LMS.

maybe someone at SolarWinds can tidy this up...

 This report filters on vendor = Cisco and Machine Type = 3750

Reports on:

Node name
card number  (so you can see the # of devices in the stack
IP Address
Firmware Revision
Software Revision
Serial Number
There is some extraneous information that I was using for testing.
I would be wonderful to obtain a single Cirrus / NCM report that could be used for Cisco SmartNet auditing and submissions.  It would take a lot off of my plate.

 The following is what I am using.  BTW, I have no idea what the referece to Sheme=F... comes from the server doesn't have that partition.

<Report Version="2.0" ReportType="" Schema="F:\SOLARW~1\SOURCE~1\COAEFA~1\ConfigMgmtEngine8\Schemas\Node_Details.Schema" Category="Inventory" Title="Cisco - 3750 Physical Entities with Class 3 only - REC modification  " SubTitle="" Description="Display information about Physical Entities within each device" Footer="" Grouping="" FieldList="NODES.NodeCaption,ENTITY_PHYSICAL.Name,NODES.AgentIP,ENTITY_PHYSICAL.Description,ENTITY_PHYSICAL.Class,ENTITY_PHYSICAL.Position,ENTITY_PHYSICAL.HardwareRevision,ENTITY_PHYSICAL.FirmwareRevision,ENTITY_PHYSICAL.SoftwareRevision,ENTITY_PHYSICAL.Serial,ENTITY_PHYSICAL.Manufacturer,ENTITY_PHYSICAL.Model,ENTITY_PHYSICAL.Alias,ENTITY_PHYSICAL.AssetID" DisplayStatus="FALSE" IncludeConfigs="FALSE" MergeLikeRows="FALSE" Lines="Horizontal" SQL="SELECT Nodes.*,[ENTITY_PHYSICAL].[Name],[ENTITY_PHYSICAL].[Description],[ENTITY_PHYSICAL].[Class],[ENTITY_PHYSICAL].[Position],[ENTITY_PHYSICAL].[HardwareRevision],[ENTITY_PHYSICAL].[FirmwareRevision],[ENTITY_PHYSICAL].[SoftwareRevision],[ENTITY_PHYSICAL].[Serial],[ENTITY_PHYSICAL].[Manufacturer],[ENTITY_PHYSICAL].[Model],[ENTITY_PHYSICAL].[Alias],[ENTITY_PHYSICAL].[AssetID]
FROM Entity_Physical RIGHT JOIN Nodes ON Entity_Physical.NodeID = Nodes.NodeID and [ENTITY_PHYSICAL].[Class]=3
Where 
(
  (Nodes.Vendor = 'Cisco') AND
  (Nodes.MachineType = 'Catalyst 37xx Stack')
)

ORDER BY [NODES].[NodeCaption],[ENTITY_PHYSICAL].[Name],[NODES].[AgentIP]" SelectClause="SELECT Nodes.*,[ENTITY_PHYSICAL].[Name],[ENTITY_PHYSICAL].[Description],[ENTITY_PHYSICAL].[Class],[ENTITY_PHYSICAL].[Position],[ENTITY_PHYSICAL].[HardwareRevision],[ENTITY_PHYSICAL].[FirmwareRevision],[ENTITY_PHYSICAL].[SoftwareRevision],[ENTITY_PHYSICAL].[Serial],[ENTITY_PHYSICAL].[Manufacturer],[ENTITY_PHYSICAL].[Model],[ENTITY_PHYSICAL].[Alias],[ENTITY_PHYSICAL].[AssetID]" FromClause="FROM Entity_Physical RIGHT JOIN Nodes ON Entity_Physical.NodeID = Nodes.NodeID and [ENTITY_PHYSICAL].[Class]=3" WhereClause="Where 
(
  (Nodes.Vendor = 'Cisco') AND
  (Nodes.MachineType = 'Catalyst 37xx Stack')
)
" OrderByClause="ORDER BY [NODES].[NodeCaption],[ENTITY_PHYSICAL].[Name],[NODES].[AgentIP]" TopX="All" TopXCount="10" TopXPercent="10" Orientation="Landscape"><FieldSelection></FieldSelection><CriteriaSelection><QUERY><KIND>1</KIND><COMPLEX><TAG></TAG><CONNECTIVE>1</CONNECTIVE><CHECKED>1</CHECKED><SIMPLE><TAG></TAG><ALIAS></ALIAS><ADVANCED>0</ADVANCED><COMPARISON>0</COMPARISON><FUNCTION>0</FUNCTION><SORT>0</SORT><CHECKED>1</CHECKED><LEFTSIDEKIND>2</LEFTSIDEKIND><RIGHTSIDEKIND>1</RIGHTSIDEKIND><COMPARISONATTRIBUTES></COMPARISONATTRIBUTES><FUNCTIONATTRIBUTES></FUNCTIONATTRIBUTES><LEFTFIELDPATH>Discovered Properties.Vendor</LEFTFIELDPATH><RIGHTFIELDPATH></RIGHTFIELDPATH><LEFTVALUETYPE>0</LEFTVALUETYPE><LEFTVALUE></LEFTVALUE><LEFTCAPTION>Vendor</LEFTCAPTION><RIGHTVALUETYPE>8</RIGHTVALUETYPE><RIGHTVALUE>Cisco</RIGHTVALUE><RIGHTCAPTION>Cisco</RIGHTCAPTION></SIMPLE><SIMPLE><TAG></TAG><ALIAS></ALIAS><ADVANCED>0</ADVANCED><COMPARISON>0</COMPARISON><FUNCTION>0</FUNCTION><SORT>0</SORT><CHECKED>1</CHECKED><LEFTSIDEKIND>2</LEFTSIDEKIND><RIGHTSIDEKIND>1</RIGHTSIDEKIND><COMPARISONATTRIBUTES></COMPARISONATTRIBUTES><FUNCTIONATTRIBUTES></FUNCTIONATTRIBUTES><LEFTFIELDPATH>Discovered Properties.Machine Type</LEFTFIELDPATH><RIGHTFIELDPATH></RIGHTFIELDPATH><LEFTVALUETYPE>0</LEFTVALUETYPE><LEFTVALUE></LEFTVALUE><LEFTCAPTION>Machine Type</LEFTCAPTION><RIGHTVALUETYPE>8</RIGHTVALUETYPE><RIGHTVALUE>Catalyst 37xx Stack</RIGHTVALUE><RIGHTCAPTION>Catalyst 37xx Stack</RIGHTCAPTION></SIMPLE></COMPLEX></QUERY>
 </CriteriaSelection></Report>

They are part of the same "virtual" chassis utilizing one IP address.

What happens is this:  Configure one 3750 chassis with it's IP Address, etc. like a normal Cisco device.  Cisco supplies you with a StackWise cable which is used to link the devices.  When you link a second, third, fourth, etc. switch 3750 device it becomes a member of the stack of switches, using the same IP Address and management.  (FYI DELL PowerConnect devices do this also).

When Orion NCM inventories the switch it'll obtain all of the information.  Currently Orion gets the information; the report is the problem.
The following is an limited and modified extract from the co inventory. 
Node, Number in stack, IP Address, Description, Class, Position, Hardware Revision, Firmware Revision, Software Revision, Serial Number, Manufacturer, Model

DC_Stack_1 1 10.127.1.1 WS-C3750G-24TS 3 1 M0 12.2(25)SEE3 12.2 25)SEE   1234567890   WS-C3750G-24TS-E   
DC_Stack_1 2 10.127.1.1 WS-C3750G-24TS 3   C0 12.2(25)SEE3 12.2(25)SEE3  1234567890   WS-C3750G-24TS-E   
DC_Stack_1 3 10.127.1.1 WS-C3750-48TS  3 3 E0 12.2(25)SEE3 12.2(25)SEE3  1234567890   WS-C3750-48TS-S   
DC_Stack_1 4 10.127.1.1 WS-C3750-48TS  3 4 E0 12.2(25)SEE3 12.2(25)SEE3  1234567890   WS-C3750-48TS-S   
DC_Stack_1 5 10.127.1.1 WS-C3750G-12S  3 5 V05 12.2(25)SEE3 12.2(25)SEE3 1234567890   WS-C3750G-12S-S   

This would go a long way to properly inventory stack based equipment.

 Chris,

Any update of getting this added to the Inventory report?

Thanks,

Jeff

jeff.stewart:

 Chris,

Any update of getting this added to the Inventory report?

Thanks,

Jeff

Jeff,

Try saving the above text in a file in the ..\Configuration Management\Reports" directory with the   .ConfigMgmtReport  Extension.

  I used the file name "3750-PhysicalEntitiesClass3.ConfigMgmtReport"

chris.lapoint:

I've tested that report on my lab here, but I've only got 1 3750 stack.   Can you send me a screen shot of the output of the report in your environment?    Also, is this report acceptable or is there something else that you'd want incorporated into the OOTB version?

I'll do this on Wednesday, and offer this report for consideration letting the user community chime in. I probably will like to hear the forum's input.

Regards, 

chris.lapoint:

I've tested that report on my lab here, but I've only got 1 3750 stack.   Can you send me a screen shot of the output of the report in your environment?    Also, is this report acceptable or is there something else that you'd want incorporated into the OOTB version?

 Chris,

Please see the attached graphic this somewhat represents the information from the above 10-21-2008 4:50 PM message.

Some of the fields in the report are not editable. Why I have no idea.

chris.lapoint:

Thanks for posting.  That helps.   In addition to ensuring that all fields are editable, would you like it if the report was grouped by node name?   For others viewing, is this what you are looking for as well?

Opinion.

For ease of use it would be helpful if the first sort is either ip address or node name ( It depends orgainzation's naming conventions ). 
The second level.sort should be on "Card Name".  "Card Name" reflects the location in the stack.  If you are responsible for 3750 stack switches that have multiple devices it would be helpful to have the report sort that for you.
If you notice on this report one stack is ordered (1,3,2) and the other (2,3,1).  

Another take using the same report would be helpful to be able to group by Description, IPAddress/Node Name, Card Name.
This would represent a device inventory helpful for locating specfic switches type.  But I guess a filter could provide the same information.

Notes on the report fields:

1. Manufacturer, Alias, and Asset ID provide no results.
2. Field "Manufacturer model" provides better detail then "Description".
3. "Class" ENTITY_PHYSICAL].[Class] does not need to display

For me this is a WIP to provide required information.