Create an Etherchannel link

Catalyst WS-C3560X-24T-L  switch EtherChannel provides fault-tolerant high-speed links between switches, routers, and servers. You can use it to increase the bandwidth between the wiring closets and the data center, and you can deploy it anywhere in the network where bottlenecks are likely to occur. EtherChannel provides automatic recovery for the loss of a link by redistributing the load across the remaining links. If a link fails, EtherChannel redirects traffic from the failed link to the remaining links in the channel without intervention.

 I would like to create an etherchannel link between two cisco 3560 switches.

My question is: do all ports involved (4 in this case 2 on each switch) need to be the same number channel? or does the pair on one switch need to be a different channel from the  pair on the other switch.

Probably identifiable number on both sides will make maintenance easier, but technically it does not negotiate any channel name on the wire.

Configuring Layer 3 EtherChannels section of Configuring EtherChannel (Catalyst WS-C3560X-24T-S switch)

Configuring a GPON ONT

The Huawei MA5600  /MA5680T /MA5608T provides end users with services through the ONT. The MA5600T/MA5603T/MA5608T can manage the ONT and the ONT can work in the normal state only after the channel between the MA5600T/MA5603T/MA5608T and the ONT is available.

huawei(config)#interface gpon 0/2

huawei(config-if-gpon-0/2)#ont add 0 password-auth 0100000001 always-on profile-id 10 manage-mode omci

huawei(config-if-gpon-0/2)#ont add 0 password-auth 0100000002 always-on profile-id 10 manage-mode omci

huawei(config-if-gpon-0/2)#ont add 0 password-auth 0100000003 always-on profile-id 10 manage-mode omci

huawei(config-if-gpon-0/2)#ont add 0 password-auth 0100000004 always-on profile-id 10 manage-mode omci

huawei(config-if-gpon-0/2)#ont add 0 password-auth 0100000005 always-on profile-id 10 manage-mode omci

To add an ONT that is managed by the OLT through the OMCI protocol, confirm this ONT according to the SN 3230313185885B41 automatically reported by the system, and bind the ONT with capability profile 3 that match the ONT, do as follows:

huawei(config)#interface gpon 0/2

huawei(config-if-gpon-0/2)#port 0 ont-auto-find enable

huawei(config-if-gpon-0/2)#ont confirm 0 sn-auth 3230313185885B41 profile-id 3 manage-mode omci

To add an ONU that is managed as an independent NE and whose SN is known as 3230313185885641, bind the ONU with capability profile 4 that matches the ONU, configure the NMS parameters for the ONU, and set the management VLAN to 100, do as follows:

huawei(config)#snmp-profile add profile-id 1 v2c public private 10.10.5.53 161 huawei

huawei(config)#interface gpon 0/2

huawei(config-if-gpon-0/2)#ont add 0 2 sn-auth 3230313185885641 profile-id 4 manage-mode snmp

huawei(config-if-gpon-0/2)#ont ipconfig 0 2 static ip-address 10.20.20.20 mask 255.255.255.0 gateway 10.10.20.1 vlan 100 

huawei(config-if-gpon-0/2)#ont snmp-profile 0 2 profile-id 1

huawei(config-if-gpon-0/2)#ont snmp-route 0 2 ip-address 10.10.20.190 mask 255.255.255.0 next-hop 10.10.20.100

If the ONU is an independent NE and is directly managed by the NMS through the SNMP management mode, select the SNMP management mode. For this mode, you only need to configure the parameters for the GPON line and the parameters for the management channel on the OLT.

If the ONU is not an independent NE and all its configuration data is issued by the OLT through OMCI, select the OMCI management mode. For this mode, you need to configure all parameters (including line parameters, UNI port parameters, and service parameters) that are required for the ONU on the OLT.

Generally, the ONT management mode is set to the OMCI mode.

Cisco 3750 Stacking Q

I have two WS-C3750X-48T-L  and I want to stack them together to create one switch with 96 ports.  Do I just cable them together and the 3750s will become a stack automagically?  Or is there more that needs to be done?

 So here is what I would do with two switches that were already in production with configs on them.

#1 - make sure they have the same IOS on each them.  If not update one or the other so they are the same.  This just makes things easier.

#2 - Whichever switch will be on the bottom - issue a write erase and turn it off.

#3 - Cable the switches together with the stack cables criss crossing each other.

#4 - Power on the bottom switch

After it boots the top switch should recognize the 2nd switch as part of the stack and if you do a show ver it should show you that there are 2 switches in the stack.  The boot up takes a good bit on the WS-C3750X-48T-S   so be patient.

Police policy on SVI Cisco 3750

I'm trying to rate limit traffic from a couple of IPs in a VLAN (920). The traffic is incoming from 6 physical trunk ports. The VLAN 920 interface on this WS-C3750X-24P-S  is the default gateway in VLAN 920, the 3750 routes traffic to other VLANs.

I've created the policy as below, but I get this error when I try to apply it to the VLAN interface;

QoS: class(IdentifyPorts) Unsupported classification [Vlan920]

Service Policy attachment failed

添加图片说明

int range gi 1/0/1-3

mls qos vlan-based

int range gi 2/0/1-3

mls qos vlan-based

access-list 102 permit ip host 192.168.143.3 host 192.168.178.8

class-map match-any IdentifyTraffic

match access-group 102

class-map IdentifyPorts

match input gi 1/0/1 - gi 1/0/3

match input gi 2/0/1 - gi 2/0/3

policy-map Port-Policy

class IdentifyPorts

police 8000000 1000000 exceed-action drop

policy-map VLAN-policy

class IdentifyTraffic

set ip precedence 1

service-policy Port-Policy

int vlan 920

service WS-C3750V2-48PS-S-policy input VLAN-policy

. Bandwidth Threshold on Cisco 3750

Does anyone know if at layer 3 an interface has a limit ?

I have been told that even thought our WS-C3750V2-48PS-S  switch has 1GB ports that we can expect much lower bandwidth throughput on the ports if we are using layer 3 on those ports

I'm trying to find some documentation that explains this but nothing clear is coming up

All switches have a limit in layer 2 forwarding, usually expressed in Gbps or Mbps. It's sometimes called the backplane bandwidth.

Layer 3 switches also have a limit in routing, expressed in (IP) packets per second: Mpps.

For a routing device, routing a 16 byte ICMP 'ping' packet is the same effort as routing a 1450 byte TCP packet carrying HTTP. If you multiply your average packet size with this Mpps value, you get an average Mbps value that indicates your L3 performance.

Not sure about the 3750 (and it'll depend on the exact model), but from memory even the 3550-48 had the horsepower to do layer3 at 1Gbps with 800byte packets; and compared to that, even a first generation WS-C3750X-24T-L  is a monster.

Cisco 3750 trunks

I am currently replacing our backbone switches (2 x 3560's) linked together via

trunked ether channels.

The user switches (2960's) connect to each 3560 using their 2 x 1GB trunked

Ports.

Install a stack of (3 x WS-C3750V2-24TS-S 's) as the main backbone and server connections.

Install a stack  of ( 2 x 3750's) for the user switches to connect to . This will

Connect to the 3750X's using multiple trunked ether channels (2 x to

each 3750X)

Then ether channel and trunk each user 2960' to each the 3750's (2 x to

each 3750) using the two 1GB Ethernet ports.

This allows us to use the 3750x's for the high bandwidth requirements and

The user switches are kept away from the main backbone.

Not sure if you've already purchased the 3750x's, but if you haven't, see if you can order the new 3850 switches. They are the successor the to 3750X. Some cool features are a 480G stack cable (versus 64G with the 3750x), have netflow enabled on ALL ports, up to 4 10G ports (2 10G ports on the 3750X), and has a built in wireless controller (activated via licensing, but if not needed... just don't license it).

Here's the kicker - it's the exact same list price as the 3750X.

If you have an "ordinary office" network load, there is no advantage in putting the the 2x 3750 for the client switches to connect to. Even with etherchannel, you will have multiple client connections sharing each 1GB link, from the 3750 switches to the 3750 X switches

If your budget permits, I've be tempted to do a stack of 5x 3750 X, if it doesn't then even a stack of 4x 3750 X with the client switches distributed across would be better, then you can utilize the stack bandwidth between the switches.

As you are stacking the 3750 X switches, the trunks to/from each trunked server and switch should be across two switches, for example port 1 on switch 1 and port 1 on switch 2 rather than ports 1 & 2 on switch 1.

Much as I like the WS-C3750X-48T-S  series of switches (and manage several stacks of them), for a L2 network, or even one with "light" L3 requirements (inter VLAN routing, but not BGP etc) I would usually specify the HP 5400zl series.