Nexus 5548 - PFMA-2-PS_HIGH_VIN message on device with DC power supply

Hi,
we got following message on Cisco Nexus 5548 (NX-OS 6.0(2)N2(3)):
2014 Aug 25 06:41:11 MO-BPROD-AS-N5k-1 %PFMA-2-PS_HIGH_VIN: Input Voltage 1023
exceeded maximum threshold of 250V for Power supply 2.
2014 Oct 18 14:12:10 MO-BPROD-AS-N5k-1 %PFMA-2-PS_HIGH_VIN: Input Voltage 1023
exceeded maximum threshold of 250V for Power supply 1.
Strange thing is that power supplies at Nexus are DC (48 Volts), not an AC.
I serach at Cisco Error Message decoder and didn't find anything.
At Nexus 6000 (we have Nexus 5500) System Messages document I found this:
Error Message PFMA-2-PS_HIGH_VIN: Input Voltage [dec] exceeded maximum threshold of 250V for Power supply [dec].
Explanation Input Voltage has exceeded higher threshold of 250V for Power Supply
Recommended Action Please perform a showenvironmentpower'and'showplatforminternalinfo'tocollectmoreinformation.'
But, there is no any useful info from this commands (just first command works).

Hi,
1. The connection setup looks fine to me for a single ended measurement - you may want to connect to 68 and 32 for differential measurements.
3. The example should be ready to take measurements
4. The Data Acquisition card forces the input range to a valid value - 8V is not a valid range and it will be coerced to 10V - this is expected.
5. I am not sure why its not letting you cahnge the channel but a good way to test you hardware is by opening up a test panel in Measurement and Automation Explorer - can you try that and let me know?
Hope this helps!
Abhinav T.
Applications Engineering
National Instruments India
LabVIEW Introduction Course - Six Hours
Getting Started with NI-DAQmx
Measurement Fundamentals

Similar Messages

Supplying CAN devices with bus power

Hello everyone,
Is it possible to provide bus power to a CAN device with a PCI-CAN Series 2 card?
The manual is a little confusing in this matter. Table 4-1 in the manual states that V+ is "Optional CAN power supply if bus power or external VBAT is required." This makes me think that I can supply a CAN device with bus power from the card's internal source (as long as my jumper is configured for internal).
A few lines later the following statement is made: "V+ supplies bus power to the CAN physical layer if external power is required...it is not necessary to supply V+, unless you have configured the VBAT jumper for EXT." This makes me think that V+ has nothing to do with supplying power to devices, and only with powering the bus on the card itself.
If it is not possible to supply bus power with the NICAN card, what is the recommended method for powering a device on the same CAN network (assuming the device is not powered somewhere in its own circuitry)?
Thanks for any help,
Dave

Hi Dabramsom,
the part of the manual that I assume you are referencing is:
   "V+ supplies bus power to the CAN physical layer if external power is
   required. All High-Speed Series 2 PCI, PXI, and USB hardware is powered
   internally, so it is not necessary to supply V+, unless you have configured
   the VBAT jumper for EXT."
The PCI-CAN/2 cards can be powered either internally or externally.
To power the device externally the VBAT jumper should be configured for EXT,
now your card will be powered by an external source, your card cannot be
configured to be the source for another device. Please reference the following KnowledgeBase:
What Do the Power Jumper Settings on the NI-CAN Cards Mean?
As for powering your CAN device it really depends on your device; what are the power
specifications? Can you consider using a battery?
I hope this answers your questions.
Christian A
National Instruments
Applications Engineer

Why are my purchases made on one device showing up as "waiting" to download on my other devices, until I plug those devices into a power supply?

Any time I make a purchase on one device, say my Mac Book, the items show as "waiting" in the downloads area of my iPad and iPhone. Once I plug those devices in to a power supply, they begin to download.
note that automatic downloads in all format types are turned on on all devices.
Any ideas on if there's a power setting that I can change somewhere to make it NOT a requirement that my devices be plugged in to automatically download?? I know you are all shocked to hear this, but I did not have this problem prior to iOS 8. (Both my iPad and iPhone have 8.1)

The iPod has to be powered on, and it has to have a live wifi connection. If it is not showing up it may be powered off, the battery may have died, it may be in sleep mode (the wifi radio is off in sleep mode when running on the battery), or it may not be in range of any known wifi networks.
Also, since the tracking feature is a function of iCloud account credentials, if the device has been reset as new, then your daughters iCloud account and its settings will have been erased. In that case, the device will never show up again.
If the device did not have a passcode lock and/or account restrictions enabled on it, then anyone finding it could also go into the iCloud account settings and disable the "find my iPod" setting.

