BT HH 4 - GigE port - connection to switch

Anyone know how I can connect the GigE port to a switch at 1Gbps?
I connect the HH4 GigE port to my computer and it does so at 1Gbps (according to Windows XP)
I connect my computer to a netgear GS608 and it does so at 1Gbps (according to Netgear status lights and Windows XP)
I connect the HH4 GigE port to the GS608 and it does so at 100Mbps!! (according to the status lights on the GS608)
Cat 5 cable used - BT Home Hub 4 (Type A) | Software version 4.7.5.1.83.8.130.1.10 | Last updated 20/08/13

correct about cable.
Cat5 is not suited for Gig speeds.
Cat5E can cope but again would be the weak link if the hardware can utilize the speeds.
Your switch maybe picking up the inablilitly of the Cat5 cable to produce the right speeds and is auto switching down to maxamize stability. Borrow or buy a Cat6 cable and try that out
If I've helped, just click the Star - Every little bit helps
If you can't fix it with a hammer, you've got an electrical problem.

Similar Messages

Cisco 2950 MT-RJ ports - Connect two switches?

Hi Everyone,
I'm wondering if I can connect two cisco 2950s together via the two MT-RJ ports they have?
Basically, I'd like the fibre ports to be the trunk between the two switches if possible
I have two of these:
Thanks!

Hi,
Yes, that is possible. As long as your fiber patch cable is good there should be no issues.
HTH

Upgrade IOS on 3550 w/ Gig ports

Good morning,
I am in the middle of IOS upgrades and kind of stuck! I have a 3550 that has 12 gig interfaces, 10 of which are fiber and 2 of which are copper interfaces. I want to try to minimize the amount of downtime as much as possible. Obviously it's going to come down when I have to reload.
Here is my question. Is there a way for me to upgrade the IOS from one of the 10 Gig fiber interfaces? I tried using a media converter (fiber to copper) to connect my laptop to the switch, but I couldn't get the interface to come up. The media converter is 10/100Mbps and I couldn't find a way to change the speed on the interface of the switch to match that. Both copper interfaces are currently being used. The device is unmanaged so I cannot upgrade it remotely.
Thanks!
Colin

hi
I dont think you can make use of a media converter which is different in speed when compared to the port speed of the switch.
If you have 10/100Mbps port connecting to the Gig port on the switch whichs again 1000Mbps the port wont come up at all and you wont be to get them synced...
We did try something inline with this quite sometime back and failed with that.
what i can suggest is to logon to the console port of the switch and configure a vlan ip.
hook up your pc on any of the ethernet ports and configure on the same subnet to which the vlan belongs too.
Check the ip reachability to the switch from the local pc and upload the ios using TFTP..
regds

Networking Best Practices - Connecting Two Switches

Connecting two switches together is an easy task, which makes it so frustrating when it doesn’t work. Here we will outline a basic scenario of connecting two switches and achieving connectivity. In these scenarios we will be using commands and settings that will work for most modern PowerConnect switches. However this does not cover all possible scenarios and the commands may differ slightly from switch to switch.
For instance, in most cases you can use General or Trunk mode when connecting two switches. However, on the PowerConnect 62xx series switches, you must use General mode if you want to allow management traffic onto the switch over the PVID. If you use Trunk mode, you will not have the default VLAN on those ports. The ports will only allow tagged traffic.
For more details on the difference between Access, General, and Trunk modes, follow this link.
http://en.community.dell.com/support-forums/network-switches/f/866/p/19445142/20089157.aspx#20089157
It is always a good idea to have the user and CLI guide for your switch, to reference any possible changes in command syntax.
http://support.dell.com/support/edocs/network/
Layer 2
Layer 2 switches operate at the data link layer of the OSI model. Layer 2 is responsible for error checking and transmitting data across the physical media. MAC addressing sources and destination protocols are layer 2 protocols. Layer 2 switches use the MAC address of data packets to determine where those packets should go. It learns the MAC addresses of all devices and creates a segment/forwarding table.
When a switch receives a frame with a destination address that isn't in its forwarding table, the switch forwards the frame to all other ports. If the destination machine responds to the server, the switch will listen to the reply and learn which port the destination machine is attached to. It then adds that MAC address to the forwarding table.
The Dell PowerConnect Layer 2 switches have ports that all operate in VLAN 1 by default. If it is acceptable to have all traffic on the same broadcast domain, then you can simply leave the default alone, connect the two switches and traffic will flow.
If you do not want all traffic on the same broadcast domain, then we need to look at adding additional broadcast domains through the use of VLANs.
We will use 3 VLANs for the following scenario.
VLAN 1=Management
VLAN 2=Client
VLAN 3=Server
To create these VLANs we do the following commands (VLAN 1 is already created by default)
console(config)# vlan database
console(config-vlan)# VLAN 2
console(config-vlan)# VLAN 3
console(config-vlan)# exit
We can then name the VLANs to help keep things organized.
console(config)# interface vlan 2
console(config-vlan)# name Client
console(config-vlan)# exit
console(config)# interface vlan 3
console(config-vlan)# name Server
console(config-vlan)# exit
Once we have the VLANs created we can place a device in that VLAN by placing the port it plugs into, in access mode for the specific VLAN.
So we have a workstation on port e2 we want to be placed in VLAN 2, we would issue the following commands.
console(config)# interface ethernet 1/e2
console(config-if)# switchport mode access
console(config-if)# switchport access vlan 2
console(config-if)# exit
The next port plugs into a server on port e3 we want on VLAN 3, we would issue these commands.
console(config)# interface ethernet 1/e3
console(config-if)# switchport mode access
console(config-if)# switchport access vlan 3
console(config-if)# exit
For the ports connecting the two switches together, we place the ports in trunk mode and specify the native VLAN and allowed VLANs.
For the port e1 that connect the two switches to each other would be configured like this.
console(config)# interface ethernet 1/e1
console(config-if)# switchport mode general
console(config-if)# switchport general allowed vlan add 2,3 tagged
console(config-if)# switchport general pvid 1
console(config-if)# exit
Once these VLANs and port settings are made on both switches. A server connected to switch A on VLAN 3 should be able to communicate with another Server connected to switch B that is also in VLAN 3. Without the use of a router the devices in VLAN 3 will not be able to communicate with devices that are outside of their broadcast domain (i.e. VLAN 2 devices could not reach VLAN 3 devices)
Layer 3 + Layer 2
Until recently, routers were the only devices capable of layer 3 protocols. Switches capable of routing are now available and in widespread use. In most cases we will connect our layer 2 switches to a Layer 3 capable switch to perform our routing for us.
On the layer 3 switches we will use the same VLANs and setup that we did with the layer 2 switches. Then we will add to the configuration.
We can assign an IP address to each switch with the following command.
Switch A
console(config)#ip address 172.16.1.1 255.255.255.0
Switch B
console(config)#ip address 172.16.2.1 255.255.255.0
Then we will enable routing only on Switch A
console(config)# ip routing
Switch A we assign an IP address to VLAN 2 and enabling routing on the VLAN.
console(config)# interface vlan 2
console(config-if-vlan2)# Routing
console(config-if-vlan2)# ip address 172.16.20.1 255.255.255.0
console(config-if-vlan2)# exit
Switch A we assign an IP address to VLAN 3 and enabling routing on the VLAN.
console(config)# interface vlan 3
console(config-if-vlan2)# Routing
console(config-if-vlan2)# ip address 172.16.30.1 255.255.255.0
console(config-if-vlan2)# exit
On both switch A and switch B we will keep things simple and use interface 1/e1 for the connection between each switch. Setting both switches 1/e1 to general mode, allowing the additional VLAN 2,3, and keeping the PVID of 1.
console(config)# interface ethernet 1/e1
console(config-if)# switchport mode general
console(config-if)# switchport general allowed vlan add 2,3 tagged
console(config-if)# switchport general pvid 1
console(config-if)# exit
We will have one client computer connect to switch A on port 1/e2 and one client connect to switch B on port 1/e2. These ports will be in access mode for VLAN 2, and the config should look like this on both switches.
console(config)# interface ethernet 1/e2
console(config-if)# switchport mode access
console(config-if)# switchport access vlan 2
console(config-if)# exit
We will have another client computer connect to switch A on port 1/e3 and one client connect to switch B on port 1/e3. These ports will be in access mode for VLAN 3, and the config should look like this on both switches.
console(config)# interface ethernet 1/e3
console(config-if)# switchport mode access
console(config-if)# switchport access vlan 3
console(config-if)# exit
On Clients connected to Switch A we will assign an IP address and gateway based on the VLAN they are in access mode for.
Client connected to access port for VLAN 2.
IP Address:172.16.20.11
Default Gateway:172.16.20.1
Client connected to access port for VLAN 3.
IP Address:172.16.30.11
Default Gateway:172.16.30.1
On Clients connected to Switch B we will assign an IP address and gateway based on the VLAN they are in access mode for.
Client connected to access port for VLAN 2.
IP Address:172.16.20.12
Default Gateway:172.16.20.1
Client connected to access port for VLAN 3.
IP Address:172.16.30.12
Default Gateway:172.16.30.1
External Connection
At some point we may want traffic to have an external connection. To do this we can create a new VLAN for our point to point connection from Switch A to our router. We will use VLAN 7 for this and assign an IP address.
console(config)# vlan database
console(config-vlan)# VLAN 7
console(config-vlan)# exit
console(config)# interface vlan 7
console(config-vlan)# name WAN
console(config-if-vlan2)# Routing
console(config-if-vlan2)# ip address 10.10.10.2 255.255.255.0
console(config-if-vlan2)# exit
On our router we will assign an IP address of 10.10.10.1
Then place the port connecting the switch and router into access mode for VLAN 7. In this case we use port e4.
console(config)# interface ethernet 1/e4
console(config-if)# switchport mode access
console(config-if)# switchport access vlan 7
console(config-if)# exit
We will then need to put in a default route with the next hop as the router IP address. This allows the switch to know where to route traffic not destined for VLANs 2, 3, or 7.
console(config)#ip route 0.0.0.0 0.0.0.0 10.10.10.1
Next on the router we’ll need to add a route back so the router knows about the networks attached to switch A. Generally adding a static route on most routers is done with the following command:
ip route {Network} {Wildcard Mask} {Next Hop-IP}
In our case here are the 2 static routes we could use.
Ip route 172.16.20.0 0.0.0.255 10.10.10.2
Ip route 172.16.30.0 0.0.0.255 10.10.10.2
The routing that we enabled on Switch A will enable traffic from the other VLANs to traverse over port 1/e4 to the router, connecting us to external traffic. The routes we added to the router allow the traffic to flow back to the switch over port 1/e4.
Layer 3 + Layer 3
In some situations we have two switches, each setup to route for its own broadcast domain, which we want to connect together. In this situation we no longer have a need to use Trunk or General mode between the switches. Instead we can create a common VLAN that will be used for the connection between the two switches.
To create this VLAN we will run the following commands on both switch A and B
console(config)# vlan database
console(config-vlan)# vlan 6
console(config-vlan)# exit
console(config)# interface vlan 6
console(config-vlan)# name Connection
console(config-vlan)# exit
On switch A we assign an IP address to VLAN 6 and enable routing on the VLAN.
console(config)# interface vlan 6
console(config-if-vlan2)# Routing
console(config-if-vlan2)# ip address 172.16.60.1 255.255.255.0
console(config-if-vlan2)# exit
On switch B we assign an IP address to VLAN 6 and enable routing on the VLAN.
console(config)# interface vlan 6
console(config-if-vlan2)# Routing
console(config-if-vlan2)# ip address 172.16.60.2 255.255.255.0
console(config-if-vlan2)# exit
On both switch A and B we place the connecting ports into Access mode for VLAN 6.
console(config)# interface ethernet 1/e1
console(config-if)# switchport mode access
console(config-if)# switchport access vlan 6
console(config-if)# exit
We then need to make some changes to switch B now that it is layer 3 and not layer 2 and has its own broadcast domain.
We will enable routing on Switch B
console(config)# ip routing
What used to be VLAN 2 and 3 will now be VLAN 4 and 5 for our separate broadcast domains.
Switch B we assign an IP address to VLAN 4 and enabling routing on the VLAN.
console(config)# interface vlan 4
console(config-if-vlan2)# Routing
console(config-if-vlan2)# ip address 172.16.40.1 255.255.255.0
console(config-if-vlan2)# exit
Switch B we assign an IP address to VLAN 5 and enabling routing on the VLAN.
console(config)# interface vlan 5
console(config-if-vlan2)# Routing
console(config-if-vlan2)# ip address 172.16.50.1 255.255.255.0
console(config-if-vlan2)# exit
On Clients connected to Switch B we will assign an IP address and gateway based on the VLAN they are in access mode for.
Client connected to access port for VLAN 4.
IP Address:172.16.40.11
Default Gateway:172.16.40.1
Client connected to access port for VLAN 5.
IP Address:172.16.50.11
Default Gateway:172.16.50.1
The end result should look like this.
Troubleshooting
If we are having issues with connectivity, we may need to place some static routes in place to help traffic to the next hop in the network.
On switch A we configure a static route to help traffic to the next hop in the network, which is the router.
console(config)# ip route 0.0.0.0 0.0.0.0 10.10.10.1
The external router will also need a path defined back to all networks/VLANs.
To check the status of a port we can use the command. Show interfaces detail, this will help us see the port status. For example to check the status of port 48, we would run this command.
console# show interfaces detail ethernet 1/g48
To check routing paths:
console# show ip route
The IP address of the network for each VLAN should be listed as C – Connected. Then also a path or default route to your upstream router.
We can use basic ping commands from a client to help test where connectivity is dropping off at. By doing this we can narrow down where in the network to start troubleshooting.
-Ping from client to default gateway, being the VLAN the client is in access mode for. If this fails then we may need to double check our client settings making sure the proper IP and gateway are being used.
-Ping from client to the ip address of the switch the client plugs into. If this fails we may not have VLAN routing enabled on the VLAN the client is in.
-Ping from client to another client on same VLAN, same switch. If this fails we need to check on client settings, IP address and gateway.
-ping from client to another client on different VLAN, same switch. If this fails we need to double check the VLAN routing commands are in place.
-ping from client to the ip address of the next switch in the network. If this fails then check Trunk port configuration from switch to switch, ensuring the VLAN is added to the Trunk port.
-ping from client to another client on same VLAN, different switch. If this fails, check Trunk port settings.
-ping from client to another client on different VLAN, different switch. If this fails then check trunk settings and VLAN routing configuration.

Derek,
I tried to draw my prefered setup for this network configuration.
I would create a Team with the two 1 GBit NICs and use it for Domain, DNS, Backup and any SystemCenter Agents.
I would also Team the two 10 GBit NICs and than assign it to a Hyper-V Switch for the VMs. In Windows Server 2012 it is posible to create vNICs for the Management OS that use this Hyper-V Switch (Converged Network Design). I would create two vNICs SMB1
and SMB2 to use them for Cluster and Livemigration traffic with SMB Multichannel. If your storage system supports SMB Multichannel you can also use both as storage NICs (but this depends wich vendor you have).
Hope this helps.
Grüße/Regards Carsten Rachfahl | MVP Virtual Machine | MCT | MCITP | MCSA | CCA | Husband and Papa |
www.hyper-v-server.de | First German Gold Virtualisation Kompetenz Partner ---- If my answer is helpful please mark it as answer or press the green arrow.

HSRP Question 2 core 6513 connected with trunk gig port

i have problem and wish to help me , i have 2 core 6513 connected with trunk gig port .
suddenly the HSRP changed from standby to active on the standby switch and cause the network to freeze from about 30sec .
after while the HSRP revert back to it's original status , i have check the log and didn't able to define the root cause for the problem .
Attached the log for both of them , and i can share the show-tech if needed .

Post your HSRP configs for each vlan interface to see. Are you tracking any interfaces for any Standby groups? Could you have lost connection temporarily between the switches? Check the interface statistics for the link between the switches.

Failed while creating virtual Ethernet switch. Failed to connect Ethernet switch port

Hello Folks
I am completely stuck with the configuration of my virtual networks. I have one logical switch left to add to one of my Hyper-V 2012 R2 hosts when I started getting the error below when I try to add logical switches to either Hyper-V Host. I have been using
the document. 'Hybrid Cloud with NVGRE (Cloud OS)' to implement the virtual networking. Basically using the exact configuration that is in the document. I have added the PA Logical Network and the Network adapters and added the logical switch for it to my
hyper-v 2012 R2 host and everything was fine. I am now trying to add my ISCSI Logical Switch to the host and this is the error I get. My other Hyper-V host I get this error for any logical switch I am trying to add. Can someone help me with this error. I haven't
been able to find any information about it.
Also a some quick info on tracing an error like this so I can figure out what is causing it.
Thsi is my configuration so far
So as far as I know everything is peachy untill the error below. Dead stop now
Error (12700)
VMM cannot complete the host operation on the 08-NY-VHOST01.accounts.ccac-ont.ca server because of the error: Failed while creating virtual Ethernet switch.
Failed to connect Ethernet switch port (switch name = '******', port name = '88C16766-ED02-4AC0-8CD7-660AC9D424DD', adapter GUID = '{FAF431D8-0124-4E40-BB3B-9234BAA02973}'): The system cannot find the file specified. (0x80070002).
Unknown error (0x800b)
Thank you for your time
Christopher
Christopher Scannell

notice your GUID? you may want to consider ensuring that is the same GUID associated in your database. Sometimes during data corruption theres a smidge of a chance your sql database kind of either pulls old guids esp if this was reverted to snapshot
without it being powered off etc.
I would try that first. then i would consider if you get to configure that with your current liscense associated with the host. I would need way more info to help any further

Can I use straight cable to connect trunk ports between 2 switches?

Hi,
Am I able to use straight instead of cross cable to connect trunk ports between 2 switches??
thanks!

Hi Devang,
When a 10/100 Fast Ethernet interface is enabled, one end of the link must perform media dependent interface (MDI) crossover (MDIX), so that the transmitter on one end of the data link is connected to the receiver on the other end of the data link (a crossover cable is typically used).
The Auto-MDIX feature eliminates the need for crossover cabling by performing an internal crossover when a straight cable is detected during the auto-negotiation phase.
HTH, if yes please rate the post.
Ankur

Connect unmanaged switch to 887VA fast ethernet port

I tried connecting an unmanaged (and dumb) switch to one of the four fast ethernet ports on the back of the router. I configured the port to act as an access port bound to a specific VLAN, say no. 100.
What I can see on the LEDs of the unmanaged switch is that the link goes up and down every few seconds. I don't know if this is related to the spanning tree protocol and unfortunately the unmanaged switch doesn't know about STP and doesn't send out BPDUs.
So, how I should configure the port in order to avoid the link going up and down?
The actual conf. for the port:
interface fastEthernet 3
switchport mode access
switchport access vlan 100

What do you mean by dumb siwthc? What model/make/company is that switch?
Can you try to do the reset of the switch so that it wipe off all the config what so ever present on the box and then try to connect the switch to the router?

2960x - stack cables connected while switches power on. SFP ports - status unknown

Connected 2960x uplink using SFP ports both stacks and all 4 ports worked good.
Remote tech connected last stack cable between first and last switch, in 2 different 2960x stacks of switches, while switches were powered on. A longer stack cable was needed. 3 of 4 SFP ports did stopped communicating.
One stack SFP stayed up in switch 2, not master. Completed reload - other SPF connected in switch 4/0/52
Second stack no connection on either SFP, remote tech power cycled switches.
After power cycle one SFP worked in Master 1/0/52, other switches SFP ports show "unknown" when inserting SFP.
Configured port 48 on stack with issue and connected second uplink just fine.
Has anyone experienced this with the SFP's?
- GLC-T P/N 30-1410-03
Looking for documentation on reccommending procedure for connecting stack cables while switches should be powered off or not.
Thanks,

Opened Cisco TAC case. the following bug was found.
the two different HBRN's below require 2 different IOS and they cannot be in same stack.
https://tools.cisco.com/bugsearch/bug/CSCur56395
switch#sh ver | s Hardware Board
Hardware Board Revision Number : 0x05
switch#remote command 2 sh ver | s Hardware Board
Switch : 2 :------------ Hardware Board Revision Number : 0x05
switch#remote command 3 sh ver | s Hardware Board
Switch : 3 : ------------ Hardware Board Revision Number : 0x12
switch#remote command 4 sh ver | s Hardware Board
Switch : 4 :------------Hardware Board Revision Number : 0x12
From Cisco.
Developers have recommended to upgrade the IOS version of switches with a Hardware Board revision Number below 0x10 to the release 15.0(2.0).EX5ES. this is the one attached to this email and should be applied to switch 1 and 2.
For switches with a Hardware Board revision Number above 0x10 to the release 152-2.4.E1ES, which I will send you right away. This should be done on switch 3 and 4.
Now, If you load the engineering special, you will need to do a full power-cycle (physically unplug the power and plug it back in for every single switch). A simple ‘reload’ will not resolve this.
The same must be done on Switch-0. For this stack you will only need to load the image attached to this email since all the Hardware Board revision Numbers are lower than 0x10.
done.

How to find which port on the switch that it connected with Mac address?

Hi,
I am trying to find which port of the switches it connected to thru mac-address?
I am able to get the mac-address from the ip address when i do
"show ip dhcp binding snooping" at the core switch.
But when I move on to the Edge switch to check which PC with this Mac address connected to the port,i returned with no result.(onli trunk port result)
I use sh ip arp | inc 000d.60cb.445d
but didn't give me which port it connected to.
How to solve this problem?
thanks!
KL

Hi KL,
If you are already on the edge switch you can run a command "sh mac-address-table address " and it will give you the port number.
Incase you get a port which is a trunk port that means the end device does not exist on this switch and exist on some downstream switch. So you can just find out the ip address of the downstream switch with "sh cdp neigh detail" command and connect to that downstream switch and then again issue the command "sh mac-address-table address " and check the port number and follow the above steps till the time you get the switch on whcih end host is connected.
HTH, if yes please rate the post.
Ankur

SG 300-28 28-Port Gigabit Managed Switch -Lan connectivity issues

Hello,
Our office lan running on 2 * SG 300-28 28-Port Gigabit Managed Switch.
PID VID:SRW2024-K9 V01
Firmware Version (Active Image):1.0.0.27
The users are seeing there connection to fileservers(mapped network drives) slowing down over the period.
We have to re-boot the offending switch to get the normal traffic back.
I have raised a ticket with cisco small business people and they said to upgrade the firmware to latest version.
But I am wondering why I need to upgrade this switch as the other switch which also brought at the same time with the same spec have no such issues.
Even if I decided to upgrade the firmware, they have recommended that I need to reset the switch to factory settings and try to put the previous configuration manually which is a worry for me.
I have logged on to the web console and I have found out, I can use TFTP or HTTP to backup the config,how do I use those services and what parameters i need to pass those to work, does using that functionality can rollback the switch to previous running configuration?
PS: Both the switch have connected together using a FC trunk with link aggregation eanbled.So how do I get all those settings back if I upgrade/rollback?
I just have to come up with some solution as it is affecting the business, so any help would be much appreciated.
Please see the attachment and let me know if any other info needed?
Thanks in advance,
Regards
Suji

Hi,
Please see the difference between the connected switches configuration.
Maybe the vlan 10 and 30 has been created wrongly.
Please see the config for both the switches and give me some advice/suggestions.
I really appreciate that.
                              Bad Switch Config
/* This is the config for the bad switch */
interface port-channel 1
flowcontrol auto
exit
interface port-channel 2
description netAppFiler1
exit
interface port-channel 3
description Switch
flowcontrol auto
exit
port jumbo-frame
vlan database
vlan 10,30
exit
interface ethernet g12
switchport trunk native vlan 10
exit
interface ethernet g24
switchport trunk native vlan 30
exit
interface vlan 10
name Private
exit
interface vlan 30
name "Private 2"
exit
voice vlan oui-table add 0001e3 Siemens_AG_phone________
voice vlan oui-table add 00036b Cisco_phone_____________
voice vlan oui-table add 00096e Avaya___________________
voice vlan oui-table add 000fe2 H3C_Aolynk______________
voice vlan oui-table add 0060b9 Philips_and_NEC_AG_phone
voice vlan oui-table add 00d01e Pingtel_phone___________
voice vlan oui-table add 00e075 Polycom/Veritel_phone___
voice vlan oui-table add 00e0bb 3Com_phone______________
port-channel load-balance layer-2-3
interface range ethernet g(25-26)
channel-group 2 mode on
exit
interface range ethernet g(27-28)
channel-group 3 mode on
exit
interface range ethernet g(27-28)
lacp timeout short
exit
interface range ethernet g(1-26)
lacp port-priority 2
exit
ip dhcp relay address 192.168.0.1
ip dhcp relay enable
ip dhcp information option
interface vlan 1
ip dhcp relay enable
exit
bonjour service enable csco-sb
bonjour service enable http
bonjour service enable https
bonjour service enable ssh
bonjour service enable telnet
hostname switchbad
line console
exec-timeout 0
exit
line ssh
exec-timeout 0
exit
line telnet
exec-timeout 0
exit
username admin password xxxxxxxxxxxxxxxxxxxxxxxxxx level 15 encrypted
no snmp-server enable
snmp-server location "Server Rack"
ip http exec-timeout 0
ip https exec-timeout 0
clock timezone 1
clock dhcp timezone
ip name-server 192.168.0.1 192.168.0.9
snmp-server set rlAutomaticClockSetFromPCEnabled rlAutomaticClockSetFromPCEnabled true
                         Good Switch Config
/* Good switch run config *
interface port-channel 1
description Switch
flowcontrol auto
exit
port jumbo-frame
lacp system-priority 2
voice vlan oui-table add 0001e3 Siemens_AG_phone________
voice vlan oui-table add 00036b Cisco_phone_____________
voice vlan oui-table add 00096e Avaya___________________
voice vlan oui-table add 000fe2 H3C_Aolynk______________
voice vlan oui-table add 0060b9 Philips_and_NEC_AG_phone
voice vlan oui-table add 00d01e Pingtel_phone___________
voice vlan oui-table add 00e075 Polycom/Veritel_phone___
voice vlan oui-table add 00e0bb 3Com_phone______________
port-channel load-balance layer-2-3
interface range ethernet g(27-28)
channel-group 1 mode on
exit
interface range ethernet g(27-28)
lacp timeout short
exit
interface range ethernet g(1-26)
lacp port-priority 2
exit
interface port-channel 1
switchport protected-port
exit
ip dhcp relay address 192.168.0.1
ip dhcp relay enable
ip dhcp information option
bonjour service enable csco-sb
bonjour service enable http
bonjour service enable https
bonjour service enable ssh
bonjour service enable telnet
hostname switchbaebf1
line console
exec-timeout 0
exit
line ssh
exec-timeout 0
exit
line telnet
exec-timeout 0
exit
aaa authentication enable Console local
aaa authentication enable SSH local
aaa authentication enable Telnet local
aaa authentication login Console local
aaa authentication login SSH local
aaa authentication login Telnet local
line telnet
login authentication Telnet
enable authentication Telnet
password xxxxxxxxxxxxxxxxx encrypted
exit
line ssh
login authentication SSH
enable authentication SSH
password xxxxxxxxxxxxxxx encrypted
exit
line console
login authentication Console
enable authentication Console
password xxxxxxxxxxxxxx encrypted
exit
username admin password xxxxxxxxxxxxxx level xy encrypted
ip ssh server
snmp-server location "Comms rack"
ip http exec-timeout 0
ip https server
ip https exec-timeout 0
clock summer-time recurring eu
sntp unicast client enable
sntp unicast client poll
sntp broadcast client enable
sntp server xx.yyy.zz.70 poll
sntp server zz.yyy.xx.201 poll
sntp server zz.yy.xxx.2 poll
sntp server xzz.xxx.xy.149 poll
clock dhcp timezone
ip name-server 192.168.0.1 192.168.0.9
ip telnet server
snmp-server set rlAutomaticClockSetFromPCEnabled rlAutomaticClockSetFromPCEnabled true
Regards
Smith

IPSEC w/ 2 FCIP tunnels using a single gigE port

A gig1/1 interface on a 9216i is servicing 2 FCIP tunnels (port 3225 & 3737) from 2 other 9216i switches. The FCIP ISL connecting to port 3225 has IPSEC configured and is working (trunking). The FCIP ISL connecting to port 3737 was trunking prior to configuring IPSEC for it, but now with IPSEC configured it is now broken. Looking through the IPSEC trouble shooting section, I'm not seeing any conflicting IPSEC/IKE parameters.
Is it possible to have IPSEC services working for 2 FCIP ISLs connecting to a single gig port? If so, I'm at a loss on how to properly configure it.
Thanks, Craig

Understand and that is the case there is only one crypto map assigned with the appropriate ACL, but still the connecution using port 3737 will not establish a connection. Here cmap definintion.
Crypto Map "cmap30" 10 ipsec
Peer = 211.175.105.69
IP ACL = acl30
permit ip 87.61.121.2 255.255.255.255 211.175.105.69 255.255.255.255
permit ip 87.16.121.2 255.255.255.255 211.175.105.85 255.255.255.255
Transform-sets: tfs30,
Security Association Lifetime: 450 gigabytes*/3600 seconds*
(* global configuration value)
PFS (Y/N): Y
PFS Group: group5
Crypto Map "cmap30" 20 ipsec
Peer = 211175.105.85
IP ACL = acl30
permit ip 87.61.121.2 255.255.255.255 211.175.105.69 255.255.255.255
permit ip 87.16.121.2 255.255.255.255 211.175.105.85 255.255.255.255
Transform-sets: tfs30,
Security Association Lifetime: 450 gigabytes*/3600 seconds*
(* global configuration value)
PFS (Y/N): Y
PFS Group: group5
Interface using crypto map set cmap30:
GigabitEthernet1/1

HH4 GigE port

Can anyone explain why
A:the port is called GigE and not any one of the industry standard terms?
B: laptop connects fine at GB speed but switch does not. Its a Gigabit switch all the ports are set to auto but forceing them to 1000 either full or half duplex results in a disconect - on any of the 24 ports, or any of the 3 switches Ive tried.
theres no option to change anything in the HH, unlike any other router Ive got where you can set the port speed\duplex etc
C: how it makes any sense to make only one port GB and the rest 10/100?- unless your now trying to sell me the HH5 i actually ordered for an additional £125 not free as specifed on the order.

A: Because "1000BaseT" wouldn't fit over the socket on the back?
B: You wouldn't be the only one where the GigE port on the Hub didn't connect at the right speed. It seems to be an automatic speed detection issue.
C: Most likely, that's what the hardware that BT bought supported at the time. Home Hubs may look pretty, but inside they are just modified versions of existing commercial designs. It does seem a bit pointless, though.

SRE External Gig port for WCCP traffic?

Has anyone been successful with using the external Gig port on the SRE modules for WCCP traffic? Has anyone tried it?
I'd like to reduce the CPU on my ISR-G2 routers that have the SRE modules running WCCP GRE. I'd like to use the external gig port on the SRE module for the WCCP traffic, which will allow me to use WCCP L2. Is this even feasible? Or maybe I just need to add WCCP L2 on an SRE as a New Feature request to Cisco?
According the to Cisco documentation....
The external service-module interface can be used to monitor LAN traffic. You can also select the external interface as the management interface for the SM. The external interface cannot be used for downloading applications.
Visible only to the SM software on the Cisco SM-SRE, the external service-module interface is the Gigabit Ethernet interface connector on the Cisco SM-SRE faceplate. The external interface supports data requests and data transfers from outside sources, and it provides direct connectivity to the LAN through an RJ-45 connector.

Tammy,
What is preventing you from configuing WAAS on SRE with L2 WCCP / Mask assignment via the internal interface? This is totally feasible.
If you are trying to decrease CPU utilization on your router, don't expect switching from GRE to L2 to make a drastic difference. The ISR G2 is a software based platform, as such WCCP (whether L2 or GRE) is processed by the CPU with CEF assistance.
True removing the GRE encapsulation will save some processing overhead, but in the end it's the PPS (packets per second) your router is handling that's driving the CPU.
Remember when you add WCCP / WAAS to the flow it's no longer packet in/ packet out on the router. Compressed data in on WAN, out to WAAS, uncompressed from WAAS back to Router, out on the LAN, then the reverse... uncompressed data on the LAN in to the router, out to WAAS, compressed from WAAS out to the router, then out on the WAN. So depending on the compression observed you will see > 2x the amount of traffic being processed by the router.

Can you Connect Cisco switch modules for to N2K?

I have not seen anything about connecting Cisco Switch modules for Blade Chassis to fex. Does anybody now if you can do that?
thank you.

thank you Lucien.
I think you got a right name for N2Ks, a NIC card extender. In my opion N2K should be able to support Blade switches. Not every company has just rack mount servers, most enviroment is mixed. In my case, I run out ports on N5K, but plenty available on N2K. I want add two more blade centers with gig switch modules in them. now I have to buy a N5K!!!. I'm sure Cisco can make N2K to support switches too.

BT HH 4 - GigE port - connection to switch

Similar Messages

Maybe you are looking for