- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- Re: IGMP between 2 4108gl
Switches, Hubs, and Modems
1752580
Members
5246
Online
108788
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-09-2003 01:39 PM
тАО01-09-2003 01:39 PM
IGMP between 2 4108gl
Hi,
I have the following problem in a Procurve switched environment, when running multicast traffic between two Procurve 4108gl
Here is the scenario ;
Switch A = 4108gl - IGMP enable with normal priority
Switch B = 4108gl - connected to Switch A - IGMP enable with normal priority
Switch C = 2524 - connected to Switch A - IGMP enable
Server A is connected on Switch A
Station B is connected on Switch B
Station C is connected on Switch C
We run a Ghost Console on Server A ( for multicasting image on stations)
When we run a multicast from Server A to Station B ( between both 4108gl ) , the multicast traffic seems to take a very high priority since no other
traffic is working. We can't even telnet the switch . As soon as the multicast is over we get full connectivity back.
Another strange thing is if we multicast on Station C ( between a 4108gl and a 2524 ), the multicast traffic takes normal priority and other types of traffic
keeps working, but if we look in Switch A , we can see that the multicast traffic occurs not only on the port connecting the 2524 ( wich is normal since Station C participate in the multicast) , but the multicast traffic occurs also on the port connecting the other 4108gl , even if there is no station participing in the multicast on this other switch.
The only igmp command applied in all switches is ip igmp , the rest is by default .
So the question is , is there a specific configuration to put in the 4108gl to get this working properly ?
thanks
Michel Caissie
Switch A
Image Size(Bytes) Date Version
----- ---------- -------- -------
Primary Image : 2588998 04/19/02 G.05.02
Secondary Image : 2588998 04/19/02 G.05.02
Boot Rom Version: G.05.01
Current Boot : Primary
vlan 1
name "DEFAULT_VLAN"
untagged A1-A3,B1-B3,H1-H24
ip address 172.22.0.3 255.255.252.0
ip igmp
exit
Status and Counters - IP Multicast (IGMP) Status
VLAN ID : 1
VLAN Name : DEFAULT_VLAN
Active Group Addresses Reports Queries Querier Access Port
---------------------- ------- ------- -------------------
224.0.1.24 31085 31084 A3
229.55.150.208 31085 31084 A3
235.80.68.83 31085 31084 A3
239.255.255.254 31085 31084 A3
IGMP Service
VLAN ID VLAN NAME IGMP Enabled Forward with High Priority Querier Allowed
------- ------------ ------------ -------------------------- ---------------
1 DEFAULT_VLAN Yes No Yes
Switch B
Image Size(Bytes) Date Version
----- ---------- -------- -------
Primary Image : 2588998 04/19/02 G.05.02
Secondary Image : 2588998 04/19/02 G.05.02
Boot Rom Version: G.05.01
Current Boot : Primary
vlan 1
name "DEFAULT_VLAN"
untagged A1-A3,B1-B24,C1-C24,D1-D24,E1-E24,F1-F24,G1-G6,H1-H6
ip address 172.22.0.4 255.255.252.0
ip igmp
exit
VLAN ID : 1
VLAN Name : DEFAULT_VLAN
Active Group Addresses Reports Queries Querier Access Port
---------------------- ------- ------- -------------------
224.0.1.24 24931 0
229.55.150.208 24931 0
235.80.68.83 24931 0
239.255.255.254 24931 0
IGMP Service
VLAN ID VLAN NAME IGMP Enabled Forward with High Priority Querier Allowed
------- ------------ ------------ -------------------------- ---------------
1 DEFAULT_VLAN Yes No Yes
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-09-2003 03:54 PM
тАО01-09-2003 03:54 PM
Re: IGMP between 2 4108gl
There is a command in command line mode which lets you set the priority. It says it's an interface Vlan command so I assume it goes something like:
int vlan1
no ip igmp high-priority-forwarding
That should fix your not being able to do anything else while multicasting.
The other problem I expect requires that you make each switch a querier. There is a command line option for that too but I am having trouble reading the damn pdf manual from HP. Everytime i try to read it it hangs IE.
Once you do that you may need to read:
http://www1.ietf.org/mail-archive/working-groups/magma/current/msg00048.html
Ron
int vlan1
no ip igmp high-priority-forwarding
That should fix your not being able to do anything else while multicasting.
The other problem I expect requires that you make each switch a querier. There is a command line option for that too but I am having trouble reading the damn pdf manual from HP. Everytime i try to read it it hangs IE.
Once you do that you may need to read:
http://www1.ietf.org/mail-archive/working-groups/magma/current/msg00048.html
Ron
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-10-2003 07:28 AM
тАО01-10-2003 07:28 AM
Re: IGMP between 2 4108gl
Hi Ron,
thanks for your answer ,
Regarding the priority it's already set for normal.It's not easy to read in the message , but in the IGMP Service part of the show tech
"
IGMP Service
VLAN ID VLAN NAME IGMP Enabled Forward with High Priority Querier Allowed
------- ------------ ------------ -------------------------- ---------------
1 DEFAULT_VLAN Yes No Yes "
The first Yes is for IGMP enable;
The No is for Forward with High Priority;
The third Yes is for Querier Allowed
But i may try to reset this by enabling High Priority and disabling it back.
Regarding the Querier options , i think only one switch is elected as a Querier within all the switch in the network that are willing to take the job. Maybe both 4108 are trying to act as a Querier . I gona disalow Querier on Switch B and see if it do any good.
-Michel
thanks for your answer ,
Regarding the priority it's already set for normal.It's not easy to read in the message , but in the IGMP Service part of the show tech
"
IGMP Service
VLAN ID VLAN NAME IGMP Enabled Forward with High Priority Querier Allowed
------- ------------ ------------ -------------------------- ---------------
1 DEFAULT_VLAN Yes No Yes "
The first Yes is for IGMP enable;
The No is for Forward with High Priority;
The third Yes is for Querier Allowed
But i may try to reset this by enabling High Priority and disabling it back.
Regarding the Querier options , i think only one switch is elected as a Querier within all the switch in the network that are willing to take the job. Maybe both 4108 are trying to act as a Querier . I gona disalow Querier on Switch B and see if it do any good.
-Michel
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-10-2003 10:25 AM
тАО01-10-2003 10:25 AM
Re: IGMP between 2 4108gl
Problem resolved:
After applying
no vlan 1 ip igmp querier on Switch B , the problem disapeared .
After allowing Switch B again to act as a Querier the problem did not reapear.
So there must have been some problem previously in the election of the Querier between the 2 4108gl .
So i wont take any chance , i'll just allow my main Switch to act as a Querier to prevent similar problems in the futur
-Michel
After applying
no vlan 1 ip igmp querier on Switch B , the problem disapeared .
After allowing Switch B again to act as a Querier the problem did not reapear.
So there must have been some problem previously in the election of the Querier between the 2 4108gl .
So i wont take any chance , i'll just allow my main Switch to act as a Querier to prevent similar problems in the futur
-Michel
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP