monitoring cisco interfaces in stack

To the Ipswitch web site

Ipswitch Forums
Home      Members   Calendar   Who's On
Welcome Guest ( Login | Register )
      



monitoring cisco interfaces in stackExpand / Collapse
Author
Message
Posted 6/20/2005 5:12:21 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: Forum Members
Last Login: 11/19/2007 8:14:09 AM
Posts: 7, Visits: 23

Hello, i'm using the wup to monitor cisco IOS switches interfaces, my problem is when the switches are

in stack. both switches using the IP address and to view the 2nd or 3rd switch interface i need to use multiple community strings, for ex: public@es0, public@es1 etc.

how can i monitor those interfaces ??

10q.

Ronen

Post #7962
Posted 6/20/2005 5:51:13 AM


Time Traveler

Time TravelerTime TravelerTime TravelerTime TravelerTime TravelerTime TravelerTime TravelerTime Traveler

Group: WhatsUp Gold Expert
Last Login: Today @ 6:09:05 PM
Posts: 1,481, Visits: 4,501

Solution 1 : Use more standard switches

Solution 2 : Create one WUP object for each stack element. Although this is not directly possible because WUP will tell you that the IP address already exists. You can work around this by creating an object with a loopback ip (eg 127.0.0.x) then change its IP address. Since you can only assign the snmp community at the device level you can then poll your stuff the way you want.



Reading, writing and arithmetic - If you need to choose, please take option 1.
Post #7963
Posted 6/20/2005 7:12:08 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: Forum Members
Last Login: 11/19/2007 8:14:09 AM
Posts: 7, Visits: 23

works.

10ks.

Post #7964
Posted 6/20/2005 9:23:53 AM
Time Traveler

Time TravelerTime TravelerTime TravelerTime TravelerTime TravelerTime TravelerTime TravelerTime Traveler

Group: Forum Members
Last Login: 2 days ago @ 2:46:07 PM
Posts: 170, Visits: 76

Another option, and one we acutally use, is to assign a real ip address to the management vlan of each switch in the stack.  Luckily, I use a class B for my enterprize, so I have a entire class c i can dedicated to just my switches. (we have over 200 of them).

This makes things alot easier for not only mangement, but for rolling out IOS upgrades, etc.. Also, since each device has its own IP address, its easier for us to determine exactly WHICH switch has a problem.

 



Don Click
Network Manager
Denton County, Texas
Post #7967
Posted 6/20/2005 11:43:26 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: Forum Members
Last Login: 11/19/2007 8:14:09 AM
Posts: 7, Visits: 23

the main idea of the stack is to simplify the management, i wish i had more stacks i have only several. i dont have any problem with addresses because we have 2 B classes  ....

you right when u said that u can know witch switch has problem but u can solve it by monitoring both of the connected links.

finally stacks give u the ability to upgrade the hole stack at once .....

10q.

Ronen

Post #7976
« Prev Topic | Next Topic »


Reading This TopicExpand / Collapse
Active Users: 0 (0 guests, 0 members, 0 anonymous members)
No members currently viewing this topic.
Forum Moderators: Dave, Mark Singh, kevin r gillis, Jason Benton, Brandon Felger, Ben Henderson, Tripp Allen, Will Sansbury, Jason Williams, Hush, FTPplanet.com, Hugh Garber, George Dailey, WUP-PM, mmulryan@ipswitch.com, mswimm

PermissionsExpand / Collapse

All times are GMT -5:00, Time now is 7:54pm

Powered By InstantForum.NET v4.1.4 © 2008
Execution: 0.078. 7 queries. Compression Enabled.