Use devices with USB without supplying charging

is it possible, say via an app or a terminal command, to tell OS X Mavericks to stop charging connected devices and just let them use for other purposes like sending data.
for example, i use my macbook air for ios development (making my first app) and connect my iphone to the air to load my app to test it. i dont want my phone to derive charging current from the air as i dont want an unnecessary drain of my laptop's battery.
Neerav

I don't think so. Make sure your iPhone is fully charged and the battery drain should be negligible.

Power supply for Nexus gear

I need to migrate devices off of 110v and move them over to 208v. I was wondering if there would be any risk moving one side to 208v while the other is still connected to 110v on the Nexus 7 and 5K switches, or would it be best to take down the device all together then make the change?

For the DMP-4400G:
Part# is DMP-4400-ACC-KIT=
(Accessory Kit)
For the DMP-4305G:
Part# is DMS-DMP-4300G-KIT
NOTE: The ACCESSORY KIT does come with the Power supply
for the DMP. However, the power cable is a separate
configuration item that needs to be ordered separately.
I hope this helps!
T.

Cisco Nexus 5548 device

Hi,
Can you please let me know how to get (command) Manufacture date for Cisco Nexus 5548 device.
Appreciate your support.
Thanks,
Brahma

Hi Brahma,
I dont believe there is a command which would give you the Manufacture date directly, however there is an old theory which speaks about decoding the date of manufacture from the serial number.
Excerpt is as captured below:-
The date code is built into the serial number. The format is LLLYYWWSSSS, where:
LLL is the location at which the unit was built.
YY is the year that the unit was built (1997=01, 1998=02, 1999=03, 2000=04).
WW is the work week of the year that the unit was built.
SSSS is the serial number.
Else the account rep would be able to give more details by backtracking the serial number to the inventory.
HTH,
S@G@R

Telephony Issues on Nexus 5548

