Port down...

Well, it's great. I managed to bump "sh" and then "entry" when I was in the configuration for a port section, and stop at the port.

I tried 'Set interface active ethernet 1/eXX', no luck. He accepts the order, but it is still down. I searched and found not the other options.

Is there something that I am missing?

This switch work? Usually just issue the command # no shutdown, will bring the port up.

Tags: Dell Switches

Similar Questions

Direct specific ports down a VPN L2L

I have a client who is trying to use an ISP hosted web filtering and content management a gateway, the ISP wants to use and L2L ISPEC VPN on site at their front door to control the traffic. Today we have the tunnel with an ACL test for peripheral test side customer down the tunnel, but that it blocks all traffic that is not being analyzed. The problem is that they are on an ASA 5510 with 8.2.2. You cannot add ports tcp in the ACL sheep, it error when you try to apply the nat 0 access-list statement sheep (inside). We can define the ports to go down the VPN traffic interesting ACL with number, but there is no way to send just the web ports down the VPN and allow the other ports on regular overflow interface NAT I was look in 8.4 and see if it allows a policy NAT (twice the NAT for virtual private networks) to set a port to a range of IPS (IE (: nat static destination WEBINSPECT-WEBINSPECT (indoor, outdoor) static source a whole) but who only define as web ports.

I do not have an ASA test to use, but I guess that vpn l2l will be only by IP and I can not define a port tunnel.

In any case, it is a strange, but the ideas are welcome. I don't think it's possible, but I thought I'd see if anyone encountered at the front.

Hello

Well to give you a simple example where we use the double NAT / manual transmission NAT to handle traffic

For example a configuration example I just did on my 8.4 (5) ASA

The following configuration will
- Set the 'object' that contains the source network for NAT
- Set the 'object' that contains the service for NAT
- Define the real NAT
The real NAT is going to make any connection from the network under 'Wireless' network object to the destination port TCP/80 will be sent 'WAN' interface without NAT

Of course it is the next step with VPN L2L network under 'network wireless of the object' would correspond to the ACL of VPN L2L. But that seemed straight forward for you already

the subject wireless network

10.0.255.0 subnet 255.255.255.0

service object WWW

Service tcp destination eq www

NAT (WLAN, WAN) static source without WIRE WIRELESS WWW WWW service

The following configuration will
- Define the "object-group", that defines networks of the source of the rule by default PAT for Internet traffic
- Set the 'object' for the PAT address (could just use 'interface' instead of the 'object')
- Define the real NAT
The NAT configuration will just make a rule by default PAT for the wireless network. The key thing to note here is that we use the setting "auto after." This basically inserts the NAT rule to the priority of the very bottom of the ASA.

object-group, network WIRELESS-network

object-network 10.0.255.0 255.255.255.0

network of the PAT object - 1.1.1.1

host 1.1.1.1

NAT (WLAN, WAN) after the automatic termination of wireless - NETWORK PAT dynamic source - 1.1.1.1

Now we can use the command "packet - trace" to confirm that the NAT works as expected.

WWW TEST-TRAFFIC

ASA (config) # packet - trace 12355 1.2.3.4 entry WLAN tcp 10.0.255.100 80

Phase: 1

Type: UN - NAT

Subtype: static

Result: ALLOW

Config:

NAT (WLAN, WAN) static source without WIRE WIRELESS WWW WWW service

Additional information:

NAT divert on the output WAN interface

Untranslate 1.2.3.4/80 to 1.2.3.4/80

Phase: 2

Type: IP-OPTIONS

Subtype:

Result: ALLOW

Config:

Additional information:

Phase: 3

Type: NAT

Subtype:

Result: ALLOW

Config:

NAT (WLAN, WAN) static source without WIRE WIRELESS WWW WWW service

Additional information:

Definition of static 10.0.255.100/12355 to 10.0.255.100/12355

Phase: 4

Type: HOST-LIMIT

Subtype:

Result: ALLOW

Config:

Additional information:

Phase: 5

Type: NAT

Subtype: rpf check

Result: ALLOW

Config:

NAT (WLAN, WAN) static source without WIRE WIRELESS WWW WWW service

Additional information:

Phase: 6

Type: USER-STATISTICS

Subtype: user-statistics

Result: ALLOW

Config:

Additional information:

Phase: 7

Type: IP-OPTIONS

Subtype:

Result: ALLOW

Config:

Additional information:

Phase: 8

Type: USER-STATISTICS

Subtype: user-statistics

Result: ALLOW

Config:

Additional information:

Phase: 9

Type: CREATING STREAMS

Subtype:

Result: ALLOW

Config:

Additional information:

New workflow created with the 1727146 id, package sent to the next module

Result:

input interface: WLAN

entry status: to the top

entry-line-status: to the top

the output interface: WAN

the status of the output: to the top

output-line-status: to the top

Action: allow

TEST FTP - TRAFFIC

ASA (config) # packet - trace entry tcp 10.0.255.100 WLAN 12355 1.2.3.4 21

Phase: 1

Type:-ROUTE SEARCH

Subtype: entry

Result: ALLOW

Config:

Additional information:

in 0.0.0.0 0.0.0.0 WAN

Phase: 2

Type: IP-OPTIONS

Subtype:

Result: ALLOW

Config:

Additional information:

Phase: 3

Type: INSPECT

Subtype: inspect-ftp

Result: ALLOW

Config:

class-map inspection_default

match default-inspection-traffic

Policy-map global_policy

class inspection_default

inspect the ftp

global service-policy global_policy

Additional information:

Phase: 4

Type: NAT

Subtype:

Result: ALLOW

Config:

NAT (WLAN, WAN) after the automatic termination of wireless - NETWORK PAT dynamic source - 1.1.1.1

Additional information:

Definition of dynamic 10.0.255.100/12355 to 1.1.1.1/12355

Phase: 5

Type: HOST-LIMIT

Subtype:

Result: ALLOW

Config:

Additional information:

Phase: 6

Type: NAT

Subtype: rpf check

Result: ALLOW

Config:

NAT (WLAN, WAN) after the automatic termination of wireless - NETWORK PAT dynamic source - 1.1.1.1

Additional information:

Phase: 7

Type: USER-STATISTICS

Subtype: user-statistics

Result: ALLOW

Config:

Additional information:

Phase: 8

Type: IP-OPTIONS

Subtype:

Result: ALLOW

Config:

Additional information:

Phase: 9

Type: USER-STATISTICS

Subtype: user-statistics

Result: ALLOW

Config:

Additional information:

Phase: 10

Type: CREATING STREAMS

Subtype:

Result: ALLOW

Config:

Additional information:

New workflow created with the 1727154 id, package sent to the next module

Result:

input interface: WLAN

entry status: to the top

entry-line-status: to the top

the output interface: WAN

the status of the output: to the top

output-line-status: to the top

Action: allow

As you can see traffic TCP/80 corresponds to rule on the other. And the FTP used for example corresponds to rule by default PAT as expected.

If you want to know a little more about the new NAT 8.3 format + you can check a document I created

https://supportforums.Cisco.com/docs/doc-31116

Hope this helps you, please mark it as answered in the affirmative or rate of answer.

Naturally ask more if necessary

-Jouni

Preferred infrastructure: alarm on the port down

Hi all

Given that we have improved our PI to 2.0.0.0.294 version last week, we receive several alarms a day regarding the port on wlc.

Here is an example:

Virtual domain: DOMAIN-ROOT

PI has detected a change in one or more alarms category controller and critical severity.

The new severity of the following is clear:

1. message: "3" Port is down on the device "x.X.X.X". -Controller name: XXXXXXXXXX

(3 times)

2. message: Port '4' 'x.X.X.X' device is idle. -Controller name: XXXXXXXXXX

(3 times)

3. message: Port '5' is down on the device "x.X.X.X". -Controller name: XXXXXXXXXX

(3 times)

4. message: Port '6' appliance 'x.X.X.X' is inactive. -Controller name: XXXXXXXXXX

(3 times)

5. message: Port '6' appliance "y.y.y.y" is inactive. -Controller name: YYYYYYY

(3 times)

E-mail will be deleted up to 30 minutes for these changes.

I checked all the mentioned ports and they are not in use and not physically connected. I put "admin status" of these ports as 'disable' and 'link trap' like disable too, but we continue to receive these alerts.

Do you know if this is a bug related to PI v2? or what I can do to remove these false alarms?

Thank you!

I saw these on NCS too... and I still see it on 2.0 FT I have running.

Thank you

Scott

Help others by using the rating system and marking answers questions as 'response '.

Port of heart beat Vmkernal of storage for table Equalogic PS

Dell has just installed a new EQL PS SAN and configured for our 5 x ESXi hosts 5.0U1. Each host has 2 10 GB NIC have inaugurated a vswitch dedicated for iSCSi connections to the SAN. MPIO is via the driver of Dell MPIO add-on.

They are configured so as to VMK 2 ports iSCSi1 ands iSCSi2 1:1 as usual. However, as Dell has left, I came across a Dell/EQL (TR1075-Configure-iSCSI-Connectivity-with-VMware-vSphere-5.pdf) white paper that says that a separate vmk port must be configured to maintain "pingability' of the iscsi ports during failure/failover. This port must have an ip address on the iSCSi subnet and 2 10GB network adapters must be active in the team but are not related to the iSCSi adapter. It should also be the port down vmk not.

The following positions in various net forums seem to suggest this is very important: -.

http://communities.VMware.com/message/1877959

http://www.LinkedIn.com/groups/new-guidelines-VMware-iSCSI-65187.S.89647775

http://sostech.WordPress.com/2012/01/10/iSCSI-multipath-for-EqualLogic-round-3/

If it is there, it is easy to create the additional vmk but how I would make the lowest port without deleting existing ports and access of SAN interupting.

Kind regards

Gerry

5.1 ESXi does not resolve the problem, then the kernel of Heartbeat of storage (SHB), is no longer necessary.

However, with ESXi v5.0 you don't have to remove the two ports VMK and start from scratch. You can unbind the VMK port below via the GUI ESX. Then, change the network cards so that both are active. Then create a NEW VMK port in this subnet that has bound to the iSCSI HBA to replace the port lowest VMK used for SHB.

Tektronix AFG 3253 USB question

I'm having some problems with running a test of long duration (100 + hour) with a Tek AFG 3252. I was using a converter USB / GPIB to communicate with him. For some reason any USB port down and he refused to communicate after that and the settings are pasted on the AFG. The issue seems to occur at random times and after a while.

I checked the USB sleep on the port settings and it is not permissible to put he's asleep. I also tried to use a hub USB powered and it does not solve the issue.

I will try to convert the right USB communications today or tomorrow and see if that makes a difference. If I can't make it work reliability with USB I'll try Ethernet. We had a problem like this with a range of Tektronix finally had to convert the comms in Ethernet.

Has anyone else had a problem like that? If so what did you do to solve?

Does anyone know if there is a sniffer software and/or hardware that can be used for USB ports? I would like to know if there are any detectable reason this port is stalled.

The problems get fixed if the USB cable is unplugged and plugged in the back. I saw an article on the realization of a software new departure of a USB port. Has anyone tried this before? If it works, I'll have to make sure I can detect an error indicating that a reboot is necessary. Is it possible a hardware switch that I can put in line with the USB port which will create the physical disconnect with digital or software control and does not interfere with the characteristics of the physical layer?

Thanks for your help.

You run Windows by chance? I had a similar problem a while crossing a field of Tektronix USB. After a few hours the connection would be deleted and I had to reconnect the USB and restart LabVIEW to resume the connection. In my case, the solution was to turn off the selective suspension of USB in Windows power settings. My understanding is that Windows, in an effort to save energy, turn off USB ports apparently at random. On Windows 7, go to the Power Saving settings > change Plan settings > change advanced power settings > USB settings > USB selective suspend framework. Of course, this might be different in other versions of Windows. If you do not use Windows, then your question is probably something different altogether so feel free to ignore this message.

USB docks/pass-through/techniques...?

Does anyone know if Motorola (or any third-party company) has any plans to release a better dock for the Xoom, preferably one at least a USB port? I have a kind of doubt Motorola will be at this stage, but it would certainly many of us happy that I am sure!

I would like to see me mind not so much, but when you use the USB host adapter/cable I can't configure my Xoom in my portfolio case correctly because the port is down and stop to rest in one of these positions correctly. So if anyone has found a solution which doesn't involve propping it against something or leave this dish? Thanks in advance for any idea!

@kidroboto,

I doubt we'll see any change to the docking station, bur it is a simple solution for this in the case of portfolio. When I use one of the ports on the Xoom while in the case, I simply turn the Xoom upside down (with the ports on the TOP) and the place he put the case (automatic rotation must be turned on).

I also bought a pair of bent of cable USB OTG (host) and a HDMI cable right angle than the excellent work with the Xoom and are not as inclined to be broken (low profile). Besides the cables, I found a portable easel on Amazon that holds my Xoom (when not in the case of portfolio) and has plenty of clearance for these same right angle when facing with the ports down cables. Let me know if you are interested in one of these cables and I can give you the links.

-Doc

players

I would like something similar to an i House but is compatible with my Sansa Fuze + please help

Your subject line is prominent. It looks like what you're asking for is a device of type dock to play your rocket + through, is that correct?

Since the Fuze + doesn't have a connection port down there not made for it as the pod series. However, any device that you can connect to a 3.5 mm plug can be plugged into the headphone jack of your rocket + and plays through the system. You wouldn't be able to control the Fuze + by (or with) the controls or remote controls on the media base if. You would control volume and selection of the railway, etc. on the drive itself. essentially by the speakers on the dock.

The rocket + uses a micro-USB for data and charging connector, but even I know there is no output line for a dock - as the device can be done by.

EMC Ex3 - 40f, Qlogic ISP 2432 and RHEL 4 x86_64

I have a blade of 1855 w / daughter CF card. The OS is RHEL AS 4 update 5 x86_64. I recently installed this OS and have it connected to an EMC3 40f, which presents this host w / 100GB RAID5 LUN. First of all, I did this: (orders in "BOLD", released in BLUE)

1. register with RHN

2 up2date rpm-build redhat-config-RPM

3. up2date - get-source kernel

4. rpm-ivh /var/spool/up2date/kernel*.src.rpm

5. cd/usr/src/redhat/SPECS

6 rpmbuild - bp - target = x86_64 kernel - 2.6.spec

7. cp-a /usr/src/redhat/BUILD/kernel-2.6.9/linux-2.6.9/usr/src

8. ln-s /usr/src/linux-2.6.9 usr

The steps above were made so that these steps should compile without any problem

9 tar - xvf qla2xxx - v8.01.00 - 3dkms.tar.gz

10. rpm-ivh dkms - 2.0.5 - 1.noarch.rpm

11 rpm - ivh qla2xxx - v8.01.00 - 3dkms.noarch.rpm

Step 11 will produce the following:

Preparing... ########################################### [100%]
1:qla2xxx ########################################### [100%]

Create a symbolic link /var/lib/dkms/qla2xxx/v8.01.00/source->
/usr/src/qla2xxx-V8.01.00

DKMS: Add Completed.

Construction of module to the kernel running has been ignored since the
for this kernel kernel sources does not appear to be installed.

Hmm... I thought that I just added the CBC core following steps 1 through 8. These steps are listed here: http://kbase.redhat.com/faq/FAQ_85_5109.shtm

I also installed the EMCPower. Linux - 5.0.0 - 157.rhel.x86_64.rpm under the default location. It has now SANsurferCLI and SANsurfer (gui).

When I rebooted the machine, I see dmesg:

HBA QLogic Fibre Channel adapter driver
ACPI: PCI Interrupt 0000:02:00.0 -> GSI 16 (level, low)-> IRQ 169
qla2400 0000:02:00.0: found an ISP2432, irq 169, the iobase 0xffffff0000014000
qla2400 0000:02:00.0: PCI configuration space...
PCI: The timer setting of latency of the device 0000:02:00.0 to 64
qla2400 0000:02:00.0: NVRAM configuration settings...
qla2400 0000:02:00.0: audit loaded RISC code...
qla2400 0000:02:00.0: allocated (1061 KB) to dump the firmware...
qla2400 0000:02:00.0: waiting for LIP finish...
qla2400 0000:02:00.0: LIP reset occurred (f7f7).
qla2400 0000:02:00.0: LOOP UP detected (2 Gbps).
qla2400 0000:02:00.0: topology - (F_Port), loop 0 host address 0 x
SCSI1: qla2xxx
qla2400 0000:02:00.0:
Adapter HBA QLogic Fibre Channel driver: 8.01.04 - d8
QLogic QME2462 - Dell B S PCI-Express to 4Gb FC Dual Channel
ISP2432: PCIe (2.5 Gb/s x 4) @ 0000:02:00.0 hdma + host # 1, fw = 4.00.23 =
Seller: DGC model: LUNZ Rev: 0324
Type: Access Direct ANSI SCSI Revision: 04
qla2400 0000:02:00.0: scsi(1:0:0:0): activated tagged depth of queue lines, 32.
SDB: READ CAPACITY failed.
SDB: State = 1, message = 00, host = 0, driver = 08
Current SD: sense key illegal request
Additional detection: logical unit not supported
SDB: asking cached data failed
SDB: assuming drive cache: write through
SDB: READ CAPACITY failed.
SDB: State = 1, message = 00, host = 0, driver = 08
Current SD: sense key illegal request
Additional detection: logical unit not supported
SDB: asking cached data failed
SDB: assuming drive cache: write through
SDB:end_request: i/o error, dev sdb, sector 0
Buffer I/O error on device sdb, logical block 0
end_request: i/o error, dev sdb, sector 0
Buffer I/O error on device sdb, logical block 0
end_request: i/o error, dev sdb, sector 0
Buffer I/O error on device sdb, logical block 0
Failed to read the partition table
Attached scsi disk sdb at scsi1, channel 0, id 0, lun 0
Attached scsi generic sg2 at scsi1, channel 0, id 0, lun 0, type 0
Seller: DGC model: LUNZ Rev: 0324
Type: Access Direct ANSI SCSI Revision: 04
qla2400 0000:02:00.0: scsi(1:0:1:0): activated tagged depth of queue lines, 32.
SDC: READ CAPACITY failed.
SDC: State = 1, message = 00, host = 0, driver = 08
Current SD: sense key illegal request
Additional detection: logical unit not supported
SDC: asking cached data failed
SDC: assuming drive cache: write through
SDC: READ CAPACITY failed.
SDC: State = 1, message = 00, host = 0, driver = 08
Current SD: sense key illegal request
Additional detection: logical unit not supported
SDC: asking cached data failed
SDC: assuming drive cache: write through
SDC:end_request: error e/s, dev SDC, sector 0
Buffer I/O error on device DSC, logical block 0
end_request: error e/s, dev SDC, sector 0
Buffer I/O error on device DSC, logical block 0
end_request: error e/s, dev SDC, sector 0
Buffer I/O error on device DSC, logical block 0
Failed to read the partition table
Attached scsi disk SDC at scsi1, channel 0, id 1, lun 0
Attached scsi generic sg3 at scsi1, id 1, channel 0, lun 0, type 0
ACPI: PCI Interrupt 0000:02:00.1 -> 17 of GSI (low)-> IRQ 193
qla2400 0000:02:00.1: found an ISP2432, irq 193, the iobase 0xffffff0000016000
qla2400 0000:02:00.1: PCI configuration space...
PCI: The timer setting of latency of the device 0000:02:00.1 to 64
qla2400 0000:02:00.1: NVRAM configuration settings...
qla2400 0000:02:00.1: audit loaded RISC code...
qla2400 0000:02:00.1: allocated (1061 KB) to dump the firmware...
qla2400 0000:02:00.1: waiting for LIP finish...
qla2400 0000:02:00.1: cable is disconnected...
SCSI2: qla2xxx
qla2400 0000:02:00.1:
Adapter HBA QLogic Fibre Channel driver: 8.01.04 - d8
QLogic QME2462 - Dell B S PCI-Express to 4Gb FC Dual Channel
ISP2432: PCIe (2.5 Gb/s x 4) @ 0000:02:00.1 hdma + host # 2, fw = 4.00.23 =
Insert the floppy driver for 2.6.9 - 55.ELsmp
Floppy drive (s): fd0 is 1.44 M
floppy0: not found floppy disk controller

However, when I run the SANsurferCLI, it shows no. HBA connected. I cannot fdisk the LUN. I get:

[root@xxx ~] # fdisk/dev/sdb

Unable to read/dev/sdb

[root@xxx ~] # mkfs - v-j/dev/sdb
mke2fs 1.35 (February 28, 2004)
/ dev/sdb whole device, is not just a partition.
Still? (y, n) y
WARNING: could not delete sector 2: try to write the file system blocks resulted in brief writing
Filesystem label =.
OS type: Linux
Block size = 4096 (log = 2)
Fragment size = 4096 (log = 2)
131072 inodes, 262144 blocks
13107 blocks (5.00%) reserved for the super user
First data block = 0
Maximum filesystem blocks = 268435456
8 groups of block
32768 blocks per group, 32768 fragments per group
16384 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840 229376

WARNING: could not read block 0: try to read the file system block resulted in short read
WARNING: could not delete sector 0: try to write the file system blocks resulted in brief writing
Writing inode tables: fact
Creating the journal (8192 blocks): fact
Writing Superblocks and filesystem accounting information:
Attention, was struggling to write to superblocks.done

This file system will be automatically checked all 38 media or
180 days, whichever comes first. Use tune2fs - c or-i to substitute.

I expect that to happen. Included here for clues:

[root@xxx ~] # mount/dev/sdb/san/01 /
/ dev/sdb: input/output error
Mount: / dev/sdb: cannot read the superblock

The output of/proc/scsci/qla2xxx/1:

[root@xxx qla2xxx] # 1
QLogic PCI with Fibre Channel for QME2462 host adapter:
4.00.23 firmware version , Driver version 8.01.04 - d8
INTERNET SERVICE PROVIDER: ISP2432
Ask the queue = 0 x 215580000, queue response = 0x215d10000
Ask account queue = 4096, the response queue = 512 count
Total number of active orders = 0
Total number of interruptions = 12855
Device queue depth = 0 x 20
Number of entries free request = 3592
Number of time-outs of the mailbox = 0
Number of ISP abandons = 0
Number of the loop = 0 Resync
Number of retries for empty slots = 0
Number of requests in pending_q = 0, retry_q = 0, done_q = 0, scsi_retry_q = 0
Adapter: loop State host = , flags is 0x1e03
DPC flags = 0 x 4000000
Flags MBX = 0 x 0
Link down Timeout = 045
Port down retry = 045
Number of connection attempts = 045
Dropped orders retried with image (s) = 0
Product ID = 0000 0000 0000 0000

The SCSI device information:
SCSI-qla0-adapter-node = 200000e08b9b8968;
SCSI-qla0-adapter-port = 210000e08b9b8968;
Qla0-SCSI-target - 0 = 5006016941e07929;
Qla0-SCSI-target - 1 = 5006016041e07929;

FC Port information:
SCSI-qla0-port-0 = 50060160c1e07929:5006016941e07929:c302ef:81;
SCSI-qla0-port-1 = 50060160c1e07929:5006016041e07929:c303ef:82;

Information about the SCSI LUN:
(Id: Lun) *-indicates the logical unit number is not registered with the operating system.
(0: 0): total reqs 12595 pending reqs 0, flags 0x0, 0:0:81 00
(1: 0): flags of reqs total 130, in anticipation of reqs 0, 0 x 0, 0:0:82 00

So can someone indicate on WHAT I'm doing wrong? I am open to reinstall the operating system for the same version (LIKE 4u5 x86_64).

Thank you.

UCS < 1.4.2b >, N1K and uplink

Hi all

I have a UCS (cluster) connected in vPC mode to a Nexus 7010.

UCS 4.1U1 VMware ESXi, N1K with EHM PC blade-based UCS NIC is 71KR.

Question is what happens if the two uplink of interconnection fails? I mean maybe cut fibres or stuff like that. N1K channel will be still two active link?

Maybe the redundancy is performed by re arping for finding a mac (i've got UCS in switch mode) address, but I'm not sure. I saw a feature in the new version for a link status tracking rising full failure handling system (how?).

last question about redundancy... what happens if a UCS IOM resets? I have some traffic disruption?

TNX

Dan

Dan,

Just to be clear, check the following:

-UCS in switch mode

-Adapters M71KR

-N1k using Mac-pinning (I guess)

-Connectivity upstream of each FI is a VPC to a pair of N7Ks.

In this case, the N1K has no visibility of uplinks UCS. See all your hosts VEM are two uplinks for each host (a session each fabric interconnect.) If one of the two uplinks fails on interconnection, traffic will be the uplink remaining on this FI re-hairpin. If the TWO uplinks on a financial institution fail, then UCS will be down (called the link at the bottom) server links and traffic should be routed through the MEC is another uplink will the other. You can change this behavior to follow links to Server (for local switching only) but the default action of UCSM's close links to corresponding server if there are no links available on a financial institution. Make sense?

Now, in the last version of N1K here (1.4) is a new feature called followed by the State of the network (NST) for use with VPC - HM (such as Mac pinning). This feature will allow to test the connectivity of a VLAN sends a probe packet and expect to get fired on another group of liaison rising/sup. If you have a network VLAN which SHOULD be identified, you can follow with TSN. If the network becomes unavailable, you can choose to close the uplink and re - route traffic to an another uplink. This is useful to detect failures beyond the first jump (which would be the interconnections) as a failure somewhere in your N7K level or beyond.

Setup Guide: http://www.cisco.com/en/US/partner/docs/switches/datacenter/nexus1000/sw/4_2_1_s_v_1_4/interface/configuration/guide/n1000v_if_5portchannel.html#wp1284321

White paper: https://communities.Cisco.com/docs/doc-20657

Order code: http://www.cisco.com/en/US/docs/switches/datacenter/nexus1000/sw/4_2_1_s_v_1_4/command/reference/n1000v_cmds_t.html#wp1295608

For your last question about a failure/reset of the IOM, the cards corresponding to each blade will lose connectivity. This is redundancy at the host level comes into play to reroute traffic. In the case of your hosts N1K VEM, they would simply be re - route traffic on the access road to functional IOM of the chassis.

Another point to consider is the M71 and M81 adapters support Fabric Failover. He is tilting at the adapter level if there is a failure with any device between the adapter and uplink (like the IOM or FI). Fabric failover is a configurable option adapter which re - will route traffic in Menlo ASIC adapters to the fabric in the 'other', such that the host will NOT see one of the two ports down. Without switch fabric, a failure of a MOI or FI consider the adapter and this port would descend. FF only adds a level of redundancy in the adapter without having to rely on any OS host grouping/failover. M51KR, M61 KR and M72KR adapters do NOT support this feature.

Kind regards

Robert

What is a traffic LOOP Ethereal?

Hi all

I am stable and by analyzing the packet captured in ethereal.

but I can't know the traffic of LOOP.

I connect two mutually routers with fast ethernet.

R1 ------------------------------------- R2

fa0/1 fa0/1

then R1 and R2 send traffic LOOP each other by 60 dry.

Card fast ethernet R1 MAC: 00: 1a: 6 c: fe: 49:80

Card fast ethernet R2 MAC: 00: 1a: 6 c: 70:7 has: 66

Where R1 and R2 are connecting between them and no configuration is not applied in this interface.

R1 sends LOOP frame in the media as below

source_MAC: 00: 1a: 6 c: fe: 49:80

destination_MAC: 00: 1a: 6 c: fe: 49:80

Finally, source_MAC and destination_MAC is the same.

What is this image?

is this keepalive framework?

Why R1 sends frame LOOP which use the same MAC (source and destination MAC)

If R1 sends the frame above LOOP,

I think that R2 will ignore it as destination MAC is not Mac of R2

is for this reason that R1 sends LOOP frame just to test the State of the media?

I have attached the file CAP captured.

You can find this number in strange package number (1,3, 5...)

Hello Peter,.

This is my current understanding of the keepalive ethernet.

If I take an Rj-45 ethernet port for example ethernet to a 4th PA and I leave it unplugged the interface is down/down

If the port unplugged I disable keepalive (no keepalive under config interface) ports rises and it's even pings (because when ping interface ethernet, that the packet is not sent on the wire as it happens with serial number or ATM interfaces).

Ethernet interfaces have no carrier detect and no Management TDM to be detected.

My first idea was that keepalive frames were sent with SA MAC router = NIC MAC and MAC DA = broadcast.

I did some research and most of the links point to the following:

http://www.mit.edu/~jhawk/CTP.PDF

http://LWN.NET/articles/330797/
```
ECTP packets can be sent to unicast, broadcast, or the ECTP reserved

+       cf:00:00:00:00:00 multicast address
```
> If the frame of the LOOP was supposed to be received in return, what action would be if it wasn't back?

See above, to consider the port down

receving save his own keepalive frames is that a sign of a loop for me is linked to a famous bug on C3750 and other switches to fibers according to ports where workaround suggested was to disable keepalive on these ports.

This bug has been through several discussions in the forums.

It is reasonable that if the goal is to test the ability to send and receive ethernet frames a test with a frame sent the wire and then received back would be the most significant.

Sebastin:

http://wiki.Wireshark.org/loop

We are talking about something so fundamental, that the received frames could be simply ignored and not transmitted to the upper layers as suggested above documents. I'll watch again how you did your tests.

I'm willing to change my mind again about it as I did many times in the past.

Hope to help

Giuseppe

I have an old Mac Mini with a DVI Port that came with a VGA DVI-adapter. Tonight, my monitor went down. Brand new monitor works with that? Can I use an adapter? If yes should which adapter I?

I have an old Mac Mini with a DVI Port that came with a VGA DVI-adapter. Tonight, my monitor went down. Brand new monitor works with that? Any recommendations? Can I use an adapter? If yes should which adapter I?

You can use any DVI monitor DVI port directly or have any VGA monitor with the power that you adapter. A HDMI monitor might work with an adapter DVI to HDMI in a pinch, but HDMI tends to be more fickle.

Port of uplink on PowerConnect 8024F went to the D State down

Hi all

We had a strange behavior on one of our switches PowerConnect 8024F. The uplink port of the device (connected to a port on a Cisco Catalyst 6513 10Gig) came down. The output of 'show interfaces status' looked like this:

Port speed Duplex Neg frothing link Description
Status of the State
--------- ------------------------- ------ ------- ---- ------ ------------
TE1/0/1 cat6500-rz-1 (te11/2) 10000 Full Off D-low idle
TE1/0/2 pc8024-ub-1 (te1, 0, 1) complete 10000 Off place Active
TE1/0/3 pc8024-uv-1 (te1, 0, 1) complete 10000 Off place Active
TE1/0/4 pc5500-naf02n-1 (te1, 0, 1) complete 10000 Off place Active
TE1/0/5 pc5500-naf04n-1 (te1, 0, 1) complete 10000 Off place Active
TE1/0/6 pc5500-naf03-1 (te1, 0, 2) 10000 Full Active Off
TE1/0/7 pc8024-mensa-1 (te1, 0, 1) complete 10000 Off place Active
Defekt TE1/0/8 n/a unknown inactive low Auto
TE1/0/9 pc5500-naf03-2 (te1, 0, 1) complete 10000 Off place Active
TE1/0/10 pc5500-naf03-3 (te1, 0, 1) complete 10000 Off place Active
...

.. and so on. Firmware is 5.1.2.3. We rebooted the device and he returned to normal behavior.

Now, can someone explain to me what the "D-Down" State means? I have not found anything in the documentation and using google not any success.

The configuration of the port looks like the following:

Description ' cat6500-rz-1 (te11/2).
MTU 9216
switchport mode general
switchport general allowed vlan add 4-5, 14, 22-2729-33, 36, 39-41, 43 tag
switchport general allowed vlan add 47,51-52,54-56,58-60,63-64,66,75,78-79 tag
switchport general allowed vlan add 81, 86-90, 93-99, 107, 120, 122 tag
switchport general allowed vlan add 124 132 - 135, 137, 140, 142-143 147-152 154 tag
switchport general allowed vlan add 156-157, 160, 165-166, 171, 173-175 the tag
switchport general allowed vlan add 177-178 180-181, 183, 189, 192, 195-196 the tag
switchport general allowed vlan add 199,201,203-205 207-208 210-212 the tag
switchport general allowed vlan add 219-222 224-225 227-233 235-244 246 tag
switchport general allowed vlan add 248-249, 253, 256, 258-260 262-267 tag
switchport general allowed vlan add 269-272 274-276 278-279, 282, 284, 286-288 the tag
switchport general allowed vlan add 292 295 - 298, 323, 344, 347, 349 tag
switchport general allowed vlan add 354,362,366,370,372,378-380 382-383 385-386 tag
switchport general allowed vlan add 391,399,405,431,443,447 tag
switchport general allowed vlan add 475-476, 485, 488, 511, 522, 584, 700-703 710-714 tag
switchport general allowed vlan add 725,734,838,854-855 909 tag
switchport general allowed vlan add 950 961 - 962, 981, 999, 1234, 1236, 2205, 2218-2220 tag
switchport general allowed vlan add 2222,2233,2414,2417 tag
switchport general allowed vlan add 2506-2507, 2519, 2521, 2621, 2699 tag
Access-group PVST Mac - filter 1
LLDP transmit tlv sys - name sys - cap
LLDP transmit-mgmt

The used mac filter access PVST-group is:

Mac-extended access list filter-PVST
refuse any 0100.0CCC. RCC 0000.0000.0000
allow a full
output

Thanks for reading and suggestions!

Robin

It's all associated spanning-tree protocols. D to the bottom is synonymous with diagnostic downwards, which occurs if more than 15 BPDU per second is received during 3 seconds. The switch closes the port. USL worker task is bound traffic so a big change covering tree cause it's really high.

USB ports have power when the PC is shut down. Power supply connected to the battery.

PC is HP G62 - 222us W7 64-bit. When the PC was first powered, they gave me the option to allow USB ports ON or OFF after his stop. I chose IT, but now I want ports USB OFF after his stop. I can't remember have this option is found. Any help would be great. Thanks in advance for your help...

I found my answer: Control Panel Goto (W7), search for 'power', click "Change the Power settings", click on "USB settings", click on "USB selective suspend parameters", for the battery, select "Disable", except change, click OK.

Now, all USB PORTS are INACTIVE when the PC is shut DOWN.

Wireless use USB ports locks and prevents the Windows shut down

Hi all. Faced with this one.

Computer is the laptop, HP Pavilion DM4 - 1150ca. 4 GB of Ram, 150 GB HD

OS Win 7 Home Premium 64-bit, SP1 and latest updates installed

Problem: I have 3 ways to connect to the internet: 1 Dongle USB (Device Manager calls "Remote NDIS based internet device for sharing". No problem connecting to the network and to the internet with this device. 2. built in WiFi adapter, "Intel Centrino Wireless - N 1000 and 3. External antenna for high power USB and USB «Realtek RTL8187» adapter Medium 1 and 2, I can normally connect to the network, get decent speed but he declines quickly and then to a random period, usually within a few minutes, I lose my internet connection, and finally my network shows disconnect icon. At this stage all 3 of my USB ports are locked up, removal of the WiFi device does nothing, don't disconnect sound and no USB device is recognized if I try their connection. In addition, Windows will not stop. I get a "shutting down" screen but it stays that way until the expiration time and finally restarts, screen asking if I want to start normally or in safe mode.

Action taken:

Several online sites checked and tried solutions including:

RTL8187 uninstalled and reinstalled several times

Uninstalled and reinstalled HP wireless several times

Deleted (Device Manager, see all) entries while grayed, unused network

So far, no joy, no change. Anyone have any new ideas? Thanks for any help

Hi Raven,

Do you have third-party security programs installed on the computer?

Basically, if the internet works in safe mode and not works in normal mode, not applications or third-party security programs can be in conflict with the drivers from the internet.

As a solution, I suggest to uninstall the anti-virus program and check if it works in normal mode.

Warning: Antivirus software can help protect your computer against viruses and other security threats. In most cases, you should not disable your antivirus software. If you need to disable temporarily to install other software, you must reactivate as soon as you are finished. If you are connected to the Internet or a network, while your antivirus software is disabled, your computer is vulnerable to attacks.

Answer with the results so that we can help you even the question.

Keep the power to the USB port after stopping down?

I would use one of the USB ports to plug in my cell phone to load from one day to the next off the computer. What are the steps to follow to set computer to keep providing power via USB ports after shutting down the computer? I'm a novice so need to know where to find the place that controls the settings and what to click on. Thank you!

If you put the computer in Standby Mode when you stop, the USB ports are not powered off.

Port down...

Similar Questions

Maybe you are looking for