Dear Viewers,
I have Nexus 5548 devices in one of my client data centers and i have one 3750 switch to which all of these Avaya voice servers connect.
The 3750 switch was initially connected through a L2 Link to a 6509 catalyst switch and the telephony applications were working correctly.
The problem arises when i move this 3750 layer 2 link to a Nexus 5548 (OS version 5.1(3)N1 switch. All telephony calls coming from the outside (External calls) are not working as required but the internal calls work as usual.
What is odd is that when i migrate this L2 link back to the 6509 switch, all works as usual. This is just a layer 2 connection and i am wondering why this is not possible.
The vlan is accepted on all relevant trunks. I also deactivated igmp snooping on this voice vlan on the Nexus 5548 thinking it would help but in vain.
Any ideas and suggestions are welcome.
regards.
Alain

This is my radius config...... on a 5K
radius-server timeout 7
radius-server host 10.28.42.20 key 7 "Password" auth-port 1645 acct-port 1646 authentication accounting
radius-server host 10.28.42.21 key 7 "Password" auth-port 1645 acct-port 1646 authentication accounting
aaa group server radius Radius-Servers
server 10.28.42.20
server 10.28.42.21
aaa authentication login default group Radius-Servers
ip radius source-interface Vlan1
aaa authentication login default fallback error local
And it is currently working. On the radius server i also had to do this to make the users admins once logged in:
https://supportforums.cisco.com/document/137181/nexus-integration-admin-access-free-radius

Fabric with two Nexus-5548 and a brocade switch does not get fabric updates

We have a fabric containing two Nexus 5548 and a Brocade 5000 switch in interop mode 2. When i make changes to the zoning, the first nexus (the fabric principal) and the brocade switch see the zone changes. The second Nexus switch does not see it. There are no error messages but the change just can't be seen. What can i do to find out, what goes wrong ?

Ouch, deprecated is not the word i wanted to read
We are using 5.1(3)N1(1a) on nexus-rz1-a
and 6.0(2)N1(2) on nexus-rz2-a.
The fabric can be seen :
nexus-rz2-a# show fcs ie vsan 10
IE List for VSAN: 10
IE-WWN                   IE     Mgmt-Id Mgmt-Addr (Switch-name)
10:00:00:05:1e:90:57:27 S(Rem) 0xfffc01 10.88.133.110 (bc-san1)
20:0a:00:2a:6a:72:ba:01 S(Loc) 0xfffc1c 10.88.133.105 (nexus-rz2-a)
20:0a:54:7f:ee:7f:dc:01 S(Adj) 0xfffc0b 10.88.133.100 (nexus-rz1-a)
[Total 3 IEs in Fabric]
nexus-rz1-a# show fcs ie vsan 10
IE List for VSAN: 10
IE-WWN                   IE     Mgmt-Id Mgmt-Addr (Switch-name)
10:00:00:05:1e:90:57:27 S(Adj) 0xfffc01 10.88.133.110 (bc-san1)
20:0a:00:2a:6a:72:ba:01 S(Adj) 0xfffc1c 10.88.133.105 (nexus-rz2-a)
20:0a:54:7f:ee:7f:dc:01 S(Loc) 0xfffc0b 10.88.133.100 (nexus-rz1-a)
[Total 3 IEs in Fabric]
I try to distribute the zoneset this way:
zoneset distribute vsan 10
Zoneset distribution initiated. check zone status
nexus-rz1-a# show zone status
VSAN: 10 default-zone: deny distribute: full Interop: 2
    mode: basic merge-control: allow
    session: none
    hard-zoning: enabled broadcast: disabled
Default zone:
    qos: none broadcast: disabled ronly: unsupported
Full Zoning Database :
    DB size: 6291 bytes
    Zonesets:1 Zones:62 Aliases: 44
Active Zoning Database :
    DB size: 10243 bytes
    Name: FABRIC1 Zonesets:1 Zones:60
Status: Zoneset distribution completed at 08:06:00 UTC Dec 3 2013
nexus-rz2-a# show zone status
VSAN: 1 default-zone: deny distribute: active only Interop: default
    mode: basic merge-control: allow
    session: none
    hard-zoning: enabled broadcast: disabled
Default zone:
    qos: none broadcast: disabled ronly: unsupported
Full Zoning Database :
    DB size: 4 bytes
    Zonesets:0 Zones:0 Aliases: 0
Active Zoning Database :
    Database Not Available
Status:
VSAN: 10 default-zone: deny distribute: full Interop: 2
    mode: basic merge-control: allow
    session: none
    hard-zoning: enabled broadcast: disabled
Default zone:
    qos: none broadcast: disabled ronly: unsupported
Full Zoning Database :
    DB size: 6291 bytes
    Zonesets:1 Zones:62 Aliases: 44
Active Zoning Database :
    DB size: 10243 bytes
    Name: FABRIC1 Zonesets:1 Zones:60
Status: Activation completed at 13:03:42 UTC Dec 2 2013

Nexus 5548 L3 daughter card flapping

Hi guys,
Anyone of you here that experienced the logs below on their Nexus box:
2011 Dec 12 06:24:45 GDCNXS5K01 %BTCM-2-BTCM_LOG_ROUTER_ERR: router card in slot 3 has internal link(s) flapped: router ports down: 0x1a108000 0x1a109000 0x1a10a000 0x1a10b000 0x1a10c000 0x1a10d000 0x1a10e000 0x1a10f000
I am getting this log at least once a day. Seems like it is shutting down the SVI of the box after the said log occured. Good thing I have enable vPC and I am able to access the NXS5K through the vCP keepalive link (mgmt).
I have two Nexus 5548, but only one is experiencing the said error.
Any inputs, suggestions would be greatly appreciated.
Thanks,
Edzel

We had this same problem this past weekend, only in module 2 on a 5596.
In our case, we had rebooted our primary Nexus and found the following message immediately preceeded the BTCM error you noted:
%$ VDC-1 %$ %NOHMS-2-NOHMS_DIAG_ERROR: Module 2: Bootup diag detected major event: Forwarding ASIC failure: Ethernet2/9 Ethernet2/10 Ethernet2/11 Ethernet2/12 Ethernet2/13 Ethernet2/14 Ethernet2/15 Ethernet2/16
We replaced the module. A "show diag results module 3" would probably show you the same thing. However, I don't think the error message will show up until you reboot.
If your flapping Nexus is secondary, you probably won't notice anything major, but if it is your primary, it would probably affect your routing.

Urgent help: L3 daughter card for Nexus 5548

Hi
We have 2 Nexus 5548 which is in one vPC doamin. All the servers are teamed to these switches
Requirement
We have to install New L3 daughter card.(N55-D160L3-V2(=))
I have gone through the Cisco websites and found that we have to do the following things
1. software version:
i Nexus 5548P Daughter Card (N55-D160L3)
Before installing a Layer 3 daughter card (N55-D160L3) into a Cisco Nexus 5548P switch, you must upgrade to Cisco NX-OS Release 5.0(3)N1(1b) or NX-OS Release 5.0(3)N1(1c) and then install the card into the chassis.
http://www.cisco.com/en/US/docs/switches/datacenter/nexus5000/sw/release/notes/Rel_5_0_3_N2_1/Nexus5000_Release_Notes_5_0_3_N2.html
2. license:
Also in order to enable this module following license should present on N5k device:
LAN_BASE_SERVICES_PKG - it's free and lifetime.
https://supportforums.cisco.com/thread/2121574
I have 2 questions
1- In cisco documentation its says that these cards will be installed in the front where I/O module is and after NX OS 5.X they are hot swappable
Does that mean that no reboot will be required after installing this module (keeping in mind its the first time) so i am confused about the wording ???
Does license installation requires reboot??? in short if you are installing for the first time do we require a reboot ???? that is my main question
2- I have heard there is a known bug which keep rebooting the switch after installation of L3 card
http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCtl45495
has that been address in any version of license or NS-OS yet???
Thanks heaps guys
If the module is still offline when the requirements are met above, it could be a bug.(CSCtl45495) Try reloading the switch.

1- In cisco documentation its says that these cards will be installed in the front where I/O module is and after NX OS 5.X they are hot swappable
Does that mean that no reboot will be required after installing this module (keeping in mind its the first time) so i am confused about the wording ???
Answer: -- Yes no reboot is required.
Does license installation requires reboot??? in short if you are installing for the first time do we require a reboot ???? that is my main question
Answer: As you are installing the license for the first time reboot of the box is not required.
2- I have heard there is a known bug which keep rebooting the switch after installation of L3 card
http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCtl45495
has that been address in any version of license or NS-OS yet???
Answer;--No this is not fixed yet.
HTH
Regards
Inayath
********Please do not forget to rate the post if this info is helpfull.

Nexus 5548 Layer 3 daughter card insertion

Hello there,
I am planning to install Nexus 5548 Layer 3 daughter card. I found the hardware removal procedure on Cisco website but it doesn't say whether it's hot plugged or not. (Since I've to remove existing L2 module so I guess the box needs to be powered off but not sure). Has anybody had the experience in doing the upgrade to share?
Thanks in advance
Regards,
Chinnawoot
PS. Detail of the running system
Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Copyright (c) 2002-2014, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained in this software are
owned by other third parties and used and distributed under
license. Certain components of this software are licensed under
the GNU General Public License (GPL) version 2.0 or the GNU
Lesser General Public License (LGPL) Version 2.1. A copy of each
such license is available at
http://www.opensource.org/licenses/gpl-2.0.php and
http://www.opensource.org/licenses/lgpl-2.1.php
AUUT05TRUSDS03# show ver
Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Documents: http://www.cisco.com/en/US/products/ps9372/tsd_products_support_series_home.html
Copyright (c) 2002-2014, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained herein are owned by
other third parties and are used and distributed under license.
Some parts of this software are covered under the GNU Public
License. A copy of the license is available at
http://www.gnu.org/licenses/gpl.html.
Software
BIOS:      version 3.6.0
loader:    version N/A
kickstart: version 7.0(1)N1(1)
system:    version 7.0(1)N1(1)
Power Sequencer Firmware:
             Module 1: version v2.0
             Module 3: version v2.0
Microcontroller Firmware:        version v1.2.0.1
SFP uC:    Module 1: v1.0.0.0
QSFP uC:   Module not detected
BIOS compile time:       05/09/2012
kickstart image file is: bootflash:///n5000-uk9-kickstart.7.0.1.N1.1.bin
kickstart compile time: 3/19/2014 14:00:00 [03/20/2014 10:09:46]
system image file is:    bootflash:///n5000-uk9.7.0.1.N1.1.bin
system compile time:     3/19/2014 14:00:00 [03/20/2014 13:54:43]
Hardware
cisco Nexus5548 Chassis ("O2 32X10GE/Modular Universal Platform Supervisor")
Intel(R) Xeon(R) CPU         with 8253860 kB of memory.
Processor Board ID FOC172441CQ
Device name: AUUT05TRUSDS03
bootflash:    1966080 kB
Kernel uptime is 172 day(s), 21 hour(s), 56 minute(s), 9 second(s)
Last reset at 126063 usecs after Wed May 21 12:35:50 2014
Reason: Reset Requested by CLI command reload
System version: 7.0(1)N1(1)
Service: power-sequence cycled
plugin
Core Plugin, Ethernet Plugin
AUUT05TRUSDS03# show lic usage
Feature                      Ins Lic   Status Expiry Date Comments
                                 Count
FCOE_NPV_PKG                  No    -   Unused             -
FM_SERVER_PKG                 No    -   Unused             -
ENTERPRISE_PKG                No    -   Unused             -
FC_FEATURES_PKG               No    -   Unused             -
VMFEX_FEATURE_PKG             No    -   Unused             -
ENHANCED_LAYER2_PKG           Yes   -   Unused Never       -
LAN_BASE_SERVICES_PKG         No    -   Unused             -
LAN_ENTERPRISE_SERVICES_PKG   No    -   Unused             -

I ended up getting the answer from TAC. First put in these two commands:
test ethpm l3 enable-show-iport
test port-channel l3 enable-show-ipc
Then you will get some new port channels showing up (127 and 128).
I'm not sure what 128 is for, but 127 is the internal port channel for the L3 card. Then you can view stats and poll with SNMP against the interface...
show interface port-channel 127

Nexus 5548 - %ARP-3-DUP_SRCIP_PROBE: Duplicate address Detected

Hello.
Looking for some assistance on the following please, I'll try to include a lot of detail:
I noticed we're receiving repeating messages on a pair of Nexus 5548UP switches, regarding duplicate IP's, and the IP's in question are the mgmt0 of each respective Nexus switch; which are connected to each other and uplinked to two 3750X switches which are also linked to each other (not as a stack, with optics).
Here is a sample of the syslog message: %ARP-3-DUP_SRCIP_PROBE: arp [####] Duplicate address Detected. Probe packet received from zzzz.zzzz.zzzz on mgmt0 with destination set to our local ip, xxx.xxx.xxx.xxx
And in ascii art, here is a diagram: SW1&2 are 3750X (running 15.x code) and NX1&2 are Nexus 5548UP (running 6.x code)
SW1---SW2
| |
NX1---NX2
Pretty basic box/"ring", just in case the diagram doesn't format well, with rapid spanning-tree in effect. The Nexus are Layer2 only, and the 3750X's are Layer 2 & 3 /w HSRP on a few SVI's in them. All vlans can pass over the connecting trunks. And on the Nexus, the management interface (mgmt0) is connected to 3750X (NX1 to SW1 and NX2 to SW2); e.g. management is done over this vrf interface, versus it flowing through a trunk interface to a SVI on the Nexus.
I know these messages to be erroneous as far an being actual duplicate IP's on the network, and have seen a few posts that indicate a command ("no ip arp gratuitous hsrp duplicate") typically referencing a Nexus 7000 setup has helped, but obviously as described that's not involved here. Note: Placing that command on the mgmt0 interface of the two nexus had no positive effect. The messages didn't start showing until after HSRP was enabled on the applicable 3750X SVI's - so seems a likely correlation.
Essentially looking to clear this up (ideally) or suppress the messages since they're false. Any ideas?
Thanks!

For those encountering this same issue, here is some information that may lead you to a resolve.
I decided to open a TAC case to get some direct assistance, and I was directed to the 3750X's and a new feature in the 15.x code, "ip device tracking". I was directed to remove that without specific details / steps on how to best do it (e.g. "no ip device tracking" does not remove it from the global config, as of 15.2(1)E anyway and is the most current at the time of this posting), and that didn't take, giving the message: % IP device tracking is disabled at the interface level by removing the relevant configs. However, after doing some research on the command, I can across some similar posts on 15.x code and duplicate IP messages.... Here's two posts I referenced:
https://supportforums.cisco.com/thread/2244042
https://supportforums.cisco.com/thread/2239656
I opted for the "no macro auto monitor" command in the 3750X's in global config, as mentioned in the above post(s) - This did stop the messages from occurring in the Nexus switches. IMPORTANT NOTE: I noticed that it did appear to bounce all the switch ports however, which could impact production - Be advised!
I cannot speak to if the interface level command 'nmsp attach suppress' is a better route to go, which is also referenced in the posts (first one primarily) - I went the other route to not have all the extra config line entries. I have asked Cisco what the true impact of the "no macro auto monitor" command is, and am waiting a response - Ideally there's little to none, probably depending on if you want to make use of device tracking or not... in my case, I suspect I don't have a need for this and thus there's no impact - I shall see.
It would be ideal if code is released to disable this service / feature in the future more gracefully and/or code changes are done to remedy this issue so you can have the feature enabled (or not). I akin this much like the "vstack" service that was introduced around 12.2(55/58)SE IOS that couldn't be disabled & left an open TCP port (not good for security scans), then with 12.2(58)SE2 they allowed it to be disabled (e.g. "no vstack" in global config).
Hopefully these details prove of value.
Regards.
NOTE: Since it doesn't seem you can"answer" your own posts, which seems silly; please note I consider this item resolved / answered.

Using 24 ports on 5548 for non fabric devices with 24 FEX's attached.

If you have 24 Nexus 2248 fabric extenders dual-homed to two Nexus 5548 switches using one 10Gig port from each 2248, can the remaining 24 ports on each 5548 be used for non fabric devices? (Ex. Blade server chassis with integrated switches)

Yes, you can use the remaining 24 ports for whatever you want to connect. It could connect to IBM chassis, other routers, switches, etc...
HTH

NTP Nexus 5548s

I know that with the Nexus switches that we must use the management port and the management vrf for services such as NTP, SNMP etc. I have this configured on my 5548 and it still will not sync with NTP.
ntp server 10.1.0.63 prefer use-vrf management
ntp server 10.1.0.65 use-vrf management
ntp peer 10.100.4.156 use-vrf management
ntp source 10.100.4.155
I verified connectivity to the NTP server by pinging it:
5548-A# ping 10.1.0.63 vrf management
PING 10.1.0.63 (10.1.0.63): 56 data bytes
64 bytes from 10.1.0.63: icmp_seq=0 ttl=126 time=1.095 ms
64 bytes from 10.1.0.63: icmp_seq=1 ttl=126 time=0.657 ms
64 bytes from 10.1.0.63: icmp_seq=2 ttl=126 time=1.242 ms
64 bytes from 10.1.0.63: icmp_seq=3 ttl=126 time=0.783 ms
64 bytes from 10.1.0.63: icmp_seq=4 ttl=126 time=0.735 ms
Maybe it is working and I dont know it. When I run "show ntp status", I get this
5548-A# show ntp status
Distribution : Enabled
Last operational state: Commit operation successful
5548-A#
5548-A#
5548-A# show ntp peers
Peer IP Address               Serv/Peer
10.100.4.156                  Peer (configured)
10.1.0.63                     Server (configured)
10.1.0.65                     Server (configured)
5548-A#
i am used to seeing a different output from show ntp status. It is not telling me that it is synchronized. Please tell me what I am missing here.
Bruce

Hi Bruce,
This looks good. I admit NTP isn't as easy to verify on NX-OS as it is on IOS, this indeed causes confusion.
In your case you see the * for 10.1.0.63, so the device is synched to this source. You can verify with:
# show ntp statistics peer ipaddr x.x.x.x
with the above IP.
Here is a brief explanation:
* - selected for sync
Device is synchronized to this source
+ - peer mode(active)
The mode in which a host has configured itself to poll a time server
that it might synchronize with. In this mode, the host also allows
itself to be polled by that time server.
- - peer mode(passive)
The mode in which a time server is polled by a host that has configured
itself in ``symmetric active mode''. In this mode, the time server can
also poll that host.
= - polled in client mode
The mode in which a host polls a time server that it might synchronize
with, but it will not respond to polls from that time server.
I hope the above helps, but this looks as if you are up and running at this point.
Thanks,
/gary

C220 M4 w/ VIC1225 and Nexus 5548

I have four UCS C220 M4 servers that each have a VIC 1225 and are connected up to a Nexus 5548. I have set them to trunk ports and have set the appropriate VLANs in ESX and the portgroups. I can ping the gateway and other hosts on the network, but for some reason I can't ping any of the other C220 M4 servers that have a VIC1225. All of the C220's can ping other devices on the network, but not each other. Is there some setting I need to modify on the VIC or switch? Currently the VIC is running as Classical Ethernet mode.

There is no special configuration to make connectivity work in the rack servers, I assume these servers are in standalone mode and not integrated with UCSM.
What L3 device is doing your Inter-Vlan routing? Is it the N5K these servers are connected to or there is another device doing this job? If it is the N5K, are all the servers in the same network segment? I mean, is there a single SVI or multiple? can your Nexus 5K ping each of the servers?
-Kenny

Nexus 5548 - PFMA-2-PS_HIGH_VIN message on device with DC power supply

Similar Messages

Maybe you are looking for